SEPTENTRIO PolaRx5TR, Reference Manual

Page: 160 / 512

3 Command Line Reference
3.2.9 Timing and Time Management
scst
gcst
setClockSyncThreshold
getClockSyncThreshold
Threshold StartupSync
ClockSteering
usec500
msec1
msec2
msec3
msec4
msec5
off
on
RxControl: Navigation > Receiver Operation > Timing
Use these commands to define/inquire the maximum allowed offset between the receiver
internal clock and the system time defined by the
setTimingSystem
command.
If the argument
ClockSteering
is selected, the receiver internal clock is continuously
steered to the system time to within a couple of nanoseconds. Clock steering accuracy is
dependent on the satellite visibility, and it is recommended to only enable it under open-sky
conditions.
If any other argument is selected, the internal clock is left free running. Synchronization with
the system time is done through regular millisecond clock jumps. More specifically, when
the receiver detects that the time offset is larger than
Threshold
, it initiates a clock jump of
an integer number of milliseconds to re-synchronise its internal clock with the system time.
These clock jumps have no influence on the generation of the xPPS pulses: the xPPS pulses
are always maintained within a few nanoseconds from the requested time, regardless of the
value of the
Threshold
argument.
The
StartupSync
argument can be used to force the receiver to start with a small clock bias
value (less than 100ns). This setting will only have effect at the next reset or reboot of the
receiver. So, when enabling startup synchronization (
StartupSync
set to
on
), do not forget
to save the configuration in the boot configuration file with the
exeCopyConfigFile
com-
mand.
This argument has no effect when clock steering is enabled or when a PPS IN signal is avail-
able.
Refer to section 2.3 for a more detailed description of the time keeping in your receiver.
Example
COM1> scst, msec1, on<CR>
$R: scst, msec1, on
ClockSyncThreshold, msec1, on
COM1>
160