MDT power supplies

  • by NTU Athens

MDT Power Supply Configuration DB

General Information

The MDT PS DCS project is also connected to a configuration DB. This DB is responsible for the storage of device properties (e.g. trip current limits, trend smoothing details, archiving configuration) and settings (e.g. alarms ranges, output values, operational voltages). The project uses a tool developed from JCOP fw called "configuration DB tool". The main concept behind configuration DB tool is the concept of recipes. The recipes are a set of predefined settings under one name - the recipe name. The DCS expert, after collaboration with the detector experts, gathers all the appropriate settings that characterize a state of the detector (at least from Power Supply side) and creates a recipe with a meaningful name. This recipe is saved in DB is ready, in any time, to be used by the shifter. The panel below is the interface to the configuration DB. The shifter can choose one of the predefined recipes from the drop down list and apply it pressing the "Apply Recipe" button. Moreover, this interface, allows a not predefined recipe, under the name "custom" where the user can chose the chambers to be applied the new settings and the settings with their values themselves. Configuration DB tool is a powerful tool that ease the detector driving from DCS side, while ensuring on the same time coherency and safety. For the Power Supply of MDTs the Operational Interface of this tool is the panel below:


Shifter Manual

In case you want to use the configuration DB tool , for the MDT Power Supply, follow the instructions below:
  • Check first that the DCS project is connected to the DB. On the top left of the panel, The DB box


  • Since the project is connected to the DB , a shifter , has the acces to apply predifined reipes. In the lower part of the panel (2.Apply Recipes) , the shifter has already access to the drop down list of the Operational Recipes The recipes have a self-expained name. So for example, if the shifter wants to apply 3000V for HV for barrel chambers, he/she can select from the drop-down list the name HV_v0_3000V_Barrel.


  • As soon as the recipe is chosen, the shifter mast apply this recipe. This is done by pressing the "Apply the recipe" button.


  • The recipe is now applied. (It worhts to be mentioned that for this type of recipes, that applied in the hole partition, the application may take about 3min - the amount of opc items to be sent to hardware is very big)

Explert priviledges

In case an expert takes control of the DCS, the configuration DB panel provides more facilities. The expert besides the actions of a shifter ,explained above, can also apply some basic hardware settings, make custom recipes, create new predifined recipes.

Apply basic hardware settings.

For users with expert priviledges, a second drop-down list is enabled. This drop-down list has recipes connected with detector safety settings. e.g. The recipe Basic_Trip_Tip_1s_Barrel applies in all barrel the trip time limit to 1sec.


Make a custom recipe:

It is usefull some times the expert to be able to apply settings in a smaller group of chambers than a hole partition. Besides, it may be useful to apply to some chmabers settings that are not the predifined ones. In such cases the expert has to create its own custom recipes. The proedure will be explained with the help of an example. E.g. we want for the inner barrel chambers of side A and sector 6 to apply HV in 3050V.
  • Firstly in the top part of the panel the expert should choose the wanted chambers ( "*" can be used as a pattern filter). Enter in filter BI*A06


  • Then since we are interested in HV, we press the HV button on the right, and the list of the wanted chambers appear.


  • On the bottom, on the select recipe type radio box, we choose Make Custom Recipe


  • Then we check the tic box of the v0 and inset the wanted value e.g.3050


  • Then we check again from the above list what chambers we want to apply the recipe to. In our case all, so we press the button select all.
  • Then in the custom recipe area, we check the tick box Selet Chambers And Values & Tic that means we checked our settings before create/apply the recipe.


  • Since it is a custom recipe we do not change the name of the recipe in the box.


  • The recipe should then be created


  • Finally the recipe should be applied


Create a new predefined recipe:


The procedure to create a new predifined recipe is the same as the procedure of creating a custom recipe with the only difference of the name entry. In case the expert wants to create a new predifined recipe, he/she should give a descriptful name to this recipe instead of custom. All the rest are the same.

Recipe Name Restrictions / Conventions

  • The name of the new predifined recipe , should not be "custom"
  • In case it is an operation safety recipe (like set all trip time limit at 10sec), the name should start with safe (e.g. _safe_trip_time_10sec_barrel)
  • The name should be self exlplained (e.g. HV_ML1_3000V_barrel)

"How-to" instructions for Experts

Changes in the mapping of the channels

There are two procedures to follow concerning changes in PS channels connected to MDT chambers. The first case concerns exchange between already used PS channels. The second one refers to dismissing an already used PS channel and using a spare one. The procedures to be followed in each case are shortly described below:

Exchange between already used channels

  • Change mapping info
  • Change descriptions
  • Update DB
  • Restart FSM
  • Restart the control scripts

Using spare channels

  • Deactivate alarms
  • Stop archiving
  • Change settings (use settings for spare channels)
  • Deactivate addresses
  • Change mapping info
  • Change descriptions
  • Activate addresses
  • Change settings (use settings for regular channels)
  • Start archiving
  • Activate alarms
  • Update DB
  • Restart FSM
  • Restart the control scripts

Description of individual procedures

Each of the above actions is described precisely in the respective paragraphs and should be applied in the correspondent system; in the case that the chamber whose PS channel is being changed belongs to the Barrel, all the following actions must be applied in the pcatlmdtps2 pc, while in the case of an Endcaps' chamber in the pcatlmdtps3 pc. After logging in the correct PS pc, the first step is to open the project's PVSS console and the Log Viewer. Then, in the console click on the gedi "User Interface" and start the manager.
De-/activate alarms
In the gedi click on the "Vision" (gear) icon and then in the "Project" drop down list choose the "\\cerntsatldcs01\ATLAS_DCS_MDT\panels" path. Navigate in the mdtPs_tools and choose the "alarmHandling.pnl". Click on the "Display All Chambers" button and then from the filled list choose and transfer through the ">" button the chambers whose channels' alarms you want to de-/activate. Before clicking on the "De-/activate chambers' alarms" button make sure you check the ML1, ML2 and/or LV checkboxes. Wait until you get a message in the Log Viewer letting you know that the process has finished and then close the panel.


Stop/start archiving
As in the previous paragraph, you open the "archiveHandling.pnl" in the mdtPs_tools directory. In the case of starting the archiving after the channel change, the archiving needs to be configured first. So, before pressing any button on that panel, choose the "RDB Archive Manager" on the console, press on the "Edit Manager Properties" button, set the start mode to "manual" and then stop the manager. On the "archiveHandling.pnl" choose "select specific chambers" in the radiobox, press on the “Get all chambers” button, choose from the first table the chambers whose archiving you want to stop/configure/start and transfer them to the second table using the ">" button. There are three groups of archiving to be taken care of: the float values for every channel, their boolean values and the state of every chamber along with the status of its channels. Among these values, the float ones’ archiving has to be configured by the user: the type of the archiving has to be defined (usually timeANDvalue dependent) and then the deadband and the time interval independently for the current and the voltage. Having set these values you press the “Configure archiving” button and then the respective button for the other two groups of archiving (boolean values and state-status). After configuring the archiving you have to start it. When stopping/starting the archiving, you need to have the RDB manager working. So, if you have stopped it in order to configure the archiving, go to the console, choose the "RDB Archive Manager", press on the "Edit Manager Properties" button and set the start mode to "always". This will cause the RDB manager to start automatically. This procedure will take about 3-5 minutes. When the manager is running, you can start/stop the archiving for all three groups. The “All boards’ temperature” group archiving shouldn’t be changed.


De-/activate addresses
You open the "communicationHandling.pnl" in the mdtPs_tools directory. In the “Chamber selection” frame choose "select specific chambers" in the radiobox, press on the “Get all chambers” button, choose from the first table the chambers for which you want to de-/activate the addresses and click on the corresponding button on the right side of the table.


Change mapping information
In order to change the mapping for the channels, you navigate to the chamber's datapoint in the "Fw_DUwithScript" datapoint type in para. In order to open the para module, in the gedi you choose it in the "Module" menu. When opening the datapoint elements you choose the appropriate channel (ML1, ML2, LV) you want to change the mapping for under the "Mapping" node. Click on the appropriate channel and then you will get information on the right side of the panel. On the "original value" text field enter the new channel mapping and then press the "Apply" at the bottom of the panel in order the change to be applied.


Change descriptions
You open the "descriptionHandling.pnl" in the mdtPs_tools directory. On the left of the “Chamber selection” frame choose "select specific chambers" in the radiobox, press on the “Get all chambers” button, choose from the first table the chambers which changed PS channels and then press on the “Set CAENchannel DPE description for the chambers”. Then, on the “Spare channels” frame press on the “List spare channels” button and wait until you get all the channels listed and the corresponding message on the Log Viewer. Afterwards, choose the no longer used channels from the first table, transfer them to the second one using the ">" button and press the “Set spare channels’ description” button.


Change settings
Using either the FSM panels in the chamber level or through the “para” module, set the correct settings for the channels (usually put the same settings as the neighboring channels) and 0 Set voltage in the case of spare channels. In the FSM panels you will have to log on with an expert account to make any changes to the settings (in the frame at the bottom of the chamber panel), while in para you will have to change the datapoint elements below “settings” and press the apply button after each change.


Update Database (DB)
You open the "mdtPs_compareDpsDB.pnl" in the mdtPs_tools directory. Choose "ATLMDTPS2" or "ATLMDTPS3" in the system frame depending on which system you want to make the update (Barrel or Endcaps respectively). Press the "DP Access" button to get the dps of the system and then "DB Access" to get the information from the DB. Once the above listing has finished, press the "Compare" button to see what is not updated in the DB (this check requires about 10 minutes) and then enter the Chamber name, the multilayer (type of the channel) and the Branch Controller, Crate, board and channel numbers of the channels to be updated in the DB and press the "Update DB information manually" button. Do this for all the channels that have different mapping in the DB and afterwards get all the information again and compare them to make sure that the changes have applied.


Restart FSM
In the project's console click on the fwDeviceEditorNavigator/fwDeviceEditorNavigator.pnl "User Interface" (DEN) and start the manager. In the panel that appears select the FSM tab and press the "Stop All" button. Wait until the "PVSS00smi (10), 2008.09.26 23:24:02.937, SYS, INFO, 2, Manager Stop" message appears on the Log viewer or alternatively until PVSS00smi process ends in the Task Manager. Then, press the "Start/Restart All" button on the DEN panel.


Restart the control scripts
The scripts that have to be restarted are the:
  • mdtPs/mdtPs_CaenWatchdog.ctl
  • mdtPs/mdtPs_copyInterlockFlags.ctl
  • mdtPs/mdtPs_tripCounter.ctl
In order to restart them you have to stop the corresponding control manager in the console. All of them are supposed to restart automatically after the stop. If not, inform the corresponding Expert and try stopping and starting it after you change the manager's settings from 'always' to 'manual'.

CAEN Firmware (FW) upgrade

The Firmware (FW) upgrade for the Branch Controllers and the Easy Boards can be done remotely through a telnet connection as long as the Firmware (FW) is transferred on the mainframe (telnet). So, the FW upgrade consists of two independent processes: the transfer of files to the mainframe and the upload of the files on the boards.

File transfer to the mainframe

In order to transfer files to the mainframe you will have to get the files in one of the two Power Supplies pc (ATLMDTPS2 or ATLMDTPS3). Such files are stored in the "C:\pvss\ATLMDTPS2\boardFWupgrade" or "C:\pvss\ATLMDTPS3\boardFWupgrade" folder respectively. Please place them on that file and do not create new folders or place them elsewhere. After you make sure that the file you want to upload to the mainframe is on the correct one, you will have to start the PumpKIN application.


When the window opens, click on the "Options" button and another window will pop up where you will use the default settings but you will have to check that the path of the file is the correct and press "OK". Afterwards, you will have to open a telnet session by running the "command prompt" and putting "telnet 1527" in the command line. When the telnet session starts you press any key and then enter the credentials: username:admin and password:admin.


Pressing the "right" and then the "down" arrow you get the "Utility" menu. By choosing either the "Boards Upgrade" or the "Remote Upgrade" you will get the "Upgrade Menu".


In the box of this window are the previously downloaded files; if they are three will not be able to upload a new one and you will have to delete one of the three. After making sure you can upload your file, press "tab" to place the cursor on the second menu where you choose the "Add File (via TFTP)" option and press "Enter". You will then have to give the name of the file and the IP address of the pc from which you will upload the file to the mainframe (ATLMDTPS2 or ATLMDTPS3). You can get the IP addresses by running another "command prompt" and putting the "ipconfig" command. If the transfer is successful you will be able to see the new file in the "Upgrade Menu" box. Exit the "Upgrade menu".

Uploading files on the boards

There are two kinds of board FW upgrade: the Branch Controllers' FW upgrade and the EasyBoards' FW upgrade. In the first case you open the "Utility" menu again and choose the "Boards Upgrade" while in the second one you choose "Remote Upgrade". In both cases you get the "Upgrade Menu" again where you select first (by pressing "Enter") the correct file and then choose "Download Sel. file on Board". After that you give the correct information; in the first case just the number of the Branch Controller, while in the second one the number of the Branch Controller and the Crate to which the EasyBoard belongs as well as the slot where the board is placed in the crate the way the telnet sees it.


After you finish working with the telnet session, expand the “Main” menu, choose “Log Out” and type "exit" in the command line. Make sure you exit this way the window and NOT by closing it through the “x” on the top right corner because this causes “ghost” sessions in telnet and makes the mainframe to “freeze”.

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng Apply.PNG r1 manage 0.6 K 2008-10-01 - 18:25 CharilaosTsarouchas  
PNGpng ConBox.PNG r1 manage 1.0 K 2008-10-01 - 18:18 CharilaosTsarouchas  
PowerPointppt ConfDB.ppt r1 manage 169.0 K 2008-10-01 - 16:45 CharilaosTsarouchas  
JPEGjpg ConfDBpanel.jpg r1 manage 262.0 K 2008-10-01 - 16:42 CharilaosTsarouchas  
PNGpng ConfDBpanel.png r1 manage 44.4 K 2008-10-01 - 16:41 CharilaosTsarouchas  
PNGpng DB.PNG r1 manage 168.8 K 2008-10-01 - 18:30 CharilaosTsarouchas  
JPEGjpg DBbox.JPG r1 manage 2.4 K 2008-10-01 - 16:49 CharilaosTsarouchas  
PNGpng DBbox.PNG r2 r1 manage 1.1 K 2008-10-01 - 18:13 CharilaosTsarouchas  
PNGpng DD_basic.PNG r1 manage 1.6 K 2008-10-01 - 19:07 CharilaosTsarouchas  
PNGpng DD_op.PNG r1 manage 5.3 K 2008-10-01 - 18:25 CharilaosTsarouchas  
Bitmapbmp DEN.bmp r1 manage 13.2 K 2008-10-06 - 12:41 EleniMountricha Device Editor and Navigator
JPEGjpg Dbbox.JPG r1 manage 2.6 K 2008-10-01 - 18:15 CharilaosTsarouchas  
PNGpng Sel.PNG r1 manage 1.9 K 2008-10-01 - 18:59 CharilaosTsarouchas  
Bitmapbmp addresses.bmp r1 manage 2690.7 K 2008-10-06 - 12:31 EleniMountricha Communication handling Expert panel
Bitmapbmp alarms.bmp r1 manage 1816.0 K 2008-10-06 - 12:30 EleniMountricha Alarm handling Expert panel
Bitmapbmp archive.bmp r1 manage 1737.8 K 2008-10-06 - 12:31 EleniMountricha Archive handling Expert panel
PNGpng c.PNG r1 manage 0.7 K 2008-10-01 - 19:06 CharilaosTsarouchas  
Bitmapbmp chamberFsmPanel.bmp r1 manage 97.8 K 2008-10-06 - 12:39 EleniMountricha The FSM panel for the chambers
Bitmapbmp compare.bmp r1 manage 2059.4 K 2008-10-06 - 12:34 EleniMountricha DB-datapoints mapping comparison Expert panel
PNGpng cust.PNG r1 manage 0.8 K 2008-10-01 - 19:05 CharilaosTsarouchas  
Bitmapbmp descriptions.bmp r1 manage 1330.6 K 2008-10-06 - 12:32 EleniMountricha Description handling Expert panel
PNGpng list.PNG r1 manage 11.6 K 2008-10-01 - 18:59 CharilaosTsarouchas  
Bitmapbmp logOut.bmp r1 manage 659.6 K 2008-10-06 - 12:16 EleniMountricha How to exit the telnet session
Bitmapbmp para.bmp r1 manage 1551.3 K 2008-10-06 - 12:35 EleniMountricha Mapping information in para
Bitmapbmp pumpkin.bmp r1 manage 560.1 K 2008-10-06 - 12:22 EleniMountricha The "PumpKIN" window
PNGpng rb.PNG r1 manage 2.0 K 2008-10-01 - 19:00 CharilaosTsarouchas  
PNGpng selT.PNG r1 manage 0.9 K 2008-10-01 - 19:04 CharilaosTsarouchas  
PNGpng tb.PNG r1 manage 0.5 K 2008-10-01 - 19:02 CharilaosTsarouchas  
Bitmapbmp telnet.bmp r1 manage 659.6 K 2008-10-06 - 12:23 EleniMountricha The "Utility" menu
Bitmapbmp upgadeMenu.bmp r1 manage 659.6 K 2008-10-06 - 12:21 EleniMountricha Upgrade menu in telnet
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2008-12-08 - EleniMountricha
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas 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