Reports 1-1 of 1 Clear search Modify search
AdV-COM (AdV commissioning (1st part) )
bersanetti, masserot, mours, allocca, ruggi - 0:17 Wednesday 07 June 2017 (37871) Print this report
Full day ITF recovery & demodulation frequency mistuning

After today's maintenance we found nearly impossible to lock, even the initial PRITF configuration was difficult to get and to keep; we found a very big line in SSFS signals exactly at 10 kHz (see Figure 1), which seemed suspicious from the start. We contacted SSFS experts, and Alain found out that such line appeared on Sat Jun 3rd at around 19:56 UTC, and began to grow (see Figure 2), with some additional noise at very low frequency as well. This was in between locks, when FmodErr was being tuned, and he suspected our tuning of the demodulation frequency (which I thought had been disabled for the time being) as a culprit. Indeed there was a big change in the demodulation frequency in correspondence of the appearance of the line, and the same happened today (see Figure 3); also, the 56 MHz frequency was mistuned by 2 Hz.

Given the ITF behaviour of the last days, one could assume that the system recovered in some way only when the mechanical tuning of FmodErr was triggered, and then progressively degrade again; this is far from being a valid hypothesis, but the trend of the MC Z position right after the LNFS jumps suggests something similar. After this we decided to remove the LNFS frequency tuning from the FmodErr procedure, and Benoit changed the requested demodulation frequencies used by the demodulations mezzanines of the daqboxes to make them consistent to what FmodErr has changed.

A reload of all the *_dbox_bench configurations was needed, and this made all the demodulation phases to be retuned:

  • the RFC phases have been tuned as first thing; the RFC lock was immediately recovered but maybe some fine tuning of the demodulation phase is still needed, to be better checked tomorrow;
  • the phases for all the longitudinal signals have been correctly recovered;
  • I spent the rest of evening trying to tune the phases for the QPD signals, in order to restore the good alignment configuration; the B2 QD2 signals, used in PRITF @ MICH_SET = 0.7, were recovered and the path towards dark fringe is working reasonably well, and we went back to DC_READOUT; as we were trying to recover the other QPD signals, with some difficulty due to some strange sidebands behaviour and some signals being poorly sensitive on both quadratures, we had to quit to leave time to some noise injections.

The last phases we tuned and the switches that will need to be uncommented are in ITF_LOCK, lines 2415-2440.

Images attached to this report
Comments to this report:
carbognani - 15:06 Wednesday 07 June 2017 (37877) Print this report

> he suspected our tuning of the demodulation frequency (which I thought had been disabled for the time being) as a culprit.

I wanted to check when the tuning was activated, and I report here the path I followed just as a reference for looking for changes inside the automation scripts.

The involved file is INJ_MAIN.py, the latest changes/upload can be seen this way:

svn log $SVNROOT/Automation/userapps/trunk/INJ_MAIN.py | more

------------------------------------------------------------------------
r67092 | virgod | 2017-06-06 19:11:11 +0200 (Tue, 06 Jun 2017) | 1 line

DAEMON RELOAD
------------------------------------------------------------------------
r66990 | virgod | 2017-05-30 14:56:25 +0200 (Tue, 30 May 2017) | 1 line

DAEMON RELOAD
------------------------------------------------------------------------
r66977 | virgod | 2017-05-30 12:12:14 +0200 (Tue, 30 May 2017) | 1 line

DAEMON RELOAD
------------------------------------------------------------------------
r66973 | virgod | 2017-05-30 11:12:20 +0200 (Tue, 30 May 2017) | 1 line

DAEMON RELOAD
------------------------------------------------------------------------
r66972 | virgod | 2017-05-30 11:07:41 +0200 (Tue, 30 May 2017) | 1 line

DAEMON RELOAD
------------------------------------------------------------------------
r66900 | virgod | 2017-05-26 19:12:32 +0200 (Fri, 26 May 2017) | 1 line

DAEMON RELOAD
 

So it can be seen that a series of reload happened on May 30. To look at what changed on those reloads we can compare the previous (66900) and final releases (66990) this way:

svn diff --diff-cmd tkdiff -r 66900:66990 /virgoDev/Automation/userapps/INJ_MAIN.py

This generate the diff reported in Fig. 1 where it can be seen that, indeed, the tuning of the demodulation frequency was activated. From that time it remained active and generated the trends seen on Fig. 2.

Rediscussing with Maddalena she confirmed that the activation happened at that time.

Images attached to this comment
Search Help
×

Warning

Error

The present report has been modified outside this window. Please check for its integrity in the main page.

Refreshing this page will move this report into drafts.

×