Written by Yuta
This morning, I could dither PR2 and PRM from ASC-ADS, but I can't now.
For example, even if I put on H1:ASC-ADS_PRM_PIT_OSC, the signal doesn't show up at H1:SUS-PRM_M3_ISCINF_P_IN1.
Since it did this morning(6AMish~10AMish), I suspect this is related to the boot festival today.
If I lookup the simulink diagram, h1asc.mdl has H1:ASC_SUS_PRM_PIT_DITHER, but h1prm doesn't.
[PRMI dither alignent work this morning]
We want the alignment automation to speed up the PRMI commissioning.
I checked the guardian script for PRX dither alignment Evan and I made yesterday. It now works for PR2 dither alignment. PRX_ALIGN state closes PR2 (and PRM) dither alignment loop, wait for a while, and offloads the feedback offset (e.g. H1:SUS-PR2_M1_LOCK_P_OUT) to the alignment slider values (e.g. H1:SUS-PR2_M1_OPTICALIGN_P_OFFSET).
For PRM, I had to lower the excitation frequency for pitch/yaw from 14/11.5 Hz to 5.4/7.2 Hz, and excite not only M3 but also M2 to get the error signal. I haven't checked fully yet, but the guardian script should also work for PRM dither alignment.
Next work is to do BS(or ITMY) alignment using PRY.
Just to make it clear:
The excitation was not active because of a change in the ASC model rather than the SUS models. I was in the middle of splitting the ASC paths into the low frequency feedback and dither paths. Currently only PR2 is capable of having the split dither signal.