Support
Evaluate FAQ and Helpful Tips
Q: What is Generic NMEA Interface?
A: Evaluate will function with any GPS receiver which supports the standard NMEA messages GGA, GSA, GSV and VTG. Evaluate also works with receivers that support any subset of these four NMEA messages. Evaluate will play back any ASCII data file with these NMEA messages, or any subset of these messages.
Q: How do I connect to a receiver?
A: Evaluate will automatically connect to a Magellan receiver through the RS232 serial port, and automatically turn on the Magellan POS and SAT messages when the Position and Satellite windows are opened. Evaluate can set the baud rate and protocol automatically for Magellan receivers. For non-Magellan receivers you must do the following:
- Set the correct Comm. Port, baud rate, and protocol.
- Select Manual Connect.
- Set up the receiver to transmit GGA, GSA, GSV and VTG (or as many of these as possible).
- From the Terminal window, verify that you are receiving the NMEA messages.
- Open the Position and Satellite windows.
Q: What is Analysis Mode?
A: The Analysis screen works with any Magellan receiver, and any receiver supporting the GGA message. It is used to determine the level of accuracy a receiver is capable over time or it can be used to average a position. A statistical analysis of position accuracy can be generated for either Truth Reference mode or Averaging mode.
Q: Why would I want to average my position over time?
A: A GPS receiver is subject to constantly changing errors of up to 10's of meters. However, these errors are generally centered about the true point. By allowing Evaluate to average the position over a period of time the point can be statistically generated. This is important for determining the base position so that accurate estimations of positioning capability can be made.
Q: How do I read data files?
A: To playback data from a file, use the Read Logfile mode to open the data file. Evaluate reserves certain file names for Magellan receivers. For these files Evaluate looks for Ashtech POS and SAT messages. For any other file named .LOG, Evaluate will look for the 4 NMEA messages GGA, GSA, GSV, VTG. Note that reserved Magellan filenames are: ADU2_xxx.LOG, G8___xxx.LOG, G12__xxx.LOG, GG24_xxx.LOG, SCA_xxx.LOG, SII_xxx.LOG, Z12__xxx.LOG.
Q: Can I log data?
A: Evaluate can log computed data from any receiver. For Magellan receivers the reserved filenames are used. For non-Magellan receivers the file names are: UNKN_xxx.LOG. xxx denotes numbers from 001 through 999.
Q: Can I download an almanac with Evaluate?
A: Evaluate will download almanacs from Magellan receivers and save them as either Magellan binary format (for use with other Magellan software) or YUMA standard format.
Q: Can I initialize the receiver from a file?
A: During initial connection to a Magellan receiver, Evaluate can automatically configure a receiver with user parameters from a simple list file of commands. These configuration files are called .GPS files. Several examples of .GPS files are included in the software to use as templates.
Q: Why does Evaluate show Heading, Pitch, Roll and Yaw?
A: These dials work only with the Magellan ADU attitude determination receivers. Note that COG (Course over Ground) is different from Heading. COG works with any Magellan receiver, and any receiver supporting VTG.
Q: Evaluate 5.0 isn't working with my ADU?
A: You will need to contact the Magellan Customer Support Group and have them send you the latest Evaluate version, or you can download it from the Customer Support FTP server.
Q: Can I use Evaluate software to help troubleshoot receiver problems?
A: Yes, Evaluate has an important feature, which allows users to generate a Support Ticket file. With a simple mouseclick, the receiver will perform a full receiver identification and parameter dump, writing all current user settings to a text file and invoking a short data logging session. The output data is also written to the ticket file, which can then be emailed to Magellan support staff for analysis. Many common user setup problems can be resolved quickly in this fashion.
![]()
