NavCom Sapphire Rev.J - Manual (Page 38)

Sapphire Technical Reference Manual Rev. J
38
[PORT] accepts up to five arguments:
1. The port identifier: An integer from 1 to 4. If this argument is not specified, the port is
assumed to be the one receiving the command.
2. The baud rate (1200,2400,4800,9600,19200,38400,57600,115200)
3. The number of data bits per frame (7 or 8)
4. The number of stop bits per frame (1 or 2)
5. The parity option for each frame (NONE, ODD, EVEN)
Table 4: Examples of Multiple Argument Command Inputs and Responses
Input Response* Description
[PORT] 1,19200 [OK] PORT
Command accepted. Last 3
arguments left off.
[PORT] 1,19200,,,NONE [OK] PORT
Command accepted.
Arguments 3 and 4 not
specified as indicated by
commas.
[PORT] 1 4800 8 1 NONE [OK] PORT
Command accepted. (Note
use of spaces as argument
delimiters.)
[PORT] 2,9600,9
[??] PORT,argument #3 out of
range Command not accepted.
Problem with third argument.
[PORT]
[PORT]
1,4800,8,1,NONE
No arguments specified so
receiver reports current
value(s) for port receiving
command.
[PORT] 2
[PORT]
2,9600,9,1,NONE
Only port argument specified
so receiver reports current
value(s) for specified port.

* Command responses must be enabled to receive responses (verbose mode).

= carriage return + line feed
Sapphire Output Messages
The Sapphire GNSS receiver supports a number of different types of output messages (data
output streams). Some of these are industry standard outputs such as NMEA-0183 sentences
and various RTK/dGPS correction formats (RTCM, CMR, etc.). This section, however,
describes the format of specialized Sapphire output messages designed to provide access to
commonly used internal receiver data (measurements, ephemeris, channel status, etc.), as well
as efficient, low latency outputs of the navigation results.