- •TABLE OF CONTENTS
- •Important Comments
- •Legal Principles
- •Copyright
- •Personnel Qualification
- •Intended Use
- •Symbols
- •Font Conventions
- •Number Notation
- •Scope
- •Abbreviation
- •The WAGO-I/O-SYSTEM 750
- •System Description
- •Technical Data
- •Manufacturing Number
- •Storage, Consignment 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
- •Function Earth
- •Protective Earth
- •Shielding (screening)
- •General
- •Bus Conductors
- •Signal Conductors
- •WAGO Shield (Screen) Connecting System
- •Assembly Guidelines / Norms
- •Fieldbus Coupler/Controller
- •Fieldbus Coupler 750-306
- •Description
- •Hardware
- •View
- •Device Supply
- •Fieldbus Connection
- •Display Elements
- •Configuration Interface
- •Hardware Address (MAC ID)
- •Setting the Baud Rate
- •Operating System
- •Process Image
- •Data Exchange
- •Communication Interfaces
- •Memory Areas
- •Addressing
- •Fieldbus Specific
- •Configuration Software
- •Starting up DeviceNet Fieldbus Nodes
- •Connecting the PC and Fieldbus Node
- •Setting the MAC ID and Baud Rate
- •Configuration with Static Assembly
- •LED Display
- •Node Status
- •Blink Code
- •Fault Message via the Blink Code of the I/O LED
- •Supply Voltage Status
- •Technical Data
- •Fieldbus Controller 750-806
- •Description
- •Hardware
- •View
- •Device Supply
- •Fieldbus Connection
- •Display Elements
- •Configuration and Programming Interface
- •Operating Mode Switch
- •Hardware Address (MAC ID)
- •Setting the Baud Rate
- •Operating System
- •Start-up
- •PLC Cycle
- •Process Image
- •Data Exchange
- •Communication Interfaces
- •Memory Areas
- •Addressing
- •Fieldbus Specific
- •Absolute Addressing
- •Calculate Addresses
- •Address Range for I/O Module Data
- •Address Range for Fieldbus Variables
- •Address Range for Flags
- •Example for Absolute Addresses
- •Programming the PFC with WAGO-I/O-PRO 32
- •WAGO-I/O-PRO 32 Library Elements
- •IEC 61131-3 Program Transfer
- •Transmission via the Serial Interface
- •Transmission via the Fieldbus
- •Special DeviceNet Features of the Controller
- •Connection via the UCMM port
- •Offline Connection Set
- •DeviceNet Shutdown
- •Dynamic Assembly
- •Change MAC ID by SW
- •Heartbeat
- •Bit-Strobe
- •Configuration Software
- •Starting-up DeviceNet Fieldbus Nodes
- •Connecting the PC and Fieldbus Node
- •Setting the MAC ID and Baud Rate
- •Configuration with Static and Dynamic Assembly
- •LED Display
- •Node Status
- •Blink Code
- •Fault Message via the Blink Code of the I/O LED
- •Supply Voltage Status
- •Technical Data
- •I/O modules
- •DeviceNet
- •Description
- •Network Architecture
- •Transmission Media
- •Type of Cable
- •Cable Types
- •Maximum Bus Length
- •Cabling
- •Network Topology
- •Network Grounding
- •Interface Modules
- •Network Communication
- •Objects, Classes, Instances and Attributes
- •Module Characteristics
- •Communication Model
- •Message Groups
- •Message Types
- •I/O Messaging
- •Explicit Messaging
- •I/O Messaging Connections
- •Process data and Diagnostic Status
- •Process Image
- •Assembly Instances
- •Configuration / Parametering with the Object Model
- •EDS Files
- •Object Model
- •Identity Class (0x01):
- •Message Router (0x02):
- •DeviceNet Object (0x03):
- •Assembly Object (0x04):
- •Connection Object (0x05):
- •Acknowledge Handler Object (0x2B):
- •Coupler configuration object (0x64):
- •Discrete Output Point Object (0x66):
- •Analog Input Point Object (0x67):
- •Analog Output Point Object (0x68):
- •Supplement to the Object Model for Controller 750-806
- •Bit-Strobe
- •Dynamic Assembly
- •New Classes for the PFC Fieldbus Variables
- •Class 160 (0xA0) Input PLC Fieldbus Variable USINT
- •Class 161 (0xA1) Input Fieldbus Variable USINT
- •Class 162 (0xA2) Input Fieldbus Variable USINT
- •Class 163 (0xA3) Output Fieldbus Variable USINT
- •Class 164 (0xA4) Output Fieldbus Variable USINT
- •Class 165 (0xA5) Output Fieldbus Variable USINT
- •Class 166 (0xA6) Input Fieldbus Variable UINT
- •Class 167 (0xA7) Input Fieldbus Variable UINT
- •Class 168 (0xA8) Output Fieldbus Variable UINT
- •Class 169 (0xA9) Output Fieldbus Variable UINT
- •Class 170 (0xAA) Input Fieldbus Variable UDINT
- •Class 171 (0xAB) Input Fieldbus Variable UDINT
- •Class 172 (0xAC) Output Fieldbus Variable UDINT
- •Class 173 (0xAD) Output Fieldbus Variable UDINT
- •Class 100 (0x64) - Attribute 44/100/101
- •Identity Class 1 (0x01)
- •Connection Object (0x05)
- •Additional Assembly Instances 10 and 11
- •Application in Explosive 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
136 • DeviceNet
Configuration / Parametering with the Object Model
5.6.2.2.16Class 172 (0xAC) Output Fieldbus Variable UDINT
PLC output byte 1..128
Max. instance: 128
5.6.2.2.17Class 173 (0xAD) Output Fieldbus Variable UDINT
PLC output byte 1..128 Max. instance: 128
Starts with 2 bytes offset
(the 2nd and 3rd UINT (class168 / instance 2 and 3)
=1st UDINT (class173 / instance 1) etc.)
5.6.2.2.18Class 100 (0x64) - Attribute 44/100/101
Attribut ID |
Used in Coupler |
Access rule |
Attribute |
Data type |
Brief description of the attribute |
|
|
|
name |
|
|
44 |
Specific |
Get/Set |
BK_SAVE_ |
UINT |
Save dynamic created instances in non |
(0x2C) |
|
|
DYN_ASS_ |
|
volatile memory (after power up all |
|
|
|
INST |
|
saved instances are automatically |
|
|
|
|
|
created ) |
|
|
|
|
|
0: save no dynamic instances |
|
|
|
|
|
1: save dynamic instances |
100 (0x64) |
Specific |
Get/Set |
BK_FBINP_ |
UINT |
Defines the number of bytes from the |
|
|
|
VAR_CNT |
|
PLC-fieldbus-variables (inputs) which |
|
|
|
|
|
will be added to the assembly object |
|
|
|
|
|
(this count will be added to the consu- |
|
|
|
|
|
med path – assembly instances 1..3) |
101 (0x65) |
Specific |
Get/Set |
BK_FBOUT |
UINT |
Defines the number of bytes from the |
|
|
|
_VAR_CNT |
|
PLC-fieldbus-variables (outputs) |
|
|
|
|
|
which will be added to the assembly |
|
|
|
|
|
object (this count will be added to the |
|
|
|
|
|
produced path – assembly instances |
|
|
|
|
|
4..9) |
Example:
The example comes from the DeviceNet Coupler point of view:
-> Configuration Coupler: |
input process image 12 byte, |
|
output process image 10 byte |
-> BK_FBINP_VAR_CNT = 0; |
BK_FBOUT_VAR_CNT = 0 |
poll connection: -> 12 byte produced -> 10 byte consumed
-> BK_FBINP_VAR_CNT = 4; BK_FBOUT_VAR_CNT = 3 poll connection:
-> 15 byte produced
(12 byte input process image + 3 byte PLC output fieldbus variables) -> 14 byte consumed
(10 byte output process image + 4 byte PLC input fieldbus variables)
5.6.2.2.19Identity Class 1 (0x01)
Instance 1:
Attribut ID |
Used in Coupler |
Access rule |
Attribute name |
Data type |
Description of the attribute |
Default |
|
|
|
|
|
|
Value |
10 (0x0A) |
required |
Get/Set |
Heartbeat |
USINT |
Interval between 2 Heartbe- |
0 |
|
|
|
Interval |
|
at messages in seconds |
|
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 137
Configuration / Parametering with the Object Model
5.6.2.2.20Connection Object (0x05)
Description of the instances:
Instance ID |
Description |
|
1 |
... 4 |
... |
5 |
|
|
6 |
|
References dynamic Connection |
7 |
|
|
8 |
|
|
9 |
|
|
10 |
|
|
11 |
References I/O Connection |
|
12 |
||
13 |
|
|
14 |
|
|
5.6.2.2.21Additional Assembly Instances 10 and 11
In addition to the (static) assemblies (1 ... 9) that are permanently preprogrammed in the device, the Controller has the assembly instances 10 and 11.
These simplify and speed up the transmission of the input and output image of the PFC variable from the fieldbus Controller to the master.
Description of the instances:
Instance |
Description |
ID |
|
1 ... 9 |
.... |
10 |
References to the process image containing PFC output variables. |
11 |
References to the process image containing PFC input variables. |
Instance 10:
Attribute |
Used in |
Access |
Name |
Data type |
Description |
Value |
ID |
buscoupler |
rule |
|
|
|
|
3 |
optional |
get |
PFC |
Array of |
process image, collection of all |
|
|
|
|
output |
Byte |
PFC output variables |
|
|
|
|
variables |
|
|
|
Instance 11:
Attribute |
Used in |
Access |
Name |
Data type |
Description |
Value |
ID |
buscoupler |
rule |
|
|
|
|
3 |
optional |
get |
PFC input |
Array of |
process image, collection of all |
|
|
|
|
variables |
Byte |
PFC input variables |
|
(For PFCs with software version before SW 01.06): PFC Output (I/O Assembly Instance 10):
Only the PFC output variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 101 (BK_FBOUT_ VAR_CNT).
WAGO-I/O-SYSTEM 750
DeviceNet
138 • DeviceNet
Configuration / Parametering with the Object Model
PFC Input (I/O Assembly Instance 11):
Only the PFC input variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 100 (BK_FBIN_ VAR_CNT).
(For PFCs from software version SW 01.06):
PFC Output (I/O Assembly Instance 10):
Only the PFC output variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 104 (BK_FBOUT_ PLCONLY_VAR_CNT).
The first PFC transfer byte is defined by the value in class 100 / instance 1 / attribute 105 (BK_FBOUT_STARTPLC_VAR_CNT).
PFC Input (I/O Assembly Instance 11):
Only the PFC input variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 102 (BK_FBINP_PLCONLY_ VAR_CNT).
The first PFC transfer byte is defined by the value in class 100 / instance 1 / attribute 103 (BK_FBIN_STARTPLC_VAR_CNT).
WAGO-I/O-SYSTEM 750
DeviceNet