Io System 750 Series
Io System 750 Series
DeviceNet
750-346
Manual
Technical Description,
Installation and
Configuration
Version 1.0.1
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
WAGO-I/O-SYSTEM 750
DeviceNet
iv • Table of Contents
4 DeviceNet ................................................................................................... 68
4.1 Description ............................................................................................. 68
4.2 Network Architecture ............................................................................. 69
4.2.1 Transmission Media........................................................................... 69
4.2.1.1 Type of Cable................................................................................ 69
4.2.1.2 Cable Types .................................................................................. 69
4.2.1.3 Maximum Bus Length .................................................................. 70
4.2.2 Cabling............................................................................................... 70
4.2.3 Network Topology............................................................................. 72
4.2.4 Network Grounding ........................................................................... 73
4.2.5 Interface Modules .............................................................................. 73
4.3 Network Communication ....................................................................... 74
4.3.1 Objects, Classes, Instances and Attributes ........................................ 74
4.4 Module Characteristics........................................................................... 75
4.4.1 Communication Model ...................................................................... 75
WAGO-I/O-SYSTEM 750
DeviceNet
Table of Contents • v
6 Glossary.................................................................................................... 127
WAGO-I/O-SYSTEM 750
DeviceNet
6 • Important Notes
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
Important Notes • 7
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
8 • Important Notes
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
Important Notes • 9
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
10 • Important Notes
Font Conventions
1.7 Scope
This manual describes the modular WAGO-I/O-SYSTEM 750 with the
DeviceNet ECO fieldbus coupler.
Item-No. Description
750-346 DeviceNet ECO fieldbus coupler, 125 kBaud ... 500 kBaud;
digital and analog signals
WAGO-I/O-SYSTEM 750
DeviceNet
Important Notes • 11
Abbreviation
1.8 Abbreviation
AI Analog Input
AO Analog Output
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 Interconnection (model)
HB High Byte
HW Hardware
LB Low Byte
MAC ID Media Access Control Identifier (nodeaddress)
MS Module Status
NMT Network Management
NS Network Status
RO Read Only
RW Read/Write
SW Software
WAGO-I/O-SYSTEM 750
DeviceNet
12 • The WAGO-I/O-SYSTEM 750
System Description
The ECO coupler contains the fieldbus interface, electronics and a power sup-
ply for the system. The fieldbus interface forms the physical interface to the
relevant fieldbus. The electronics process the data of the bus modules and
make it available for the fieldbus communication. The 24 V system supply is
fed in via the voltage supply.
The ECO coupler is primarily conceived for applications with digital I/O func-
tions. In addition, modules for most different digital and analog I/O functions
as well as special functions can be connected to the ECO coupler. The com-
munication between the ECO coupler and the bus modules is carried out via
an internal bus.
The WAGO-I/O-SYSTEM 750 has a clear port level with LEDs for status in-
dication, insertable mini WSB markers and pullout group marker carriers. The
3-wire technology supplemented by a ground wire connection allows for direct
sensor/actuator wiring.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 13
Technical Data
WAGO-I/O-SYSTEM 750
DeviceNet
14 • The WAGO-I/O-SYSTEM 750
Technical Data
Mechanical strength
Vibration resistance acc. to IEC 60068-2-6
Comment to the vibration restistance:
a) Type of oscillation:
sweep with a rate of change of 1 octave per minute
10 Hz ≤ f < 57 Hz, const. Amplitude 0,075 mm
57 Hz ≤ f < 150 Hz, const. Acceleration 1 g
b) Period of oscillation:
10 sweep per axis in each of the 3 vertical axes
Shock resistance acc. to IEC 60068-2-27
Comment to the shock restistance:
a) Type of impulse: half sinusoidal
b) Intensity of impulse:
15 g peak value, 11 ms maintenance time
c) Route of impulse:
3 impulses in each pos. And neg. direction of the
3 vertical axes of the test object, this means
18 impulses in all
Free fall acc. to IEC 60068-2-32
≤ 1m (module in original packing)
Safe electrical isolation
Air and creepage distance acc. to IEC 60664-1
Degree of pollution 2
acc. to IEC 61131-2
Degree of protection
Degree of protection IP 20
Electromagnetic compatibility*
Directive Test values Strength Evaluation
class criteria
Immunity to interference acc. to EN 50082-2 (96)
EN 61000-4-2 4kV/8kV (2/4) B
EN 61000-4-3 10V/m 80% AM (3) A
EN 61000-4-4 2kV (3/4) B
EN 61000-4-6 10V/m 80% AM (3) A
Emission of interference acc. to Measuring Class
EN 50081-2 (94) distance
EN 55011 30 dBµV/m (30m) A
37 dBµV/m
Emission of interference acc. to Measuring Class
EN 50081-1 (93) distance
EN 55022 30 dBµV/m (10m) B
37 dBµV/m
* Exception: 750-630, 750-631
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 15
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
16 • The WAGO-I/O-SYSTEM 750
Manufacturing Number
Dimensions
A A A A
C C C C
B B B B
D D D D
100
35
50 12 24
65
64
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 17
Component Update
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
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
software version (if available), the hardware version of the component, the
firmware loader (if available) and further internal information for
WAGO Kontakttechnik GmbH.
Update Matrix
Current Version data for: 1. Update 2. Update 3. Update
Production Order NO <- Only starting from Calen-
Number dar week 13/2004
Datestamp DS
Software index SW
Hardware index HW
Firmware loader FWL <- Only for coupler/controller
index
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 ECO fieldbus coupler also the cover of the
configuration interface of the coupler is printed on with the current manufac-
turing and production order number.
The original manufacturing data on the housing of the component remain
thereby.
WAGO-I/O-SYSTEM 750
DeviceNet
18 • The WAGO-I/O-SYSTEM 750
Storage, Assembly and Transport
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.
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
Warning
The maximal total expansion of a node must not exceed 830 mm
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 19
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
20 • 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 • 21
Mechanical Setup
In order to safeguard the ECO coupler from jamming, it should be fixed onto
the carrier rail with the locking disc. To do so, push on the upper groove of the
locking disc using a screwdriver.
To pull out the ECO fieldbus coupler, 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
22 • 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 ECO coupler, 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 recog-
nized, 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 ECO coupler, 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 • 23
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
24 • 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 • 25
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
26 • The WAGO-I/O-SYSTEM 750
Power Supply
• Electronics of the ECO coupler and the bus modules (internal bus).
• All bus modules have an electrical isolation between the electronics (inter-
nal bus, logic) and the field electronics. Some analog input modules have
each channel electrically isolated, please see catalog.
Potential of the system supply
Electrical isolation
to the field level
per channel
Elektronic
DC
DC
Potential Potentials
Fieldbus interface in the field level
Fig. 2-10: Isolation g0xxx11e
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 • 27
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. ECO coupler
electronics, fieldbus interface and bus modules via the internal bus (5 V sys-
tem voltage). The 5 V system voltage is electrically connected to the 24 V sys-
tem supply.
750-343…346 750-613
DC 5 V
DC
0V
DC
Interface
Fieldbus
Electronic
DC
DC
DC 24 V
(-15% / + 20%)
WAGO-I/O-SYSTEM 750
DeviceNet
28 • 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 (ECO coupler 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 supply capacity of the ECO coupler or the internal system supply module
(750-613) can be taken from the technical data of the components.
The internal current consumption is indicated in the technical data for each bus
terminal. In order to determine the overall requirement, add together the val-
ues 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 • 29
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 260 mA. The exact
electrical consumption (I(24 V)) can be determined with the following formulas:
ECO Coupler
I(5 V) total = Sum of all the internal current consumption of the connected
bus modules
+ internal current consumption coupler
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 of the ECO coupler exceeds 260 mA or 500 mA for the 750-613, 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
30 • 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 power supply modules provide field side power (DC 24V). In this case it
is a passive power supply without protection equipment. Power supply mod-
ules are available for different potentials, e.g. DC 24 V, AC 230 V or others.
Likewise, with the aid of the power supply modules, various potentials can be
set up. The connections are linked in pairs with a power contact.
Note
The 24 V field supply can be connected also directly to a bus module, if the
connection points are not needed for the peripheral device supply. In this
case, the connection points need the connection to the power jumper contacts.
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.
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 31
Power Supply
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.
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) g0xxx09e
WAGO-I/O-SYSTEM 750
DeviceNet
32 • 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 • 33
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
34 • The WAGO-I/O-SYSTEM 750
Power Supply
b) 1) 1) d)
a) c)
750-612 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 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
The WAGO-I/O-SYSTEM 750 • 35
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
36 • The WAGO-I/O-SYSTEM 750
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
The WAGO-I/O-SYSTEM 750 • 37
Grounding
Attention
Care must be taken to ensure the direct electrical connection between the car-
rier rail contact and the carrier rail.
WAGO-I/O-SYSTEM 750
DeviceNet
38 • The WAGO-I/O-SYSTEM 750
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
The WAGO-I/O-SYSTEM 750 • 39
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
40 • The WAGO-I/O-SYSTEM 750
Assembly Guidelines / Standards
Fig. 2-24: WAGO Shield (Screen) Connecting System p0xxx08x, p0xxx09x, and p0xxx10x
Fig. 2-25: Application of the WAGO Shield (Screen) Connecting System p0xxx11x
WAGO-I/O-SYSTEM 750
DeviceNet
The WAGO-I/O-SYSTEM 750 • 41
Assembly Guidelines / Standards
WAGO-I/O-SYSTEM 750
DeviceNet
42 • Fieldbus Coupler
Fieldbus Coupler 750-346
3 Fieldbus Coupler
3.1 Fieldbus Coupler 750-346
This chapter includes:
3.1.1 Description......................................................................................... 43
3.1.2 Hardware............................................................................................ 44
3.1.2.1 View .............................................................................................. 44
3.1.2.2 Device Supply ............................................................................... 45
3.1.2.3 Fieldbus Connection ..................................................................... 45
3.1.2.4 Display Elements .......................................................................... 46
3.1.2.5 Configuration Interface ................................................................. 47
3.1.2.6 Hardware Address (MAC ID)....................................................... 47
3.1.2.7 Setting the Baud Rate.................................................................... 48
3.1.3 Operating System............................................................................... 48
3.1.4 Process Image .................................................................................... 49
3.1.5 Data Exchange ................................................................................... 50
3.1.5.1 Communication Interfaces ............................................................ 51
3.1.5.2 Memory Areas .............................................................................. 51
3.1.5.3 Addressing .................................................................................... 52
3.1.5.3.1 Fieldbus Specific........................................................................... 52
3.1.6 Configuration Software ..................................................................... 54
3.1.7 Starting up DeviceNet Fieldbus Nodes.............................................. 54
3.1.7.1 Connecting the PC and Fieldbus Node ......................................... 54
3.1.7.2 Setting the MAC ID and Baud Rate ............................................. 54
3.1.7.3 Configuration with Static Assembly ............................................. 55
3.1.8 LED Display ...................................................................................... 59
3.1.8.1 Node status – Blink code from the 'I/O' LED ............................... 60
3.1.9 Technical Data ................................................................................... 67
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 43
Fieldbus Coupler 750-346
3.1.1 Description
The ECO fieldbus coupler is designed for applications with a reduced scale
I/O requirement. By using digital only process data, or small amounts of ana-
log data, the ECO Fieldbus coupler retains all of the choices that are offered
by the Series 750 I/O.
The coupler has an integrated supply terminal for the system voltage. The field
power jumper contacts are supplied via a separate supply module.
The DeviceNet bus coupler is capable of supporting all I/O modules and au-
tomatically configures, creating a local process image.
DeviceNet allows the storing of the process image in the corresponding Mas-
ter control (PLC, PC or NC).
The local process image is divided into two data zones containing the data re-
ceived and the data to be sent.
The process data can be sent via the DeviceNet fieldbus to the PLC, PC or NC
for further processing, and received from the field via DeviceNet TM.
The data of the analog modules is stored in the process image which is created
automatically according to the order in which the modules are connected to the
buscoupler. The bits of the digital modules are sent byte by byte and added to
the analog data. If the amount of digital information exceeds 8 bits, the bus-
coupler automatically starts with a new byte.
WAGO-I/O-SYSTEM 750
DeviceNet
44 • Fieldbus Coupler
Fieldbus Coupler 750-346
3.1.2 Hardware
3.1.2.1 View
1 2 3 4 5 6 7 8
OVERFL -Fieldbus
DIP switch MS
750-346
RUN
-Fieldbus node
for MAC ID
and baud rate BUS OFF Data contacts
NS
ON
CONNECT
I/O
01 02 03 04
Marking area
Fieldbus
connection
Series 231
(MCS)
Configuration
Supply interface
24 V
0V
• Supply module with internal system supply module for the system supply
• 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-
nosics
• Configuration interface
• Electronics for communication with the I/O modules (internal bus) and the
fieldbus interface
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 45
Fieldbus Coupler 750-346
The supply is made via terminal blocks with CAGE CLAMP® connection.
The device supply is intended for the system unit.
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-346
The integrated internal system supply module generates the necessary voltage
to supply the electronics of the coupler and the connected I/O modules.
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 below shows the connection diagram, the colors resulting in accor-
dance with the DeviceNet specification and are identical to the conductor col-
ors of the DeviceNet cables.
WAGO-I/O-SYSTEM 750
DeviceNet
46 • Fieldbus Coupler
Fieldbus Coupler 750-346
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.
The operating condition of the fieldbus coupler or node is signalled via light
diodes (LED).
DEVICENET
OVERFL
MS
750-346
RUN
BUS OFF
NS
CONNECT
I/O
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 47
Fieldbus Coupler 750-346
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.
8
1 2 3 4 5 6 7 8
7
6
ON 5
4
3
2
ON
Fig. 3-6: Example: Setting of station (node) address MAC ID 1 (DIP 1 = ON) g012548x
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.
WAGO-I/O-SYSTEM 750
DeviceNet
48 • Fieldbus Coupler
Fieldbus Coupler 750-346
The bus 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.
8 Baudrate DIP7 DIP8
1 2 3 4 5 6 7 8
7 *)
6 125 kBaud OFF OFF
ON 5
4 250 kBaud ON OFF
3
2 500 kBaud OFF ON
ON
1
not allowed ON ON
g012549x *)
Presetting
Fig. 3-7: Example: Setting the baud
rate 250 kBaud (DIP 7 = ON) on a
station (node) with the address MAC
ID 1.
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.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 49
Fieldbus Coupler 750-346
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 modules
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 proc-
ess 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
50 • Fieldbus Coupler
Fieldbus Coupler 750-346
For an easy and quick set-up of a connection the DeviceNet fieldbus coupler
750-346 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-346 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.1Assembly Instance".
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 51
Fieldbus Coupler 750-346
For a data exchange, the DeviceNet fieldbus coupler is equipped with two inter-
faces:
• 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 32 bytes for the physical input and 32
bytes for the physical output data.
fieldbus coupler
memory area
fieldbus for input data
I/O modules
1
input
modules
memory area
for output data
2
output
modules
I O
Fig. 3-9: Memory areas and data exchange for a fieldbus coupler g012447e
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 (32 bytes 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
52 • Fieldbus Coupler
Fieldbus Coupler 750-346
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
1 I/O modules
fieldbus
master Consumer
memory area
for output data
Output-
Assemly 2
output
modules
I O
Fig. 3-1: Fieldbus specific data exchange for a DeviceNet fieldbus coupler g012547e
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 • 53
Fieldbus Coupler 750-346
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 CS08 2) CS07 2) CS06 2) CS05 2) CS04 2) CS03 2) CS02 2) CS01 2)
1)
DI = = Digital Input
2)
CS = Coupler Status (The last byte in the input process image is the Status Byte
of the Coupler, CS01...CS08, see also Object 0x64, Instance 1, Attribute 5)
CS01 =1: internal bus error (0x01)
CS02 =1: module communication error (0x02)
CS04 =1: module diagnostic (0x08)
CS08 =1: fieldbus error (0x80)
Output process image:
Default process data, output image (Assembly Class, Instance 1)
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
54 • Fieldbus Coupler
Fieldbus Coupler 750-346
1. 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).
2. Start your PC.
3.1.7.2 Setting the MAC ID and Baud Rate
3. Use the DIP switches 1...6 to set the desired node address (MAC ID). The bina-
ry significance of the individual DIP switches increases according to the switch
number.
8 DIP switch Value
1 2 3 4 5 6 7 8
7
6 1 20
ON 5
4 2 21
3
2 3 22
ON
1
g012550x
4 23
Fig. 3-10: Example: Setting the
5 24
MAC ID 4 (DIP 3 = ON).
6 25
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 55
Fieldbus Coupler 750-346
4. DIP switches 7 and 8 are used to set the desired baud rate.
8 Baud rate DIP7 DIP8
1 2 3 4 5 6 7 8
7
6 125 kBaud*) OFF OFF
ON 5
4 250 kBaud ON OFF
3
2 500 kBaud OFF ON
ON
1
g012551x
not allowed ON ON
Fig. 3-11: Example: Setting the baud *)
rate 250 kBaud (DIP 7 = ON) of the Presetting
station with MAC ID 1.
In this example, the software WAGO NETCON is used for the configuration.
8. 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
56 • Fieldbus Coupler
Fieldbus Coupler 750-346
3. Enter Master
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 p112502d
2. For the DeviceNet Master interface card, click in the left-hand selection
window on the corresponding entry to mark it.
3. Take the Master into the right-hand window by clicking on the "Add" but-
ton and confirm by clicking on the "OK" button.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 57
Fieldbus Coupler 750-346
4. Add a Slave
2. Move this mouse pointer to the graphic display of the fieldbus, then click
on the left-hand mouse key.
Fig.
3-15: Insert slave g012503d
3. For the fieldbus coupler 750-346 click in the left-hand selection window on
the corresponding entry to mark it.
4. Take this 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
58 • Fieldbus Coupler
Fieldbus Coupler 750-346
5. Device Configuration
1. 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 set-
tings.
6. Load Configuration
1. 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 "On-
line" menu.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 59
Fieldbus Coupler 750-346
DEVICENET
OVERFL
750-346 MS
RUN
BUS OFF
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.
Module status
OVERFL RUN State of device Meaning
(red) (green)
off off no power No power supply to the device.
off on device operational The device operates correctly.
off blinking device in standby The device needs to be configured or has been partly
configured.
blinking off minor fault A minor fault has occurred. It exists a diagnostics.
on off unrecoverable fault The device is defective, needs to be serviced or
replaced.
blinking blinking device self testing The device performs a built-in check.
Network status
BUSOFF CONNECT State of device Meaning
(red) (green)
off off not powered, not online No power supply to the device / fieldbus supply /
DeviceNet cable not connected and „Duplicate MAC
ID detection“ is not yet completed.
off blinking online, not connected The device operates correctly at the fieldbus. How-
ever, it has not yet been integrated by a scanner.
off on link ok online, con- The device operates correctly at the fieldbus. At
nected least one connection to another device has been
established.
blinking off connection time out A minor fault has occurred.
on off critical link failure The device has detected a fault. It is unable to per-
form any more functions in the network.
WAGO-I/O-SYSTEM 750
DeviceNet
60 • Fieldbus Coupler
Fieldbus Coupler 750-346
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 Coupler • 61
Fieldbus Coupler 750-346
I/O Meaning
green Data cycle on the internal bus
off No data cycle on the internal bus
red Coupler 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
WAGO-I/O-SYSTEM 750
DeviceNet
62 • Fieldbus Coupler
Fieldbus Coupler 750-346
5 Error occurred with read access Turn off the power supply of the
to serial EEPROM node, exchange fieldbus coupler
and turn the power supply on
again.
6 Changed I/O module configura- Restart the fieldbus coupler by
tion determined after turning the power supply off and
AUTORESET on again.
7 Firmware does not run on exist- Turn off the power supply of the
ing hardware node, exchange fieldbus coupler
and turn the power supply on
again.
8 Time limit exceeded for access- Turn off the power supply of the
ing the serial EEPROM node, exchange fieldbus coupler
and turn the power supply on
again.
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 -Process Image Fault -
Fault argument Fault description Trouble shooting
1 Process image not activ Access on invalid process image.
Please contact the WAGO I/O-
Support (Note the version number
and the configuration)
2 Prozess image is larger than size Reduce the number of I/O modules
of buffer
3 Prozess image is zero Please contact the WAGO I/O-
Support (Note the version number
and the configuration)
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 63
Fieldbus Coupler 750-346
WAGO-I/O-SYSTEM 750
DeviceNet
64 • Fieldbus Coupler
Fieldbus Coupler 750-346
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 65
Fieldbus Coupler 750-346
WAGO-I/O-SYSTEM 750
DeviceNet
66 • Fieldbus Coupler
Fieldbus Coupler 750-346
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.
WAGO-I/O-SYSTEM 750
DeviceNet
Fieldbus Coupler • 67
Fieldbus Coupler 750-346
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
DEMKO 02 ATEX 132273 X
II 3 GD EEx nA II T4
Conformity marking CE
Accessories
EDS files Download: www.wago.com
Miniature WSB quick marking system
Technical data
Max. number of I/O modules 64
Fieldbus
Input process image max. 32 Byte
Output process image max. 32 Byte
Configuration via PC or PLC
Voltage supply DC 24 V (-15 % / + 20 %)
Current consumption
- via power supply terminal typ. at no- 260 mA at 24 V
minal load
- via DeviceNet interface <120 mA at 11 V
Efficiency of the power supply typ. at 80 %
nominal load
Internal current consumption 350 mA at 5 V
Total current for I/O modules 650 mA at 5 V
Dimensions (mm) W x H x L 50 x 65* x 97
(*from top edge of mounting rail)
Weight ca. 120 g
EMC interference resistance gem. EN 61000-6-2 (2)
EMC interference transmission gem. EN 50081-2 (94)
WAGO-I/O-SYSTEM 750
DeviceNet
68 • DeviceNet
Description
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
DeviceNet • 69
Network Architecture
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
70 • DeviceNet
Network Architecture
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
DeviceNet • 71
Network Architecture
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
72 • DeviceNet
Network Architecture
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
DeviceNet • 73
Network Architecture
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
74 • DeviceNet
Network Communication
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
DeviceNet • 75
Module Characteristics
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
76 • DeviceNet
Process data and Diagnostic Status
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
DeviceNet • 77
Process data and Diagnostic Status
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
78 • DeviceNet
Process data and Diagnostic Status
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
DeviceNet • 79
Configuration / Parametering with the Object Model
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
80 • DeviceNet
Configuration / Parametering with the 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 ...
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 81
Configuration / Parametering with the 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, 0x0001
Range 1-65535, class definition
upon which the implementation
is based.
2 optional get Max UINT Maximum instance number 0x0001
Instance
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. 346
Code product of an individual vendor (0x15A),
for the
750-346
4 required get Revision Stuct: Revision of the item the Identity i. e. {1;2}
Major/ USINT, object represents for the
Minor USINT 750-346
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 „750-346“
(num,char for the
char...) 750-346
10 optional get Heartbeat USINT The nominal interval between 0
Interval heartbeat messages in seconds
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
82 • DeviceNet
Configuration / Parametering with the 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)
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 83
Configuration / Parametering with the Object Model
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Assembly Object, 0x0002
Range 1-65535, class definition
upon which the implementation is
based.
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
15 References to the process image: Status plus three zero bytes and analog and digital input data
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.
WAGO-I/O-SYSTEM 750
DeviceNet
84 • DeviceNet
Configuration / Parametering with the Object Model
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.
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
DeviceNet • 85
Configuration / Parametering with the 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)
Instance 15:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
3 dep. on kind get Status Array of Status (Cl. 100/Inst. 1/Attr. 5)
of connected + first zero Byte plus three bytes, which are always
modules byte (‘0’) zero plus analog and digital input
+ second data
zero byte
(‘0’)
+ third
zero byte
(‘0’)
+ Process
image
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 0x0001
Object, Range 1-65535, class
definition upon which the im-
plementation is based.
WAGO-I/O-SYSTEM 750
DeviceNet
86 • DeviceNet
Configuration / Parametering with the Object Model
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 87
Configuration / Parametering with the Object Model
connec- transmits
tion_id
5 required get con- UINT CAN Identifier field value that denotes mes-
sumed_co sage to be received
nnec-
tion_id
6 required get ini- USINT Defines the message groups across which
tial_comm productions and consumptions associated
_character with this connection occur
istics
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 received 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_timeo timeouts
ut_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/set 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
88 • DeviceNet
Configuration / Parametering with the Object Model
nec-
tion_size
8 required get con- UINT maximum number of Bytes received 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_timeo timeouts
ut_action
13 required get pro- UINT number of Bytes in pro-
duced_con duced_connection_path attribute
nec-
tion_path_
length
14 required get 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
DeviceNet • 89
Configuration / Parametering with the Object Model
ut_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/set produc- USINT defines minimum time between new data
tion_inhibi production
t_time
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
WAGO-I/O-SYSTEM 750
DeviceNet
90 • DeviceNet
Configuration / Parametering with the Object Model
Instance 0:
Attribute Used in Access Name Data type Description Wert
ID buscoupler rule
1 required get Revision UINT Revision of the Acknowledge 0x0001
Handler Object, Range 1-65535,
class definition upon which the
implementation is based.
2 required get Max UINT maximum instance number of an 0x0001
instance object currently created in this
class level of device
Instance 1:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get/set Acknowl- UINT time to wait for acknowledge before resend-
edge timer ing range 1-65,535 ms (0 invalid), default 16
ms
2 required get/set Retry limit USINT number of ack timeouts to wait before inform-
ing the producing application of a Re-
tryLimit_Reached event default=1, range 0-
255; default 16 ms
3 required get COS UINT 0x04, connection instance which contains the
Producing path of the producing I/O application object
Connec- which will be notified of ack handler objects
tion
Instance
4 optinal Get Ack List BYTE Maximum number of members in Ack List.
Size
5 Optinal Get Ack List BYTE List of active connection instances which are
Array of receiving Acks.
UINT
6 Optinal Get Data with BYTE Maximum number of members in Data with
Ack Path Ack Path List.
List Size
7 optinal get Data with BYTE List of active connection instance/consuming
Ack Path Array of application object pairs. This attribute is used
List UINT to forward data received with acknowledg-
USINT ment.
Array of
USINT
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 Coupler Configu- 0x01
ration 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
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 91
Configuration / Parametering with the Object Model
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_Trm UINT Module status, 0x8000 to decode a message,
nldia (**) High Byte (Bit14...8): channel number, Low
Byte (Bit7..0) Module number
(**) Object 100 (0x64) Instance 1 Attribute 6
The attribute DNS_i_Trmndia is set depending on the state of the node, i. e.it will be execute a
diagnostic evaluation. This word will only supply valid data, if bit 3 (count up from 0) in Proc-
essState (class 100/Inst1/Attr.5) is set. This bit indicates, that a new diagnostic notification is present
(see description ProcessState).
The diagnostic evaluation is done by bit 15 in the attribute DNS_i_Trmndia.
If a diagnostic error appears, bit 15 is set.
If an error is rectifyed, bit 15 is reset.
As long as at least one diagnostic error is present, the MS LED is blinking red.
If there are a lot of diagnostic notifications at the same time, with every readout of this attribute you
get the next diagnostic notification. If DNS_i_Trmndia = 0, there is current no new diagnostic notifi-
cation. The MS LED changes on green again, not until the readout of the last diagnostic notification
(only if the diagnostic reason is solved).
7 specific get CnfLen. UINT number of I/O Bits for analog output data
AnalogOut words
8 specific get CnfLen. UINT number of I/O Bits for analog input data
AnalogInp words
9 specific get CnfLen. UINT number of I/O Bits for digital output data bits
DigitalOut
10 specific get CnfLen. UINT number of I/O Bits for digital input data bits
DigitalInp
11 specific get/set BK_FAULT USINT An enumerator used to specify fieldbus error
_REACTIO handling
N 0: stop local I/O cycles (default)
1: switch all outputs to 0
2: do nothing
12 specific get/set BK_SEL_S UINT Non volatile power up value for the polled I/O
TORED_PO produced connection path. The attribute is
LL_P_PAT used to hold an enumerator for the assembly
H path and the class and instance for the mod-
ules object (discrete input point...) paths.
Write only instance values that are available
for couplers present module configuration.
(e.g. do not use analog input points if only
digital modules are fixed to the coupler.)
4:analog and digital input data,status
5: only digital input data plus status
6: only analog input data plus status
7: analog and digital input data
8: only digital input data
9: only analog input data
12: analog and digital input data plus
BK_LED_ERR_CODE (C 100, I 1, A45)
13: analog and digital input data plus
BK_LED_ERR_CODE (C 100, I 1, A45) plus
BK_LED_ERR_ARG (C 100, I 1, A46)
14: analog and digital input data plus
BK_LED_ERR_CODE (C 100, I 1, A45) plus
BK_LED_ERR_ARG (C 100, I 1, A46) plus
Status (C 100, I 1 A 5) plus DNS_i_Trmnldia
(C 100, I 1, A6) plus BK_DIAG_VALUE (C
100, I 1, A47)
15: Status (C 100, I 1 A 5) plus three bytes,
which are always zero plus analog and digital
input data
13 specific get/set BK_SEL_S UINT Non volatile power up value for the polled I/O
TORED_PO consumed connection path. The attribute is
WAGO-I/O-SYSTEM 750
DeviceNet
92 • DeviceNet
Configuration / Parametering with the Object Model
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 93
Configuration / Parametering with the Object Model
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
of the process image all bits are mapped to
analog bits.
42 specific get/set BK_specific UINT Defines the couplers functionality.
_coupler_b 0xFFFF: All possible functions are enabled.
ehavior (resetting a bit to 0 disables the assigned
functionality).
It is only possible to reduce the functionality.
Resetting to „1“ is ignored.
43 specific get/set BK_revisio UINT Defines the couplers major and minor revision
n_setting attribute.
0xFFFF: The major and minor revison Attrib-
utes are set by the firmware.
(This is the default behavior).
0x??00: The minor revison is set to 0.
0x03??: The mjor revison is set to 3.
All other values are valid to.
45 specific get BK_LED_ER UINT Defines the Error Code, displayed by the
R_CODE blink code of the I/O LED.
46 specific get BK_LED_ER UINT Defines the Error Argument, displayed by the
R_ARG blink code of the I/O LED.
47 specific get BK_DIAG_V UINT Defines the Diagnostic information, supplied
ALUE by the IO Module. This attribute must be read
out before attribute 6 of this class. Only if
attribute 6 contains valid data, it contains also
valid data.
48 specific get/set BK_FIXED_P USIN Fixed width of the ProduceConnectionSize
ROD_SIZE T (input data) 0xFFFF(default): ProduceCon-
nectionSize corresponds to the data width of
the connected input modules 0 – 32 (
PI_LIMIT ): Fixed width of the ProduceCon-
nectionSize, independent of the input mod-
ules. PI_LIMIT – 0xFFFE: These values
These values cannot be set and led to fault
messages. The adjusted value become only on
valid with next switching.
49 specific get/set BK_FIXED_C USIN Fixed width of the ConsumedConnectionSize
ONS_SIZE T (output data)
WAGO-I/O-SYSTEM 750
DeviceNet
94 • DeviceNet
Configuration / Parametering with the Object Model
0xFFFF(default): ConsumedConnectionSize
corresponds to the data width of the con-
nected output modules 0 – 32 ( PI_LIMIT ):
Fixed width of the ConsumedConnectionSize,
independent of the output modules.
PI_LIMIT – 0xFFFE: These values These
values cannot be set and led to fault messages.
The adjusted value become only on valid with
next switching.
50 specific get/set reserved UINT 0xFFFF
51 specific get/set BK_FBC_CF UINT Defines configuration settings
G Bit 0: =1 switches off global the announce-
ment of active diagnostic messages via the
MS LED. The diagnostic messages are trans-
ferred however further over the fieldbus. A
change of this attitude becomes only active
after a PowerOn cycle.
Bit 1..15 reserved.
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 Discrete Input 0x01
Point Object, Range 1-65535, class
definition upon which the imple-
mentation is based.
2 optional get Max UINT maximum number of instances of 0x00ff
instance an object currently created in this
class level of the device
Description of the instances:
Instance ID Description
1 Reference to the first digital input point
2 Reference to the next digital input point
...
255 Reference to the last possible digital input point
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
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read an object attribute value.
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 95
Configuration / Parametering with the Object Model
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of the Discrete Output 0x01
Point Object, Range 1-65535, class
definition upon which the imple-
mentation is based.
2 optional get Max UINT maximum instance number of an 0x00ff
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 Analog Input Point 0x0001
Object, Range 1-65535, class
definition upon which the imple-
mentation is based.
2 optional get Max UINT maximum instance number of an 0x0010
instance object currently created in this
class level of device
WAGO-I/O-SYSTEM 750
DeviceNet
96 • DeviceNet
Configuration / Parametering with the Object Model
Instance 1 to 16:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 dep. on kind get AIPOBJ_ Array of Input data actual
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 Analog Output 0x01
Point Object, Range 1-65535, class
definition upon which the imple-
mentation is based.
2 optional get Max UINT maximum instance number of an 0x0010
instance object currently created in this
class level of device
Instance 1 to 16:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 dep. on kind get AOPOBJ_ Array of output data actual
of connected VALUE Byte output
modules value
2 dep. on kind get AOPOBJ_ USINT output 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
WAGO-I/O-SYSTEM 750
DeviceNet
DeviceNet • 97
Configuration / Parametering with the Object Model
Instance 0:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 required get Revision UINT Revision of this Object. 1 (0x0001)
2 optional get Max UINT maximum number of instances -
instance
Instance 1 to 65:
Attribute Used in Access Name Data type Description Value
ID buscoupler rule
1 dep. on kind get ModulDe- WORD Description of the connected actual
of connected scription modules output
modules (Instance 1 = Coupler/Controller, value
Instance 2 = Module 1,...)
Bit 0: Module with inputs,
Bit 1: Module with outputs,
Bit 8-14: Data width internal in
bits
Bit 15: 0/1 Analog/Digital module,
For analog modules the bits 1-14
describe the type of module i. e.
460 for the module 750-460
Services:
Service Code Service Name Description
0x0E Get_Attribute_Single Used to read a DeviceNet Object attribute
value
WAGO-I/O-SYSTEM 750
DeviceNet
98 • 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 • 99
WAGO-I/O-SYSTEM 750
DeviceNet
100 • I/O Modules
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 101
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 103
WAGO-I/O-SYSTEM 750
DeviceNet
104 • I/O Modules
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 105
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
106 • I/O Modules
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 • 107
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
108 • I/O Modules
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 • 109
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
110 • I/O Modules
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 • 111
WAGO-I/O-SYSTEM 750
DeviceNet
112 • I/O Modules
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 • 113
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
114 • I/O Modules
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 • 115
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
116 • I/O Modules
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 Output
Process Image, which has a total of 6 bytes mapped into each image.
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 117
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 se-
rial data and 1 byte of control/status). The following table illustrates the Input
and Output Process Image, which have a total of 4 bytes mapped into each im-
age.
WAGO-I/O-SYSTEM 750
DeviceNet
118 • I/O Modules
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 In-
put 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 • 119
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
120 • I/O Modules
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 • 121
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
122 • I/O Modules
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 • 123
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
124 • I/O Modules
750-645
WAGO-I/O-SYSTEM 750
DeviceNet
I/O Modules • 125
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
126 • I/O Modules
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
Glossary • 127
6 Glossary
Bit Smallest information unit. Its value can either be 1 or
0.
WAGO-I/O-SYSTEM 750
DeviceNet
128 • Literature List
7 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 • 129
8 Index
C L
carrier rail ................................................................................. 19, 22 Light diodes ...................................................................................45
contacts locking disc.....................................................................................21
data- .......................................................................................... 23
power-................................................................................. 30, 31 P
D Power contacts ..........................................................................24, 30
not carried out...........................................................................31
data contacts ................................................................................... 23
S
E
Subnet ...........................................................................................137
Electrical isolation.......................................................................... 45
U
F
unlocking lug ..................................................................................21
Fieldbus node ................................................................................. 77
W
I
word-alignment.............................................................................115
I/O Modules.................................................................................. 108
WAGO-I/O-SYSTEM 750
DeviceNet
WAGO Kontakttechnik GmbH & Co. KG
Web: http://www.wago.com