FS2Phidget doesn't populate index's for LED 64

[Mickey_Techy]

Been trying to get my Phidget LED-64 Advanced board to interface with FS2Phidget for last few days, but, ostensibly, there is some critical step I'm missing.

I'm using ver 4.3.86 of FS2Phidgets and when I test the program with built in emulator, it works quite fine.
However, when I physically connect my LED-64 board, thought it recognizes the board, but the component list doesn't get populated. A picture of how it looks to me as as shown below:-

7778

As you can see, FS2Ph is recognizing my FSX installation, my FSUIPC installation and is also friendly to the Phidget drivers installed. It even recognizes my board, but the components list is totally empty.

I have also included a picture, while testing out the built in emulator.
7779

Please help/advice. What vital piece of procedure am I missing.

Thank you all, in anticipation.

[Mickey_Techy]

Request/question for Coconut Air,

Searching through the forums posts, I came across an "old" post from this thread. (http://www.mycockpit.org/forums/fs2phidget-users/21002-help-please-fs2phidgets-5-0-21-a.html)

I quote,


................

Upgrading to any version was a waste of time. No version of Fs2Phidgets supports PhidgetsLED Adavanced.
Not yet.



Alan, could you "please" confirm if the above statement is still true. I'm using 1032_Phidgets_LED64_Advanced board, with FS2Ph Ver 4.3.86

Is this board supported on this version of FS2Ph.

Regards,

[Mickey_Techy]

Forums admins, veteran users, anybody?
Not a single suggestion, advice, offer of help!

I have always found hobby pit builders to be a helpful community.

[CocnutAir]

The yellow and the text on the Phidget Manager indication shows you have latest Phidget driver installed, but software is expecting earlier version. I will send you an updated version that is built against latest driver. Will send as response to PM you sent me. Latest version also supports FSUIPC virtual joystick buttons. i.e. can assign Phidget digital input to an FSUIPC virtual joystick button. Looks like you have an expectation of getting a response from forums within 24 hours. Pressing a lot of buttons when you don't. I can understand your eagerness to make progress on your project but this is a hobby for most people and not a support center with guaranteed service levels. I have just come out of hospital and looking for work. Between doctor's appointments and job interviews I answer this forum as soon as I can. Being a nice guy I dropped what I was doing and took care of you.

[CocnutAir]

Sent you updated software.

[Mickey_Techy]

The yellow and the text on the Phidget Manager indication shows you have latest Phidget driver installed, but software is expecting earlier version............

Actually, I did notice that, but since it wasn't colored in red, I disregarded that information.


.............I will send you an updated version that is built against latest driver...............

Thank you Sir.


..................Looks like you have an expectation of getting a response from forums within 24 hours. Pressing a lot of buttons when you don't. I can understand your eagerness to make progress on your project but this is a hobby for most people and not a support center with guaranteed service levels...........

My bad. I accept, and humbly apologize.


.............I have just come out of hospital and looking for work. Between doctor's appointments and job interviews I answer this forum as soon as I can. Being a nice guy I dropped what I was doing and took care of you.

...am really feeling humbled now. I have no words to express how I feel.
Do take care, wish you get well soon.

[Mickey_Techy]

Sent you updated software.

Copy that.

Will report how it goes!

Many thanks, again!

[Mickey_Techy]

Tested out with the updated version created by Coconut Air.

The issue of compatibility with latest Phidget driver is now sorted out. But, certain newer issues have now manifested themselves.

Firstly, as soon as I start FS2Ph, the FS2Ph process crashes within the first 4 seconds (I know it from a notification I receive from a program called 'Soluto', which monitors such stuff), but the GUI still remains on screen.

The Phidget control panel detects my LED-64 correctly, as shown below:-
http://i842.photobucket.com/albums/zz345/AviaScorp/FS2Phidgets/PhidgetCP.png (http://s842.photobucket.com/user/AviaScorp/media/FS2Phidgets/PhidgetCP.png.html)

When I double click on the board, to launch its UI, I can see various adjustable properties of the board, as shown below:-
http://i842.photobucket.com/albums/zz345/AviaScorp/FS2Phidgets/PhidgetCPFull.png (http://s842.photobucket.com/user/AviaScorp/media/FS2Phidgets/PhidgetCPFull.png.html)

Like I mentioned above, even though I get a caution that FS2Ph has crashed, but the GUI still keeps running. A picture of GUI is as shown:-
http://i842.photobucket.com/albums/zz345/AviaScorp/FS2Phidgets/42907152-54ff-48fd-8b1e-0c81fc5edc0c.jpg (http://s842.photobucket.com/user/AviaScorp/media/FS2Phidgets/42907152-54ff-48fd-8b1e-0c81fc5edc0c.jpg.html)

The GUI tells me, it's now happy with the Phidget driver. It also tells me that no Phidget is attached to the computer, while it actually is. As a matter of fact, the GUI also detects the LED64, it's just not showing it. I discovered it by clicking in the space marked with red circle. I have assigned two LEDs at index 0 & 1 to certain variables. After I click in the blank space, I'm able to see these assignments. A picture of my desktop is attached below:-
http://i842.photobucket.com/albums/zz345/AviaScorp/FS2Phidgets/09a87eca-a501-479f-83f0-e0e6b07f9a34.jpg (http://s842.photobucket.com/user/AviaScorp/media/FS2Phidgets/09a87eca-a501-479f-83f0-e0e6b07f9a34.jpg.html)


The digital outputs shown above are not enabled, and the options to enable them are grayed out:-
http://i842.photobucket.com/albums/zz345/AviaScorp/FS2Phidgets/PhidgetEnableAll.png (http://s842.photobucket.com/user/AviaScorp/media/FS2Phidgets/PhidgetEnableAll.png.html)

I repeated the above process a few times, including after restarting my computer a couple of times, but the results are repeatedly fairly consistently. On one occasion, I waited on the GUI for about 5 minutes, and I could see my LED board in the list of Phidgets, but I still couldn't "enable" it.

Also, I have noticed, with FS2Ph running, it seems to take control of LED UI from Phidget Driver Control Panel. With FS2Ph running, one can't change the properties of individual LEDs through it UI (I can understand that, since I think, this can now be accomplished from within FS2Ph). A combined picture of all the GUI/UI's running is as shown:-
http://i842.photobucket.com/albums/zz345/AviaScorp/FS2Phidgets/PhidgetComplete.png (http://s842.photobucket.com/user/AviaScorp/media/FS2Phidgets/PhidgetComplete.png.html)

If there is any other information I need to provide, please do let me know.

Regards,

Mickey

Edit: For some reason, the pictures are not showing as a part of the post, but as links to attachments. Atleast on my computer, I was able to view them in a separate browser tab/window.

Edit-2: Uploaded picture to an online photo-repository and edited this post to include links to these pictures. Hopefully, the pictures should now be visible to other forum users.

[CocnutAir]

I cannot see links. I get error: Invalid Attachment specified. If you followed a valid link, please notify the administrator (http://www.mycockpit.org/forums/sendmessage.php). Also when I enter this quick reply the return key does not produce new line. Hence, the continuous text. Matt move admin of this web site offshore. Since then has had problems.

[CocnutAir]

send me you Fs2Phidget log file. <inserted bunch of spaces to format this> This file is in your FS2Phidget folder. Filename is Fs2Phidget.log

[Mickey_Techy]

send me you Fs2Phidget log file. <inserted bunch of spaces to format this> This file is in your FS2Phidget folder. Filename is Fs2Phidget.log


Updated the forum post (two posts above) with links to pictures. I am hoping, you should be able to view pictures of screen-shots now. If it still doesn't work for you, I will figure out some other way.

Forwarded the log file through PM.

Thank you for looking into this.

Regards,

Mickey

[CocnutAir]

Tried an LED-64 version 200 card (same as yours)
with same version of software you are running.
Works fine.
Looking at your log I see one major difference.
When software requests number of components on LED-64 from the Phidget Manager, the number 2 is being returned.
On my system that number is 64.
Program gets settings for first component (index 0)
Is failing when getting setttings for next index.
Difference between 64 and 2 is 1000000 and 10 bits.
What harware are you using? 32 or 64 bit?
What operating system are you using?
You mentioned system monitoring software and software for remote access.
Is this a work computer?

[Mickey_Techy]

What operating system are you using?

Windows 7, 64 bit, home premium



You mentioned system monitoring software and software for remote access.

I use a web based application called 'Soluto (https://www.soluto.com/Login)' to monitor my system (haven't found it exceptionally useful and am planning to remove it shortly).

For remote access (either providing or gaining), I use Teamviewer (http://www.teamviewer.com/en/index.aspx) (It's free for private use).



Is this a work computer?

Nope. It's my home, gaming computer.



What harware are you using? 32 or 64 bit?

Not sure I understand this correctly. Don't know about my hardware, but, my OS is a 64 bit OS. Accordingly, I had downloaded 64 bit Phidget libraries (is/was this an incorrect choice??)

Details of my hardware are (Please disregard details, if this is not what you were asking):-

Intel Core i7 920 DO 2.67 OC 3.49 GHz processor,
Corsair 6GB Triple Channel DDR3 667 MHz Memory,
MSI X58 Pro-E MoBo,
Antec Kuhler H2O 920 Liquid Cooler
Two Graphics cards (nVidia GeForce GTX 260 896 MB & nVidia GeForce GTX 660 2GB), with Matrox TripleHead2Go.
3 x 23" LCD monitors (LG) + 1 X 24" monitor (Samsung) + 1 X 21" LCD Monitor (Samsung)
Power Supply Cooler Master 850W Silent Pro.
HDD 3 x 1TB internal + 3 x 500 GB external.
Saitek X52 Pro with Saitek Pro Rudder Pedals
Natural Point Track IR 5

Thank you for taking so much of your time to get this sorted out.

Regards,

Mickey

[CocnutAir]

Same version of Windows I used. You have correct version of Phidget driver.

[CocnutAir]

Soluto is Israeli freeware that uses a downloaded agent to transmit data to and from Soluto’s back-end servers.
In addition, it takes action on the local computer.
FS2Phidget interacts with two other apps i.e. Wideclient-FSUIPC and Phidget manager.
Phidgets interacts thru an API with both client app and hardware.
There is a lot of process-to-process comms going on.
Wonder if Soluto isn't seeing this interaction as a problem.
i.e. your environment is now outside Soluto's design parameters.
Wonder how Soluto monitors and takes action on processes without disrupting a process.
Soluto has detailed reporting tools.
Could you post Soluto's crash report.

[Mickey_Techy]

.......Looking at your log I see one major difference.
When software requests number of components on LED-64 from the Phidget Manager, the number 2 is being returned.
On my system that number is 64...........

That is consistent with what I'm saying.

Please refer my findings at post # 8 above. I'm attaching a picture again.

http://i842.photobucket.com/albums/zz345/AviaScorp/FS2Phidgets/09a87eca-a501-479f-83f0-e0e6b07f9a34.jpg (http://s842.photobucket.com/user/AviaScorp/media/FS2Phidgets/09a87eca-a501-479f-83f0-e0e6b07f9a34.jpg.html)

Could this be due to the fact that I'm using a custom 'FSVariables file' and this file has only two pin assignments?

[Mickey_Techy]

..............Soluto has detailed reporting tools.
Could you post Soluto's crash report.

This is the only information that the reporting tool provides me,

".......................
This is a rare crash and we don't yet have complete statistics on it.
You may even be the first Soluto user to have this crash... :)..............................."

Did you say, Israeli..download agent...backend servers....., oh man.
This application is gone, before you post again.

[CocnutAir]

FsVariable file will have no affect on this problem. The number of components on a Phidget card is obtained by talking to the Phidget API. In object programming terms is a property of the Phidget LED-64 object. Program first determines how many components (not strictly pins) a card has, then looks to see if there are any saved settings for each component. Some of those saved settings might be for an FsVariable. At which point program attempts to read the appropriate FsVariable file. If the settings files are not located, either for hardware or FsVariable, then the component is disabled. This is also for safety reasons. Phidget might be driving huge hydraulic actuator. Local newspaper headline: Man Beaten to Death by Flight Simulator. Freeware Provider Supporting Widow and Children.

[BenHuur]

Hello!


I have exactly the same problem :
I am using a Phidget LED-64 board andFS2Phidget 4.3.86.
Everything work fine with the emulator,and when I connect the board, FS2Phidget sees it but I don't have thecomponent list :
8291


Mickey_Techy, did you manage yourproblem?

I use : Win7, Prepar3D, FSUIPC4, FS2Phidget 4.3.86, Phidget LED 64 Advanced

Thank you in advance

Ben

[Mickey_Techy]

.........Mickey_Techy, did you manage your problem?.........

Hi Ben,

Can't say that I was able to 'manage' my problem. Coconut Air was very helpful with his support, though he wasn't keeping too well at that time. But despite his best efforts to help me out, I wasn't able to use FS2P as it's designed. Guess, some computers are built in strange ways, and mine is probably one.

FS2P Version 4.3.86 is not fully compatible the current build 21 of Phidget libraries (hence the yellow highlight in the picture you posted above). I remember, Allan had updated 4.3.86 to a newer version, or maybe it was a 'fix' specifically for me.

However, I had continued to have issues with the newer (fixed) version of FS2P also.
Having said that, I had also tried to manually write the FSVariable.ini file, and had managed to successfully test AoA lights (drive 3 LEDs) on the VRS Superbug (http://aviascorpmusing.blogspot.in/2013/05/aoa-indexer.html).

But, largely due to various issues I had configuring this board, I have left this board alone for the time being.

Wish I was of more help to you, but that's all I got at the moment. You could send a PM to Allan and see if he is still around to help?

Am shortly planning to re-commence my pit build, and am happy to share whatever "tweaks" I resort to, to make this board work.

[BenHuur]

Thank you for your quick response.
I will see what I can do...

[hrnet940]

This is what I have so far. Just plugged my Phidget LED64 Advanced in and starting to figure it out and get it working. Am I an the correct path? I learn quick just need some help to get going. Eventually this will be used with my VRS F/A-18E Super Bug, but would like to get it working with something and chose a Sludge hornet for starters.

Wayne http://www.mycockpit.org/forums/attachment.php?attachmentid=12904&stc=1