Details
-
Type:
Bug
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Epic Link:
-
Team:Telescope and Site
-
Urgent?:No
Description
26.04.20
The camera hexapod started to move when switched to DDS control this morning.
The hexapod executed a command that was given while DDS mode was off.
There was some testing the night before while the Hex was in Enabled/Stationary with DDS connection of.
Starting a movement by switching on DDS control is at least unexpected.
When switching on DDS mode all previous command should be dropped and only new commands accepted.
Attachments
Issue Links
- relates to
-
DM-28687 The MTHexapod low-level controller mis-handles clearError if there is a fault condition
- Done
Activity
I am pretty sure this must be in the low-level controller. I can't quite imagine how it can be in the CSC.
After the update of DM-28687, the cmdMsgBuffer will be a thread-safe circular queue. Therefore, I intend to remove the restriction that only the EUI or DDS can control the low-level controller in a single time. This is to align the behavior of M1M3 and I think this is preferred. This also means I could remove the EUI function to release the command source to DDS. The DDS does not need to wait the EUI open to release the control. It should be able to communicate with the low-level controller directly.
I am assuming this is in the CSC control, but I might be wrong. Te-Wei Tsai might need to help out with this. Thanks.