36
edits
Changes
Jump to navigation
Jump to search
Line 282:
Line 282: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 561:
Line 605: + + + + Line 567:
Line 615: − + Line 578:
Line 626: + + + Line 600:
Line 651: − + Line 666:
Line 717: + + + + + + + +
Update some GPS information for the RTCM/VOTER.
Enter Selection (1-9,99,c,x,q,r) :
Enter Selection (1-9,99,c,x,q,r) :
</pre>
</pre>
==Status Menu==
This is what a typical Status Menu looks like:
<pre>
S/W Version: 1.51 BEW 08/07/2017 Chuck
System Uptime: 19569.3 Secs
IP Address: 172.16.16.191
Netmask: 255.255.255.0
Gateway: 172.16.16.254
Primary DNS: 172.16.16.254
Secondary DNS: 0.0.0.0
DHCP: 0
VOTER Server IP: 172.16.16.164
VOTER Server UDP Port: 667
OUR UDP Port: 667
GPS Lock: 1
Connected: 1
COR: 0
EXT CTCSS IN: 0
PTT: 0
RSSI: 0
Current Samples / Sec.: 8000
Current Peak Audio Level: 58112
Squelch Noise Gain Value: 45, Diode Cal. Value: 56, SQL pot 621
Current Time: Mon Dec 07, 2020 02:15:25.120
Last Rx Pkt System time: 12/07/2020 02:05:32.340, diff: 592780 msec
Last Rx Pkt Timestamp time: 12/07/2020 02:05:32.340, diff: 0 msec
Last Rx Pkt index: 320, inbounds: 1
Press The Any Key (Enter) To Continue
</pre>
Something to note about the "Last Rx Pkt" status. This is the last received packet '''from the network''', not over the air. As such, on your satellite voter receivers that are receive-only, you will likely see something like:
<pre>
Last Rx Pkt System time: <System Time Not Set>, diff: 990080296 msec
Last Rx Pkt Timestamp time: <System Time Not Set>, diff: 0 msec
Last Rx Pkt index: 0, inbounds: 0
</pre>
The Last Rx Pkt System Time is the last time a packet was sent to this device to be transmitted (diff: is how many msec ago that was).
The Last Rx Pkt Timestamp Time is what the timestamp embedded in that last TX packet was, and the diff: is the difference between the packet timestamp, and the system time.
=Configuration Options=
=Configuration Options=
$GPRMC
$GPRMC
</pre>
</pre>
==TSIP Packets==
If you are using a Trimble GPS that speaks TSIP, it needs to automatically send out the 0x8F-AB and 0x8F-AC timing packets. Such devices include the Thunderbolt, Resolution T, etc.
It is not unusual for it to take up to 20 mins to get a GPS lock LED (ie. using a Trimble Thunderbolt) after any reboot.
It is not unusual for it to take up to 20 mins to get a GPS lock LED (ie. using a Trimble Thunderbolt) after any reboot. With the Trimble GPS', that is because it is waiting to complete the download of the almanac, and clear the status flags.
I found the debug setting of 32 useful in the RTCM, you can see a hex output of the GPS status.
I found the debug setting of 32 useful in the RTCM, you can see a hex output of the GPS status.
</pre>
</pre>
That has also been observed when trying to use a cheap "patch" antenna in a high RF site (lots of TV/FM transmitters nearby). Switching to a "proper" (commercial) GPS antenna that actually has filtering in it resolved the issue.
We have added a brute-force fix starting in RTCM/VOTER firmware >=1.51. This fix adds 619315200 seconds (1024 weeks) to the time reported by the GPS. It fixes the Thunderbolts, we have not done extensive testing to see how it affects other TSIP receivers.
We have added a brute-force fix starting in RTCM/VOTER firmware >=1.51. This fix adds 619315200 seconds (1024 weeks) to the time reported by the GPS. It fixes the Thunderbolts, it breaks other TSIP receivers (Resolution T). A better fix is being tested.
Make sure to save (99) and reboot (r) your VOTER/RTCM after making changes for them to be effective.
Make sure to save (99) and reboot (r) your VOTER/RTCM after making changes for them to be effective.
===PPS Issues===
If your VOTER/RTCM connects to your server, but it won't receive anything, check/toggle the PPS polarity, it may be incorrect.
===NMEA <--> TSIP Mode Change===
If you change from NMEA to TSIP (or vice versa), the VOTER/RTCM tries to be smart and change the baud rate for you. For TSIP, it sets it to 9600, and for NMEA it sets it to 4800. However, '''it also resets GPS and PPS polarity to 0'''! This WILL cause you confusion, if you are trying to find the right set of settings for your GPS. This will probably be removed in a future firmware version.