Downtime in solar tower

Date Startup time W downtime AdSec downtime Notes
2009 09 17 30:00      
2009 09 18   Rerotator made wrong homing at startup.    
2009 09 21        
2009 09 22        
2009 09 23        
2009 09 24   12:50 WFS Arbitrator crashed 15:30 AdSec ripped when loading a flat

2009 09 25 9:12 WFS board set up failure   There are many devices not connected:
error message: " s = setupDevices.get()

s.setup( self, ["flowerpot", "lamp", "cube"], parallel=True)
([], '')
self.fw1.moveTo(0.999974)
Error:
Controller in wrong state for requested operation. - code: -11005
2009 09 25 9:21 WFS start up,problem with the flower pot  

pyarg00

ALW 128 2009-09-25 09:17:38.114228 MAIN > Turning on flowerpot
0
Error: Operate failed System exception: unsubscriptable object
pyarg00
ALW 129 2009-09-25 09:18:38.146102 MAIN > System exception: unsubscriptable objectFault loading the board set up:

2009-09-28

9:00

____

____

14:23

 

Secondary cooling problem
____
Secondary RIP when opening/closing the loop

______
Disk filled. 100% by secondary logs.

cooling proble, it was necessary to bypass the system with the backup system.Restart the system at 11:00

After trying to move the heaxop, we noticed that the hexapod didn't move, checking the fastdiag we see that the system is stopped at 14:23. The disk logs files are removed by hand to

2009 09 29 9:30     IRTC startup failre. Reboot controller.
2009 09 30 10:49 wfs sec fault saving slopes from the secondary. bin3 freq:200Hz..... check the bcuLUT
2009 09 30 11:05   sec RIP during the intmat acquire. skip Recover worked
2009 09 30 12:30 wfs   RIP the secondary, this fault came from the reset of the BCU46 which is doing a continous reseting, this effect power off the camera lens and this problem affects the close loop procedure
2009 10 01 12:00 irtc   broken fiber link, the fiber is changed for a new one. time lost 30'
2009 10 01 12:30 wfs   detected channel 3 of the tt not working. the W unit is off and on at 18:30. Not observation
2009 10 02 9:30     NETWORK PROBLEM. restart:10:30
2009 10 02 10:30   sec fast link not connected.
2009 10 02 11:30   SEC Using the OSS to communicate with the hexapod. This is showing a fault with the link with the UMAC. time lost
2009 10 06     sec the secondaryhas done an startup ok, but afte 30 minutes has enable the coils (RIP), tried to bring up the secondary with a continous fault. time:7:30--->13:00
2009 10 13 10:00 wfs   close the loop, The loop doesn't close properly, the system said that the loop is closed BUT the master diagnostic gives an error message : MASTDIAGN01 WAR 6160 2009-10-13 10:16:40.434839 OPTICAL-LOOP > Wrong filotto. Frame skipped.
20091014 10:30 wfs sec the system don't close the loop, seems a problem with the message deamon in the secondary..
20091104 10:00 all morning all morning WFS msgd failure. AdSec msgd failure. TCS spontanous reboot. IRC single frame not working. Hexapod stuck, needs reboot.
20091105 10:00 wfs sec WFS msgd failure. AdSec msgd failure

2009 09 29     10:18secondary rip the secondary RIP applying a close loop. 2009 09 29 10:18   secondary rip the secondary RIP applying a close loop.   2009 09 29   14:30 MSGD crashed     2009 09 29 17:31   secondary RIP the secondary RIP after applying a close loop at bin 2.nothing has been change from previous working close loop
Topic revision: r26 - 05 Nov 2009, JuanCarlosGuerra
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback