runtime error 5 !!

[JBaymore]

At that time only persons who had copies of this code were myself and 3 other persons who were helping me de-bug.
Have suspicion that this interim version is lurking out there, distributed via the informal network.
Bottom line: ensure you are installing code from the PhidgetsUSA web site.

Alan,

Just to put your mind to rest...... the "test" version of FS2Phidgets 3.0.9 that you sent to me has not left my machine. So that is one "informal" source that is NOT a source .

I am busy working on other aspects o my pit right now...... but soon I will start hooking up the Phidgets. Can't wait!

best,

............john

[imported_MattO]

Alan, should I be able to use all of my .ini files from the previous version 2.x.x?

When I installed 3.09 on top of my 2.0.6 version, on my cockpit computers, I came up with errors when Connecting to Phidgets. Of course this is after setting up the Card Manager.

If you think it's easier, better, or whatever.... to reassign, I'll do it... No Problem

Matt O.

[alandyer]

Matt Oscar,

Did you copy your old FS2PhUIPC.ini to FSVariable folder after you installed ?

Alan.

[imported_MattO]

Alan,

Matt Oscar??????

Yes, I did copy the old FS2PhUIPC.ini to FSVariable folder. I get a:

Run Time Error '9'
Subscript out of range

This happens when looking at the 9th module (Encoder 4046).

Of course FS2Phidget shuts down immediately, and no log of the events.

Matt O.

UPDATE:

I started elimenating modules and found this ERROR only occures with TXT LCD's

[jun]

Hi Alan and Matt

I came back here after almost one month interval, and I was very surprized to know my thread is growing bigger.
I was too busy to make my original VB6 program to control Phidget servo instead of trying to use Runtime-errored FS2phidget . And I could succeeded to link servos to FS2004.

Well Alan, thank you for new FS2phidget. I encountered exactly same trouble as Matt's case. I could not install. But now I could install it after I updated my WindowsXP to SP2!!
Thank you Matt for informations.

Now I'm wondering which program I should use, my original program or FS2phidget . Surely FS2Phidget is much more easy to use

best regards

Jun

[alandyer]

Hi Jun,

I am pleased things are working out for you.

The most important thing is to ensure that you are making progress on your B747.
You should use whatever software works for you.
No-one will be offended.
If you are happy, then I am happy.

Best regards,
Alan.

[imported_dnoize]

At that time only persons who had copies of this code were myself and 3 other persons who were helping me de-bug.
Have suspicion that this interim version is lurking out there, distributed via the informal network..

Just to get things clear...my version did never leave my computer either...

Stef

[alandyer]

Stef,

Thanks for your assistance with the debugging.
Truly appreciated.
My apologies if it sounded like I was accusing you of something.

I have no problem with distributing.
Its freeware.
I want as many people to share our hobby as possible.
It can only benefit all of us.

Just wanted to know about distribution to help me debug a problem some are reporting.
That was reason for my question.

Sometimes problems are reported, but with no details,
which makes resolution harder.

Its like taking your car to a workshop and saying to the mechanic
"My car makes a strange noise".

Just realised :
Perhaps I should add a Troubleshooting chapter to documentation and web site.
Your thoughts, Stef.

Thanks again,
Alan.

[imported_MattO]

Alan Delta,

"Troubleshooting Chapter"

Fantastic idea, or something like FAQ. Just a other thing for you to do

"Sometimes problems are reported, but with no details, which makes resolution harder."

I think there a lot of NEWBIES in our hobby, and it always seems it is taken for granted they know how to report BUG problems. I've BETA tested a lot of software, and surprisingly even some authors didn't really know what details they wanted, or at least until a BUG was reported.

I recommend, a BUG report procedure, outlined in the Docs, and or either post it here. Alan, it would make your job easier, at least, I would hope

Just my two cents worth.

Matt Oscar

[alandyer]

Matt Oscar,

Appreciate the feedback.

On the subject of problems.
I had a look at heading problem.

- Go into the FS Editor (FS EDit button).
- Rotate heading knob on FS screen using mouse.
(I was using the MS-FS2002 delivered B737 MCP).
- Observe the values being generated by FS.
- You will observe that headings in the range 180 - 359, are represented as negative numbers. For example, 359 is -2, 358 is -3, 180 is -180.

Set your low value (using FSEdit function) to -180 and high value to 179.
Calibrate the step value to 1 (which is the default).

Step 1 in Troubleshooting:

- Confirm FS Value settings is correct.

B737nut's problem with the strobing Dual Bleed and incorrect Throttle Reversers turned out to be:

- No FS Type was specified for FS variable.
- When those were set using FSEdit problem evaporated.

The current version does not make it apparent that FS Type is not set.
(Defaults to Digital on screen)
3.0.10 will have an additional button labeled RAW - indicating that raw values from FS are being used.

I realize this does require:
- some investigation work on the part of the builder.
- reading the manual.

My concern is that I will spend a lot of time adding section to documentation, but nobody will read it.

Every pilot I know reads the POH and checklists.
(This definitely applies to you, as you are a renowned pilot and instructor).
Do you still hold that record!

Regards,
Alan.