Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:TSSW Sprint - Sep 13 - Sep 27, TSSW Sprint - Sep 27 - Oct 11
-
Team:Telescope and Site
-
Urgent?:No
Description
I am not sure if this is an issue with the CSC or with the low level controller but we are constantly getting failures in state transition with the MTHexapod component when operating with the real hardware.
Assuming the system is in STANDBY state
A simple;
import salobj
|
|
|
r = salobj.Remote(salobj.Domain(), "MTHexapod", index=1)
|
|
|
await r.start_task
|
|
|
await salobj.set_summary_state(r, salobj.State.DISABLED, settingsToApply="default")
|
results in;
RuntimeError: Error on cmd=cmd_start, initial_state=5: msg='Command failed', ackcmd=(ackcmd private_seqNum=1948430428, ack=<SalRetCode.CMD_FAILED: -302>, error=1, result='Failed: Failed: final state is <State.STANDBY: 5> instead of <State.DISABLED: 1>')
|
most of the time, though it works some times. Despite the failure reported above the CSC does transition to DISABLED state shortly after.
I wonder if the CSC should allow a bit more time for the state transition to occur, or if the low level controller is reporting the command as completed too early.
Attachments
Issue Links
- relates to
-
DM-31244 Hexapod state transition from EnabledState to DisabledState is sometimes rejected
- Won't Fix
-
- Invalid
-
- Done