CAVUJIM

That was my thinking. The # 9 pin is pulled from the null modem adapter but I think #9 is input and they don't want input to input. I'll try to find a RS232 tester. I also have a USB Bluetooth adapter. I'll give that a try too. It would be nice not to have any wires.

The description of the \\\USB... settings wasn't totally clear so I gave it a shot to see if it would work. Apparently it only works with a USB to USB connection. FS9 PC has the regualr serial com port (I assume COM2 because COM1 is the PFC). The pen tablet has the USB port. When I installed the USB driver on the pen tablet, it assigned COM5. I see no activity (using PortMon) on the Pen Tablet.

There are 2 reported com ports and com1 is used for PFC sio I assume the other 9 pin port on the pc is com2. Could be the port doesn't work. Yes, I have a serial to usb adapter. Jim

I have newest version of FS9 update, GPSout, PFC and fsuipc installed. I have LS800 pen tablet with moving map and only USB connectors. So i hooked up serial to USB adapter with null modem . Portmon on FS machine show plenty of activity to com2. INI set to Com2 and 4800. Portmon on pen tablet shows no activity. Should I see activity on the port using portmon on the receiving PC. USB shows as com5 on pen tablet. Installed with manufacturers CD. I also tried changing port speeds and changing com2 to \\\WCEUSBSH001 I also tested cable and that seems OK though the #9 pin is removed on the null modem adapter. Any ideas.

Typing Dir>>Com2 from a command prompt sends data to the port and it shows up within Portmon. On my latest tests, I did not bother to hook up moving map laptop to FS9 computer. I assume it doesn't matter on a serial port. Here is the entire ini file that I extacted directly into the modles folder. I downloaded the GPSout last week. I do have ActiveSky installed. Besides FSUIPC v3.07 and PFC.dll (both downloaded 12/2003), I have no other modules installed. ; GPSout version 2.41 by Pete Dowson 31st October 2001 ; email: pete@millhays.demon.co.uk ; ====================================================== [GPSout] Sentences=RMC,GPRMZ ; This parameter selects the NMEA standard sentences to be sent by the ; GPSout module. Currently the following are supported: ; ; RMC -- best for FliteMap, provides course and ground speed, but no altitude ; RMA -- similar ; PGRMZ -- Garmin NMEA 0183 extension for Altitude only: use with RMC ; GLL -- used by Microsoft Autoroute 2001 but GGA works better ; VTG -- usually used with GLL to provide course and ground speed data ; GGA -- also works with FliteMap and others, and provides altitude, ; but not course and speed. Some need this for the number of satellites. ; GSA -- provides no useful information from GPSout, but appears to be needed ; by some applications (such as "Anywhere") in order for it to be ; able to use the altitude in the GGA sentence. ; ; To send more than one merely list them here separated by commas, with ; no spaces. For example: ; ; Sentences=RMA,RMC,GLL,GGA ; ; will make GPSout send these four formats every time (not very efficient, ; but useful to determine whether the target program supports any of these). ; ; GPSout has only been thoroughly tested only with FliteMap. With version ; 7 of that program, in the LORAN/Gps connection, select "NMEA 0183 RMC ; (9600)", or find a Garmin NMEA setting. Then the default settings in this ; .ini file should work okay (but possibly the Garmin setting will need ; the Speed setting to 4800) -- excepting for the Port which you'll need ; to set yourself (the default is COM2). ; ; In version 8 of Flitemap there are far more options, under "Connections- ; External Device Setup". Those I now find work best are the Garmin NMEA ; settings. All the values are recognised if you send RMC and PGRMZ ; sentences, or RMC, GGA and GSA, and you can choose a really decent ; speed like 19200 as well. Interval=1500 ; This specifies the interval, in milliseconds, at which the GPS message ; is to be sent. The minimum is 100 msecs, but bear in mind that the ; serial port is being asked to send around 65 characters at each interval. ; At the default port speed of 9600, this requires about 70 milliseconds ; in any case. The default interval of 1000 seems good for most purposes. ; I currently use 1500, as shown here. Port=COM2 ; The port to be used on the FS98/2K PC. Speed=9600 ; The speed to use. This must, of course, match the speed expected by the ; moving map program. most GPS's output at 4800 or 9600. Recent versions ; of FliteMap support 19200. Use the highest speed you can, for efficiency.

Trying to get GPS output to moving map program on laptop. I have FS9 running on XP machine with PFC Cirrus running off Com1 (works fine). I moved GPSout files into module folder (no changes to ini file). Placed serial cable (extension cable with null modem adapter) to remaining 9 pin serial port and connected to a moving map software program on laptop (Voyageur). I set the moving map to autodetect GPS signal ( I also tried forcing to Com1 on laptop). Started both programs up and PortMon on PC . I see no activitiy on PortMon at all. Shouldn't there be some activity for the PFC stuff? I looked in System > hardware and see the Com2 port and it does not report any problem. COM2 is set within the GPSout.ini file I tested the cable and the 2-3 connections are reversed but the 1 pin is jumpered to the 6 pin and feeds to the 4 pin on the other end. Pin 4 feeds to both 1 and 6. Without the null adapter its a straight through connection. I ran Dir>>Com2 from command prompt and I do see activity within Portmon then. Any ideas what I'm doing wrong?

Thanks for responding. I thought it was pretty obvious that I had been though the entire INI file. The default by the way is Com2. Someone who uses the same moving map as me said it works fine on the default settings, so I didn't change any. The problem seems to be in FS actually transmitting the data to the port, see my previous messages.

in cmd mode. Typed Dir>>com2 and saw activity to com2, so the port works, Why does FS not generate GPS output?

Portmon working,pfc activity continuous, but still no GPS. I have activeradar installed. Does that interfer?

Trying to get GPS output to moving map program on laptop. I have FS9 running on XP machine with PFC Cirrus running off Com1 (works fine). I moved GPSout files into module folder (no changes to ini file). Placed serial cable (extension cable with null modem adapter) to remaining 9 pin serial port and connected to a moving map software program on laptop (Voyageur). I set the moving map to autodetect GPS signal ( I also tried forcing to Com1 on laptop). Started both programs up and PortMon on PC . I see no activitiy on PortMon at all. Shouldn't there be some activity for the PFC stuff? I looked in System > hardware and see the Com2 port and it does not report any problem. I tested the cable and the 2-3 connections are reversed but the 1 pin is jumpered to the 6 pin and feeds to the 4 pin on the other end. Pin 4 feeds to both 1 and 6. Without the null adapter its a straight through connection. Any ideas what I'm doing wrong?

I have all the newest PFC and FSUIPC dlls installed. I am not using the FSUIPC to control the Heading bug with the RIC. The bug turns much slower than the altimeter setting within the kollsman window when turning the corresponding knobs at the same rate. The heading bug will sit on one setting for a few seconds while turning the heading bug knob on the RIC. It was never this slow before and was wondering if you could give me some ideas on what to check. JIm

I have not yet installed 3.3 which I will do tonight. I'll remove FSUIPC references to DG bug. I'll let you know how that works.

Calm down Pete. My message wasn't that difficult to interpret. I had an older version of FSUIPC (perhaps 3.0) then I updated to the newer version 3.22 and the newest vrsion of PFC.dll on the pFC website. It was at this time that the heading bug seemed to "slow down" When I spin the knob on the RIC, even very slowly, the heading bug seems to be not responding or responds very slowly. I tried to correct by using the buttn assignment within FSUIPC (tried using "rapid increase" and "regular increase"). This doesn't give the added response either. Rapid increase seems to jump the bug around. Is there any meaning to the parameter setting within FSUIPC for this function? I have downloaded the 3.3 version of FSUIPC and will load, but I doubt this will have any effect as the function used to work fine.

Actually I turning the knob unrealistical slow and it still doesn't keep up. Changed after installing FSUIPC. The PFC.dll (i believe the most current one I have is 1.90) is installed. I'd be glad to install newest one but older combination worked fine. Jim

I have FSUIPC 3.22 installed and using PFC remote console on avionic stack. The heading bug does not seem to spin (actually it doesn't keep up) when I spin the heading bug knob. I tried using FSUIPC to control it and that doesn't seem to do any better even I use Heading Bug Increase Rapid in both positions (press and release) Is this a polling problem? How do I correct this?