Add new latome
cd /det/dcs/Development/ATLAS_DCS_LAR/bin/OpcUaLarLtdbServer/configs/latomes
vi latome_<num_pc>.xml
add new latome thanks to it number <connection address_table="file://../../latome/registers.xml" id="
latome.XXX
" uri="ipbusudp-2.0://aam-lar-latome-XXX:50001"/>
Replace the fake latome_50 by a real one
cd /det/dcs/Development/ATLAS_DCS_LAR/bin/OpcUaLarLtdbServer/mapping/ltdb<num ltdb>
vi mapping.txt :%s/50/<num latome>/g
Restart
OpcUaLar
On the FSM
Disable other card thank to GUI main panel (keep only the quadrant you need) Do a power off on your quadrant Go on your first ltdb do :
- Power on
- Init
- Mapping→Generate Mapping (check log of OpcUaLar)
cd /det/dcs/Development/ATLAS_DCS_LAR/bin/OpcUaLarLtdbServer/mapping/ltdb<num ltdb>
vi mapping_generated.txt -> check the file and delete the first line
for the fiber which are no connected put 49
mv mapping_generated.txt mapping.txt
Check if the mapping is good
Do :
- Shutdown
- power off
- power on
- init
- mapping→Check mapping
Before do the next mapping think to power off this ltdb
OLD
Take care:
- This functionnality of the OpcUaLarLtdbServer is still is development, use it at you own risk
- The LTDB must be configured before any use and all channels at DATA_MODE
- The configuration of the LTDB is lost durig the process
ssh -X lardcs@pcatllarltdb
cd /afs/cern.ch/user/l/lardcs/public/etfortin-peripheral/OpcUaLarLtdbServer
./tail_last.sh
/!\Don't close the logs, now they are the only way to now if the mapping generation is a success
Configure Latome on with reorder 1 to 1
There is a option in the latome firmware control under istage
Launch the pannel:
On a different terminal
ssh -X lardcs@pcatllarltdb
WCCOAui -proj ATLLARLTDB -p Mapping.pnl &
Use the pannel:
Just click on "Generate Mapping"
All other functions are useless
On the logs you will see a lot of lines with begin with:
2019-07-31 15:31.41.486427 [DMapping_functions.cpp:605, INF] -----Reload of adc ID for ADC:80-------
It's normal it's the initialization of the theoric mapping and LATOME connexion
After ~10s
2019-07-31 15:31.49.272197 [DMapping_functions.cpp:177, INF] Ltdb_fiber Latome_fiber
2019-07-31 15:31.49.272303 [DMapping_functions.cpp:179, INF] 1 48
2019-07-31 15:31.49.272370 [DMapping_functions.cpp:179, INF] 2 47
...
...
Here if on each line if Latome_fiber is -1 it's an error Latome side.
IS not the generation fiber to fiber is finished and the server will begin to generate it for SC, you will have this line:
2019-07-31 15:31.49.338207 [DMapping_functions.cpp:257, INF] mapping Istage for channel:1
After it will show the results:
2019-07-31 15:32.28.612016 [DMapping_functions.cpp:276, INF] 319 3 7
2019-07-31 15:32.28.612057 [DMapping_functions.cpp:276, INF] 320 3 8
When you see for SC 320 it's good.
You can close the logs.
The results are under:
- mapping_generated.txt
- mappingSCIstage_generated.txt
--
EtienneMarieFortin - 2019-07-31