Running GPSout

[Stingray160]

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

[Pete Dowson]

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.

Is GPSout set to use WideFS? Is the WideClient in the client PC set to receive GPSout data?

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.

If you enable all of them at once you may need to make the frequency much more than the default 1 second or whatever it is, depending on the port speed you've set in the client and in your receiving program.

I also downloaded Lawrance demo 2000 but I do not know how to tell it to see the port from the other computer.

Sorry, I don't know that program either. But it won't be a "port from another computer", it will be one of the pair of virtual COM ports you created with MixW.

Courseplanner is working but it cannot see the program folder on the FS 2004 machine.

I've no idea what "courseplanner" is, but sharing files across a network is not a function of any of my software. You need to sort that out in Windows networking.

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.

WideClient on the Client PC will log the data if you ask it to. Set the Log parameter in the INI to read "Log=PartRX". It will log other stuff too.

Regards

Pete

[Stingray160]

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

[Pete Dowson]

This is the WideClient config:

[GPSout]

Port=COM 50

COM 50 isn't right -- there most certainly should be no space, so possibly COM50 would be correct, but 50 seems an awfully big number for a COM port. Normally MixW uses the next pair of COM port numbers available -- have you already got 49? What is the other number of the pair, the one you've set in the program to receive data? Where did you get '50' from?

Where's the WideClient log?

Pete

[Stingray160]

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".

[Pete Dowson]

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.

Erthat's one port of a pair. What is the other? What have you entered into the program which is supposed to be receiving the GPS data?

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.

Sorry, I don't understand the relevance of this? The speed parameter isn't relevant in the Server, that's all. But it is in the client of course, and needs to match whatever speed you set in the receiving program.

Can you not find the WideClient.Log file? It will be with the WideClient program, next to the WideClient.INI file, not on the Server.

Regards

Pete

[Stingray160]

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

[Pete Dowson]

From my post above;

Speed= Do I leave this blank or fill it in.

Since, as it clearly says, it isn't used, it matters not at all whether you put it in, take it out, or set it to read "mickey mouse". That's why it says "not used". The speed is irrelevant on the Network link.

I set up the port pair to 50 and 51.

Okay. And the program you are using accepts "COM51" and speed 9600 okay? Most programs I've used seem to be limited to COM1 to COM9.

Non of the documentation explanes this very well.

Sorry, but it is only a freebie which I originally wrote for my own use for a REAL COM port link. Use it that way with a null modem cable if you feel so bad about it. And MixW is not mine at all. There are easier programs to use, but you'll pay $1000 or more for them. MixW is okay for free.

Pete

[Stingray160]

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

[Pete Dowson]

I hope I am not coming off as being a bother.

No, not a problem.

So, what's the current state? With COM50 and COM51? Where's the WideClient.Log file I keep asking to see? Is there still a problem to resolve?

Regards

Pete

[Stingray160]

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

[Pete Dowson]

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.

Sorry, I still don't understand. What small sentence are you suggesting?

Regards

Pete

[Stingray160]

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

[Pete Dowson]

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.

Oh, I see. You didn't realise that serial ports are normally used with pieces of wire (though is does say this, no?), so the port at either end of the wire cannot be the same (you cannot actually physically plug two plugs into the one socket).

The "virtual" ports are simply emulating "real" ports, so the same applies.

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.

Hmm. Of course you could have the first of the pair in your map program and the second in WideClient. All MixW is doing is replacing a bit of wire between two real ports to save you having a bit of wire and two real ports. Doesn't the part about how to wire two PCs with a null modem cable imply this?

Maybe I should never have mentioned virtual ports, as this seems to be where you are getting lost. Real bits of wire and sockets wouldn't be so confusing, and you'd actually see them and plug them. We always used real stuff back in the years when PCs had at least two COM ports anyway.

I'll look at adding something next time I update anything in the package, but to be honest no such confusion has arisen in the many years this facility has been available. Maybe it is just that every one else has given up and not bothered to ask? I don't know. Thanks for the feedback, nonetheless. Duly noted.

Regards

Pete

[joemurffy]

First of all, Pete, you're awesome! I'm not a programmer, but I have been playing with your FS2004 stuff for awhile now (accidentally bought FSX stuff, also, so hope that helps); and I am very happy with everything that it's done. I'm not saying that I don't have to use some brain-power to get it to always do what I want it to, but that is part of the fun.

Dan,

I just registered on here and feel your pain. I did get FS2004 working flawlessly with my ChartCase Pro on my Samsung Q1 (over my wireless LAN) last year, but it took a couple nights to figure it out. What is especially frustrating was that when I spoke with some of the guys at FlightPrep about setting it up to use at shows they were very excited but never pursued it. I spoke to them at Oshkosh last year and they still didn't have it running. This could be huge for them for both demonstrating and as a safety of flight thing by allowing other customers to do just what we are doing - practicing with the program on the ground prior to getting into actual IMC! I was just going to send them copies of all of my config files, so it would have been easy for them. Oh, well.

I just moved back to Macintosh after eight years of PC's, and am very happy. I am about to get back into the entire "figuring it out thing" because I want to run X-Plane and am hoping that I will be able to do the same thing. Anyone know if X-Plane users can access VATSIM? I have also installed Windows onto a VMWare ESX setup, and will run FS2004 with that. The only problem that I'm having with that so far is that I had reconfigured a downloaded PA32 to look like my Cherokee Six's panel and had included Reality-XP instruments and a dual 530 setup, but it isn't working right yet. The fun never stops. I can always go back to the old machine for just flying, but it is now in the living room being beat up by the kids.

Dan, do you know of anyone else using ChartCase with their FS?

Joe