Closed BradSchoenrock closed 6 years ago
Note that I just found Error 66 from the wavemeter. It apparently happens when the wavemeter closes comms from the computer. This is easy to ignore so a default value is returned to the wavemeter of -1, -1, -1, -1. The Command Interpreter knows to look for a value of -1 to retry the communication.
during the 6 week test coming up i would like to test how the python CFRadial merging routine behaves when children are shut down. It would be good to reserve a couple days for turning on or off the subsystems for
Data Power LaserLocking Etalons WeatherStation
We should test power failures on those subsystems as well as changes in controls by users which might halt creating their respective data files in as much as will be possible.
Just got error warning -1073807265 from the Thor8000 box. It is caused by the modules in that box turning off. Scott thinks it is related to power spikes. Resolution is to program a warmup function that will turn all those things back on as needed.
Saw error 62 from the wave meter a few days ago. This error has not recurred but a trap can be added if it does. It is similar to error 66 and should be handled accordingly.
This is a very general comment. Individual errors are going to be logged here in the future so I am closing this issue.
We want known errors to be able to recover.
One example of this is the MCS UDP port becoming non responsive. We want the MCS to re-enter the config/init phases to reset the state of the MCS when the MCS regains UDP connectivity. Similar error handling needs to take place in other children.