User Manual

Maintenance RF-Baton! Transmitter Controller Installation and Operation
6-20 6880497G01-B June 1999
5. View the error log to determine if any of the following network time errors are present.
At the prompt, type:
a 104 <Enter>
The terminal displays the error messages. (see Appendix D).
– E_LATE_LAUNCH_TIME (caused by too little network delay)
– E_UNMATCHED_ACTIVE_SUBCHANL_LAUNCH_TIME
– E_DUPLICATE_MDP_FRAMES
These errors are indications of network problems.
Note: 1 tick = 10 ms.
6. Observe the difference between the Launch ticks and the Calc Launch ticks to check the
RF-B! transmitter controller and transmitter time synchronization.
The Launch ticks represent the actual launch time of the message by the transmitter. The
Calc Launch ticks represent the time the transmitter must receive the data to launch at the
proper launch time. The difference between the Launch ticks and Calc Launch ticks is
dependent upon parameters received by the RF-B! transmitter controller from the
transmitter on startup.
The two values are the Workahead Time (FIPS parameter 602) and the Workahead
Window Width (FIPS parameter 603). The difference between the Launch ticks and Calc
Launch ticks
should be:
Tick delta = round up{ [ (Workahead Window/2) + Workahead Time]/10}
If the actual delta is less than the expected delta, check the transmitter values which get
reported to the RF-B! transmitter controller.
Network time errors are caused when the RF-C! controller schedules simultaneous
transmissions on the same subchannel. This can happen when the RF-C! controller makes
a positive time change correction causing data to overlap.