 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 |
|
Thu Jan 16 22:06:39 2020, tions applied to solve this issue :Martin Will, Thierry Le Flour, Telescope Operations, Software, Semi-Expert Drive GUI not connecting / MOS server not working, Fixed
|
In the late afternoon shifters noticed the semi-expert drive GUI was not updating, several restarts did not help. Checking into the issue with the drive
team connecting from remote it was found that the MOS server is not running and cannot be restarted. This issue could not be solved and will be revisited
tomorrow, Jan 17, during the day. |
|
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 |
|
Wed Nov 27 21:27:29 2019, Mathieu David Armand, Telescope Operations, , CDM & SG images with alternative target,
|
Test of alternative grey target for the OARL
|
|
Tue Nov 26 21:37:03 2019, David Sanchez, Armand Fiasson, Mathieu De Bony, Telescope Operations, , CDM bending model image 26-11-2019,
|
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 |
|
Mon Nov 25 22:53:22 2019, Mathieu David Armand, Telescope Operations, , CDM images 19/11/25,
|
Mg=1.25
DenebDark 60x1s RA-2
TestTracking 60x1s Displacement from Deneb RA-2
Deneb 60x1s
DenebLed
10x20ms Led On OARL On
Zd~32
Mg=3.65
OmiAndLed Led Lasers On 10x20ms
OmiAnd
60x1s
OmiAndDark Ra-2 60x1s
Zd~14
//====== Not good
Mg=4.75
KsiPegLed |
|
Sun Nov 24 19:33:56 2019, Mathieu David Armand, Telescope Operations, General, CDM images for bending model,
|
- CDM images at park out position.
Exposure 100ms.
OARL on. |
|
Thu Sep 19 19:10:39 2019, Martin, Ino, Thierry, Quentin, Thomas, Tracking Debugging, , Star images with various Az and Zd offsets,
|
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 |
|
Mon Sep 16 08:59:41 2019, Drive Team- Ino&Thierry + Ievgen + Vitalii + Jean-Luc, PLC + Control Software debugging, , Test TCU<->Drive,
|
Thierry&Ino on site
Ievgen, Vitalli and Jean-Luc remotely.
TCU tests to perform the parkin-in and park-out procedure from the Drive. |
|
Thu Sep 12 16:41:53 2019, Drive Team- Ino&Thierry, PLC + Control Software debugging, , ,
|
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 |
|
Sat Jul 27 11:11:08 2019, Yusuke, Satoshi, Tomo, Yoshiki, Other, , GUI stacked due to a wrong shutdown procedure,
|
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 |
|
Tue Jul 23 13:50:43 2019, Yusuke, Patricia, Problem Fixed, , Reboot Flywheel PLC,
|
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. |
|
Mon Jul 22 23:07:20 2019, Yusuke, Daniel K., Mitsunari, Satoshi, Tomo, Juan Abel, Yoshiki, Telescope Operations, , Flywheel PLC down,
|
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. |
|
Fri Jul 19 23:06:13 2019, Mitsunari, Tomohiro, Satoshi, Moritz, Yusuke, Telescope Operations, Issues, Telescope stuck in strange state/lost control by Semi-Expert GUI,
|
Tonight, we tracked Vega to test (a correction of) the pointing offset of the Drive.
Around 22:30UTC, we tried different Az offsets of the pointing in the Semi-expert GUI, followed by taking an image with the PSF camera to see
the effect of the offset choice. |
|
Tue Jul 9 00:46:52 2019, Mitsunari, Yukiho, Noah, Moritz, Telescope Operations, Issues, Park-in problems,
|
At parking in, the telescope got stuck at 94.254°. We checked in the container that fuse Q21 went off. We did not see any errors both in the Drive
cointainer and the GUI. We texted the experts. After 15 minutes, we pressed again "ParkIn" (without having touched the fuse). After nothing happend
in the GUI, we called the experts. They authorized us to switch back the fuse. After that, still heavy intervention by the experts was needed, who finally |
|
Sat Jul 6 23:17:54 2019, Moritz, Dirk, Telescope Operations, , Park-in problems,
|
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. |
|
Sat Jul 6 22:47:38 2019, Dirk Hoffmann, Telescope Operations, General, Car flash from road above+,
|
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 |
|
Fri Jul 5 23:23:57 2019, Dirk, Moritz, Telescope Operations, General, Park-in report,
|
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.
|
|
Fri Jul 5 08:58:42 2019, Dirk Hoffmann, Problem Fixed, Software, Small problem with park-in,
|
When parking in yesterday, the telescope drove to the nominal position (approx. 95° zenith angle and -1° azimuth), but then it took a long time
and never showed the "park out" button again.
In the driver container, we saw two alerts to acknowledge, then the GUI indicated "telescope parked". We confirmed visually that the |
|
Wed Jul 3 21:02:09 2019, Dirk, Taka, Mitsunari, Yukiho, Noah, Telescope Operations, Issues, Feedback from shiftcrew,
|
(For Thierry with love <3 :-)
The semi-expert drive control panel uses various terms for the zenith angle: "Altitude (zenith angle)", "Elevation", "Angle".
"Zenith Angle". |
|
Tue Jul 2 21:25:07 2019, Dirk Hoffmann, Applications, Software, Current & Power Monitoring stuck ("Socomec display"),
|
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. |
|
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. |
 Fri Jun 28 23:06:36 2019, Dirk Hoffmann, Telescope Operations, General, Telescope stuck,
|
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.
Quote:
|
|
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 |
|
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 |
|
Wed Jun 26 20:06:22 2019, Ino, PLC + Control Software debugging, , Tracking Trajectory,
|
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) |
|
Thu May 30 13:18:04 2019, Alessandro, Telescope Operations, , semi expert gui (marginal) issues,
|
- 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 |
|
Fri Apr 26 23:17:07 2019, Alessandro for the drive team, Telescope Operations, Issues, drive tracking issue,
|
We encountered a couple of issue with tracking
- When we tried to track on polaris coordinates (RA: 37.946143deg Dec: 89.264138 AzOff=0.261 ZdOff=-0.359) the telescope started
to move toward the east relatively fast (roughly ~5deg in less than 1 min) while it was supposed to basically stay on place. Some ephemerides evaluation |
|
Thu Apr 18 21:21:25 2019, Drive Team- Ino&Thierry&Alessandro, Telescope Operations, Hardware, Elevation limit switch issue,
|
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) |
|
Thu Apr 18 21:07:20 2019, Drive Team- Ino&Thierry&Alessandro, Telescope Operations, , TESTS Parkout Parkin for fixing the bolt issue,
|
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.
|
|
Thu Apr 18 09:10:29 2019, Ino, PLC Software and Configuration, Hardware, Offset of the Zero Azimuth,
|
After pointing Polaris yesterday, it seems that the zero position of the telescope was incorrect but It's never had been calibrated (zero was equals
to parking position towards center of tower).
So I shift the zero position of telescope by 0.869°. |
|
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
|
|
Tue Apr 16 14:34:22 2019, Drive Team- Ino, Telescope Operations, Hardware, Cabling the azimuth end switches,
|
Cabling the azimuth end switches.
|
|
Tue Apr 16 10:10:55 2019, Drive Team- Ino&Thierry, PLC Software and Configuration, , Elevation setup,
|
1 degree has been added to the Elevation accordingly to the last measurement given by Olger
|
|
Mon Apr 1 07:43:23 2019, Drive Team- Ino&Thierry&Armand, Problem Fixed, Hardware, LST Parking control,
|
On Wenesday morning (27/03/19) :
With Holger and Robert (MPI) , many telescope "park in/park out" operations have been
performed in order to refine the positionning in the acces tower and at the elevation locking bolt
Holger and Robert applied many mechanical modifications on the acces tower to make the telescope park operations very smooth |
|
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
|
|
Thu Mar 28 10:34:41 2019, Drive Team- Ino&Thierry&Armand + Juli (IFAE), Telescope Operations, , High speed drive tests,
|
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 |
|
Fri Mar 8 09:25:22 2019, Drive Team- Ino&Thierry&Armand, PLC + Control Software debugging, Software, Tracking debug and setup,
|
Tracking procedure has been debugged from the GUI-MOS (OPCUA Server with tracking plugin)-PLC
Still some improvments to apply
but globally the procedure is running well.
|
|
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.
|
|
Wed Mar 6 16:30:56 2019, Drive Team- Ino&Thierry&Armand, PLC + Control Software debugging, Software, Tracking mode debug,
|
Debugging of the MOS plugin corresponding to the tracking
|
|
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
|
|
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 |