LSE_CTXTIMFLAGS_V_SIMULATED_VALUE |
The timetone value is simulated |
LSE_CTXTIMFLAGS_V_SIMULATED_PPS_CPU |
The receiving CPU did not receive a 1 PPS interrupted, so the 1 PPS was simulated by a timeout. In this case, the timetone message should be okay. This bit is really here for hardware accounting purposes. If this happens, it may indicate a faulty interrupt line to the CPU |
LSE_CTXTIMFLAGS_V_SIMULATED_PPS_GEM |
The GEM did not get the 1 PPS. This IS a serious problem. It means the CPU thought that at least 1 second has gone by, but the 7-bit index in the GEM's 1 PPS register did not advance. One should not trust the 1 PPS register. |
LSE_CTXTIMFLAGS_V_NO_MESSAGE |
The receiving CPU did not have a timetone message corresponding to the 1 PPS GEM register at the time the event arrived. This is a semi-normal situation, occuring when the event from the EBM (normally an event that occurs very near the 1-PPS time) arrives at the processing CPU before the timetone message arrives. When events are being processed on an EPU, this is just a race between the event from the EBM to the CPU and the timetone message from the SIU. Under normal conditions, a timetone message with this bit set will be followed (within a couple of events) by the real timetone message. However, the processing software, not wishing to wait an indeterminate amount of time for the real message, fabricates a timetone message, marking it with this bit |
LSE_CTXTIMFLAGS_V_CNT_GPS_NO_LOCK |
The count of consecutive timetone messages that have an imperfect timetone message or reception. |
LSE_CTXTIMFLAGS_V_IS_SOURCE_GPS |
This is bit indicates the source of the time is the GPS. If not, the spacecraft lost the GPS lock and is simulating the timetone message by flywheeling off its own internal oscillator. This oscillator is very accurate, but one should exercise caution if the flywheel period lasts for a while. |
LSE_CTXTIMFLAGS_V_SA_RSVD |
Reserved for future use |