Pixel-ROD-Crate-Controller(Pxl-RCC) @ CPPM

Atlas
PxlModule scan with the ROD

Recipe for a ROD Pxl scan from A to Z
received from Guido; June 10th, 2004

Prerequisites, Summary
So, you want to do a scan on a stave. To do that you have to:

Setup the hardware for scanning
Get the head of the CVS and compile and link the programs in Example
Create a database with the settings for your system
Run ScanTest and get the results

Implementation, Step by Step

We have an electrical Back-of-crate card (eBOC) in Marseille. You must find out to which connector on the back of the board the capton cable from PP0 is connected (J1, J2, J3 or J4).
See instructions and status at CPPM
Change to the directory (cd Applications/Pixel/PixLib/)Examples/. In this directory should be a BaseConf.cfg file. (Otherwise cvs update to retreive the latest version from CVS.) This file is used as input to create a new root database by issuing the command:
RootDBTest -n BaseConf.cfg
The output is a new root file called BaseConf.cfg.root
Now you have to populate the root file with your modules. You need to put the configuration files for your modules into a subdirectory of Examples/ or your choice (look in atldaq2 as example the subdirectory Examples/M510902 or a similar one, that has a substructure configs/, fdacs, masks, tdacs where to put the TurboDaq files. Once you have these directories ready for a given module, you may issue the command

ModuleGroup_Wizard BaseConf.cfg.root "/Test_0/application" Grp0_0 <module_dir>/configs/<config_file>.cfg
where:

the first parameter of ModuleGroup_Wizard executable is the root file you want to put the module configuration in,
the second parameter is where the PixModuleGroup you want to create/update is located in the database,
the third parameter is the name of the PixModuleGroup inquire (you may choose one you want, if you like),
the fourth parameter is the location of the TurboDaq config file you want to import in the database.
It may take some time until the application ends the processing of the TurboDaq file, so keep patient.
At this point you have a file BaseConf.cfg.root which holds a PixModuleGroup which have one module. You still have to arrange the default parameters of BaseConf.cfg to your system. In order to do so, you can edit the database file. First issue the command:

root RootDBTest.kumac
this command does nothing but loading the root shared library with the PixLib code and open the file BaseConf.cfg.root in update mode, so that you can modify from the TBrowser.
Now you have got a TBrowser in your desktop and you can navigate "explorer like" into the ROOT files directory where you should find BaseConf.cfg.root.
You need to modify several parameters.

the VME slot where your rod is: Follow the directory structure and find out: Test_0/Grp0_0/RodPixController_0. At this point you will see some items (actually six) which are the fields of the RodPixController inquiry (cf. figure).

The field you are interested is Slot. Click on it with the right mouse button, a popup menu will appear. Select "Dump" and on the text window of root will be dumped something like that:
Dumping RootDBField named: Slot RootDBField decName: /Test_0/Grp0_0/RodPixController_0/Slot;1 Data type: int Data content: 9
In order to modify the content of the field you again rightclik over the Slot item, and select "ModifyFieldValue". A popup window will appear, you can write the slot number you have in your system (e.g. 12 - is decimal) and click OK. You can then dump again the field and see the modified value.
the input link number of your module: This value depends on where you put in the PP0 your module, and where you connected the capton cable to your electrical BOC. The ROD/BOC link map contains the numbering scheme of the input/output connections. It is quite easy to find out which channel number is your module connected to, consider that the optoboard is on the right side of the PP0. For example, suppose that you connected the capton to the connector J3 of the electrical BOC, and the module to the nearest slot in PP0 to the optoboard, your module index is 20. Now follow the table: module index 20 is cmd link 32. This is your inputlink. The input link field you find in /Test_0/Grp0_0/<your module config name> and is the field general_InputLink (cf. figure).

Edit it like for the slot number and put your input link value
the output link of your module: This is the FMT link in the table. If the number you find is (following the example above) 6:2, then you have to set the field (cf. figure above) general_OutputLink1 (that is, DTO of the MCC...) to the value 0x62 in hexadecimal, that is with the value 98!
You the exit from root, it closes the BaseConf.cfg.root files and you're done! I suggest you to copy then the file BaseConf.cfg.root with another mnemonic name, in order to have in the end some configuration files accordingly to your differents modules/PP0-positions ...
Now simply issue the command:
ScanTest <your configuration file>
where <your configuration file> is BaseConf.cfg.root or whatever you called it, finger your cross and get a scan!

Remarks, Comments
Use these instructions only for setups with eBOC until confirmation by experts.

Let us know, if these recipes works or you want to suggest improvements.
(Guido.Gagliardige.infn.it, Paolo.Morettinige.infn.it, Hoffmanncppm.in2p3.fr)

Created: June 2004; last updated: June, 14th 2004

Atlas PxlModule scan with the ROD	Recipe for a ROD Pxl scan from A to Z received from Guido; June 10th, 2004
	Prerequisites, Summary So, you want to do a scan on a stave. To do that you have to: Setup the hardware for scanning Get the head of the CVS and compile and link the programs in Example Create a database with the settings for your system Run ScanTest and get the results Implementation, Step by Step We have an electrical Back-of-crate card (eBOC) in Marseille. You must find out to which connector on the back of the board the capton cable from PP0 is connected (J1, J2, J3 or J4). See instructions and status at CPPM Change to the directory (`cd Applications/Pixel/PixLib/`)`Examples/`. In this directory should be a `BaseConf.cfg` file. (Otherwise `cvs update` to retreive the latest version from CVS.) This file is used as input to create a new root database by issuing the command: `RootDBTest -n BaseConf.cfg` The output is a new root file called `BaseConf.cfg.root` Now you have to populate the root file with your modules. You need to put the configuration files for your modules into a subdirectory of `Examples/` or your choice (look in atldaq2 as example the subdirectory `Examples/M510902` or a similar one, that has a substructure `configs/`, `fdacs`, `masks`, `tdacs` where to put the TurboDaq files. Once you have these directories ready for a given module, you may issue the command `ModuleGroup_Wizard BaseConf.cfg.root "/Test_0/application" Grp0_0` <module_dir>`/configs/`<config_file>`.cfg` where: the first parameter of ModuleGroup_Wizard executable is the root file you want to put the module configuration in, the second parameter is where the PixModuleGroup you want to create/update is located in the database, the third parameter is the name of the PixModuleGroup inquire (you may choose one you want, if you like), the fourth parameter is the location of the TurboDaq config file you want to import in the database. It may take some time until the application ends the processing of the TurboDaq file, so keep patient. At this point you have a file BaseConf.cfg.root which holds a PixModuleGroup which have one module. You still have to arrange the default parameters of BaseConf.cfg to your system. In order to do so, you can edit the database file. First issue the command: `root RootDBTest.kumac` this command does nothing but loading the root shared library with the PixLib code and open the file `BaseConf.cfg.root` in update mode, so that you can modify from the TBrowser. Now you have got a TBrowser in your desktop and you can navigate "explorer like" into the ROOT files directory where you should find `BaseConf.cfg.root`. You need to modify several parameters. the VME slot where your rod is: Follow the directory structure and find out: Test_0/Grp0_0/RodPixController_0. At this point you will see some items (actually six) which are the fields of the RodPixController inquiry (cf. figure). The field you are interested is Slot. Click on it with the right mouse button, a popup menu will appear. Select "Dump" and on the text window of root will be dumped something like that: Dumping RootDBField named: Slot RootDBField decName: /Test_0/Grp0_0/RodPixController_0/Slot;1 Data type: int Data content: 9 In order to modify the content of the field you again rightclik over the Slot item, and select "ModifyFieldValue". A popup window will appear, you can write the slot number you have in your system (e.g. 12 - is decimal) and click OK. You can then dump again the field and see the modified value. the input link number of your module: This value depends on where you put in the PP0 your module, and where you connected the capton cable to your electrical BOC. The ROD/BOC link map contains the numbering scheme of the input/output connections. It is quite easy to find out which channel number is your module connected to, consider that the optoboard is on the right side of the PP0. For example, suppose that you connected the capton to the connector J3 of the electrical BOC, and the module to the nearest slot in PP0 to the optoboard, your module index is 20. Now follow the table: module index 20 is cmd link 32. This is your inputlink. The input link field you find in `/Test_0/Grp0_0/`<your module config name> and is the field general_InputLink (cf. figure). Edit it like for the slot number and put your input link value the output link of your module: This is the FMT link in the table. If the number you find is (following the example above) 6:2, then you have to set the field (cf. figure above) general_OutputLink1 (that is, DTO of the MCC...) to the value 0x62 in hexadecimal, that is with the value 98! You the exit from root, it closes the `BaseConf.cfg.root` files and you're done! I suggest you to copy then the file BaseConf.cfg.root with another mnemonic name, in order to have in the end some configuration files accordingly to your differents modules/PP0-positions ... Now simply issue the command: `ScanTest` <your configuration file> where <your configuration file> is `BaseConf.cfg.root` or whatever you called it, finger your cross and get a scan!
	Remarks, Comments Use these instructions only for setups with eBOC until confirmation by experts.
	Let us know, if these recipes works or you want to suggest improvements. (Guido.Gagliardige.infn.it, Paolo.Morettinige.infn.it, Hoffmanncppm.in2p3.fr)