What to do in case of Power CUT, How to restart the config (experts only):
A-Resart felixcore
- config felix: /det/dcs/Development/ATLAS_DCS_LAR/bin/Felix/configurationFelixScript_productionServer.sh
- start felixcore:/det/dcs/Development/ATLAS_DCS_LAR/bin/Felix/start.sh
B-Restart OpcUaSca server:
- if 1 or more link not answered: looks which link, which ltdb....
- source /det/dcs/Development/ATLAS_DCS_LAR/bin/tools/board_reset/setup.sh
- run
/det/dcs/Development/ATLAS_DCS_LAR/bin/tools/board_reset/reset_from_ltdb_position.sh with #wendy-port*
OR
/det/dcs/Development/ATLAS_DCS_LAR/bin/tools/board_reset/reset_from_elink.sh #elink number from the ltdb who died (in the felix log file)
- repeat if necessary
*How to find the #wendy-port:
- looks which elink is not connected
- Find in conf file the line of the elink definition that gives you the ltdb number
- Find which LTDB board is concerned (ex:WB_LTB_EMBC2) in the felix setup web interface
- and that gives the connector number (ex: 59(H07))
- In the wendy setup web interface, there is the #wendy-port you are looking for !!
D- Try config all LTDB if error all the time on:
before this change contact Florent
- Mtx => add it in the specific xml file in "degraded" mode => mapping/ltdbxxx/configFileLtdbxxx.xml
<!--?xml version="1.0" encoding="UTF-8" standalone="no"?--> <ltdb> <sca id='5'> <mtx id='4' mode='degraded'> </mtx> </sca> </ltdb><br />
<
--
DanieleLaugier - 2020-09-14