Reports 1-1 of 1 Clear search Modify search
VIS (PRM)
koki.okutomi - 22:03 Tuesday 09 July 2019 (9449) Print this report
PRM glitch investigation:

[Okutomi, Yamada, Aso, with remote help of Shoda]

  • To monitor the PRM output glitch in the analog path, we set a data logger in the voltage monitor port of the coil driver for BF horizontal LVDTs.
    • The data logger stores voltage outputs in recent 10 hours.
  • In order to keep the DC output from the DAC, I temporarily raised the AC-coupled RMS limits of the watchdog to 10,000 cnts for all the raw sensor inputs.

Bug report: klog#9439

Comments to this report:
ayaka.shoda - 11:17 Friday 19 July 2019 (9577) Print this report

I plotted the 10-hour data obtained by the data logger and compared with the trend.

Apparently the Ch2 (corresponds to BF H2) is noisy.

Other than that, I could not find the time the outputs became zeros during the measurement, while the trend data shows that PRM was operated in the ALIGNED state for a while.
I do not know why this happens. Do I misunderstand the time of the observation?

More investigation is required.

Images attached to this comment
Non-image files attached to this comment
kouseki.miyo - 8:28 Friday 06 November 2020 (15404) Print this report

Nakagaki, Miyo

We found wrong cable connection on the LVDT driver for BF-damper of PRM. The cable for the secondary coil and the cable for the primary coil are swapped.

This wrong cabling may be happen in the re-installation (klog#6499) without any cabling diagram or cabling procedure.

I think wrong cabling on the LVDT driver could be acceptable in the LVDT coils for GAS or IP because the LVDT coils and actuator coil are separated.

Hoever, in the case of BF-damper, they are mixing the actuation signal and the modulation signal of LVDT readout in the primary coil. I'm not sure whether this wrong cabling is acceptable or not for BF-damper.

(The cabling of other Type-Bp are same in each other except PRM)

Images attached to this comment
kouseki.miyo - 7:23 Tuesday 09 February 2021 (15960) Print this report

Nakagaki, Miyo

Today
Before replacing the wrong cabling, today, we clean up the cable labels not to miss the cabling by arranging the common naming convention defined in JGW-D2011573-v8.
During this work, we found some typos in this document. So update it to version 9 now.

Next
Though we clean up almost labels, we did not do for some labels due to several things that I have to check before the modification. 

  • IM1 and IM2 was not modified because I was not sure whether IM1 is IM-V or IM-H. 
  • BI, BO cable from HPCD to IO chassis were unclear to understand the label due to messy cabling.
  • PSD label was not prepared due to no description in the version 8.
kouseki.miyo - 6:51 Thursday 11 February 2021 (15988) Print this report
We had done following items for PRM rack. So we will fix the wrong cable next
  • IM1 and IM2 was not modified because I was not sure whether IM1 is IM-V or IM-H.
  • BI, BO cable from HPCD to IO chassis were unclear to understand the label due to messy cabling.
  • PSD label was not prepared due to no description in the version 8.
kouseki.miyo - 20:59 Thursday 11 February 2021 (15994) Print this report

After I fixed the wrong cable, the noise coupling at higher frequency of the BF-damper in PRM was reduced as shown in the attached first figure.
Coherence at the frequency is decreased after fixing the wrong cabling. (Python script that I used to plot is in '/users/Miyo/dropbox/LOG/210211/')




I also compared the TFs among other Type-Bp suspensions in the second attached figure. In this figure, I confirmed that all Type-Bp suspensions roughly have the same TF each other but there is a difference among PRM and the other suspensions due to wrong calibration in klog#6949. So, we should calibrate so that the PRM have same TFs like other PR suspensions.
 

shinji.miyoki - 8:53 Friday 12 February 2021 (15995) Print this report

Glitches in PRM are like in klog ??

Search Help
×

Warning

×