Contents

1. Device integration into automation systems with configurable device handlerScheibelmasser, Traussnigg, Schindin, Derado

2. Test bed automation Types of device handler Device integration goals Configurable Device Handler (CDH) CDH configuration procedure CDH runtime functionality Future extensions, conclusion Contents

3. Combustion engine test and development (CAT) Control the test bed in a defined mode (test run) Evaluate and control sensors, actuators and complex devices Acquire data, calculate and store results Real time behaviour Test bed automation

4. Intelligent subsystems Measurement devices „Small“ automation systems Controlled via communication lines Test bed automation: Device categories • Simple sensors/actuators • Part of the real time data acquisition • Fully integrated in the automation system • Parameters (filter, buffer, sampling rate)

5. Uniform SW-Layer for device control and data acquisition Use of Platform Adapter interfaces for OS and lower OSI/ISO-Layer access Implements interfaces to the Automation System‘s Device Framework (PUMA) Test bed automation: Device handler

6. Synchronisation Supports states and transitions of the Device Framework Implementation of mandatory methods Abstract method definitions Device specific implementation Test bed automation: Handler Functions • Interface • Data: System Channel • Commands: Activation Objects Visualisation(GUI)

7. Test bed automation Types of device handler Device integration goals Configurable Device Handler (CDH) CDH configuration procedure CDH runtime functionality Future extensions, conclusion Contents

8. Device Specific Handler: Handler programmed for a special measurement device Functionality fixed (hard coded) Types of device handler • Configurable Device Handler: • Generic PUMA Device Handler • “Configuration instead of programming” • Device functionality given by means of parameterisation

9. Test bed automation Types of device handler Device integration goals Configurable Device Handler (CDH) CDH configuration procedure CDH runtime functionality Future extensions, conclusion Contents

10. CDH Device integration goals • Low integration costs and effort • Focus on device functionality • Consideration of automation and not of a specific automation system • Improved costumisation • High flexibility • No programming skills • Support of standards (e.g. ASAM-GDI) • Advantages of Scripting and Labview

11. Test bed automation Types of device handler Device integration goals Configurable Device Handler (CDH) CDH configuration procedure CDH runtime functionality Future extensions, conclusion Contents

12. Configurable Device Handler • Configurable Device Generator • Offline component for configuration (Wizard) • Mesaurement Device Description • Measurement Description File • Configurable Device Engine • Online interpreter engine • Configurable Device Panel • Online Handler visualization (generic GUI)

13. Test bed automation Types of device handler Device integration goals Configurable Device Handler (CDH) CDH configuration procedure CDH runtime functionality Future extensions, conclusion Contents

14. CDH configuration procedure : General • Device integration assumptions: • Knowledge of device states, functions and communication protocol telegrams • Knowledge of PUMA Open Standard Commands and the expected device behaviour • Idea for the implementation of the Standard Commands (e.g Initialize, Measurement ...) • Device integration definition steps: • Physical Line, Variables, Telegrams, Sequences, MDD-File

15. Physical Line Definition • RS232, Ethernet (TCP/IP, UDP) • COM-Port, Baudrate, Frame • Port, IP-Address • Timeout CDH configuration procedure : Line CDG-wizard guides the device integrator through the necessary step

16. CDH configuration procedure : Variable • Device Variable Definition • Variables are gained from device protocol telegrams • Systemchannels are generated according to Variable definition • Systemchannels are connected to all PUMA components Value: FB_Temperature Unit: °C I/O-Type: Output Type: Float Initial Value: 0 Minimum: -10 Maximum: 70

17. CDH configuration procedure : Telegram • Telegram Definition • Telegrams are used to control the device, to set parameters or to inquire values from the device • Send/Receive-Telegram definitions enables CDH the fill in/extract variables to/from the device protocol Send telegram: [STX] AWRT K0 [ETX] Receive telegram: [STX] AWRT 00.275[ETX] Send text: <02> AWRT #channel#<03> Receive text: <02> AWRT #error_status# #measurement_value#<03>

18. CDH configuration procedure: Sequence • Sequence Definition • Sequences separated in single (start, end) and cyclic activities • Sequences are a list of telegrams, conditions and functions in an logical order • Sequences are used as complex PUMA commands • Mandatory Standard Commands acts as PUMA synchronisation

19. CDH configuration procedure : Global • Global Condition • Necessary reactions on every protocol frame • Useful for error- or checksum handling • Reduction of telegrams and conditions in sequences

20. Test bed automation Types of device handler Device integration goals Configurable Device Handler (CDH) CDH configuration procedure CDH runtime functionality Future extensions, conclusion Contents

21. MDD Measurement Device Description File CDH runtime functionality • Device communication based on parameterisation, stored in MDD-File

22. Test bed automation Types of device handler Device integration goals Configurable Device Handler (CDH) CDH configuration procedure CDH runtime functionality Future extensions, conclusion Contents

23. Future CDH steps • Calculation capability • Device auto detect • Multiline connection • Binary protocol • Fieldbus support • ASAM-GDI standard

24. Conclusion • CDH as a new approach for device integration • Excellent practical experiences • Integration on customer site, even for third party devices • Increased quality of device integration • Decreased integration time and costs • Integration possible in the office with simulator … Device Integration got very easy (if you understand the device well)

25. Thank you for your attention !