NavCom Sapphire Rev.J - Manual (Page 169)

Sapphire Technical Reference Manual Rev. J
169
1.119 NTRIPCLIENT (ASCII)
SF-3050 Sapphire SF-3040
This command controls the behavior of the NTRIP client. If no keyword is specified, the current
status will be displayed.
Command:
[NTRIPCLIENT] {NONE} {CONNECT} {DISCONNECT} {SRCTBL} {NEWSRCTBL}
{DEBUG}
Parameter Definition
None Keyword that displays the NTRIP client status
Connect Keyword that connects to the caster mountpoint
Disconnect Keyword that disconnects from the caster mountpoint
SRCTBL
Keyword that retrieves the current source table
1
from the client and uploads it to the
user
NEWSRCTBL
Keyword that retrieves the updated source table from the caster and uploads it to the
user

1 The source table is the list that each NTRIP caster maintains of all of the NTRIP
servers (“sources” or “base stations”) that are connected to mountpoints on the
caster. Each entry in the table has details about the server, such as its location,
what type of corrections it sends, and what GPS receiver brand it uses. The source
table is not used by the receiver itself; it is only used by a user to select which
mountpoint to connect to. The source table in the receiver is always cleared at
power-on.

The NTRIP client and server cannot be active at the same time. An error message
will be displayed if any keyword other than a status request or DISCONNECT is
issued to one while the other is active.

NEWSRCTBL and SRCTBL can only be executed when the NTRIP client is idle
because the source table must be requested upon initial handshake with the caster.
The caster will then download the source table to the receiver and disconnect. If
the NTRIP client is not idle, an error message will be displayed.

NMEA messages may be scheduled for output on the NTRIP port (NP1). If they are
scheduled, they will be sent to the NTRIP server on the mountpoint to which the
client is connected.

Any message other than NMEAGGA on the NTRIP port should not be scheduled
since many casters may not handle them properly. Also, NMEAGGA should not be
scheduled any faster than 1Hz in order to avoid clouding the connection.

The client connection will timeout and disconnect if there is no data coming from
the receiver for either 30 seconds or 5 times the fastest stream rate, whichever is
bigger. This is determined dynamically on connection when the receiver asks for
the Source Table. If the correction stream is one message every 60 seconds, the
receiver will disconnect if no corrections are received for 300 seconds.