Runtime errors on Led64

[Andras]

Hi,

I connected 30 leds to the Led64 unit. Most of them do work, however whenever I try any of the window-heat, probe-heat leds in any combination, I get a division by zero error.
What's strange about it is, that it just works fine when I'm doing the config inside the prg, but after saving it, the next time I fire up FS2Phodget it quits with the error. :mad:
Also, the WindowOverHeat variables are not yet in the config, I could add them manually if the core worked...

regards
Andras

[alandyer]

Andras,

Will fix that error today.

"Division by Zero" error is very embarrasing for a programmer.
Will send pic of my red face :)

Thanks for heads up.

Regards,
Alan.

[Andras]

Will fix that error today.
"Division by Zero" error is very embarrasing for a programmer.
Will send pic of my red face

Hi Alan,
No need for the pic... it ALWAYS happens, I know that...
It's great you pick up the problems so quick.
I'm just eagerly waiting for the update, those leds look so nice when working...

regards
Andras

[Andras]

Hi Alan,

Thanks for the new version. I wish it was perfect, but:
Small problem...
Instead of the 'division by zero' error which is gone, now when using the led64 I get a runtime error '6' overflow...

regards
Andras

[alandyer]

Andras,

What FS function fom drop down list did you assign to LED that gave you error?
Will help me replicate error.

Alan.

[Andras]

What FS function fom drop down list did you assign to LED that gave you error? Will help me replicate error.

Hi Alan,

I was assigning the window-heat and probe-heat led for ther Pmsys boeing.
The error comes in even just after assigning the
LPitotFail and LPitotFail2 offsets after each other, but other combinations also trigger the problem as well.
Of course I can send a config file, I don't see any attachment possibility here in the forum.

regards
Andras

[alandyer]

Thanks, Andras.

This will help me replicate problem.
Give my another day or so to figure out and fix.
Is that OK?

Regards,
Alan.

[Andras]

Give my another day or so to figure out and fix.
Is that OK?

Hi Alan,

OK? More than that... perfect.
Thanks for your efforts!

regards
Andras

[imported_MattO]

Just wanted to ad, and hope it helps.

I get the same "runtime error '6' overflow..." But only after the initial setup of the LED's and then returning into FS2Phidget.

I'm not sure if I'm saying this right.... I'll try this.

I set up the LED's in FS2Phidget, i.e. LED 0 assigned to an offset. I test LED 0 and it works, I continue to enter the rest of my LED's, and test, they all work.

I End FS2Phidget, and then load FS2phidget, After loading, you must have it look at the PhidgetLED2872.ini file, because it seems when it looks at the 2nd assigned LED (index 8), the runtime error '6' overflow... occurs.

Here's the first 9 assignments of the PhidgetLED2872.ini file,

[Output 0]
FSID=ND_CPT_LIGHT_ARPT
Enabled=True
Invert=False
SMin=0
SMax=0
[Output 1]
FSID=Unassigned
Enabled=False
Invert=False
SMin=0
SMax=0
[Output 2]
FSID=Unassigned
Enabled=False
Invert=False
SMin=0
SMax=0
[Output 3]
FSID=Unassigned
Enabled=False
Invert=False
SMin=0
SMax=0
[Output 4]
FSID=Unassigned
Enabled=False
Invert=False
SMin=0
SMax=0
[Output 5]
FSID=Unassigned
Enabled=False
Invert=False
SMin=0
SMax=0
[Output 6]
FSID=Unassigned
Enabled=False
Invert=False
SMin=0
SMax=0
[Output 7]
FSID=Unassigned
Enabled=False
Invert=False
SMin=0
SMax=0
[Output 8]
FSID=ND_CPT_LIGHT_NDB
Enabled=True
Invert=False
SMin=0
SMax=0

Hope this helps.
Matt O.

[Andras]

I get the same "runtime error '6' overflow..." But only after the initial setup of the LED's and then returning into FS2Phidget.

I set up the LED's in FS2Phidget, i.e. LED 0 assigned to an offset. I test LED 0 and it works, I continue to enter the rest of my LED's, and test, they all work.

I End FS2Phidget, and then load FS2phidget, After loading, you must have it look at the PhidgetLED2872.ini file, because it seems when it looks at the 2nd assigned LED (index 8), the runtime error '6' overflow... occurs.

Matt,

I have found the exact same thing. Tried all possible combinations, but I have some settings which do work, whereas some offsets always cause the error.

regards
Andras

[alandyer]

Don't recall seeing ND_CPT_LIGHT_ARPT or ND_CPT_LIGHT_NDB in FSUIPC.

What are those functions?

[alandyer]

Andras,

The example MattO gave me for overflow (and division by zero) problem helped me trace and fix.
Was occuring with bitmapped functions.

I have posted 2.0.5 for download to take care of issue.

Regards,
Alan.

[imported_MattO]

Don't recall seeing ND_CPT_LIGHT_ARPT or ND_CPT_LIGHT_NDB in FSUIPC.

What are those functions?

They're Airbus EFIS off/on button lights, I created in the ini file. It'll be nice to see the EFIS/FCU Offsets as part of the list. I think Jonathan R. is working on it, not sure though.

Matt O.

[Andras]

The example MattO gave me for overflow (and division by zero) problem helped me trace and fix. Was occuring with bitmapped functions.
I have posted 2.0.5 for download to take care of issue.

Alan,

Works nicely so far. Many thanks. :)
Two minor things: when the prg is minimized sometimes it gets stuck in that state and becomes almost impossible to restore it again, specially if other stuff is in the background. Is it possible that it is a memory allocation problem?

The other one is even simpler, it a silly question: what do the led calibration sliders actually do in case of the led64? I changed some but nothing happens.

regards
Andras

[alandyer]

Calibration slider should set thresholds for when LED illuminate and extinguish.
Let me check it out.

[alandyer]

Matt,

Figured it was somthing special for Airbus.
Curiosity got the better of me.

Alan.

[alandyer]

Andras,

Version 2.0.6 has fully functioning calibration for LED64.
Now works same wayas interfacekit digital output.

Alan.

[Andras]

Version 2.0.6 has fully functioning calibration for LED64.
Now works same wayas interfacekit digital output.

Hi Alan,

Yes, now the leds work just fine, but whenever I try to calibrate any of them I get an error 380 'invalid property value' message and the prg quits.

regards
Andras

[alandyer]

Andras,

Many thanks for pointing out bug.
I gray out calibrate button for interfacekit outputs that are not "proportional".
Will definitely need to do the same for LED64.
Will incorporate fix into next release.

Only makes sense to set thresholds for functions that have a range of numbers.
Which is purpose of calibrate button for digital output (LEDs).
Bitmapped functions are either On or Off.

Regards,
Alan.