This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
operations:documentation.clock_and_delay_check [2014/12/17 09:55] Warren Hankey [Maser to GPS, Formatter to GPS delays and difference] |
operations:documentation.clock_and_delay_check [2014/12/17 09:55] Warren Hankey [Maser to GPS, Formatter to GPS delays and difference] |
||
---|---|---|---|
Line 19: | Line 19: | ||
- | **Be sure that mk5=sot? returns FHG_off before you run fmset. Sometimes if a power glitch occurs while the Mark5 is recording, it can get stuck. If FHG_on, end with disk_record=off and then run fmset again | + | **Be sure that mk5=dot? returns FHG_off before you run fmset. Sometimes if a power glitch occurs while the Mark5 is recording, it can get stuck. If FHG_on, end with disk_record=off and then run fmset again |
=====GPIB communication with Agilent counters ===== | =====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. | 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. | ||