Ino explained: MOS was totally desynchronised with PLC. (It was assuming that the telescope was parked.) He parked the telescope manually. Thanks!
Experts will investigate on Monday. But the shift crews can continue to use the  Drive Control and tracking.

On park-in command, telescope went to the right position 95/-1, but did not recognise that it was there.

• Pushed Park-In again
• Acknowledged one error
• Then everything fine.

When checking the telescope visually outside, while it was in the "park-out" position, a car happened to pass by from the upper road (coming from the other telescopes). Its lights flashed directly into the camera. It seems that the road is in direct prolongation of our current park-out position.

• We saw the CAM HV going down several times in the park-out position (where the shutter is typically opened) during the last weeks. Can we change this standard position slightly (higher or lower)?
• Another question is of course, why cars drive with lights on in that place. The "no luz larga" sign is below the MAGIC site, if I remember correctly.

- CDM images at park out position.
Exposure 100ms.
OARL on.
Leds 255-200-150-100-50-25-10-1

- CDM image  Az=0 Zd=75-70-65-60-55-50-45-40-35-30-25-20-15-10-5-0
 exposure 100ms
OARL on
Leds On 255

Then we track serie of stars, all affected by clouds unfortunately

- Gamma Peg
- Markab
- Vega
- Altair
- Deneb
For each we took 1 image 100ms led/oarl on + 60 1s images led/oarl off
Then we moved by 2 deg on dark region at took 60 1s images
 

We found out a bug in drive repointing that was affecting the image quality in the first seconds after repositionning. It has been correct in drive SW.

Debugging of the tracking sequence :

• PLC sequence : trajectory tracking data correctly managed
• PLC tuning : regulation OK ==> need to refine.
• Tracking algorithm :
  • Changes in Drive.ccp to allow azimuth negative values.
  • Tracking duration : even by changing the duration of he tracking (from 1'to 5') ==> not correctly managed (still 1' tracking) ==> to be checked
•  

new session of high speed drive tests after issues with Power Supply.

• Tests of emergency stop (with a speed at 25% and 43 % GRB speed) with a modification of the jerk value from 0.08 to 0.2 ==> OK
• Tests of azimuth movements : (-90 to 270 degres)
  • at 60% of GRB speed. ==> Ok for 6 movements
  • at 80% of GRB speed
    • Ok for 4 movements
    • Failures due to resistance  (sur-tension). Breaking modules in failure then reset
    • Ok for 2 next movements
  • at 100% of GRB speed :
    • 3 movements from -90 to 90 ==> OK
    • Temperature of breaking resistance are getting very high (at least the top one) 

• 1 degree has been added to the Elevation accordingly to the last measurement given by Olger

• Different ParkOut and Parkin done with different values for testing the torque limitation. 
  • By decreasing the torque and the position , the parkin failed because we are not in the CSS locking sensor (in locking position)
  • By setting back the original values, th parkin is ok but the bolt cannot be properly inserted.

- During shutter tests, we were requested to move the telescope many times between two positions at different zenith. Sometimes, once the position is reached and in the log I got the message 'GoToTelescopePosition Done received', the command panel stay stack with the "action in progress" bar without possibility to perform other atctions. I need to click to 'general abort' to stop the action and  get the panel comand back. It happened 3 times

- During tracking, the message on the screen switch from "tracking in progress" to "action in progress, please wait..." The latter is quite misleading for non-familiar user of the gui.

We sent a tracking with with RA211,08 and DEC29,52

1st time the goto position of azimuth was sent at +42° and the trajectory requierts  -52° !!! (speed limit of the tracking 0,001 rad/s)

After a cancel the azimuth was sent at -54° !!!

Yesterday we had the same problem with the same RAD/DEC coordinates. -31° and after a cancel +270° !!!

Is it a problem of trajectory with the 1st point positionning or with this coordinates does we need a higher speed in tracking ?

When parking in the telescope, accidently hit "Shutdown" button instead of "Parkin" in Drive Semi-epert GUI. Nothing seem to happen for minutes despite telling command in progress "Shutdown"

Texted Drive experts, they told to just hit again the correct "Parkin" button.

Near the end of parkin in, procedure got stuck. Drive expert identified fuse Q21 having gone off. Switched back the fuse, acknowledged error, retried park in. Then, tower close. After expert intervention, did close and everything was fine.

After finishing the normal start-up procedure, we tried to park out by GUI, but got an error (22:30 local time): "MSG_WARNINGPark_Out_TimeOut"

The Drive, FSM and Command Statuses were "Parked", "in parking Area" and "No command in progress," respectively.

We closed&reopend the GUI and "Park Out" three times, but everytime got the same error.

We then send a message to the WhatsApp group of Drive experts (22:32).

Thierry asked us to restart the server on 10.1.8.3 and we killed the corresponding process (ps -ef | grep MOS), but the statuses didn't change (still FSM "in parking Area").

Thierry asked us to press the "General Abort" button, but didn't improve the situation.

After Ino's intervention (probably, we don't know detail), Thierry asked us to restart the GUI and we did so. The statuses got improved (Drive&FSM: Parked, Command: Started). So, we pushed the park out button, but the same error happend.

Ino suspected if the telescope wasn't unlocked by ALS, but we could visually confirm the ALSs unlocked the telescope properly.

Ino found the problem that "the Flywheel interlock says no motion allowed so PLC refuse to do Park out". He wanted to see the screen shot of Flywheel page. But, we could not connect to the server 10.1.200.1 which means the Flywheel PLC is probably down.

Daniel M. asked us to go to UC1 and we went there (23:45). After some discussion between Daniel and Ino, they asked us to try "stop" -> "run" -> "reset" in the PLC (lower white one, in the cabinet opposite side of the Flywheels). But, still there was no connection to 10.1.200.1 (also no two LEDs in the right side of the PLC turned on). See attachment 1, the LEDs were ON when it was working fine. Attachment 2 was taken tonight (the LEDs were OFF).

Daniel M. suggested us to close the shop because we need Koji's help to fix this problem (00:01).

Regarding the problem on the Flywheel PLC (see here), we entered UC1 under the supervision of Daniel M. and Koji (11:16 local time).

First we checked the LEDs of the black Ethernet cable. LINK in green was constantly ON and ACT in orange was blinking.

Then, we disconnected the black cable and reconnected again after 20 sec (11:30). But, the LEDs of the PLC in the right side were OFF.

Finally, we removed the two red power lines connected to the PLC with a screw driver and reconnected again (11:52). The LEDs of the PLC turned ON. The UC1 web page was back (12:08).

Drive GUI stacked due to a wrong shutdown procedure (Jul. 27th 01-02UTC). This was simply a human error.

First, we pushed ParkIn button as usual in the end of the night. We confirmed the telescope was in Locking Position in GUI, but most probably overlooked to check the statuses of access tower and CSS.

Next, we went to the drive container, turn the key into Service mode and pull it out. (Before get into the drive container, we saw the telescope in parking position, but apparently this inspection was not enough.)

Then, we visually found the camera shutter/SIS was not closed/put back (this was also our misoperation). BUT, at this time, we couldn't notice that access tower was open. (Since it was complete dark time, it was not clear to see even using a fully charged flash light.)

After closing/putting back the camera shutter/SIS (visually checked), we inserted the elevation bolt and locked the azimuth properly. Then, inserted the key back and went back to CC.

Finally, we found that the status of access tower/CSS was opened/unlocked. At first we though this was a bug of the GUI, so closed and opened the GUI, but (of course) it didn't change.

Then, we tried to push the parkin button after turning the key into Automatic mode, but the GUI didn't response. So, we contacted to the drive expert at this point (01:35UTC).

Ino asked us to visullay check the access tower and CSS (01:52UTC). After turning the key into Service mode, we confirmed that the CSS seemed to be locked but the tower was indeed open (02:00UTC). We turned the key into Automatic mode and got out the telescope area. Ino successfully locked and closed remotely (02:21UTC). We turned the key into Service mode and closed the shop.

Tuesday September 110th :

• Tests park-in and park-out to manage the different type of failures 
• Tests failure during park-in phase with a telescope in a position different from the park-out position
• Tests (from the Drive semi-expert GUI) to send the telecope to the parking area from any positions. Useful to close the camera shutter without parking-in the telescope.
• Night : tracking tests for fixing the shifhting issues : Problems with the PSF camera  

Wenesday September 11th :

• Night : Still tracking tests for fixing the shifhting issues. PSF camera OK. Many pictures taken. Small shifting not yet understood

Thierry&Ino on site

Ievgen, Vitalli and Jean-Luc remotely.

TCU tests to perform the parkin-in and park-out procedure from the Drive.

Results :

• Actions can be triggered from the TCU and correctly executed thru the ACS Drive Bridge-MOS-Drive PLC.
• Monitoring information is not correctly pushed from the bridge to the TCU (positions , ...)
  • Investigation brings many options. For the time being, a simple change in the ACS xml description will fix the problem. Anyway, this solution is not satifactory and a new solution will be implement asap.

Plans : Monday September 16th (2pm localtime) : new TCU tests to validate the intermediate solution for park-in, park-out and probably for some others action like Tracking,  GotoCircularPosition, ...

We tracked stars at various zenith angles and changed the Az and Zd offsets, taking images with the PSF camera for each position. After Armand's changes during the day the offset is the same for all Zenith angles.

Star Zd Az
dAz, dZd image

Polaris 61.5 0.7
0, 0 1568923765.fits
0.5, 0 1568923985.fits
0, 0.5 1568924088.fits
0.5, -0.5 1568924324.fits

Eltanin 29.2 327.9
0, 0 1568924558.fits
0.5, 0 1568924683.fits
0, 0.5 1568924747.fits

Benetnasch 66.6 314.7
Vega 15.6 313.8
0, 0 1568925023.fits
0.5, 0 1568925090.fits
0, 0.5

Kochab 57.3 342.0
Sulafat 8.7 299.5
0, 0 1568925265.fits
0.5, 0 1568925420.fits
0, 0.5 1568925485.fits

Alphecca 52.6 283.0
Arcturus 72.2 282.5
Oph Alpha-55 32.2 246.0
Albireo 1.2 229.1
0, 0 1568925734.fits
0.5, 0 1568925842.fits
0, 0.5 1568925917.fits

Nunki 55.8 190.6
Altair 20.2 168.3
Enif 35.7 115.2
Alpheratz 59.0 71.4
Caph 54.8 35.6
Deneb 21.2 33.9
Polaris 61.5 0.7

The aim was to observe several stars with different magnitude and check the sensitivity of the CDM. We wanted to use a semi-automatic procedure with command sent to the drive via a script to the Acs

After we realized that the telescope was not moving after a StarTracking command we try to use the drive system through the Acs server. StartTracking command not sent to the drive but the other commands (such as StopTracking) worked. 

Instead we used the Semi-expert Gui to make our test. All fine. list of stars observed:

AlphaAqr mag 3.11

10 images with LEDs and OARL

100 images + 100 dark

Homam mag 3.39

10 images with LEDs and OARL

100 images + 100 dark

48-peg mag 3.66

10 images with LEDs and OARL

100 images + 100 dark

24-peg mag 3.87

10 images with LEDs and OARL

100 images + 100 dark

47-peg mag 4.13

10 images with LEDs and OARL

120 images + 120 dark

17 And mag 4.26

10 images with LEDs and OARL

120 images + 120 dark

84Peg mag 4.69

10 images with LEDs and OARL

120 images + 120 dark

56Peg mag 4.91

10 images with LEDs and OARL

180 images + 180 dark

81Peg mag 5.13

10 images with LEDs and OARL

300 images + 300 dark

63 Peg mag 5.70

10 images with LEDs and OARL

400 images + 400 dark

85 Peg mag 5.87

10 images with LEDs and OARL

400 images + 400 dark

Few first images at 5s with LED @1