For easy identifying the object in e.g. the Object Explorer.

This is an optional field and can be left blank.

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: " ___° __._____' _".

The values for these fields are taken form the Object Control Center and can be dynamically adjusted when this object is at the foreground and visible.

Note that the Course can also be influenced with the Rudder Control.

UTC Date and Time as this appears in the appropriate NMEA data.

The user can either choose for the  "real" and actual UTC, or can choose to take a faked UTC.

In the latter case the UTC can be manually manipulated.

The method to be used is determined by a setting in the General Settings, NMEA tab.

Dilution Of Precision values, Geoidal Separation and number of satellites in view to be embedded in GGA and GSA data.

Note that these can dynamically be adjusted while the object is running!

To be used in the GSA sentence. For standard GPS, select satellite number 1 to 32, for WAAS select satellite numbers 33 to 64.

Here you enter the Magnetic Variation for the RMC sentence. Select Easterly or Westerly variation by clicking E resp. W.

Initially the value is taken from the General Settings. Mind that this setting is also used in the Heading instrument.

Set here the GPS fix quality for the GGA sentence.

Either select "Normal", "Auto" or "Navigate".

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 NemaStudio will automatically follow in Auto or Navigate mode.

In Auto and Navigate mode some new controls are enbled:

(Note: Rhumb, XTE, VMG and Steer only relevant in Navigate mode)

Ticking the Track Back checkbox will force NemaStudio to sail the route backwards when it has arrived at the last waypoint.

Ticking the Loop checkbox will force NemaStudio to restart the route from the beginning when it has arrived at the last waypoint.

Auto mode

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:

$GPWPL,5126.253,N,00334.389,E,1-121021*54

$GPWPL,5125.000,N,00333.283,E,2-121025*55

$GPWPL,5124.925,N,00327.862,E,3-121027*54

$GPWPL,5123.610,N,00323.304,E,4-121031*55

$GPWPL,5122.306,N,00311.994,E,5-121043*50

$GPWPL,5121.742,N,00311.544,E,6-121104*57

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 NemaStudio'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.

Navigate mode

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. Also shown are the rhumbline from the current waypoint to the next waypoint and the VMG (Velocity Made Good), inserted as the "Destination Closing Velocity" field in the RMB sentence.

Note that in Navigate mode the XTE and RMB sentences also are enabled and can be selected for output.

Slave (of GPS1) mode

This option is greyed out in GPS1. For all other GPS's select this mode when you want to simulate two or more GPS's on the same vessel. In this mode you can set all parameters, like sentences, fix quality, satellites, port etc, but Position, Altitude, Course, Speed and Rudder are taken from GPS1. Of course GPS1 should be running when using this mode.

Here you select the sentences you want NemaStudio to output for this instrument and the Identifier, normally $GP but can also be changed to a proprietary ID.

For most sentences you can also select the desired mode indicator. For GLL, RMC, VTG, XTE and RMB the meaning of the Mode Indicator is, according to the NMEA 0183 specifications, as follows:

A = Autonomous mode

D = Differential mode

E = Estimated (DR) mode

M = Manual Input mode

S = Simulator mode

N = Data not valid

P = Precision (RMC sentence)

For the GGA sentence in NMEA 0183 version 2.30 and 3.01 (General Settings, NMEA settings tab) the GPS Fix Quality can be set as follows:

0 = invalid

1 = GPS fix (SPS)

2 = DGPS fix

3 = PPS fix

4 = Real Time Kinematic

5 = Float RTK

6 = estimated (dead reckoning) (2.3 feature)

7 = Manual input mode

8 = Simulation mode

Checking the "Add checksum" does exactly what it suggests.

The Status parameter can be set to Valid (A) or Invalid (V).

Set the time in seconds NemaStudio must update the position coordinates for this GPS.

Note that this is a different value than the Transmit Interval.

Checking this option will add a valid checksum to each sentence