 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 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
|
|
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 |
|
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 |
|
Thu Feb 28 19:56:55 2019, Drive Team- Ino&Thierry, PLC Software and Configuration, , Tracking debug and setup,
|
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 |
|
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 |
|
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) |
|
Tue Feb 26 20:45:41 2019, Drive Team- Ino&Thierry, Telescope Operations, General, Tracking debug,
|
| Start of the tracking debug ==> PLC and MOS |
|
Wed Jan 30 15:43:12 2019, Drive Team, Telescope Operations, Software, Tests Tracking,
|
Tests and debugging of the tracking procedure. Many components are involved : PLC MOS GUIs.
Each component needs to be well debbuged to achieve a safe movement of the telescope
==> IN PROGRESS |
|
Mon Jan 28 15:27:35 2019, Drive Team, Telescope Operations, Software, Error Tests ,
|
Debugging of the "Parkout" sequence with errors ==>
MOS received the error and set the FSM in error state
User from
semi-expert GUI should acknowledge the error ==> MOS FSM acknowledge methosd is call (just authorized from the error state) to acknowledge the error
to the PLC.
PLC set up all the needed variables to inform the MOS and GUI of the result of the acknowlegment
Today, |
|
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 |
|
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 |
|
Fri Jan 25 12:39:52 2019, Drive Team, Problem Fixed, Hardware, Brakes issues fixed,
|
| The brake of the elevation issue has been fixed. Operations on drive can be resumed. |
|
Thu Jan 24 10:52:59 2019, Drive Team, Hardware, Issues, ,
|
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
|
|
Wed Jan 23 15:10:34 2019, Drive Team, Telescope Operations, Hardware, ,
|
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)
|
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
|
|
Tue Jan 22 15:55:25 2019, Drive Team, Software Installation, Software, TESTS Parkout Parkin,
|
Many parkin and parkout operations with different torque (with the clamping system of the access tower (from 18% to 8% = 26N/m). With 8%,
the locking position cannot be reached
Some minors have been corrected
|
|
Tue Jan 22 09:37:03 2019, Ino Monteiro, PLC Software and Configuration, Software, Installation new PLC version,
|
| Installation of the new PLC code and re-initilalisation of the system. |
|
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 |