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 - Jan 17 - Jan 31, TSSW Sprint - Jan 31 - Feb 14
-
Team:Telescope and Site
-
Urgent?:No
Description
Unify the servers of DDS and GUI in low-level rotator controller (use the existed DDS servers as a main body because they allow the connection/disconnection). To work on this, I would need to figure out why the wrapper sometimes has the problem to get the updated values from the Copley drive. In addition, I need to check the possible memory leakage in the code.
Note. In DM-32550, the code was updated to reject all connections to allow the rerun of wrapper code to remap the PDO of drive.
Use the version of 1.4.0 for rotator controller.
Attachments
Issue Links
- is triggered by
-
DM-32050 Refactor the Low-Level Rotator Controller to be the TCP/IP Server
- Done
- is triggering
-
DM-33252 Unify the Servers in Low-Level Common Code Repository in Phase 1
- Done
-
DM-33630 Test the Latest Version of Rotator Code on Summit
- Done
-
DM-33671 Rename the driverStatus to driveStatus in Low-Level Rotator Controller
- Done
- relates to
-
DM-32550 Reject the Following Connection Request in Rotator Controller
- Done
I discussed with Russell for the use case to put the CSC to be the default commander. In the long run, we will modify the state machine in the Simulink model. At this moment, if there is the interlock/drive fault in the Offline/PublishOnly state, the CSC will not try to clear the error. Instead, it should be EUI to do so. But CSC should be still able to connect to the controller to get the telemetry. I need to consider how to support this in the another ticket to put the CSC to be the default commander.