User's Manual Part 2

RVP8 User’s Manual
April 2003
TTY Nonvolatile Setups (draft)
3–5
0x00400000 : Internal tests failed on some slave
0x00800000 : Trigger Generator RAM and addressing
0x01000000 : Excessive coax/fiber round trip jitter
0x02000000 : No sync found in round trip test
0x04000000 : Internal error in compile/link
Coax/Fiber/Pipeline Delay: 0.624 usec (Stdev: 0.014 usec)
During bootup the RVP8 measures the round trip delay along 1) the coax uplink to
the receiver module, 2) the pipeline delays within the receiver module, 3) the optical
fiber downlink to the main board, and 4) pipeline delays in the data decoding
hardware. The time shown is accurate to within 14ns, and is used internally to insure
that the absolute calibration of trigger and burst pulse timing remains unaffected by
the distance between the main board and the receiver module. You may freely splice
any lengths of coax and fiber without affecting the calibrations; the delay time will
change, but the trigger and burst calibrations will remain constant.
The standard deviation of the measured delay is also shown. If the coax uplink and
fiber downlink cables are run properly this variation should be less than the period of
the acquisition clock, e.g., 0.028 msec for the standard 35.975MHz rate. Larger
errors may indicate a problem in the cabling. A diagnostic error bit is set if the error
is greater than two acquisition clock periods.
IFD:Okay, Burst Pwr:–48.6 dBm, Freq:35.975 MHz
This line summarizes the receiver status and Burst input signal parameters. The
status may show:
Okay RVP8/IFD and connecting cables are all working properly
NoFiber Problem in DownLink fiber cable from RVP8/IFD ––> RVP8/Main
UpErr Problem in UpLink COAX cable from RVP8/Main ––> RVP8/IFD
NoPLL RVP8/IFD PLL is not locked to external user-supplied clock reference
DiagSW RVP8/IFD test switches are not in their normal operating position
Reset by: Software Up–time: 0–days 00:49:22
This line lists the origin of the last processor reset, as well as the total time that has
elapsed since that reset occurred. The running time is given in days, followed by
hours : minutes : seconds. The timer wraps around after approximately 180-days of
continuous operation. The cause of the last reset will be one of the following:
1) Power-Up 2) External RESET line
3) SCSI Bus Reset 4) RESET OpCode with “Pwr” bit
5) RESET OpCode with “Rst” bit 6) RESET OpCode with “Dig” bit
7) BOOT OpCode 8) Internal Watchdog
9) TTY “*” command 10) IFD Power Sequencing
11) Burn-In Self Tests
3.1.5 Burst-In / IF-In Swap Command
The “~” command swaps the Burst and IF inputs at the IFD. Requests to toggle the state are
made from the top level as follows: