Layer 7. Application Layer. Chapter 2.6. Layered model automation system. Application Process. Application. Management. Data Link Physical

Size: px

Start display at page:

Download "Layer 7. Application Layer. Chapter 2.6. Layered model automation system. Application Process. Application. Management. Data Link Physical"

Jacob Newman
5 years ago
Views:

1 Chapter 2.6 Layer 7 Application Layer 1 Layered model automation system Application Process Application Data Link Physical Management 2

com) EtherNet/IP and DeviceNet 4 Source:

2 PROFINET 3 Communication channel with PROFInet.(ref: EtherNet/IP and DeviceNet 4 Source: CIP: Common Industrial Protocol

3 CANOpen Communication structure is defined by the application Suitable for cars Special solution for each node Idea: make it more general, that a system integrator can use components without reprogramming them Higher Level Protocols (Layer 7) Examples Device Net, CANOpen, CanKingdom,... CANOpen Forced by smaller companies CiA Can in Automation 5 Protocol Layer Interaction Approach: Objects Transmitting Device CANopen Application Layer CAN Data Link Layer CAN Physical Layer Object at Index ID+Data ID+Data Recessive Recessive dominant Receiving Device CANopen Application Layer CAN Data Link Layer CAN Physical Layer 6

4 How to describe Objects Describtion available on the device Object directory (e.g. CANOpen) Description available outside the device (description file) EDS (Electronic Data Sheet, DeviceNet) GSD (Profibus, Profinet) 7 CANOpen Device Model CAN Communication SDO PDO Special Function Objects NMT Objects Object Dictionary Data Types Communication And Application Objects Application Application Program Device Profile Implementation I/O 8

5 Object Dictionary 9 Ordered List to Structure the Device Information can be accessed by Index Sub index All Information can be accessed in a Client- Server concept using a peer to peer communication using SDO s The application can read and write to the Object dictionary Process-PDO are transmitted by the device. The content and transmission behaviours ( rate, ID, mapping) is defined in the Object dictionary Behaviour of a device can be parameterised Need: Device-Profiles Object Dictionary 10 Index Object-Types 0 reserved F Static Data Types F Complex Data Types F Manufacturer Specific Data Types F Device Profile Specific Static Data Types F Device Profile Specific Complex Data Types 00A0-0FFF Reserved FFF Communication Profile Area FFF MAnufacturer Specific Profile Area FFF Standardized Device Profile Area A000 - FFFF Reserved for future Use

6 Objects (Example) Index Information 1000 Device type 1001 Error-Register 1002 specific status register 1003 List of errors 1005 COB-ID of SYNC 1009 Hardware-Version 100A Software-Version 100B Node-ID 100E COB-ID Node guarding 1011 Restore default parameter F Parameter for SERVER SDO FF Paramerer for Client SDO FF Parameter for Receive-PDO FF Mapping receive PDO's FF Parameter Transmit PDO 1A00-1BFF Mapping transmit PDO 11 Device-Profiles CiA 401: Device profile for generic I/O modules CiA 402: Device profile for drives and motion control (servo controller, stepper motor controller, frequency inverter) CiA 404: Device profile for measuring devices and closed-loop controllers CiA 406: Device profile for encoders (rotating and linear) CiA 408: Device profile for proportional valves and hydraulic transmissions CiA 410: Device profile for inclinometers CiA 412: Set of device profiles for medical devices (e.g. colimator, dosimeter) CiA 413: Set of device profiles for truck gateways CiA 414: Set of device profiles for weaving machines (e.g. feeder) CiA 415: Application profile for road construction machine sensors CiA 416: Application profile for building door control systems CiA 417: Application profile for lift control systems CiA 418: Device profile for battery module CiA 419: Device profile for battery charger CiA 420: Set of device profiles for extruder downstream devices CiA 421: Application profile for train vehicle control networks (intergration platform on vehicle sublevel) CiA 422: Application profile for municipal vehicles (e.g. garbage trucks) CiA 423: Application profile for power drive systems (e.g. diesel engine) CiA 424: Application profile for rail vehicle door control systems CiA 425: Set of device profiles for medical add-on devices (e.g. contrast media injector) CiA 426: Application profile for exterior rail vehicle lighting CiA 430: Application profile for auxiliary rail vehicle devices (e.g. cooling fans, engine pre-heating) CiA 433: Application profile for interior rail vehicle lighting CiA 444: Set of device profiles for crane add-on devices (e.g. spreader) CiA 445: Device profile for RFID reader CiA 446: Interface profile for AS-Interface gateways 12

7 Communication Objects Process Data Objects (PDO) (each node) Service Data Objects (SDO) (each node) Special Function Objects Synchronisation Object (SYNC) (one node) Time Stamp Object (one node) Emergency Object (EMCY) (each node) Network Management Objects NMT Message (one node) Boot Up Object (one node) Error Control Object (each node) Identifier have to be assigned! 13 PDO (1) Transmission Modes 14 Process data, build as described in OD. Synchronous and asynchronous transmission Sync-Object Synchronous PDO Synchronous Window length Asynchronous PDO Transmission types: 0: after SYNC, only if a defined event occurred before 1: after every SYNC N: after every N-th SYNC

8 PDO (2) Trigger modes Event driven Device specific event, defined in Device-Profile SYNC Object for synchronous PDO Timer driven Device specific event Specified time has elapsed Remotely requested Remote request 15 SDO (1) SDO s provides access to the Object Dictionary Upload and Download is possible with a peerto peer communication Exchange of small Parameters is defined Exchange of large Blocks is defined Protocol is defined OD-entries can be write-protected Parametration of a Device is possible 16

9 CANOpen Network Node ID NMT Master Node-ID 2 Slave Bus lines Node ID 3 Slave Node ID 4 Slave Each node has a unique node-id (often manually defined) Identifier for Communication objects depend on Node-ID 17 Identifier (Predefined) Function Code Node-ID Function Code to distinguish between different objects Node ID 0 is reserved, is interpreted as Broadcast 127 nodes in a network are possible 18

10 Predefined connection set 19 Object Function Code (binary) resulting COB-ID NMT (0x00) SYNC (0x80) TIME STAMP (0x100) Peer to Peer Objects Emergency x081-0x0FF PDO1 (tx) x181-0x1FF PDO1 (rx) x201-0x27F PDO2 (tx) x281-0x2FF PDO2 (rx) x301-0x37F PDO3 (tx) x381-0x3FF PDO3 (rx) x401-0x47F PDO4 (tx) x481-0x4FF PDO 4(rx) x501-0x57F SDO (tx) x581-0x5FF SDO (rx) x601-0x67F NMT Error Contro x701-0x77F Network Initialisation Configuration of all device parameters Including communication parameters (via default SDO) (Optional) Start transmission of SYNC, wait for Synchronisation of all devices (Optional) Start Node-Guarding Stetting of all nodes to Operational State 20

11 State Diagram of a Device Reset Comm. Initialisation Pre-Operational Start Power on Operational Enter Pre-Op Enter Pre-Op Start Stop Stop Stopped Reset Node 21

Application Layer. Chapter 2.6. Layered model automation system. Application Process. Application. Data Link Physical.

Application Layer. Chapter 2.6. Layered model automation system. Application Process. Application. Data Link Physical. Chapter 2.6 Layer 7 Application Layer 1 Layered model automation system Application Process Application Data Link Physical Manage ment 2 1 PROFINET Layer 3.6. Application L 3 Communication channel with