Professional Documents
Culture Documents
DeviceNet
750-306, 750-806
Manual
Technical Description,
Installation and
Configuration
Version 1.0.0
ii • General
Technical Support
Phone: +49 (0) 571/8 87 – 5 55
Fax: +49 (0) 571/8 87 – 85 55
E-Mail: support@wago.com
Every conceivable measure has been taken to ensure the correctness and com-
pleteness of this documentation. However, as errors can never be fully ex-
cluded we would appreciate any information or ideas at any time.
E-Mail: documentation@wago.com
We wish to point out that the software and hardware terms as well as the
trademarks of companies used and/or mentioned in the present manual are
generally trademark or patent protected.
WAGO-I/O-SYSTEM 750
DeviceNet
Table of Contents • iii
TABLE OF CONTENTS
1 Important Notes .......................................................................................... 7
1.1 Legal Principles........................................................................................ 7
1.1.1 Copyright ............................................................................................. 7
1.1.2 Personnel Qualification ....................................................................... 7
1.1.3 Conforming Use of Series 750 ............................................................ 8
1.1.4 Technical Condition of the Devices .................................................... 8
1.2 Standards and Regulations for Operating the 750 Series ......................... 8
1.3 Symbols .................................................................................................... 9
1.4 Safety Information.................................................................................. 10
1.5 Font Conventions ................................................................................... 11
1.6 Number Notation.................................................................................... 11
1.7 Scope ...................................................................................................... 12
1.8 Abbreviation........................................................................................... 12
WAGO-I/O-SYSTEM 750
DeviceNet
iv • Table of Contents
WAGO-I/O-SYSTEM 750
DeviceNet
Table of Contents • v
WAGO-I/O-SYSTEM 750
DeviceNet
vi • Table of Contents
7 Glossary.................................................................................................... 197
WAGO-I/O-SYSTEM 750
DeviceNet
Important Notes • 7
Legal Principles
1 Important Notes
This section provides only a summary of the most important safety require-
ments and notes which will be mentioned in the individual sections. To protect
your health and prevent damage to the devices, it is essential to read and care-
fully follow the safety guidelines.
WAGO Kontakttechnik GmbH & Co. KG reserves the right of changes serv-
ing technical progress.
All rights developing from the issue of a patent or the legal protection of util-
ity patents are reserved to WAGO Kontakttechnik GmbH & Co. KG. Third-
party products are always indicated without any notes concerning patent
rights. Thus, the existence of such rights must not be excluded.
Specialists**) having
Instructed person-
Activity Electrical specialist qualifications in PLC
nel*)
programming
Assembly X X
Commissioning X X
Programming X
Maintenance X X
Troubleshooting X
Disassembly X X
**) A specialist is someone who, through technical training, knowledge and experience,
demonstrates the ability to meet the relevant specifications and identify potential dangers in
the mentioned field of activity.
WAGO-I/O-SYSTEM 750
DeviceNet
8 • Important Notes
Standards and Regulations for Operating the 750 Series
improper action and damage to WAGO products and third party products due to
non-observance of the information contained in this manual.
The device is designed for IP20 protection class. It is protected against finger
touch and solid impurities up to 12.5mm diameter, but not against water pene-
tration. Unless otherwise specified, the device must not be operated in wet and
dusty environments.
• The data and power lines must be connected and installed in compliance
with the standards to avoid failures on your installation and eliminate any
danger to personnel.
• For installation, startup, maintenance and repair, please observe the acci-
dent prevention regulations of your machine (e.g. BGV A 3, "Electrical In-
stallations and Equipment").
• Emergency stop functions and equipment must not be made ineffective.
See relevant standards (e.g. DIN EN 418).
• Your installation must be equipped in accordance to the EMC guidelines so
that electromagnetic interferences can be eliminated.
• Operating 750 Series components in home applications without further
measures is only permitted if they meet the emission limits (emissions of
interference) according to EN 61000-6-3. You will find the relevant in-
formation in the section on "WAGO-I/O-SYSTEM 750" Æ "System De-
scription" Æ "Technical Data".
WAGO-I/O-SYSTEM 750
DeviceNet
Important Notes • 9
Symbols
1.3 Symbols
Danger
Always observe this information to protect persons from injury.
Warning
Always observe this information to prevent damage to the device.
Attention
Marginal conditions that must always be observed to ensure smooth and effi-
cient operation.
Note
Make important notes that are to be complied with so that a trouble-free and
efficient device operation can be guaranteed.
Additional Information
References to additional literature, manuals, data sheets and INTERNET
pages.
WAGO-I/O-SYSTEM 750
DeviceNet
10 • Important Notes
Safety Information
Danger
The WAGO-I/O-SYSTEM 750 and its components are an open system. It
must only be assembled in housings, cabinets or in electrical operation
rooms. Access is only permitted via a key or tool to authorized qualified per-
sonnel.
Danger
All power sources to the device must always be switched off before carrying
out any installation, repair or maintenance work.
Warning
Replace defective or damaged device/module (e.g. in the event of deformed
contacts), as the functionality of fieldbus station in question can no longer be
ensured on a long-term basis.
Warning
The components are not resistant against materials having seeping and insu-
lating properties. Belonging to this group of materials is: e.g. aerosols, sili-
cones, triglycerides (found in some hand creams). If it cannot be ruled out
that these materials appear in the component environment, then the compo-
nents must be installed in an enclosure that is resistant against the above men-
tioned materials. Clean tools and materials are generally required to operate
the device/module.
Warning
Soiled contacts must be cleaned using oil-free compressed air or with ethyl
alcohol and leather cloths.
Warning
Do not use contact sprays, which could possibly impair the functioning of the
contact area.
Warning
Avoid reverse polarity of data and power lines, as this may damage the de-
vices.
WAGO-I/O-SYSTEM 750
DeviceNet
Important Notes • 11
Font Conventions
WAGO-I/O-SYSTEM 750
DeviceNet
12 • Important Notes
Scope
1.7 Scope
Item no. Description
750-306 fieldbus Coupler DeviceNet; 125 – 500 kBaud
750-806 prog. Fieldbus Controller DeviceNet; 125 – 500 kBaud
1.8 Abbreviation
AI Analog Input
AO Analog Output
BC BusCoupler
CAL CAN Application Layer
CAN Controller Area Network
DI Digital Input
DIP Dual In-line Package
DO Digital Output
EDS Electronic Data Sheets
I/O Input/Output
ID Identifier, Identification
Idx Index
ISO/ OSI International Organization for Standardization / Open Systems Interconnec-
tion (model)
M Master
MAC ID Media Access Control Identifier (nodeaddress)
MS Module Status
NMT Network Management
NS Network Status
PFC Programmable fieldbus Controller
RO Read Only
RW Read/Write
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 13
System Description
WAGO-I/O-SYSTEM 750
DeviceNet
14 • The WAGO-I/O-SYSTEM 750
Technical Data
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 15
Technical Data
WAGO-I/O-SYSTEM 750
DeviceNet
16 • The WAGO-I/O-SYSTEM 750
Technical Data
Note:
If the technical data of components differ from the values described here, the
technical data shown in the manuals of the respective components shall be
valid.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 17
Technical Data
Electromagnetic compatibility
Immunity to interference acc. to Germanischer Lloyd (2003)
Test specification Test values Strength Evaluation
class criteria
IEC 61000-4-2 ESD 6 kV/8 kV (contact/air) 3/3 B
IEC 61000-4-3 10 V/m 80 MHz ... 2 GHz 3 A
electromagnetic fields
IEC 61000-4-4 burst 1 kV/2 kV (data/supply) 2/3 A
IEC 61000-4-5 surge AC/DC 0.5 kV (line/line) 1 A
Supply:
1 kV (line/earth) 2
IEC 61000-4-6 10 V/m 80 % AM (0.15 ... 80 3 A
RF disturances MHz)
Type test AF disturbances 3 V, 2 W - A
(harmonic waves)
Type test high voltage 755 V DC - -
1500 V AC
Emission of interference acc. to Germanischer Lloyd (2003)
Test specification Limit values Frequency range Distance
Type test 96 ... 50 dB (µV) 10 kHz ... 150 kHz
(EMC1, conducted)
allows for ship bridge control 60 ... 50 dB (µV) 150 kHz ... 350 kHz
applications
50 dB (µV) 350 kHz ... 30 MHz
WAGO-I/O-SYSTEM 750
DeviceNet
18 • The WAGO-I/O-SYSTEM 750
Technical Data
Warning
The power dissipation of all installed components must not exceed the maxi-
mum conductible power of the housing (cabinet).
When dimensioning the housing, care is to be taken that even under high ex-
ternal temperatures, the temperature inside the housing does not exceed the
permissible ambient temperature of 55 °C.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 19
Technical Data
Dimensions
01 02
A A A A A
C C C C C
B B B B B
D D D D D
24V 0V
+ +
100
- -
35
51 12 24
65
64
Note:
The illustration shows a standard coupler. For detailed dimensions, please
refer to the technical data of the respective coupler/controller.
WAGO-I/O-SYSTEM 750
DeviceNet
20 • The WAGO-I/O-SYSTEM 750
Manufacturing Number
PROFIBUS
ITEM-NO.:750-333
PROFIBUS DP 12 MBd /DPV1
0 1 0 3 0 0 0 2 0 3 - B 0 60 0 60 0 60
AWG 28-14
24V DC
72072
- 24 V
+ 0V
Power Supply Power Supply
Field Electronic
WAGO - I/O - SYSTEM
FWL
HW
SW
NO
DS
PATENTS PENDING
II 3 GD
DEMKO 02 ATEX132273 X
750-333
EEx nA II T4
Manufacturing Number
01030002 0 1 0 3 0 0 0 2 0 3 - B 0 6 0 6 0 6
03-B
060606
72072
The manufacturing number consists of the production week and year, the soft-
ware version (if available), the hardware version of the component, the firm-
ware loader (if available) and further internal information for
WAGO Kontakttechnik GmbH.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 21
Component Update
Update Matrix
If the update of a component took place, the current version data are registered
into the columns of the matrix.
Additionally with the update of a fieldbus coupler or controller also the cover
of the configuration and programming interface of the coupler or controller is
printed on with the current manufacturing and production order number.
The original manufacturing data on the housing of the component remain
thereby.
Statically shielded transport bags with metal coatings are to be used for the
transport of open components for which soiling with amine, amide and sili-
cone has been ruled out, e.g. 3M 1900E.
WAGO-I/O-SYSTEM 750
DeviceNet
22 • The WAGO-I/O-SYSTEM 750
Mechanical Setup
Attention
In the case of vertical assembly, an end stop has to be mounted as an addi-
tional safeguard against slipping.
WAGO item 249-116 End stop for DIN 35 rail, 6 mm wide
WAGO item 249-117 End stop for DIN 35 rail, 10 mm wide
Examples:
Exception:
The number of connected I/O modules also depends on which type of cou-
pler/controller is used. For example, the maximum number of I/O modules
that can be connected to a Profibus coupler/controller is 63 without end mod-
ule.The maximum total expansion of a node is calculated as follows:
Warning
The maximum total length of a node without coupler/controller must not ex-
ceed 780mm. Furthermore, restrictions made on certain types of cou-
plers/controllers must be observed (e.g. for Profibus).
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 23
Mechanical Setup
All system components can be snapped directly onto a carrier rail in accor-
dance with the European standard EN 50022 (DIN 35).
Warning
WAGO supplies standardized carrier rails that are optimal for use with the
I/O system. If other carrier rails are used, then a technical inspection and ap-
proval of the rail by WAGO Kontakttechnik GmbH should take place.
Carrier rails have different mechanical and electrical properties. For the opti-
mal system setup on a carrier rail, certain guidelines must be observed:
• The carrier rail must optimally support the EMC measures integrated into
the system and the shielding of the bus module connections.
• The geometry of the carrier rail must not be altered in order to secure the
safe hold of the components. In particular, when shortening or mounting
the carrier rail, it must not be crushed or bent.
• The base of the I/O components extends into the profile of the carrier rail.
For carrier rails with a height of 7.5 mm, mounting points are to be riveted
under the node in the carrier rail (slotted head captive screws or blind riv-
ets).
WAGO-I/O-SYSTEM 750
DeviceNet
24 • The WAGO-I/O-SYSTEM 750
Mechanical Setup
2.6.4 Spacing
The spacing between adjacent components, cable conduits, casing and frame
sides must be maintained for the complete field bus node.
The spacing creates room for heat transfer, installation or wiring. The spacing
to cable conduits also prevents conducted electromagnetic interferences from
influencing the operation.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 25
Mechanical Setup
To pull out the fieldbus coupler/controller, release the locking disc by pressing
on the bottom groove with a screwdriver and then pulling the orange colored
unlocking lug.
It is also possible to release an individual I/O module from the unit by pulling
an unlocking lug.
Danger
Ensure that an interruption of the PE will not result in a condition which
could endanger a person or equipment!
For planning the ring feeding of the ground wire, please see chapter 2.6.3.
WAGO-I/O-SYSTEM 750
DeviceNet
26 • The WAGO-I/O-SYSTEM 750
Mechanical Setup
The reliable positioning and connection is made using a tongue and groove
system. Due to the automatic locking, the individual components are securely
seated on the rail after installing.
Starting with the coupler/controller, the bus modules are assembled adjacent
to each other according to the project planning. Errors in the planning of the
node in terms of the potential groups (connection via the power contacts) are
recognized, as the bus modules with power contacts (male contacts) cannot be
linked to bus modules with fewer power contacts.
Attention
Always link the bus modules with the coupler/controller, and always plug
from above.
Warning
Never plug bus modules from the direction of the end terminal. A ground
wire power contact, which is inserted into a terminal without contacts, e.g. a
4-channel digital input module, has a decreased air and creepage distance to
the neighboring contact in the example DI4.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 27
Mechanical Setup
Warning
Do not touch the gold spring contacts on the I/O modules in order to avoid
soiling or scratching!
WAGO-I/O-SYSTEM 750
DeviceNet
28 • The WAGO-I/O-SYSTEM 750
Mechanical Setup
Danger
The power contacts are sharp-edged. Handle the module carefully to prevent
injury.
Attention
Please take into consideration that some bus modules have no or only a few
power jumper contacts. The design of some modules does not allow them to
be physically assembled in rows, as the grooves for the male contacts are
closed at the top.
Recommendation
With the WAGO ProServe® Software smartDESIGNER, the assembly of a
fieldbus node can be configured. The configuration can be tested via the inte-
grated accuracy check.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 29
Mechanical Setup
The operating tool is inserted into the opening above the connection. This
opens the CAGE CLAMP®. Subsequently the conductor can be inserted into
the opening. After removing the operating tool, the conductor is safely
clamped.
More than one conductor per connection is not permissible. If several conduc-
tors have to be made at one connection point, then they should be made away
from the connection point using WAGO Terminal Blocks. The terminal blocks
may be jumpered together and a single wire brought back to the I/O module
connection point.
Attention
If it is unavoidable to jointly connect 2 conductors, then a ferrule must be
used to join the wires together.
Ferrule:
Length 8 mm
Nominal cross sectionmax. 1 mm2 for 2 conductors with 0.5 mm2
each
WAGO Product 216-103
or products with comparable properties
WAGO-I/O-SYSTEM 750
DeviceNet
30 • The WAGO-I/O-SYSTEM 750
Power Supply
• All bus modules have an electrical isolation between the electronics (inter-
nal bus, logic) and the field electronics. Some digital and analog input
modules have each channel electrically isolated, please see catalog.
Attention
The ground wire connection must be present in each group. In order that all
protective conductor functions are maintained under all circumstances, it is
recommended that a ground wire be connected at the beginning and end of a
potential group. (ring format, please see chapter "2.8.3"). Thus, if a bus mod-
ule comes loose from a composite during servicing, then the protective con-
ductor connection is still guaranteed for all connected field devices.
When using a joint power supply unit for the 24 V system supply and the
24 V field supply, the electrical isolation between the internal bus and the
field level is eliminated for the potential group.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 31
Power Supply
Attention
The use of an incorrect supply voltage or frequency can cause severe damage
to the component.
The direct current supplies all internal system components, e.g. cou-
pler/controller electronics, fieldbus interface and bus modules via the internal
bus (5 V system voltage). The 5 V system voltage is electrically connected to
the 24 V system supply.
WAGO-I/O-SYSTEM 750
DeviceNet
32 • The WAGO-I/O-SYSTEM 750
Power Supply
Attention
Resetting the system by switching on and off the system supply, must take
place simultaneously for all supply modules (coupler/controller and
750-613).
2.7.2.2 Alignment
Recommendation
A stable network supply cannot be taken for granted always and everywhere.
Therefore, regulated power supply units should be used in order to guarantee
the quality of the supply voltage.
The internal current consumption is indicated in the technical data for each
bus terminal. In order to determine the overall requirement, add together the
values of all bus modules in the node.
Attention
If the sum of the internal current consumption exceeds the residual current
for bus modules, then an internal system supply module (750-613) must be
placed before the module where the permissible residual current was ex-
ceeded.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 33
Power Supply
Recommendation
With the WAGO ProServe® Software smartDESIGNER, the assembly of a
fieldbus node can be configured. The configuration can be tested via the inte-
grated accuracy check.
The maximum input current of the 24 V system supply is 500 mA. The exact
electrical consumption (I(24 V)) can be determined with the following formulas:
Coupler/Controller
I(5 V) total = Sum of all the internal current consumption of the connected
bus modules
+ internal current consumption coupler/controller
750-613
I(5 V) total = Sum of all the internal current consumption of the connected
bus modules
Note
If the electrical consumption of the power supply point for the 24 V-system
supply exceeds 500 mA, then the cause may be an improperly aligned node
or a defect.
During the test, all outputs, in particular those of the relay modules, must be
active.
WAGO-I/O-SYSTEM 750
DeviceNet
34 • The WAGO-I/O-SYSTEM 750
Power Supply
Sensors and actuators can be directly connected to the relevant channel of the
bus module in 1-/4 conductor connection technology. The bus module supplies
power to the sensors and actuators. The input and output drivers of some bus
modules require the field side supply voltage.
The coupler/controller provides field side power (DC 24V). In this case it is a
passive power supply without protection equipment.
Power supply modules are available for other potentials, e.g. AC 230 V. Like-
wise, with the aid of the power supply modules, various potentials can be set
up. The connections are linked in pairs with a power contact.
The supply voltage for the field side is automatically passed to the next mod-
ule via the power jumper contacts when assembling the bus modules .
The current load of the power contacts must not exceed 10 A on a continual
basis. The current load capacity between two connection terminals is identical
to the load capacity of the connection wires.
By inserting an additional power supply module, the field supply via the
power contacts is disrupted. From there a new power supply occurs which
may also contain a new voltage potential.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 35
Power Supply
Attention
Some bus modules have no or very few power contacts (depending on the I/O
function). Due to this, the passing through of the relevant potential is dis-
rupted. If a field supply is required for subsequent bus modules, then a power
supply module must be used.
Note the data sheets of the bus modules.
In the case of a node setup with different potentials, e.g. the alteration from
DC 24 V to AC 230V, a spacer module should be used. The optical separa-
tion of the potentials acts as a warning to heed caution in the case of wiring
and maintenance works. Thus, the results of wiring errors can be prevented.
2.7.3.2 Fusing
Internal fusing of the field supply is possible for various field voltages via an
appropriate power supply module.
Fig. 2-14: Supply module with fuse carrier (Example 750-610) g0xxx09x
WAGO-I/O-SYSTEM 750
DeviceNet
36 • The WAGO-I/O-SYSTEM 750
Power Supply
Warning
In the case of power supply modules with fuse holders, only fuses with a
maximum dissipation of 1.6 W (IEC 127) must be used.
After changing the fuse, the fuse carrier is pushed back into its original posi-
tion.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 37
Power Supply
Alternatively, fusing can be done externally. The fuse modules of the WAGO
series 281 and 282 are suitable for this purpose.
Fig. 2-18: Fuse modules for automotive fuses, Series 282 pf66800x
Fig. 2-19: Fuse modules with pivotable fuse carrier, Series 281 pe61100x
WAGO-I/O-SYSTEM 750
DeviceNet
38 • The WAGO-I/O-SYSTEM 750
Power Supply
Filter modules for 24-volt supply are required for the certified operation of the
system.
Note
Another potential power terminal 750-601/602/610 must only be used behind
the filter terminal 750-626 if the protective earth conductor is needed on the
lower power contact or if a fuse protection is required.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 39
Power Supply
a) b) 1) 1) d)
c)
750-400 750-410 750-401 750-613 750-616 750-612 750-512 750-512 750-513 750-616 750-610 750-552 750-630 750-600
2) 2)
Shield (screen) bus
System
Supply
230V
24V
Field
Supply
230V
24V
Field
Supply 1) Separation module
recommended
2) Ring-feeding
10 A recommended
a) Power Supply
on coupler / controller
via external Supply
Module
b) Internal System
Supply Module
c) Supply Module
passive
d) Supply Module
with fuse carrier/
diagnostics
WAGO-I/O-SYSTEM 750
DeviceNet
40 • The WAGO-I/O-SYSTEM 750
Power Supply
Recommendation
A stable network supply cannot be taken for granted always and everywhere.
Therefore, regulated power supply units should be used in order to guarantee
the quality of the supply voltage.
A buffer (200 µF per 1 A current load) should be provided for brief voltage
dips. The I/O system buffers for approx 1 ms.
Note
The system supply and the field supply should be isolated from the power
supplies in order to ensure bus operation in the event of short circuits on the
actuator side.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 41
Grounding
2.8 Grounding
2.8.1 Grounding the DIN Rail
2.8.1.1 Framework Assembly
When setting up the framework, the carrier rail must be screwed together with
the electrically conducting cabinet or housing frame. The framework or the
housing must be grounded. The electronic connection is established via the
screw. Thus, the carrier rail is grounded.
Attention
Care must be taken to ensure the flawless electrical connection between the
carrier rail and the frame or housing in order to guarantee sufficient ground-
ing.
Recommendation
The optimal insulated setup is a metallic assembly plate with grounding con-
nection with an electrical conductive link with the carrier rail.
The separate grounding of the carrier rail can be easily set up with the aid of
the WAGO ground wire terminals.
WAGO-I/O-SYSTEM 750
DeviceNet
42 • The WAGO-I/O-SYSTEM 750
Grounding
Attention
Care must be taken to ensure the direct electrical connection between the
carrier rail contact and the carrier rail.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 43
Grounding
Attention
Should the ground conductor connection of the power jumper contacts within
the node become disrupted, e.g. due to a 4-channel bus terminal, the ground
connection will need to be re-established.
The ring feeding of the grounding potential will increase the system safety.
When one bus module is removed from the group, the grounding connection
will remain intact.
The ring feeding method has the grounding conductor connected to the begin-
ning and end of each potential group.
Attention
The regulations relating to the place of assembly as well as the national regu-
lations for maintenance and inspection of the grounding protection must be
observed.
WAGO-I/O-SYSTEM 750
DeviceNet
44 • The WAGO-I/O-SYSTEM 750
Shielding (Screening)
Attention
Constant shielding is absolutely required in order to ensure the technical
specifications in terms of the measurement accuracy.
The data and signal conductors should be separated from all high-voltage
cables.
The cable shield should be potential. With this, incoming disturbances can be
easily diverted.
The shielding should be placed over the entrance of the cabinet or housing in
order to already repel disturbances at the entrance.
Note
For better shield performance, the shield should have previously been placed
over a large area. The WAGO shield connection system is suggested for such
an application.
This suggestion is especially applicable when the equipment can have even
current or high impulse formed currents running through it (for example
through atmospheric end loading).
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 45
Assembly Guidelines/Standards
Fig. 2-25: WAGO Shield (Screen) Connecting System p0xxx08x, p0xxx09x, and p0xxx10x
Fig. 2-26: Application of the WAGO Shield (Screen) Connecting System p0xxx11x
WAGO-I/O-SYSTEM 750
DeviceNet
46 • Fieldbus Coupler 750-306
Description
3 Fieldbus Coupler/Controller
3.1 Fieldbus Coupler 750-306
3.1.1 Description
The fieldbus Coupler 750-306 displays the peripheral data of all I/O modules
in the WAGO-I/O-SYSTEM 750 on DeviceNet Feldbus. The data is transmit-
ted with objects.
The bus Coupler determines the physical structure of the node and creates a
process image from this with all inputs and outputs. This could involve a
mixed arrangement of analog (word by word data exchange) and digital (byte
by byte data exchange) modules.
The local process image is subdivided into an input and output data area. The
process data can be read in via the DeviceNet bus and further processed in a
control system. The process output data is sent via the DeviceNet bus.
The data of the analog modules are mapped into the automatical created proc-
ess image according to the order of their position downstream of the bus Cou-
pler. The bits of the digital modules are compiled to form bytes and also
mapped into the process image attached to the data of the analog modules.
Should the number of digital I/Os exceed 8 bits, the Coupler automatically
starts another byte.
The fieldbus Coupler supports the DeviceNet function Bit-Strobe, whereby the
function is insofar restricted, that only the status byte will be delivered.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 47
Hardware
3.1.2 Hardware
3.1.2.1 View
Status
voltage supply
DeviceNet 01 02 -Power jumper
OVERFL A
contacts
MS C
RUN B -System
Fieldbus D
connection BUS OFF 24V 0V Data contacts
NS
Series 231 CONNECT Supply
(MCS) 24V
0V
I/O
+ + Supply via
power jumper
contacts
24V
Ñ Ñ
750-306
0V
1 2 3 4 5 6 7 8
ON
DIP switch PE PE
for MAC ID
and baud rate
Power jumper
Configuration contacts
interface
flap
opened
Fig. 3-1: Fieldbus Coupler 750-306 DeviceNet g030600e
• Supply module with Internal system supply module for the system supply
as well as power jumper contacts for the field supply via I/O module as-
semblies.
• Display elements (LED's) for status display of the operation, the bus com-
munication, the operating voltages as well as for fault messages and diag-
nosis
• Configuration interface
• Electronics for communication with the I/O modules (internal bus) and the
fieldbus interface
WAGO-I/O-SYSTEM 750
DeviceNet
48 • Fieldbus Coupler 750-306
Hardware
The supply is made via terminal blocks with CAGE CLAMP® connection.
The device supply is intended both for the system and the field units.
24V
1 5
DC Bus
24V/0V 10nF modules
DC
0V
2 6
FIELDBUS INTERFACE
24V 24V
ELECTRONICS
ELECTRONICS
FIELDBUS
INTERFACE
3 7 1) 2)
0V 0V
10nF
1) 1MW
4 8 2) 10nF/500V
750-306
The integrated internal system supply module generates the necessary voltage
to supply the electronics and the connected I/O modules.
The fieldbus interface is supplied with electrically isolated voltage from the
internal system supply module.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 49
Hardware
For the field bus connection, the DeviceNet interface is equipped with a 5 pole
header, its counter-piece being a plug connector (Open Style Connector).
The table shows the connection diagram, the colours resulting in accordance
with the DeviceNet specification and are identical to the conductor colours of
the DeviceNet cables.
V+
5 V+ red 11 ... 25 V
Fieldbus CAN_High 4 CAN_H white CAN Signal High
connection
drain
Series 231 3 Shield Shield connection
(MCS) CAN_Low
2 CAN_L blue CAN Signal Low
V-
1 V- black 0V
The connection point is lowered in such a way that after a connector is in-
serted, installation in an 80 mm high switchbox is possible.
The electrical isolation between the fieldbus system and the electronics is
made via the DC/DC converter and the optoCoupler in the fieldbus.
WAGO-I/O-SYSTEM 750
DeviceNet
50 • Fieldbus Coupler 750-306
Hardware
The operating condition of the fieldbus Coupler or node is signalled via light
diodes (LED).
DeviceNet DeviceNet
OVERFL A OVERFL A
MS B
C C MS B
C A
RUN RUN
D A D B
BUS OFF 24V 0V BUS OFF 24V 0V
NS NS
CONNECT CONNECT
I/O I/O
+ + + +
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 51
Hardware
open
flap
Configuration
interface
Fig. 3-5: Configuration interface g01xx06e
Warning
The communication cable 750-920 must not be connected or disconnected
while the coupler/controller is powered on!
The DIP switch is used both for parametrizing (setting the baud rate) of the
fieldbus Coupler and for setting the MAC ID.
The MAC-ID (node address) is set with the DIP switches 1 to 6 by 'sliding' the
desired DIP switch to 'ON'.
The binary significance of the individual DIP switches increases according to
the switch number. DIP switch 1 being the lowest bit with the value 20 and
switch 6 the highest bit with the value 25. Therefore the MAC ID 1 is set with
DIP1 = ON, the MAC ID 8 with DIP4 = ON, etc.
For the DeviceNet fieldbus nodes, the node address can be set within the range
from 0 to 63.
1
ON
1 2 3 4 5
2
3
4 ON
5
6
6 7 8
7
8
Fig. 3-6: Example: Setting of station (node) address MAC ID 1 (DIP 1 = ON) g012540x
The configuration is only read during the power up sequence. Changing the
switch position during operation does not change the configuration of the bus-
WAGO-I/O-SYSTEM 750
DeviceNet
52 • Fieldbus Coupler 750-306
Operating System
coupler. Turn off and on the power supply for the fieldbus coupler to accept
the DIP switch change.
The fieldbus coupler supports 3 different Baud rates, 125 kBaud, 250 kBaud
and 500 kBaud. DIP switches 7 and 8 are used to set the baud rate.
2
3 125 kBaud*) OFF OFF
4 ON
5 250 kBaud ON OFF
6
6 7 8
The configuration is only read during the power up sequence. Changing the
switch position during operation does not change the configuration of the bus-
coupler. Turn off and on the power supply for the fieldbus Coupler to accept
the DIP switch change.
The default setting is Baud rate 125 kB.
After switching on the supply voltage, the Coupler performs a self-test of all
functions of its devices, the I/O module and the fieldbus interface. Following
this, the I/O modules and the present configuration is determined, whereby an
external, not visible list is generated.
In the event of a fault, the Coupler changes to the "Stop" condition. The "I/O"
LED flashes red. After clearing the fault and cycling power, the Coupler
changes to the "Fieldbus start" status and the "I/O" LED lights up green.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 53
Process Image
The Coupler produces an internal process image from the data width and the
type of I/O module as well as the position of the I/O modules in the node. It is
divided into an input and an output data area.
The data of the digital I/O modules is bit orientated, i.e. the data exchange is
made bit for bit. The analog I/O modules are all byte orientated I/O modules,
i.e. modules where the data exchange is made byte for byte. These I/O mod-
ules include, for example, the counter modules, I/O modules for angle and
path measurement as well as the communication modules.
Note
For the number of input and output bits or bytes of the individual I/O mod-
ules, please refer to the corresponding I/O module description.
The data of the I/O modules is separated for the local input and output process
image in the sequence of their position after the Coupler in the individual
process image.
In the respective I/O area, analog modules are mapped first, then all digital
modules, even if the order of the connected analog and digital modules does
not comply with this order. The digital channels are grouped, each of these
groups having a data width of 1 byte. Should the number of digital I/Os ex-
ceed 8 bits, the Coupler automatically starts another byte.
Note
A process image restructuring may result if a node is changed or extended. In
this case, the process data addresses also change in comparison with earlier
ones. In the event of adding a module, take the process data of all previous
modules into account.
WAGO-I/O-SYSTEM 750
DeviceNet
54 • Fieldbus Coupler 750-306
Data Exchange
For an easy and quick set-up of a connection, the DeviceNet fieldbus Coupler
750-306 uses the "Predefined Master/Slave Connection Set", which contains 4
pre-defined connections. For the access on the Coupler the connections only
need to be allocated. The "Predefined Master/Slave Connection Set" confines
itself to pure Master/Slave relationships.
The DeviceNet fieldbus Coupler 750-306 can only communicate via its as-
signed client and it is a so-called "Group 2 Only Server". The Group 2 Only
Server communicating is only possible via the Group 2 Only Unconnected
Explicit Message Port. These slaves exclusively receive messages defined in
message group 2.
Further information
The Assembly instances for the static assembly are described in chapter
4.5.1.1 "Assembly Instance".
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 55
Data Exchange
For a data exchange, the DeviceNet fieldbus Coupler is equipped with two in-
terfaces:
• the interface to fieldbus (-master) and
• the interface to the bus modules.
Data exchange takes place between the fieldbus master and the bus modules.
Access from the fieldbus side is fieldbus specific.
The Coupler uses a memory space of 256 words (word 0 ... 255) for the physi-
cal input and output data.
The division of the memory spaces is identical with all WAGO fieldbus Cou-
plers.
fieldbus coupler
memory area
fieldbus for input data
word 0 I/O modules
1
input
modules
word 255
memory area
for output data
word 0
2
output
modules
I O
word 255
Fig. 3-9: Memory areas and data exchange for a fieldbus Coupler g012433e
The Coupler process image contains the physical data of the bus modules in a
storage area for input data and in a storage area for output data (word 0 ... 255
each).
1 The input module data can be read from the fieldbus side.
2 In the same manner, writing to the output modules is possible from the
fieldbus side.
WAGO-I/O-SYSTEM 750
DeviceNet
56 • Fieldbus Coupler 750-306
Data Exchange
3.1.5.3 Addressing
Once the supply voltage is applied, the Assembly Object maps data from the
process image. As soon as a connection is established, a DeviceNet-Master
(Scanner) can address and access the data by "Class", "Instance" and "Attrib-
ute".
Data mapping depends on the selected Assembly Instance of the static Assem-
bly.
Further information
The Assembly Instances of the static Assembly are described in chapter
4.5.1.1 "Assembly Instance".
Fieldbus coupler
memory area
for input data
word 0
1 I/O modules
master Consumer
memory area
for output data
Output- word 0
Assemly 2
output
modules
I O
word 255
Fig. 3-1: Fieldbus specific data exchange for a DeviceNet fieldbus Coupler g012531e
Note
For the number of input and output bits or bytes of the individual I/O modules,
please refer to the corresponding I/O module description.
Note
A process image restructuring may result if a node is changed or extended. In
this case the process data addresses also change in comparison with earlier
ones. In the event of adding a module, take the process data of all previous
modules into account.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 57
Data Exchange
4) 1 analog 2- channel output module with 2 bytes per channel (i. e. 750-552),
5) 1 analog 2- channel input module with 2 bytes per channel (i. e. 750-456),
Byte .7 .6 .5 .4 .3 .2 .1 .0
0 low byte channel 1
1 high byte channel 1
2 low byte channel 2
3 high byte channel 2
4 not used DI041) DI031) DI021) DI011)
5 DS08 2) DS07 2) DS06 2) DS05 2) DS04 2) DS03 2) DS02 2) DS01 2)
1)
DI = Digital Input
2)
DS = Diagnostic Status (The last byte in the input process image is the Diagnostic
Status Byte, DS01...DS08, see also: Object 0x64/Instance 1/Attr. 5)
DS01 =1: internal bus error (0x01)
DS02 =1: module communication error (0x02)
DS04 =1: module diagnostic (0x08)
DS08 =1: fieldbus error (0x80)
WAGO-I/O-SYSTEM 750
DeviceNet
58 • Fieldbus Coupler 750-306
Configuration Software
Byte .7 .6 .5 .4 .3 .2 .1 .0
0 low byte channel 1
1 high byte channel 1
2 low byte channel 2
3 high byte channel 2
4 not used DO041) DO031) DO021) DO011)
1)
DO = Digital Output
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 59
Starting up DeviceNet Fieldbus Nodes
4. Connect the fitted DeviceNet fieldbus node to the DeviceNet fieldbus PCB in
your PC via a fieldbus cable.
The 24 V field bus supply is fed by an external fieldbus network power supply
over the connections V+, V- of the 5-pin fieldbus connector (MCS Series 231).
5. Start your PC.
3.1.7.2 Setting the MAC ID and Baud Rate
6. Use the DIP switches 1...6 to set the desired node address (MAC ID). The bi-
nary significance of the individual DIP switches increases according to the
switch number.
DIP switch Value
ON
1 2 3 4 5
1 20
2 21
3 22
6 7 8
4 23
g012443x
5 24
Fig. 3-10: Example: Setting the 6
MAC ID 4 (DIP 3 = ON). 25
7. DIP switches 7 and 8 are used to set the desired baud rate.
2
3 125 kBaud*) OFF OFF
4 ON
5 250 kBaud ON OFF
6
6 7 8
WAGO-I/O-SYSTEM 750
DeviceNet
60 • Fieldbus Coupler 750-306
Starting up DeviceNet Fieldbus Nodes
In this example, the software WAGO NETCON is used for the configuration.
750-306
Upon downloading the EDS file into WAGO NETCON, you can create a
new project and start configuring your network.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 61
Starting up DeviceNet Fieldbus Nodes
3. Enter Master
5. Enter a fieldbus master on the surface by clicking on the „Master“ menu point
in the "Insert" menu.
A dialog window opens in which you can select the DeviceNet fieldbus card in
your PC.
Fig. 3-14: Select the DeviceNet fieldbus PCB / Insert Master p1x2602d
6. For the DeviceNet Master interface card, click in the left-hand selection win-
dow on the corresponding entry to mark it.
7. Take the Master into the right-hand window by clicking on the "Add" button
and confirm by clicking on the "OK" button.
WAGO-I/O-SYSTEM 750
DeviceNet
62 • Fieldbus Coupler 750-306
Starting up DeviceNet Fieldbus Nodes
4. Add a slave
8. Enter a fieldbus slave on the surface by clicking on the “Device” menu point in
the "Insert" menu.
10.For the fieldbus Coupler 750-306 click in the left-hand selection window on
the corresponding entry to mark it.
11.Take this into the right-hand window by clicking on the "Add" button and con-
firm by clicking on the "OK" button.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 63
Starting up DeviceNet Fieldbus Nodes
5. Device configuration
12.To configure the device, click on its graphic to mark it, then click on the menu
point “Device configuration” in the "Settings" menu.
A dialog window opens permitting you to proceed with the desired settings.
6. Load configuration
13.To load the set configuration in the interface card, click on the master’s graphic
to mark it, then click on the “Download” menu point in the "Online" menu.
WAGO-I/O-SYSTEM 750
DeviceNet
64 • Fieldbus Coupler 750-306
LED Display
DeviceNet 01 02
OVERFL A
C
MS C
RUN
B
D
A
BUS OFF 24V 0V
NS
CONNECT
I/O
The module status (MS) and the network status (NS) can be displayed by the
top 4 LED’s. They react as described in the table.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 65
LED Display
The ‘I/O‘-LED displays the communication status of the internal bus. Addi-
tionally, this LED is used to display fault codes (blink codes) in the event of a
system error.
I/O
Green Fieldbus coupler operating perfectly, Data cycle on the
internal bus
Off No data cycle on the internal bus
Red a) During startup of fieldbus coupler:
Internal bus being initialized,
Startup displayed by LED flashing fast for approx.
1-2 seconds
Red b) After startup of fieldbus coupler:
Errors, which occur, are indicated by three conse- Evaluate the fault message (fault code and
cutive flashing sequences. There is a short pause fault argument).
between each sequential flash.
The coupler starts up after switching on the supply voltage. The "I/O" LED
blinks. The "I/O" LED has a steady light following a fault free start-up.
In the case of a fault the "I/O" LED continues blinking. The fault is cyclically
displayed by the blink code.
Detailed fault messages are displayed with the aid of a blink code. A fault is
cyclically displayed with up to 3 blink sequences.
• The first blink sequence (approx. 10 Hz) starts the fault display.
• The third blink sequence (approx. 1 Hz) follows after a further pause.
The number of blink pulses indicates the fault argument.
WAGO-I/O-SYSTEM 750
DeviceNet
66 • Fieldbus Coupler 750-306
LED Display
Switching on
the power supply
Coupler/Controller starts up
“I/O”-LED is blinking
No
Test o.k.?
Yes
“I/O” LED
1st flash sequence
(Introduction of the
error indication)
1st break
“I/O” LED
2nd flash sequence
Error code
(Number of flash cycles)
2nd break
“I/O” LED
3rd flash sequence
“I/O”-LED is shining Error argument
(Number of flash cycles)
Fig. 3-19: Signalling of the LED for indication of the node status g012111e
I/O Meaning
green Data cycle on the internal bus
off No data cycle on the internal bus
red Hardware of fieldbus coupler is defect
red During startup of fieldbus coupler: Internal bus being initialized,
flashing After startup of fieldbus coupler: Errors, which occur, are indicated by
three consecutive flashing sequences
cyclic Fault message during internal bus reset or internal error. The evaluation
red flashing is made by the three consecutive flashing sequences (fault code and
fault argument).
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 67
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
68 • Fieldbus Coupler 750-306
LED Display
9 Invalid checksum within the Turn off the power supply of the
serial EEPROM node, exchange the bus coupler
and turn the power supply on
again.
10 serial EEPROM initialization Turn off the power supply of the
fault node, exchange the bus coupler
and turn the power supply on
again.
11 Fault when reading out data from Turn off the power supply of the
the EEPROM node, exchange the bus coupler
and turn the power supply on
again.
12 Timeout when writing data in the Turn off the power supply of the
EEPROM node, exchange the bus coupler
and turn the power supply on
again.
13 - not used -
14 Maximum number of Gateway or Turn off the power supply of the
Mailbox I/O modules exceeded node, reduce number of Gateway
or Mailbox I/O modules and turn
the power supply on again.
Fault code 2 -not used-
Fault argument Fault description Trouble shooting
- not used -
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 69
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
70 • Fieldbus Coupler 750-306
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 71
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
72 • Fieldbus Coupler 750-306
LED Display
Example for a fault message; Fault: The 13th I/O module has been removed
1. The "I/O" LED starts the fault display with the first blink sequence (approx. 10
flashes/second).
2. The second blink sequence (1 flash/second) follows the first pause. The "I/O" LED
blinks four times and thus signals the fault code 4 (internal bus data fault).
3. The third blink sequence follows the second pause. The "I/O " LED blinks twelve
times. The fault argument 12 means that the internal bus is interrupted after the 12th
I/O module.
The two green LED’s in the coupler supply section, display the status of the
supply voltage. The left LED (A) indicates the status of the 24 V supply for
the coupler. The right hand LED (‘B‘ or ‘C‘) displays the status of the field
side supply (i.e., the power jumper contacts).
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler 750-306 • 73
Technical Data
System data
Max. no. of nodes 64 with scanner
Max. no. of I/O points ca. 6000 (depends on master)
Transmission medium shielded Cu cable,
trunk line: AWG 15, 18 (2x 0.82mm2 +2x1.7mm2)
drop line: AWG 22, 24 (2x0.2mm2 +2x0.32mm2)
Max. length of bus line 100 m ... 500 m
(depends on baud rate / on the cable)
Baud rate 125 kBaud, 250 kBaud, 500 kBaud
BusCoupler connection 5-pole male connector, series 231 (MCS)
female connector 231-305/010-000/050-000
is included
Standards and approvals
UL E175199, UL508
E198726, UL1604
Clas I Div2 ABCD T4A
KEMA 01ATEX1024 X
Eex nA II T4
Certification ODVA
Conformity marking CE
Accessories
EDS files Download: www.wago.com
Miniature WSB quick marking system
Technical data
Max. number of I/O modules 64
Input process image max. 512 bytes
Output process image max. 512 bytes
Configuration via PC or PLC
Voltage supply DC 24 V (-15 % / + 20 %)
Current consumption
- via power supply terminal < 500 mA at 24 V
- via CAN interface < 120 mA at 11 V
Efficiency of the power supply 87 %
Internal power consumption 350 mA at 5 V
Total current for I/O modules 1650 mA at 5 V
Isolation 500 V system/supply
Voltage via power jumper contacts DC 24 V (-15 % / + 20 %)
Current via power jumper contactmax DC 10 A
Dimensions (mm) W x H x L 51 x 65* x 100 (*from top edge of mounting rail)
Weight ca. 195 g
EMC interference resistance acc. EN 50082-2 (96)
EMC interference transmission acc. EN 50081-2 (94)
WAGO-I/O-SYSTEM 750
DeviceNet
74 • Fieldbus Controller 750-806
Description
The local process image is subdivided into an input and output data area.
The data of the analog modules are mapped into the PDOs according to the
order of their position downstream of the bus Coupler. The bits of the digital
modules are compiled to form bytes and also mapped into PDOs. Should the
number of digital I/Os exceed 8 bits, the Coupler automatically starts another
byte.
• DeviceNet Shutdown
• Dynamic assembly
• Change MAC ID by SW
• Heartbeat
• Bit-Strobe
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 75
Hardware
3.2.2 Hardware
3.2.2.1 View
Status
voltage supply
DeviceNet 01 02 -Power jumper
OVERFL A
contacts
MS C
RUN
B -System
Fieldbus D
connection BUS OFF 24V 0V Data contacts
NS
Series 231 CONNECT Supply
(MCS) 24V
0V
I/O
+ + Supply via
USR
power jumper
contacts
24V
Ñ Ñ
750-806 0V
1 2 3 4 5 6 7 8
ON
DIP switch
for MAC ID
and baud rate
Power jumper
Configuration contacts
and programming operating
interface mode switch
flap
opened
Fig. 3-20: Fieldbus Controller 750-806 DeviceNet g080600e
• Display elements (LEDs) for status display of the operation, the bus com-
munication, the operating voltages as well as for fault messages and diag-
nosis
• Electronics for communication with the I/O modules (internal bus) and the
fieldbus interface
WAGO-I/O-SYSTEM 750
DeviceNet
76 • Fieldbus Controller 750-806
Hardware
The voltage supply is fed in via the terminals with the CAGE CLAMP® con-
nection. Device supply is intended for system supply and field side supply.
I/O Modules
1/2
24 V
24 V
10 nF Electronic
5V
3/4
0V
Electronic
Interface
Fieldbus
24 V Fieldbus
Interface
5V
10 nF 1) 2)
24 V 0V 1) 1M
2) 10nF/500V
1 2 3 4
750-806
The integrated internal system supply module generates the necessary voltage
to supply the electronics and the connected I/O modules.
The fieldbus interface is supplied with electrically isolated voltage from the
internal system supply module.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 77
Hardware
The connection diagram shows the table, the colours resulting in accordance
with the DeviceNet specification and are identical to the conductor colours of
the DeviceNet cables.
V+
5 V+ red 11 ... 25 V
Fieldbus CAN_High 4 CAN_H white CAN Signal High
connection
drain
Series 231 3 Shield Shield connection
(MCS) CAN_Low
2 CAN_L blue CAN Signal Low
V-
1 V- black 0V
The connection point is lowered in such a way that after a connector is in-
serted, installation in an 80 mm high switchbox is possible.
The electrical isolation between the fieldbus system and the electronics is
made via the DC/DC converter and the optocoupler in the fieldbus.
WAGO-I/O-SYSTEM 750
DeviceNet
78 • Fieldbus Controller 750-806
Hardware
The operating condition of the fieldbus controller or node is signalled via light
diodes (LED).
DeviceNet DeviceNet
OVERFL A OVERFL A
MS B
C C MS B
C A
RUN RUN
D A D B
BUS OFF 24V 0V BUS OFF 24V 0V
NS NS
CONNECT CONNECT
I/O I/O
+ + + +
USR USR
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 79
Hardware
The configuration and programming interface is located behind the cover flap.
This is used to communicate with WAGO-I/O-CHECK and
WAGO-I/O-PRO 32 as well as for firmware transfer.
open
flap
Configuration and
programming interface
Fig. 3-24: Configuration and programming interface g01xx07e
Warning
The communication cable 750-920 must not be connected or disconnected
while the coupler/controller is powered on!
The operating mode switch is located behind the cover flap beside the con-
figuration and programming interface.
open
flap Run Stop Reset
(pushing down)
Update firmware
mode switch
Fig. 3-25: Operating mode switch g01xx10e
WAGO-I/O-SYSTEM 750
DeviceNet
80 • Fieldbus Controller 750-806
Hardware
Attention
If outputs are set when switching over the operating mode switch from RUN
to STOP, they remain set! Switching off the software side i.e. by initiators,
are ineffective, because the program is no longer processed.
Note
With "GET_STOP_VALUE" (library "System.lib") WAGO-I/O-PRO 32
provides a function which serves to recognize the last cycle prior to a pro-
gram stop giving the user the possibility to program the behavior of the Con-
troller in case of a STOP. With the aid of this function the Controller outputs
can be switched to a safe condition.
The DIP switch is used both for parametrizing (setting the baud rate) of the
fieldbus controller and for setting the MAC ID.
The MAC-ID (node address) is set with the DIP switches 1 to 6 by 'sliding' the
desired DIP switch to 'ON'.
The binary significance of the individual DIP switches increases according to
the switch number. DIP switch 1 being the lowest bit with the value 20 and
switch 6 the highest bit with the value 25. Therefore the MAC ID 1 is set with
DIP1 = ON, the MAC ID 8 with DIP4 = ON, etc.
For the DeviceNet fieldbus nodes the node address can be set within the range
from 0 to 63.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 81
Hardware
ON
1 2 3 4 5
2
3
4 ON
5
6
6 7 8
7
8
Fig. 3-26: Example: Setting of station (node) address MAC ID 1 (DIP 1 = ON) g012540x
The configuration is only read during the power up sequence. Changing the
switch position during operation does not change the configuration of the bus-
coupler. Turn off and on the power supply for the fieldbus controller to accept
the DIP switch change.
The fieldbus controller supports 3 different Baud rates, 125 kBaud, 250 kBaud
and 500 kBaud. DIP switches 7 and 8 are used to set the baud rate.
2 *)
3 125 kBaud OFF OFF
4 ON
5 250 kBaud ON OFF
6
6 7 8
The configuration is only read during the power up sequence. Changing the
switch position during operation does not change the configuration of the bus-
coupler. Turn off and on the power supply for the fieldbus controller to accept
the changing.
The default setting is Baud rate 125 kB.
WAGO-I/O-SYSTEM 750
DeviceNet
82 • Fieldbus Controller 750-806
Operating System
The Controller starts-up after switching on the supply voltage or after a hard-
ware reset. The PLC program in the flash memory is transferred to the RAM.
Following an error free start-up, the Controller changes over to the "RUN"
mode. The "I/O" LED lights up green.
A PLC program does not yet exist in the flash memory when delivered. The
Controller start-up is described without initializing the system. It then behaves
as a Coupler.
The PLC cycle starts following an error free start-up when the operating mode
switch is in the top position or by a start command from the
WAGO-I/O-PRO 32. The input and output data of the fieldbus and the I/O
modules as well as the times are read. Subsequently, the PLC program in the
RAM is processed followed by the output data of the fieldbus and the I/O
modules in the process image. Operating system functions, amongst others, for
diagnosis and communication are performed and the times are updated at the
end of the PLC cycle. The cycle starts again with the reading in of the input
and output data and the times.
The change of the operating mode (STOP/RUN) is made at the end of a PLC
cycle.
The cycle time is the time from the start of the PLC program to the next start.
If a loop is programmed within a PLC program, the PLC running time and
thus the PLC cycle are extended correspondingly.
The inputs, outputs and times are not updated during the processing of the
PLC program. This update occurs in a defined manner only at the end of the
PLC program. For this reason it is not possible to wait for an event from the
process or the elapse of a time within a loop.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 83
Operating System
Switching on the
supply voltage
Is a PLC
program in the Flash No
memory ?
“I/O” LED
is blinking Yes
orange
PLC program transfer
from the flash memory to RAM
Yes Yes
operating mode switch
STOP is in the top position or
Operating mode start command in
WAGO-IO-PRO 32:
Online/Start or Online/Stop
RUN
PLC cycle
Reading inputs, outputs and times Fieldbus data,
data of I/O modules
“I/O” LED
is shining
green
Fieldbus data,
Writing outputs
data of I/O modules
WAGO-I/O-SYSTEM 750
DeviceNet
84 • Fieldbus Controller 750-806
Process Image
The Controller produces an internal process image from the data width and the
type of I/O module as well as the position of the I/O modules in the node. It is
divided into an input and an output data area.
The data of the digital I/O modules is bit orientated, i.e. the data exchange is
made bit for bit. The analog I/O modules are all byte orientated I/O modules,
i.e. those where the data exchange is made byte for byte. These I/O modules
include, for example, the counter modules, I/O modules for angle and path
measurement as well as the communication modules.
Note
For the number of input and output bits or bytes of the individually activated
on I/O modules please refer to the corresponding I/O module description.
The data of the I/O modules is separated from the local input and output proc-
ess image in the sequence of their position after the controller in the individual
process image.
In the respective I/O area, first of all analog modules are mapped, then all
digital modules, even if the order of the connected analog and digital modules
does not comply with this order. The digital channels are grouped, each of
these groups having a data width of 1 byte. Should the number of digital I/Os
exceed 8 bits, the Controller automatically starts another byte.
Note
A process image restructuring may result if a node is changed or extended. In
this case, the process data addresses also change in comparison with earlier
ones. In the event of adding modules, take the process data of all previous
modules into account.
The process image for the physical bus module data is identical with that of
the WAGO DeviceNet fieldbus Coupler.
With the Controller, the data of the PFC variables are filled into the process
image, separated according to input and output data.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 85
Data Exchange
The DeviceNet fieldbus Controller 750-806 can communicate via the UCMM-
Port (Unconnected Message Manager Port).
The UCMM-Port permits a dynamic connection via one or several connec-
tions from one or more clients.
The object configuration for the data transmission is defined by the Assembly
Object. The Assembly Object can be used to group data (e.g.: I/O data) to
form blocks (mapping) and send this data via one single communication con-
nection. This mapping results in a reduced number of accesses to the network.
A differentiation is made between input and output assemblies.
An Input Assembly reads data from the application via the network or pro-
duces data on the network respectively.
An Output Assembly writes data to the application or consumes data from the
network respectively.
Further information
The Assembly instances for the static Assembly are described in chapter
4.5.1.1 "Assembly Instance".
In addition to the static assembly, dynamic assembly can also be used with the
fieldbus Controller. The dynamic assembly can be used to set up Assembly In-
stances in which process data from various application objects can be config-
ured as required.
Further information
For information regarding the dynamic Assembly, please refer to chapter
3.2.7.4 "Dynamic Assembly".
WAGO-I/O-SYSTEM 750
DeviceNet
86 • Fieldbus Controller 750-806
Data Exchange
For a data exchange, the DeviceNet fieldbus Controller is equipped with three
interfaces:
• the interface to fieldbus (-master),
• the PLC functionality of the PFC (CPU) and
• the interface to the bus modules
Data exchange takes place between the fieldbus master and the bus modules,
between the PLC functionality of the PFC (CPU) and the bus modules as well
as between the fieldbus master and the PLC functionality of the PFC (CPU).
Data access of the PLC functionality of the PFC (CPU) is via an application re-
lated IEC 61131-3 program and independent on the fieldbus system.
Access from the fieldbus side is fieldbus specific.
The Controller uses a memory space of 256 words (word 0 ... 255) for the
physical input and output data.
The Controller is assigned an additional memory space for mapping the PFC
variables defined according to IEC 61131-3. This extended memory space
(word 256 ... 511 each) is used to map the PFC variables behind the physical
process image.
The division of the memory spaces and the access of the PLC functionality
(CPU) to the process data is identical with all WAGO fieldbus Controllers.
Access is via an application related IEC 61131-3 program and independent on
the fieldbus system.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 87
Data Exchange
word 255
word 256 3
IEC 61131
PFC program
input
variables
output
modules
word 255
word 256
4 I O
PFC
output
variables
word 511
Fig. 3-29: Memory areas and data exchange for a fieldbus Controller g012434d
In its memory space word 0 ... 255, the Controller process image contains the
physical data of the bus modules.
1 The data of the input modules can be read by the CPU and from the field-
bus side.
2 In the same manner, writing to the output modules is possible from the
CPU and from the fieldbus side. The value of the last is written to the out-
put while concurrent writing on an output.
Note
A concurrent writing on an output must be avoided.
Either by using instance 11 of the static assembly (see chapter 0 "
The PFC variables are filled in the memory space word 256 ... 511 of the proc-
ess image.
3 The PFC input variables are written in the input memory space from the
fieldbus side and read by the CPU for further processing.
4 The variables processed by the CPU via the IEC 61131-3 program are filled
in the output memory space and can be read out by the master.
WAGO-I/O-SYSTEM 750
DeviceNet
88 • Fieldbus Controller 750-806
Data Exchange
In addition, the Controller offers further memory spaces which, however, can-
not be accessed from the fieldbus side:
RAM The RAM memory is used to create variables not required for com-
munication with the interfaces but for internal processing, such as
computation of results.
Retain The retain memory is a non-volatile memory, i.e. all values are re-
tained following a voltage failure. The memory management is auto-
matic. In this memory area, flags for the IEC 61131-3 program are
filed together with variables without memory space addressing or
variables which are explicitly defined with "var retain".
Note
The automatic memory management can cause a data overlap. For
this reason, we recommend not to use a mix of flags and retain vari-
ables.
Code The IEC 61131-3 program is filed in the code memory. The code
memory memory is a flash ROM. Once the supply voltage is applied, the pro-
gram is transmitted from the flash to the RAM memory. After an
error-free start-up, the PFC cycle starts when the operating mode
switch is turned to its upper position or by a start command from
WAGO-I/O-PRO 32.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 89
Data Exchange
3.2.5.3 Addressing
Once the supply voltage is applied, the Assembly Object maps data from the
process image. As soon as a connection is established, a DeviceNet Master
(scanner) can address and access the data by "Class", "Instance" and "Attrib-
ute" or read and/or write the data using I/O connections.
Data mapping depends on the selected Assembly instance of the static assem-
bly or on the application specific determination with the dynamic Assembly.
Further information
The Assembly Instances of the static Assembly are described in chapter
4.5.1.1 "Assembly Instance".
Further information
For information regarding the dynamic Assembly, please refer to chapter
3.2.7.4 "Dynamic Assembly".
output
modules
word 255
word 256 4 I O
PFC
output
variables
word 511
Fig. 3-2: Fieldbus specific data exchange for a DeviceNet fieldbus Controller g012532d
Note
For the number of input and output bits or bytes of the individual I/O modules,
please refer to the corresponding I/O module description.
Note
A process image restructuring may result if a node is changed or extended. In
this case, the process data addresses also change in comparison with earlier
ones. In the event of adding a module, take the process data of all previous
modules into account.
WAGO-I/O-SYSTEM 750
DeviceNet
90 • Fieldbus Controller 750-806
Data Exchange
Byte .7 .6 .5 .4 .3 .2 .1 .0
0 low byte channel 1
1 high byte channel 1
2 low byte channel 2
3 high byte channel 2
4 not used DI041) DI031) DI021) DI011)
5 DS08 2) DS07 2) DS06 2) DS05 2) DS04 2) DS03 2) DS02 2) DS01 2)
1)
DI = Digital Input
2)
DS = Diagnostic Status (The last byte in the input process image is the Diagnostic
Status Byte, DS01...DS08, see also: Object 0x64/Instance 1/Attr. 5)
DS01 =1: internal bus error (0x01)
DS02 =1: module communication error (0x02)
DS04 =1: module diagnostic (0x08)
DS08 =1: fieldbus error (0x80)
Byte .7 .6 .5 .4 .3 .2 .1 .0
0 low byte channel 1
1 high byte channel 1
2 low byte channel 2
3 high byte channel 2
4 not used DO041) DO031) DO021) DO011)
1)
DO = Digital Output
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 91
Data Exchange
The CPU has direct access to the bus terminal data through absolute ad-
dresses. Addressing begins with the address 0 both with inputs and outputs.
The corresponding addresses for bits, bytes and double words (DWord) are
derived from the word addresses.
The structure of the process image is described in chapter 3.2.4 Process Image.
Addressing is done in this structure.
WAGO-I/O-SYSTEM 750
DeviceNet
92 • Fieldbus Controller 750-806
Data Exchange
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 93
Programming the PFC with WAGO-I/O-PRO 32
This manual, however, does not include a description of how to program with
WAGO-I/O-PRO 32. In contrast, the following chapters are to describe the
special modules for WAGO-I/O-PRO 32 for you to utilize explicitly for pro-
gramming the DeviceNet fieldbus Controller.
The description also explains transmitting the IEC 61131-3 program into the
Controller and loading a suitable communication driver.
More information
For a detailed description of how to use the software, please refer to the
WAGO-I/O-PRO 32 manual (order No.: 759-122 / 000-002).
You are offered various libraries for different IEC 61131-3 programming ap-
plications in WAGO-I/O-PRO 32. They contain modules for universal use
and can, thereby, facilitate and speed up the creation of your program. As
standard, the library 'standard.lib' is available to you.
• "DevNet. lib"
This library extends the fieldbus Controller 750-806 by the master function.
As a result, it can be programmed in the network as a DeviceNet Master.
More information
For a detailed description of the POUs and the software operation, please
refer to the WAGO-I/O-PRO 32 manual (order No.: 759-122 / 000-002).
WAGO-I/O-SYSTEM 750
DeviceNet
94 • Fieldbus Controller 750-806
Programming the PFC with WAGO-I/O-PRO 32
More information
For information on the installation of the communication drivers as well as
details regarding the use of the software, please refer to the
WAGO-I/O-PRO 32 manual (order No.: 759-122 / 000-002).
Use the WAGO communication cable to produce a physical connection via the
serial interface. This is contained in the scope of delivery of the programming
tool IEC 61131-3, order No.: 759-332/000-002, or can be purchased as an ac-
cessory under order No.: 750-920.
Connect the COMX port of your PC with the communication interface of your
Controller via the WAGO communication cable.
Warning
The communication cable 750-920 must not be connected or disconnected
while the coupler/controller is powered on!
3. In the selection window mark the desired driver on the right-hand dialog
side (i.e. "Serial RS232"), to configure the serial connection between PC
and the Controller).
4. In the center window of the dialog, the following entries have to appear:
- Parity: Even
- Stop bits: 1
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 95
Programming the PFC with WAGO-I/O-PRO 32
Note
To be able to access the Controller, ensure that the operating mode switch of
the Controller is set to the center or the top position.
5. Under "Online" click on the "Log-on" menu point to log into the Control-
ler.
(The WAGO-I/O-PRO 32 server is active during online operation. The
communication parameters cannot be polled.)
7. As soon as the program is loaded, you can start program via the "Online"
menu, menu point "Start".
At the right-hand end of the status bar, the system signals "ONLINE
RUNNING"."
8. To terminate the online operation, return via the "Online" menu and click
on the "Log-off" menu point.
The field bus cable is the physical connection between the PC and the Con-
troller. It is necessary to have a suitable communication driver for data trans-
mission. This driver and how it is parametered is entered in
WAGO-I/O-PRO 32 in the "communication parameter" dialog.
Note
Transmission via the fieldbus is supported by UCMM. Here, for the down-
load of the PFC program, WAGO-I/O-PRO 32 counts as a subscriber.
4. Enter any name and mark the driver "Hilscher PA Interface standard" in
the selection window of the dialog.
Subsequently confirm with "OK".
WAGO-I/O-SYSTEM 750
DeviceNet
96 • Fieldbus Controller 750-806
Programming the PFC with WAGO-I/O-PRO 32
5. If necessary, change the entry accordingly in the center window of the dia-
log.
Note
Prerequisite for the access to the Controller is that the operating mode switch
of the Controller is in the center or top position.
6. Under "Online" click on the "Log-on" menu point to log into the Control-
ler.
(During online operation, the WAGO-I/O-PRO 32 server is active. The
communication parameters cannot be polled.)
8. As soon as the program is loaded, you can start the program via the "On-
line" menu, menu point "Start".
At the right-hand end of the status bar, the system signals "ONLINE
RUNNING".
9. To terminate the online operation, return via the "Online" menu and click
on the "Log-off" menu point.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 97
Special DeviceNet Features of the Controller
In contrast to the fieldbus Coupler 750-306 as a Group 2 Only Server, the De-
viceNet Controller supports the dynamic connection via the UCMM port (Un-
connected Message Manager Port).
For the Controller, the simultaneous set-up of 5 explicit and 5 dynamic I/O
connections, i.e. the connection with 5 subscribers, is possible.
Due to the Offline Connection Set, the fieldbus node can be addressed via the
network when this node has been switched off because of a double MAC ID
and is in a Communication Fault status. After being addressed, the MAC ID of
the fieldbus Controller can be changed using the software.
The Device Shutdown allows the fieldbus node to log out from a control in a
defined manner if the node is switched off due to internal faults. This function
can be used in a targeted way in DeviceNet networks subject to very high
safety requirements, such as e.g. in the chemical industry or in semi-conductor
production.
An Assembly Object is used to group data (e.g. I/O data) to form blocks to be
sent as a single message. The static Assembly allows the user to access per-
manently pre-programmed Assembly Instances in the fieldbus Controller. The
dynamic Assembly, on the other hand, offers the possibility to set up Assem-
bly Instances in which process data from various application objects can be
configured as required.
In addition to the I/O data transmission, the dynamic assembly can also be
used for a targeted selection of data which are to be transmitted explicitly via
the fieldbus, or those which are explicitly not to be transmitted via the field-
bus.
Attention
To set the pysical outputs with the PFC either use the dynamic assembly or
the instance 11 of the static assemblies. With this, you do not enter the physi-
cal outputs into the mapping in order to prevent the output data from being
transmitted and temporary overwritten by the fieldbus.
Further information
You can find more details in chapter 4.6.2.2.2 "Dynamic Assembly".
WAGO-I/O-SYSTEM 750
DeviceNet
98 • Fieldbus Controller 750-806
Special DeviceNet Features of the Controller
The MAC ID of the Controller can be changed via the network using the soft-
ware (e.g. WAGO NETCON, RS NetWorx). For this purpose, the node ad-
dress is stored in non-volatile memory. Should the address set at the DIP
switch differ from the one set via the network using the software, the I/O LED
changes its colour to orange.
To reset the software default address, the invalid address 64 is entered in class
3, instance 1, attribute 1.
Subsequently, the Controller has its MAC ID that is set at the DIP switch.
3.2.7.6 Heartbeat
3.2.7.7 Bit-Strobe
Further information
You can find more details in chapter 4.6.2.2.1 "Bit-Strobe".
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 99
Configuration Software
1. Connect the assembled DeviceNet fieldbus node to the DeviceNet fieldbus PCB in your PC
via a fieldbus cable and start your PC.
The 24 V field bus supply is fed by an external fieldbus network power supply over the con-
nections V+, V- of the 5-pin fieldbus connector (MCS Series 231).
2. Start your PC.
1. Use the DIP switches 1...6 to set the desired node address (MAC ID). The binary significance
of the individual DIP switches increases according to the switch number.
DIP switch Value
ON
1 2 3 4 5
1 20
2 21
6 7 8
3 22
4 23
g012443x
5 24
Fig. 3-30 Example: Setting the MAC
ID 4 (DIP 3 = ON). 6 25
DIP switches 7 and 8 are used to set the desired baud rate.
WAGO-I/O-SYSTEM 750
DeviceNet
100 • Fieldbus Controller 750-806
Starting-up DeviceNet Fieldbus Nodes
ON
1 2 3 4 5
2 *)
3 125 kBaud OFF OFF
4 ON
5 250 kBaud ON OFF
6
6 7 8
7 500 kBaud OFF ON
8
g012541x
not allowed ON ON
Fig. 3-31: Example: Setting the baud *)
rate 250 kBaud (DIP 7 = ON) of the Presetting
station with MAC ID 1.
2. Load the EDS file "750-806_1.EDS" for the fieldbus Controller in RSNetWorx.
For this click on "Tools/ EDS Wizard" and choose the EDS-file to load.
Note
You can download the EDS file 750-806_1.EDS from the Internet under:
www.wago.com
1. After the EDS file has been loaded in RSNetWorx, you can start establish-
ing your network.
For this purpose, click in the tree structure located in the left-hand screen
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 101
Starting-up DeviceNet Fieldbus Nodes
3. Take over the selected scanner into the right-hand graphics window with a
double-click or drag&drop.
4. Now select the DeviceNet Controller 806 in the tree structure in the
"Communication Adapter" folder.
5. Also take this over into the right-hand graphic window with a double-click
or drag&drop.
The correct setting of the TX/RX configuration is a prerequisite for the perfect
running of the DeviceNet network. For this purpose, the TX/RX configuration
must coincide with the node configuration.
For the entry into the RX and TX fields in RSNetworx, all input bit/bytes
count as a whole, as well as all output bits/bytes.
Here, individual bits are always grouped to form full bytes.
From the fieldbus master standpoint, the example node has the following data
configuration:
I/O module RX TX
750-806 DeviceNet PFC 1 byte input status
750-402 4-channel input 4 bits input
750-402 4- channel input 4 bits input
750-516 4- channel output 4 bits output
750-516 4- channel output 4 bits output
750-516 4- channel output 4 bits output
750-467 2 channel analog input 4 bytes input
750-550 2 channel analog output 4 bytes output
750-600 end module - -
PFC fieldbus input variables 0 bytes input
PFC fieldbus output variables 4 bytes output
WAGO-I/O-SYSTEM 750
DeviceNet
102 • Fieldbus Controller 750-806
Starting-up DeviceNet Fieldbus Nodes
Note
PFC output variables are defined from the point of view of the programmable
fieldbus Controller. These are input variables from the point of view of the
fieldbus DeviceNet, which are added to the RX Settings. Accordingly, PFC
input variables are output variables for IEC 61131-3 access of the field bus.
For that reason they will be added to the TX Settings:
IEC 61131-3 input variable = PFC output variable
PFC input variable = IEC 61131-3 output variable
Programmable
fieldbus fieldbus controller
PLC PFC
input input
variables variables
PLC PFC
output output
variables variables
In the present example, the master/scanner is to have access to the physical in-
puts and to the 4 bytes PFC output variables.
The number of input data is complemented by 4 bytes of the PFC output vari-
ables during the static assembly for the TX configuration of the scanner.
1. To be able to parameterize the Controller, double-click on the graphic
symbol of the fieldbus node 750-806.
2. In the "General" register, you can assign the Controller any desired ad-
dress.
To this effect, click in the input window for the address and enter the ad-
dress in accordance with the address set at the Controller DIP switch.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 103
Starting-up DeviceNet Fieldbus Nodes
4. Do not change the value for the ID#37 "PLC fieldbus Input variables"
which is 0. Enter 4 for the ID#38 "PLC fieldbus Output variables".
8. Click on the button with the arrow to the right in order to take over the
DeviceNet Controller 750-806 in the left-hand window "Available De-
vices" into the "Scanlist" window.
10. Activate the poll function by clicking on the field located in front of
"Polled".
The field is now ticked which permits the entry for TX and RX.
11. Enter 6 bytes in the "TX-Size" dialog box. They are receipt bytes for the
inputs.
Enter 4 bytes for the PFC input variables in the "RX-Size" dialog box. The
number of these bytes results from the following determinations in the dy-
namic assembly for the outputs. This simultaneously defines that only the
PFC input variables and no physical outputs are to be written by the mas-
ter.
12. Then click on the "OK" button to take over the parameters.
A window appears indicating that several I/O data will not be mapped.
Confirm the question of whether or not you wish to continue by clicking
on the "Yes" button.
WAGO-I/O-SYSTEM 750
DeviceNet
104 • Fieldbus Controller 750-806
Starting-up DeviceNet Fieldbus Nodes
13. In the "1797-SDN Scanner Module" dialog window, select the "Input" reg-
ister card. All inputs are mapped as digital inputs.
Mapped Inputs
I:1.0 1 Word Reserved for Scanner Module
I:1.1 1 Word Analog Input Channel 1
I:1.2 1 Word Analog Input Channel 2
I:1.3 1 Byte Status | 1 Byte Digital Inputs
I:1.4 1 Word IEC 61131-3 input variable 1
(or PFC output variable 1)
I:1.5 1 Word IEC 61131-3 input variable 2
(or PFC output variable 2)
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 105
Starting-up DeviceNet Fieldbus Nodes
14. In the "1797-SDN Scaner Module" dialog window, select the "Output"
register card. All outputs are mapped as digital outputs.
Mapped Outputs
O:1.0 1 Word Reserved for Scanner Module
O:1.1 1 Word IEC 61131-3 output variable 1
(or PFC input variable 1)
O:1.2 1 Word IEC 61131-3 output variable 2
(or PFC input variable 2)
WAGO-I/O-SYSTEM 750
DeviceNet
106 • Fieldbus Controller 750-806
Starting-up DeviceNet Fieldbus Nodes
The dynamic assembly is used to map those data which are to be transmitted
via the fieldbus. They are stored as classes, instances and attributes.
17.In the graphical display, click on the symbol of the fieldbus Controller 750-806
so that the symbol is marked.
18.Then click on the “Class Instance Editor...” menu point in the "Device" menu.
Note
This editor changes parameters in the Controller.
For this reason, ensure that all data is entered consistently either as hexadeci-
mal or decimal. If the data number format is not consistent, data loss can result
up to a total functional failure of the Controller.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 107
Starting-up DeviceNet Fieldbus Nodes
20.In the "Description" dialog box select the "Create" utility and enter the follow-
ing values in the dialog boxes for the "Object Address":
- "Class": 4
– "Instance": 0
– "Attribute": 1.
Note
Do not click on the "ENTER" key, because this will close the dialog window
so that it has to be reopened.
21.Click on the "Execute" button to create the instance for the dynamic assembly.
If the setting was successful, the fieldbus node will send the instance number =
100 0.
If a fault has occurred, you will receive a fault message.
In this case, check the entries for class, instance and attribute, the DeviceNet
connection and the configuration.
22.In the "Description" dialog box, select the "Set Single Attribute" utility and en-
ter the following values in the "Object Address" dialog boxes:
- "Class": 4
– "Instance": 64 (64 hexadecimal = 100 decimal)
– "Attribute": 2.
23.Click in the " Data Sent to the device" dialog box and enter the following val-
ues in hexadecimal:
10 00 06 00 20 A6 24 01 30 01 10 00 06 00 20 A6 24 02 30 01
WAGO-I/O-SYSTEM 750
DeviceNet
108 • Fieldbus Controller 750-806
Starting-up DeviceNet Fieldbus Nodes
If the mapping was successful, the fieldbus node sends a “performance” con-
firmation.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 109
Starting-up DeviceNet Fieldbus Nodes
1. Use the scroll bar to move down to the ID#13 and #ID14 addresses.
WAGO-I/O-SYSTEM 750
DeviceNet
110 • Fieldbus Controller 750-806
Starting-up DeviceNet Fieldbus Nodes
3. Change the value for the ID#39. Select "Dynamic created instances are stored in non volatile
memory", to retain the storage of the configuration for the Dynamic Assembly even follow-
ing a voltage failure of the Controller.
4. To take over the pre-set parameters into the Controller, select the following parameter in the
right-hand control box in the "Parameters" register:
"All Values", then click on the "Download parameters to the device" symbol which is located
on the far right next to the dialog box.
6. Then switch the supply voltage of the Controller off and on again.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 111
LED Display
DeviceNet 01 02
OVERFL A
C
MS C
RUN
B
D A
BUS OFF 24V 0V
NS
CONNECT
I/O
USR
The module status (MS) and the network status (NS) can be displayed by the
top 4 LED’s. They react as described in the following tables.
WAGO-I/O-SYSTEM 750
DeviceNet
112 • Fieldbus Controller 750-806
LED Display
The ‘I/O‘-LED displays the communication status of the internal bus. Addi-
tionally, this LED is used to display fault codes (blink codes) in the event of a
system error.
I/O
Green Fieldbus coupler operating perfectly, Data cycle on the
internal bus
Off No data cycle on the internal bus
Red a) During startup of fieldbus controller:
Internal bus being initialized,
Startup displayed by LED flashing fast for approx.
1-2 seconds
Red b) After startup of fieldbus controller:
Errors, which occur, are indicated by three conse- Evaluate the fault message (fault code and
cutive flashing sequences. There is a short pause fault argument).
between each sequential flash.
The controller starts up after switching on the supply voltage. The "I/O" LED
blinks. The "I/O" LED has a steady light following a fault free start-up.
In the case of a fault the "I/O" LED continues blinking. The fault is cyclically
displayed by the blink code.
Detailed fault messages are displayed with the aid of a blink code. A fault is
cyclically displayed with up to 3 blink sequences.
• The first blink sequence (approx. 10 Hz) starts the fault display.
• The third blink sequence (approx. 1 Hz) follows after a further pause.
The number of blink pulses indicates the fault argument.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 113
LED Display
Switching on
the power supply
Coupler/Controller starts up
“I/O”-LED is blinking
No
Test o.k.?
Yes
“I/O” LED
1st flash sequence
(Introduction of the
error indication)
1st break
“I/O” LED
2nd flash sequence
Error code
(Number of flash cycles)
2nd break
“I/O” LED
3rd flash sequence
“I/O”-LED is shining Error argument
(Number of flash cycles)
I/O Meaning
green Data cycle on the internal bus
off No data cycle on the internal bus
red Controller hardware defective
red When starting: internal bus is initialized
blinks During operation: general internal bus fault
red Fault message during internal bus reset and internal fault:
blinks cyclically
orange MAC-ID is changed via SW and is different to the DIP switch setting
WAGO-I/O-SYSTEM 750
DeviceNet
114 • Fieldbus Controller 750-806
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 115
LED Display
9 Invalid checksum within the Turn off the power supply of the
serial EEPROM node, exchange the bus coupler
and turn the power supply on
again.
10 serial EEPROM initialization Turn off the power supply of the
fault node, exchange the bus coupler
and turn the power supply on
again.
11 Fault when reading out data from Turn off the power supply of the
the EEPROM node, exchange the bus coupler
and turn the power supply on
again.
12 Timeout when writing data in the Turn off the power supply of the
EEPROM node, exchange the bus coupler
and turn the power supply on
again.
13 - not used -
14 Maximum number of Gateway or Turn off the power supply of the
Mailbox I/O modules exceeded node, reduce number of Gateway
or Mailbox I/O modules and turn
the power supply on again.
Fault code 2 -not used-
Fault argument Fault description Trouble shooting
- not used -
WAGO-I/O-SYSTEM 750
DeviceNet
116 • Fieldbus Controller 750-806
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 117
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
118 • Fieldbus Controller 750-806
LED Display
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 119
LED Display
Example for a fault message; Fault: The 13th I/O module has been removed
1. The "I/O" LED starts the fault display with the first blink sequence (approx. 10
flashes/second).
2. The second blink sequence (1 flash/second) follows the first pause. The "I/O" LED
blinks four times and thus signals the fault code 4 (internal bus data fault).
3. The third blink sequence follows the second pause. The "I/O " LED blinks twelve
times. The fault argument 12 means that the internal bus is interrupted after the 12th
I/O module.
The two green LED’s in the coupler supply section, display the status of the
supply voltage. The left LED (A) indicates the status of the 24 V supply for
the coupler. The right hand LED (‘B‘ or ‘C‘) displays the status of the field
side supply (i.e., the power jumper contacts).
WAGO-I/O-SYSTEM 750
DeviceNet
120 • Fieldbus Controller 750-806
Technical Data
System data
Max. no. of nodes 64 with scanner
Max. no. of I/O points ca. 6000 (depends on master)
Transmission medium shielded Cu cable,
trunk line: AWG 15, 18 (2x 0.82mm2 +2x1.7mm2)
drop line: AWG 22, 24 (2x0.2mm2 +2x0.32mm2)
Max. length of bus line 100 m ... 500 m
(baud rate dependent / cable dependent)
Baud rate 125 kBaud, 250 kBaud, 500 kBaud
Bus coupler connection 5-pole male connector, series 231 (MCS)
female connector 231-305/010-000/050-000
is included
Programming WAGO-I/O-PRO 32
IEC 61131-3 IL, LD, FBD, ST, FC
Standards and approvals
UL E175199, UL 508
E198726, UL 1604
Clas I Div2 ABCD T4A (applied for)
DEMKO 02ATEX132273 X
II 3 GD EEx nA II T4
Conformity marking CE
Accessories
EDS-Dateien Download: www.wago.com
Miniature WSB quick marking system
Technical data
Max. number of I/O modules 64
Fieldbus
Input process image max. 1024 Byte
Output process image max. 1024 Byte
Input variables max. 512 Byte
Output variables max. 512 Byte
Program memory 128 kByte
Data memory 64 kByte
Non-volatile memory 8 kByte (retain)
Cycle time < 3 ms for 1,000 statements /256 dig. I/Os
Configuration via PC or control
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Controller 750-806 • 121
Technical Data
WAGO-I/O-SYSTEM 750
DeviceNet
122 • Description
Technical Data
4 DeviceNet
4.1 Description
DeviceNet is a networking concept in the device level based on the serial bus
system CAN (Controller Area Network). It is particularly distinguished by the
problem-free addition and removal of devices, from simple light barriers up to
complex motor controls during operation. DeviceNet is mainly used in indus-
trial automation and for robot controls.
The Data Link Layer, i.e. the physical and data storage layer, is defined in the
CAN specification. The telegram architecture is described. However, there is
no information about the application layer.
This is where DeviceNet comes into play. It describes the defined meaning of
the data transmitted in the application layer.
The Open DeviceNet Vendor Association (abridged: ODVA) is the user or-
ganisation for DeviceNet. In a specification, the ODVA DeviceNet is defined
as a uniform application layer and it lays down technical and functional fea-
tures for device networking.
A maximum of 64 fieldbus nodes can be operated in one DeviceNet network.
The extension of the network depends on the selected baud rate (125 kBaud,
250 kBaud or 500 kBaud).
In contrast to other fieldbus systems, CAN does not address the modules con-
nected to the bus but identifies the messages. Whenever the bus is free, sub-
scribers are allowed to send messages. Each bus subscriber decides on its own
when it wants to send data or instigate other bus subscribers to send data. This
permits a communication without a bus master assembly group.
Bus conflicts are solved in that the messages are assigned a certain priority.
This priority is defined by the CAN identifier, called Connection ID in De-
viceNet. The following rule applies: the smaller the identifier, the higher the
priority.
A general distinction between high priority process messages (I/O Messages)
and low priority management messages (Explicit Messages) is done before.
Messages having a data length of more than 8 bytes can be fragmented.
The communication with DeviceNet occurs always connection-referenced
(connection based). All data and functions of a device are described by means
of an object model. Therefore, for a message exchange directly after switching
on a device, the connections to the desired subscriber have to be established
first and communication objects be created or allocated. Message distribution
is according to the broadcast system, data exchange according to the producer
consumer model.
A transmitting DeviceNet node produces data that is either consumed via a
point-to-point connection (1 to 1) by one receiving node, or via a multicast
connection (1 to n) by several receiving nodes.
WAGO-I/O-SYSTEM 750
DeviceNet
Network Architecture • 123
Transmission Media
Further information
The Open DeviceNet Vendor Association (ODVA) provides further docu-
ments in the Internet under: http://www.odva.org
A bus medium forms the basis for the physical realization of a network using
DeviceNet.
According to the line specification, a double 2-conductor twisted pair cable
(twisted pair, screened cable) is recommended to be used as a medium.
It consists of two screened twisted pair cables with a wire in the middle of the
cable. Further screening extended at the outside.
The blue and the white twisted pair cable is used for signal transmission, the
black and red one for the supply voltage.
The DeviceNet bus is configured using a remote bus cable as the trunk line
and several drop lines.
• Thick Cable
For the trunk line of maximum 8 A or for networks extending over more
than 100 m.
The trunk line topology is linear, i.e. the remote bus cables are not further
branched. On each end of the remote bus cable, terminating resistors are
required.
• Thin Cable
For drop lines with maximum 3 A or for networks extending less than
100 m.
One or more nodes can be connected to the drop lines, in other words,
branching is permitted here. The length of the individual drop lines is
measured from the branching point of the node and can be up to 6 m. The
entire length of the drop line depends on the Baud rate.
WAGO-I/O-SYSTEM 750
DeviceNet
124 • Network Architecture
Cabling
Note
If possible, route the data line separately from all high current carrying ca-
bles.
Further information
For a detailed specification regarding the cable types, please refer to the
INTERNET under: http://www.odva.org.
In the following table, the permitted cable length is represented in dependence of the Baud
rate. Here, a differentiation is made between the maximum length for a transmission using a
thick and a thin cable.
Tab. 4-1: Maximum bus length dependent on the set Baud rate
When specifying the maximum cable lengths, it is made sure that communica-
tion is possible between two nodes located at maximum distance to each other
(worst case).
4.2.2 Cabling
The connection of a WAGO fieldbus node to the DeviceNet bus cable is made
by the supplied 5-pole plug (Multi Connector 231).
V+
Fieldbus CAN_High
connection
drain
Series 231
(MCS) CAN_Low
V-
For wiring using a screened cable, the plus is assigned the connections V+, V-
for the voltage supply and with CAN_High, CAN_Low for data transmission.
The 24 V field bus supply is fed by an external fieldbus network power sup-
ply.
WAGO-I/O-SYSTEM 750
DeviceNet
Network Architecture • 125
Cabling
Note
WAGO offers the screen connection system (series 790) for an optimum con-
nection between fieldbus cable screening and functional earth.
Each DeviceNet node forms the differential voltage UDiff with: UDiff =
UCAN_High - UCAN_Low. using the bus levels CAN_High and CAN_Low.
Differential signal transmission offers the advantage of an insensitivity com-
pared to common mode malfunctions and ground offset between the nodes.
Note
At its conductor ends, the bus cable must always be connected with a match-
ing resistor of 120 Ohm to avoid reflections and, as a result, transmission
problems.
This is also required for very short conductor lengths.
The CAN bus is a 2-wire bus and bus error management can detect a cable
break or a short-circuit by the asymmetric operation.
Further information
The CiA provides documents regarding specifications, especially cable specifi-
cations on the Internet under:
http://www.can-cia.de
WAGO-I/O-SYSTEM 750
DeviceNet
126 • Network Architecture
Network Topology
120
WAGO Scanner Busnetz-
I/ O teil
In systems accommodating more than two stations, all subscribers are wired in
parallel. Node connection to the remote bus cable (trunk line) is made by
means of drop lines. For this purpose, the bus cable has to be looped without
interruption. A maximum length of 6 m for a drop line should not be ex-
ceeded.
Power Supply
WAGO-I/O-SYSTEM 750
DeviceNet
Network Architecture • 127
Network Grounding
All subscribers in the network communicate at the same Baud rate. The bus
structure permits the interference-free connection and disconnection of sta-
tions or a stepped start-up of the system.
Future extensions have no influence on the stations already in operation.
Should a subscriber fail or be added to the network as a new one, it is auto-
matically deteced by the system.
Prerequisite being, however, that the network is only grounded at one point.
Preferably, grounding is in the network center (V and screen drain with round
media) to optimize the capacity and minimize interference.
Not permitted are ground loops via devices that are not disconnected from the
power supply. The device must either be insulated or, if this is not possible,
the power must be correspondingly disconnected in the device.
Note
The programmable fieldbus Controller 750-806 can assume the master op-
eration when being extended by the "DevNet.lib" library.
WAGO-I/O-SYSTEM 750
DeviceNet
128 • Network Communication
Objects, Classes, Instances and Attributes
Other interface modules for programmable logic controls (PLCs) are also of-
fered by other manufacturers.
• Object:
Object is an abstract representation of individual components within a de-
vice belonging to each other. It is defined by its data or attributes, its ex-
ternal functions or services available, and by its defined behaviour.
• Class:
A class includes objects of a product belonging together, it is organized in
instances, e.g. Identity Class, DeviceNet Class.
• Instance:
An instance is composed of various variables (attributes). Differing in-
stances of a class have the same services, the same behaviour and the same
variables (attributes). However, they can have different variable values,
e.g. different connection instances: Expilict Message, Poll I/O or Bit-
Strobe connection instance.
• Attributes:
The attributes represent data provided by a device via DeviceNet. They
contain the current values, e.g. a configuration of an input, such as, for in-
stance Vendor ID, Device Type or Product Name.
• Service:
Services can be applied to classes and attributes. They perform defined ac-
tions, e.g. reading of variables (attributes) or resetting a class.
• Behaviour:
The behaviour defines how a device reacts as a consequence of external
events, such as changed process data, or as a consequence of internal
events, such as expiring timers.
WAGO-I/O-SYSTEM 750
DeviceNet
Module Characteristics • 129
Communication Model
CAN messages are divided into several groups in order to achieve different
priorities.
The CAN Identifier (Connection ID) and with it the priority is built via differ-
ent message groups and the MAC ID.
I/O messages are sent by a node and can be received by one or several other
nodes. Only I/O data is transmitted and no protocol data is specified by this
way.
Explicit messages are sent directly from one node to another. They consist of a
request and an answer. Therefore services can be requested directly from an-
other node. The data field consists of the service identification and the destina-
tion address. The format of the explicit messages is defined. Via explicit mes-
sages devices can be configured or a dynamic built-up of message connections
can be made.
WAGO-I/O-SYSTEM 750
DeviceNet
130 • Process data and Diagnostic Status
I/O Messaging Connections
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).
WAGO-I/O-SYSTEM 750
DeviceNet
Process data and Diagnostic Status • 131
Process Image
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.
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.
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.
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.
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.
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.
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
132 • Process data and Diagnostic Status
Process Image
The digital input data image is transmitted to the master via the corresponding
I/O message connection. The data length is equivalent to the number of digital
input data and is rounded up to full bytes.
The analog input data image is 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.
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 133
EDS Files
Architecture, contents and coding of the EDS files are standardized which
permits design and configuration with devices of different manufacturers.
The EDS file is read by the configuration software and corresponding settings
transmitted. For required entries and handling steps for this purpose, please re-
fer to the software user manuals.
Further information
ODVA informs about the EDS files of all listed manufacturers.
http://www.odva.org
EDS and symbol files to configure the I/O modules are available under the
order numberr 750-912 on a floppy disk or on the WAGO INTERNET home-
page.
http://www.wago.com
WAGO-I/O-SYSTEM 750
DeviceNet
134 • Configuration / Parametering with the Object Model
Object Model
Data Type
USINT Unsigned Short INTeger (8 Bit)
UINT Unsigned INTeger (16 Bit)
USINT Unsigned Short INTeger (8 Bit)
UDINT Unsigned Double INTeger (32 Bit)
BOOL Boolean, True (1) or False (0)
STRUCT Structure of ...
ARRAY Array of ...
Note
In the following, the object model for the fieldbus Coupler 750-306 and the
fieldbus Controller 750-806 are listed. The explicit supplements to the fieldbus
Controller 750-806 can be taken from the following chapter.
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 135
Object Model
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Identity Object, 0x01
Range 1-65535, class definition
upon which the implementation
is based.
Instance 1:
Attribute Used in Access Name Data type Description Default
ID buscoupler rule Value
1 required get Vendor UINT Identification of vendor 40 (0x28)
2 required get Device UINT Indication of general type of 12 (0x0C)
Type product
3 required get Product UINT Identification of particular i. e. 306
Code product of an individual vendor (0x132)
for the
750-306
4 required get Revision Stuct: Revision of the item the Identity i. e. {3;0}
Major/ USINT, object represents for the
Minor USINT 750-306
5 required get Status WORD status of device -
6 required get Serial_ UDINT Serial number of device -
number
7 required get Product SHORT_ Human readable identification i. e.
name STRING „WAGO
(num,char 750-306 V
char...) 3.0)“
for the
750-306
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Returns the contents of the specified attribute
0x05 Reset Invokes the reset service for the device
WAGO-I/O-SYSTEM 750
DeviceNet
136 • Configuration / Parametering with the Object Model
Object Model
no attribute, no services
Instance 0:
Attribute Used in Access Name Data type Description Default
ID buscoupler rule Value
1 required get Revision UINT Revision of the Identity Object, 0x02
Range 1-65535, class definition
upon which the implementation
is based.
Instance 1:
Attribute Used in Access Name Data type Description Default
ID buscoupler rule Value
1 Optional get/set MAC ID USINT Node address 0 - 63
2 Optional get Baud Rate USINT Baud rate 0-2
3 Optional get/set BOI BOOL Bus-off Interrupt 0/1
4 Optional get/set Bus-Off USINT Number of times CAN went to 0 - 255
Counter the bus-off state
5 Optional get Allocation Struct of: s. MAC ID of Master (from 0 - 63, 255
Informa- BYTE, Allocate)
tion USINT
Allocation
Choice
Byte
Master`s
ID
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute value
0x4B Allocate_Master/Slave_Connection Requests the use of the predefined Master/Slave
connection
0x4C Release_Group_2_Identifier_Set Indicates that the specified connections within the
predefined Master/Slave connection set are no
longer desired. These connections are to be released
(deleted)
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Assembly Object, 0x02
Range 1-65535, class definition
upon which the implementation is
based.
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 137
Object Model
12 References to the process image: analog and digital input data plus Error Code
13 References to the process image: analog and digital input data plus Error Code and Error Argument
14 References to the process image: analog and digital input data plus Error Code and Error Argument,
Status
Instance 1:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get/set Process Array of process image, collection of all
of connected image Byte modules process output data.
modules
Instance 2:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get/set Process Array of process image, collection of all
of connected image Byte modules process output data.
modules
Instance 3:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get/set Process Array of process image, collection of all
of connected image Byte analog modules process output
modules data.
Instance 4:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image Byte modules process input data plus
modules status byte.
Instance 5:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image Byte digital modules process input data
modules plus status byte.
Instance 6:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image Byte analog modules process input data
modules plus status byte.
WAGO-I/O-SYSTEM 750
DeviceNet
138 • Configuration / Parametering with the Object Model
Object Model
Instance 7:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image Byte modules process input data
modules
Instance 8:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image Byte digital modules process input data
modules
Instance 9:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image Byte analog modules process input data
modules
Instance 12:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image + Byte analog modules process input data
modules Error plus Error Code (Cl. 100/Inst. 1/
Code Attr. 45)
Instance 13:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image + Byte analog modules process input data
modules Error plus Error Code (Cl. 100/Inst. 1/
Code + Attr. 45)
Error plus Error Argument (Cl. 100/Inst.
Argument 1/ Attr. 46)
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 139
Object Model
Instance 14:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Process Array of process image, collection of all
of connected image + Byte analog modules process input data
modules Error plus Error Code (Cl. 100/Inst. 1/
Code + Attr. 45)
Error plus Error Argument (Cl. 100/Inst.
Argument 1/ Attr. 46)
+ Status plus Status (Cl. 100/Inst. 1/Attr. 5)
Plus Terminal diagnostic *) (Cl.
100/Inst. 1/Attr. 6)
plus Diagnostic value*) (Cl. 100/
Inst. 1/Attr. 47), the diagnostic
value is only valid, if in the Status
is indicated, that a diagnostic
message lies close
*) Diagnostic is only possible for
the Controller 750-806
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute value
Instance 0:
Attribute Used in Access Name Data type Description Default
ID buscoupler rule Value
1 required get Revision UINT Revision of the Connection 0x01
Object, Range 1-65535, class
definition upon which the im-
plementation is based.
WAGO-I/O-SYSTEM 750
DeviceNet
140 • Configuration / Parametering with the Object Model
Object Model
tion_id
6 required get ini- USINT Defines the message groups across which
tial_comm productions and consumptions associated with
_characteri this connection occur
stics
7 required get pro- UINT maximum number of Bytes transmitted across
duced_con this connection
nec-
tion_size
8 required get con- UINT maximum number of Bytes transmitted across
sumed_co this connection
nnec-
tion_size
9 required get/set ex- UINT defines timing associated with this connnec-
pected_pa tion
cket_rate
10-11 N/A get N/A N/A not used
12 required get watch- USINT defines how to handle inactivity/watchdog
dog_time- timeouts
out_action
13 required get pro- UINT number of Bytes in pro-
duced_con duced_connection_path attribute
nec-
tion_path_
length
14 required get/set pro- Array of specifies the application objects which data is
duced_con USINT to be produced by this connection object
nec-
tion_path
15 required get con- UINT number of Bytes in con-
sumed_co sumed_connection_path attribute
nnec-
tion_path_
length
16 required get con- Array of specifies the application objects that are to
sumed_co USINT receive the data consumed by this connection
nnec- object
tion_path
17 required get produc- USINT defines minimum time between new data
tion_inhibi production
t_time
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 141
Object Model
WAGO-I/O-SYSTEM 750
DeviceNet
142 • Configuration / Parametering with the Object Model
Object Model
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 143
Object Model
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute value
0x05 Reset Restores connection default values.
The instances are not available if the connection is in state „non existent“.
Create Get_Atribute/Set_Attribute
Get_Atribute/
Set_Attribute/ Established
Apply_Attributes/
Reset/Message
Produced/Consumed Inactivity/Watchdog
Reset Timeout & watchdog_timeout_action =
Transition to Time Out
Delete
Timed Out
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Acknowledge 0x01
Handler Object, Range 1-65535,
class definition upon which the
implementation is based.
2 required get Max UINT maximum instance number of an 0x01
instance object currently created in this
class level of device
Instance 1:
WAGO-I/O-SYSTEM 750
DeviceNet
144 • Configuration / Parametering with the Object Model
Object Model
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute
value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute
value
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Identity Object, 0x01
Range 1-65535, class definition
upon which the implementation is
based.
2 required get Max UINT maximum instance number of an 0x01
instance object currently created in this
class level of device
Instance 1:
Attribute Used in Access Name Data Description
ID buscoupler rule type
1 specific get/set Bk_Module USINT module number: 0-Coupler, 1- first module, 2-
No 2.module
2 specific get/set Bk_TableNo USINT table number: 0 ... 256; not all existing
3 specific get/set Bk_Register USINT Register number: 0...255 for the Coupler
No (0...63 for modules)
4 specific get/set Bk_Data UINT Register data , Status
5 specific get ProcessState USINT Coupler status: 0x01 module communication
error, 0x02 internal bus error , 0x08: module
diagnostic , 0x80 fieldbus error
6 specific get DNS_i_Trmnl UINT Module diagnostic, 0x8000 to decode a
dia (**) message, High Byte (Bit14...8): channel
number, Low Byte (Bit7..0) Module number
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 145
Object Model
WAGO-I/O-SYSTEM 750
DeviceNet
146 • Configuration / Parametering with the Object Model
Object Model
26 specific get/set BK_DO_FA USINT Defines the behavior after de allocation the
ULT_REAC strobed Connection
TION_ON_ 0: (default) do nothing
RELEASE_ 1: Process the Coupler fault reaction
ST
40 specific get/set BK_static_ UINT Defines how to calculate the values for the
ana- number of analog and digital input bits.
log_digital_i 0000: All bits are digital
nput_mappi 0016: One word is analog remaining bits are
ng digital
0032: Two words are analog remaining bits
are digital
...
0xFFFF: All bits are handled like module type
(default)
41 specific get/set BK_static_ UINT Defines how to calculate the values for the
ana- number of analog and digital input bits.
log_digital_ 0000: All bits are digital
out- 0016: One word is analog remaining bits are
put_mappin digital
g 0032: Two words are analog remaining bits
are digital
...
0xFFFF: All bits are handled like module type
(default)
(If the number of analog bits exceeds the size
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 147
Object Model
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute
value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute
value
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Identity Object, 0x01
Range 1-65535, class definition
upon which the implementation is
based.
2 optional get Max UINT maximum number of instances of 0x256
instance an object currently created in this
class level of the device
Instance 1 to 255:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 dep. on kind get DIPOBJ_ BIT digital input bit 0:off
of connected VALUE 1:on
modules
WAGO-I/O-SYSTEM 750
DeviceNet
148 • Configuration / Parametering with the Object Model
Object Model
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read an object attribute value.
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Identity Object, 0x01
Range 1-65535, class definition
upon which the implementation is
based.
2 optional get Max UINT maximum instance number of an 0x256
instance object currently created in this
class level of device
Instance 1 to 255:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 dep. on kind get/set DOPOBJ_ BIT digital output bit 0:off
of connected VALUE 1:on
modules
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute
value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute
value
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Identity Object, 01
Range 1-65535, class definition
upon which the implementation is
based.
2 optional get Max UINT maximum instance number of an 256
instance object currently created in this
class level of device
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 149
Object Model
Instance 1 to 255:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 dep. on kind get AIPOBJ_ Array of Input data aktual
of connected VALUE Byte input
modules Values
2 dep. on kind get AIPOBJ_ USINT Input data length Number
of connected VALUE of Bytes
modules
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute
value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute
value
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Identity Object, 01
Range 1-65535, class definition
upon which the implementation is
based.
2 optional get Max UINT maximum instance number of an 256
instance object currently created in this
class level of device
WAGO-I/O-SYSTEM 750
DeviceNet
150 • Configuration / Parametering with the Object Model
Object Model
modules
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute
value
0x10 Set_Attribute_Single Used to modify a DeviceNet object attribute
value
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 151
Object Model
4.6.2.2.1 Bit-Strobe
• Produced-Path changeable like a poll connection (if data size more than 8
bytes, only the first 8 bytes are transmitted)
(**)
Descrition of the MemberPath:
0x20 CC 0x24 II 0x30 AA
CC: class
II: instance
AA: attribute
The following classes / instances / attributes are possible:
class:100 instance 1 attribute 5 (ProcessState)
class:100 instance 1 attribute 6 (DNS_i_Trmnldia)
class:101 (Discrete Input Point Object)
class:102 (Discrete Output Point Object)
class:103 (Analog Input Point Object)
class:104 (Analog Output Point Object)
class:160-173 (PLC variables)
Class Services
Service code Service name Service description
0x0Eh Get_Attribute_Single Used to read an Object attribute value
0x08h Create Instantiates an Assembly object within a
specified class. Response contains ins-
tance number.
Instance Services
Service code Service name Service description
0x0Eh Get_Attribute_Single Used to read an Object attribute value
0x10h Set_Attribute_Single Modifies an attribute value
0x09h Delete Deletes an assembly object and releases
all associated resources
WAGO-I/O-SYSTEM 750
DeviceNet
152 • Configuration / Parametering with the Object Model
Object Model
Instance 0:
Attribute ID Used in buscoupler Acces Name DeviceNet Description of attribute Semantics of
Rule data type values
1 Required Get Revi- UINT Revision of this object 0x01
sion
2 Optional Get Max. UINT Max. instance number of 255
instance an object currently created
in this class level of the
device
Services:
Service code Service name Service description
0x0Eh Get_Attribute_Single Used to read an Object attribute value
0x10h Set_Attribute_Single Used to write an Object attribute value
Max. instance: 2
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 153
Object Model
Services:
Service code Service name Service description
0x0Eh Get_Attribute_Single Used to read an Object attribute value
Max. instance: 2
Max. instance: 1
WAGO-I/O-SYSTEM 750
DeviceNet
154 • Configuration / Parametering with the Object Model
Object Model
Max. instance: 1
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 155
Object Model
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)
WAGO-I/O-SYSTEM 750
DeviceNet
156 • Configuration / Parametering with the Object Model
Object Model
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 Heart- 0
Interval beat messages in seconds
4.6.2.2.20 Connection Object (0x05)
Instance 10:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 optional get PLC Array of process image, collection of all
output Byte PLC output variables
variables
Instance 11:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 optional get PLC input Array of process image, collection of all
variables Byte PLC input variables
WAGO-I/O-SYSTEM 750
DeviceNet
Configuration / Parametering with the Object Model • 157
Object Model
WAGO-I/O-SYSTEM 750
DeviceNet
158 • I/O Modules
5 I/O Modules
5.1 Overview
All listed bus modules, in the overview below, are available for modular ap-
plications with the WAGO-I/O-SYSTEM 750.
For detailed information on the I/O modules and the module variations, please
refer to the manuals for the I/O modules.
You will find these manuals on CD ROM „ELECTRONICC Tools and Docs“
(Item-no.: 0888-0412) or on the web pages:
www.wago.com Æ Service Æ Download Æ Documentation.
More Information
Current information on the modular WAGO-I/O-SYSTEM is available in the
Internet under:
www.wago.com
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 159
WAGO-I/O-SYSTEM 750
DeviceNet
160 • I/O Modules
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 161
WAGO-I/O-SYSTEM 750
DeviceNet
162 • I/O Modules
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 163
WAGO-I/O-SYSTEM 750
DeviceNet
164 • I/O Modules
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 165
Process Data Architecture for DeviceNet
Note
Depending on the specific position of an I/O module in the fieldbus node,
the process data of all previous byte or bit-oriented modules must be
taken into account to determine its location in the process data map.
For the PFC process image of the programmable fieldbus controller is the
structure of the process data mapping identical.
When analog input modules are also present in the node, the digital data is al-
ways appended after the analog data in the Input Process Image, grouped into
bytes.
Some digital modules have an additional diagnostic bit per channel in the In-
put Process Image. The diagnostic bit is used for detecting faults that occur
(e.g., wire breaks and/or short circuits).
Each input channel seizes one Instance in the Discrete Input Point Object
(Class 0x65).
750-435
WAGO-I/O-SYSTEM 750
DeviceNet
166 • I/O Modules
Process Data Architecture for DeviceNet
750-400, -401, -405, -406, -410, -411, -412, -427, -438, (and all variations),
753-400, -401, -405, -406, -410, -411, -412, -427
750-418, 753-418
The 750-418, 753-418 digital input module supplies a diagnostic and ac-
knowledge bit for each input channel. If a fault condition occurs, the diagnos-
tic bit is set. After the fault condition is cleared, an acknowledge bit must be
set to re-activate the input. The diagnostic data and input data bit is mapped in
the Input Process Image, while the acknowledge bit is in the Output Process
Image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 167
Process Data Architecture for DeviceNet
750-402, -403, -408, -409, -414, -415, -422, -423, -428, -432, -433,
753-402, -403, -408, -409, -415, -422, -423, -428, -432, -433, -440
When analog output modules are also present in the node, the digital image
data is always appended after the analog data in the Output Process Image,
grouped into bytes.
Each output channel seizes one Instance in the Discrete Output Point Object
(Class 0x66).
750-523
WAGO-I/O-SYSTEM 750
DeviceNet
168 • I/O Modules
Process Data Architecture for DeviceNet
750-501, -502, -509, -512, -513, -514, -517, -535, (and all variations),
753-501, -502, -509, -512, -513, -514, -517
Output Process Image
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
controls controls
DO 2 DO 1
Channel Channel
2 1
The output modules seize 2 Instances in Class (0x66).
The 750-507 (-508), -522 and 753-507 digital output modules have a diagnos-
tic bit for each output channel. When an output fault condition occurs (i.e.,
overload, short circuit, or broken wire), a diagnostic bit is set. The diagnostic
data is mapped into the Input Process Image, while the output control bits are
in the Output Process Image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 169
Process Data Architecture for DeviceNet
750-506, 753-506
The 750-506, 753-506 digital output module has 2-bits of diagnostic informa-
tion for each output channel. The 2-bit diagnostic information can then be de-
coded to determine the exact fault condition of the module (i.e., overload, a
short circuit, or a broken wire). The 4-bits of diagnostic data are mapped into
the Input Process Image, while the output control bits are in the Output Proc-
ess Image.
750-532
The 750-532 digital output modules have a diagnostic bit for each output
channel. When an output fault condition occurs (i.e., overload, short circuit, or
broken wire), a diagnostic bit is set. The diagnostic data is mapped into the
Input Process Image, while the output control bits are in the Output Process
Image.
WAGO-I/O-SYSTEM 750
DeviceNet
170 • I/O Modules
Process Data Architecture for DeviceNet
750-537
The 750-537 digital output modules have a diagnostic bit for each output
channel. When an output fault condition occurs (i.e., overload, short circuit, or
broken wire), a diagnostic bit is set. The diagnostic data is mapped into the
Input Process Image, while the output control bits are in the Output Process
Image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 171
Process Data Architecture for DeviceNet
WAGO-I/O-SYSTEM 750
DeviceNet
172 • I/O Modules
Process Data Architecture for DeviceNet
750-452, -454, -456, -461, -462, -465, -466, -467, -469, -472, -474, -475, -476,
-477, -478, -479, -480, -481, -483, -485, -492, (and all variations),
753-452, -454, -456, -461, -465, -466, -467, -469, -472, -474, -475, -476, -477,
-478, -479, -483, -492, (and all variations)
Input Process Image
Instance Byte Destination Remark
D0
n Measured Value Channel 1
D1
D2
n+1 Measured Value Channel 2
D3
The input modules represent 2x2 bytes and seize 2 Instances in Class (0x67).
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 173
Process Data Architecture for DeviceNet
When digital output modules are also present in the node, the analog output
data is always mapped into the Output Process Image in front of the digital
data.
Each output channel seizes one Instance in the Analog Output Point Object
(Class 0x68).
WAGO-I/O-SYSTEM 750
DeviceNet
174 • I/O Modules
Process Data Architecture for DeviceNet
This allows, for example, setting of a counter with the control byte or display-
ing of overshooting or undershooting of the range with the status byte.
Further information
For detailed information about the structure of a particular module’s con-
trol/status byte, please refer to that module’s manual. Manuals for each
module can be found on the Internet under:
http://www.wago.com.
Counter Modules
The above Counter Modules have a total of 5 bytes of user data in both the In-
put and Output Process Image (4 bytes of counter data and 1 byte of con-
trol/status). The counter value is supplied as 32 bits. The following tables il-
lustrate the Input and Output Process Image, which has a total of 6 bytes
mapped into each image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 175
Process Data Architecture for DeviceNet
750-404/000-005
The above Counter Modules have a total of 5 bytes of user data in both the In-
put and Output Process Image (4 bytes of counter data and 1 byte of con-
trol/status). The two counter values are supplied as 16 bits. The following ta-
bles illustrate the Input and Output Process Image, which has a total of 6 bytes
mapped into each image.
WAGO-I/O-SYSTEM 750
DeviceNet
176 • I/O Modules
Process Data Architecture for DeviceNet
750-638, 753-638
The above Counter Modules have a total of 6 bytes of user data in both the In-
put and Output Process Image (4 bytes of counter data and 2 bytes of con-
trol/status). The two counter values are supplied as 16 bits. The following ta-
bles illustrate the Input and Output Process Image, which has a total of 6 bytes
mapped into each image.
The above Pulse Width modules have a total of 6 bytes of user data in both the
Input and Output Process Image (4 bytes of channel data and 2 bytes of con-
trol/status). The two channel values are supplied as 16 bits. Each channel has
its own control/status byte. The following table illustrates the Input and Out-
put Process Image, which has a total of 6 bytes mapped into each image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 177
Process Data Architecture for DeviceNet
750-650, (and the variations /000-002, -004, -006, -009, -010, -011, -012,
-013)
750-651, (and the variations /000-002, -003)
750-653, (and the variations /000-002, -007)
Note:
With the freely parametrizable variations /003 000 of the serial interface
modules, the desired operation mode can be set. Dependent on it, the
process image of these modules is then the same, as from the appropriate
variation.
The above Serial Interface Modules with alternative data format have a total
of 4 bytes of user data in both the Input and Output Process Image (3 bytes of
serial data and 1 byte of control/status). The following table illustrates the In-
put and Output Process Image, which have a total of 4 bytes mapped into each
image.
WAGO-I/O-SYSTEM 750
DeviceNet
178 • I/O Modules
Process Data Architecture for DeviceNet
The above Serial Interface Modules with Standard Data Format have a total of
6 bytes of user data in both the Input and Output Process Image (5 bytes of se-
rial data and 1 byte of control/status). The following table illustrates the Input
and Output Process Image, which have a total of 6 bytes mapped into each im-
age.
The Data Exchange modules have a total of 4 bytes of user data in both the
Input and Output Process Image. The following tables illustrate the Input and
Output Process Image, which has a total of 4 bytes mapped into each image.
The above SSI Transmitter Interface modules have a total of 4 bytes of user
data in the Input Process Image, which has 4 bytes mapped into the image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 179
Process Data Architecture for DeviceNet
The above SSI Transmitter Interface modules with status have a total of 5
bytes of user data in the Input Process Image, which has 6 bytes mapped into
the image.
750-631
The above Incremental Encoder Interface modules have 5 bytes of input data
and 3 bytes of output data. The following tables illustrate the Input and Output
Process Image, which have 6 bytes into each image.
Input Process Image
Instance Byte Destination Remark
S Status byte
D0
Counter word
D1
n
- not used
D2
Latch word
D3
The specialty modules represent 1x6 bytes input data and seize 1 Instance in
Class (0x67).
WAGO-I/O-SYSTEM 750
DeviceNet
180 • I/O Modules
Process Data Architecture for DeviceNet
750-634
The above Incremental Encoder Interface module has 5 bytes of input data (6
bytes in cycle duration measurement mode) and 3 bytes of output data. The
following tables illustrate the Input and Output Process Image, which has 6
bytes mapped into each image.
Input Process Image
Instance Byte Destination Remark
S Status byte
D0
Counter word
D1
n
(D2)*) (Periodic time)
D3
Latch word
D4
*) If cycle duration measurement mode is enabled in the control byte, the cycle
duration is given as a 24-bit value that is stored in D2 together with D3/D4.
The specialty modules represent 1x6 bytes input data and seize 1 Instance in
Class (0x67).
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 181
Process Data Architecture for DeviceNet
750-637
The above Incremental Encoder Interface Module has a total of 6 bytes of user
data in both the Input and Output Process Image (4 bytes of encoder data and
2 bytes of control/status). The following table illustrates the Input and Output
Process Image, which have 6 bytes mapped into each image.
Input and Output Process Image
Instance Byte Destination Remark
C0/S0 Control/Status byte of Channel 1
n D0
Data Value of Channel 1
D1
C1/S1 Control/Status byte of Channel 2
n+1 D2
Data Value of Channel 2
D3
The specialty modules represent 2x3 bytes input and output data and seize 2
Instances in Class (0x67) and 2 Instances in Class (0x68).
750-635, 753-635
The above Digital Pulse Interface module has a total of 4 bytes of user data in
both the Input and Output Process Image (3 bytes of module data and 1 byte of
control/status). The following table illustrates the Input and Output Process
Image, which have 4 bytes mapped into each image.
Input and Output Process Image
Instance Byte Destination Remark
C0/S0 Control/Status byte
D0
n
D1 Data bytes
D2
The specialty modules represent 1x4 bytes input and output data and seize 1
Instance in Class (0x67) and 1 Instance in Class (0x68).
RTC Module
750-640
The above RTC module has a total of 6 bytes of user data in both the Input
and Output Process Image (4 bytes of module data and 1 byte of control/status
and 1 byte ID for command). The following table illustrates the Input and
Output Process Image, which have 6 bytes mapped into each image.
WAGO-I/O-SYSTEM 750
DeviceNet
182 • I/O Modules
Process Data Architecture for DeviceNet
The DALI/DSI Master module has a total of 6 bytes of user data in both the
Input and Output Process Image (5 bytes of module data and 1 byte of con-
trol/status). The following tables illustrate the Input and Output Process Im-
age, which have 6 bytes mapped into each image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 183
Process Data Architecture for DeviceNet
The EnOcean radio receiver has a total of 4 bytes of user data in both the Input
and Output Process Image (3 bytes of module data and 1 byte of con-
trol/status). The following tables illustrate the Input and Output Process Im-
age, which have 4 bytes mapped into each image.
750-643
The MP Bus Master Module has a total of 8 bytes of user data in both the In-
put and Output Process Image (6 bytes of module data and 2 bytes of con-
trol/status). The following table illustrates the Input and Output Process Im-
age, which have 8 bytes mapped into each image.
WAGO-I/O-SYSTEM 750
DeviceNet
184 • I/O Modules
Process Data Architecture for DeviceNet
750-645
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 185
Process Data Architecture for DeviceNet
The specialty modules represent 4x3 bytes input and output data and seize 4
Instances in Class (0x67) and 4 Instances in Class (0x68).
750-655
The length of the process image of the AS-interface master module can be set
to fixed sizes of 12, 20, 24, 32, 40 or 48 bytes.
It consists of a control or status byte, a mailbox with a size of 0, 6, 10, 12 or
18 bytes and the AS-interface process data, which can range from 0 to 32
bytes.
The first Input and output byte, which is assigned to an AS-interface master
module, contains the status / control byte, the second byte is one empty byte.
Subsequently the mailbox data are mapped, when the mailbox is permanently
superimposed (Mode 1).
In the operating mode with suppressable mailbox (Mode 2), the mailbox and
the cyclical process data are mapped next.
The following bytes contain the remaining process data.
WAGO-I/O-SYSTEM 750
DeviceNet
186 • I/O Modules
Process Data Architecture for DeviceNet
750-610, -611
The 750-610 and 750-611 Supply Modules provide 2 bits of diagnostics in the
Input Process Image for monitoring of the internal power supply.
750-622
The Binary Space Modules 750-622 behave alternatively like 2 channel digital
input modules or output modules and occupy depending upon the selected set-
tings 1, 2, 3 or 4 bits per channel. According to this, 2, 4, 6 or 8 bits are occu-
pied then either in the process input or the process output image.
WAGO-I/O-SYSTEM 750
DeviceNet
Use in Hazardous Environments • 187
Foreword
6.3.1 Divisions
Explosive environments are areas in which the atmosphere can potentially be-
come explosive. The term explosive means a special mixture of ignitable sub-
stances existing in the form of air-borne gases, fumes, mist or dust under at-
mospheric conditions which, when heated beyond a tolerable temperature or
subjected to an electric arc or sparks, can produce explosions. Explosive zones
have been created to describe the concentrations level of an explosive atmos-
phere. This division, based on the probability of an explosion occurring, is of
great importance both for technical safety and feasibility reasons. Knowing
that the demands placed on electrical components permanently employed in an
explosive environment have to be much more stringent than those placed on
electrical components that are only rarely and, if at all, for short periods, sub-
ject to a dangerous explosive environment.
WAGO-I/O-SYSTEM 750
DeviceNet
188 • Use in Hazardous Environments
Classification meeting CENELEC and IEC
Group II: Group II includes electrical components for use in all other
explosive environments. This group is further subdivided by
pertinent combustible gases in the environment.
Subdivision IIA, IIB and IIC takes into account that differ-
ent materials/substances/gases have various ignition energy
characteristic values. For this reason the three sub-groups
are assigned representative types of gases:
IIA – Propane
IIB – Ethylene
IIC – Hydrogen
WAGO-I/O-SYSTEM 750
DeviceNet
Use in Hazardous Environments • 189
Classification meeting CENELEC and IEC
In line with the maximum surface temperature for all ignition protection types,
the electrical components are subdivided into temperature classes, as far as
electrical components of explosion protection group II are concerned. Here the
temperatures refer to a surrounding temperature of 40 °C for operation and
testing of the electrical components. The lowest ignition temperature of the
existing explosive atmosphere must be higher than the maximum surface tem-
perature.
WAGO-I/O-SYSTEM 750
DeviceNet
190 • Use in Hazardous Environments
Classification meeting CENELEC and IEC
The following table represents the division and attributes of the materials to
the temperature classes and material groups in percent:
Temperature classes
T1 T2 T3 T4 T5 T6 Total*
26.6 % 42.8 % 25.5 %
94.9 % 4.9 % 0% 0.2 % 432
Explosion group
IIA IIB IIC Total*
85.2 % 13.8 % 1.0 % 501
*
Number of classified materials
WAGO-I/O-SYSTEM 750
DeviceNet
Use in Hazardous Environments • 191
Classifications meeting the NEC 500
6.4.1 Divisions
The "Divisions" describe the degree of probability of whatever type of dan-
gerous situation occurring. Here the following assignments apply:
Explosion endangered areas due to combustible gases, fumes, mist and dust:
Division 1 Encompasses areas in which explosive atmospheres are to be expected
occasionally (> 10 h ≤ 1000 h /year) as well as continuously and long-term
(> 1000 h /year).
Division 2 Encompasses areas in which explosive atmospheres can be expected rarely
and short-term (>0 h ≤ 10 h /year).
WAGO-I/O-SYSTEM 750
DeviceNet
192 • Use in Hazardous Environments
Classifications meeting the NEC 500
WAGO-I/O-SYSTEM 750
DeviceNet
Use in Hazardous Environments • 193
Identification
6.5 Identification
6.5.1 For Europe
According to CENELEC and IEC
ITEM-NO.:750-400
2DI 24V DC 3.0ms
55°C max ambient
Hansastr. 27
2
D-32423 Minden 0.08-2.5mm
AWG 28-14
24V DC
2101--02----03
LISTED 22ZA AND 22XM
0V 24V DI1
24246
Di2
PATENTS PENDING
op temp code T4A
II 3 G
KEMA 01ATEX1024 X
Grp. A B C D
CL I DIV 2
EEx nA II T4
WAGO-I/O-SYSTEM 750
DeviceNet
194 • Use in Hazardous Environments
Identification
ITEM-NO.:750-400
2DI 24V DC 3.0ms
55°C max ambient
Hansastr. 27
2
D-32423 Minden 0.08-2.5mm
AWG 28-14
24V DC
4100--02----03
LISTED 22ZA AND 22XM
0V 24V DI1
24246
Di2
PATENTS PENDING
op temp code T4A
II 3 G
KEMA 01ATEX1024 X
Grp. A B C D
CL I DIV 2
EEx nA II T4
WAGO-I/O-SYSTEM 750
DeviceNet
Use in Hazardous Environments • 195
Installation regulations
DIN VDE 0101 Installation in power plants with rated voltages above
1 kV
The USA and Canada have their own regulations. The following are excerpts
from these regulations:
WAGO-I/O-SYSTEM 750
DeviceNet
196 • Use in Hazardous Environments
Installation regulations
Danger
When using the WAGO-I/O SYSTEM 750 (electrical operation) with Ex ap-
proval, the following points are mandatory:
The fieldbus independent I/O System Modules Type 750-xxx are to be in-
stalled in enclosures that provide for the degree of ingress protection of at
least IP54.
For use in the presence of combustible dust, the above mentioned modules
are to be installed in enclosures that provide for the degree of ingress pro-
tection of at least IP64.
The fieldbus independent I/O system may only be installed in hazardous areas
(Europe: Group II, Zone 2 or America: Class I, Division 2, Group A, B, C,
D) or in non-hazardous areas!
Installation, connection, addition, removal or replacement of modules, field-
bus connectors or fuses may only take place when the system supply and
the field supply are switched off, or when the area is known to be
non-hazardous.
Ensure that only approved modules of the electrical operating type will be
used. The Substitution or Replacement of modules can jeopardize the suit-
ability of the system in hazardous environments!
Operation of intrinsically safe EEx i modules with direct connection to sen-
sors/actuators in hazardous areas of Zone 0 + 1 and Division 1 type re-
quires the use of a 24 V DC Power Supply EEx i module!
DIP switches and potentiometers are only to be adjusted when the area is
know to be non-hazardous.
Further Information
Proof of certification is available on request. Also take note of the informa-
tion given on the module technical information sheet.
WAGO-I/O-SYSTEM 750
DeviceNet
Glossary • 197
7 Glossary
Bit Smallest information unit. Its value can either be 1 or
0.
WAGO-I/O-SYSTEM 750
DeviceNet
198 • Literature List
8 Literature List
Controller-Area-Network
Grundlagen, Protokolle, Bausteine, Anwendungen
Konrad Etschberger
2., völlig überarbeitete Auflage
2000 Carl Hanser Verlag München Wien
ISBN 3-4446-19431-2
WAGO-I/O-SYSTEM 750
DeviceNet
Index • 199
9 Index
C O
carrier rail · 16, 19 Operating mode
contacts RUN · 69
data- · 20 STOP · 69
power- · 27 Operating mode switch · 69, 72, 78, 86
Controller · 8
Coupler · 8 P
Cycle time · 72
PFC cycle · 78
D PLC cycle · 72
PLC program · 72
data contacts · 20 Power contacts · 21, 27
not carried out · 28
E power jumper contacts · 44
Process image · 47, 62, 72, 105
Electrical isolation · 43, 67
R
F
RAM · 72
Fieldbus interface · 72 RUN · 72
Fieldbus node · 111
Fieldbus start · 72 S
Flag · 72
Flags · 82 Start-up · 72
Flash memory · 72 STOP · 72
Subnet · 156
H
T
Hardware reset · 69
Times · 72
I
U
I/O modules
Address range · 81 unlocking lug · 18
IEC 61131-3 · 105
Internal bus · 65, 72, 103 V
L Variables · 69
WAGO-I/O-SYSTEM 750
DeviceNet
200 • Index
Web: http://www.wago.com
WAGO-I/O-SYSTEM 750
DeviceNet