Jump to content
The simFlight Network Forums

Stingray160

Members
  • Posts

    7
  • Joined

  • Last visited

Stingray160's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. This is in the WideFS User Guide: GPSout relay facility WideClient will now receive GPS data from my GPSout module installed in the Server‘s FS (or, for FSX, from the GPSout option in a Registered FSUIPC4 installation). This data will simply be relayed to a local COM port. To do this you need set the serial port in GPSout to ―WideFS‖. Then, in the appropriate client‘s WideClient INI file add this section: [GPSout] Port=COMn Speed=n ... with, of course, the correct Port and Speed for the local connection. Note that you can use the freeware Virtual Serial Port program ―MixW ComEmul‖ (provided in the GPSout package for FS2004 or before, or downloadable from the Support Forum). This way you do not actually need any real COM ports to support a moving map program on the Client PC. If fact you can now use them on a Network with no actual serial cables involved. You can have the same GPSout data being used on any of your client PCs. It is not restricted to one recipient. For more details about GPSout please see the GPSout package or FSUIPC4 documentation. I used that guide to set up my systems Just adding; When you set up MixW ComEmul make sure you use one of the two pairs in each program. ie, if the virtual pair you created was com8 and com9, use com8 on the [GPSout] Port=com8 and com9 in the program (Moving map) that is accepting the GPSout signal. Most computer nuts probably know this, I am not computer illiterate but I did not understand the virtual thing. I had a hard time understanding what it was they wanted me to do in setting up the ports to begin with. Even a sentence on "MixW uses a pair to communicate with each computer. One com sends and the other receives." The second part of the pair is the one that is your com port in the moving map program. Just a little more help for the not so well informed, Dan
  2. Pete I finally got a chance to try it out. The problem was just the 51 com I did not understand how that part of it worked. That is all I meant about the documentation. Everything else was explained very well. If I would have just put the right com in the moving map program it would have worked. Just a small sentence in your text file would help new users. Everything is working great. It is nice to be able to practice with my EFB that I use in the plane. I will tell others about this because it is a valuable resource for practicing with your moving map that you use in the plane. Thanks for all your help Dan
  3. I totally appreciate that it is free, I hope I am not coming off as being a bother. The other two programs I bought from you worked just fine. I appreciate the help that you are giving me. It is easier for someone that knows what they are doing to see a mistake than someone who does not. Again thanks for your help, I did try and support you by registering both programs. Dan
  4. From my post above; Speed= Do I leave this blank or fill it in. ; 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 and higher. Use the highest speed you can, ; for efficiency, especially if you enable several sentences. ; ; The speed parameter is not used if the Port is set to "WideFS". You ; set both the port and the speed in the WideClient.INI file's [GPSout] ; section. I set up the port pair to 50 and 51. Non of the documentation explanes this very well. Now I am just begining to see I think. Use 50 in the GPSout ini and use 51 as the port to connect to in the program. Dan
  5. I took the space out. I used 50 because it said not to use one that was already being used. I figured 50 was a safe bet. It came up in the program as a valid port to select so maybe without the space it will work. I also looked back at the GPSout config and see that the speed is not supposed to be used I corrected that I think I just left out the number. I will try it later tonight. Thanks for the help Dan ; GPSout version 2.60 by Pete Dowson 20th September 2005 ; ====================================================== [GPSout] Sentences=RMC,PGRMZ ; 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 ; 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. ; GSV -- similarly, nothing useful from GPSout but fixed satellite data for some ; programs which seem to need it. ; ; 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). ; ; Additionally GSPout supports the "Series 400 Aviation" format, which is ; used by some real GPS units to allow input from aircraft devices. To select ; this set ; ; Sentences=AV400. ; ; You will not normally mix this with NMEA formats, and AV400 usually works ; at a speed of 9600 whereas NMEA standard is 4800. ; ; GPSout has only been thoroughly tested 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=1000 ; 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=wideFS ; The port to be used on the FS98/2K PC. If you want to send the data ; across a Network via WideFs, set this to "Port=WideFS". You will ; need WideFS version 6.50 or later. ; A freeware virtual port program, from Mix-W (to whom thanks) is ; included in this ZIP to complement the WideFS facility. Using this ; you can link the WideClient output to your mapping program's serial ; port input via two "virtual" serial ports. No cables needed! Speed= ; 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 and higher. Use the highest speed you can, ; for efficiency, especially if you enable several sentences. ; ; The speed parameter is not used if the Port is set to "WideFS". You ; set both the port and the speed in the WideClient.INI file's [GPSout] ; section. PosTo6Decimal=Yes ; GPSout now gives the Latitude and Longitude to 6 fractional decimal ; places instead of 4 as specified in the NMEA documents. This seems to ; do no harm, but if it does give you any problems, try changing this ; parameter to "No".
  6. This is the WideClient config: [Config] Port=8002 Window=1,129,798,436 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ServerName=personal-video [GPSout] Port=COM 50 Speed=9600 The server is set to port=WideFS I got course planner to work. So I know that something is being sent from FS to the other computer. CoursePlanner is a module in FS and on the other computer so that might not count. Dan
  7. I just bought WideFS and FSUIPC I have GPSout installed I also downloaded Courseplanner 3.D.4. I have a Motion laptop that I also have all of the above loaded on to. On the lap top I have a moving map software that I use in my real plane, Chartcase Pro. I want to use Chartcase with FS 2004, I got WideFS working along with FSUIPC along with MixW. I see the port in the program and configured it. Both computers are talking to each other with FS 2004 running. I do not get any GPS signal from FS 2004 to Chartcase. I have used all of the "RMC, RMA, PGRMZ, GLL, VTG, GGA, GSA, GSV. I also downloaded Lawrance demo 2000 but I do not know how to tell it to see the port from the other computer. Courseplanner is working but it cannot see the program folder on the FS 2004 machine. I cannot get any GPS software to see the GPS signal from FS 2004. Is there any program I can use to make sure that I have a signal from the FS 2004 machine? By the way this is running wireless over a network. Dan
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.