- •Important Comments
- •Legal Principles
- •Copyright
- •Personnel Qualification
- •Intended Use
- •Symbols
- •Font Conventions
- •Number Notation
- •Safety Notes
- •The WAGO-I/O-SYSTEM 750
- •System Description
- •Technical Data
- •Manufacturing Number
- •Component Update
- •Storage, Assembly and Transport
- •Mechanical Setup
- •Installation Position
- •Total Expansion
- •Assembly onto Carrier Rail
- •Carrier rail properties
- •WAGO DIN Rail
- •Spacing
- •Plugging and Removal of the Components
- •Assembly Sequence
- •Internal Bus / Data Contacts
- •Power Contacts
- •Wire connection
- •Power Supply
- •Isolation
- •System Supply
- •Connection
- •Alignment
- •Field Supply
- •Connection
- •Fusing
- •Supplementary power supply regulations
- •Supply example
- •Power Supply Unit
- •Grounding
- •Grounding the DIN Rail
- •Framework Assembly
- •Insulated Assembly
- •Grounding Function
- •Grounding Protection
- •Shielding (Screening)
- •General
- •Bus Conductors
- •Signal Conductors
- •WAGO Shield (Screen) Connecting System
- •Assembly Guidelines / Standards
- •Scope
- •Abbreviation
- •Fieldbus Controller
- •Fieldbus Controller 750-837, /02x-000, 750-838, /02x-000
- •Description
- •Hardware
- •View
- •Variants
- •Device supply
- •Fieldbus connection
- •Display elements
- •Configuration and programming interface
- •Operating mode switch
- •Hardware address (Module ID)
- •Setting the baud rate
- •Operating system
- •Start-up
- •PLC cycle
- •Process Image
- •General Structure
- •Fieldbus specific Process Data Architecture
- •Digital Input Modules
- •Digital Output Modules
- •Analog Input Modules
- •Analog Output Modules
- •Specialty Modules
- •System Modules
- •Data Exchange
- •Communication objects
- •Communication interfaces
- •Memory areas
- •Addressing
- •Fieldbus specific Addressing
- •Absolute Addresses
- •Calculate Addresses
- •Address Range for Flags
- •Example for Absolute Addresses
- •Programming the PFC with WAGO-I/O-PRO CAA
- •WAGO-I/O-PRO CAA Library Elements for CANopen
- •IEC 61131-3 Program transfer
- •Transmission via the serial interface
- •Transmission via the fieldbus
- •Starting up CANopen fieldbus nodes
- •Connecting the PC and fieldbus node
- •Checking and setting the Baud rate
- •Setting the module ID
- •Changing to the OPERATIONAL status
- •Turning on the analog input data
- •Application specific mapping
- •LED Display
- •Fieldbus status
- •Node Status – Blink code from the 'I/O' LED
- •Supply Voltage Status
- •Technical Data
- •I/O Modules
- •General
- •Digital Input Modules
- •Digital Output Modules
- •Analog Intput Modules
- •Analog Output Modules
- •Special Modules
- •System Modules
- •CANopen
- •Description
- •Network Architecture
- •Transmission Media
- •Type of Cable
- •Maximum Bus Length
- •Required Conductor Cross Section
- •Cabling
- •Network Topology
- •Interface Modules
- •Configuration Software
- •Network Communication
- •Communication Objects
- •Process Data Object - PDO
- •PDO Protocol
- •Service Data Object - SDO
- •SDO Protocol
- •Initiate SDO Download
- •Download SDO Segment
- •Initiate SDO Upload
- •Upload SDO Segment
- •SDO Examples
- •Synchronization Object - SYNC
- •SYNC Protocol
- •Emergency Object (EMCY)
- •EMCY Protocol
- •CANopen state diagram
- •INITIALIZATION
- •PRE-OPERATIONAL
- •OPERATIONAL
- •STOPPED
- •Network Management Objects
- •Module Control Protocols
- •Start Remote Node
- •Stop Remote Node
- •Enter Pre-Operational
- •Reset Node
- •Error Control Protocols
- •Node Guarding Protocol
- •Heartbeat Protocol
- •Bootup Protocol
- •Object Directory
- •Initialization
- •Communication Profile Area
- •Object 0x1000, Device Type
- •Object 0x1001, Error Register
- •Object 0x1003, Pre-defined Error Field
- •Object 0x1005, COB-ID SYNC message
- •Object 0x1006, Communication Cycle Period
- •Object 0x1008, Manufacturer Device Name
- •Object 0x1009, Manufacturer Hardware Version
- •Object 0x100A, Manufacturer Software Version
- •Object 0x100C, Guard Time
- •Object 0x100D, Life Time Factor
- •Object 0x1010, Store Parameters
- •Object 0x1011, Restore default Parameters
- •Object 0x1015, Inhibit Time Emergency Object
- •Object 0x1016, Consumer Heartbeat Time
- •Object 0x1017, Producer Heartbeat Time
- •Object 0x1018, Identity Object
- •Object 0x1200– 0x1201, Server SDO
- •Object 0x1280– 0x128F, Client SDO
- •Object 0x1400– 0x141F, Receive PDO Communication Parameter
- •Object 0x1600– 0x161F, Receive PDO Mapping Parameter
- •Object 0x1800– 0x181F, Transmit PDO Communication Parameter
- •Object 0x1A00 – 0x1A1F, Transmit PDO Mapping Parameter
- •Manufacturer Specific Profile Area
- •Object 0x2000, Digital Inputs
- •Object 0x2100, Digital Outputs
- •Object 0x2200, 1 Byte Special Modules, Inputs
- •Object 0x2300, 1 Byte Special Modules, Outputs
- •Object 0x2400, 2 Byte Special Modules, Inputs
- •Object 0x2500, 2 Byte Special Modules, Outputs
- •Object 0x2600, 3 Byte Special Modules, Inputs
- •Object 0x2700, 3 Byte Special Modules, Outputs
- •Object 0x2800, 4 Byte Special Modules, Inputs
- •Object 0x2900, 4 Byte Special Modules, Outputs
- •Object 0x3000, 5 Byte Special Modules, Inputs
- •Object 0x3100, 5 Byte Special Modules, Outputs
- •Object 0x3200, 6 Byte Special Modules, Inputs
- •Object 0x3300, 6 Byte Special Modules, Outputs
- •Object 0x3400, 7 Byte Special Modules, Inputs
- •Object 0x3500, 7 Byte Special Modules, Outputs
- •Object 0x3600, 8 Byte Special Modules, Inputs
- •Object 0x3700, 8 Byte Special Modules, Outputs
- •Object 0x4200-0x4202, Gateway Module Input
- •Object 0x4500, Spacer Module Configuration
- •Object 0x5000, Read Input Process Image
- •Object 0x5001, Write Output Process Image
- •Object 0x5200, Controller Configuration Object
- •Object 0x5201, Diagnostics Configuration Object
- •Standard Device Profile Area – DS 401
- •Object 0x6000, Digital Inputs
- •Object 0x6005, Global Interrupt Enable Digital 8-Bit
- •Object 0x6006, Interrupt Mask Any Change 8-Bit
- •Object 0x6007, Interrupt Mask Low-to-High 8-Bit
- •Object 0x6008, Interrupt Mask High-to-Low 8-Bit
- •Object 0x6200, Digital Outputs
- •Object 0x6206, Error Mode Output 8-Bit
- •Object 0x6207, Error Value Output 8-Bit
- •Object 0x6401, Analog Inputs 16 Bit
- •Object 0x6411, Analog Outputs 16 Bit
- •Object 0x6421, Analog Input Interrupt Trigger Selection
- •Object 0x6423, Analog Input Global Interrupt Enable
- •Object 0x6424, Analog Input Interrupt Upper Limit Integer
- •Object 0x6425, Analog Input Interrupt Lower Limit Integer
- •Object 0x6426, Analog Input Interrupt Delta Unsigned
- •Object 0x6443, Analog Output Error Mode
- •Object 0x6444, Analog Output Error Value Integer
- •Object 0x67FE, Error Behavior
- •Reserved Area
- •Object 0xA000, Integer8 IEC 61131-1 Input variables
- •Object 0xA040, Unsigned8 IEC 61131-1 Input variables
- •Object 0xA080, Boolean IEC 61131-1 Input variables
- •Object 0xA0C0, Integer16 IEC 61131-1 Input variables
- •PDO Transmission
- •Mapping
- •Transmit PDO1
- •Receive PDO1
- •Transmit PDO2
- •Receive PDO2
- •SYNC Monitoring
- •Node Guarding
- •Heartbeat Monitoring
- •Error Message (Emergency)
- •Diagnostic Message of I/O Modules
- •Use in Hazardous Environments
- •Foreword
- •Protective measures
- •Classification meeting CENELEC and IEC
- •Divisions
- •Explosion protection group
- •Unit categories
- •Temperature classes
- •Types of ignition protection
- •Classifications meeting the NEC 500
- •Divisions
- •Explosion protection groups
- •Temperature classes
- •Identification
- •For Europe
- •For America
- •Installation regulations
- •Glossary
- •Literature list
- •Index
CANopen • 125
Network Communication
5.3 Network Communication
With CANopen, data transmission, the triggering of events, signalling of error states etc. takes place by means of communication objects. For this purpose, each communication object is assigned a clear COB-ID (Communication Object Identifier) in the network.
The COB ID assignment according to the Device profile DS401 results in accordance with the following table.
|
10 |
|
9 |
|
8 |
|
7 |
|
6 |
|
5 |
4 |
3 |
|
2 |
1 |
|
0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Function |
|
|
|
|
node identifier |
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
code |
|
|
|
|
(0[= all], 1-127) |
|
|
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
Communication objects |
|
|
|
|
Function |
|
|
|
|
|
|
|
Object directory |
|
||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
code |
|
|
|
|
|
|
|
index |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
dec |
|
bin |
|
|
dec |
|
|
bin |
|
hex |
|
|
|
Broadcast |
|
|
NMT Command |
|
|
0 |
|
0000 |
|
0 |
|
|
|
|
|
|
|||||||||||||
|
messages |
|
|
|
Sync message |
|
|
|
1 |
|
0001 |
|
128 |
|
80 |
|
1005, 1006, 1007 |
|
||||||||||||
|
|
|
|
|
|
|
|
|
System time |
|
|
|
2 |
|
0010 |
|
256 |
|
100 |
|
1012, 1013 |
|
||||||||
|
|
|
|
|
|
|
|
|
|
1 |
|
0001 |
|
129-255 |
|
|
81-FF |
|
1014, 1015 |
|
||||||||||
|
Peer-to- |
|
|
|
|
Alarm objects |
|
|
|
|
|
|
|
|
|
|||||||||||||||
|
Peer |
|
|
|
|
|
Tx-PDO1 |
|
|
|
3 |
|
0011 |
|
|
385-511 |
181-1FF |
|
1800 |
|
||||||||||
|
messages |
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||
|
|
|
|
|
Rx-PDO1 |
|
|
|
4 |
|
0100 |
|
|
513-639 |
201-27F |
|
1400 |
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
Tx-PDO2 |
|
|
|
5 |
|
0101 |
|
|
641-767 |
281-2FF |
|
1801 |
|
|||||||
|
|
|
|
|
|
|
|
|
|
Rx-PDO2 |
|
|
|
6 |
|
0110 |
|
|
769-895 |
301-37F |
|
1401 |
|
|||||||
|
|
|
|
|
|
|
|
|
|
Tx-PDO3 |
|
|
|
7 |
|
0111 |
|
|
897-1023 |
381-3FF |
|
1802 |
|
|||||||
|
|
|
|
|
|
|
|
|
|
Rx-PDO3 |
|
|
|
8 |
|
1000 |
|
|
1025-1151 |
401-47F |
|
1402 |
|
|||||||
|
|
|
|
|
|
|
|
|
|
Tx-PDO4 |
|
|
|
9 |
|
1001 |
|
|
1153-1279 |
481-4FF |
|
1803 |
|
|||||||
|
|
|
|
|
|
|
|
|
|
Rx-PDO4 |
|
|
|
10 |
|
1010 |
|
|
1281-1407 |
501-57F |
|
1403 |
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
|
|
Tx-SDO |
|
|
|
11 |
|
1011 |
|
|
1409-1535 |
581-5FF |
|
1200 |
|
||||||
|
|
|
|
|
|
|
|
|
|
|
Rx-SDO |
|
|
|
12 |
|
1100 |
|
|
1537-1663 |
601-67F |
|
1200 |
|
||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||
|
|
|
|
|
|
|
|
node monitoring |
|
|
14 |
|
1110 |
|
1793-1919 |
|
|
701-77F |
|
100C, 100D |
|
|||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1016, 1017 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The parameters required for the communication objects as well as the parameters and data of the CANopen subscribers are filled in the object directory.
Type and number of objects supported by the node depend on the individual fieldbus coupler.
In addition to several special objects, i.e. for the network management (NMT), for synchronization (SYNC) or for error messages (EMCY), the communication profile contains the two object types PDO and SDO.
The PDOs (process data objects) are used for the transmission of real time data, and the SDOs (service data objects) permit access to the object directory both for reading and writing.
WAGO-I/O-SYSTEM 750
CANopen