E

NTP Diagnostics and Debugging

After confirming functionality of NTP using synchronous packets, you can remove fudge flag2 from the configuration file and restart NTPD in debug mode to observe event polling receive events.

E.2.5 Incorrect Port and Bad Data

If the Acutime NTP driver detects invalid packet data on the serial line, it generates debug messages similar to the following. Run NTP in a higher level debug mode to observe this message: ntpd -d-d

clock GPS_Palisade(1) event 'clk_badformat' (0x02) TSIP_decode: unit 1: bad packet 6d-4d event 0 len 21 clock GPS_Palisade(1) event 'clk_badformat' (0x02) TSIP_decode: unit 1: bad packet 82-02 event 0 len 1 clock GPS_Palisade(1) event 'clk_badformat' (0x02) TSIP_decode: unit 1: bad packet 46-00 event 0 len 2 clock GPS_Palisade(1) event 'clk_badformat' (0x02) TSIP_decode: unit 1: bad packet 4b-5b event 0 len 3 clock GPS_Palisade(1) event 'clk_badformat' (0x02) TSIP_decode: unit 1: bad packet 54-48 event 0 len 12

Table E-2 shows troubleshooting options.

Table E-2 Troubleshooting: Incorrect Port and Bad Data

Possible Problem

Solution

The host is connected to the wrong

Connect Acutime Port A to the host

Acutime port. NTP requires connection

serial port.

with Acutime Port A.

 

 

 

The Acutime Port A serial port

Verify Acutime Baud Rate, Parity, Start

configuration does not match the NTP

and Stop Bits and Protocol settings.

configuration.

 

Acutime 2000 Synchronization Kit User Guide

E-15

Page 281
Image 281
Trimble Outdoors AcutimeTM2000 Synchronization Kit, Part Number 45005-00-ENG manual Incorrect Port and Bad Data