-- RunaBriguglio - 08 Sep 2012

Communication lost with MOXA and ASM

compare: pinger.L.00001347085283.logmirrorctrl.L.00001347085285.log

pinger.L|INF|2591|2012-09-08 02:57:19.485545|MAIN > Host adam2sx: 0.586000 [ms]
pinger.L|INF|2592|2012-09-08 02:57:22.490495|MAIN > Host adamsx: 3.623000 [ms]
pinger.L|INF|2593|2012-09-08 02:57:22.490747|MAIN > Host adam2sx: 0.600000 [ms]
pinger.L|INF|2594|2012-09-08 02:57:25.493591|MAIN > Host adamsx: -1.000000 [ms]
pinger.L|INF|2595|2012-09-08 02:57:25.493872|MAIN > Host adam2sx: -1.000000 [ms]

mirrorctrl.L|ERR|288|2012-09-08 01:53:30.265506| BCUCOMMANDHANDLE > BcuCommandHandler::handleBcuRequest: REQUEST FAILED
mirrorctrl.L|ERR|289|2012-09-08 02:57:22.960489|MAIN > ****** FAILED PACKET FROM BCU 2 ******
mirrorctrl.L|ERR|290|2012-09-08 02:57:23.604546|MAIN > *******
FAILED PACKET FROM BCU 7 ******
mirrorctrl.L|ERR|291|2012-09-08 02:57:23.604640|MAIN > *******
FAILED PACKET FROM BCU 3 ******
mirrorctrl.L|ERR|292|2012-09-08 02:57:23.604699|MAIN > *******
FAILED PACKET FROM BCU 5 ******
mirrorctrl.L|ERR|293|2012-09-08 02:57:23.604753|MAIN > *******
FAILED PACKET FROM BCU 6 ******
mirrorctrl.L|ERR|294|2012-09-08 02:57:23.604864|MAIN > *******
FAILED PACKET FROM BCU 8 ******
mirrorctrl.L|ERR|295|2012-09-08 02:57:23.604925|MAIN > *******
FAILED PACKET FROM BCU 4 ******
mirrorctrl.L|ERR|296|2012-09-08 02:57:24.462534|MAIN > *******
FAILED PACKET FROM BCU 2 ******
mirrorctrl.L|ERR|297|2012-09-08 02:57:25.962562|MAIN > *******
FAILED PACKET FROM BCU 2 *******
mirrorctrl.L|ERR|298|2012-09-08 02:57:25.962614| BCUCOMMANDHANDLE > BcuCommandHandler::handleBcuReply: REQUEST COMPLETED but FAILED frown, sad smile

The power off does'nt seem to be due to a Watchdog, because the BCU are powered off before 1s after the moxa is not reachable.

moreover the sysrtem was found POWERED* when the telescope crew opened the cabinet. powered= LED on (we don't know if red or green, but as the BCU are not responding at that time this means that the main power supply is simply powered and OFF). this behaviour does'nt correspond to the watchdog one (when the system is powered of, it remains off)

the error could be due to high temperature inside the cabinet, causing the thermostat to open. when the temperature was ok, the thermostat closed and the power supplied was powered again (but the system is OFF of course)

MSGDB Errors

fastdiagn.L|INF|450|2012-09-08 15:39:40.004440|FAST > Processed10 cycles of 7624 vars in675 s (0.0148 Hz). HW frame rate 0.0133 [DiagnApp.cpp:838]
fastdiagn.L|INF|451|2012-09-08 15:39:40.004487|MAIN > Filtering for vars OFFLOADMODES [FastDiagnostic.cpp:1174]
fastdiagn.L|ERR|452|2012-09-08 15:39:41.036300|MAIN > [AOVarException] Error writing variable (code -5001) Timeout error File RTDBvar.cpp line 483Variable: ADSEC.L.OFLMODES (type REAL_VARIABLE, len 22)
fastdiagn.L|ERR|452|2012-09-08 15:39:41.036300|MAIN > .
fastdiagn.L|INF|464|2012-09-08 15:39:41.096804|FAST > Processed1 cycles of 7624 vars in1.09 s ( 0.915 Hz). HW frame rate47.6 [DiagnApp.cpp:838]
fastdiagn.L|ERR|465|2012-09-08 15:39:41.096872|MAIN > [AOVarException] Error writing variable (code -2010) Connection closed at the other end File RTDBvar.cpp line 483Variable: ADSEC.L.OFLMODES (type REAL_VARIABLE,

Optical Alignment

M3

-1135 25.0 0 sel -48.3

HP

4.87 -1.23 4.45 590 650 0

KL basis verification

the basis used is: /local/aomeas/adsec_calib/if_functions/20111210_pureKLs_01/full_m2v.fits.OLD
Tracknum modes amp
20120908_190320 0-49  
20120908_190438 50-99 100
20120908_190609 100-149 80
20120908_190745 150-199 70
20120908_190914 200-249 50
20120908_191035 250-299 50
20120908_191216 300-349 40
20120908_191353 350-399 40
20120908_191517 400-449 30
20120908_191644 450-499 30
20120908_191802 500-549 30
20120908_191928 550-599 30
20120908_192102 600-649 30
Topic revision: r4 - 11 Sep 2012, RunaBriguglio
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