This morning, the channel monitoring the arrival time of the Sc_WI DSP jumps from 10-15us to 67-72us (see the attached plot), as consequence the DMS Timing_dsp became red
At the same time period, the SUSP_Fb TolmFrameBuilder reports the following lines
2024-06-04-07h37m35-UTC>WARNING-[TolmFrameBuilderFrontEnd] Sc_WI: packet rejected: merging already done (packet: 1401521873.1004913890 < frame in construction: 1401521874.000000000) (49 times)
2024-06-04-07h37m36-UTC>ERROR..-[TfbSource::StoreData] producer Sc_WI: overflow at GPS 1401521874.199988880 (received 2001 / expected 2000) (61 times)
2024-06-04-07h37m36-UTC>WARNING-[TfbSourceManager::Merge] Times are different: dt: 0.200000-0.200000 / GTimeN: 0-1000000000 / GTimeS: 1401521874-1401521873
2024-06-04-07h37m37-UTC>WARNING-[TolmFrameBuilderFrontEnd] Sc_WI: packet rejected: merging already done (packet: 1401521874.1081887540 < frame in construction: 1401521875.000000000) (818 times)
2024-06-04-07h37m37-UTC>WARNING-[TolmFrameBuilderFrontEnd] Sc_WI: packet rejected: merging already done (packet: 1401521874.1995088790 < frame in construction: 1401521875.800000000) (9132 times)
2024-06-04-07h37m37-UTC>WARNING-[TolmFrameBuilder::ControlMerging] frame: 1401521875.000000000: merging is triggered on timeout (internal 1401521875.360415040 > max 1401521875.360000000)
2024-06-04-07h37m37-UTC>WARNING-[TfbSubFrame::Fill] GPS: 1401521875.000000000 - Source Sc_WI: 1999/2000 missing packet(s), 0 data break(s) (missing data are at the end of the vector)
2024-06-04-07h37m37-UTC>WARNING-[TfbSourceManager::Merge] Times are different: dt: 0.200000-0.200000 / GTimeN: 0-1000000000 / GTimeS: 1401521875-1401521874
2024-06-04-07h37m38-UTC>ERROR..-[TfbSource::StoreData] producer Sc_WI: overflow at GPS 1401521876.199972090 (received 2048 / expected 2000) (2928 times)
2024-06-04-08h17m15-UTC>WARNING-[TolmFrameBuilder::ControlMerging] frame: 1401524253.000000000: merging is triggered on timeout (internal 1401524253.361715080 > max 1401524253.360000000)
This channel is only a monitoring channel, used to check the correct DSP cycles running conditions. Up to now there is none logbook entry reported any activity of this DSP, so it's maybe an issue