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

The 2 swicthes are too far from the target at 56.48 elevation.  The sensor have been tuned in parkin position and the distance was correct (2mm) and at 56.48 is about 10mm. (impossible to tune correctly the sensor and the atrger has to be tuned)

Many parkin operations done. To confirm the different movements , a Parkin test with a azimuth position 20 and Elevation 70.

This is to validate the complete "Parkin" scenario with "random" az and el positions

• The FW issue is not solved . No movement can be done
• The FW is going to be restarted ==> It takes several hours to put it down and up again
• Drive movement are stucked 

The Current&Power Monitoring was not updated and hidden by two emtpy modal dialogue windows.

Restart of display (via icon on desktop) not successfull. ("MODBUS #2 communication failed.")

Called expert (ThLF), who advised how to call the old instance, then restart worked.

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.

• Cabling the azimuth end switches.

- 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.

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

The brake of the elevation issue has been fixed. Operations on drive can be resumed.

• To define precisely the correction to apply to Azimuth positionning, a set of movements have been done to calculte the correction coefficient.
• A scan from 0 deg. to 270 deg. with a step of 10 deg. and a reverse scan from 270 deg. to 0 deg. with a step of 50.deg realized to have a better approximation

Last week we put in sevice the new ALS completly modified:

_ Main System with new reducer.

_ New Speed parameters for Main System (motor is at full speed but due to reducer the spped is slow). Decceleration sensors not installed since the speed is very slow.

_ All the sensors were replaced by new ones (2 logic embedded in each sensor (NC + NO) ) = only one type of sensor in the ALS. Sensor with connector to ease maintenance.

_ All sensor cabling were changed and new ducts were installed to ease maintenance.

_ The damaged cable of the loadcell was welded again and protected (Heat shrink tube + tape).

_ Add mechanical part to protect loadcell cable when opening over the opening position. It's now impossible to damage Loadcell cable.

_ Increase speed of plier. We add a deceleration sensor in each plier.

_ All the sensors support are new to avoid dammage if there is over position due to manual operation.

The ALS is now functionnal with human interface. The system are so slow 180s !!!, They were not integrated into automatic cycles.

Shifters must manage the Opening/Closing of the ALS at the Start/End od telescope operations.

A new error code is ride up if a door is opened during motion (3002).

During a park-in action , the acces tower did not close correctly.

On Dec 6, Dario, Frederic and Yuji showed to Koji Noda and Daniel Mazin how to operate the new ALS. The idea was to do an unlock and lock again, as the weather was still bad. The automatic part went more or less OK ending in error state (excpected). We then went to EAST ALS to open the main actuator manually. After moving the actuator manually, the status of the ALS was either locked not unlocked. We realized that secondary sensor for South part was reacting incorrectly (close to metal OFF, far from metal ON), and we thought it is the reason. We removed the endswictch screw but the status did not change. After pressing again Unlock we realized that the secondary South plier squeezed the sensor cable and destroyed it (see Attachment 1). We consulted Ino and closed the ALS EAST manually (all three actuators) because the eather was getting worse.

Next day, Dec 7, we (Daniel and Koji) examined the sensor cable and confirmed it is completely distroyed. We introduced a patch cable and few adapters as a temporary repair (See attachements 2,3,4 and 5). We confirmed the reading of the pressure of the South and North sensors of teh secondary pliers are good again (attachment 6). See pictures.

Emergency stop applied because of a azimuth value(encoder) not in the pre-defined range +-0.015

• first parkin ==> Azimuth 0.013 ==> Emergency because offset even if in the correct range
• 2nd parkin ==> Azimuth 0.004 ==> Emenrgency stop because offset not in the correct range (eye control not drive control)

After issues during the parkin procedures ( 100% elveation torque ) :

• a visual inpsection has been done :  access is not involved , 2 possible causes :
  • rolls on elevation structure because they are rolling (4 of them yes , 4 of them not)
  • motor break ==> under investigation

During this 2 weeks we solve this problems:

_ Park In: Sometimes the final locking position was too limit and the "In Position" sensor was lost

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