Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:4
-
Epic Link:
-
Sprint:TSSW Sprint - Jun 21 - Jul 05, TSSW Sprint - Jul 05 - Jul 19
-
Team:Telescope and Site
-
Urgent?:No
Description
If there is a fault condition such as an e-stop pressed then the clearError command oscillates between the "FAULT" and "STANDBY" state forever. I think it should got to FAULT and stay in FAULT.
I observed this in today's testing. I believe the sequence was:
- Use the EUI to put the controller into DDS mode
- Use the hexapod commander to issue "enterControl" to the CSC
- The state goes to FAULT
- Use the hexapod commander to issue "clearError" to the CSC
- The state oscillates between FAULT and STANDBY. I see no sign that it will ever stop doing this.
That's the core of the problem above. But we continued as follows:
- Use the hexapod commander to issue "exitControl" to the CSC. The oscillation stopped.
- Use the EUI to issue "clearError". The oscillation resumed (as reported to the commander).
Attachments
Issue Links
- relates to
-
DM-29931 The camera hexapod starts to move when DDS control is switched on.
- To Do
-
DM-28695 The MTHexapod is mis-handling configuration changes
- Invalid
-
DM-29975 Please make the STOP command more reliable in the hexapod
- To Do
-
DM-30814 Have the Rotator Send Exactly the Same Telemetry and Config Data to the EUI and CSC
- Done
-
DM-29720 Support the Command Queue in Low-Level Hexapod Controller
- Invalid