...
Camera Watchdog monitors the statuses of the FACET Profile Monitors, SIOCs, and POE Hubs, and attempts to revive cameras that become disconnected.
Bugs/Issues
Sometimes after an SIOC goes down, even if it comes back, the cameras on that SIOC get stuck on State 5 (purple lamps). Jiggling or rebooting cameras doesn't seem to help. Restarting the Watchdog usually fixes this issue.
| Issue | Status |
|---|---|
Camera Reports are using some old camera names. Fix is to restart the Camera Watchdog (e.g. XUV_SLIT → IPOTR1P) | WIP |
Key Features
- The Camera Watchdog creates Camera objects in MATLAB for each FACET Profile Monitor. Each Camera object stores data such as the Camera's name, location, and the number of times a reboot has been attempted.
- The Camera Watchdog also creates SIOC objects and POEHub objects for the relevant SIOCs and POE Hubs.
- Each Camera assigns itself a State based on its Connection status, Acquisition status (Acquiring or Idle), Trigger Mode (Sync in 1 or Free Run), and Array Rate (zero or nonzero). The State is updated any time one of these PVs changes.
- If the Camera is in a disconnected State, it attempts to revive itself and the Reboot Count goes up by 1.
- Once a day, the Camera Watchdog creates a report and saves it to a MAT file.
...
Each time a reboot is attempted, the Reboot Count for the camera goes up by 1. The Reboot Count of any camera can be called with "caget" (see below), " but it is also stored in the Archiver:
[fphysics@facet-srv01 ~/shperez ]$ caget CAMR:LI20:100:REBOOTCOUNT |
Daily Report
Once a day at midnight, the Camera Watchdog creates a report of camera data for all of the FACET profile monitors. It captures the following data in a table and saves it to a MAT file:
...