- moved integrator from FM1 of IP_BLEND to FM1 of IP_ACCBLEND (Fig.1).
- set ramp time for IP_OPTICALIGN (Fig.2).
- swapped FM order of DC and DAMP, and added null filter on FM1 of IP_IDAMP (Fig.3).
- set GAIN and OFFSET as 1.0 and OFF, respectively for BF_OPTICALIGN (Fig.4).
- moved DAMP to FM3, and added null and DC on FM1 and FM4 of BF_DAMP, respectively (Fig.5 and Fig.6).
With Hirata-san.
Summary: the moved the BF pitch picomotor. The readout of V1 OSEM changes from 280 counts to 500 counts. This is still not enough and we need to move it more. There was an improvement of the IM-P transfer function.
After fixing the picomotor cable this afternoon we proceeded to tilting the BF in pitch.
The initial conditions were
- BF damper readout:
- L: -779 um
- T: 41 um
- V: 1,317 um
- R: 854 urad
- P: -1,144 urad
- Y: 5,543 urad
- IM OSEMs in counts:
- V1: 280
- V2: 9,320
- V3: 8,290
- H1: 5,500 cnt
- H2: 8,060
- H3: 6,440 cnt
- The BF was at 12 um from the setpoint.
After we moved the BF pitch picomotor, some of the the changes measured by the OSEMs and BF damper are
- H1: -334 um, 4511 cnt
- V1: 213 counts, -15 um (out of range).
- V2: 32 um, 432 counts,
- V3: 61 um, -907 counts
- BF-P: -1,377 urad
One of the relevant quantities is the ratio of (H1 displacement ) / (V1 displacement): H1/V1=-1.57 um/cnt. Although V1 is not in its linear range, it's possible to calculate an upper limit of how much we need to change H1 readout flag in order to bring V1 into range. Currently V1 is at about 500 counts. If we want to move it to 1500 counts more, we would need to move H1 2,355 um more. It might be possible. We will continue tomorrow.
We measure IM-Y and IM-P transfer functions. The IM-Y one suggests no flag it's touching its OSEM and the IM-P one shows improvement compared to the one we measured in the morning.
PR3 BF cable confirmed.
As you can see in the picture, there was a solder burr on it, and I suspect this may have been a bad thing because I want to be able to remove it easily by touch.
I think it would be better to remove and rejoin everything.
I will repair it and give it to you.
With Hirata-san.
We found that the cable adapter from D-sub 9 to RJ connector (that plugs into the picomotor driver) might have not been working. We borrowed the one from PRM and then the picomotor worked. We'll give it back once we have a replacement.
Now both BF picomotors are working.
[Ikeda, Yasui-san, Nakagaki-san]
Two issues found during routine maintenance have been addressed.
ETMY: NG -> OK
=> Can't connect to the rebooter either. Was the power supply disconnected? Cause unknown. Will check on Monday.
[Investigation result]
It was found that Picomotor and Picomotor's rebooter did not respond to ping during the regular maintenance on 9/27.
In the subsequent investigation, it was found that the temperature control device did not respond to pings as well.
When we checked the log of the temperature control device, we found that the connection was lost around 11:23 on September 20.
When I checked the log of the temperature control device, I found that the connection had been lost around 11:23 a.m. on 9/20. The backbone LAN cable was plugged into the power supply port of the network SW (S2112636:GS108TV3) placed in the VIS mini rack.
This LED was turned off and it was found to be unconnected.
This network SW had an AC adapter and a LAN connected to the PoE power supply port.
The network was restored by removing the AC adapter or connecting the AC adapter to a port other than the power supply port.
[Details]
The AC adapter was removed because it was found that PoE power supply was available.
Confirmed that it is connected to the network.
SR2_STM: NG -> OK
=> The rebooter is not installed yet, so I will install it next week to get it back.
=> Installed a switch (S2113327) for power control in Picomotor of SR2_STM.
Summary: Last week it was agreed that the strategy to follow to bring the V1 OSEM into range is to use a combination of BF-RM tilt and BF keystone height adjustments. Today I tried to do this, but realized the BF pitch picomotor doesn't seem to be working yet. Nevertheless, I was still able to move the BF keystone down and do an assessment.
I measured transfer functions having the system close to the nominal position of the BF at 8um (error function value). In this configuration, the readout of the OSEMs in number of counts is:
- V1: 390
- V2: 9310
- V3: 8310
- H1: 5546
- H2: 8020
- H3: 6460
Surprisingly, IM-V doesn't look so bad despite IM-V1 having a low readout. However IM-P does look bad. IM-Y looks relatively healthy. See screenshots.
Before moving the BF-P picomotor, I tried moving the BF keystone down to bring V1 OSEM into range at the expense of V2 and V3. Namely, I moved it to -565 um and -767 um. In both cases, the transfer fucntions IM-V becomes bad and and IM-Y suggest the OSEM flags must be touching the bodies.
Then I proceeded to move the BF pitch picomtor but it didn't work. We must go to the tunnel and check.
Abstract
- Filterbanks were cleaned up for guardian.- They were based on ones on k1visetmxt
- Set-points and matrices have been touched yet.
Details
At first, some FMs which were blank were set as OFF in safe.snap (See Fig.1).IP_ACCBLEND
Integrators on BLEND for converting velocity and displacement were moved to ACCBLEND same as klog#18152 (See Fig.2).
Integrators haven't been turned on yet. It should be turned ON in proper timing for data acquisition (maybe maintenance day?).
IP_OPTICALIGN
ramp times were set as 20s in safe.snap in order to unify other TypeA suspensions (See Fig.3 and Fig.4)
There is no difference yet because offset values are set as 0.
IP_IDAMP
FM positions of DC and DAMP were swapped in order to avoid glitches as reported in klog#18249.
And also, null filter was implemented on FM1 for floating.
Now null, DAMP and DC are set on FM1, FM3 and FM4, respectively (See Fig.5).
BF_OPTICALIGN
Because a new guardian turns ON/OFF opticalign by changing an OFFSET switch not a GAIN value,
GAIN and OFFSET were set as 1.0 and OFF in safe.snap (See Fig.6 and Fig.7).
BF_DAMP_Y
A DAMP filter was moved from FM4 to FM3.
null and DC filter was newly prepared on FM1, and FM4, respectively.
Current implementation is shown in Fig.8 and Fig.9.
In order to avoid numerical rounding error reported in klog#18254,
DAMP filter was modified as shown in Fig.10 (0Hz zero -> 0.01Hz zero).
Current DAMP, DC, and DAMP+DC filters are represents as red curves. Blue one shows an original DAMP filter.
(Integration time of BF_Y may be too long.)
Attachments are the error signal and RMS channel of each loop.
Y-cursors represent threshold of ISOLATED and ALIGNED.
The 2nd T-cursor shows the timing at being judged as ISOLATED or ALIGNED in old guardian scheme.
A new guardian can judge as ISOLATED or ALIGNED at the cross point of RMS channel and Y-cursor.
So in all cases (though there is a suspicion about BF_Y), waiting time can be reduced.
Black coated pipes.
Integration time should be adjusted with considering resonant frequency of each stage, ramp time, and so on.
Fig.1 shows error signals and rms monitors of GAS local loops after being engaged.
The behavior of signals from pre-engage to post-engage is shown in Fig.2.
It's drastically improved from klog#18301.
We noticed that LED of DGS network port was not blinking.
We doubted break of LAN cable because this cable had strong tension.
After we exchange LAN cable, the booting process was starting.
Due to conflicts with HDD replacement work, the work time was insufficient.
Today, only Type-A was updated.
Next week, I will update Type-B, Bp, and C.
Request from Ushiba-san
Add ACT align matrix before EUL2COIL and EUL2OSEM matrix.
Add k1:VIS-$(optic)_{IP,BF,MN,IM,TM}_ACTALIGN_x_x
optic: ETMX, ETMY, ITMX, ITMY
Others will be updated next time.
BS, SR2, SR3, PRM, PR2, PR3, MCI, MCE, MCO, IMMT1, IMMT2, OMMT1, OMMT2, OSTM
EUL2COIL:
IP:3x3, BF:6x6
EUL2OSEM:
MN:6x6, IM:6x6, TM:3x3
The initial value of Matrix is the unit matrix.
Request from Ushiba-san and Yamamoto-san
Changed the averaging time of the RMS monitor that was added last week.
Yamamoto-san's measurement of Tower's GAS suggested that the same time as the ramp time would be sufficient.
Changed the RMS time and data volume to the following values to match the ramp time.
Tower:
GAS(F0,F1,F2,F3,BF): 20sec * 2K = 40960
IP: 30sec * 2K = 61440
BF: 60sec * 2K = 122880
Payload:
5sec * 16K = 81920
[Target].
Window_size of TrueRMS in front of the next RMS_MON
K1:VIS-{optic}_IP_IDAMP_{L,T,Y}_IN1_RMS_MON
K1:VIS-{optic}_{F0,F1,F3,F3,SF}_DAMP_GAS_IN1_RMS_MON
K1:VIS-{optic}_BF_DAMP_{L,T,V,R,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_BF_OLDAMP_{L,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_BF_MNOLDAMP_{L,T,V,R,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_BF_PFOLDAMP_{L,P,Y}_IN1_RMS_MON
optic: ETMX,ETMY,ITMX,ITMY
Others will be updated next time.
BS,SR2,SR3,PRM,PR2,PR3
K1:VIS-{optic}_MN_DAMP_{L,T,V,R,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_MN_OLDAMP_{L,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_MN_MNOLDAMP_{L,T,V,R,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_MN_PFOLDAMP_{L,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_IM_DAMP_{L,T,V,R,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_IM_OLDAMP_{L,P,Y}_IN1_RMS_MON
K1:VIS-{optic}_TM_OLDAMP_{L,P,Y}_IN1_RMS_MON
optic: ETMX, ETMY, ITMX, ITMY
Others will be updated next time.
BS, SR2, SR3, PRM, PR2, PR3, MCI, MCE, MCO, IMMT1, IMMT2, OMMT1, OMMT2, OSTM
GitID:
Before: release/0.1.32
After: release/0.1.33
GpsTime:1316507134
Routine confirmation of DGS maintenance day (9/24)
Routine checks for DGS maintenance day (9/24) were performed.
There are no problems except for the known ones.
Stepper motor
[Checked that the power supply can be controlled by BIO.]
Checked if power can be controlled by BIO.
Check if Script can be started.
Check that the limit switch installed is green.
[Check result]
No problem
Release Sensor
[Checked]
Confirmed that the Release Sensor is 0. 1: Seated
[Check result]
ETMY, ITMX, ITMY : No problem
ETMX_F1_1 : abnormal, no other problems (known)
Picomotor
[Checked]
PingTest is performed.
[Result]
NG:
SR3_IM: NG
ETMX: NG
ETMY: NG => Both rebooted and came back.
ETMY: NG
=> Can't connect to the rebooter either. Power disconnected? Unknown cause. Will check on Monday.
SR2_STM: NG
=> The rebooter is not installed yet, so I will install it next week and get it back.
MCI,STM1,IMMT1,IMMT2:NG
AS_WFS,POP_POM,POS_POM,REFL_WFS,POM1: NG
=> Confirmation only, no recovery work done.
OK:
ITMX,ITMY
BS(IM,BF),SRM(IM,BF),SR2(IM,BF),SR3(BF)
PRM(IM,BF),PR2(IM,BF),PR3(IM,BF)
MCF(MCO,MCI),MCE
OMMT1,OMMT2,OSTM
PCAL(EX1,EX2,EY1,EY2):Not confirmed because it is ON only when used.
All RTFEs were rebooted once.
Remaining SDF diffs are as follows.
- ETMY_PAY: Fig.1, Fig.2
- ETMY_TWR: Fig.3
- ITMX_TWR: Fig.4
- ITMY_PAY: Fig.5
- ITMY_TWR: Fig.6
These diffs are also saved as ushiba.snap
Disk replacement of k1boot
HDD for NFS region (/opt) was replaced because of disk errors.
Current /opt is the copy of one around 10:30 today.
RTFEs must be rebooted when k1boot was rebooted.
real-time models seem to run fine.
But too many error messages are shown in dmesg as shown in Fig.7.
These errors cannot be solved by restarting real-time models.
For Workstations, DAQ, and other servers such as k1script, remount NFS region is enough as recovery works.
Power strip installation at OMC1 rack
Power strips were replaced as a new version.
DC-24V is not delivered to the OMC area yet. So local power supply still remains yet for RF Amplifier chassis.
And also OMC0 and OMC1 are connected as daisy chain because there is only one port at the breaker box.
DC100V power supply for HV PZT chassis is put on the floor. It should be mounted in the rack.
We noticed that LED of DGS network port was not blinking.
We doubted break of LAN cable because this cable had strong tension.
After we exchange LAN cable, the booting process was starting.
I had training to apply the First Contact on the glass plate with the jig for BS so that I could train to apply the FC widely.
I applied the edge of the circle first, then applied from top down.
It took about two hours to apply one coat today, but I think it'll take more longer out of the draft.
Current OMC anti-aliasing chassis has the following SNs:
- SN037
- S1808447
Date: 2021/9/24
Members: Dan Chen, Darkhan Tuyenbayev
- Checked S number of AA/AI circuit for OMC PDs.
- Checked YPcal Tx temperature sensor connection and taped it as a first aid.
- Attached an ASI camera on the telescope instead of the Nicon camera. (We still are waiting a parts we ordered)
- Took out the 2 pipes between EYA chamber and Tx/Rx module to coat a black coating
Current OMC anti-aliasing chassis has the following SNs:
- SN037
- S1808447
Black coated pipes.
We entered the PSL room 10:22-10:49.
We took the picture for the candidate place of the pt 100 temperature monitor.
And we temporary placed the five AIR temperature monitor inside the PSL room.
After my check, I found mis-programming and correct calibration factor is
PIT_i=251.688326 [urad/cnt]
YAW_i=-276.854928 [urad/cnt]
PIT_o=90.323135 [urad/cnt]
YAW_o=-96.749226 [urad/cnt]
PIT_e=142.644487 [urad/cnt]
YAW_e=-108.742932 [urad/cnt]
And from klog3175, the alpha value of MCi oplev was 0.23 deg., but is it too small?
We will check by CAD
I added the channels of sampling rate512 Hz on crontab of k1sum1.
Oshino-san kindly pointed out that Omicron (trigger search pipeline) was not running after the power outage.
This problem was caused by not-ordered and deplicated file list in cache file. I fixed it, so the results will appear on summary page.
Actually this issue is the second time. So, I will add the memo on wiki page of Omicron.
I added the channels of sampling rate512 Hz on crontab of k1sum1.
Abstract:
I designed the damping fiter for ETMY MN photo sensor.
I couldn't finish for all dofs, but the filters for L and T seem to work well.
Detail:
First, I measured the transfer function from K1:VIS-ETMY_MN_TEST_L to K1:VIS-ETMY_MN_DAMP_L and with this transfer function, I made SUSMod. Fig 1 shows this model and it seems the model (blue line) and measurement (red line) are matched well.
Next, I made the DAMP filter (Fig 2), and combined with SUSMod (Fig 3). Then I measured the transfer function again, and the result is shown in Fig 4. From this figure, I can say damping fiter works well.
I did the same thing for T and it seems ok, too (Fig 5). I couldn't finish for R, P, Y, so I will do next time.
* The diaggui files (TF_ETMY_MN{L,T}EXC_20210922.xml) are in /users/VISsvn/TypeApayload/ETMY/TF/Measurements/20210922.
With Hirata-san.
See album SR2 Remedying work after O3.
According to report 18237, the coil in the IM-V3 OSEM had a higher resistance than expected (24.2 Ohm vs. 19.6 Ohm), so we investigated.
The OSEM is connected to the upper flange via three cable segments:
- Segment 1: from the OSEM to the BF.
- Segment 2: from the BF to the base of the preisolator.
- Segment 3: from the base of the preisolator to the flange.
We found that the problem is in the male connector at the upper end of segment 2. When some of the pins are touched the resistance varies a lot, including becoming an open circuit sometimes.
We aim to fix the connector early next week.