Labview operation

Contents

This page is a branch of the main AHCALTestBeamCERN2015 page. More specifically, is a part of the Operation section.

Data storage

A backup of labview data is sent to the naf flc group folder manually. For that, the NAF flc group folder is mount in the Monitoring PC (flcahcallab06) as well as the Labview hard drive (which is in Windows operative system).

To mount the labview hard disk:

sshfs calice@192.168.1.11:F:/ DAQ_PC/ -oauto_cache,reconnect

To mount the NAF flc group folder:

in calice@flcahcallab06:~/Desktop$
sshfs $USERNAME@nafhh-ilc02.desy.de:/nfs/dust/ilc/group/flchcal NAF_DESY/ -oauto_cache,reconnect

/!\ Now the files are not copy to the NAF but to the dCache <link to put here>

To copy the files to the NAF flc group folder:

in calice@flcahcallab06:~/Desktop :
rsync -ahvp --progress --size-only /home/calice/Desktop/DAQ_PC/CERN_SPS_July_2015/Muon/* /home/calice/Desktop/NAF_DESY/Muon/

Don t forget then on the NAF to give the permissions on the folder.

/!\ To unmount the point in case of disconnection/non response from the mounting point. Never do a  rm -rf  of the folder on the Desktop! Do :

kill sshfs process that you are interrested in. Do htop to check the process list and then kill it.
Then : fusermount -u /home/calice/Desktop/$MOUNTPOINT

That should be it then you can remount the point.

MPOD

MPOD is the name of the rack power supply, which supplies low and high voltages to each detector layer individually. The labview project for mpod control is located in

D:/MPOD_Labview/AHCAL_MPOD.lvproj

The Labview connects to the MPOD via Ethernet with the local address 192.168.1.2. When the labview is running, it checks the actual voltages and currents all the time. The typical delay in showing the values is 1~3 s.

Channels can be switched on and off

The "set" button adjust the voltage and this button should be operated only by experts.

MPOD Labview screenshot

Switch on procedure

  1. switch on LV1 module by "LV1 ON" green button

  2. switch on LV2 module by "LV2 ON" green button

  3. wait for all chennels go green. High voltage can be switched only after all low voltage channels are ramped up!
  4. switch on Bias-V module "HV1 ON" and "HV2 ON" green buttons.

  5. switch off unused channels as shown on the screenshot by "on" buttons for u1, u101 and u401
  6. continue with detector labview contro startup procedure

Switch off procedure

  1. switch off the high voltage first by "HV1 OFF" and "HV2 OFF" red buttons

  2. wait for all high voltage reads are 0
  3. switch off LV1 module by "LV1 OFF" red button

  4. switch off LV2 module by "LV2 OFF" red button

In case of real emergency (=smoke coming from beam area) use the "ALL OFF" top red button

Single layer restart procedure

If one layer does not communicate for some reason, it is possible to restart a single layer, but this is strongly discouraged. After this all layers have to be checked for stuck TDC again, since the single-layer restart procedure often affects other layers.

Monitoring

The MPOD labview control shows the voltage on its output and the current drawn from the power supply. Typical currents are shown at the picture. The +6V current drops significantly (down to ~0.6 A) when the ASIC power is off.

Labview configuration for beam data taking

The labview project for data taking is located in

D:/AHCAL_DAQ_xLDA/AHCAL_DAQ_xLDA.lvproj

The Labview controls directly the CCC (which physically sends starts and stops the acquisition) and LDA (which the controls and readout the layers through DIFs: 1 DIF per layer). It can also run in a "slave" mode to EUDAQ, which is then controlling the runnumber, run starting and run stop.

However, the configuration of the layers can be done only in the Labview program. All communication to layers is done through the LDA, which can broadcast messages or send the messages individually as well as collecting the responses from layers.

Multiple packets are usually sent when any single buttons is clicked. To see the overview of the communication (which layer responded and which not), there is a communication summary assigned to almost any action:

screenshot_labview_comm_summary.png

The "Set" and "Ack" on the left side show the summary of the communication - if the message (packet) was successfully sent and received. If every is ok, then all lights are green. If some layer is not responding, the Ack light goes red and then in the array of lights one can list through the layers, which responded (green) and which not (red). The LED indicator array is sorted according to the LDA port position. === List of Slow Control Files. === The first tab of the labview control program contains default path for the slowcontrol it should look like this:

Labview detector configuration

There is a difference for module 11 and 10. They need a different folder for calibration mode (LEDs, Muons) and Physics (Pions, electrons...), since the SiPM produce to big signal. The folder name is "...\Calib" for the calibration mode and "...\Physics" for physics mode.

Other slowcontrol parameters should be untouched. It contains number of ASICs in the SLAB and if the power should be on during the slowcontrol write or not. === System setup=== This page control 3 main parts:

labview system setup

For the SPS testbeams only 1 LDA is used: the Wing-LDA. It has a fixed IP 192.168.1.34. The tcp port number is 5632 by default. "Configure x-ldas" button has to be pressed each time when port is enabled or disabled by the buttons, otherwise the changes are not applied.

The CCC uses fixed address 192.168.1.61 and default port 3142

Power on procedure from Labview

  1. LDA has to be configured by the "configure x-LDAs" button. It is a good point where to check if the LDA is working properly. if the "Mini-LDA A Config" status indicators don't go fully green, it can be due to:

    • huge data in the buffer ==> try again or go to expert tab and press "Stop CCC" and "flush LDA" buttons

    • some layer is not powered by MPOD ==> disable the port, which is connected to the unpowered layer

    • LDA crashed ==> see the LDA section. Needs to be rebooted or powercycled.

  2. CCC has to be configured to the default state by the "Configure CCC" button

  3. layers have to be powered by a special sequence, which has to be followed precisely
    1. (C)ASIC Power OFF
    2. (B)3.3V+Drivers Power OFF
    3. (A)VDDA/VDDD Power OFF
    4. (A)VDDA/VDDD Power ON
    5. (B)3.3V+Drivers Power ON
    6. (C)ASIC Power ON
    7. (C)ASIC Power OFF
    8. (B)3.3V+Drivers Power OFF
    9. (A)VDDA/VDDD Power OFF
    10. wait 15 seconds
    11. (A)VDDA/VDDD Power ON
    12. (B)3.3V+Drivers Power ON
    13. (C)ASIC Power ON
  4. continue with the slowcontrol

Slowcontrol loading

Labview slowcontrol load

Correct folders for the slowcontrol have to be provided before the slowcontrols are written to the layers. There are 2 path suffixes:

"Autopopulate SCs" button adds the suffix to the paths specified in the "1) Detector Config." tab. Therefore the "...\Calib\..." or "...\Physics\..." folder have to be adjusted after the autopopulate button is pressed.

Once the paths are correct, the "Write SC" button transfers the slowcontrol files to the layers.

Do not press "Write current paths to buffer" button! it will overwrite the configuration in the "1) Detector Config." tab.

Detector configuration in Calibration tab

Calibration tab for autotrigger mode

For the AutoTrigger mode, all values should be set according to the picture and all 3 "Set" buttons have to be pressed at the end.
More detailed explanation of values:
DAC1 voltage: the voltage, that is set for calibration LED. Optimal value depends on HBU type and varies from 3000 to 9500. Should be off for AutoTrigger.
TCALIB1 (5): enables the trigger for onboard LEDs. Should be off for AutoTrigger
Pre_Bias 2: apply the high voltage to the SiPM. Must be set off before removing the black cloth

"Read" button executes a temperature readout, which take ~30 s.

Configuration for taking data

Labview Take data tab

The detector has to be told after the power-up , whether it will run in AutoTrigger (AT) or External Trigger(ET). This can be done by pressing appropriate set button: Either in the "Setup Testbeam Mode" box or in "Setup Lab Mode".

Explanation of buttons:
Wait for spill: when ON: Acquisition is started only after spill arrives. Should be on.
Validation: use the signals from trigger scintillators to validate the hits in ASIC. it is mandatory to suppress noise.
LED AT: generates a LED light in AT mode. For special operation only
Dummy Trgs: Number of dummy triggers, where the memory cell is filled by fake signal elimination the first memory cell bug of the ASIC. Should be 1. It also defines number of LED AT trigger.
START: starts the data acquisition immediately without waiting for the eudaq
STOP(Stop data taking): schedule an end of acquisition. Takes 3s typically. Might take longer when temperature readout is in progress.
Write TXT data?: writes the ADC and TDC values from ASIC. Otherwise writes only slowcontrol and temperature values. Eudaq data transfer is not affected.
Write temperatures?: performs a periodic measurements of temperature every specified number of cycles
Power off during T readout: switch off the VDDA for SPIROCs during temperature readout, which remove the voltage drop offset in the temperature data.
AutoPath: automatically fill in the path from bottom right corner to the path in the top left corner. Necessary for EUDAQ operation.
Listen: puts the labview into listening mode, where it wait for the EUDAQ command.
Auto Listen: automaticallu starts "Listen" after the run is finished.

Power off during T readout: switch off the VDDA for SPIROCs during temperature readout, which remove the voltage drop offset in the temperature data.
AutoPath: automatically fill in the path from bottom right corner to the path in the top left corner. Necessary for EUDAQ operation.
Listen: puts the labview into listening mode, where it wait for the EUDAQ command.
Auto Listen: automatically starts "Listen" after the run is finished.

Listen + autopath mode (ready for the EUDAQ commands)

Once the Labview settings are ok, we must set it in Listen Mode (and Auto Listen Mode if we take more than one run) and we need to give to it the folder name in the autopath cell (bottom right corner). Double check that this information is also correct in the path cell near the Yippie!! button.

Listen Mode

{OK} We are ready to take data

Labview configuration for LED scans

The procedure for putting the detector into the LED calibration mode (=External trigger mode) is very similar to the AutoTrigger setting:

Calibration tab for external trigger mode

Automated LED scan

Each layer and each SiPM needs different LEd bias voltage, therefore the LED run has to be performed many times with different LED intensity. There is a VCalibScan.vi program to automate the process. The LED scan can be

LED daily scan LED long scan

The path for daily LED should be

F:\CERN_SPS_August_2015\Daily_LED\$DATE\Run_$NUMBER_VCalib_2000cycles_ET_

Labview crashes

The most usual reasons for a crash of the labview are:

If this happens, just close the pop-up window and the schematic Labview view that appears, unclick the "Listen" and "Yippie!!" buttons and restart the labview (click in the white arrow in the left almost top corner). Then make sure that the run number and folder name are correct and also that the settings are the expected. Put it again in Listen mode and start the run with the eudaq.

Please, double Check that the run/folder names are correct in both cells! It may happen that the next run will be called something like:

Run_24001_11p08p2015_16p00p00Run_24001_11p08p2015_16p00p20.txt

and then we would need to rename it afterwards.

AHCALTestBeamCERN2015/LabviewOperation (last edited 2015-08-26 15:08:20 by AdrianIrles)