The FEE Server Control Engine of the ALICE-TRD - Westfälische ...

6 Temperature Monitoring of the Front End Readout Electronics
The program needs three configuration files: for the transitions from STDBY to
STDBY_INIT, from STDBY_INIT to CONFIGURED, and from CONFIGURED back to
STDBY_INIT. 1 The configuration files contain the same data that are transferred from the
wingDB to the FEEServer during the corresponding transitions of the finite state machine.
By using configuration files the program becomes completely independent from the software
infrastructure and the configurations in the wingDB. Therefore it is guaranteed that
always exactly the same configurations are used and the results of the temperature measurements
remain comparable.
Before a measurement is started the supermodule should be switched off for 30 to 60
minutes. This time is required to make sure all MCMs are cooled down and have approximately
the same temperature. Afterwards the DCS boards have to be switched on
and the program with the three configuration files has to be copied to each DCS board.
The program requires four parameters. The first parameter is the chamber type (0 for a
six ROB chamber or 1 for a eight ROB chamber) and the other three parameters are the
filenames of the configuration files. When the program is started it processes the data
in the first configuration file (transition from STDBY to STDBY_INIT). When the configuration
is finished it measures the MCM temperatures at regular intervals. The interval
can be configured in the first configuration file and is set to 5 seconds by default. After
some time (usually 20 or 40 minutes) the second configuration and the same time later
the third configuration is sent. These intervals are set in the source code of mcm_temps.
It requires some time and much typing to copy the necessary files to all DCS boards of a
layer or even a supermodule, starting the program, and collecting the results afterwards.
Therefore three shell scripts were written which reduce the necessary effort. The script
dcs_script.sh runs on the DCS board and controls mcm_temps. Usually this script does
not need to be called by a user. The script do_test.sh copies all necessary files to the
DCS board and performs the temperature measurement for one chamber. It expects the
chamber name, the chamber type, and an output directory as parameters. The chamber
name is the network name of the target DCS board. The name of the output file where
the recorded data are written to is the chamber name plus the extension dat. The data
format is shown in listing 6.1. Each number represents one MCM temperature sensor.
Non-working sensors are indicated by -1.
Debug (\CE) : DCS−Temperature : #### 23.3049
Debug (\CE) : ROB: 0 : ### 360 416 467 431 461 −1 −1 400 372 360 453 379 −1 −1 −1 298 −1
Debug (\CE) : ROB: 1 : ### 404 421 420 388 358 −1 436 427 427 439 −1 362 462 −1 −1 −1 −1
Debug (\CE) : ROB: 2 : ### 431 −1 458 376 −1 362 430 409 420 384 408 442 −1 441 373 375 −1
Debug (\CE) : ROB: 3 : ### 401 457 −1 281 339 396 411 406 −1 372 349 −1 −1 −1 385 460 −1
Debug (\CE) : ROB: 4 : ### 408 −1 402 347 −1 432 389 −1 386 455 −1 370 380 398 394 424 −1 −1
Debug (\CE) : ROB: 5 : ### 443 −1 377 358 −1 358 −1 449 −1 −1 367 −1 −1 −1 309 −1 −1 −1
Debug (\CE) : ROB: 6 : ### −1 −1 448 405 −1 360 −1 363 404 −1 406 395 −1 −1 −1 −1 −1
Debug (\CE) : ROB: 7 : ### −1 402 413 355 −1 351 374 386 −1 −1 442 422 405 −1 −1 412 −1
Listing 6.1: Data format used by the temperature measurement program. Non-working
temperature sensors are represented by -1 since the possible range of the ADC values
is 0 to 1023.
The script temp_layer.sh calls do_test.sh for each chamber of a layer. It requires only
the list of layers as parameters. To measure a complete supermodule one has to call just
temp_layer.sh 0 1 2 3 4 5.
The data format used by the temperature measurement program is human readable.
1 Even if the program does not contain a finite state machine, in this section the same names as in section
5.2.2 are used since the configurations are the same.
79