Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:3
-
Epic Link:
-
Sprint:TSSW Sprint - Sep 27 - Oct 11
-
Team:Telescope and Site
-
Urgent?:No
Description
Once DM-31883 is implemented (or in progress) update the MTHexapod CSC so that the client is in the CSC and the server is in the mock low-level controller (the opposite of the current situation).
In addition: adopt Tiago Ribeiro's suggestion to decouple the low-level controller's application state (which includes the usual CSC states) from the CSC's own summary state. When the CSC is enabled it should command the low-level controller into the enabled state. This decoupling should eliminate a source of nonstandard CSC behavior and makes the MTHexapod and MTRotator CSCs much more standard. It is also a good step towards allowing the low-level controllers to have simplified application states, should we decide to do that.
This will require additional configuration for the CSC to specify the IP address of the low-level controller.
Attachments
Issue Links
- is triggered by
-
DM-31883 Refactor the Low-Level Hexapod Controller to be the TCP/IP Server
- Done
- is triggering
-
DM-32054 Delete the clearError command from MTHexapod and MTRotator
- Done
-
DM-32230 Separate the State Machine of M2 Controller and Python CSC
- Done
- relates to
-
DM-32288 Fix handling state transition failure in mthexapod
- Done
Private IPs of hexapod PXIs on summit:
1. camera hexapod: 10.9.57.226
2. M2 hexapod: 10.9.57.231