Skip to content

ArrayBenchSingle

Jump to bottom
pmeridian edited this page Oct 4, 2022 · 41 revisions

Table of Contents

Turn on cooling system

Read temperature sensors:

Check if there is a process already running, if not follow this instructions
OPEN NEW TERMINAL

conda activate tofpet_new
cd  /home/cmsdaq/Workspace/TOFPET/Timing-TOFPET2-py3/arduino/temperature
python3 read_temp.py -o temperature_tmp.txt -p /dev/tempmon_0 -r 9600

Note: keep this terminal always open.
Temperatures are saved in the temporary file "temperature_tmp.txt" and then automatically attached after each run at the end of the file "temperature_all.txt". The temporary file is then automatically cleared after each run.

Cooling control:

  • Make sure the cooling system is connected to the power (check black cable with "cooling" label)
  • Double click on the "LT_Interface" icon on the laptop desktop --> a GUI opens.
  • Click on File -> Open -> Select /home/cmsdaq/.wine/drive_c/users/cmsdaq/PR59TempController/StandardPIDConfig_withHeating.sc (The file should be visible in the window by default) -> Click Open
  • Click on Regulator -> Connect
  • Click on START on the "Regulator control" (default temperature should be set to 24 degrees Celsius, Sp1 value in the "Regulator information" box): the Peltier cell inside the box and the fans will start working.
  • Check on "Runtime" to see the variation in time of the temperature inside the box (see either T1 line on the graph or Tr1 value in the "Regulator Information" box)

Turn on xy tables

Check if there is a process already running, if not follow this instructions

Make sure the xy table system is connected to the power (check black cable with "guida mobile" label)

Start MOTOR_0 (connected to reference bar, TOP)
OPEN NEW TERMINAL

conda activate tofpet_new
cd  /home/cmsdaq/Workspace/TOFPET/Timing-TOFPET2-py3/arduino/tablexy
python3 grblServer.py --usb /dev/motor_0 -l /tmp/test.log --port=8820

Note: keep this terminal always open.

Start MOTOR_1 (connected to test array, BOTTOM)
OPEN NEW TERMINAL

conda activate tofpet_new
cd  /home/cmsdaq/Workspace/TOFPET/Timing-TOFPET2-py3/arduino/tablexy
python3 grblServer.py --usb /dev/motor_1 -l /tmp/test.log --port=8821

Note: keep this terminal always open.

To test the motors via a script:

OPEN NEW TERMINAL Edit the script (testXYMover.py) to test either motor_0 or motor_1.

conda activate tofpet_new
cd  /home/cmsdaq/Workspace/TOFPET/Timing-TOFPET2-py3/arduino/tablexy
python3 testXYMover.py

To test the motors via a gui (TO BE TESTED):

OPEN NEW TERMINAL
ENLARGE THE TERMINAL TO ABOUTR HALF OF THE SCREEN

cd  /home/cmsdaq/Workspace/TOFPET/Timing-TOFPET/arduino/tablexy
For MOTOR_0:
python xyShell.py --port 8820
For MOTOR_1:
python xyShell.py --port 8821

A GUI will open.
At first, the "homing" procedure will be run (the guide moves to reach 0,0 position). Then you can test the movement of the table by changing x/y positions.

IMPORTANT:

  • IN CASE THE XY STOPS AND MAKES A STRANGE NOISE, IMMEDIATELY UNPLUG THE POWER (CABLE WITH "GUIDA MOBILE" LABEL). STOP THE GRBLSERVERS, PLUG THE POWER CABLE BACK AND RESTART FROM THE BEGINNING.

  • IN CASE, THE XY TABLE DOES NOT WORK DURING A RUN (NO RESPONSE, BUT WITHOUT MAKING NOISE) SIMPLY STOP AND RESTART THE SERVER AND TRY AGAIN.

Turn on TOFPET

  • Switch on the TOFPET power: press the green "POWER" button in the white power unit inside the rack; the voltage is set by default to 12V.
  • Wait about 30 seconds for the system to warm up, until the current measured by the power unit is 1A.
  • Connect TOFPET to pc: OPEN NEW TERMINAL
conda activate tofpet_new
cd /home/cmsdaq/Workspace/TOFPET/Timing-TOFPET2-py3
./connect_TOFPET.sh

Note: keep this terminal always open.

  • Wait 60 min. for termal stability inside the box (within about 1/10 of degree). NOTE: Wait 1 hour only the first time you turn on the system from scratch.

Data acquisition

  • Turn off TOFPET:

    • stop the program "./connect_TOFPET.sh" (CTRL-C in the terminal)
    • turn-on the power (press green button)

  • Remove the Na22 radioactive source in its support from the box

  • Unplug / plug the crystal support in the TOFPET board:

    • In order to unplug the support first remove the support of the Na22 radioactive source (and then plug it back at the end)
    • Ask Francesco for instructions and recommendations on how to do unplug / plug the crystal in the support properly
    • Plug the crystal bar support in the TOFPET board using the slot at the bottom. (BE VERY CAREFUL with the connector since the pins are very small and delicate!!!)
    • Note: The reference crystal pixel should be already mounted on the other TOFPET board.

  • REMEMBER TO CLOSE THE BOX BEFORE STARTING ANY RUN !!!!

  • Turn on TOFPET (as in point 2):

    • turn-on the power
    • wait 30 seconds to warm up, until the measured current is about 1A
    • start the program "./connect_TOFPET.sh"

  • Wait 10 min. for system stability

  • Put back the Na22 source back in its support inside the box

  • If not present, open the GUI: OPEN NEW TERMINAL (can use the same for following runs)

cd /home/cmsdaq/Workspace/TOFPET/Timing-TOFPET 
~/startBenchGui.sh
  • Once opened the GUI:
    • Select the BAR code
    • For normal measurement make sure the Longitudinal scan box is not checked

NOTES:

  • typically you should only change the bar code (always keep 6 digits in the name). The run number will be automatically updated for every acquisition and used as label in the output file names.
  • the standard run sequence is:
    • PEDESTAL run (few seconds)
    • PHYSICS RUN (300 s)
    • PEDESTAL run (few seconds) The run numbers will be sequential.

Update airtable

When the maximum records value 1200 is reached do the following steps:

  • In airtable.com duplicate the last working DB, change the name accordingly and then remove all the RUNS records
  • Then go to https://airtable.com/api to check the REST api endpoints for your new DB. Click on the newly created DB and then:
    • appID: "The ID of this base is appXXXXXX"
    • Authentication Token: click top right "Show API key", then scrolling to authentication you will find the key "keyXXXXXXXXX"

The new authentication key should be changed in ~/AutoProcess/setup.sh. Instead the appID should be changed into "runDB.py". Then restart the autoprocess service

Clone this wiki locally