Runtime Error 6, overflow

[Bob Reed]

I am working with one of the World Flight, USA team, Just did a first time install of FS2Phidgets on the PMSystems machine (never been installed on it before) and when they start FS2Phidgts they get "Runtime Error 6, overflow from the FS2Phidgets software. Any ideas?

[737NUT]

Bob,
I got that once on a PMSys install. I just uninstalled and started from scratch.

[Bob Reed]

It's not PM giving us the error.. It is PS2Phidgets.

[James Twomey]

Bob, What version are they running?

If I remember correctly, getting the net framework updated with my PMsystems machine worked. I take it that updating that didnt work?

[AndyT]

Alan just did a big update to FS2Phidgets and its sensetive to versions. You need to uninstall and registry clean then reinstall the newest versions. You can get them in the download section here at MyCockpit.

[CocnutAir]

Bob,

What Phidget cards are being used?
You could send me logs and ini files.

Regards,
Alan.

[Shamrock224]

Got this sorted guys, thanks.
We just re-installed the Phidgets MSI and FSPhidgets and it went away.

[DarylL]

Good Day all;

I recently installed FSUIPC and FS2Phidgets on a new laptop and everything worked perfectly for a short while. I did some 'tweeking' in the variables editor and now, every time i try to start the interphase emmulator I get an error code of "runtime error: 11 - divide by 0"

I have uninstalled and reloaded both FSUIPC and FS2Phidgets several times without any succes but the problem remains... I can't use the interphase emmulator at all:(

any ideas??

[CocnutAir]

Daryl,

Zip me your ini files for fs variables and interface emulator.
This will permit me to replicate your problem.
Send to alan@coconutair.com.

Regards,
Alan.

[CocnutAir]

Which FS Variable were you tweaking?

[CocnutAir]

Daryl,

Thanks for those ini files. They really helped.
I was able to replicate the error you were getting.

Error is being caused by the settings for sensors 2 and 3 on the emulated intefacekits.
Specifically, the "range of travel" settings for the sensors.
This is due to either:
(a) bug in program allowing a zero range.
(b) manually editing the ini file (never a good idea).

I suspect the problem is (a).

Here is a workaround to apply until such time as I publish rectified program.

Open your PhidgetInterfaceKitEmulation1.ini file with text editor, say, Notepad.

Scroll down to the [Sensor 2] section.
The SMin and the SMax values should not (must not) be the same.
Change SMax=0 to SMax=1000

Scroll down and do same for [Sensor 3]
Smin and Smax are both 485.
Change SMin=485 to SMin=0

Save your settings and you should be good to go.

Regards,
Alan.