 Sat Dec 7 19:16:01 2019, Daniel Mazin, Koji Noda, Hardware, Hardware, ALS East: problem and preliminary solution, 6x
|
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 |
|
Mon Feb 10 14:57:56 2020, Ino + Gael + Thierry, Other, Hardware, Azimuth Locking System , Fixed 14x
|
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 |
|
Fri Jan 18 10:14:51 2019, Thierry Le Flour, Software Installation, General, Initlisation of the DRIVE logbook,
|
| Here is the first entry in the DRIVE ELOG logbook |
|
Wed Jan 23 11:26:29 2019, Drive Team, PLC Software and Configuration, General, Azimuth tuning ,
|
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
|
|
Fri Jan 25 14:12:28 2019, Drive Team, Telescope Operations, General, Drive Movement : PArkin and Parkout,
|
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 |
|
Sat Jan 26 09:49:34 2019, Drive Team, Telescope Operations, General, Goto Position tests,
|
Many differents succesfull "goto position" operations ... MOS configuration file (XML) modified to aplly to correct Azimth and Elevation
ranges for secure movement
GotoPosition azimuth range : [-126..354]
GotoPosition elevation range : [0..75]
FastGotoPosition azimuth range |
|
Tue Feb 26 20:45:41 2019, Drive Team- Ino&Thierry, Telescope Operations, General, Tracking debug,
|
| Start of the tracking debug ==> PLC and MOS |
|
Tue Feb 26 20:47:15 2019, Drive Team- Ino&Thierry, Telescope Operations, General, Polaris point for mirrors aligment,
|
Pointing to polaris ==>
Azimuth = 0.808
Elevation = 59.941 + 1 degree (correction) |
|
Wed Feb 27 20:33:17 2019, Drive Team- Ino&Thierry, Telescope Operations, General, Polaris point for mirrors aligment,
|
| Same operations as yesterday ==> pointing to Polaris with the same coordinates |
|
Thu Feb 28 20:01:44 2019, Drive Team- Ino&Thierry, Telescope Operations, General, Polaris point for mirrors aligment,
|
| Same operations as yesterday ==> Polaris position |
|
Tue Mar 5 14:42:22 2019, Drive Team- Ino&Thierry, Telescope Operations, General, High speed drive tests,
|
. Fisrt day of the high speed drive tests with IFAE team.
Tests for tuning and generating motor plots at 10% (0.0234 Rad/s) of the maximal speed (GRB alert speed)
Tuning of the
emergency stop from 0.05 Rad/s2 up to 0.2 Rad/s2
6 movements at 25% speed. (from -90 to 270)
repositionnning to -90 at 40%
movements |
|
Wed Mar 6 10:54:33 2019, Drive Team- Ino&Thierry&Armand, Telescope Operations, General, DRIVE : High Speed tests,
|
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
|
|
Wed Mar 6 14:58:51 2019, Drive Team- Ino&Thierry&Armand, Telescope Operations, General, Access tower failure,
|
| During a park-in action , the acces tower did not close correctly. |
|
Wed Mar 6 15:33:14 2019, Drive Team- Ino&Thierry&Armand, Telescope Operations, General, Test High Speed Drive,
|
Test at 60% maximal speed from -90 to 0
Check of the FW discharge : No error (FW 2 : 95% FW1 : 100%)
Test
at 60% maximal speed from -90 to 270
Check of the FW discharge ==> Error (FW 2 : 90 % FW1 : 100%)
Drive stops at 250
degree.
Power consumption = 60kw
|
|
Fri Mar 8 09:20:29 2019, Drive Team- Ino&Thierry&Armand, Telescope Operations, General, High speed drive tests,
|
On Thrusday :
new movements at 45% from -90 to 270 have been done.
No possible movement at 60% because the FW and UPS
issues are not solved yet
Ino will back on site when HITACHI team will be on site for FW maintenance
Tests at 60% will
be done to validate (or not) the correction applied by Hitachi team.
|
|
Mon Apr 1 07:36:04 2019, Drive Team- Ino&Thierry&Armand, Telescope Operations, General, Tracking debug and setup,
|
Regulation of the motors (PID) for slow and fast tracking and motor oscillations.
Implementation and Debugging of the Semi-Expert
control software for the drive.
GUIs + MOS plugin (OPCUA Server)
Results are quite encouraging in good wheather
condiftions.
additionnal tests in different (wind) conditions are envisaged to validate completly the process
|
|
Wed Apr 17 21:26:13 2019, Drive Team- Ino&Thierry&Alessandro, Satoshi, Telescope Operations, General, Tracking for mirrors alignment,
|
Tracking at position :
RA = 101.288541 RA Offset = -0.6
DEC = -16.71343 DEC Offset = 0.7
|
|
Thu Jun 27 12:04:43 2019, Ino, Problem Fixed, General, ,
|
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 |
|
Thu Jun 27 12:19:02 2019, Ino, Problem Fixed, General, PLC Status,
|
During this weeks we solve this problems:
_ Park In: Sometimes the final locking position was too limit and the "In Position" sensor was lost during the locking witch put the
sytems in bad state vs safety constaint (we can't unlock if the sensor In Position is not active). So now the final poition is now adjusted dynamically |
|
Fri Jun 28 22:49:39 2019, Dirk Hoffmann, Telescope Operations, General, Telescope stuck,
|
After tracking Mk421, we abort current action (acknowledged) and try to go to a new source: RA=308.1, Dec=40.96. Drive Control refuses these parameters
("check your parameters").
General Abort without effect for 2 minutes. Called expert (Ino). He will look into it. |