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.

We then send a message to the WhatsApp group of Drive experts (22:32).

Thierry asked us to restart the server on 10.1.8.3 and we killed the corresponding process (ps -ef | grep MOS), but the statuses didn't change (still FSM "in parking Area").

Thierry asked us to press the "General Abort" button, but didn't improve the situation.

After Ino's intervention (probably, we don't know detail), Thierry asked us to restart the GUI and we did so. The statuses got improved (Drive&FSM: Parked, Command: Started). So, we pushed the park out button, but the same error happend.

Ino suspected if the telescope wasn't unlocked by ALS, but we could visually confirm the ALSs unlocked the telescope properly.

Ino found the problem that "the Flywheel interlock says no motion allowed so PLC refuse to do Park out". He wanted to see the screen shot of Flywheel page. But, we could not connect to the server 10.1.200.1 which means the Flywheel PLC is probably down.

Daniel M. asked us to go to UC1 and we went there (23:45). After some discussion between Daniel and Ino, they asked us to try "stop" -> "run" -> "reset" in the PLC (lower white one, in the cabinet opposite side of the Flywheels). But, still there was no connection to 10.1.200.1 (also no two LEDs in the right side of the PLC turned on). See attachment 1, the LEDs were ON when it was working fine. Attachment 2 was taken tonight (the LEDs were OFF).

Daniel M. suggested us to close the shop because we need Koji's help to fix this problem (00:01).