About 23:56 UTC on 1 April 2019, the CALCS CPU MAX increased from 58 to 63, turning the timing error readback from green to red on the CDS overview. It has since dropped to zero in trend data since, but remains at 63 on the medm. Plots showing the change, and a 10 day trend.
CPU_METER_MAX is a latched value which gets reset when diag_reset is pressed. The attached ndscope trend shows that the cpu_meter of calcs has been fluctuating for some time, and was increased slightly around 16:30 today (PDT). This has increased the probability of it exceeding the maximum processing time of 60uS and triggering the timing bit on STATE_WORD.
cleared the MAX CPU with DIAG RESET, and it dropped to 28, and is currently 35.