runtime error 5 !!

[jun]

Hi I'm a beginner of Phidgets.
I purchased some modules, and I could run some examples normally.
I could move servos by using servoslider.exe.
Then I run FS2Phidget2.1.1, but runtime error 5 is displayed and the program shut duwn. I'm using WIndowsXP professional (Japanese version).
The runtime error 5 means "incorrect procedure call or auguments" in Japanese.
Is this specific trouble for Japanese WindowsXP??

The error comes whichever FS9 is runnning or not. And also the error comes with any phidget modules.
I tried to run FS2Phidget without connecting Phidget USB cable, then it run normally, and it also gets data from FS9. Then I connected a Phidget USB..... unfortunately the runtime error 5 appears.

I tested the same way on FS2Phidget30beta, then the runtime error was not displayed and FS2Phidget30beta is running, BUT it can't recognize my Phidget modules.

Any suggestions??

best regards

Junji Hirayama
Project-J http://hira-yama.com

[imported_Jono]

Hi Jun
I'm having the same problem as you. Have you managed to work around or fix it yet? No one has replied to my post either.
I find that if you try the Beta 3, you get a little bit further, i.e. you don't get the runtime error 5 message but the board isn't completely recognised either. If you play with the "dummy" tab, you can get a landing light flick of the switch in the SIM recognnised in the dummy value. BUT, the real board isn't picked up by fs2phidgets and therefore I'm as stuck as you. Oh dear, a waste of money it appears. I just can't understand how everyone else has it working and yet aren't prepared to help us in the posts. Sad really.
Regards
Jono

[luker]

Hi Jono and Jun,

I am also having the same problem as you two are experiencing.

I have contacted Matt (from Phidgets USA) who has replied and said he will refer the problem to Alan to see if it is a software issue on his end. I guess for now we just have to be patient and await any news.

Interestingly, I had an older version of the FS2Phidgets software which did not give the error and was recognising the Phidgets modules (the 8/8/8 board in my case) so it seems like it may be a problem with the current release of the software rather than a problem with the modules so I don't believe you have wasted your money.

Hope we hear something soon.

Cheers,
Luke

[alandyer]

Hi Junji,

A pleasure talking with you again.

Problem is not XP problem.
It was bad coding on my part.
I will be releasing a fix in the next 2-3 days.

My apologies for any inconvenience.

The new version has a push-to test feature that will illuminate all the LEDs on every InterfaceKit and LED64 cards.

There is also more comprehensive documentation on the way.
If this is not available when new version is released feel free to send any question my way on this forum.

Best regards,
Alan.

[JBaymore]

My apologies for any inconvenience.

The new version has a push-to test feature that will illuminate all the LEDs on every InterfaceKit and LED64 cards.

There is also more comprehensive documentation on the way.

Alan,

I haven't had time to do ANY work on my LED64 board... still working on other issues in the cockpit....... but I have been following the "bug" discussion. THANKS for putting in all the time on this stuff........ freeware developers of such valuable and time consuming software don't get thanked enough for sharing their efforts.

I am really glad that you have decided to put in the "test" function that Steve suggested. Steve and I have been "talking" a lot about Phidgets since we both hang out in the "Cockpits" forum over at Simviation. Hope you and the Phidgets folks will look seriously at the 360 degree servo / optical encoder suggestion too.

best,

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

[Steve Daly]

Alan,

Thanks for the "Test" function...it will grossly simplify installations. :)

[imported_Jono]

I will be releasing a fix in the next 2-3 days.



Hi Alan
That's great news. Can't wait for the new version!
Many thanks
Jono :o

[alandyer]

Version 3.0.6 is available for download.

There are some upgrades or should I say, new features:

- Users will not need an editor to update FSUIPC variables.
All editing can be performed with FS2Phidget.
- There is a Push-to-Test button that will light up every LED.
Will display word "TEST" on every TextLCD row.
- FS2Phidget uses MS-FS to detect FSUIPC valid values.
Don't need to look through FSUIPC docs for info.
Only need offset and size.
- Two brightness settings for LED64.
- TextLCD can display the usual text, or an indicator, or a bar graph (like some engine monitors).
- COM1 and COM2 audio selector support.
- Users can work with more than one FSUIPC ini file.
- Possibly better performance.

All the above, and more, is covered in a comprehensive documentation, that is included in the download zip.
Documentaton unzpped is 836k
Documentation includes Quick Tutorial chapter.

Any bugs and suggestions for documentation should be sent to this forum.
I am commited to responding to postings within 24 hours.

Best Regards,
Alan.

[imported_MattO]

>>Version 3.0.6 is available for download.

Where?

Looking forward to it:)
Matt O.

[alandyer]

3.0.7 should be available for download from PhidgetsUSA.com
I'll check with folks - perhaps problem with my upload.

[JBaymore]

I went tot he FS2Phidget page off the main menu and downloaded the file... and got what appeared to be the 3.0 beta!

Alan, when you post q release can you please use the version number in the zip file name....... something like "FS2Phidget3-0-7.zip" or something like that? Might make it eassier to keep trasck of the actuasl version that is being downloaded.

best,

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

PS: It went from version 3.0.6 to 3.0.7 already? :confused:

[alandyer]

John,

I think that's a great idea.
Folks at PhidgetsUSA want me to upload it this way.
I'll speak to folks about it.

Alan.

[alandyer]

Got a little cross-fingered.
All those late nites :o
Its definitely 3.0.7

[luker]

Help Alan/guys !!!

I downloaded the latest version of the FS2Phidgets software (3.0.7). When setting up I was told I needed to upgrade certain files as they were old and then restart my computer. After I did that and tried to setup again I had the same message and problem.

After getting around this problem, the setup seemed to go ok but then I found that no exe file had been extracted, that is, the FS2Phidget.exe did not exist in the source directory so I could not run the application.

Anybody else experience this problem? Can someone help me?

Thanks in advance

Luke

[JBaymore]

Alan,

Your "ammunition" in getting them to agree is that the easier it is for users to work with FS2Phidget........ the more Phidget simpit users there will be... and the more Phidgets thay will sell :D .

I'll try the download again today and see what I get.

best,

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

[Mizzy]

Hi,

Luke, I got same problem when I downloaded the FS2Phidgets307. No .exe file.
I just got my 0/16/16 card today. Can't wait to start. But now I'm stuck with this prob.

ANyone elese got any idea.

Rgds
Mizzy :(

[imported_MattO]

I'm having the same problem as LUKER.

The install stops at "Copying Files..... Processing: oleaut32.dll (6of6)

Matt O.

[JBaymore]

Alan,

I got the 3.0.7 download this morning...... and it SAID 3.0.7 ...... but in light of the message comments above this message... I think I will wait to install it to see how this "shakes out".

Also..... you mentioned a documentation file included with it. In the "extract" process there is no obvious .doc file of any kind. Just the MS bootstrap, the .lst file and the cab file.

In the version that was there a couple of days ago... the one that was supposed to be 3.0.6 and seemed to be the 3.0 beta........ there WAS a .doc file that explained the changes to version 3.0.

I think maybe there is a problem with the way your packaging up the .zip file or something.

best,

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

[Andras]

Hi,

Same here. The exe is missing... :(

Andras

[alandyer]

Houston has identified problem.
I am in process of uploading corrected zip.
Will make announcement when that is available.

[alandyer]

Just heard from mission control.
They have give us a GO for the download.

I checked it out myself.
The executable is there.

[JBaymore]

Houston, executing download procedure on my mark............ ;)


best,

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

[JBaymore]

Houston, reporting download "burn" successful. All systems go.


By the way... after a VERY quick scan I found a missing FSUIPC variable....... GENERATOR_4_BUS_AMPS ...... is apparently missing in the listing.

At a quick glance .....it is a WOW Alan. You've been busy. THANKS!

By the way... where is the "test" function you mentioned?


best,

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

[Andras]

The executable is there.

Hi Alan,

Got it thanks. That's the good part.
The less kind behavior of the new version is that it is giving a lot of errors, unable to connect to fsuipc, quits before it was even able to connect.
Moved all of my old files, did a fresh install, same thing...

It starts at least, but when trying to connect to cards it immediately gives a runtime error 13 'type mismatch' error msg and dies.
Tried it on 3 different PCs with the same result.
Any ideas?

regards
Andras

[cpeckinpaugh]

Alan,
Same thing here.
It won't recognize the Phidget cards and won't connect to FS.
Run Time Error 13!
Type Mismatch.
Then Quits???
Cam

[alandyer]

You should copy your FS2PhUIPC.ini into the \FSVariable folder after installation.

[alandyer]

Are we all using latest phidget.msi ? 2.0.6

[alandyer]

John,

I don't have each and every variable.
Is really easy to add.

Regards,
Alan.

[alandyer]

First thing is to get FS2Phidget to connect to cards.
Press the appropriate button.

If Fs2Phidgets does not connect to at least one card you will not be able to connect to FSim.

Usual problem for not seeing cards is old verion of phidgets.msi.
The latest version is 2.0.6 dated March 8 2005.

[cpeckinpaugh]

Alan,
"Connect to Phidget Cards" button now works. Phidget.msi was the problem.
Don't forget to delete old version before installing new or it won't work.
"Connect to Flight Sim" button still yields Run Time Error 13 - Type mismatch!!
Is it a requirement to run FS2Phidget on a separate machine thru WideFS or for testing purposes can FS2Phidget and FS reside on the same machine?
Cam

[alandyer]

Cam,

Yup - should remove first - just like the Phidgets docs says.

I run FS2Phidget either on same PC as MS-FS or over network.
In both case I have WideFS installed.

My sim, obviously, uses a network.
Would kill Flight Sim processing dozens of cards on same PC.
Most computers today just don't have the horsepower.
Flight simming requires distributed systems.
Unless its a basic setup.
I run about 5 cards on laptop OK.

When I'm travelling, usually on an aircraft, I run MS-FS and FS2Phidget on my laptop.

I tried to replicate your problem on both my systems.
Works fine on mine - I realise this doesn't solve problem :(

What version of FSUIPC are you running ?

What version of MS-FS are you running ?

Have not run bench marks, so please, no solicitations such as:
"How many cards can I run on same PC as FS ? " :)

The answer is the same as to the question:
"How long is a piece of string ?"

Answer: Depends.

[imported_MattO]

I'm not getting as far as some of you.

I'm still not able to complete the install, I've even removed the files from the FS2Phidget Folder.

The install stops at "Copying Files..... Processing: msvbvm60.dll (7of7)", I do the Restart, and run Setup again. and stops at the same place.

No files copied into the FS2Phidget Folder.

Matt O.

[alandyer]

Matt,

When you say "stops" - do you mean install terminates or does it hang ?

You could try and delete the FS2Phidget folder.

Does your zip contain readme.txt ?

Does you cab file contain executable ?

Regards,
Alan.

[imported_MattO]

No, it does not hang. I've deleted the FS2Phidget Directory.

During install, and in the install box, I have:

Copying Files, please stand by.
Processing: msvbvm60.dll (7of7)

Setup Box appears, " Setup cannot continue because some system files are out of date........ Option is to click OK to update files or Cancel to exit.

I take the OK option and the system RESTARTS. I rerun the Setup program and the same as above happens again.

I copied the MSVBVM60.DLL from the CAB file to replace the existing one. Still didn't make a difference.

Matt O.

[alandyer]

Do you get prompts "Do you want to keep existing file ?" during install?

I had two other questions which I do not believe you addressed.

[alandyer]

Matt,

Are you running Windows 2000 or XP ?

I suspect this is an operating system issue.

Alan.

[imported_MattO]

Sorry... must of been sleeping....

>Does your zip contain readme.txt ?
YES

>Does you cab file contain executable ?
YES

>Do you get prompts "Do you want to keep existing file ?" during install?
NO

Matt O.

[imported_MattO]

>Are you running Windows 2000 or XP ?

XP Pro, service pack 1

Matt O.

[imported_dnoize]

i am having exactly the same problem as MattO.

Stef

[alandyer]

Matt,

What SP are you on with XP ?

Alan.

[imported_MattO]

Rather than Pack I meant to say SP 1

Matt O.

[alandyer]

Matt O,

Do a search on you system for MSVBVM60.DLL
Using Windows Explorer hover over this file.
This willl allow you to pick up File Version.

Let me know what version number you are using.

Alan.

[imported_MattO]

Version 6.0.97.82

Matt O.

[imported_MattO]

Just to confirm... Alan, are you still working an this issue, or did I miss something?

For those of you that have 3.09 working (installed), would you let me know what OS version you're running.

Thanks,
Matt O.

[alandyer]

Matt O,

Thought I took care of thaT.
Are you still experiencing this error ?

Alan.

[imported_MattO]

Yes, still experience the same problem Alan, as indicated above.

Since others are using 3.09, it makes me wonder if I'm missing a setting or two in Windows XP Pro.

Is there anyone else STILL experiencing this problem, and if not, how was it resolved? I need to know what I have to do on my end.

Thanks,
Matt O.

[alandyer]

Matt O,

Are you using 3.0.9 ?

Alan.

[alandyer]

Matt O,

What version of phidget.msi are you using?
Should be on latest i.e. 2.0.6
This seemed to fix problem as I recall.

Alan.

[imported_MattO]

No I'm not running 3.09 because I can't install it.

Look back at response 32 to and on.... That's where I'm still at.

Regarding Phidget.msi, yes I've installed 2.0.6.

BTW, I've completely installed FS2Phidget, not on my cockpit computer, my test system computer. My cockpit computer, I'm still using FS2Phidget 2.0.9.

Matt O.

[alandyer]

Matt O,

I know you had problem with installing earlier version.
3.0.9 should have adressed your issue.
Have you attempted to install 3.0.9 ?

Alan.

[imported_737nut]

Matt,
I had the same problem,
Shoot me an e-mail and i;ll send you my file that allowed it to load. Better yet, just come and visit! :D

Rob

[alandyer]

Rob,

Were you planning on sharing that file with me ?

Alan.

[imported_MattO]

Yes, I've attempted to install 3.09.

If other people are able to install it, please let me know (anyone please) if you're running it on Win XP PRO SP1. If so, it's my problem, I'm doing something wrong.

All my Phidget files are up to date.

Matt O.

[Chris97b]

Worked fine for me in XP pro, sp1. I had to delete line 5 from the bootstrap section of setupu.lst; and it installed normally, and works like a charm :)


-Chris

[alandyer]

Matt O,

We'll get you up and running.
Did you download 3.09 from PhidgetsUSA or through the "informal network" ?
I would get that file from Rob.
Really need 2 downloads: Fresh Install and an Upgrade.

Problem is not due to anything you're doing.
This is known problem with Microsoft.
Some aspects of VB 6.0 are not upward compatible.
(Microsoft is trying to get everybody to move to VB.net)
They have bunch of SPs and fixes to address problem.
I would have to start operating like a commercial operation to deal with these kind of issues.
Would need to regression test against versions of Widows, MS-FS, Phidgets and pmSystems. Don't have the resources.

I could upgrade my code to VB.Net ( a world of pain), but everyone would have to install .net runtime (another world of pain).

The other problem that people were experiencing with "other application is busy"
is a kown Microsoft bug. Is affecting many OLE applications such as Word, Visio and Foxpro (and Phidgets).

I encountered this problem myself after a small code change, which I promptly undid. i.e. I thought I had identified problem and corrected code. Has not re-occured on my systems (both running on same PC and on LAN)

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.

Nonetheless, if this really is a problem, I need to fix it.
Hence my questions to those affected on where software was loaded from.
All of those questions have gone unanswered to date.

Alan.

[alandyer]

Matt O,

Yeah, but your XP files are way out of date.
XP is well into SP2.

You did follow the discussion on this forum about XP's File Protection feature, right ?

Alan.

[alandyer]

Chris,

Is that "Bootstrap" or "Bootstrap Files" section.
There's two of them.

I'm guessing you are referring to line in "Bootstrp Files" that reads:
File5=@olepro32.dll

Alan.

[Chris97b]

Yes, the line
File5=@olepro32.dll
in the Bootstrap Files

Sorry, I didn't realize there was a 'bootstrap' section also :D

-Chris


*edit*

FYI, I just read the post about where the files were obtained, I downloaded 3.0.9 from phidgetsusa shortly after it was made available (I'm not sure if perhaps there was a slightly defferent 3.0.9 uploaded later. I will re-download it and check to be sure)

Incedentally, I will be formatting my machine again when my new HDDs arive, so I will check the install/operation on all levels of XP (unpatched, SP1, SP2)

*/edit*

[imported_MattO]

I updated my OS.

SUCCESS!!!!! 3.09 installed beautifully.

Thank You.

Matt O.

[alandyer]

Woooooooohoooooo!

Matt O, Phidget Tower, cleared for takeoff, any runway, pilot's discretion.

[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 :o . Surely FS2Phidget is much more easy to use :D

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.

[imported_MattO]

Alan Delta,

Thank You, for the tech info, I'll check it out!!!

Renowned.... hhhhmmmm I don't know about that, and what record... It's been 15 years, besides you must be talking about B737Nut:) He knows how to fly his B737 real well, I was impressed...

Matt O.

[imported_dnoize]

Stef,

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



No problem Alan, didnt feel accused, just wanted things to be clear ;-)

Trouble shooting chapter would be great. We could all contribute to that !

Stef

[imported_dnoize]

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

We could place a sticky here. with a trouble shooting area and a feedback/bug report form. Allways on top, so everyone had a chance to read it !

Stef