Hi John, and everyone.
An easier way to get the FSX to work with Avare, in the article "Connecting to MS Flight Simulator" would be to switch step 2 instruction with step 3.
Exists:
2) Start FSX.
3) Start XConn and verify IP 192.168.0.6 and 49002.
Can be:
2) Start XConn and verify IP 192.168.0.6 and 49002.
3) Start FSX.
The reason for it being that there are some hidden steps, described in the XConn instructions but some may not know / read. They are that to get the XConn started, after you start FSX, you have to go in Window mode-Alt+Enter and start XConn. After some more testing I found that XConn will synchronize with FSX even if the FSX is running before XConn is started. It will basically save one step / confusion for some users. TVAn easier way to get the FSX to work with Avare, in the article "Connecting to MS Flight Simulator" would be to switch step 2 instruction with step 3.
Hi John and everyone.
>>I also added a note about checking here for the latest on getting older versions of MSFS working, because I'm not clear on whether or how that's been done.<<
At this time I do not have / know a solution for the MS FS9. I know that there is a way to connect FS9 (Fs2004) to the Serial RS232 deices by using an app called "GPSOut" and a free portion of FSUIPC, but no WIFI and or USB.
If we can scan the USB / hardware / wired port I may be able to get something to work. At one time I had Palm / Pocket PC running on wired USB with a moving map app. I do not think at this time we are scanning the Hardware USB in the External I/O app.? TV
Coming together is a beginning, staying together is progress, and working together is success. -Henry Ford
settings / attributes that have to be correct, Baud, Start/Stop, Bits, Flow control, Buffer settings, How Phrases are being handled, etc.
My impression is that USB may also be device-dependent. I've read that my 1st gen Nexus 7 has a crippled USB port because Google wants me to do everything in the cloud. Presumably most devices can be configured by an app to appear as a webcam or most any other USB device, but any instructions we create would need to address potential hardware limitations?
Part of the problem with getting Bluetooth to work with Avare External I/O may be in the SPP Galaxy Tab devices. It appears that there may be an additional security measure where some of the socket software does not take into account?
I get the "Failed! connecting socket" error and I cannot seem to get past it. Will try again later. TV