[INSTRM-1560] Inspect the suspect cobra before engineering run Created: 25/Mar/22  Updated: 26/Oct/24  Resolved: 03/Jun/22

Status: Done
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: chyan Assignee: chyan
Resolution: Done Votes: 0
Labels: EngRun
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File INSTRM-1560.ipynb    
Issue Links:
Relates
relates to INSTRM-2407 Adding XML file after reactivating co... Done
relates to INSTRM-1554 Double check the cobra health status ... Won't Fix
relates to INSTRM-725 Flag suspect cobra motion as soon as ... Won't Fix
Story Points: 2
Sprint: PreEngRun05 E, PreEngRun05 G

 Description   

As listed in XML file, there are 36 cobras are flag as "bad" cobras now. Also, we found few cobras constantly going to nowhere during convergence tests. According to our experience in ASRD during AIT phase, re-calibrate those cobra usually helps them get back to healthy. Therefore, a close inspection on those suspect cobra is needed.



 Comments   
Comment by hassan [ 08/Apr/22 ]

Needs to be done before the May engineering run.

Comment by hassan [ 22/Apr/22 ]

This will be done when Chi-Hung visits Subaru. 

Comment by chyan [ 06/May/22 ]

We start the inspection process on May 4th and 5th. 14 cobras are disabled after the delivery and we successfully recovered 12 by tuning their frequencies. Further calibration like on-time, geometry and motor map will be carry out after we finishing the inspection on bad cobra before delivery.

Comment by chyan [ 06/May/22 ]

The file INSTRM-1560.ipynb showing how we re-activate the cobra.

Here is the new XML after re-activating the cobra marked as bad after the delivery.
https://github.com/Subaru-PFS/pfs_instdata/blob/master/data/pfi/modules/ALL/ALL_final_20220505_mm.xml

Comment by hassan [ 03/Jun/22 ]

Following discussions with chyan, this ticket is considered done.

Generated at Mon Apr 28 17:47:20 JST 2025 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.