- •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
114 • DeviceNet
Process data and Diagnostic Status
5.4.2 I/O Messaging Connections
The transfer or exchange of process data between the scanner and the I/O device is made via a „Polled I/O Connection“, „Change of State/Cyclic“ or „Bit Strobe“.
Polled I/O Connection |
Slaves are cyclically polled by the master. |
Strobe Function |
All slaves are polled by the master by means of |
|
a command. |
Change of State |
Messages are transmitted either cyclically by |
|
the master or the slave, or in the event of a state |
|
change. |
5.5 Process data and Diagnostic Status
The data is transmitted between master and slave in the form of objects, a differentiation being made between input and output objects. The object architecture is defined by assembly objects which serve to group attributes of differing application objects. I/O data of different objects can, for this reason, be grouped to form a data block and transmitted by a message connection.
5.5.1 Process Image
The process image is differentiated according to input and output process images. The assembly object makes a statically configured process image available in the instances 1 ... 9.
The desired process image can be selected by setting the Produced Connection Path and the Consumed Connection Path of the individual I/O connections (Poll, Bit Strobe, Change of State or Change of Value).
The architecture of the individual instances of the assembly object is described in the following.
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 115
Process data and Diagnostic Status
5.5.1.1 Assembly Instances
Permanently pre-programmed (static) assemblies in the device permit an easy and rapid transmission of input and output images from the fieldbus Coupler/Controller to the master. For this purpose, various assembly instances are provided in the fieldbus Coupler/Controller:
Output 1 (I/O Assembly Instance 1):
The entire output data image is transmitted from the master to the Controller via the corresponding I/O message connection. In this case, the data length corresponds to the number of output data in bytes. Analog output data come before digital output data.
Output 2 (I/O Assembly Instance 2):
The digital output data image is transmitted from the master to the Controller via the corresponding I/O message connection. The data length is equivalent to the number of digital output data and is rounded up to full bytes.
Output 3 (I/O Assembly Instance 3):
The analog output data image is transmitted from the master to the Controller via the corresponding I/O message connection. The data length is equivalent to the number of analog output data in bytes.
Input 1 (I/O Assembly Instance 4):
The entire input data image and one status byte are transmitted to the master via the corresponding I/O message connection. The data length is equivalent to the number of input data in bytes and one status byte.
Input 2 (I/O Assembly Instance 5):
The digital input data image and one status byte are transmitted to the master via the corresponding I/O message connection. The data length is equivalent to the number of digital input data and rounded up to full bytes. In addition, a status byte is inserted.
Input 3 (I/O Assembly Instance 6):
The analog input data image and one status byte are transmitted to the master via the corresponding I/O message connection. The data length is equivalent to the number of analog input data in bytes and one status byte.
Input 1 (I/O Assembly Instance 7):
The entire input data image is transmitted to the master via the corresponding I/O message connection. The data length is equivalent to the number of input data in byte.
WAGO-I/O-SYSTEM 750
DeviceNet
