| Paper | Title | Page |
|---|---|---|
| MOX01 | TINE Release 4 in Operation | 1 |
|
||
|
The TINE* control system evolved in great part to meet the needs of controlling a large accelerator the size of HERA, where not only the size of the machine was a determining criterion, but also the seamless integration of different platforms and programming languages of the many applications developers. In keeping pace with new technologies and the new generation of accelerators such as PETRA3, FLASH, PITZ and associated pre-accelerators and beamlines, TINE has undergone a major “face-lift” in its most recent version, 4.0.1, where platforms such as Java and LabView are not only supported, but emphasized. In addition, TINE Release 4 integrates the video subsystem, the device layer, and central services to a much greater extent than its predecessor. We report here on many of the new features and how they are currently being used in operations.
* http://tine.desy.de |
||
|
Slides | |
| MOZ02 | The Concept of EMBL Beamline Control at Petra III | 22 |
|
||
| The EMBL is located at the DESY site in Hamburg and operates 7 beam lines at the DORIS III synchrotron. Currently the EMBL Hamburg constructs three new beam lines at the new PETRA III synchrotron. In the past the level of beam line automation is significantly increased. Control system tasks are changed to more data through put, faster reaction times and require more flexibility. The control electronic has to allow fast feedbacks and precise data synchronization. Sample changer offer higher speed and sample capacity. The transport of videos and the huge amount of experimental data via the control system requires networks with large bandwidth and high efficient control system transport protocols. The EMBL has chosen TINE as beam line control system. TINE features like the multi cast option and the efficient TINE transport protocol help to minimize the network load. The control electronic will be the real time PLC control EtherCat for motor control and data acquisition. Fast data acquisition will be performed with FPGA and PXI electronic. Presented will be the beam line control concept, the control electronic layout and the first finished applications. | ||
|
|
Slides | |
| TUZ01 | New TINE Java General Purpose Diagnostic Applications | 67 |
|
||
|
One of the strengths of the TINE* control system is the ability to easily make ‘rich-client’ applications containing that programming and display logic which is designed to expedite and enhance the operator’s or physicist’s abilities to diagnose problems and correlate results. In particular there are a large number of ‘rich-client’, general purpose applications which offer extensive interactions with the TINE standard servers and subsystems. This includes the TINE archive system, alarm system, post-mortem system, and video system, as well as scope trace analysis, multi-channel analysis and general configuration management. Available now for many years, these diagnostic applications have recently been realized as pure java applications using ACOP** beans. All applications have been honed and refined based on extensive feedback from the application users. We offer here a description of these applications, some of the novel techniques used and focus on those ‘rich-client’ aspects which cannot be achieved by configuring ‘simple-clients’ based on displayer widgets.
* http://tine.desy.de ** http://cosylab.com/pub/acop/site |
||
|
|
Slides | |
| WEX04 | An Embedded Distributed System Based on TINE and Windows CE | 148 |
|
||
| We present an embedded distributed system based on the integration of the control system (TINE) inside an embedded-PC running Windows CE RTOS. As Windows CE is not Windows and requires a cross-compilation of the source modules, porting TINE to Windows CE turned out to be straightforward, but non-trivial. Having a dedicated Windows CE TINE library allows creating device servers inside the embedded operating system, close to the hardware application layer. The embedded-PC is the master of the hardware line, where different hardware devices are connected through a real-time Ethernet field bus. On the one hand there is a low level control of this hardware performed by a set of programmable logic controllers (PLC) running in fast cycling and on the other hand there is a higher level control performed by the TINE server devices. The server is the responsible of providing an interface to the external world, exporting the functionality of the system through the Ethernet control network. It is also possible that the server acts as a TINE client of other external servers, constituting a network of embedded nodes. We present a practical development that demonstrates the proposed system. | ||
|
|
Slides | |
| WEZ01 | The TINE Common Device Interface in Operation | 154 |
|
||
|
The Common Device Interface (CDI)* is the primary device layer used in the TINE** control system. It offers a generic, database-driven view of a server’s hardware, where a hardware address, irrespective of the underlying bus, simply appears as a named device, which is accessed via the TINE client API. To date, CDI-supported busses include several CAN implementations, RS232, TwinCat***, Libera****, Siemens PLC, as well as the DESY in-house bus SEDAC. In this paper, we report on the latest features of CDI and more importantly on the first experiences of using CDI in operations, primarily in the PETRA3 pre-accelerator chain and in DC, Servo, and stepper motor control at the EMBL beamlines.
* Duval and Wu, “Using the Common Device Interface in TINE”, Proceedings PCaPAC 2006. ** http://tine.desy.de *** http://www.beckhoffautomation.com **** http://www.i-tech.si/products.php |
||
|
|
Slides |