FS2Phidget doesn't populate index's for LED 64

[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' 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 (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.



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 :
Untitled.png


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/2...a-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.