WFS1_PIT servo replotted with foton data overlaid:

I included the following filters in foton:

1) Integrator: zpk([0.8],[0],0.8,"n")

2) zpk([0.8],[100,100],1,"n")

3) zpk([1:10],[3,30],1,"n")

4) ELP28

I have unwound the phase by adding or subtracting 180 to portions of the phase data.

And here is the plot for WFS1_PIT.  I will repeat this process for the other three WFS loops tomorrow.

 As promised, I will get on this this week.

Locking activity last night :

  The free run beat-note in 532 nm has been measured.

However I couldn't close the ALS loop somehow.

Every time I tried closing the loop it broke the Y end PDH lock in a couple of minutes.

 (Things to be done)

   1.  Optimization of the Y end PDH servo loop

   2. Refinement of the broadband RFPD setup

Dataviewer is not able to access to fb somehow.

I restarted daqd on fb but it didn't help.

Also the status screen is showing a blank white form in all the realtime model. Something bad is happening.

JAMIEEEE !!!!

 So something very strange was happening to the framebuilder (fb).  I logged on the fb and found this being spewed to the logs once a second:

[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 15:28:51 2011] going down on signal 11
sh: /bin/gcore: No such file or directory

Apparently /bin/gcore was trying to be called by some daqd subprocess or thread, and was failing since that file doesn't exist.  This apparently started at around 5:52 AM last night:

[Tue Nov 15 05:46:52 2011] main profiler warning: 1 empty blocks in the buffer
[Tue Nov 15 05:46:53 2011] main profiler warning: 0 empty blocks in the buffer
[Tue Nov 15 05:46:54 2011] main profiler warning: 0 empty blocks in the buffer
[Tue Nov 15 05:46:55 2011] main profiler warning: 0 empty blocks in the buffer
[Tue Nov 15 05:46:56 2011] main profiler warning: 0 empty blocks in the buffer
...
[Tue Nov 15 05:52:43 2011] main profiler warning: 0 empty blocks in the buffer
[Tue Nov 15 05:52:44 2011] main profiler warning: 0 empty blocks in the buffer
[Tue Nov 15 05:52:45 2011] main profiler warning: 0 empty blocks in the buffer
GPS time jumped from 1005400026 to 1005400379
[Tue Nov 15 05:52:46 2011] going down on signal 11
sh: /bin/gcore: No such file or directory
[Tue Nov 15 05:52:46 2011] going down on signal 11
sh: /bin/gcore: No such file or directory

The gcore I believe it's looking for is a debugging tool that is able to retrieve images of running processes.  I'm guessing that something caused something int the fb to eat crap, and it was stuck trying to debug itself.  I can't tell what exactly happend, though.  I'll ping the CDS guys about it.  The daqd process was continuing to run, but it was not responding to anything, which is why it could not be restarted via the normal means, and maybe why the various FB0_*_STATUS channels were seemingly dead.

I manually killed the daqd process, and monit seemed to bring up a new process with no problem.  I'll keep an eye on it.

Ben and Sam came over to fix one of  the east side  sliding  door sensor that had to be moved from the inside  to outside on the enclosure.

We turned off the 2w Innolight for 20minutes. The power is back on, the  PMC and MC locked itself immediately.

This moring I centered the IOO Angle QPD. The IOO Pos QPD was not centered. The existing layout does not allow the beam centering of the Pos qpd without misaligning the MC

input. We have to add an aditional steering mirror. I will do that tomorrow morning.

 Yes the files are in /opt/rtcds/caltech/c1/scripts/MC/WFS.

I just went to wherever the 'scripts' alias takes me, found the 'pwd' and did a cp+paste of the path.   I checked to be sure that 'scripts' takes me to /opt/rtcds/caltech/c1/scripts/.

So why does the pwd show /cvs/cds.... instead of /opt/rtcds  ?

[Jenne, Mirko]

1. We should help the OAF by compensating for the actuator TF:

The actuator TF, from adaptive filter output to MC2, through PD, mixer, Pentek and into C1:IOO looks like this:

If we assume a white-ish error signal that the adaptive code tries to compensate for its job gets extra complicated because it has to invert this TF. So we really should compensate for that. Easiest place for that is the CORR filter directly behind the adaptive code block.

Using the TF measurement from above I used the vectfit (" /cvs/cds/caltech/apps/mDV/extra/firfit_forFotonMirkoComplex.m" ) to get fit a corresponding digital filter:

If we invert swap the zeros and poles in the digital filter we get the inverted TF.
(Todo: Figure out how to invert the TF. Just switching the poles and zeros doesn't work).

2. Wiener filtering

The idea was to use the adaptive filtering only for small corrections to the wiener filtering. So we really should try to get the wiener filtering going.

Howto:

1. Get data for STS1X and GUR1X and MC_F in matlab. E.g. via ligodv
2. Check the MC was in lock the entire time.
3, Filter MC_F with the actuator TF, so the wiener filter knows about that and compensates for it
4. Calculate the wiener filter " h1winolevLigoDV.m "
5. Export the data to the workspace. It is also saved to the disc as "h1filtcoeffTS.mat". Make sure there are first the witnesses, then MC_F
6. Execute " /cvs/cds/caltech/apps/mDV/extras/LHO/firfit_for_FotonMirko.m" while one directory higher. 
7. Copy the digital filter in SOS form that is printed into the matlab command line and put it into the corresponding filter in the OAF model via foton.

With data from 11-11-15 04:00 to 05:45. Sampling freq. 256Hz. 8000 Taps => length = 30.2s. Prefiltered to notch the 60Hz line in MC_F, but not compensation the actuator TF. This results in the following wiener filter and corresponding SOS filter to be copied into foton.
STS1X:

GUR1X:

Earlier this evening C1:LSC died then I hit the DAQ reload after adding an OAF channel to be recorded. No change to any model. Had to restart C1:SUS too. Reloaded burts from this morning 5am, except for C1:IOO, which I loaded from 16:07.

Elog was hanging. Restarted it with script.

Basically, elog hangs up by the visit of googlebot.

Googlebot repeatedly tries to obtain all (!) of entries by specifying  "page0" and "mode=full".
Elogd seems not to have the way to block an access from the specified IP.
We might be able to use http-proxy via apache. (c.f. http://midas.psi.ch/elog/adminguide.html#secure)

Or can we tweak the source of elod such that it does not accept "page0"?


GET /40m/page0?mode=full&new_entries=1 HTTP/1.1
Host: 131.215.115.52:8080
Connection: Keep-alive
Accept: */*
From: googlebot(at)googlebot.com
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Accept-Encoding: gzip,deflate

I measured the Transfer Functions between from IN2 to IN1 on the WFS1PIT, WFS2PIT, WFS1YAW and WFS2YAW servo loops. 

Then I used the foton filter profiles of the servo filters in the loop and added another one to simulate the pendulum to generate a reasonable fit to the data.  Only the pendulum filter was hand tweaked since the PIT and YAW pendula have different resonant frequencies.

The filter modules included are:

1) Integrator: zpk([0.8],[0],0.8,"n")

2) Phase lead: zpk([0.8],[100,100],1,"n")

3) 45 deg filter: zpk([1:10],[3,30],1,"n")

4) ELP28: ellip("LowPass",5,1,50,28)

5)Pendulum: zpk([ ],0.03+i*0.82;0.03+i*0.82;],1,"n"  (for YAW)

5)Pendulum: zpk([ ],0.05+i*0.68;0.05+i*0.68;],1,"n"  (for PIT)

The data and fits are below.   The UGF is around 2 to 3 Hz and there is no servo bump at this gain setting.  The fits are poor at and below the resonance because the coherence was poor at these frequencies.  I will have to do a swept sine measurement for these low frequencies.

[Steve, Suresh]

    Steve went over to the MC2 walkway and stepped over the barrier to pick up some stuff there.  MC2 stack shifted and MC2 pitch as off.  MC unlocked and could not relock till the MC2 pitch bias was readjusted

previous MC2PIT reading: 3.6235           current MC2PIT reading:  3.9565

Without the WFS the MC to PSL alignment is poor, but it is largely due to a shift in the MC and not a shift in the PSL beam.  We know this 'coz the shift in the DC spot positions on WFS (when the MC is unlocked) is not significant nor is the shift on the C1:IOO-QPD.  When WFS loops are engaged the MC optics are turned to optimise the PSL to MC alignment, but the shift is large at the moment.

(Sorry Mirko your measurement could not be completed.  The MC unlocked in the middle)

Please Note:  If you need to access the blocked off area near MC2 stack, do not step over the barrier.  The disturbance is too great and the MC2 stack will shift.  Instead please move the barrier aside and walk as gently as possible near it, taking care not to touch the MC2 Chamber.

I turned on the two remaining loops in the ASC system to see if we can lock.   I put in some ones into the WFS_OUTPUT matrix

and locked the MC2_TRANS_PIT and MC2_TRANS_YAW loops.

The effect of doing so is visible in the error signals.  The black loops are with all ASC loops off, Blue traces are with the WFS1 and 2 loops locked and Red traces are with all loops locked.  I took the red traces to a lower frequency to see if the suppression of the error signals at low frequencies is disturbed by the switching on of the MC2_TRANS loops.  They seem to be working fine without adding any perturbation above the UGF.

I measured the  Transfer Function coefs (at 10Hz using the WFS Lockins)  with MC2_TRANS loops locked in this rudimentary fashion

The green and blue bits are the only relevant parts since we ignore the off diagonal parts.  And most of these off diagonal coefs are indeed quite small (<5% of the max).  I have marked the not-so-small ones in yellow.

I then calculated the output matrix elements in two different ways.

a) Using a null vector in the place of MC_DoF --> MC2_TRANS transfer coefs.  The output matrix we get is

b) Without using the null vector.  i.e. using the MC_DoF --> MC2_TRANS transfer coefs and inverting the full matrix.  The output matrix we get is

I plan to try out these two output matrices and measure the OL TFs of the MC2_TRANS and see if we can include these into ASC in a useful fashion.

 I added the steering mirror for Pos  and centered both qpds

 There are much more simple ways to prevent page indexing by googlebot: http://www.google.com/support/webmasters/bin/answer.py?answer=156449

However, I really think that's a less-than-idea solution to get around the actual problem which is that the elog software is a total piece of crap.  If google does not index the log then it won't appear in google search results.

But if there is one url that when requested causes the elog to crash then maybe it's a better solution to cut of just that url.

The  PRM lost damping about a day ago. It was restored.

Apparently the MC2 stack had not finished shifting.   The MC unlocked while Steve was working on the PSL table installing the mirror for IOO_QPD and then it could not relock.  So I moved the MC2 once again in Pitch.  The current status of the sliders is here

Yesterday I fixed the yellow buttons on the MC_ALIGN and MCLOCK screens.  They use the new updatesnap script  .  Could we also add a couple of lines to this script so that eveytime we save a snap shot the various values are written(appended) to a text file?  That way we do not need to depend solely on the conlog, which is quite slow.

- elogd itself is a sort of web server which has no freedom to put our own file, we can not put robots.txt

- If we include elog using proxy in the usual web tree of Apache, we can put robots.txt at the root.

- So far, if we prevent "page0" browse by google, we will be saved for a while.

- It seems that the indexing is set to be refused by the following meta tags. But it does not prohibit googlebot to use "page0" URL, of course.

<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">

C1:IOO-QPD_ANG_VERT beam movement  in 1 degree C temp change in 3 hrs

MC was not locked for more than 5 hours because of the misalignment.

Noticed that MC2 WFS feedback filters had big outputs (particularly in Pitch).
They were reset to zero.

MC2 was aligned and recovered the lock. Once the WFS is engaged, the transmission returned to the uisual value.

Some updates on the Y end green PDH lock

(Measurement of the Y arm fluctuation)

 

(Temporary servo setup)

(Sanity checks)

MC fell out of lock and was then quite badly misaligned. Mostly in pitch. I realigned it and it locked ok.

Turns out the MC falls often out of lock when the WFS servo comes on. I think the MC2_Trans history is not cleared on lockloss. I cleared it manually and realigned. Seems fine for now.

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

 I suspect the integrators get fed a huge wrong signal on lockloss. Clearing the history on the trans DOFs when the MC was badly aligned gets it nicely aligned again. I switched off the alignment transmission DOFs for now.

I made a super sweet new foam box for our EOM.  It's awesome, and should be reasonably easy to duplicate.  Check out the PHOTOS!

Notes:

* I didn't think I was going to cover the inside of the box at first, since the foam is non-fuzz-generating, but Koji suggested it would be a good idea anyway.  The foam was cut perfectly to the EOM, so adding the tape inside makes it a tight fit.  Especially height-wise...leave a little space next time.

* To cover the insides of the optical path holes, do it in 2 parts.  One half-cylinder, and then another.  Way easier than trying to do the whole thing at once.  Also, pre-cut the tabs on both sides of the foil before inserting.  Then you just have to grab the tabs with tweezers and flatten them, and they hold the aluminum tape in place. 

* Having 1" wide, 2" wide and 3" wide aluminum tape was handy.  3" to make the top, 2" for the sides, and 1" for the inside of the holes. 

[Micro, Den]

Analyzing coherence of seismic noise and mode cleaner length we've figured out that at some days the coherence below 1 Hz is still present. For example, at Nov 13 we can see some coherence compared to most other dates when we are not able to see coherence as shown on the figure. On the top plot - psd of MC_L and GUR1_X at Nov 13 (red and blue) and Nov 15 (black and cyan). On the bottom plot is presented coherence between MC_L and GUR1_X on Nov 13 (red) and Nov 15 (black)

We can divide the psd plot for 2 parts - below 1 Hz and above 1 Hz. Above 1 Hz seismic noise on Nov 15 (cyan) was higher then on Nov 13 (blue) and correspondently MC_L at that region was higher on Nov 15. Below 1 Hz seismic noise was higher on Nov 13 but MC_L is still lower that on Nov 15. That is surprising. From the coherence plot we can say that once we have some more seismic noise than usually, we immediately see coherence.

Because of this we wanted to find out the level of the X noise that makes seismic noise invisible. We injected seismic noise by doing smooth physical exercises near MC_2 (1.5 m and 3 m apart). The MC_2 was in lock during the experiment.

In the coherence plot we can see that coherence between GUR1_X and MC_L increased with noise injection. The highest coherenced we obtained sittind down and standing up smoothly near MC_2 at distance 1.5 m. We did not want to come clother and break the lock. This measurement tells us that the X noise is approximately 3-4 times higher than seismic noise in the range 0.1 - 1 Hz. That means that it is approximately 1e-6 - 1e-8 m/sqrt(Hz) in this region. This noise goes down at frequencies from 2 Hz and not seen because of seismic noise. Actually, seismic noise can be filtered out with the Wiener filter and then we'll see the spectrum of X noise.

We now try to figure out the method to estimate the contribution of OSEM noise to the X noise.

I found that the temperature controller of the PSL doubling oven had been disabled.

Is there an update on Stochmon?  Are the signals acquired somewhere already?  What's the current deal-io?  The new EOM mount should be here later today, and I'm jazzed to start checking how my EOM box helps (hopefully) the amount of RFAM we see. 

I'll start making the adapter plate while I wait...

I was measuring things to see how big my adapter plate needs to be, and I decided that we'd had enough days of the HEPA being on full blast, so I turned it down to 50, from 100.  I think it's been on full since Katrin was working on the Y-green beat a week or so ago.

The  Stochmon channels for 11&55MHz have been reasonably working since last night.

The output is not yet calibrated as the RF power detector has a strange scaling.
I am analyzing the calibration data.

I'm just on an elog roll this morning...

Again while poking around inside the IFO room, I noticed that they have replaced all of our incandescent lights with CFLs.  Do we care?  The point of having the incandescent lights on a separate switch from the big fluorescent lights was so that we could have only 60Hz lines, not wide-band noise if we want the lights on while locking. 

I'm not sure that we actually care, because more often we just turn off all the lights while trying to do serious locking, but if we do care, then someone needs to ask the custodial staff (or someone else?) to undo the change.

I have modified the 'mcwfson' and 'mcwfsoff' scripts to include the Clear History step for the MC2_TRANS_PIT and _YAW filters.  

These scripts can be run, by hand, from LOCKMC screen or from the WFS_MASTER screen.  Use the 'Turn WFS ON/OFF' button. 

The mcautolockmain script will now clear history on all ASC filter banks when the MC unlocks.

I have turned on ASC loops on the MC2_TRANS (= alignment transmission DOFs of the above elog) paths.

It turns out that we don't have all the parts I would need to do a full prototype of the precision temperature controller. I am guessing that we won't want to sit around and wait for the parts given the upcoming TAC meeting, so I'll do the next best thing:

• Standard DC temperature readout using an AD590.
• More-or-less complete heater driver

Does anyone have a suggestion for how this thing will be packaged? I.e., should it be in a box or should it be mounted in a rack, etc. In the end, a real board will be printed and stuffed, so this need not be a really professional job in the short term.

Our existing 300 series SS plungers from McMastercar #8476A43 are silver plated as Atm2 shows.

Problems:  1, they become magnetized after years being close to the magnets

                     2, they oxidize by time so it is hard to turn them

I looked around to replace them.

Titanium body, nose and beryllium copper spring. None magnetic for UHV enviorment.

Can be made in 7 weeks at an UNREASONABLE $169.00 ea at quantity of 50

Another go at the noise projection from MC1-3 pit/yaw to MC length. This time injecting into the MC autoalignment FB (e.g. C1:IOO-WFS1_PIT_EXC ).

LTPDA is working now, but still the NDS server is not so cooperative.

Summary: Alignment fluctuations of the MC mirrors don't significantly contribute to MC length changes up to at least 3.5Hz. Especially they can't explain the lack of coherence between seismometers and MC length below 1Hz that we worry about for the OAF.

At high frequencies >= 10Hz you can see angle to length coupling as is evident in Sureshes spot position measurements.

Whiteish noise injection:

Injection from 0.1-20Hz.Filtered by the servo filters and zp:[1],[1] , Gain = 1 @ 2Hz

Look at the coherence plots for the quality of the measurement:

Injection details:

DOF      Amplitude[counts]        UTC Time (duration always 4mins)
WFS1p  70                               22:28
WFS1y  55                               22:03
WFS2p  70                               22:13
WFS2y  70                               22:18
None      -                                 22:23

Fixed sine injections:

To get some better SNR at low frequencies I did a fixed sine noise injection at 0.3Hz. See attached files.

DOF      Amplitude[counts]        UTC Time (duration always 4mins)    Lower limit of SNR MC length via mirror misalignment
WFS1p  4                                  00:05                                                29.3
WFS1y  4                                  00:14                                                22.0
WFS2p  4                                  00:19                                                18.5
WFS2y  4                                  00:25                                                18.0

The Y arm green PDH servo is working fine with a sufficient amount of suppression.

(Servo filters)

  

And the servo configuration looks like this :

(the Error signal)

I took a spectrum of the error signal when the laser was locked to the Y arm and found that it meets the requirement.

The noise budget on the Y arm ALS has begun.

Right now the fluctuation of the green beat-note seems mostly covered by unknown noise which is relatively white.

(Though I feel I made a wrong calibration ... I have to check it again)

(Measurement condition)

[Koji, Suresh]

8:50PM HEPA@100% for the test

8:55PM HEPA@0%

9:20-35PM HEPA level varies from 0%-50%

9:35PM HEPA@40% and left it running at this level

Nov18 1:40 AM HEPA@80% for a work around the PSL table (by KI)

Nov18 4:35 AM HEPA@40% (by KI)

Analyzing coherence between MC length and signals on MC1, MC2 and MC3 coils we have noticed that MC1 COIL signal is not coherent to MC length at all at interesting frequencies 0.1 - 1 Hz.

We try to explain this phenomena.

MC is unlocked to measure the free swing of the MC mirrors with the local sensors.

Autolocker is disabled.

We've found that one of the  MC1_SENSORS does not work properly.

See the figure.

The most interesting plot did not uploaded in the previous elog.

Upload now local MC1_SENSOR signals.

 with script.

I modified the Y-Arm PDH box (S/N 17) to have the same TF as the one of the temporary setup described in Kiwamu's earlier entry. Note that the TF below was taken with the gain knob set to 0, so that the proper DC gain is achieved with a setting of ~4. This is desirable because it gives us wiggle room.

The changes were:

• R14: 25 -> 50
• R29: 1k -> 10.5k
• R30: 1k -> 20k
• R28: 102 -> OMIT
• C20: 84nF -> OMIT
• R31: SHORT -> 475
• R16: 10k -> 48.7k
• R24: 10 -> 5

Below is the TF along with the LISO model. They are different at low frequencies because the box must have been railing internally (though the phase shows that the result is as expected), and there is a feature around 60 kHz that probably arises from some op amp instability. I will see if adding a small cap somewhere does the trick, and then take a new TF with a lower source voltage.

I'll try to lock the arm with the box tomorrow.

[Den, Mirko, Suresh]

    We were investigating why there is no correlation between MC1 osem signals and seismic motion.   During this we noticed a recurrence of this old problem of MC1_LR sensor being dead.  I went and pressed down the chip holders where the AA filters used to sit and which now hold the jumper wire.  The board is large and flexible it is quite likely some solder joint is broken on the MC1_LR path on this board.

   The signal came back to life and is okay now. But it can break off again any time.

[Mirko, Den]

While the MC was unlocked (and the local damping off) we've measured the coherence between GUR1_X and OSEM sensors. It was rather high, close to 1 at frequencies 0.1 - 1 Hz. That means that stack does not kill all coherence between seismic noise and mirror motion.

Then we've turned on the local damping and measured the coherence again between GUR1_X and OSEM sensors. It decreased due to some noise and was on the level of ~0.5. We did reduced the motion between the mirror and the frame by local damping but it is not obvious that we lost some coherence due to this effect. Probably, actuator adds some noise.

When we locked the MC, we did not see any coherence at 0.1 - 1 Hz between GUR1_X or STS1_X and OSEM sensors of MC1 and MC3 but we did see with MC2. The MC1 sensor was fixed by Suresh.

Update of the stochmon status

[Attachment 1: Circuit diagram]

- The new stochmon has a low noise amplifier (MAR-6SM) inside.
The RFAM signal from the PD has the power of -60~-50dBm, which is almost at the bottom of the sensitivity for the power detector.

- The band pass filters were doubled.

- I've suffered from some RF coupling from the power line as the power detector is quite sensitive to it.
The situation has been largely improved by the EMI filters in the power supply path, although the problem is still present.
The worst remaining problem is that we can not close the aluminum lid as it cause a huge sprious coupling.

[Attachment 2: Calibration result]

- The outputs were calibarted with Marconi. They showed the signals linear to dBm for the input powers between -70dBm and -10dBm.

- The calibration result was fitted with the empirical fit function. The function and the results are shown in the attachment.

[Attachment 3: Detection limit]

- The attached figure shows the power spectrum of the PD output. This measurement gives us the amount of the RF power given from the PD noise when there is no RF signal.

11MHz out passband noise: −72.7dBm ===> V11 = 2.0483
30MHz out passband noise: −64.6dBm ===> V30 = 1.9333
55MHz out passband noise: −71.2dBm ===> V55 = 2.0272

- Now 11MHz and 55MHz outputs seem indicating the power correctly, but the 29.5MHz output never provides useful information.
It is a constant value independent from the state of the incident beam. Strangely this problem disappears if the marconi is used
for the RF source. Thus this issue is not seen in the calibration measurement.

- So far, 11MHz, 29.5MHz, 55MHz, and DC outputs appear in the channels C1:IOO-RFAMPD_33MHZ, C1:IOO-RFAMPD_133MHZ, C1:IOO-RFAMPD_166MHZ, and C1:IOO-RFAMPD_199MHZ.
They will be renamed.

[Suresh / Kiwamu]

 The power switch button of the RF generation box is not properly working

For tonight we are leaving it as it is but it needs to be fixed at some point.

(the Story)

The temporary solution we decided is to leave it ON so that we can survive tonight.

The box was back in place. The MC is find and 11 MHz and 55 MHz seem okay.

Please be aware of it.

This is a picture showing the rear view of the RF generation box. The red arrow is pointing the blue LED switch button.