DOC 6501_Release V
ATS-6501 Users Guide
118
Note:
Changes were made to the USB Adapter cable programming between versions 3.6.3 and
3.7.2 once the ATS-6511 came on line. If you are experiencing issues after upgrading the system
software perform the following:
A.
Remove any 94000-115200 and 94001-5071A cables from the rear of the unit. If they
were installed in the system power-cycle the system. Allow the system to come back up
before proceeding.
B.
Telnet into the system.
telnet ip addr
C.
Log into the system (user = tsc, password = tsc)
D.
Use the command
flashftdi_6501.sh
. You should see:
Programming FTDI devices on the ATS-6501
---- success ----
E.
Power down the ATS-6501.
F.
Insert the desired USB Adapter Cables
G.
Power up the ATS-6501.
6.3.3 External Reference Adapter (
94001-5071A)
•
USB to Serial adapter the improper type (94001-5071A)
•
Incorrect serial cable type (requires Null Modem cable.)
•
Communication settings on the reference device are incorrect.
o
Refer to the manual and set the system to 9600,N,8,1.
Note:
Communications are only used when the external frequency reference is a hp5071A. If
you are using a different cesium clock use the
reference_type cesium
command to set the proper
reference clock type. This also applies when using the 5071A and the ATS-6501 will not be
communicating with the clock.
6.4 Syslog Command
All system error messages can be listed using the
syslog
command on the command port. The
following information is typically contained in this log during startup. The date/time will be set
to Jan 1 00:00:00 when the system is first powered on or rebooted since the time is not set until
the GPS receiver is tracking.
ATS-6501>syslog
Jan 1 00:01:21 tflex newsyslog[411]: logfile first created
Jan 1 00:01:22 tflex syslogd: restart
… (These messages pertain to the system boot/application start up process
Jan 1 00:03:25 tflex tflex[536]: .017 0x0060eb00 [GPS] Tracking
Jan 1 00:03:33 tflex tflex[536]: .005 0x0060e900 [GpsHardware] Setting system clock to 2010-06-15-13:30:52
Jun 15 13:30:52 tflex tflex[536]: .001 0x0060e900 [Tsc4370] Sending time 2010-06-15-13:30:52 to the FPGA
Jun 15 13:30:52 tflex tflex[536]: .007 0x0060e900 [GPSLogging] Starting GPS user logs
Jun 15 13:30:52 tflex tflex[536]: .048 0x0060e900 [KAS2] System time is valid, starting KAS2 processing
Jun 15 13:30:52 tflex tflex[536]: .052 0x00643d00 [Engine] Thread Log::Manager starts
Jun 15 13:30:52 tflex tflex[536]: .319 0x0060e900 [KAS2] Reference is locked and system time is valid, starting KAS2 processing
Jun 15 13:30:52 tflex tflex[536]: .317 0x00678100 [Engine] Thread ensemble starts
Jun 15 13:30:54 tflex tflex[536]: .064 0x00587f00 [Ntp] Starting NTPD
Error Logs:
After startup the system tracks all events and alarm conditions (asserted) and when
those alarms cleared (cleared) as they occurred in chronological order.
Jun 15 13:30:55 tflex tflex[536]: .350 0x00587f00 NtpPipeWriter: change in leap second info, mLeapCurr now 24 was 0, mLeapPend now 0
was 0
Jun 15 13:30:55 tflex ntpd[555]: ntpd 4.2.0-a Fri Jun 11 16:51:53 UTC 2010 (1)
Jun 15 13:30:55 tflex ntpd[555]: precision = 84.267 usec
Jun 15 13:30:55 tflex ntpd[555]: no IPv6 interfaces found
Jun 15 13:30:55 tflex ntpd[555]: kernel time sync status 2040