Winfast gps software

Home Support Download Center. Drivers Manual. Sub Category. Model Name. The seleted product :. Software License and Agreement. This is the diagnostics screen and it's best to be sitting on this when you try to connect.

If you don't see any legible data appear on screen when connected later , then you've got the wrong settings. Connecting to the GPS Receiver is hit and miss, trial and error until you find the correct settings. We said earlier we would use NMEA, so make sure this is selected, skipping to the baud rate, we know that NMEA prefers most of the time to use so we can set this easily.

If however you have a Compact Flash GPS Receiver , the easiest way is to cancel, eject the receiver, and then plug it back in again and it should pop up a dialog box and tell you what COM port it will use. With that said, we should now have all of the settings we need.

Tap the OK button. What should happen is that you'll be taken back the the Development screen in WinFast Navigator. You should see a screen like the one below left. If you don't, and you are seeing a screen like the one below right then you have the wrong settings. The data in the above left screenshot should start appearing within 5 seconds of reaching this screen. If it doesn't, go through the process again.

If you are sure you have the correct COM port, then all you need to do is change the baud rate. Like we said above, it really is a matter of trial and error. At this stage you can not break the receiver, all you are trying to do is connect to the device on the above settings, so don't worry if it doesn't work, it won't cause problems with other applications as you are not saving anything to the EPROM chip. At this stage if you have managed to successfully see the data coming through on the development screen and you have been experiencing problems with your GPS Receiver not working, then there is nothing wrong with the receiver, the problem is probably in the driver of the software you are using.

If you were experiencing problems and still are, with no data appearing on screen, then it could be either you still have the wrong settings, or the GPS Receiver is faulty.

We know that TTFF's can change, and do erratically. It all depends on whether you have clear line of sight to each satellite, and there are countless things that can delay the data, or the GPS program assumes data which may not be correct.

This will by default put you on the Initialize tab. In here you have options for resetting the GPS. If you didn't know, the GPS has two types of databases. The Almanac details what satellites are out there, and their projected positions in the sky, and this is usually current for a couple of months use. The Ephemeris data is more accurate data about signal strength, altitude and where they are exactly in the sky.

The Ephemeris data is only current really up to a couple of hours, after this time you have to download the complete Ephemeris data which takes 30 seconds under supreme conditions. Almanac data with Ephemeris will take around One way of testing a receiver in a cold state would be to acquire a 3D fix and then power it off for 4 hours, then test again and you should then have to re-download the Ephemeris data.

Another way is to foil the GPS into thinking it doesn't have it by wiping that data. This is what the options on this screen does. A Cold restart will lose all Ephemeris data, a Warm restart will lose a small segment of this data, and a hot start will lose virtually no data, and this will effectively simulate a GPS Receiver being powered off for a period of time. This is a harmless test, and you can time TTFF's yourself.

The one thing to bear in mind is you can initiate a cold start and it will come in say at 49 seconds, another cold start may come in at 36 seconds, a third cold start will come in at 53 secs. You'll see a picture forming here, no TTFF will ever be the same due to conditions and data. Cold TTFF's are what people are mainly concerned about, mainly because a Cold TTFF is what you'll see when you come home from work, power off the GPS Receiver, then power it on hours later in the next day when you go to leave for work.

Cold TTFF's are always what people complain about if it takes a long period of time. Now if you are receiving a TTFF of 2 mins plus, you either don't have a good sight of the sky, or you have a weak antenna, if you see TTFF's of mins, get a new receiver, it shouldn't take this long! Remember when you tap OK you'll be taken back to the Development screen. Okay, so you've been messing about a bit and you feel as though you're happy with all of the above, you can consistently get a connection with the GPS Receiver, and you're happy with it's output.

You want to start tweaking the GPS Receiver. Perhaps with the GPS Receiver you are using, you're getting the amount of satellites you have a lock on, but you're not seeing any signal strength in the GPS application you're using, or in WinFast Navigator? This is where we get technical. Under NMEA protocol you get different string types. All of these contain data like a database. A table of the current NMEA sentence codes are listed below and a description has been added.