Experts Only

For testing the new latome fw, just change the link to the latome fw...

EMF:

for example LATOME_FW-v3.2.0_rc3 on latome #16

  • /localdisk/OPC-PROJECTS/OpcUaLarLtdbServer/latome -> ../commonlink/LATOME_3_2_0_rc3
  • with /localdisk/OPC-PROJECTS/commonlink/LATOME_3_2_0_rc3 -> /afs/cern.ch/work/l/lardaq/public/detlar/firmware/LATOME/LATOME_FW-v3.2.0_rc3/LATOME/release/fw-48ch-48ch/compilation/latome_hw/emf/release/registers/
  • launch OpcUaLtdbServer
  • launch GUI and configure the LTDB
  • check OpcUaLtdbServer log to see if there is something wrong
scan Locx2 (expert mode) => If the scan of the locx2 was bad, check on latome with the program firmwarectrl the latome status...if the status is bad, it's a latome issue.
For example:
pc-emf-fw-03:
  1. cd /det/lar/project/firmware/LATOME/LATOME_FW-v3.2.0_rc3/LATOME/projects/firmware
  2. ./shell.latome.sh 16 => 16 is the #latome,
  3. check on istage status (live)the channels
  4. resetting counter => menu on top of the screen of istage status...you should see no error and stable calibration

P1:

There is one configuration per felix server that specify with latome on which felix server: config-felix-ltdb-00 config-felix-ltdb-01 config-felix-ltdb-02

example: use pc-lar-felix-ltdb-00 ==> config-felix-ltdb-00 ==> change the path of the latome version in connection_latome.xml for each line

<!--?xml version="1.0" ?-->
<connections>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.99" uri="ipbusudp-2.0://aam-lar-latome-099:50001"/>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.100" uri="ipbusudp-2.0://aam-lar-latome-100:50001"/>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.101" uri="ipbusudp-2.0://aam-lar-latome-101:50001"/>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.102" uri="ipbusudp-2.0://aam-lar-latome-102:50001"/>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.136" uri="ipbusudp-2.0://aam-lar-latome-136:50001"/>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.137" uri="ipbusudp-2.0://aam-lar-latome-137:50001"/>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.138" uri="ipbusudp-2.0://aam-lar-latome-138:50001"/>
<connection address_table="file://../latome_32_rc3/registers.xml" id="latome.139" uri="ipbusudp-2.0://aam-lar-latome-139:50001"/>
</connections>
<

with

/det/dcs/Development/ATLAS_DCS_LAR/bin/OpcUaLarLtdbServer/latome_32_rc3 -&gt;../common/latome.3.2.0_rc3    

  • launch server terminal dcs and configure the LTDB (open a Remote Desktop on the cerntsatldcs(cerntsatldcs.cern.ch) and make the next 5 steps described in the P1 )
  • check OpcUaLtdbServer log to see if there is something wrong

-- DanieleLaugier - 2020-09-16

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2020-09-16 - DanieleLaugier
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback