As reported in alog71528, the ETM cameras were frozen last night, and the camera guardian went to WAIT FOR CAMERA state and came back in 1 min. This process was repeated three times as shown in the attached figure.
Looking back the guardian log, the ETMX camera (PIT2, YAW2) was frozen. I also looked at the VALID channel for ETMX/ETMY cameras mentioned in alog71460 (H1:VID-CAM25_VALID for ETMX, H1:VID-CAM27_VALID for ETMY). The VALID channels of ETMX/ETMY were 1 at that time, which means that the cameras were not actually frozen. So we probably can use this VALID channel to solve the short camera freeze issue for ETMX/ETMY. Unfortunately, the BS camera does not have the VALID channel since the ETMX/ETMY cameras are running on h1digivideo3, while the BS camera is running on h1digivideo2.
It may be that the VALID channel was frozen, but I'm not certain how likely that is or how to best tell. Maybe if there was a way to put a source of dither on the light the camera is seeing, but then that would interfere with the servo. The best solution might be to put the cameras that are used for servos on Beckhoff. The issue there is that it is not well suited for providing a remote camera image display. We could additionally add a keep alive signal that alternates between 0 and 1.