Reports 1-1 of 1 Clear search Modify search
AdV-INJ (Input Mode Cleaner cavity)
ruggi, chiummo - 22:43 Friday 09 October 2020 (49619) Print this report
IMC lock loss while MC is ramping

In recent times IMC (and PMC) is loosing the lock systematically when MC is moving in order to put RFC in resonance. Actually this action determines a variation of laser frequency, performed by the 'thermal correction' (in the data, BsX_ML_TH_CORR). This is an auxiliary actuator, which replaces the main one (ML_PZT), when the request of frequency variation is too large. The 'reallocation' of the actuation is performed by the board which take care also of the Beam Pointing Control (known by DAQ as BsX). The loop is simply an integrator whose input is BxS_ML_PZT_CORR and the output is BsX_ML_TH_CORR, sent to a DAC connected to ML_TH actuator. The loop can be very slow if only the natural drift of the frequency has to be compensated, but for the ramp needed in order to lock RFC it cannot be too slow. Currently the UGF could be somewhere between 0.1 and 1 Hz, but a characterization has never been done. With the current setting, the effect of the ramp on IMC length is that the thermal correction follows fast enough, but not so fast to keep PZT correction close to zero: usually it reaches about 0.5 V. At the beginning (5 years ago or so) the gain of the loop was lower, and the maximum value of PZT_CORR during the ramp was 1 V or a bit more. After some event of lock loss during the ramp (3 years ago or so), we evaluated that 1 V was to close to the tolerable limit of PZT_CORR, so the gain of thermal loop was simply doubled.

Today we investigate about the possible relationship between the lock losses during the MC ramp and some malfunctioning/large values/other stuff/ of TH/PZT loops.

The typical pattern of IMC lock loss during RFC locking has been replicated (fig 1): 50 um of MC displacement in 30 s, producing Delta TH_CORR = 40 mV and a maximal excursion of PZT out of zero < 1 V. The lock loss typically does not occur when PZT_CORR is larger.

A larger excursion of PZT_CORR (> 1V) has been produced in two ways, with TH loop disabled (fig 2): at first, a small offset (10 mV) has been applied to TH_CORR; then, a small displacement of IMC length (10 um) has been performed. No lock loss. PZT_CORR should not be the responsible of the problem.

Could be TH_CORR the responsible? A fast step (in 1 sample), has been applied (fig 3). 15 mV and no more, because the compensating action of PZT is more than 1 V. No lock loss.

We tried with the same 50 um IMC displacement, performed slowly (fig 4). At first, 60 s, then 120 s. Correction were doing their work quite smoothly. In both the cases, IMC unlocked with the same pattern.

One possible conclusion is that who annoys IMC (PMC) lock is the variation of frequency itself, and not the way that variation is performed.

 

Images attached to this report
Comments to this report:
chiummo, Ruggi - 20:36 Saturday 10 October 2020 (49621) Print this report

Just a look at the fast channels of the frequency stabilization loop while Paolo was changing the ML frequency via the thermal correction driven by the IMC lenght.

In the first plot an overview of what was happening at the laser frequency: Paolo was scanning in both directions the IMC length by roughly 50um, this drove the piezo and thermal correction of the ML to keep up. By a rough estimation, given that 240um of IMC length can scan a FSR of the RFC, the delta frequency  is of the order of 50um/240um * 472MHz ~100MHz. During the scanning, roughly at the same value of the thermal correction (plot 2) the IMC loses its lock.

In both cases, the first error signal to leave the null condition is the PMC_REFL_I (plot 3 - decreasing correction, 4 - increasing correction). It is worth noting that in both cases the behavior of the EOM_Corr is very similar to what happens in fast-unlock case where error and correction have same sign of derivative.

The current ISYS configuration is with the new PSL fibered amplifier replacing the SL-Neovan duo for providing the high power, but we still have the SL injection locked to the ML. Despite this, I am not able to see evident changes occurring during the investigated period.

Images attached to this comment
chiummo, DeRossi, Melo, Ruggi - 18:00 Monday 12 October 2020 (49632) Print this report

As suggested by Raffaele, I made a scan of the ML_TH_CORR with the IMC unlocked.

I put the rampeauto of the IMC in "manual",  misaligned by 30urad MC_TY, then:

1st plot: made a slow scan of ML_TH_CORR, both increasing and decreasing. While scanning, the PMC cavity lost lock many times. We can see the Slave laser PZT corr following the ML frequency variation quite smoothly, while this does not seem to be the case for the PMC piezo correction.

2nd plot: made a slow scan with PZT_CORR and EOM_CORR cables unplugged from IMC rampeauto. Did not see striking difference.

We zoomed in on one of these PMC unlocks: 3rd plot, where we can see a fast glitch occurring on the power delivered by the SL in coincidence with the unlock. Zooming further in (4th plot) the glitch seems to be due to some optical cross-talk with the PMC reflection (TBC).

No conclusions at the moment.

The IMC was relocked at the end of the measurement.

EDIT: the ISYS configuration did not change wrt the past days, i.e. we have the new fibered amplifier replacing the SL-Neovan,but the SL is still injection locked to the ML, and its beam is blocked before entering the Neovan. Also, before making a large scan with ML_TH_CORR (reaching out values as we saw in the past days), we made a scan comparable with that made on friday evening (40mV). This is reported in the plot 5, where we can see that the PMC loses its lock while decreasing the correction, but not when putting it back to the original value. Plot 6 is a zoom of the lock loss of the PMC.

In plot 5 we can see indeed a glitch in 50Hz-sampled error signal of the SL in coincidence with the lock loss, but not in the related fast channel (plot 6), perhaps because of the high frequency noise.

 

Images attached to this comment
Search Help
×

Warning

×