To start there must be a valid starting position represented by the latitude/longitude fields. When a new GPS is instantiated the Latitude and Longitude values are initiated within the range you have set in the General Settings. First time users may find the way of inputting data in these fields a bit awkward in the beginning, but once used to it you will appreciate the "error proof" entry!
Valid values should also be present in all Control Center fields.
After clicking the "Start" button the GPS simulation will start, and NMEA sentences will be sent to the selected output port of the PC, until the "Stop" button is pressed. Note that only those NMEA sentences will be sent that have been checked in the "NMEA sentences" panel. When the Transmit Interval is set to 0.0 the sentences are output as "single shot" each time you click the "Start" button.
All sentences are shown in the I/O Port Monitor as they are output. When logging is ON (toolbar option), the sentences will also be written to the user selected log file.
Clicking the "Stop" button will suspend the operation, until "Start" is clicked again. Clicking the little X top-right will exit the object and save optionally all current values, so that next time the instrument is used it can continue where it stopped. Note: saving is an optional setting in the General Settings.
A short description of each field follows below.
For easy identifying the object in e.g. the Object Explorer.
At creating a new GPS object, the Lat and Lon values are initially taken from the Program Settings. After starting the object, the coordinates are then dynamically updated every n second by calculating a new position from parameters like Velocity and Course, and embedded in the appropriate NMEA sentences before transmitting.
n is taken from the Position Update control (see below).
To change the value of either Latitude or Longitude the instrument must not be running.
To change: place the mouse cursor left of the leftmost digit. Then just start typing the new latitude or longitude, the cursor will advance automatically and the value will be automatically formatted. Example: 53° 21.56' N must be entered as 0532156000N.
After clearing, the fields will look like this: " ___° __._____' _".
Both Auto and Navigate mode force a dialog window to open, where you are asked to select a waypoint file. A valid waypoint file is a text file containing one $GPWPL sentence for each waypoint. A series of such waypoints is a route that NemaTalker will automatically follow in Auto or Navigate mode.
In Auto and Navigate mode some new controls are enbled:
(Note: XTE and Steer only relevant in Navigate mode)
Ticking the Track Back checkbox will force NemaTalker to sail the route backwards when it has arrived at the last waypoint.
Ticking the Loop checkbox will force NemaTalker to restart the route from the beginning when it has arrived at the last waypoint.
Select "Auto" if you want the simulator to run a predefined route taken from an input text file containing $GPWPL sentences. Such a file could look like this:
The checksum is not necessary. NemaTalker does not check it. You can obtain the file from a route planning program or create it manually with NemaTalker's built-in text editor. The most convenient way however is to use "Waypoint Creator", a free utility that can be downloaded from the Sailsoft website.
During the Auto mode session you can alter Altitude and Velocity with the controls in the Object Control Center, but not the Course, because bearing and range are automatically calculated by the program.
Opt for "Navigate" if you want to simulate the run of a predefined route, but want to remain in full control by using all controls in the Object Control Center. Observe the difference with the Auto mode: next to the bearing and range to the next waypoint, the simulator also shows the Cross Track Error (XTE) and the direction to steer to correct the error.
Note that in Navigate mode the XTE and RMB sentences also are enabled and can be selected for output.