 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
|
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
|
|
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)
|
|
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
|
|
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. |
|
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 |
|
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, |
|
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 |
|
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". |
|
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 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:
|
|
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 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 |
|
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 |
|
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 |
|
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 |
|
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 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 |