Upload
naomi-hembrough
View
216
Download
0
Tags:
Embed Size (px)
Citation preview
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20041/25
Device integration into automation systems with configurable device handler
Scheibelmasser, Traussnigg, Schindin, Derado
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20042/25
Contents
• Test bed automation• Types of device handler• Device integration goals • Configurable Device Handler (CDH)• CDH configuration procedure• CDH runtime functionality• Future extensions, conclusion
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20043/25
Test bed automation
•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
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20044/25
Test bed automation: Device categories
Intelligent subsystems
•Measurement devices•„Small“ automation systems
•Controlled via communication lines
Simple sensors/actuators
•Part of the real time data acquisition
•Fully integrated in the automation system
•Parameters (filter, buffer, sampling rate)
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20045/25
Test bed automation: Device handler
•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)
Device 2
Automation System
Device Framework
Device Handler
Device 1 Device 3
Platform Adapter
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20046/25
Test bed automation: Handler FunctionsSynchronisation
•Supports states and transitions of the Device Framework•Implementation of mandatory methods•Abstract method definitions•Device specific implementation
Visualisation (GUI)
Interface• Data: System Channel
• Commands: Activation Objects
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20047/25
Contents
• Test bed automation• Types of device handler• Device integration goals• Configurable Device Handler (CDH)• CDH configuration procedure• CDH runtime functionality• Future extensions, conclusion
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20048/25
Types of device handler
Device Specific Handler:• Handler programmed for a
special measurement device• Functionality fixed (hard coded)
Device 2
Automation System
Device Framework
Device 1 Device 3
Platform Adapter
Device SpecificHandler
CDH(Configurable
Device Handler)
Configurable Device Handler:• Generic PUMA Device Handler
• “Configuration instead of programming”
• Device functionality given by means of parameterisation
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 20049/25
Contents
• Test bed automation• Types of device handler• Device integration goals• Configurable Device Handler (CDH)• CDH configuration procedure• CDH runtime functionality• Future extensions, conclusion
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200410/25
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
CDH
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200411/25
Contents
• Test bed automation• Types of device handler• Device integration goals• Configurable Device Handler (CDH)• CDH configuration procedure• CDH runtime functionality• Future extensions, conclusion
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200412/25
Configurable Device HandlerConfigurable Device Generator
• Offline component for configuration (Wizard)
Device 2
Automation System
Device Framework
Device 1 Device 3
Platform Adapter
Configurable Device Handler (CDH)
Engine (CDE)
Generator (C
DG
)
Pan
el (
CD
P)
MeasurementDeviceDescriptionFile (MDD)
Configurable Device Panel
• Online Handler visualization (generic GUI)
Configurable Device Engine
• Online interpreter engine
Mesaurement Device Description
• Measurement Description File
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200413/25
Contents
• Test bed automation• Types of device handler• Device integration goals• Configurable Device Handler (CDH)• CDH configuration procedure• CDH runtime functionality• Future extensions, conclusion
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200414/25
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
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200415/25
CDH configuration procedure : Line
CDG-wizard guides the device integrator through the necessary step
Physical Line Definition
• RS232, Ethernet (TCP/IP, UDP)
• COM-Port, Baudrate, Frame
• Port, IP-Address
• Timeout
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200416/25
CDH configuration procedure : VariableDevice 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
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200417/25
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 0 0.275[ETX]
Send text: <02> AWRT #channel#<03> Receive text: <02> AWRT #error_status# #measurement_value#<03>
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200418/25
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
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200419/25
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
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200420/25
Contents
• Test bed automation• Types of device handler• Device integration goals• Configurable Device Handler (CDH)• CDH configuration procedure• CDH runtime functionality• Future extensions, conclusion
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200421/25
CDH runtime functionality
Device communication based on parameterisation, stored in MDD-File
Measurement Device Description
File
MDD
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200422/25
Contents
• Test bed automation• Types of device handler• Device integration goals• Configurable Device Handler (CDH)• CDH configuration procedure• CDH runtime functionality• Future extensions, conclusion
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200423/25
Future CDH steps
• Calculation capability
• Device auto detect
• Multiline connection
• Binary protocol
• Fieldbus support
• ASAM-GDI standard
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200424/25
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)
campus02.at
don't stop thinking about tomorrow
DI Anton Scheibelmasser
Setubal 28.08.2004ICINCO 200425/25
Thank you for your attention !