This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
operations:documentation.clock_and_delay_check [2012/11/13 02:48] Jim Lovell [Field System and station time agreement] |
operations:documentation.clock_and_delay_check [2014/09/12 00:40] Warren Hankey [GPIB communication with counters trobleshooting] |
||
---|---|---|---|
Line 15: | Line 15: | ||
If one or both counters are not responding to these commands, you will see an error message like this <code>ERROR sp -4 GPIB Device time-out on response c2</code> To fix this, try re-setting the counters. In the Operator Input window, type <code>counter</code> and try the ''maserdelay'' and ''clkoff'' commands again. | If one or both counters are not responding to these commands, you will see an error message like this <code>ERROR sp -4 GPIB Device time-out on response c2</code> To fix this, try re-setting the counters. In the Operator Input window, type <code>counter</code> and try the ''maserdelay'' and ''clkoff'' commands again. | ||
+ | |||
+ | =====GPIB communication with Agilent counters ===== | ||
+ | If the GPIB has been restarted (via the PDU internet power switch, or a power outage) a field system restart is probably required to re-establish communications with the counters connected to the GPIB. Symptomatic is ''fmset'' working OK, sync_error=0, but ''counter'', ''clkoff'','' maserdelay'' commands not working; the ddiff counter showing random large offsets and/or changing rapidly. Restarting the field system should bring the ddiff counter back to a steady several microseconds and enable GPIB comms. | ||