16/17 december 2004 Tango-ds project Vue de Soleil le 1 er décembre 2004

16/17 december 2004

Tango-ds project

Vue de Soleil le 1er décembre 2004

16/17 december 2004

Tango-ds project

Avancée du projet : quelques photos

Equipements techniques bât T3Novembre 2004

16/17 december 2004

Tango-ds project

Planning

Plannings are shifting due to building construction

Machine zones are some months lateWe still do not have installation dates

we can trustTL1 installation

should have began in September has been posted in november, december,

january ..

16/17 december 2004

Tango-ds project

Planning Général

16/17 december 2004

Tango-ds project

Linac : L’installation par THALES a commencé début octobre

Tunnel Linac Hall RF Linac


16/17 december 2004

Tango-ds project

On the Controls side

Device Server for TL1 Are ready and have been tested in lab

We are waiting for the installation

Hardware architectures and Dservers have are 90% finished for Booster

Work is going on for Storage Ring

We also work in parallel for beamlines Project definition for 10 beamlines LUCIA Diffractometers with hkl routines Scienta analysers

16/17 december 2004

Tango-ds project


16/17 december 2004

Tango-ds project


la cabane expérimentale

la cabane optique

La ligne LUCIA au SLS inaugurée le 22 juin 2004

avec un contrôle au standard SOLEIL

16/17 december 2004

Tango-ds project

Diffractomètre 6C Kappa pour les lignes CRISTAL et DIFFABS


16/17 december 2004

Tango-ds project

Gun chamber

Ion pump

FCT

Lens

Le canon du LINAC a produit ses premiers électrons le 23 Septembre 2004


16/17 december 2004

Tango-ds project

The tango-ds SourceForge project

With the help of Sylvain Dupuy

16/17 december 2004

Tango-ds project

Motivations to share DeviceServers

For TANGO dancers : Share code & experience on what represents an important part of the daily work of our Control

groups : interfacing hardware For TANGO middle/long term future

be attractive in the Controls community labs because, (at least for commercial Hardware) Controls can come “for free”

• May help to diffuse TANGO in small research laboratories with few software development forces Goal : Get off the shelf “control components”

already tested and “bugs free” in other institutes BUT also that can be easily

• recompiled in other institutes• modified in other institute

• installed & configured

on what is an important

16/17 december 2004

Tango-ds project

Tango-ds CVS repository What should we store in SourceForge repository ? For now DeviceServers

low-level DeviceServers • Serial Line• GPIB• I/O boards , etc ..

standalone DeviceServers based on commercial hardware• ex: Rhode& Schwarz RF master clock• Agilent signal generator• I Tech BPM

generic “Process DeviceServers”• ScanServer

In a word everything than can be used in a different context than the institute that developped the DServer

16/17 december 2004

Tango-ds project

Tango-ds CVS repository

We should not store DeviceServer driving specific Hardware

• ex : the RF cavity of SOLEIL’s booster specific process

• ex : A Device Server driving the Energy of the LUCIA beamline

16/17 december 2004

Tango-ds project

The CVS Hierarchy

The existing one should be changed !! The proposed one is the following : $CVSROOT/Motion/

DeviceServers related to motion systems : for instance Axis or Slits controls

$CVSROOT/Acquisition/: DeviceServers related to acquisition boards (Counter/Timer

boards, Digital or Analog I/O boards ) , or acquisition procedures (ScanServer for instance)

$CVSROOT/Communication/ DeviceServers related to communication buses or protocols

(RS232, GPIB, MODBUS, Siemens S7, OPC, etc …) $CVSROOT/Instrumentation/

DeviceServers for controlling instruments (Keithley PicoAmmeters, Agilent WaveFormGenerator, Multi Channel Analysers, etc ...)

$CVSROOT/Calculation/ DeviceServers providing calculations (Data fitting, hkl routines for

diffractometers control, etc ..)

16/17 december 2004

Tango-ds project

The CVS Hierarchy

$CVSROOT/Process/ DeviceServers driving generic processes : Generation of "software

waveforms" for ramping values on group of devices, … $CVSROOT/Vacuum/:

DeviceServers related to vacuum systems : ion pumps, vacuum gauges, vacuum valves, residual gas analysers etc...

$CVSROOT/PowerSupplies/: DeviceServers related to commercial power supplies : Brücker,

Danfisik, etc $CVSROOT/BeamDiag/:

DeviceServers related to commercial beam diagnostics systems : Xbpm, libera bpm, current monitors etc

$CVSROOT/Interlock/: DeviceServers related to generic interlock, Daresbury PSS server.

16/17 december 2004

Tango-ds project

The hierachy for each Device Server

/my_deviceServer/src/ : the sources (*.cpp and *.h) generated by POGO (without the

binaries) A Makefile (for linux) and/or a Makefile.VC (for WIN32)

/my_deviceServer/doc/ (/my_deviceServer/doc/doc_html) :doc generated by POGO DeviceServerUsersGuide.doc:

• English Users guide documentation in Word format. And/or DeviceServerUsersGuide.pdf

/myDeviceServer/scripts/ : scripts that could be used for testing the DS or to declare

and configure it in the TANGO Control System

16/17 december 2004

Tango-ds project


/myDeviceServer/examples/ : Source examples explaining a particular usage of

the DeviceServer or client code example

/myDeviceServer/include/ : specific files to be included which are not

generated by POGO

/myDeviceServer/lib/ : specific library(ies) which are necessary to

compile the DeviceServer

/myDeviceServer/configuration/ : files (for instance firmware, …) which may be

necessary for configuring the hardware.

16/17 december 2004

Tango-ds project


/myDeviceServer/gui/ : javabeans or graphical components used

for the Man Machine Interface of the Device

/myDeviceServer/README : the famous file for lost people.

myDeviceServer/ReleaseNote.txt : textual file describing changes from differents

releases

16/17 december 2004

Tango-ds project

Branch policy

Developpement should be done in a single CVS Branch

When : a major change is planned (modification of

Tango interface or when the code has to be deeply rewritten), a new branch must be created by the

developer During some time, 2 (and even more) branches may coexist

16/17 december 2004

Tango-ds project

Release policy

Each release must be taggedOfficial releases must be tagged like thisRELEASE_{major version#}_{minor version#}

16/17 december 2004

Tango-ds project

HEAD Branch

RELEASE_1_0

RELEASE_1_1

RELEASE_2_0

DServer developer remains in same branch for

Bugs fixes Internal implementation changes No need to change Branch Just Commit And Release

Cvs Administrator Creates Official RELEASE Web doc generation Deploiement issues on target system fixed

Dserver developper creates branch Driver or library changes Tango Interface modification Goal is to protect Production Release (RELEASE_1_1) from codes changes

RELEASE_1_2

RELEASE_2_4Dserver developper merges code To return in HEAD Branch When RELEASE_1_X is obsolete and could be definitively closed

RELEASE_2_1

RELEASE_2_2

CVS Administrator creates Module in CVS Repository

According to CVS hierarchy map On Internal CVS or SourceForge according to Dserver

BE CAREFUL :This closure of RELEASE_1_Xbranch is definitiveand should be done only whenno more RELEASE_1_X Device arein production

At this stage, 2 Official Releases (1_X &2_X) are available and are still opened

Dserver Developper

CVS Admin

Documents

16/17 december 2004 Tango-ds project Vue de Soleil le 1 er décembre 2004