If you have GPS:

1. Navigate to the Web Interface and login with your credentials.

2. From the navigation menu, select Logs and click GPS Antenna Debug.

3. Select Enable Debug. Allow the debugger to run for atleast 1 minute.

4. Select Download Log to download the debug logs to your computer.

 If you have Radio:

1. Navigate to the Web Interface and login with your credentials.

2. From the navigation menu, select Logs and click Radio Antenna Debug.

3. Select Enable Debug. Allow the debugger to run for atleast 1 minute.

4. Select Download Log to download the debug logs to your computer.

GPS Debugging Information

When debugging, the following information should be printed on screen:

Jan 19 09:40:40 nts-6001 daemon.debug gpsclkd[820]: Received $GPRMC data 2016/1/19 09:40:40 UTC
Jan 19 09:40:40 nts-6001 daemon.debug gpsclkd[820]: Decoding NMEA string: $GPRMC,094040.000,A,5228.5990,N,00146.2345,W,0.00,,190116,,,A*6E
Jan 19 09:40:39 nts-6001 daemon.debug gpsclkd[820]: Received $GPRMC data 2016/1/19 09:40:39 UTC
Jan 19 09:40:39 nts-6001 daemon.debug gpsclkd[820]: Decoding NMEA string: $GPRMC,094039.000,A,5228.5990,N,00146.2345,W,0.00,,190116,,,A*60
Jan 19 09:40:38 nts-6001 daemon.debug gpsclkd[820]: Received $GPRMC data 2016/1/19 09:40:38 UTC
Jan 19 09:40:38 nts-6001 daemon.debug gpsclkd[820]: Decoding NMEA string: $GPRMC,094038.000,A,5228.5990,N,00146.2345,W,0.00,,190116,,,A*61
Jan 19 09:40:37 nts-6001 daemon.debug gpsclkd[820]: Received $GPRMC data 2016/1/19 09:40:37 UTC

Below is a breakdown of what each string means:

• $GPRMC - The string will always start with this.
• 094040 - This is the UTC timestamp in the string. In this case it is 09:40:40
• A - An A here indicates that the GPS antenna is synchronised to at least 3 satellites. If this is a V then the antenna does not have a lock on 3 satellites yet
• 5228.5990,N,00146.2345,W - These are your GPS coordinates and are not used by the timeserver
• 190116 - The current date. In this case it is the 19th January 2016.

If no information is printed to the screen this can indicate either a wiring issue or an antenna problem. If you receive garbled data then this would usually indicate a wiring issue.

If your $GPRMC string contains a V instead of an A then your antenna is not synchronised yet. It can take up to 48 hours to initially synchronise.

Once you have debugged your unit, it is recommended to disable debugging as it can introduce some latency to the GPS parsing.

Radio Debugging Information for MSF

When debugging using the Radio debug, the following information should be printed on the screen:

Jan 19 17:17:00 nts-6001 daemon.debug radioclkd[828]: Decoding MSF: 5111111111111111111112122111112122112121121222112122212232321 [60]
Jan 19 17:16:00 nts-6001 daemon.debug radioclkd[828]: Decoding MSF: 5111111111111111111112122111112122112121121222112122112232221 [60]
Jan 19 17:15:00 nts-6001 daemon.debug radioclkd[828]: Decoding MSF: 5111111111111111111112122111112122112121121222112121212232221 [60]
Jan 19 17:14:00 nts-6001 daemon.debug radioclkd[828]: Decoding MSF: 5111111111111111111112122111112122112121121222112121112232321 [60]

When debugging using the Radio Debugger, the above information should be printed on screen.

• Decoding MSF - Converting the MSF signal into a language that can be understood.
• 5 - If your device has a strong signal, it will always start with the number 5.
• 111222 - These numbers represent the pulse per second.
• [60] - The total number of pulses per second. 60 represents a valid signal for MSF. Anything less than 60 for MSF means that the signal is invalid.

If there is no pulse per second data printed to the screen then this can indicate either a wiring issue or an antenna problem. If you have less pulses per second then this can indicate poor signal strength in your area or interferance with the antenna.

Once you have debugged your unit, it is recommended to disable debugging as it can introduce some latency to the Radio parsing.