dboll

You're right, I would know what I'm doing in the plane, but we're trying to programmatically determine the state of the current flight to adjust visual displays to the state of the flight (taxi, etc.). Anyway, thanks for your prompt answer. P.S. - I saw mention of your cataract surgery. Good luck to you. I too had both eyes done, in 2001 (also two months apart). I've had fantastic results. Of course there are the inevitable optical artifacts to get used to (e.g. halos, glints, etc., which I don't even notice anymore). I was fortunate enough to get what they called multi-focal lenses, somewhat like a fresnel lense where there are concentric beveled surfaces on the lense allowing near and far focus, though I still need reading glasses for computer work. Anyway, good luck to you and give them time to adjust.

Does the AI Traffic Data (for TCAS apps, etc.) from offsets 0xD000-0xFFFF include data for the aircraft being flown in the simulation? I see that it contains data for vicinity traffic, but I don't see the actual plane I'm flying in the data. Do the tables have an entry for the current aircraft, or is there some other way to obtain this data (specifically bState) from FSUIPC? Thanks.

Yes, portmon in fact does show that GPSout is sending data to that com port. So I've somehow got a problem in how I'm reading the port so I'll have to go chase that down. Thanks very much for your help and for a useful product.

Well, I'm actually writing the software that reads the NMEA sentences (it already reads the NMEA sentence stream from a number of GPS devices). It just doesn't seem to be sending any data, by any number of measures. I'm assuming it's something in configuration. I know that GPSout.dll is at least running because it takes over the designated com port. The docs for FSUIPC.dll it seem to indicate that it might be needed for GPSout. Is there any such dependency? I guess I just want to verify without a doubt that GPSout is producing the data, then I can work on getting it and processing it properly. Thanks for your quick responses.

I've verified that I'm using a null modem cable. My GPSout.ini file specifies the following (the defaults): [GPSout] Sentences=RMC,GGA,GSA Interval=1500 Port=COM2 Speed=4800 This machine has two serial ports. I just have the null modem cable going from the COM2 port to the COM1 port. All I'm doing to see what comes from GPSout is using the "type" command in a command window (this is on win2k): c:\> type com1: With the same cable setup, if I send data to com2 using the "type" command ( as in c:\> type x.txt > com2:), then the data shows up at the com1 port (com settings for both ports set correctly). Does GPSout set all the com port settings in the DCB (using SetCommState)? Thanks.

I know from reading the other posts in this forum that this should work (I'm using GPSout v2.52 with FS2k4), and I know the settings are trivial (yes, the GPSout.ini file is pointing to the intended com port and the baud rate matches the baud rate which the "reader" is expecting), but when I run flight sim, I see no data coming from the designated com port. Could it be mismatched values for other com port settings, such as parity (even), data bits (7), stop bits (1)? What values for these settings does GPSout use? Thanks.