Pixel Detector Control System1st training session

May 10, 2007

OverviewCANbus and ELMB

Pixel DCS Computers in the pitELMB integration

ELMB control CAN PSU

Susanne Kersten, Wuppertal University

OverviewOverview

Hardware of the Pixel Control System

Further Hardware of the Pixel Control System

What is missing on the overview figure:

• Aux Power Supplies

PP2 PS (WIENER PS)PP3 PS (custom made device to power BBIMs)CAN PSU

• Opto PP3 (patch panel)

• Monitoring of DAQ hardwareVME crate control (via CANbus interface)BOC parameters (via DDC, DAQ-DCS-Communication)BOC Temp. monitoring (via CAN)

• Details of Interlock SystemLogic UnitInterlock Distribution BoxesBOC-I-BoxPP1 BoxOpto Heater Ilock & Beampipe BakeOut Ilock

Software of the Pixel Control System

Pixel specific termini:FITs: front end integration tool functional orderSIT: system integration tool geographical/detector oriented

order

DAQ

conditions

connectivity

configuration

FITs

FSM

SIT

ATLAS DCS

Hardware 1 Hardware 2 Hardware 3 Hardware n

DDC

DCS software

• In most cases CANbus is used to establish communication between hardware and DCS PCs (see next section)

• DCS software is based on PVSS (ProzessVisualisierungs- und SteuerungsSystem, commercial tool, used CERN wide)

• On each DCS PC several PVSS projects can be running, independent of each other

• The FITs, special PVSS (sub)projects, communicate with the hardware, e,g, a LV power supply, a HV power supply or an ELMB. These FITs will be handled in 1st and 2nd session of the DCS training.

• Higher level control software:• SIT System integration tool (3rd session)• FSM (finite state machine) • RDM manager, PVSSdataViewer,

PVSS2COOL etc… • DDC (DAQ DCS Communication)

Next DCS training sessions

Introduction to Introduction to

CANbusCANbus

and ELMBand ELMB

Control Area Network

Serial fieldbus, communication standard chosen for its reliability

One needs • a CAN interface in the PC• cables (‘CANbus’), for short distances

typically sub D9 connector and flat cable• CANnodes connected to the bus: ELMB (subject of this session)• termination of CANbus cable• In some cases a CAN power supply unit

(CAN PSU)

3 different interfaces in use:• Peak for iseg HV System• Kvaser (up to 4 ports) • Systec USB (up to 2* 8 ports)

Embedded Local Monitor Board

Altogether we have 630 CANnodes in the pixel DCS

485 are of type ELMB

ELMB:• Standard ATLAS frontend IO unit for DCS• ATMEGA128 microprocessor• 24 digital IO channels• 64 channel, multiplexed ADC 16 bit

with selectable range• CAN interface• speaks CANopen ELMB top view (credit card size)

Settings of an ELMB node

don‘t touch!

Figure taken from ElmbUserGuide (J. Cook)

Speed depends on max. cable length, 125 kbit/s ↔ max. 250 m

No identical node IDs on the same CANbus!Not more than 32 nodes on one busDon‘t mix CAN nodes of different flavour on one bus

Typical CANbus

• A CAN bus for ISEG or VME crate control looks the same besides that there is no CAN PSU required

• Please note the CAN PSU is necessary for the operation of the ELMB, but not a sufficient requirement for operation of some DCS crates!

CAN interface

CAN interface

CAN interface

120Ω ELMBELMB

ELMB

ELMBELMB

ELMB

ELMB

ELMBELMB

DCS crate

120Ω

long, thickCAN cable(CAN signals + CAN power lines)

DCS PC CAN PSU

thin CAN cable(CAN signals)

OPC server / client

• Protocol on the CANbus is CANopen

• The ELMBs are communicating via CANbus to the OPC server

• Name: CANOPEN25+.exe (see task manager)

• The clients (PVSS projects, see below) connect to the OPC server in order to send or receive data

• Client is one of the ‚managers‘ (PVSS processes)

client

Winhost programs

Simple tool to check whether your ELMB is responding properly

For Kvaser cards: Winhost+.exe

For systec: Winhost+Rel.exe

proper icon on desktops

select port = CANbus ID

Bus scan!

check whether your ELMB has shown up!

Always Kvaser+

check if the number of nodes is as expected

Pixel DCS ComputersPixel DCS Computers

In the PitIn the Pit

Pixel DCS-net in the Pit

Our computers: PCATLPIX…..

e.g. PCATLPIXSCS (Sub-detector Control Station)

• https://twiki.cern.ch/twiki/bin/view/Atlas/PixelDCS

• → PCs in USA15

status May 8, 2007

Always check the actual status on the wiki!!!

Pixel DCS-net in the Pit

Always check the actual status on the wiki!!!

How to log in

• there is no common pixel account• ask susanne.kersten@cern.ch for access rights• then log in with nice username and password

Via terminals directly connected to PCs: • Location of PCs in rack Y.12-14.A2 in USA counting room• In neighbouring racks 10-14 and 11-14 two screens • Double click ‘ctrl’ shows you which machines are connected to the

screen and allows you to make your choice• Your personal username/password

How to login

Or via double remote desktop:

(1) remote desktop to cerntsatldcs01.cern.ch (your nice username/passwd)

→ remote desktopSelect the PC(again nice username/passwd)

(2)

Access to PVSS projects

• Look on the DCS wiki page for the required project name • check in the PVSS Project Administration (desktop) whether the

project is running, should be!

• if it not around, start your project via the Services console (desktop)

• the related user interfaces are either started – via a shortcut from the desktop (e.g SCOL UserInterface on the SCOL

machine)or

– from the PVSS Project Administration Console (.e.g. ATLASPixDCS_ELMB_userInterface on the PP2 machine)

• before going home, stop the user interfaces and always Log Off (this cleans up things properly)

ELMB IntegrationELMB Integration

Construction kit of DCS crates

• A DCS crate (e.g. SC-OLink, BBIM etc..) consists of 3-6 identical building blocks, which are installed in one 19“ crate

• boss of each block is an ELMB for control and communication• Add-on cards (e.g. ‚I-Box‘, SC-OL card) are the workers• Input/output signals are distributed by fitting front/backpanel• CANbus is internally connected in serial to all CANnodes

ELMB naming scheme

blocks of DCS crates (= ELMB = CANnode) are reflected in the DCS naming scheme:

Rack nr. (A2: USA counting room, S2: US counting room, X..: ATLAS cavern)

Y3303X1_BBIM03A Y1214A2_SC06C Y1406S2_LV_PP4_08C Crate type crate and block nr

Exception PP2 crates’ namings: PP2_AP2_621 A or C side, platform 1…6, box nr xx

Definition of a CANbus

(1) Define a name (CAN0), the type of interface (always KV) and the number of the CAN (0).

Start menu

(2) Apply changes! Creates the internal PVSS datapoints

(3) Proceed with ELMB definition

Don‘t try to change the name of a CANbus or node! Remove it and define a new one.

ELMB definition

1. Define - Name of ELMB- CAN to which it is connected- Node id- ELMB type

2. Apply changes (creates internal datapoints)

3. Prepare internal configuration for OPC communication

4. Store configuration and restart OPCserver

1

5

4

32

6

ELMB ControlELMB Control

(including introduction to different (including introduction to different

DCS crates)DCS crates)

ELMB section

ELMB section

≠0 !!

Pixel standard settings

state

running √

stopped (on purpose)

Pre-operational: ADC not working

disconnected: cable missing, wrong ELMB node id etc..

disconnected (OPC): OPC client or Server dead

ELMB section will be found in all ELMB based DCS devices

Network Management

Building Block Interlock & Monitor

• monitors the temperatures of detector modules, opto boards and PP2 crates, using 10 kΩ NTCs

• 1 crates consists of 4 BBIM, each owning 4 ‚I-Boxes‘• I-Box creates interlock signals when temperature level is

exceeded (40 °C for detector modules a. opto boards, 60 °C PP2 crates)

• Location at PP3

BBIM front BBIM back

BBIM

ELMB section Monitoring section

Temperature reading

Vref for the NTCs: 2.5V

Current of I-Box

To create a test interlock signal via digital output port

Black field: OPC quality bit is bad, no actual value or value very close to zero

PP3 Power

The one with the blue LEDs, indicating that the channel is operating

Powers NTCs and Iboxes of BBIM

One channel / BBIM crate

ELMB for monitoring only

To check Vmon/Imon with a DVM Front view of the PP3 PS

PP3 power crate

typically 12 Vcurrent < 500 mA depending on the loadint. supply voltage for ELMB

should be 3.3 V!

Building Block Monitoring

Little brother of BBIM: 2 blocks for temperature monitoring +

1 block for humidity monitoring (still in work)

Connected to temperature sensors (NTC) distributed in the pixel volume

Panel of a BBM temperature monitoring block

Temperature values

Vref for the NTCs: 2.5 V

Derived from the CAN power, no separate PS

LV-PP4

• Splits Vdd and Vdda coming from a Wiener LV power supply onto 7 lines• Consists of 3 identical blocks, each block can handle 4 Wiener channels • Measures current per line

(Imon up to 3 A, calibrated up to 2 A, rms < 5 mA)• For debugging purposes also the current in the return line can be

measured, when a second opto isolator card is added

Front of LV-PP4

Backpanel of LV-PP4

LV-PP4

• screenshot

int. supply voltage for ELMB should be 3.3 V!

Current measurement per channel, Zero suppression (Imon < 10 mA)sum is a calculated value

1 Wiener channel, return current is not measured

Supply and Control for the OptoLink

• Power supply system for the opto boards• Provides Vpin, Viset and Rst-Opto via opto PP3 to the opto boards• Provides Vvdc via the regulator station to the opto boards• SC-OLink crate consists of 4 blocks, each powering 4 opto boards

Vpin (20V, 20 mA)

Viset (5V, 20 mA)

Vvdc (10V, 800 mA)

Rst-Opto

SC-OLink

To toggle between on/off

Acts on all 3 voltages of 1 SC-OLink channel

Voltage/current monitoring value

Status ERROR, if nominal condition differs from the actual one

nominal value

Regulator Station ‘PP2’

• The remotely controlled regulator station is located at patch panel 2 (PP2, inside the muon chambers)

• One regulator station can house up to 12 regulator boards, each board provides Vdd and Vdda for a half stave and Vvdc for the related opto board

• In the middle of each regulator station a controller card is installed, which provides control via a FPGA and communication to the outer world via CAN interface of ELMB

• Input voltage to the regulator channels is provided by the WIENER LV crates

• Controller requires +/- 15 V, this is also provided by some specially configured Wiener powers supplies (but installed in a different crate and controlled by a separate PVSS project)

Integration of PP2

Version of regulator board, normally 4

Boards installed in the PP2 crate

Besides the standard integration parameters

Control Panel of PP2

12 boards are defined, selection of boards via tab, board 8 is shown

PP2 station S21

channel

boardcrate

ELMB section

Msg field

Channel commands

Make sure that the channel you want to control is powered! (Wiener/SC-OLink)

Only if the channel is powered it is ensured that the commands are executed and the PP2 panel shows the actual state of the PP2 crate! To check if the channel is powered have a look into the SIT. The detector unit to which the board corresponds can easily be found out via the toolTipText of the ChannelName.

• Channel can be turned on/off• Desired voltage can be set 1.5 -2.5 V for Vdd, Vdda 1.9 to 3.1 V for Vvdc• Monitor values

(If no unit is displayed the channel is not marked as “calibrated” and possibly pure ADC counts are displayed)

Board commands

2 temperatures/board measured, as well as Vref.

Kill/Unkill: A “killed” board has no output voltage, but if the board is unkilled again the inhibit-state will determine if there is an output voltage or not. (see next slide)

“Trimmers” button. To set the default voltages for all channels of this board. (The default trimmer positions can be checked in the Calibration panel).

“Off”/“On”: inhibits/uninhibits all channels of this board. (a series of 16 single commands)

killed PP2 board

A channel which is uninhibited ON(K) will deliver a voltage as soon as the board is unkilled, OFF(K) will stay off after unkill

‚high speed‘ Crate commands

consist each of one internal PP2-command:

• Kill/Unkill: Kill or Unkill all boards of the PP2 station

• GU (“General Uninhibit”): uninhibit all channels of all boards

• Min: sets all the Trimmers of all the boards to the Minimum

Composed crate commands

• combinations of internal PP2-commands, therefore more time-consuming.

• Reset: was intended to synchronize PP2 and PVSS. Should normally not be used. (double click). It sends the PP2commands KillAll/GU/Min, and starts the readout for all boards.

• Recover: will KillAll, then set the values known to PVSS (Inhibit, Vset) and start the readout for all boards.

• Inh: will Inhibit all channels of all boards

• Init: will KillAll, Inhibit all channels and set all the Trimmers to default

• Cal: will open the Calibration panel for all the crates defined on this system

• GoMin/Direct: determines how the Trimmers are set. If the button shows “GoMin” the Trimmer will be set to the Minimum and afterwards to the Trimmer position corresponding to the desired voltage. If the button shows “Direct” than the necessary steps to reach the new trimmer position is calculated from the previous trimmer position and set directly. “GoMin” should be used if one suspects that the trimmer position of PP2 crate and PVSS is not synchronized. But since these are two commands and the total number of trimmer steps moved is larger, this will take more time than in “direct mode”

ELMB section

green: board is readout yellow: no readout white: board not defined

Red: board is killed

The Regulator ELMB has no NodeGuarding, under construction state: alive or not responding

Blue: PDO is active white. PDO is inactive

=0! Start!

128!

PDO routine inside ELMB responsible of reading of values

During command execution:

PDO should inactive, (white)PP2 mode: 0

To change the above settings, start child panel

PDO (process data object): for exchange of process data inside CANopen

Setting of the PDO routine

For changing which boards are read out/killed, click the corresponding squares. If the pattern matches the desired one, the button “ReadOut” or “Kill” must be pressed.

After every power cycle of the controller the ReadOut-Pattern must be sent!

Otherwise no board will be read out and no values sent to PVSS, even if the routine is running.

Stop/start of PDO routine

Execution of commands

Command execution in progress

If the panel gets “stuck”

Watchdog

• Each standard (non PP2) ELMB has its watchdog, starts barking when ELMB does not send heart beat

• If the watchdog is happy, ELMB is alive, OPC server and client are working properly

Work on watchdogs still ongoing!

CAN PSUCAN PSU

CAN PSU

CAN PSU provides 2 voltages/CANbus:

• Vcan for the CAN controller

• Vad for the analogue and

digital circuits of the ELMB

Front view of 2 CAN PSUs

CAN PSU

(1) In the starting panel (left) you can select the ELMBs controlling the CAN PSU

Right: 2 ELMBs for 2 crates are displayed

(2) Double click here, gives you the monitoring panel on the next slide

Standard CERN software used: fw (frame work)

CAN PSU

Right click opens a small panel to switch on/off the corresponding bus

Power cycle of the CANbus is used as a hardware reset to all ELMBs on the bus

Trouble shooting

ELMB disconnected• Use winhost program to verify connection• (stop OPC client first)• If no response, check power of CANbus, power cycle the related

CANbus, check cabling as far as possible• If winhost works, restart OPC client, go back to PVSS, check in the

integration panel for the correct node

No actual values in ELMB• Synchron. Interval ≠ 0 (for non PP2 ELMBs)?• power supply of DCS crates turned on?

Dokuments + Help

• Documents:

https://twiki.cern.ch/twiki/bin/view/Atlas/PixelDCS#Manuals

• Comments to susanne.kersten@cern.ch

• DCS experts permanently at CERN:– Francesco Bellina– Kerstin Lantzsch

• DCS support: 16 2231