WinCC Notes

Introduction

The WinCC projects are in the bgvctrl machine and the bgvopc machine.

  • Start the project administrator: $ startPA
    • bgvctrl
      • BGV : Basic detector usage
      • DCS : HV & LV edit/control
      • HLT : ?
      • TFC : ?
      • LHC : ?
    • bgvopc
      • BGVOPC : OPC server for CAEN control.
      • If server is stopped (e.g. machine restart), then most possibly will not be able to restart, as the time of the bgvopc machine needs to be synced with bgvcltr. Not being connected to TN, the bgvopc will loose sync.
      • For that purpose, Colin has installed Dimension 4 for time sync, but ofc it requires internet connection.
      • So the principle should be (?) to periodically connect the bgvopc machine to the network manually from the service area (!?). Is there a way to control this from some of the switches ?
      • What I did was simply to reset time by checking it with bgvctrl machine

  • To start the panels:
    • $ WCCOAui -proj BGV -p fwDeviceEditorNavigator/fwDeviceEditorNavigator.pnl &
    • $ WCCOAui -proj DCS -p fwDeviceEditorNavigator/fwDeviceEditorNavigator.pnl &

DAQ Runs

Physics Run
  • BGV_TOP Panel:
    • Activity: PHYSICS, Nr.Events: e.g. 30.000, Automated Run with Steps: 1
  • BGV_TFC / TFC_PART16 Panel:
    • TFC Functions: Auxiliary trigger must be by default enabled.
    • Apply Enables
  • BGV_TFC / TFC_PART16 / tfcodin16 Panel:
    • Check *L0 latency*=114, should be by default

Pedestal Run
  • BGV_TOP Panel:
    • Activity: PHYSICS, Nr.Events: e.g. 30.000, Automated Run with Steps: 1
  • BGV_TFC / TFC_PART16 Panel:
    • TFC Functions: Enable only Random Triggers, Trigger type brdcst
    • Apply Enables
  • BGV_TFC / TFC_PART16 / tfcodin16 Panel:
    • Triggers 1 tab, Random Trigger box, set Random Rate, e.g 0.5kHz
    • Apply Enables

Important Note Pedestal run should be made with both SiPM bias (BGV_HV) ON & OFF The values on the CondDB are from SiPM HV OFF.

Turning SiPMs OFF for the Run

  • From BGV_TOP, change BGV_HV state to GO_OFF
  • To the right of the state indication of BGV_HV there is a lock.
  • Press it, choose Exclude
  • System should now be able to go to state READY in order to run.

Pulse Shape Scan Run
  • BGV_TOP Panel:
    • Activity: PULSESHAPESCAN, Nr.Events:*e.g. 1.000, *Automated Run with Steps: 26
  • BGV_TFC / TFC_PART16 Panel:
    • TFC Functions: Enable only Timing Triggers, Auxiliary Trigger, Trigger type brdcst
    • Apply Enables
  • BGV_TFC / TFC_PART16 / tfcodin16 Panel:
    • L0 Latency: 112 (the latency should be your known good l0 latency minus the amount of TAEs set in the top panel, e.g. goot latency = 114, TAE = 2 -> PulseShapeScan l0Latency = 112)
    • Apply Enables
  • in the LHC project, verify that rf2ttc (LHC_interfaces panel) is ready and that BC2 signal source is external (load recipe from "select recipe" button with name RF2TTC/R_HWInit/_external_BGV)
  • Analysis:
    • get the FILLED_BUCKETS from Timber (LHC.BQM.B2:FILLED_BUCKETS)
    • open bgv_raw.py
    • add filenames of PulseShapeRun you want to analyse (Run_000*.mdf). There should be 4 files for a run with 1000 Events per step (26 steps, TAE=2, NZS data)
    • add list of filled buckets
    • give your rootfile a name
    • save and close bgv_raw.py
    • on lxplus, SetupProject LHCb
    • run python -i bgv_raw.py runnumber EvtsperStep TAE
    • this takes very long. For 1000 evts. per Step and all 8 tell1s included it's about 3 hours.
    • after .root and .pkl are created from the py script, run python -i pulseShapeScanAnalyzer.py runnumber
    • for the first time running these two python scripts, make sure that the paths are set correctly by you, they are not independent from the user atm

ADC Delay Scan Run
  • BGV_TOP Panel:
    • Activity: ADCDELAYSCAN, Nr.Events:*e.g. 100, *Automated Run with Steps: 17
  • BGV_TFC / TFC_PART16 Panel:
    • check that TFC Functions: are * Enable only Calibration trigger A, , Trigger type brdcst * BGV_DAQ_M01 / *CB0HybridX Panel:
    • *In Hybrid panel, check if TestPulse is activated (press read button)
    • TP is normally not activated by configuration from top. You need to reset the CBs and Hybrids from the BGV_DAQ_M01 panel and then configure from there with PHYSICSTP recipe. Checking TP again should give you a tick and a delay-value.
  • Analysis:
    • in the ADCDELAYSCAN folder at /group/bgv open Vetra-ADCDelayScan.py
    • change line 70 and line 73 regarding to your source file and destination file
    • SetupVetra (if not already done)
    • gaudirun.py Vetra-ADCDelayScan.py
    • verify data with output root file
    • run ./delayScanAnalyzer rootfilename.root
    • copy the ADCDelayValues from the xml file to the cfg files
    • careful: the list in the xml file is 4 times 16 links. The first 16 values represent the last 16 values in the cfg-file (the order 1-16 remains the same).
    • save cfg files and configer each Tell1 manually with it's respective cfg file. Then, in WinCC, read values from current configuration and save as recipe again.
    • the xml files have different names to what we call the tell1s. bgvtell01: 527, bgvtell02: 467, bgvtell04: 510, bgvtell05: 477, bgvtell06: 152, bgvtell07: 508, bgvtell08: 460, bgvtell09: 466

Recipes

Files located under DCS project directory, /localdisk/wincc/DCS/HV_LV_recipes .

Simple text format, if needed for recipe change, change files, then "Load from file" on DCS_HV or DCS_HV project.

Other scripts

  • Script that gathers data from LV, HV and temperatures
    • logSensorsData_complete.pnl, located under /localdisk/wincc/DCS/scripts/
    • Writes ouput to /tmp/temperatures.txt
    • Must be started manually, $ startPA, then open DCS project console, Control Manager No.10 is the script.
  • Script that gathers run parameters
    • RunParameters.pnl, located under /localdisk/wincc/BGV/scripts/
    • Writes output to ?
    • Must be started manually, $ startPA, then open BGV project console, Control Manager No.11 is the script.
Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt bgv_raw.py.txt r1 manage 232.6 K 2016-12-14 - 14:33 UnknownUser  
Texttxt pulseShapeScanAnalyzer.py.txt r1 manage 7.2 K 2016-12-14 - 14:33 UnknownUser  
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2016-12-14 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    BGV All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 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