Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:TSSW Sprint - Apr 25 - May 09
-
Team:Telescope and Site
-
Urgent?:No
Description
During Camera hexapod verification the hexapod was given and a position and the EUI presented a different reached value.
E.g. The screenshot from 14.51.50 shows an expected X=0 and a reached X= 12861um.
Together with the reached value of Y= 5600, this would exceed the XY- limit at 11400um (X+Y = 12861um+5600um = 18461um)
The EFD sees the same values. See screen recording 2020-03-28 at 11.27.37.mov
After first triage with Te-Wei, this might be an issue with hexapod trajectory. Please investigate.
Update:
More faults were detected on April 31. Plots added here.
It was noted that struts 1 and 2 are not moving when these faults appeared.
Ian Ordenes asked for help. Connectors reviewed. No more faults were detected afterward. Further tests are needed.
Attachments
Activity
Documented the algorithm in Trajectory Generator in Hexapod.
Please help to review this ticket. The page is:
https://confluence.lsstcorp.org/display/LTS/Trajectory+Generator+in+Hexapod
Thanks!
Thanks, Te-Wei for looking into it. The issue did not reappear since the last time it was mentioned here. Nothing from the software side for this issue at the moment. Closing this ticket and keeping the FRACAS ticket open to monitor the situation.
After the discussion with Holger, this only happens twice in these months. Holger planned to do more test on 5/5. If there is any problem, I will be on the summit to support the debugging. In the meantime, I will use this chance to have some understanding of MOOG trajectory for the hexapod.