HDB e 10

Handbuch
Manual
Manuel
Cube67
BN-DN 56507
CUBE67
Bus System Manual
DeviceNet
Art. No. 56 507 Cube67 BN-DN
- For use in combination with SW Version 1.xx -
Manual Art. No. 56 984 Version 1.0
Murrelektronik GmbH P.O. Box 1165 71567 Oppenweiler Tel. ++49 7191 47-0
Falkenstrasse 3 71570 Oppenweiler Fax ++49 7191 47-130
Internet : http://www.murrelektronik.com
Cube67 DeviceNet Bus System Manual
Contents
1 About this Manual ................................................................................................... 1
1.1 Overview of Chapters.....................................................................................................................1
1.2 Symbols and Safety Instructions..................................................................................................1
2 Safety Instructions .................................................................................................. 3

2.1 Explanation of Symbols.................................................................................................................3
2.1.1 Use of Notes ..............................................................................................................................3
2.1.2 Use of Hazard Warnings ...........................................................................................................3
2.1.3 Use of Numbering in Figures ...................................................................................................3
2.1.4 Use of Action Instructions .......................................................................................................3
2.1.5 Use of Footnotes .......................................................................................................................3
2.2 Intended Purpose ...........................................................................................................................4
2.3 Qualified Personnel........................................................................................................................5
3 Configuration Notes ................................................................................................ 6

3.1 DeviceNet System Description .....................................................................................................6
3.2 System Data ....................................................................................................................................7
3.3 Information for First-Time Users ..................................................................................................8
3.4 System Cables ................................................................................................................................9
3.5 Calculating the Line Length ........................................................................................................10
3.6 System Connectors......................................................................................................................11
3.7 System Power Supply ..................................................................................................................12
3.8 Wire Cross-Sections ....................................................................................................................14
3.9 Electromagnetic Compatibility (EMC) ........................................................................................15

3.9.1 Protection Against Electrostatic Discharge .........................................................................15
3.9.2 Grounding ................................................................................................................................16
3.9.3 Cable Routing ..........................................................................................................................16
3.9.4 Blackouts and Brownouts......................................................................................................16
3.9.5 Separate Power Supplies .......................................................................................................16
3.9.6 Interference Suppression of Inductive Loads ......................................................................17
3.9.7 Don't let limitations limit you .................................................................................................17
4 Installation and Wiring .......................................................................................... 19

4.1 Connecting the DeviceNet Bus ...................................................................................................19
4.1.1 Pin Assignment of the M12 Bus Connection .......................................................................19
4.1.2 Terminating the DeviceNet Line ............................................................................................20
4.1.3 Connecting a Terminating Resistor ......................................................................................20
5 Startup ................................................................................................................... 21
5.1 EDS File......................................................................................................................................... 21
5.1.1 Standard EDS File................................................................................................................... 21
5.1.2 Modular EDS Files .................................................................................................................. 22
5.2 Cube67 Standard EDS Generator............................................................................................... 23
5.3 Assigning and Generating DeviceNet Addresses and Baud Rates........................................ 24
5.4 Configuration ............................................................................................................................... 25

5.4.1 Configuration Example .......................................................................................................... 25
5.4.1.1 Presentation of I/O Data - Simplified Representation of Example Configuration.............. 26
5.4.1.2 Presentation of I/O Data - Detailed Representation of Example Configuration ................ 26
5.5 Parameterization .......................................................................................................................... 27

5.5.1 Digital I/O Modules ................................................................................................................. 28
5.5.1.1 Input / Diagnostic Input Function....................................................................................... 28
5.5.1.2 Input NO Contact / NC Contact Function .......................................................................... 28
5.5.1.3 Input / Output Function...................................................................................................... 30
5.5.1.4 Error Action........................................................................................................................ 31
5.5.1.5 Error Value ........................................................................................................................ 33
5.5.2 Function Module Cube67 CNT2 C 4xM12 – Art. No. 56 750................................................ 35
5.5.2.1 Counter 0 Operating Mode................................................................................................ 35
5.5.2.2 Counter 1 Operating Mode................................................................................................ 36
5.5.2.3 Counter 0 Comparison Value ............................................................................................ 36
5.5.2.4 Counter 1 Comparison Value ............................................................................................ 36
5.5.2.5 Counter 0 Counter Status.................................................................................................. 36
5.5.2.6 Counter 1 Counter Status.................................................................................................. 36
5.5.2.7 COMDRV - SAP 0 ............................................................................................................. 37
5.5.2.8 Examples of COMDRV Application ................................................................................... 38
5.5.3 Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760................................................................... 39
5.5.3.1 Input / Diagnostic Input Function....................................................................................... 39
5.5.3.2 Input NO Contact / NC Contact Function .......................................................................... 39
5.5.3.3 Input / Output Function...................................................................................................... 39
5.5.3.4 Error Action........................................................................................................................ 40
5.5.3.5 Error Value ........................................................................................................................ 40
5.5.3.6 RS485 Operating Mode..................................................................................................... 41
5.5.3.7 RS485 Baud Rate.............................................................................................................. 41
5.5.3.8 RS485 Send ...................................................................................................................... 41
5.5.3.9 RS485 Echo ...................................................................................................................... 41
5.5.3.10 RS485 Handshake ............................................................................................................ 41
5.5.3.11 RS485 XOFF Timeout....................................................................................................... 42
5.5.3.12 RS485 Send Delay ............................................................................................................ 42
5.5.4 Cube67 Logic 4xM12 – Art. No. 56 771 ................................................................................. 43
5.5.5 Analog Input Modules ............................................................................................................ 44
5.5.5.1 Selection of Measuring Range and Filter Art. Nos. 56 700 / 56 701 / 56 730................... 44
5.5.5.2 Filter Description Art. Nos. 56 700 / 56 701 / 56 730 ........................................................ 44
5.5.5.3 Application of Delta Value Art. Nos. 56 700 / 56 701 / 56 730.......................................... 45
5.5.5.4 Additional Settings Art. Nos. 56 700 / 56 701 / 56 730 ..................................................... 45
5.5.5.5 Filter Description Art. Nos. 56 740 / / 56 748 .................................................................... 46
5.5.5.6 Module Operating Mode – Global Module Settings Art. Nos. 56 740 / 56 748 ................. 46
5.5.5.7 Selection of Connectivity Art. No. 56 740.......................................................................... 46
5.5.5.8 Resistance Selection Art. No. 56 740................................................................................ 47
5.5.5.9 Thermocouple Selection Art. No. 56 748 .......................................................................... 47
5.5.5.10 Analog Output Modules..................................................................................................... 47
5.5.5.11 Selection of Voltage Setpoint Range................................................................................. 47
5.5.5.12 Additional Settings............................................................................................................. 48
5.5.5.13 Use of Error Value..............................................................................................................48

5.5.6 Parameter Access via Explicit Message Service .................................................................49
5.5.7 Saving Parameters to Flash Memory ....................................................................................52
5.5.8 Checking the Configuration after a Voltage Reset ..............................................................52
5.5.9 Operating Modes .....................................................................................................................53
5.5.9.1 Polling ................................................................................................................................53
5.5.9.2 Change of State .................................................................................................................53
5.5.9.3 Cyclic..................................................................................................................................53
5.6 Mapping of I/O Data......................................................................................................................54

5.6.1 Input Data.................................................................................................................................55
5.6.2 Output Data..............................................................................................................................55
5.6.3 Overview of I/O Data Lengths of Cube67 Modules ..............................................................56
5.7 Format of I/O Data ........................................................................................................................57

5.7.1 Bus Node..................................................................................................................................57
5.7.2 Digital I/O Modules ..................................................................................................................58
5.7.2.1 Inputs .................................................................................................................................58
5.7.2.2 Outputs...............................................................................................................................59
5.7.3 Function Modules....................................................................................................................61
5.7.3.1 Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760 .............................................................61
5.7.3.1.1 Input Data .....................................................................................................................61
5.7.3.1.2 Output Data ..................................................................................................................63
5.7.3.2 Cube67 CNT2 C 4xM12 – Art. No. 56 750 ........................................................................64
5.7.3.2.1 Input Data .....................................................................................................................64
5.7.3.2.2 Output Data ..................................................................................................................65
5.7.4 Cube67 Logic 4xM12 – Art. No. 56 771..................................................................................66
5.7.4.1.1 Input Data .....................................................................................................................66
5.7.5 Analog I/O Modules.................................................................................................................67
5.7.5.1 Inputs .................................................................................................................................67
5.7.5.2 Outputs...............................................................................................................................67
5.7.5.3 Analog Value Representation ............................................................................................68
5.7.5.3.1 Art. Nos. 56 700 / 56 730..............................................................................................68
5.7.5.3.2 Art. Nos. 56 710 / 56 720..............................................................................................69
5.7.5.3.3 Art. No. 56 740 RTD .....................................................................................................70
5.7.5.3.4 Art. No. 56 748 TH........................................................................................................71
5.8 Step by Step: Startup Example ...................................................................................................73

5.8.1 Mechanical Configuration ......................................................................................................73
5.8.1.1 Assembling the Bus Node Hood ........................................................................................73
5.8.1.2 Connecting System Components ......................................................................................74
5.8.2 Configuration with RSNetWorx Version 4.XX or Higher .....................................................75
6 Diagnostics ............................................................................................................ 77
6.1 Diagnostics via DeviceNet Bus...................................................................................................77
6.1.1 Bus Node Diagnostic Format.................................................................................................77
6.1.1.1 Bus Node Diagnostic Format, Byte 0.................................................................................78
6.1.1.2 Communication/Configuration Diagnostic, Byte 1/2 ..........................................................79
6.1.1.3 Module Diagnostic, Byte 3/4 ..............................................................................................79
6.1.2 Group Diagnostic Format .......................................................................................................80
6.2 Displays on Bus Node..................................................................................................................81

6.2.1 Displays for DeviceNet Status ...............................................................................................81
6.2.2 Displays of the Internal System Connection........................................................................82
6.2.3 Bus Node Response to Defective Supply Voltages.............................................................83
6.2.3.1 Internal System Connection: Sensor Power Supply Short-Circuit.....................................83
6.2.3.2 Internal System Connection: Short-Circuit of Actuator Power Supply...............................83
6.2.3.3 Internal System Connection: Undervollage of Sensor Power Supply ............................... 83

6.2.3.4 Internal System Connection: Undervoltage of Actuator Power Supply............................. 84
6.2.4 Other Fault States................................................................................................................... 84
6.2.4.1 Open Internal System Connection .................................................................................... 84
6.2.4.2 Open Field Bus Connection or I/O Connection Timeout ................................................... 84
6.3 Displays of the Digital I/O Modules............................................................................................ 85

6.3.1 LED Displays of the Digital I/O Modules .............................................................................. 85
6.3.1.1 Bus IN LED Display ........................................................................................................... 85
6.3.1.2 External Power – LED Display (Art. Nos. 56 600, 56 640)................................................ 86
6.3.1.3 M12 Sockets – LED Diagnostic Display............................................................................ 86
6.3.2 Relationship between Signal-Logic Image and LED Response......................................... 87
6.4 Displays of Analog I/O Modules ................................................................................................. 88

6.4.1 Bus IN LED Display ................................................................................................................ 88
6.4.1.1 M12 Sockets – LED Diagnostic Display............................................................................ 88
6.5 Displays on Power Distributor.................................................................................................... 90
6.6 Displays on Valve DO16/DO8/DO32 and Cable DIO8 / M16 ..................................................... 91

6.6.1 Bus IN LED Display ................................................................................................................ 91
6.6.2 DIAG LED Display................................................................................................................... 91
6.6.3 Displays on Valve DO16 C K3 ............................................................................................... 92
7 Extended Functions in I/O Modules .................................................................... 94

7.1 General.......................................................................................................................................... 94
7.2 SAP Format................................................................................................................................... 94
8 List of Figures ....................................................................................................... 95
9 List of Tables ......................................................................................................... 96

Manual Supplements / Corrections
Version Section Supplement / Correction Date/Name

1.0 Performed by 12.06.06 M.H./Hi
Notes:
1 About this Manual

Care must be taken to read this instruction manual before you put Cube67 into operation. The instruction
manual should be kept in a safe place accessible to all users at all times.
Instruction manuals for the Cube67 product line are divided into 3 parts:
Cube67 System Manual, Art. No. 56 970
Cube67 Bus System Manual Profibus Art. No. 56 980

DeviceNet Art. No. 56 981
CANopen Art. No. 56 982
Ethernet Art. No. 56 983
Cube67 Technical Data Art. No. 56 971.
The texts, figures, charts and examples used in this manual serve only to explain the operation and use
of input/output modules of the Cube67 product line.
If you have any further queries regarding the installation and startup of the devices described in this
manual, please contact us. We will be pleased to assist you at any time.
Murrelektronik GmbH P.O. Box 1165 71567 Oppenweiler Tel. ++49 7191 47-0
Falkenstrasse 3 71570 Oppenweiler Telefax ++49 7191 47130
Internet: http://www.murrelektronik.com
www.cube67.com
Murrelektronik reserves the right to change technical specifications or contents of this manual at any time
without notice.
1.1 Overview of Chapters

Care must be taken to read the chapter on "Wiring" before you use the products and the system. It
contains important information for safe setup and handling.
The chapter on "Wiring" contains information on the bus connections for the bus node. It is directed
specifically towards trained electricians responsible for the assembly and installation of system
components. Refer to the "Technical Data" manual for more important information on installation.
The chapter "Startup" is intended for specialist personnel with responsibility for startup. It provides
important information for quick and easy startup in a DeviceNet network.
The chapter entitled "Configuration Notes" is intended for system planners and contains important
information on successful configuration.
1.2 Symbols and Safety Instructions

Please pay attention to our safety instructions. Before putting the Cube67 System into operation, read
Chapter 2 in the Cube67 System Manual.
Cube67 System Manual Sec. 2.3 contains explanations of the symbols used in this manual.
V 1.0 1
2 Safety Instructions
2.1 Explanation of Symbols
2.1.1 Use of Notes

Notes pointing out important information are marked in a special way. They are represented as follows:
Note text........
2.1.2 Use of Hazard Warnings

Hazard warnings are additionally placed in a frame.
CAUTION:
Failure to observe safety precautions can result in damage to devices and other
physical assets.
WARNING:
Failure to observe the appropriate safety precautions represents a danger to the
life and health of the user.
2.1.3 Use of Numbering in Figures

Numbering in figures are represented by white numbers in round, black boxes.
Example: Text 1......
Text 2…...
Text 3…...
Explanations are given in tables under the same number, and refer directly to the preceding figure.
2.1.4 Use of Action Instructions

An action instruction describes a sequence of operations which must be strictly adhered to, such as
installation, startup, operation and maintenance.
Numbering is continuous in ascending order by means of black numbers in round, white boxes.
Example: Instruction 1….....
Instruction 2….....
Instruction 3….....
2.1.5 Use of Footnotes
Additional information is marked by superscript digits (Example: Text Text 1) Text Text). They are
explained in the form of footnotes below tables, or at the foot of the page in the case of running text.
V 1.0 3
2.2 Intended Purpose
The devices described in this manual are used as decentralized input/output units for connection to a
DeviceNet network.
The products described in this manual
• have been developed, manufactured, qaulity-controlled and documented in accordance with the
applicable safety standards. These products do not normally represent a danger to persons or
property if the handling specifications described for system planning and design, assembly, operation
with the intended purpose, and safety instructions are observed.
• meet the requirements specified in the
• EMC Directive (89/336/EEC)

• PLC Standard EN61131-2
• are designed for use in industrial applications. A feature of the industrial environment is that
consumers are not directly connected to the public low-voltage power network. Extra precautions are
required for use in residential, business and commercial applications.
Warning
This is a Class A device. This device can cause radio-frequency interference
in residential rooms. In such cases, the operator can be asked to take appropriate
precautions.
Troublefree and safe functioning of the product can only be assured through proper transportation,
storage, installation, assembly and operation with proper care and attention.
Use of the device for its intended purpose is only assured if the housing is fully mounted.
The power supply must correspond to SELV or PELV standards. Power supplies conforming with EN
61558-2-6 (transformers) or EN 60950-1 (switched-mode power supply) meet this requirement.
System configuration, installation, startup, maintenance and testing of devices may only be performed by
an accredited, trained electrician familiar with automation technology safety standards.
The safety and accident prevention regulations valid for specific applications must be observed during the
configuration, installation, startup, maintenance and testing of devices.
Only cables and accessories may be installed provided they conform with the requirements and
regulations for safety, electromagnetic compatibility and, where applicable, telecommunications terminal
equipment, as well as the specifications.
Information regarding cables and accessories approved for installation can be obtained from the
Murrelektronik subsidiary in your region, and may also be found in this manual.
4 V 1.0
2.3 Qualified Personnel
The requirements for qualified personnel are based on requirements profiles defined by ZVEI and VDMA.
Weiterbildung in der Automatisierungstechnik (Advanced Training in Automation Technology)

Publisher : ZVEI and VDMA
Maschinenbau Verlag
P.O. Box 71 08 64
60498 Frankfurt
Only electricians who are familiar with the contents of this manual are authorized to install and maintain
the described products.
These are persons who
• are able to assess the work to be done and identify potential hazards on the basis of their specialist
training, knowledge, experience and their knowledge of the applicable standards.
• based on years of experience working in a comparable field of activity, have an equivalent level of
knowledge to a person with specialist training.
The hardware and software of our products must only be modified by specialist personnel of
Murrelektronik if such modifications are not described in this manual.
Warning
Unqualified tampering with hardware or software or failure to observe the warnings
in this manual may result in severe personal injury or damage to property.
V 1.0 5
3 Configuration Notes
3.1 DeviceNet System Description

DeviceNet is based on international standards (EN50325, IEC62026-1, IEC62026-3) and commonly used
CAN (Controller Area Network) technology (OSI Layers 1 and 2).
Plug&Play connectivity and power supply over the network cable (or an auxiliary power cable) make
startup and maintenance easier.
Manufacturers which market certified DeviceNet products are generally members of the Open DeviceNet
Vendor Association (ODVA)
Figure 3-1 shows the DeviceNet Conformance Tested logo and the general DeviceNet logo . Certified
devices bear the DeviceNet Conformance Tested logo. You will find an overview of certified DeviceNet
products on the web at the ODVA website.
Our active membership in ODVA has provided Murrelektronik with a broad-based knowledge of
DeviceNet and this flows back into the development of components for this bus system.
You will find us and the ODVA on the web at:
www.murrelektronik.com, www.cube67.com, www.odva.org und www.can-cia.com
Figure 3-1: DeviceNet Conformance Tested logo and the general DeviceNet logo
The figure below shows an example of a DeviceNet network topography. A typical feature of DeviceNet is
that the bus cable provides the power supply for DeviceNet users.
Trunk Leitung (Fernleitung) 3 2

2
1 1
1
1 1
1
1 1 1 1
1
1
Verzweigte Dropleitung (Stichleitung) Zero Drop Kurze Dropleitungen
1- Network nodes
2- Terminating resistor
3- Tap1
Figure 3-2: DN system topology
1
Tap T-piece
6 V 1.0
3.2 System Data
The table below lists the main system data.
Table 3-1: DN system data

Feature Description
Topology Tree topology
Twisted shielded 4-wire cable, separate wires for data (white and blue)
Transmission route
and power (black and red)
Line length Main line, max. 500 m, tap line length, max. 6 m
Number of bus users Max. 64
Number of I/O points Dependent on controller
Addresses One unique MAC ID within 0 to 63 range per device
Address type MAC ID, serial number (32 bits)
Dependent on line length (max. 500 Kbit/s)
500 Kbit/s to 100 m (Thick Cable)
Transmission rates 250 Kbit/s up to 250 m (Thick Cable)
125 Kbit/s up to 500 m (Thick Cable)
Maximum length of main line with repeaters: 3 km
Useful data 8 bytes per telegram
Terminating resistors 121 Ω, at each end of data line
Error detection Identification of errored messages, automatic repetition
Power supply 24 VDC tolerance (total) +/- 4%
V 1.0 7
3.3 Information for First-Time Users
DeviceNet is an industrial field bus system whose advantages include simple handling in the project
engineering and application phases, and a clear layout of the overall system.
To make first-time use much simpler and safer, we advise you to follow the procedure in the checklist
below:
Table 3-2: DeviceNet step-by-step guide to first-time system use

Work Stage Questions Answers
What is the total number of This helps to decide whether one or several
Planning Stage
inputs and outputs required? DeviceNet networks are required.
This is important to select the right size of system
What is the power requirement power supply unit. DeviceNet system power supply
Planning Stage
of the DeviceNet? units can be switched in parallel by means of a
diode.
What is the total system If the sum of all line lengths exceeds 500 m,
Planning Stage
expansion size? repeaters must be used.
How are the addresses A plan should be made to avoid address errors.
Configuration
assigned to the modules? Label the addressed modules with great care.
Depends on the module protection degree. Either in
the control cabinet or terminal box; modules with IP
How are the modules
Installation 67 protection degree should be placed as close as
installed?
possible to sensors and actuators for maximum
rationalization.
In configuration mode (scans the DeviceNet
What is the system
Startup network), profiles of the DeviceNet devices are read
configuration?
in automatically by the setup tool.
If all DeviceNet users have been detected, the
Are all DeviceNet users scanner should display no error message (if the
Startup
detected by the scanner? users were included in the scan list). This permits
extensive diagnostics.
How is a simple I/O function Simply and understandably with special easy-to-use
Startup
test carried out? setup tools2. Or via the PLC software,
2
e.g. Allen Bradley KFD box (1770).
8 V 1.0
3.4 System Cables

Round cables or DeviceNet profile flat cables can be used for system cabling on the field bus side,
depending on the requirements of various applications.
Two electrical criteria are decisive when selecting suitable transmission lines:
a) DC resistance (wire cross-section)
for reasons of auxiliary power transmission
b) Transmission properties
Impedance of 121 ohms (1/4, 1/2 W or more)
Murrelektronik offers a number of preterminated M12 round cables to fit Cube67.
The cable make-up is 4-wire in all cases. The cable requires shielding due to the applied transmission
technology.
CAUTION:
The maximum permitted current in Thin Cable (DeviceNet specification of ODVA
Version 2.0 Chapter 10) is 1.5 A.
Table 3-3: Relation between transmission rate and main line length
Data
Length of main line (Thin Cable) Total length of tap line
rate
500 100 meters 39 meters
Kbit/s
Kbit/s
Kbit/s
Make sure that the DeviceNet bus is correctly terminated between CAN_H and CAN_L
(121 Ω ). A terminating resistor must be fitted to each end of the main line.
V 1.0 9
3.5 Calculating the Line Length

If the distance from a tap in the main line to the furthest device is greater than the distance to the nearest
terminating resistor, then this tap line length (Drop A-C) is included in the calculation for the total cable
length.
Example :
3m
1,5m 50m 12m
Drop A 1m
Drop B 5m
Netz- 6m
knoten Drop C
Netz-
knoten
Netz-
knoten
Figure 3-3: Example network for calculating cable length

Drop A: not included in the max. cable length 1.5 m > 1 m
Drop B: included in the max. cable length 3m>5m
Drop C: not included in the max. cable length 12 m > 6 m
Maximum cable length: 5 m + 50 m + 12 m = 67 m
The cumulative tap line length results from the sum of all tap lines in the cable system. This sum may not
exceed the maximum cumulative length referred to the transmission rate (see Cable table).
Example :
2m
4m 6m
1m 5m
3m
1m
4m
3m
2m 3m
1m 3m
3m 2m
Figure 3-4: Example of cable length calculation

A total of 13 devices are connected. No device is further than 6 m from the main line tap. The cumulative
length is 45 m. This means that a maximum data rate of 250 Kbit/s is used.
10 V 1.0
3.6 System Connectors
Figure 3-5: Overview of DN connectors
Micro-style connector (M12)

Mini-style connector (7/8“)
Open-style connector (only in IP20 zone)
V 1.0 11
3.7 System Power Supply
DeviceNet modules require a typical DC voltage of 24 VDC that complies with the specifications for
DeviceNet industrial power supplies.
It is recommended to draw the power for sensors and actuators from different power
supplies in order to achieve greater immunity from interference and decoupling.
We recommend the use of primary switched-mode power supplies both for the
DeviceNet bus and for sensors and actuators.
If linear regulated power supplies are used, make sure that the power supply unit
shuts down with a sufficiently long delay in the event of a fault (short-circuit, etc.).
The power rating of the power supply units is dependent on the number and power demand of the
connected loads.
Power Conductor
24 volt Signal Conductor
24 volt
Power Power
Supply Supply
Back-Up Supply
Power Tap
Node Node Node Node Node Node
Figure 3-6: DeviceNet system power supply units
The power supply units of DeviceNet systems require a DC voltage in the range of 23.76 V to 24.24 VDC
(24 V +/- 1%) in compliance with IEC regulations regarding Protective Extra-Low Voltage (PELV).
Figure 3-7 shows the circuit diagram of a power tap.
A power supply unit can be switched at any point in the network. Only power taps
with Schottky diodes may be used.
12 V 1.0
Signal
Signal
Shield
V-
Fuse Fuse
V+
Schottky Diode
V- V+
Gnd
Network Power Supply
Figure 3-7: DeviceNet power tap

Maximum function reliability and associated troublefree operation are dependent on urgent compliance
with system supply voltage and system-side limits.
CAUTION:
In all cases, it must be ensured that the system voltage does not undershoot 23.04
VDC (24 V – 4%) measured at the furthest user, viewed from the system power
supply.
Dependent on the load current, there is a voltage drop across the system line as a result of the central
power supply of DeviceNet users and connected sensors by the DeviceNet system power supply unit.
In critical cases, optimization is achievable by changing the location of the system

power supply within the overall system and by using power supply lines with a larger
wire cross-section (Thick Cable, Thin Cable, Flat Cable).
Bus node electronics are supplied from the DeviceNet bus. Cube67 I/O modules are powered by the
sensor power supply. The sensor power supply is fed to the 7/8“ socket. At least two voltages are
required to operate the system (bus voltage and sensor supply).
V 1.0 13
3.8 Wire Cross-Sections
DC resistance is the decisive factor when selecting a suitable transmission line from the aspect of power
transmission.
The diagrams below are extracts from the ODVA specification (Chapter 10-2.1).
3,5
2,5
1,5
0,5
0
0 10 (33) 20 (66) 30 (98) 40 (131) 50 (164) 60 (197) 70 (230) 80 (262) 90 (295) 100
(328)
Network length [m] ([feet])
Figure 3-8: Loading capacity of Thin Cable as a function of cable length
Table 3-4: Impact of different line lengths

Network length 0 10 20 30 40 50 60 70 80 90 100
[m] ([feet]) (33) (66) (98) (131) (164) (197) (230) (262) (295) (328)
Max. current [A] 3.00 3.00 3.00 2.06 1.57 1.26 1.06 0.91 0.80 0.71 0.64
9
8
7
6
5
4
3
2
1
0
0 25 (82) 50 100 150 200 250 300 350 400 450 500
(164) (328) (492) (656) (820) (984) (1148) (1312) (1476) (1640)
Network length [m] ([feet])
Figure 3-9: Loading capacity of thick cable as a function of cable length
Table 3-5: Impact of different line lengths

Network length 0 25 50 100 150 200 250 300 350 400 450 500
[m] ([feet]) (82) (164) (328) (492) (656) (820) (984) (1148) (1312) (1476) (1640)
Max. current [A] 8.00 8.00 5.42 2.93 2.01 1.53 1.23 1.03 0.89 0.78 0.69 0.63
14 V 1.0
3.9 Electromagnetic Compatibility (EMC)
This device meets the requirements specified in EC Directive 89/336/EEC

"Electromagnetic compatibility"
CAUTION:
This equipment complies with Classes A and B. The responsibility for conformance
with EMC requirements of the overall system is borne by the system constructor
alone.
Each of the devices described in this manual meets the EMC requirements specified in the relevant
standards. However, this does not guarantee their electromagnetic compatibility when used in a system.
For this reason, the user is urgently advised to comply with the following instructions to obtain
installations conformant with EMC standards. It can only be assumed that the overall system is in
compliance with the applicable EMC requirements if these conditions are met and if individually CE-
labelled components are used.
The system constructor alone is responsible for ensuring that the overall system complies with the
applicable EMC requirements.
3.9.1 Protection Against Electrostatic Discharge
The products described in this manual contain complex semiconductor components which can be
destroyed or damaged by electrostatic discharge (ESD). Damage will not necessarily result in an
immediately detectable failure or malfunction. Failures or malfunctions can occur with a delayed effect or
sporadically.
Caution:
Do not plug or unplug connectors live.
The generally accepted safety precautions for ESD-sensitive devices must be observed when handling
the devices. The following precautions in particular must be taken:
Caution:
Before handling the devices, operatives must discharge themselves from any
electrostatic charge. This can be done by touching a grounded part of the system
or by carrying an ESD static-dissipative grounding tape connected to ground.
Caution:
Unused sockets must be provided with a blank plug.
V 1.0 15
3.9.2 Grounding
A low-impedance connection of the shortest possible length between the ground terminal and reference
ground is required in order to dissipate interference voltages between the device and reference ground.
The inductance of standard FE 3conductors is a high impedance for high-frequency interference
voltages. For this reason, the use of grounding straps is advised. If this is no possible, a fine-wire FE
conductor should be selected with the largest possible cross-section and the connection to ground should
be kept as short as possible.
3.9.3 Cable Routing

A frequent cause of EMC problems is nonobservance of elementary cable routing rules.
The field bus line must be routed as far away as possible from power lines.
A minimum distance of 10 cm must be maintained.
Data and power lines may only cross at right angles.
It is recommended that data and power lines be laid in separate, shielded ducts.
The interference potential of other devices or cables must be taken into account during cable laying.
The greatest possible distance must be maintained to frequency inverters, motor lines and other
devices or cables that emit high frequency interference.
3.9.4 Blackouts and Brownouts

The power supply to the electronics is buffered by integrated capacitors in such a way that short voltage
interruptions do not normally impair operation. This does not apply to power supply to the sensors and
actuators connected to Cube67, the high power demand of which cannot be protected by capacitors that
are integratable in the device.
An interruption in sensor power supply < 1 ms does not cause any change to the input status reported to
the bus master as a result of the integrated input filter. Longer interruptions in sensor supply may lead to
input signal changes. Interruptions in actuator voltage may directly lead to undesired switching processes.
3.9.5 Separate Power Supplies
The sensors and actuators can be supplied via a common power supply unit. However, a separate supply
is recommended in order to maximize the electromagnetic compatibility of the complete system.
3
FE function ground
16 V 1.0
3.9.6 Interference Suppression of Inductive Loads

The outputs of the devices described in this manual have an integrated protective circuit that provides
safety against high-energy interference voltages such as those which occur when switching inductive
consumers.
Varistor Inductive load

(e.g. solenoid valve)
The varistor ensures rapid dissipation of the energy stored in the magnetic field of the inductive load.
The high voltages on shutdown of inductive loads result in strong fields in the cables with consequential
faults in adjacent circuits or devices. For this reason, we recommend additional switching of inductive
loads if there are greater distances between module output and load if there are other reasons. As a
result, the voltage peak produced by the inductive load will be short-circuited directly at the source.
Murrelektronik GmbH can supply you with a wide selection of interference

suppression products for this purpose.
3.9.7 Don't let limitations limit you
There are system configurations where the requirements for noise emission or immunity from interference
can only be met by additional measures, or cannot be met at all, because the EMC within the system is
also dependent on the individual components of other manufacturers.
Mains filters are a suitable means of reducing line-conducted interference.

Various manufacturers supply optical fibre converters. Data transmitted across optical fibres is
generally immune to interference. However, this does not apply to the electronics required for
conversion purposes. Therefore, the use of optical fibres cannot solve all EMC problems.
If you have any further queries regarding EMC, or if you are seeking advice on how to
ensure compliance of your systems with the EMC Directive, please contact our
accredited test centre.
MURRELEKTRONIK Test Centre

Grabenstr. 27
D-71 570 Oppenweiler
Tel.: +49 7191 47334
Fax: +49 7191 47323
Pruefzentrum@murrelektronik.de
V 1.0 17
4 Installation and Wiring
This chapter only contains information on wiring the bus connection to the bus node.
For other bus node wiring options, please refer to the "Technical Data" manual.
4.1 Connecting the DeviceNet Bus
4.1.1 Pin Assignment of the M12 Bus Connection
Plug Socket
3 2 2 3
5 5
4 1 1 4
BUS IN BUS OUT
Contact No. Signal Wire Colour Definition

1 Shield Bus shield
2 V+ red 24 VDC bus node supply
3 V- black 0 VDC bus node supply
4 CAN_H white CAN_HIGH
5 CAN_L blue CAN_LOW
Thread FE Function ground
Figure 4-1: Bus contact assignments
The shield is connected to the bus node at high impedance to FE in accordance with ODVA
recommendations. The hood of the bus node has FE potential and no direct connection to the shield.
V 1.0 19
4.1.2 Terminating the DeviceNet Line
Bus cable
Braided shield
CAN_H (shield)
CAN_L ( blue)
Stranded wire V+ (red)
Stranded wire V- (black)
40 mm
7 mm
Figure 4-2: Terminating the DeviceNet bus line
4.1.3 Connecting a Terminating Resistor
The DeviceNet network must be terminated by a terminating resistor at both ends.
Art. No. Designation

55 319 Terminating resistor connector
20 V 1.0
5 Startup
Before startup, make sure that the field bus is configured in accordance with system
requirements and is tested by professional service technicians.
Users that have an identical MAC ID fail to complete the MAC ID test. The NS LED
lights up red after the self-test.
Each device type has an EDS file (*.eds) and a symbol image (*.ico).
5.1 EDS File

An EDS file4 is required to start up a DeviceNet user.
The Cube67 bus node supports the functionality of the modular EDS file. An EDS file is always required
to configure the Cube67 system and additional EDS files for any expansion modules. However, not every
configuration software supports the module EDS file format. In this case, a standard EDS file must be
generated.
CAUTION:
Changes to EDS files may only be carried out by Murrelektronik technical personnel.
5.1.1 Standard EDS File
You can produce a standard EDS file using the standard Murrelektronik EDS Generator. A separate EDS
file must be generated for each Cube67 configuration. The file is then imported into the configuration
program.
If your DeviceNet environment does not support the functionality of the modular EDS
file, the Cube67 System can also be put into operation using standard EDS files.
However, in this case, make sure that only one EDS file describes the overall system.
For this reason, the EDS file must be adapted to the system topology (e.g. different
number of expansion modules).
4
Electronic Data Sheet
V 1.0 21
5.1.2 Modular EDS Files
The current DeviceNet specification (5/2006) contains the specification for modular EDS files which
permit the startup of modular systems without the use of a manufacturer-specific configuration tool or the
need for user adaptations in the EDS file. Allan-Bradley RS-Networx for DeviceNet from Version 3.21.00
(Build 27) or higher supports modular EDS files.
Not all DeviceNet tools already support the current specification. To find out whether the modular EDS
files of the tool you are using are supported, please consult the tool manufacturer.
Modular EDS files can be obtained over the web from http://www.murrelektronik.com or ordered through
your Murrelektronik branch.
Modular EDS files describe each I/O module and bus node by means of separate EDS files. It is therefore
necessary to import several EDS files into the configuration software.
22 V 1.0
5.2 Cube67 Standard EDS Generator

The EDS Generator is a software for the generation of standard EDS files.
The Cube67 Standard EDS Generator can be downloaded from the Murrelektronik website
www.murrelektronik.com or obtained from the Customer Service Centre (CSC).
Figure 5-1: Cube67 Standard EDS Generator
Module configuration can be carried out by drag'n'drop. Select the module you require by choosing it from
the list box. Hold down the left mouse button and position the module in the line you require. Always
place compact modules, e.g. Art. No. 56600, as the last module in the line.
The Configurator saves the configuration file with the extension *.CS2. This file only contains the module
order. The generated EDS file contains the module configuration corresponding to the order selected.
The modules are parameterized in the DeviceNet configuration software which you are using.
V 1.0 23
5.3 Assigning and Generating DeviceNet Addresses and Baud Rates

x 10 x1
9 01 9 01
NA - Node Address
23
23
78
78
45 6 45 6
0 ... 63
9 01 >63 no comunication
23
DR - Data Rate
78
45 6
0 125 kbit/s
1 250 kbit/s
2 500 kbit/s
>2 no communication
When assigning addresses, make sure that an explicit and unique address is
assigned to each DeviceNet user in the network.
The set address is read in after the power supply voltage is applied. The address
cannot be changed without removing the hood.
Since the DeviceNet address on the device is not visible from the exterior without
removing the hood, we urgently advise you to mark the devices accordingly on the
labels provided.
When assigning the baud rate, make sure that the same baud rate is assigned to each
DeviceNet user.
The configured baud rate is read in only once after the power supply voltage is
applied. The baud rate cannot be changed without removing the hood.
Since the DeviceNet address on the device is not visible from the exterior without
removing the hood, we urgently advise you to mark the devices accordingly on the
labels provided.
24 V 1.0
5.4 Configuration
The Cube67 System is normally configured using a configuration tool provided by the
PLC manufacturer. In this case, you can skip the technical details described in this
chapter. A configuration example using RSNetworx is provided in chapter 5.8 Step by
Step: Startup Example.
The Cube67 system can only be configured with a DN Scanner if the scanner supports
the format of the modular EDS files. If your scanner does not support this format,
please contact our Technical Support for assistance.
5.4.1 Configuration Example

Figure 5-2 shows a typical configuration.
Figure 5-2: Configuration example for IDs

Bus node Cube67 DIO8 C 4xM12 in line 3
Cube67 DIO8C 4xM12 in Line 0 Internal system connection
Cube67 DIO8 C 8xM8 in Line 1 DeviceNet
Cube67 DIO16 C 8xM12 in line 2 Power supply
Table 5-1: Relationship between display in RSNetworx and actual layout

Internal system
Slot (list index) Module
connection
0 Cube67 BN-DN
1 Cube67 DIO8 C 4xM12 Line 0
5 Cube67 BN-DN Diagnostic
V 1.0 25
5.4.1.1 Presentation of I/O Data - Simplified Representation of Example

Configuration
Table 5-2: Format of I/O data referred to the configuration example
Description Module Byte
Input data Module 1, 2, 3 and 4 0 to 6

Input
Diagnostic Bus node 7 to 11

Output
Output data Module 1, 2, 3 and 4 0 to 6
The format of module I/O data is described in sections 5.7ff.
5.4.1.2 Presentation of I/O Data - Detailed Representation of Example

Configuration
Table 5-3: Detailed format of the I/O data referred to the configuration example
Byte Length Module / Line Description Reference to data format
0 Input data, channels 00 to 03
2 0
2 1 1 Input data, channels 00 to 07
3 Input data, channels 00 to 07 see Chapter 5.7.2.1 ff.
2 2
2 3
7 1 Bus node diagnostic
8
2 5 Communication/configuration diagnostic
9 BN see Chapter 5.7.1 ff.
10
2 Module diagnostic
11
Table 5-4: Output data map of sample configuration

Byte Length Module / Line Description Format Reference Table
0 0 Output data, channels 00 to 03
2
1 Output data, channels 10 to 13
2 1 1 Output data, channels 00 to 07
3 2 Output data, channels 00 to 07 see Chapter 5.7.2.2 ff.
2
2 3
5
BN - bus node
26 V 1.0
5.5 Parameterization
Parameterization is normally accomplished using the configuration software supplied with the controller.
This software must be capable of understanding and processing modular EDS files. If you use such a
configuration software, you can skip this chapter as the information is supplied to you in the EDS file (see
Figure 5-3).
Figure 5-3: Parameterization in EDS file (e.g. RSNetWorx)
With some Cube67 I/O modules, not all parameter bytes accessible via EDS are fully
occupied. They must always be written with "0" as bits marked as reserved.
V 1.0 27
5.5.1 Digital I/O Modules
5.5.1.1 Input / Diagnostic Input Function
Table 5-5: Bit assignment, input / diagnostic input function (only 8xM12 modules)
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- 17 16 15 14 13 12 11 10 n/a n/a n/a n/a n/a n/a n/a n/a
nel
Table 5-6: Bit assignment, input / diagnostic input function (only 4xM12 modules)
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- n/a n/a n/a n/a 13 12 11 10 n/a n/a n/a n/a n/a n/a n/a 00
nel
Table 5-7: Value assignment, input / diagnostic input function
Bit Definition
value
0 Input with NO or NC contact function
1 Diagnostic input
n/a Channel not available
5.5.1.2 Input NO Contact / NC Contact Function
Table 5-8: Bit assignment, NO contact / NC contact function (only 8xM12 modules)
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- 17 16 15 14 13 12 11 10 07 06 05 04 03 02 01 00
nel
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- n/a n/a n/a n/a 13 12 11 10 n/a n/a n/a n/a 03 02 01 00
nel
Bit 7 6 5 4 3 2 1 0
Chan- 07 06 05 04 03 02 01 00
nel
Table 5-11: Bit assignment, input NO contact / NC contact function, Art.Nos. 56 661 /56 663 / 56 6650
Bit 7 6 5 4 3 2 1 0
Chan- 08 07 06 05 04 03 02 01
nel
28 V 1.0
Table 5-12: Bit assignment, input NO contact / NC contact function, Art.No. 56 662
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
nel
Table 5-13: Bit assignment, input NO contact / NC contact channel function, Art.Nos. 56 681 / 56 691
Bit 7 6 5 4 3 2 1 0
Chan- X0 07 X0 06 X0 05 X0 04 X0 03 X0 02 X0 01 X0 00
nel
Chan- X1 07 X1 06 X1 05 X1 04 X1 03 X1 02 X1 01 X1 00
nel
Table 5-14: Value assignment,input NO contact / NC contact function
Bit Definition
value
0 NO function
1 NC function
V 1.0 29
5.5.1.3 Input / Output Function
Table 5-15: Bit assignment, input / output function (only 8xM12 modules)
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- 17 16 15 14 13 12 11 10 07 06 05 04 03 02 01 00
nel
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- n/a n/a n/a n/a 13 12 11 10 n/a n/a n/a n/a 03 02 01 00
nel
Bit 7 6 5 4 3 2 1 0
Chan- 07 06 05 04 03 02 01 00
nel
Table 5-18: Bit assignment, input / output function, Art.Nos. 56 661 / 56 663 / 56 6650
Bit 7 6 5 4 3 2 1 0
Chan- 08 07 06 05 04 03 02 01
nel
Table 5-19: Bit assignment, input / output function, Art.No. 56 662
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
nel
Table 5-20: Bit assignment, input input / output channel function, X1 00…X1 07 Art.Nos. 56 681 / 56 691
Bit 7 6 5 4 3 2 1 0
Chan- X1 07 X1 06 X1 05 X1 04 X1 03 X1 02 X1 01 X1 00
nel
Table 5-21: Value assignment, input / output function
Bit Definition
value
1 Output
30 V 1.0
5.5.1.4 Error Action
Table 5-22: Bit assignment, error action, Art. No. (only 8xM12 modules)
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 17 16 15 14 13 12 11 10 07 06 05 04 03 02 01 00
Table 5-23: Bit assignment, error action (only 4xM12 modules)
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel n/a n/a n/a n/a 13 12 11 10 n/a n/a n/a n/a 03 02 01 00
Table 5-24: Bit assignment, error action (only 8xM8 modules)
Bit 7 6 5 4 3 2 1 0
Channel 07 06 05 04 03 02 01 00
Table 5-25: Bit assignment, error action, Art.Nos. 56 650 / 56 651
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
Table 5-26: Bit assignment, error action, Art.No. 56 655
Bit 7 6 5 4 3 2 1 0
Channel 07 06 05 04 03 02 01 00
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
Channel 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17
Table 5-28: Bit assignment, error action, Art.Nos. 56 661 / 56 663
Bit 7 6 5 4 3 2 1 0
Channel 08 07 06 05 04 03 02 01
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
Bit 7 6 5 4 3 2 1 0
Channel Skip +24 V n/a n/a n/a n/a n/a n/a
V 1.0 31
Table 5-31: Bit assignment, error action function, channels X1 00…X1 07 Art.Nos. 56 681 / 56 691
Bit 7 6 5 4 3 2 1 0
Channel X1 07 X1 06 X1 05 X1 04 X1 03 X1 02 X1 01 X1 00
Table 5-32: Value assignment, error action
Bit Definition
value
1 Output value corresponds to error value (default)
0 Initial value is retained in case of error (last state)
32 V 1.0
5.5.1.5 Error Value
Table 5-33: Bit assignment, error value (only 8xM12 modules)
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 17 16 15 14 13 12 11 10 07 06 05 04 03 02 01 00
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit 7 6 5 4 3 2 1 0
Channel 07 06 05 04 03 02 01 00
Table 5-36: Bit assignment, error value, Art.Nos. 56 650 / 56 651
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
Table 5-37: Bit assignment, error value, Art.No. 56 655
Bit 7 6 5 4 3 2 1 0
Channel 07 06 05 04 03 02 01 00
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
Channel 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Table 5-39: Bit assignment, error value, Art.Nos. 56 661 / 56 663
Bit 7 6 5 4 3 2 1 0
Channel 08 07 06 05 04 03 02 01
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
Bit 7 6 5 4 3 2 1 0
Channel Skip +24 V n/a n/a n/a n/a n/a n/a
V 1.0 33
Table 5-42: Bit assignment, error value function, channels X1 00…X1 07 Art.Nos. 56 681 / 56 691
Bit 7 6 5 4 3 2 1 0
Channel X1 07 X1 06 X1 05 X1 04 X1 03 X1 02 X1 01 X1 00
Table 5-43: Value assignment, error value
Bit Definition
value
0 Output has status 0
34 V 1.0
5.5.2 Function Module Cube67 CNT2 C 4xM12 – Art. No. 56 750
The Cube67 CNT2 C 4xM12 – Art. No. 56 750 is controlled via a communication driver
(COMDRV) in the useful data. The following parameter settings are also settable via
the COMDRV. The function of the COMDRV is described in section COMDRV - SAP 0 .
Table 5-44: Settings of Parameter Word 0
Bit Parameter Function Description

position
0 – Motorola data format Default setting
0 Word order
1 – Intel data format Word exchange
1, 2 reserved reserved
0 – Report diagnostic Transfer channel-related diagnostic
3 Diagnostic
1 – Do not report diagnostic Suppress channel-related diagnostic
4 ... 7 reserved reserved
0 – Enable
8 DO_0 Output 0
1 - Disable
0 - Not inverted
9 GATE_0 Enable counter 0
1 - Inverted
10 reserved reserved
0 - Not inverted
11 DO_0 Output 0
1 - Inverted
12 … 15 reserved reserved
0 – Enable
16 DO_1 Output 1
1 - Disable
0 - Not inverted
17 GATE_1 Enable counter 1
1 - Inverted
18 reserved reserved
0 - Not inverted
19 DO_1 Output 1
1 - Inverted
20 … 31 reserved reserved
5.5.2.1 Counter 0 Operating Mode
Table 5-45: Settings of Counter 0
Bit Value Parameter Selection Description

0 Counter 0 0 Counter disabled
0-31 1 operating Mode 0 Event count Mode 0
mode
>1 reserved Mode 0
V 1.0 35
5.5.2.2 Counter 1 Operating Mode
Table 5-46: Settings of Counter 1
Bit Value Parameter Selection Description

0 Counter 1 0 Counter disabled
0-31 operating
1 Mode 0 Event count Mode 0
>1 mode reserved Mode 0
5.5.2.3 Counter 0 Comparison Value
Table 5-47: Counter 0 comparison value
Byte 3 2 1 0
Format VZ Comparison value (Bit 0…31)
Representation in two's complement.
5.5.2.4 Counter 1 Comparison Value
Table 5-48: Comparison value Counter 1
Byte 3 2 1 0
Format VZ Comparison value (Bit 0…31)
5.5.2.5 Counter 0 Counter Status
Table 5-49: Counter 0 counter status
Byte 3 2 1 0
Format VZ Counter status (Bit 0…31)
5.5.2.6 Counter 1 Counter Status
Table 5-50: Counter 1 counter status
Byte 3 2 1 0
Format VZ Counter status (Bit 0…31)
36 V 1.0
5.5.2.7 COMDRV - SAP 0

The counter module (CNT2 C 4xM12) is controlled by a communication driver (COMDRV). The COMDRV
is integrated in the module I/O data. An Explicit Message Service is not necessary.
COMDRV allows data read/write or the execution of services from the I/O module.
The following access codes are written in the output data CTRL (Byte 2):
Table 5-51: Permissible values for the control byte

Write access Read access
Byte 192dec C0hex 128dec 80hex
Double word 224dec E0hex 160dec A0hex
Please note the parameter format of the I/O module when deploying the COMDRV.
Table 5-52: Supported indexes of SAP 0 of Cube67 CNT2 4xM12 – Art.No. 56 750
SAP Access Designation Default Description

Index value
0 Write Control 0 Control SAP
1 Read Status 0 Status SAP
2 Read MAX_WR_ADR 28 Highest permissible index for write access
3 Read MAX_RD_ADR 28 Highest permissible index for read access
4 Write PWD_HIGH 0 Reserved
5 Write PWD_LOW 0 Reserved
6 Read Version 0 SW Version
7 Read Version 1 COMDRV
8 Read 0 LSB
9 Read 0
Counterwert0 Counter status 0
10 Read 0
11 Read 0 MSB
12 Read 0 LSB
13 Read 0
Counterwert1 Counter status 1
14 Read 0
15 Read 0 MSB
0 Global module settings Bits 0 to 7 of
16 Read/write Parameter[0]
Parameter Word 0 (see also Table 5-44)
17 Read/write Parameter[1] 0 Settings of Counter 0 Bits 8 to 15 of
18 Read/write Parameter[2] 0 Reserved
19 Read/write Parameter[3] 0 LSB
20 Read/write Parameter[4] 0
Counter 0 comparison value
22 Read/write Parameter[6] 0 MSB
23 Read/write Parameter[7] 0 Settings of Counter 1 Bits 16 to 24 of
24 Read/write Parameter[8] 0 Reserved
25 Read/write Parameter[9] 0 LSB
Counter 1 comparison value
28 Read/write Parameter[12] 0 MSB
V 1.0 37
5.5.2.8 Examples of COMDRV Application

The next section described some examples of write and read access.
Read access to counter status double word:
The counter status is a double word. For this reason, the access code 160dec "Read Access Double
Word“ is described in the output data Byte 2 (CTRL).
This example accesses the counter status of Counter_0, which is Index 8.
Byte 0 1 2 3 4 5 6 7
Measured Ctrl Index Data3 Data2 Data1 Data0
Ctrl_0 Ctrl_1
value 160dec 8dec 0 0 0 0
If the command is executed successfully, the following reply is sent back in the input data.
In our example, the counter status is 0x12345678
Byte 0 1 2 3 4 5 6 7
Stat_0 Stat_1
value 160dec 8dec 12 34 56 78
In order to execute another command, the previous command must be reset. A zero is then entered in
Byte 2 (CTRL).
Byte 0 1 2 3 4 5 6 7
Ctrl_0 Ctrl_1
value 0 0 0 0 0 0
Write access to comparison value double word:
The comparison value is a double word. For this reason, the access code 224dec "Write Access Double
Word“ is written to the output data Byte 2 (CTRL).
This example accesses the comparison value of Counter_1, which is Index 25, and writes this value with
0x7FFFFFFF.
Byte 0 1 2 3 4 5 6 7
Ctrl_0 Ctrl_1
value 224dec 25dec 7F FF FF FF
In order to execute another command, the previous command must be reset. A zero is then entered in
Byte 2 (CTRL). Each write access is entered with a confirmation in the input data.
Byte 0 1 2 3 4 5 6 7
Ctrl_0 Ctrl_1
value 0 0 0 0 0 0
Read/write access to byte value:
With byte access, the process is the same as for the double word. Only the access codes change
(Write 192, Read 128). Carry out the steps below as described above.
38 V 1.0
5.5.3 Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760
5.5.3.1 Input / Diagnostic Input Function
Table 5-53: Bit assignment, input / diagnostic input function, Art.No. 56 760
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel n/a n/a n/a n/a n/a n/a 11 10 n/a n/a n/a n/a n/a n/a n/a n/a
Table 5-54: Value definition, input / diagnostic input function, Art.No. 56 760
Bit Definition
value
1 Diagnostic input
5.5.3.2 Input NO Contact / NC Contact Function
Table 5-55: Bit assignment, input NO contact / NC contact function, Art.No. 56 760
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel n/a n/a n/a n/a n/a n/a 11 10 n/a n/a n/a n/a n/a n/a 01 00
Table 5-56: Value definition, input NO contact / NC contact function, Art.No. 56 760
Bit Definition
value
0 NO function
1 Break function
5.5.3.3 Input / Output Function
Table 5-57: Bit assignment, input / output function, Art.No. 56 760

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel n/a n/a n/a n/a n/a n/a 11 10 n/a n/a n/a n/a n/a n/a 01 00
Table 5-58: Value definition, input / output function, Art.No. 56 760

Bit Definition
value
1 Output
V 1.0 39
5.5.3.4 Error Action
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- n/a n/a n/a n/a n/a n/a 11 10 n/a n/a n/a n/a n/a n/a 01 00
nel
Table 5-60: Value definition, error action, Art.No. 56 760
Bit Definition
value
1 Output value corresponds to error value (default)
0 Initial value is retained in case of error (last state)
5.5.3.5 Error Value
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Chan- n/a n/a n/a n/a n/a n/a 11 10 n/a n/a n/a n/a n/a n/a 01 00
nel
Table 5-62: Value definition, error value, Art.No. 56 760
Bit Definition
value
40 V 1.0
5.5.3.6 RS485 Operating Mode
Table 5-63: Value definition, RS485 operating mode, Art.No. 56 760
Definition
Possible
settings Reserved
Request (default)
5.5.3.7 RS485 Baud Rate
Table 5-64: Value definition, RS485 operating mode, Art.No. 56 760
Definition
9600 Baud (default)
Possible
settings 2400 Baud
4800 Baud
19200 Baud
5.5.3.8 RS485 Send
Table 5-65: Value definition, RS485 send, Art.No. 56 760
Definition
8 bits, no parity, 1 stop bit
8 bits, even parity, 1 stop bit (default)
Possible
settings 8 bits, odd parity, 1 stop bit
7 bits, no parity, 2 stop bits
7 bits, even parity, 1 stop bit
7 bits, odd parity, 1 stop bit
5.5.3.9 RS485 Echo
Table 5-66: Value definition, RS485 echo, Art.No. 56 760
Definition
Possible
settings No transmit echo in RX buffer
Transmit echo in RX buffer
5.5.3.10 RS485 Handshake
Table 5-67: Value definition, RS485 handshake, Art.No. 56 760
Definition
Possible
settings XOFF (default)
XON
V 1.0 41
5.5.3.11 RS485 XOFF Timeout
Value Definition
0 … 255 Handshake timeout in ms (the earliest that data
can be received again)
5.5.3.12 RS485 Send Delay
Value Definition
0 … 255 Signal delay in ms
(when data can be sent again)
42 V 1.0
5.5.4 Cube67 Logic 4xM12 – Art. No. 56 771
Table 5-70: Settings of logic function
Definition
Disabled
Possible
settings 1x6 AND/NOR
2x3 AND
2x3 XOR
1x6 AND/NOR:
Pin 2 Pin 4 Output

Channel
10 11 12 00 01 02 13 03
1 1 1 1 1 1 1 0
1x6 AND
1x6 NOR 0 0 0 0 0 0 0 1
Any other status 0 0
2x3 AND:
Pin 2 Pin 4 Output

Channel
10 11 12 00 01 02 13 03
1 1 1 x x x 1 x
2x3 AND 6
X X X 1 1 1 x 1
2x3 XOR:
Pin 2 Pin 4 Outputs

Channel
10 11 12 00 01 02 13 03
1 1 1 0 0 0 1 0
2x3 XOR 0 0 0 1 1 1 0 1
6
X = Don’t care.
V 1.0 43
5.5.5 Analog Input Modules
5.5.5.1 Selection of Measuring Range and Filter Art. Nos. 56 700 / 56 701 / 56 730
When you select the input measuring range, you also define the smoothing level for the measuring
signal.The following settings are available:
Table 5-71: Selecting the measuring range Art.Nos. 56 700 / 56 701 / 56 730
Art. No. 56 700 / 56 701 56 730

Channel disabled (default) Channel disabled (default)
+/- 10 V (no smoothing) 0...20 mA (no smoothing)
0 ... 10 V (no smoothing) 4...20 mA (no smoothing)
+/- 10 V (low smoothing) 0...20 mA (low smoothing)
Measuring range 0 ... 10 V (low smoothing) 4...20 mA (low smoothing)
+/- 10 V (moderate smoothing) 0...20 mA (moderate smoothing)
0 ... 10 V (moderate smoothing) 4...20 mA (moderate smoothing)
+/- 10 V (high smoothing) 0...20 mA (high smoothing)
0 ... 10 V (high smoothing) 4...20 mA (high smoothing)
5.5.5.2 Filter Description Art. Nos. 56 700 / 56 701 / 56 730
The analog signal can be prefiltered in the device in order to obtain distinct values even under difficult
EMC conditions. The filter produces a smoothing of the analog signal. The time response of the input
signal in the PLC can be corrupted as a result of smoothing. The calculations below are based on the
filters:
Low smoothing Moderate smoothing High smoothing
5 * x( t −1) + x(t ) 10 * x(t −1) + x(t ) 50 * x( t −1) + x( t )

y= 7
y= y=
6 11 51
Smoothing is achieved by weighting the analog input signals at times (t-1) and (t). The chart below shows
the response of the module to a step response in an active channel.
The measuring time per channel is approx. 2.0 ms. The total program runtime of the firmware is
calculated from the measuring time per channel + 2.5 ms.
7
x – analog input value (raw value at the module); y – analog input value transferred to the PLC
44 V 1.0
Detected step response with filters used and one

active channel
1,1
1
0,9
0,8
0,7
HIGH
0,6
MEDIUM
0,5
LOW
0,4
0,3
0,2
0,1
0
0 250 500 750 1000 1250 1500 1750 2000
Time [ms]
Figure 5-4: Time-dependent response to smoothing in Cube67 AI4 (U) modules
Capture of measured parameters slows down linearly with the number of channels switched to active.
The above chart plots the capture of the step response for one active channel only.
Capture of measured parameters slows down linearly with the number of channels
switched to active.
5.5.5.3 Application of Delta Value Art. Nos. 56 700 / 56 701 / 56 730

The delta value limits the bus load in an event-controlled transmission of measured parameters, e.g.
change of state. Using delta, you can determine by how many increments or decrements the measured
parameter must be changed to send the analog input value, starting with the last measured parameter
sent, or after a voltage reset by the value of the first measured parameter captured.
5.5.5.4 Additional Settings Art. Nos. 56 700 / 56 701 / 56 730
Table 5-72Additional settings Art.Nos. 56 700 / 56 701
Bit position Function Description

0 – Diagnostic ON
0 Switch off channel diagnostic
1 – Diagnostic OFF
0 – Motorola data format
1 Activate byte exchange
1 – Intel data format
0 – Delta value not enabled
2 Activate delta value
1 – Use delta value
3 ... 7 reserved
The settings listed in the table above impact on all channels.
Unused channels should be deactivated to optimize cycle time.
V 1.0 45
5.5.5.5 Filter Description Art. Nos. 56 740 / / 56 748
The 50/60 Hz filter can suppress faults on the lines. The module A/D converter is switched to a special
mode. As a result, the conversion time lengthens to approximately ten times the default time.
When the filter is used, the conversion time is approx. 10 times greater than without a
filter.
5.5.5.6 Module Operating Mode – Global Module Settings Art. Nos. 56 740 / 56 748
Table 5-73: Module operating mode, Art.Nos. 56 740 / 56 748

0 – Motorola data format
0 Activate byte exchange
0 – Celsius
1 Temperature unit setting
1 – Fahrenheit
0 – Filter OFF
2 Activate blocking filter
1 – Filter 50/60 Hz
0 – Diagnostic ON
3 Switch off bus diagnostic
4 ... 7 reserved
Input is bit-by-bit. The module operating mode settings impact on all channels.
5.5.5.7 Selection of Connectivity Art. No. 56 740
Table 5-74: Overview of connectivity, Art.No. 56 740
Channel operating mode

Channel inactive
Possible settings 3-wire technology
2-wire technology
4-wire technology
46 V 1.0
5.5.5.8 Resistance Selection Art. No. 56 740
Table 5-752: Channel operating mode format (2) Art.No. 56 740

Platinum 100 (default)
Platinum 200
Platinum 500
Platinum 1000
Possible settings Nickel 100
Nickel 120
Nickel 200
Nickel 500
Nickel 1000
Resistance
Unused channels should be deactivated to optimize cycle time.
5.5.5.9 Thermocouple Selection Art. No. 56 748
Table 5-76: Thermocouple selection Art.No. 56 748

Channel disabled (default)
Type K
Possible settings Type N
Type J
Type E
Type R
5.5.5.10 Analog Output Modules
5.5.5.11 Selection of Voltage Setpoint Range
Table 5-77: Channel operating mode (1) - Cube67 AO4 C 4xM12 – Art. Nos. 56 710 / 56 720
Art. No. 56 710 56 720

Channel inactive Channel inactive
Measuring range +/10 V 0 ... 20 mA
0 ... 10 V 4 ... 20 mA
V 1.0 47
5.5.5.12 Additional Settings
Table 5-78: Channel operating mode (2) - Cube67 AO4 C 4xM12 – Art. Nos. 56 710 / 56 720

0 0 – Diagnostic ON
Switch off bus diagnostic
1 0 – Motorola data format
Activate byte exchange
2 0 – Error action assumes error value
Generating the error action
1 – Error action retains last state
3 ... 7 reserved
The settings listed in the table above impact on all channels.
5.5.5.13 Use of Error Value
In the Channel Operating Mode (2) parameter, you can determine in the Error Action value how the
output responds in the event of a communication error (DeviceNet or internal system connection).
The error value default setting is zero, so that, in the event of an error, zero is generated at the outputs if
there is no change to the error action value.
Table 5-79: Error value format, Art.No. 56 710
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Definition VZ n/a n/a n/a Highbyte Lowbyte
48 V 1.0
5.5.6 Parameter Access via Explicit Message Service
If you want Explicit Message Service to have access to individual data via your PLC program, you may
find this chapter helpful. If the module is parameterized without an EDS file, you can read and write your
data via the device profile and the Explicit Message Service (see Figure 5-5).
This involves accessing Class 101dec. The Cube67 I/O modules reflect the instances of this class. The
attributes of the instances contain parameterization data or general information on the module.
The input data are contained from attribute 20 to 29, output data from attribute 30 to 39, and parameter
data from attribute 40 to 59. The diagnostic data range starts at attribute 80 and ends at attribute 100.
Attributes 20 to 100 are formatted as word (16 bits).
Attributes 10, 11, 12 and 13 contain the input, output and diagnostic data in different formats as a byte
field.
Figure 5-5: Access via Explicit Message Service
V 1.0 49
The table below shows the manufacturer-specific class 100 for the Cube67 bus node.
Table 5-80: Attributes of Class 100 Instance 1

Attribute Access Name DeviceNet Attribute description Value description
ID data type
Number of I/O
3 Get Byte Sum of all Cube67 I/O boxes 0 ... 16
boxes
Total number of
4 Get UINT Sum total of all I/O channels 0 ... 256
I/O channels
ARRAY OF Overview of the group diagnoses of
5 Get Group diagnoses { 0. 0. 0. ...}
BYTE the Cube67 I/O modules
Bus node
6 Get WORD Undervoltage See Chapter 6.1.1
diagnostic
List of article numbers of the
ARRAY OF
7 Get List of modules Cube67 I/O modules beginning with { 56502. 0. 0. ...}
WORD
the bus node
Bus node Short circuit in actuator / sensor
8 Get Byte See Chapter 6.1.1
diagnostic supply
Manufacturer
10 Get Byte Hardware version 100
Hardware Version
Manufacturer
11 Get Byte Software version 202
software version
Set user
20 Get / Set parameter non- Byte Set user-defined parameterization Write sequence 1hex
volatile
Clear user Delete user-defined
21 Set WORD Write sequence 1hex
parameter parameterization
50 V 1.0
The table below shows the manufacturer-specific Class 101 for the Cube67 I/O modules.
Table 5-81: Attributes of Class 101 of all instances
Attribute Acces Name DeviceNet Attribute description

ID s data type
3 Get Status Byte Communication status in the internal connection
4 Get Name of the Cube67 STRING[5] Internal module name in plaintext (not identical to catalogue
I/O module designation)
5 Get Article number of the WORD Article number
Cube67 I/O module
6 Get Device type of the WORD Device type (input / output)
Cube67 I/O module
7 Get VendorID of the WORD Manufacturer ID
Cube67 I/O module
8 Get Number of I/O WORD Sum of all I/O connections
connections
9 Get Revisionnumber DWORD Revision number HW / SW
10 Get Assembly Input ARRAY OF Input data of the Cube67 I/O module
BYTE
11 Get Assembly Input + ARRAY OF Input data + diagnostic of the Cube67 I/O module
Diagnostic BYTE
12 Get / Set Assembly Output ARRAY OF Output data
BYTE
13 Get Assembly Diagnostic ARRAY OF Diagnostic data
BYTE
14 Get Common Diagnostic WORD Group diagnostic
20 Get Inputword n WORD Value of the inputs (LSB)

21 Get Inputword n+1 WORD ...
... ... ...
29 Get Inputword n+9 Value of the inputs (MSB)
30 Get / Set Outputword n WORD Value of the outputs (LSB)

31 Get / Set Outputword n+1 WORD ...
... ... ...
39 Get / Set Outputword n+9 Value of the outputs (MSB)
40 Get / Set Parameterword n WORD Parameter n

41 Get / Set Parameterword n+1 WORD Parameter n+1
... ...
80 Get Diagnostic n Byte Diagnostic byte 0

81 Get Diagnostic n+1 Byte Diagnostic byte 1
82 Get Diagnostic n+2 WORD Diagnostic word n+2
83 Get Diagnostic n+3 WORD Diagnostic word n+3
... ... ...
100 Get Diagnostic WORD Diagnostic word n+20
V 1.0 51
5.5.7 Saving Parameters to Flash Memory
The parameters are automatically saved to the flash memory in the bus node
depending on the configuration software used.
Before you begin to save data, remove the bus node from the scan list of your PLC,
otherwise an error message is generated. The bus node does not respond to any
requests from the master during a save operation.
5.5.8 Checking the Configuration after a Voltage Reset
If parameters, and therefore the configuration, have been saved to flash memory, the current
configuration is compared with the stored configuration after a voltage reset.
If both configurations are not identical, the default settings of the Cube67 I/O modules in the bus node are
used. The default parameters are polled from the Cube67 I/O modules on startup. Even if the I/O data
length is changed, the I/O data are displayed in the configuration diagnostic from the module in which a
noncompliance was detected.
The configuration diagnostic shows from which module a noncompliance between

saved and currently connected configuration was detected. It is urgently
recommended to evaluate the configuration diagnostic to detect configuration errors.
52 V 1.0
5.5.9 Operating Modes

For I/O data exchange, you have the choice between the following transmission services:
• Poll,
• Change of State (COS), and
• Cyclic
The I/O data is polled using the default parameters defined in the EDS file. There is no
parameterization option via the I/O data.
5.5.9.1 Polling
Poll Command: The I/O message is directed to a single, specific slave device (point-to-point). The
master must send a separate poll command to each "poll" slave that contains the salve output data,
provided the device has outputs.
Poll Response: The "polled" slave returns its input data, provided it supplies input data.
5.5.9.2 Change of State
Change of state: The devices transfer their I/O data after a change of state.
Heartbeat: Used as device monitor in this operating mode. A cyclical poll is sent (e.g. every 250 ms) to
check whether the slave is still connected to the network.
This efficient (for discrete I/O applications) mode of operation can minimize the bus
load.
5.5.9.3 Cyclic
Cyclic Data Transfer: The devices transfer their I/O data with a user-configurable time base (TB).
This operating mode is suitable for highly efficient analog I/O applications.
V 1.0 53
5.6 Mapping of I/O Data
In the device identification, the scanner (DeviceNet bus master) has received all the information it
requires on data width, operating mode, etc. From this information, the scanner generates an adequate
periphery map of all detected slaves in the DeviceNet System. The I/O data is then mapped in a scan list
depending on their physical order.
The user can assign the scan list to logical addresses in the PLC in accordance with the periphery map of
the bus users.
PLC DeviceNet Scanner DeviceNet

Interface module Consumer/Producer
Periphery map "Inputs" Cube67 BN DN Node 1

Input data Node 1
Process map Diagnostic data Node 1 • Input data
of inputs Input data Node 2 • Diagnostic
(PAE) • Output data
Diagnostic data Node 2
Input data Node 3
DeviceNet Bus
Diagnostic data Node 3
Cube67 BN DN Node 2
• Input data
• Diagnostic
PLC program Periphery map "Outputs” • Output data
Output data Node 1
Output data Node 2
DeviceNet Bus
Output data Node 3
Cube67 BN DN Node 3
• Input data
Process map of the • Diagnostic
outputs
• Output data
(PAA)
Fig. 5-1 : Data exchange between PLC, interface module (scanner) and DeviceNet Bus users
54 V 1.0
5.6.1 Input Data

Input data is sent by the bus node as a fragmented I/O message. The bus node supplies 5 bytes of data,
even if no Cube67 I/O modules are connected. The format of this data is described in section 6.1 .
The data format structure can be represented in a simplified manner as follows.
Table 5-82: Sequence of input data of the Cube67 System

Byte 0..n Byte n +1 Byte n+2 Byte n+4
Input data of Cube67 I/O Bus node diagnostic Communication/ Module diagnostic
modules configuration diagnostic
5.6.2 Output Data

The output data of the Cube67 System is arranged in accordance with their physical connection order.
Table 5-83: Sequence of the output data of the Cube67 System

Byte 0..n
Output data of Cube67 I/O modules
V 1.0 55
5.6.3 Overview of I/O Data Lengths of Cube67 Modules
Table 5-84: Overview of I/O data lengths
Article number Input data Output data

56 507 5 n/a8
56 600 2 2
56 601 2 2
56 602 2 n/a
56 603 2 n/a
56 605 2 n/a
56 606 2 n/a
56 610 2 2
56 611 2 2
56 612 2 n/a
56 613 2 n/a
56 616 2 n/a
56 620 1 1
56 621 1 1
56 622 1 n/a
56 623 1 n/a
56 626 1 n/a
56 631 2 2
56 640 2 2
56 650 n/a 2
56 651 n/a 2
56 655 n/a 1
56 656 n/a 4
56 661 1 1
56 662 2 2
56 663 1 1
56 681 2 2
56 691 2 2
56 700 8 n/a
56 701 8 n/a
56 710 n/a 8
56 720 n/a 8
56 730 8 n/a
56 740 8 n/a
56 748 8 n/a
56 750 8 8
56 760 8 8
56 771 1 n/a
8
n/a – no data available
56 V 1.0
5.7 Format of I/O Data
5.7.1 Bus Node
A diagnostic byte for the bus node, a diagnostic word for communication/configuration errors in the
internal system connection and a diagnostic word for module-related errors are sent in addition to input
data.
Table 5-85: Format of bus node input data
Byte 0 Byte 1 / 2 Byte 3 / 4

Bus node diagnostic Communication/configuration diagnostic Module diagnostic
The bus node diagnostic is arranged after the module input data.
For further information, please refer to Chapter 6.1 Diagnostics via DeviceNet Bus.
V 1.0 57
5.7.2 Digital I/O Modules
5.7.2.1 Inputs
Table 5-86: Input word for Cube67 I/O modules with M12 connection and max. 16 inputs9
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Value Input byte, channels 10..17 Input byte, channels 00..07
Channel 17 16 15 14 13 12 11 10 07 06 05 04 03 02 01 00
Table 5-87: Input word for Cube67 I/O modules with M12 connection and max. 8 inputs10
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Value Input byte, channels 10..17 Input byte, channels 00..07
Table 5-88: Input word for Cube67 I/O modules with M8 or valve connection and max. 8 inputs11
Bit 7 6 5 4 3 2 1 0
Value Input byte, channels 00..07
Channel 07 06 05 04 03 02 01 00
Table 5-89: Input word for Cube67 I/O modules with terminal block and max. 16 inputs12
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Value Terminal X1 channels 00..07 Terminal X0 channels 00..07
Channel 07 06 05 04 03 02 01 00 07 06 05 04 03 02 01 00
9
Art. Nos. 56 600,56 605, 56 601, 56 602, 56 603, 56 606, 56 640, 56 662
10
Art. Nos. 56 610, 56 611, 56 612, 56 613, 56 616, , 56 631
11
Art. Nos. 56 620, 56 621, 56 622, 56 623, 56 626, 56 661, 56 663
12
Art. Nos. 56 681,56 691
58 V 1.0
5.7.2.2 Outputs
Table 5-90: Output word for Cube67 I/O modules with M12 connection and max. 16 outputs13
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Value Output byte, channels 10..17 Output byte, channels 00..07
Channel 17 16 15 14 13 12 11 10 07 06 05 04 03 02 01 00
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Table 5-92: Output byte for Cube67 I/O modules with M8 or valve connection and max. 8 outputs15
Bit 7 6 5 4 3 2 1 0
Value Output byte, channels 00..07
Channel 07 06 05 04 03 02 01 00
Table 5-93: Output byte for Cube67 I/O modules with valve connection and max. 16 outputs16
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
Table 5-94: Output byte for Cube67 I/O modules with terminal connection and max. 8 outputs17
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel n/a n/a n/a n/a n/a n/a n/a n/a 07 06 05 04 03 02 01 00
13
Art. Nos. 56 600, 56 601, 56 640, 56 662
14
Art. Nos. 56 610, 56 611, 56 631
15
Art. Nos. 56 620, 56 621, 56 655, 56 661, 56 663
16
Art. Nos. 56 651, 56 650
17
Art. Nos. 56681, 56691
V 1.0 59
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Channel n/a n/a n/a n/a 13 12 11 10 n/a n/a n/a 04 03 02 01 00
Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Channel n/a n/a n/a n/a 13 12 11 10 n/a n/a n/a 04 03 02 01 00
18
Art. No. 56656
60 V 1.0
5.7.3 Function Modules
5.7.3.1 Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760
5.7.3.1.1 Input Data
Table 5-96: Input data for Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760
Byte 0 1 2 3 4 5 6 7
Designation Status_0 Status_1 Status_2 Data 4 Data 3 Data 2 Data 1 Data 0
Input data RS485 status Useful data
Table 5-97: Description of bit assignment, Byte Status_0, Art.No. 56 760
Bit Designation Value Definition

0 Request_Done
1 Request_Done
2 Transmit_Done
3 Delete RX-Buffer_Done
0 to 2 Retval
4 Delete TX-Buffer_Done
5 Reset_Done
6 -
7 -
3 Rx Character in Rx Buffer present for fetching
4 DI 00 Input of channel 00
Table 5-98: Description of bit assignment, Byte Status_1, Art.No. 56 760
Bit Designation Definition

0
The length of Rx data that is transferred in the first Send PDO.
1 DataLengthRx (0 to 5)
Maximum 5 bytes.
2
3
4
Response Number Reply number. Incremented each time a PLC request is
5 (0 to 31) processed.
6
7
V 1.0 61
Table 5-99: Description of bit assignment, Byte Status_2 (communication status), Art.No. 56 760
Bit Designation Definition

0 TX_BUSY Module is sending data
1 - -
2 RX_WARN Rx Buffer 80% full
3 RX_PARITY Parity error on reception
4 - -
5 TX_OVERFLOW Tx Buffer Overflow
6 RX_OVERFLOW Rx Buffer Overflow
No XON to XOFF was received within the parameterized
7 XOFF_TIMEOUT
monitoring time. The transmit process is continued.
62 V 1.0
5.7.3.1.2 Output Data
Table 5-100: Output data for Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760
Byte 0 1 2 3 4 5 6 7
Designation Ctrl_0 Ctrl_1 Ctrl_2 Data 4 Data 3 Data 2 Data 1 Data 0
Output data RS485 status Useful data
Table 5-101: Bit assignment, Byte 0 : Ctrl_0
Bit Designation Value Definition

0 Request
1 Request
2 Transmit
3 Delete RX Buffer
0 to 2 CMD
4 Delete TX Buffer
5 Reset
6 -
7 -
3 - - -
4 DO 00 Output of channel 00
Command Explanation
Request When 0->1 or 1->0, Tx and Rx data are replaced in the buffers.
Transmit All characters in the Tx buffer are sent. Tx buffer is then empty.
Delete RX Buffer Delete Rx buffer.
Delete TX Buffer Delete Tx buffer. Characters are NOT sent.
Reset Reset port, RX and TX buffers are erased
Status Designation Definition

0
DataLengthTx
1 Length of Tx data saved in the module Tx buffer. Maximum 5 bytes.
(0 to 5)
2
3 reserved
4 reserved
5 reserved
6 reserved
7 reserved
Status Definition
0 reserved
… …
… …
… …
7 reserved
V 1.0 63
5.7.3.2 Cube67 CNT2 C 4xM12 – Art. No. 56 750
A protocol inserted in module CNT2 C 4xM12 – Art.No. 56750 allows data to be read or written from the
module in cyclical data exchange and to execute services.
- Read SW Version.
- Alternative access to counter status for comparison value and parameter.
- Edit parameter.
Please refer to our web site to find out whether there is a software library for your
controller.
Table 5-104: Input bytes for Cube67 CNT2 C 4xM12 – Art. No. 56 750
Byte 0 1 2 3 4 5 6 7
CD32I CD32I CD32I CD32I CD32I CD32I
Designation Stat_0 Stat_1
Index Status Data0 Data1 Data2 Data3
Input data Counter status COMDRV
The meaning of the input data bytes 2 to 7 is described in Sec. 5.5.2.7 COMDRV - SAP
0.
Table 5-105: Bit assignment, Byte Stat_0 / Stat_1
Byte Designation Definition

0 Status_0/1 Comparison value of Counter 0/1 reached/not reached
1 GATE_0/1 Counter 0/1 input status
2 UPDOWN_0/1 Counter 0/1 counter advance sense status
3 DO_0/1 Status of output DO_0/1
4 - -
5 - -
6 - -
7 - -
64 V 1.0
5.7.3.2.2 Output Data
Table 5-106: Output data for Cube67 CNT2 C 4xM12 – Art. No. 56 750
Byte 0 1 2 3 4 5 6 7
CD32O CD32O CD32O CD32O CD32O CD32O
Designation Ctrl_0 Ctrl_1
Ctrl Index Data3 Data2 Data1 Data0
Table 5-107: Bit assignment Byte Ctrl_0 / Ctrl_1
Bit Name Definition

Switch counter to active
0 Gate 0/1
Gate 0/1 set, counter can start to count
1 RESET_0/1 Reset Counter 0/1 to start value (0000hex)
2 DO_0/1 Output 0/1 should be switched off or reset if 1
3 Up/Down_0/1 0 – process-controlled, 1- sense down PLC controlled
4…7 - Reserved
Access and the meaning of the output data bytes 2 to 7 is described in Sec. 5.5.2.7
COMDRV - SAP 0.
Table 5-108: Response of gate signal
Control of output data with gate signal

Controller Process Description
0 0 Counter disabled
1 0 Counter enabled
1 1 Counter enabled
0 1 Counter enabled
Table 5-109: Response of up/down signal
Control of output data with up/down signal

Controller Process Description
0 0 Counter advance sense up
1 0 Counter advance sense down
The counters and the associated outputs operate independently of each other.
After the comparison value is reached, the counter and the associated output must be
reset together. If only the counter is reset, the associated output would retain its
status.
V 1.0 65
5.7.4 Cube67 Logic 4xM12 – Art. No. 56 771
Table 5-110: Input byte for Cube67 Logic module with M12 connection
Bit 7 6 5 4 3 2 1 0
Input of Input of Input of Input of Input of Input of
Value Output S4 Output S2 socket 2 socket 2 socket 1 socket 1 socket 0 socket 0
Pin 4 Pin 2 Pin 4 Pin 2 Pin 4 Pin 2
Byte 0
66 V 1.0
5.7.5 Analog I/O Modules
5.7.5.1 Inputs
Table 5-111: Input data format for AI4 (U) / (I) / RTD /TH, Motorola format
Byte 7 6 5 4 3 2 1 0
Channel 03 02 01 00
Detail representation using example of
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Format VZ HIGHBYTE LOWBYTE
Table 5-112: Input data format for AI4 (U) / (I) / RTD /TH, Intel format
Byte 7 6 5 4 3 2 1 0
Channel 03 02 01 00
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Format LOWBYTE VZ HIGHBYTE
5.7.5.2 Outputs
Table 5-113: Output data format for AO4 (U) / (I) Motorola format
Byte 7 6 5 4 3 2 1 0
Channel 03 02 01 00
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Format VZ n/a n/a n/a n/a HIGHBYTE LOWBYTE
Table 5-114: Output data format for AO4 (U) / (I) Intel format
Byte 7 6 5 4 3 2 1 0
Channel 03 02 01 00
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Format LOWBYTE VZ n/a n/a n/a n/a HIGHBYTE
Data representation is in two's complement.
V 1.0 67
5.7.5.3 Analog Value Representation
5.7.5.3.1 Art. Nos. 56 700 / 56 730
Table 5-115: Representation of the analog values of input modules, Art. Nos. 56 700 / 56 701 / 56 730
Measuring Range Measured value Range Diagnostic
0...10 V 0...20 mA Decimal Hexadecimal Binary
Overmodulati
>10 >20 32767 7FFF 0111 1111 1111 1111 Yes
on
10 20 32767 7FFF 0111 1111 1111 1111
Nominal
5 10 16383 3FFF 0011 1111 1111 1111 range
0 0 0 0 0000 0000 0000 0000
Undermodula-
<0 <0 0 0 0000 0000 0000 0000 No
tion
4...20 mA
>20 32767 7FFF 0111 1111 1111 1111 Overmodula- Yes
tion
20 32767 7FFF 0111 1111 1111 1111
Nominal
10 16383 3FFF 0011 1111 1111 1111 range
4 0 0 0000 0000 0000 0000
<4 0 0 0000 0000 0000 0000 Undermodula- Yes
tion
<2 0 0 0000 0000 0000 0000 Line break Yes
-10...+10 V
> +10 32767 7FFF 0111 1111 1111 1111 Overmodula- Yes
tion
10 32767 7FFF 0111 1111 1111 1111
5 16383 3FFF 0011 1111 1111 1111
Nominal
0 0 0 0000 0000 0000 0000 range
-5 49153 C001 1100 0000 0000 0001
-10 32768 8000 1000 0000 0000 0000
< -10 32768 8000 1000 0000 0000 0000 Undermodula- Yes
tion
68 V 1.0
5.7.5.3.2 Art. Nos. 56 710 / 56 720
Table 5-116: Representation of analog values of output modules, Art. Nos. 56 710 / 56 720
Measuring Range Measured value
0...10 V 0...20 mA Decimal Hexadecimal Binary
10 20 2047 7FF 0xxx x111 1111 1111
5 10 1023 3FF 0xxx x111 1111 1111
0 0 0 0 0xxx x000 0000 0000
4...20 mA
20 2047 7FF 0xxx x111 1111 1111
10 768 300 0xxx x011 1111 1111
4 0 0 0xxx x000 0000 0000
-10...+10 V
10 2047 7FF 0xxx x111 1111 1111
5 1023 3FF 0xxx x011 1111 1111
0 0 0 0xxx x000 0000 0000
-5 33793 8401 1xxx x010 0000 0001
-10 32768 8000 1xxx x000 0000 0000
The bit positions marked by "X" are ignored by the device and have no impact on the
specified value. The sign is always evaluated. In operating modes 0...10 V, 0...20 mA
and 4...20 mA, the sign should always be zero (0).
V 1.0 69
5.7.5.3.3 Art. No. 56 740 RTD
Table 5-117: Representation of analog values of input module, Art. No. 56 740
Measuring Range Measured value Range Diagnos-
Platinum Decimal Hexadecimal Binary tic
100,200,500,1000
> 1800°C 32767 7FFF 0111 1111 1111 1111 Line break Yes
850°C < T < 1800°C >8500 >2134 0010 0001 0011 0100 Overmodulation Yes
850°C 8500 2134 0010 0001 0011 0100
0°C 0 0 0000 0000 0000 0000 Nominal range
-200°C -2000 F830 1111 1000 0011 0000
< -200°C <-2000 <F830 1111 1000 0011 0000 Undermodulation Yes
Ni Decimal Hexadecimal Binary
100,120,200,500,1000
250°C < T < 1800°C >2500 >9C4 0000 1001 1100 0100 Overmodulation Yes
250°C 2500 9C4 0000 1001 1100 0100
0°C 0 0 0000 0000 0000 0000 Nominal range
-60°C -600 FDA8 1111 1101 1010 1000
< -60°C <-600 <FDA8 1111 1101 1010 1000 Undermodulation Yes
Platinum Decimal Hexadecimal Binary
100,200,500,1000
> 3272°F 32767 7FFF 0111 1111 1111 1111 Line break Yes
1562°F < T < 3272°F 15620 3D04 0011 1101 0000 0100 Overmodulation Yes
1562°F 15620 3D04 0011 1101 0000 0100
0°F 0 0 0000 0000 0000 0000 Nominal range
-328°F -3280 F330 1111 0011 0011 0000
< -328°F <-3280 <F330 1111 0011 0011 0000 Undermodulation Yes
Ni Decimal Hexadecimal Binary
100,120,200,500,1000
> 3272°F 32767 7FFF 0111 1111 1111 1111 Line break Yes
482°F < T < 3272°F 4820 >12D4 0001 0010 1101 0100 Overmodulation Yes
482°F 4820 12D4 0001 0010 1101 0100
0°F 0 0 0000 0000 0000 0000 Nominal range
-76°F -760 FD08 1111 1101 0000 1000
< -76°F <-760 <FD08 1111 1101 0000 1000 Undermodulation Yes
Resistance 0...3000 Decimal Hexadecimal Binary
> 3251.2 ohms 32767 7FFF 0111 1111 1111 1111 Line break Yes
3000 < R < 3251.2 30000 7530 0111 0101 0011 0000 Overmodulation Yes
3000 ohms 30000 7530 0111 0101 0011 0000
2073.6 ohms 20736 5100 0101 0001 0000 0000 Nominal range
0 ohm 0 0 0000 0000 0000 0000
< 0 ohm <0 <0 0000 0000 0000 0000 Undermodulation Yes
70 V 1.0
5.7.5.3.4 Art. No. 56 748 TH
Table 5-118: Representation of analog values of input module, Art. No. 56 748
Measuring range Measured value Range Diagnostic

Type K Decimal Hexadecimal Binary
1372<T<2000 >13720 >3598 0011 0101 1001 1000 Overmodulation Yes
1372 13720 3598 0011 0101 1001 1000
0 0 0 0000 0000 0000 0000 Nominal range
-200 -2000 F830 1111 1000 0011 0000
<-200 <-2000 <F830 1111 1000 0011 0000 Underflow Yes
>3272°F 32767 7FFF 0111 1111 1111 1111 Line break Yes
2473 24728 6098 0110 0000 1001 1000
0 0 0 0000 0000 0000 0000 Nominal range
-328 -3280 F330 1111 0011 0011 0000
<-328 <-3280 <F330 1111 0011 0011 0000 Underflow Yes
Type N Decimal Hexadecimal Binary

1300<T<2000 >13000 >32C8 0011 0010 1100 1000 Overmodulation Yes
1300 13000 35C8 0011 0010 1100 1000
0 0 0 0000 0000 0000 0000 Nominal range
-200 -2000 F830 1111 1000 0011 0000
<-200 <-2000 <F830 1111 1000 0011 0000 Underflow Yes
2343<T<2473 >23432 >5B88 0101 1011 1000 1000 Overmodulation Yes
2343 23432 5B88 0101 1011 1000 1000
0 0 0 0000 0000 0000 0000 Nominal range
-328 -3280 F330 1111 0011 0011 0000
<-328 <-3280 <F330 1111 0011 0011 0000 Underflow Yes
Type J Decimal Hexadecimal Binary

1200<T<2000 >12000 >2EE0 0010 1110 1110 0000 Overmodulation Yes
1200 12000 2EE0 0010 1110 1110 0000
0 0 0 0000 0000 0000 0000 Nominal range
-200 -2000 F830 1111 1000 0011 0000
<-200 <-2000 <F830 1111 1000 0011 0000 Underflow Yes
2163 21632 5480 0101 0100 1000 0000
0 0 0 0000 0000 0000 0000 Nominal range
-328 -3280 F330 1111 0011 0011 0000
<-328 <-3280 <F330 1111 0011 0011 0000 Underflow Yes
V 1.0 71
Measuring range Measured value Range Diagnostic

Type E Decimal Hexadecimal Binary
1000 10000 2710 0010 0111 0001 0000
0 0 0 0000 0000 0000 0000 Nominal range
-200 -2000 F830 1111 1000 0011 0000
<-200 <-2000 <F830 1111 1000 0011 0000 Underflow Yes
1803 24728 6098 0100 0110 0111 0000
0 0 0 0000 0000 0000 0000 Nominal range
-328 -3280 F330 1111 0011 0011 0000
<-328 <-3280 <F330 1111 0011 0011 0000 Underflow Yes
Type R Decimal Hexadecimal Binary

250 17680 4510 0100 0101 0001 0000
0 0 0 0000 0000 0000 0000 Nominal range
-50 -500 FDB2 1111 1101 1011 0010
<-50 <-500 <FD B2 1111 1101 1011 0010 Underflow Yes
3214<T<3272 >32140 >7D8C 0111 1101 1000 1100 Overmodulation Yes
3214 32140 7D8C 0111 1101 1000 1100
0 0 0 0000 0000 0000 0000 Nominal range
-93 -932 FC5C 1111 1100 0101 1100
<-93 <-932 <FC5C 1111 1100 0101 1100 Underflow Yes
72 V 1.0
5.8 Step by Step: Startup Example
5.8.1 Mechanical Configuration
5.8.1.1 Assembling the Bus Node Hood
1
2
Figure 5-6: Assembly of the bus node hood
Fastening screws NA node addressing switch

Hood DR baud rate switch
FE connection Base module
Step by step :
1 Set the DeviceNet address using the two rotary switches in the base module .
2 Set the baud rate via the rotary switch .
3 Connect the FE wire to the base of the hood .
4 Mount the hood on the base module. Take care not to tilt the hood.
The hood is fastened by three captive screws integrated in the hood. Tighten these screws.
IP67 protection is only guaranteed when the hood is screwed to the base module and
all sockets are plugged with wires or blank plugs.
V 1.0 73
5.8.1.2 Connecting System Components
Figure 5-7: Connecting system components

Bus node base module DeviceNet terminating resistor
Bus node hood Power supply line
Cube67 DIO8 C 4xM12 M12 cable to sensor or actuator
Internal system connection Controller
Incoming DeviceNet bus cable Power supply unit
Step by step :
1 Connect the module to the bus node using the green system cable.
2 Connect the M12 lines routed to the sensors or actuators to the module .
3 Connect incoming DeviceNet bus cable to the bus in terminal of the bus node hood .
4 Connect the outgoing DeviceNet bus cable to the next DeviceNet user or, if the bus node is the last
user, connect a terminating resistor .
5 Connect the power supply via a 7/8" connector.
74 V 1.0
5.8.2 Configuration with RSNetWorx Version 4.XX or Higher
Before putting the equipment into operation, please read the operating instructions of
all devices used and their software.
CAUTION:
These instructions show, by way of example, the startup procedure using the above-
mentioned hardware and software.
1 Download the latest EDS files from www.murrelektronik.com. If you have no internet access,
please contact our Technical Support.
2 Connect one or several devices to the DeviceNet bus. Make sure that the DeviceNet network is
installed correctly.
During baud rate assignment, it must be ensured that the same baud rate is assigned
to each DeviceNet user.
During address assignment, it must be ensured that an explicit and unique address is
assigned to each DeviceNet user in the network.
3 Check that all power supplies are correctly wired up. Then switch on all power supplies for the bus
users.
4 The scanner (voltage must be applied to scanner and PLC) carries out a self-test and shows the
status messages in the display (the display reads: "80"). When the scanner is run up, "00" and "75"
begin to flash alternately in the display. The scanner status is additionally displayed by 2 LEDs on
the scanner. These two LEDs indicate DeviceNet bus status and scanner module status. If no user
is connected to the bus except the scanner, the net indicator flashes green. If there are users on
the bus, the status LEDs are green and the messages "00" and "76" flash alternately in the display.
5 The Cube67 BN-DN modules now indicate their status via the LEDs on the bus module (MS =
green and NS = green flashing).
6 Connect the KFD box19 to the DeviceNet network and the PC. Start the software tool RSNetWorx.
Install the latest version of the EDS files in RSNetworx. A separate EDS file is required in the
Cube67 System for the bus nodes and for each Cube67 I/O modules.
7 Click on the "Online" button in the RSNetWorx toolbar and confirm a number of confirmation boxes.
The program scans the network via the KFD box (you may have to previously confirm that
scanning is to take place via the KFD box).
19
The KFD box is an interface module made by Allen-Bradley for DeviceNet. This device permits access
to the DeviceNet bus and its devices via the RSNetworx software.
V 1.0 75
8 When all users have been scanned, click on the bus node symbol in RSNetWorx. Check the
configuration of the bus node and parameterize the Cube67 system. Download the complete
configuration. Then save the configuration in the bus node. To do this, set the "Save Parameter" to
"1".
During the save process, the bus node may not be in the middle of a data exchange
with the PLC. For this reason, remove the bus node from the scan list before saving.
9 Go to the scanner symbol in RSNetWorx. Check whether the I/O data lengths are entered correctly
in the scan list of the scanner. Select an operating mode for the bus node or acknowledge the
default operating mode, Poll.
Click on the Scan List tab and confirm by clicking on "Download". Click on ">>" in the window that
opens. Confirm by clicking "Accept" and confirm the download. Now all the Cube67 BN-DN are
included in the scanner scan list. The scanner sets up an I/O connection to the modules. The NS-
LED on the Cube67 BN-DN is green. Then you can access the data of the individual Cube67 BN-
DN from the PLC in accordance with the scan list generated.
76 V 1.0
6 Diagnostics
6.1 Diagnostics via DeviceNet Bus
6.1.1 Bus Node Diagnostic Format
Table 6-1: Format of bus node input data
Byte 0 1/2 3/4

Communication/configuration
Designation Bus node diagnostic Module diagnostic
diagnostic
The bus node diagnostic is only available in the I/O data. If the connected module configuration does not
match the saved configuration, the bus node started the bus node using the last I/O data length saved.
This ensures that the I/O data remains available in the controller even if the configuration has been
changed but not saved.
The bus node diagnostic is only available in the I/O data.
We advise you to evaluate the diagnostic bytes to detect configuration and module
errors.
V 1.0 77
6.1.1.1 Bus Node Diagnostic Format, Byte 0
Bit 07 06 05 04 03 02 01 00
Under- No Under-
Designation Reserved Reserved Reserved Reserved Reserved voltage voltage voltage
UA UA US
The bit for each voltage US or UA (power input at 7/8“ power plug) is set when at least one of the
following conditions is fulfilled:
Undervoltage
No voltage
Additional detailed information on the voltage states US and UA is available in the

Explicit Message Service (Class 100 Instance 1 Attributes 6 and 8).
Table 6-2: Bus node diagnostic, Class 100 Instance 1
Attribute Access Designation DeviceNet Attribute description

ID data type
Bus node
6 Get WORD Undervoltage
diagnostic
Bus node Short circuit in actuator / sensor
8 Get Byte
diagnostic supply
Table 6-3: Bus node diagnostic, Class 100 Instance 1 Attribute 6

No voltage Undervoltage
Slot 3 Slot 2 Slot 1 Slot 0 Slot 3 Slot 2 Slot 1 Slot 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
UA US UA US UA US UA US UA US UA US UA US UA US
Table 6-4: Bus node diagnostic, Class 100 Instance 1 Attribute 8

Short circuit
Slot 3 Slot 2 Slot 1 Slot 0
Bit 7 6 5 4 3 2 1 0
Designation UA US UA US UA US UA US
US - Sensor power supply

UA – Actuator power supply
78 V 1.0
6.1.1.2 Communication/Configuration Diagnostic, Byte 1/2
Table 6-5: Communication/configuration diagnostic word
Bit 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
Module No. 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
The diagnostic is set when the saved (reference) configuration does not match the current (actual)
configuration, or one or more modules have failed in the prevailing mode.
6.1.1.3 Module Diagnostic, Byte 3/4
Table 6-6: Module diagnostic word
Bit 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
Module No. 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
The bit for each module is set when a diagnostic is sent to a module. It is cancelled when the diagnostic
is no longer present. The diagnostic can be evaluated by a function block in the PLC program. The
Explicit Message Service is used for this. A group diagnostic is entered for each module in Class 101,
Instance (=Module No.) Attribute 14 of the bus node.
Explizit Message Dienst

(Get Attribute Single)
PLC FB Diagnostic
buffer
16-bit
I/O data Module diagnostic word
Bus node
Object directory
Class 101
I/O data Diagnostic data Instance (Modulno.),
Attribut 14
Figure 6-1: Evaluation of 16-bit group diagnostic of Cube67 I/O modules
The diagnostic of the I/O modules is sent with a time delay, tDiag is approx. 50 ms long.
V 1.0 79
6.1.2 Group Diagnostic Format
Table 6-7: Group diagnostic format, (Class 101, Instance (Module No.) Attribute 14)
Bit Definition Art. Nos. 56 600, 56 601, 56 605, Art. Nos. 56 651, 56 655, Art. Nos. 56 700, 56 701, 56 710,
56 640, 56 602, 56 603, 56 606, 56 656, 56 662, 56 66500 56 720, 56 730, 56 740, 56 748
56 612, 56 613, 56 616, 56 610,
56 611, 56 631, 56 650, 56 771,
56 620, 56 621, 56 661, 56 663,
56 681, 56 691, 56 622, 56 623,
56 626, 56 750, 56 760
0 Undervoltage sensor supply Undervoltage sensor supply Undervoltage sensor supply Undervoltage sensor supply
Undervoltage actuator supply infeed bus Undervoltage actuator supply infeed bus
1 Undervoltage actuator supply infeed bus node Undervoltage actuator supply infeed bus node
node node
Undervoltage actuator supply infeed Undervollage actuator power supply infeed
2 reserved reserved
external external (only 56 600 / 56 640)
Failure actuator power supply infeed bus
3 reserved reserved Failure actuator power supply infeed bus node
node
4 Sensor power supply short-circuit at socket Sensor power supply short-circuit at socket reserved Sensor power supply short-circuit at socket
5 Actuator disable, channels 00..07 Actuator disable, channels 00..07 Actuator disable, channels 00..07 Output short-circuit
6 Actuator disable, channels 10..17 Actuator disable, channels 10..17 Actuator disable, channels 08..15 reserved
7 Actuator disable, channels 16..23 reserved Actuator disable, channels 16..23 reserved
8 Actuator disable, channels 24..31 reserved Actuator disable, channels 24..31 reserved
9 Actuator warning, channels 00..07 Actuator warning, channels 00..07 reserved reserved
10 Actuator warning, channels 10..17 Actuator warning, channels 10..17 reserved reserved
11 Line break reserved Line break Line break
12 Selected measuring range undershot reserved reserved Selected measuring range undershot
13 Selected measuring range exceeded reserved reserved Selected measuring range exceeded
only 56600, 56601, 56602, 56603, 56610,
14 DESINA diagnostic reserved reserved
56611, 56612, 56613
15 reserved reserved reserved reserved
80 V 1.0
6.2 Displays on Bus Node
6.2.1 Displays for DeviceNet Status
Table 6-8: Description of the DeviceNet displays
LED Designation LED Display Response Definition
MS OFF Self-test not completed
MS Green Self-test completed

DupMac Check not completed, no other bus
NS OFF
users on the DeviceNet network
DupMac Check completed, no connection to
NS Green flashing
master
Connection to master (explicit and / or I/O
NS green
connection)
Connection to master lost (timeout, bus
NS Red flashing
disconnected)
Bus disconnected, general physical bus error
NS Red
(voltage reset required)
Cube67 BN-DN
Art.-No. 56502
MS
NS
Figure 6-2: Position of DeviceNet displays on bus node
V 1.0 81
6.2.2 Displays of the Internal System Connection
Bus
In Out
MS
NS
US UA 0 US UA
US UA 2
UA
Figure 6-3: Position of US and UA displays on the bus node
Table 6-9: Status of system communication at bus node
LED Designation LED Display20 Response Definition
US ON Data exchange
US Flashing No data exchange21
US OFF No communication22
Table 6-10: Status of sensor and system power supply at bus node
US Green OK (> 18 V)
Undervoltage or short circuit of sensor

US Red
supply
US OFF Not available or sensor supply < 12.5 V
20
The display colour indicates the voltage state.
21
Communication is interrupted in at least one line.
22
No module is connected or the sensor power supply is switched off.
82 V 1.0
Table 6-11: Status of actuator power supply at bus node
UA Green OK (> 18 V)
Undervoltage or short circuit of actuator

UA Red
power supply
Not available or actuator power supply

UA OFF
<12.5 V
6.2.3 Bus Node Response to Defective Supply Voltages
6.2.3.1 Internal System Connection: Sensor Power Supply Short-Circuit
A short circuit is detected at the socket or in the cable of the system connection. The sensor power
supply, and therefore the module supply for this line, are switched off. The system then signals a
communication error. After the short circuit has been rectified, the internal system connection can be
restarted by resetting the sensor supply or the bus node electronics supply (supply voltage via
DeviceNet). If a power supply unit is selected with too low a rating, the power supply unit shuts off before
the short-circuit is detected in the bus node, thus triggering a reset in the bus node. The US LED on the
bus node on the corresponding line lights up red in the event of a short-circuit.
6.2.3.2 Internal System Connection: Short-Circuit of Actuator Power Supply
A short-circuit is detected at the socket or in the cable of the system connection. The actuator power
supply for this line is switched off. After the short circuit has been eliminated, the fault can be cleared via
a resetting the actuator supply voltage. The UA LED on the bus node on the corresponding line lights up
red.
6.2.3.3 Internal System Connection: Undervollage of Sensor Power Supply
Undervoltage is detected below approx. 17.0 V. The US LEDs of the affected lines are red. If the voltage
drops below approx. 12.5 V, the bus node disconnects from the DeviceNet bus and carries out a self-test.
The bus node does not reconnect to the DeviceNet bus until the sensor power supply is above approx.
13.0 V.
Self-test state can be recognized by green-red flashing US and UA LEDs.
If the sensor power supply drops below approx. 12.5 V, the bus node disconnects
from the DeviceNet bus and carries out a self-test. Self-test state can be recognized
by green-red flashing US and UA LEDs.
V 1.0 83
6.2.3.4 Internal System Connection: Undervoltage of Actuator Power Supply
Undervoltage is detected below approx. 17.0 V. The UA LEDs of the affected lines are red. From a
voltage below approx. 12.5 V, the actuator power supply switches off at the 6-pin M12 socket of the bus
node. The UA LED also goes out.
The output drivers of the Cube67 I/O modules automatically switch off when the
actuator supply voltage drops below 12.5 V. The output drives automatically
reconnect at approx. 13 V.
6.2.4 Other Fault States
6.2.4.1 Open Internal System Connection
When the internal system connection (communication line or sensor power supply from bus node to
individual Cube67 I/O module) is interrupted, the entire system goes to error condition. It is no longer
possible to read or write input data or output data, respectively. The last values of the inputs and outputs
are frozen. The outputs take on the error value programmed via the parameter data. The bus node
diagnostic indicates the internal status of the system connection (see also Chapter 6.1.1. Bus Node
Diagnostic Format).
6.2.4.2 Open Field Bus Connection or I/O Connection Timeout
After a timeout, the input and output data can be read and / or written from the bus node with an Explicit
Message Connection.
The following DeviceNet fault states are detected:

(1) Two or more modules with the same MAC ID on the network
(2) Module has detected CAN in BusOff state.
(3) The timeout for an I/O connection between the module and master was tripped (master did not
disable the timeout for this connection or no master request was issued within the set time period).
(4) A CAN controller message buffer could not be read between two messages with identical identifiers.
(5) Overflow of the internal software receive buffer for messages (DN CAN).
(6) Overflow of the internal software send buffer for messages (DN CAN).
(7) A poll message or COS/CYCL message could not be sent (various causes on the CAN bus).
84 V 1.0
6.3 Displays of the Digital I/O Modules
6.3.1 LED Displays of the Digital I/O Modules
6.3.1.1 Bus IN LED Display
US UA
Figure 6-4: Position of US and UA displays using Art. No. 56 600 as an example
Table 6-12: Status of system communication
LED Designation LED Display23 Response Definition
US ON Data exchange
US Flashing No data exchange24
US OFF No communication25
Table 6-13: Status of sensor and system power supply (bus in display)
US Green OK (> 18 V)
US Red Undervoltage
US OFF Not available (< 12 V)
23
The display colour indicates the voltage state.
24
Communication is interrupted in at least on line.
25
The module has no sensor power supply.
V 1.0 85
Table 6-14: Status of internal actuator power supply (bus in display)
UA Red Undervoltage
UA OFF Not available (< 12 V)
6.3.1.2 External Power – LED Display (Art. Nos. 56 600, 56 640)
Table 6-15: Status of external power display (Art. Nos. 56 600, 56 640)
UA Red Undervoltage
UA OFF Not available (< 12 V)
6.3.1.3 M12 Sockets – LED Diagnostic Display
Table 6-16: M12 sockets – LED diagnostic display
Voltage at Voltage at
Diagnostic at channels Diagnostic at channels
LED Display26 channels channels
00..07 10..17
00..07 10..17
0V 0V - External fault
0V 0V - Sensor short-circuit at Pin 1
0V 0V - Actuator disable
0V 24 V - Actuator warning
- 0V - -
0V 0V Sensor short-circuit at Pin 1 -
0V 0V Actuator disable -
24 V 0V Actuator warning -
26
All diagnostic displays are in red.
86 V 1.0
6.3.2 Relationship between Signal-Logic Image and LED Response
Each input and output is assigned to a separate status display. The LED is labelled '00…07’ or '10…17’.
It is located directly next to the associated M12 socket and allows simple assignment to the status of
peripheral components such as sensors and actuators.
Table 6-17: Relationship between signal-logic image and LED response input
Voltage at Input Logic Value LED Display27
Input with NO 0V 0 OFF

Function
24 V 1 Yellow
0V 1 OFF
Input with NC Function
24 V 0 Yellow
0V 1 Red
Diagnostic Input
24 V 0 OFF
Table 6-18: Relationship between signal-logic image and LED response output
Logic Value Voltage at Output LED Display
0 0V OFF
Output
1 24 V Yellow
27
If a channel-related diagnostic is available, the LED assigned to this channel is continuously lit red.
V 1.0 87
6.4 Displays of Analog I/O Modules
6.4.1 Bus IN LED Display
The function of the Bus IN LED display is identical to the digital modules and is described in section
6.3.1.1 Bus IN LED Display.
6.4.1.1 M12 Sockets – LED Diagnostic Display
Table 6-19: M12 socket – LED diagnostic display AI4 (U) / (I)
LED Display Measured parameter at input Diagnostic in Channel

- Sensor short-circuit
Greater than the parameterized
Measuring range exceeded
measuring range
red
Smaller than the parameterized
Measuring range undershot28
measuring range
<2 mA Line break (only Art. No. 56 730)
Table 6-20: M12 socket – LED diagnostic display AO4 (U) / (I)
LED Display Setpoint at Output Diagnostic in Channel
- Sensor short-circuit
Red 0V Short-circuit (only Art. No. 56 710)
> 2 mA (line open) Line break (only Art. No. 56 720)
Table 6-21: M12 sockets – LED diagnostic display AI4 RTD

> 1800°C Line break
Measuring range exceeded
red measuring range
Measuring range undershot
measuring range
0x7FFF Line break
28
Only in operating modes –10 V...+10 V, or 4 mA...20 mA
88 V 1.0
Table 6-22: M12 sockets – LED diagnostic display AI4 TH

> 2000°C
no KTY Line break
no line connected
Red Measuring range exceeded
measuring range
Measuring range undershot
measuring range
0x7FFF Line break
V 1.0 89
6.5 Displays on Power Distributor
Table 6-23: 6-pin M12 sockets – LED display
LED Display Voltage at Output Definition
OFF 0V No power supply connected
Green Present Power supply connected
Red 0V Short-circuit at output
The power distributor does not carry out undervoltage detection. Undervoltage diagnostics are carried out
in the module to which the voltage coming from the distributor is applied.
Figure 6-5: Position displays on power distributor
90 V 1.0
6.6 Displays on Valve DO16/DO8/DO32 and Cable DIO8 / M16
In
US UA
US UA
In
In
US UA
Out
Diag
Diag
Diag
++49(0)719147-0
Cube67
DO16 E Valve
++49(0)719147-0 Art.-No. 56651
Cube67
DO16 E Valve
Art.-No. 56651
Figure 6-6: Position of displays on valve controller
6.6.1 Bus IN LED Display
The function of the Bus IN LED display is identical to the digital modules and is described in section
6.3.1.1 Bus IN LED Display.
6.6.2 DIAG LED Display
Table 6-24: DIAG LED display
LED Display Diagnostic
OFF No diagnostic
Red Short-circuit at min. one output
Red Wire break in sense line (only valve)
Red Sensor short-circuit (only cable / M16)
V 1.0 91
6.6.3 Displays on Valve DO16 C K3
In
US UA
US UA
In
In
US UA
Out
Diag
Diag
Diag
++49(0)719147-0
Cube67
DO16 E Valve
++49(0)719147-0 Art.-No. 56651
Cube67
DO16 E Valve
Art.-No. 56651
Table 6-25: Status of system communication on Valve DO16 C K3
US Green ok (> 18 V) and Data exchange
Undervoltage or short circuit of

US Red
sensor supply
Flashing:
US No data exchange
red or green
or
US OFF No communication
92 V 1.0
Table 6-26: Status of internal actuator power supply on Valve DO16 C K3
UA Green all 4 Actuator Power Supply > 18 V
Undervoltage of actuator power

UA Red
supply
Not available or sensor supply <

UA OFF
12.5 V
Table 6-27: LED diagnostic display Valve DO16 C K3
LED Display Diagnostic
OFF No diagnostic
Red
Short-circuit at min. one output
Red
Actuator warning at min. one output
V 1.0 93
7 Extended Functions in I/O Modules
You will find examples and function modules of extended functions on our website:
www.murrelektronik.de
www.cube67.com.
CAUTION:
These extended functions are only supported with effect from SW Version 2.04 (or
Major Version 2, Minor Version 5) of the bus nodes.
7.1 General
In some I/O modules, Services Access Points (SAPs) are available for extended functions. These
services are assigned to data and a command set. Each service is identified by a number referred to here
as SAP (Service Access Point).
Communication between application and service takes place using a protocol embedded in the I/O data
section. Access to the SAP contents is by means of an access command (CRTL) and by specifying the
associated index. A description of each of the SAPs deployed, the commands and the indices are in the
respective sections containing module information.
7.2 SAP Format

Each SAP consists of an administration section that is identical for all SAPs (SAP INFO) and an individual
part (SAP USER). The administration section is always assigned to Indices 0 to 5. Indices 6 to 255 are
available for SAP-specific data. Note that the SAPs do not normally use all the index space. The
maximum permitted index for read/write access is saved in the administration section of the SAP in
Indices 2 and 3, respectively.
SAP Info
Index/Byte Access Designation Description
0 Write CTRL_SAP Control SAP
1 Read only INFO_SAP Status SAP
2 Read only MAX_WR_ADR Highest permissible index for write access
3 Read only MAX_RD_ADR Highest permissible index for read access
4 Write - reserved
5 Write - reserved
6
.
. Individual area for specific SAP data
.
255
94 V 1.0
8 List of Figures
Figure 3-1: DeviceNet Conformance Tested logo and the general DeviceNet logo .....................................6
Figure 3-2: DN system topology....................................................................................................................6
Figure 3-3: Example network for calculating cable length ..........................................................................10
Figure 3-4: Example of cable length calculation .........................................................................................10
Figure 3-5: Overview of DN connectors ......................................................................................................11
Figure 3-6: DeviceNet system power supply units ......................................................................................12
Figure 3-7: DeviceNet power tap.................................................................................................................13
Figure 3-8: Loading capacity of Thin Cable as a function of cable length ..................................................14
Figure 3-9: Loading capacity of thick cable as a function of cable length...................................................14
Figure 4-1: Bus contact assignments..........................................................................................................19
Figure 4-2: Terminating the DeviceNet bus line..........................................................................................20
Figure 5-1: Cube67 Standard EDS Generator ............................................................................................23
Figure 5-2: Configuration example for IDs ..................................................................................................25
Figure 5-3: Parameterization in EDS file (e.g. RSNetWorx) .......................................................................27
Figure 5-4: Time-dependent response to smoothing in Cube67 AI4 (U) modules .....................................45
Figure 5-5: Access via Explicit Message Service........................................................................................49
Figure 5-6: Assembly of the bus node hood ...............................................................................................73
Figure 5-7: Connecting system components...............................................................................................74
Figure 6-1: Evaluation of 16-bit group diagnostic of Cube67 I/O modules .................................................79
Figure 6-2: Position of DeviceNet displays on bus node ............................................................................81
Figure 6-3: Position of US and UA displays on the bus node .......................................................................82
Figure 6-4: Position of US and UA displays using Art. No. 56 600 as an example ......................................85
Figure 6-5: Position displays on power distributor ......................................................................................90
Figure 6-6: Position of displays on valve controller.....................................................................................91
V 1.0 95
9 List of Tables
Table 3-1: DN system data ........................................................................................................................... 7

Table 3-2: DeviceNet step-by-step guide to first-time system use ............................................................... 8
Table 3-3: Relation between transmission rate and main line length........................................................... 9
Table 3-4: Impact of different line lengths .................................................................................................. 14
Table 3-5: Impact of different line lengths .................................................................................................. 14
Table 5-1: Relationship between display in RSNetworx and actual layout ................................................ 25
Table 5-2: Format of I/O data referred to the configuration example ......................................................... 26
Table 5-3: Detailed format of the I/O data referred to the configuration example ...................................... 26
Table 5-4: Output data map of sample configuration ................................................................................. 26
Table 5-5: Bit assignment, input / diagnostic input function (only 8xM12 modules)................................... 28
Table 5-6: Bit assignment, input / diagnostic input function (only 4xM12 modules)................................... 28
Table 5-7: Value assignment, input / diagnostic input function .................................................................. 28
Table 5-8: Bit assignment, NO contact / NC contact function (only 8xM12 modules)............................... 28
Table 5-9: Bit assignment, NO contact / NC contact function (only 4xM12 modules)................................ 28
Table 5-10: Bit assignment, NO contact / NC contact function (only 8xM8 modules)............................... 28
Table 5-11: Bit assignment, input NO contact / NC contact function, Art.Nos. 56 661 /56 663 / 56 6650 . 28
Table 5-12: Bit assignment, input NO contact / NC contact function, Art.No. 56 662 ................................ 29
Table 5-13: Bit assignment, input NO contact / NC contact channel function, Art.Nos. 56 681 / 56 691 .. 29
Table 5-14: Value assignment,input NO contact / NC contact function ..................................................... 29
Table 5-15: Bit assignment, input / output function (only 8xM12 modules)................................................ 30
Table 5-16: Bit assignment, input / output function (only 4xM12 modules)............................................... 30
Table 5-17: Bit assignment, input / output function (only 8xM8 modules)................................................. 30
Table 5-18: Bit assignment, input / output function, Art.Nos. 56 661 / 56 663 / 56 6650 ........................... 30
Table 5-19: Bit assignment, input / output function, Art.No. 56 662 ........................................................... 30
Table 5-20: Bit assignment, input input / output channel function, X1 00…X1 07 Art.Nos. 56 681 / 56 691
............................................................................................................................................................. 30
Table 5-21: Value assignment, input / output function ............................................................................... 30
Table 5-22: Bit assignment, error action, Art. No. (only 8xM12 modules).................................................. 31
Table 5-23: Bit assignment, error action (only 4xM12 modules) ................................................................ 31
Table 5-24: Bit assignment, error action (only 8xM8 modules) .................................................................. 31
Table 5-25: Bit assignment, error action, Art.Nos. 56 650 / 56 651 ........................................................... 31
Table 5-26: Bit assignment, error action, Art.No. 56 655 ........................................................................... 31
Table 5-28: Bit assignment, error action, Art.Nos. 56 661 / 56 663 ........................................................... 31
Table 5-31: Bit assignment, error action function, channels X1 00…X1 07 Art.Nos. 56 681 / 56 691....... 32
Table 5-32: Value assignment, error action................................................................................................ 32
Table 5-33: Bit assignment, error value (only 8xM12 modules) ................................................................. 33
Table 5-34: Bit assignment, error value (only 4xM12 modules) ................................................................. 33
Table 5-35: Bit assignment, error value (only 8xM8 modules) ................................................................... 33
Table 5-36: Bit assignment, error value, Art.Nos. 56 650 / 56 651 ............................................................ 33
Table 5-37: Bit assignment, error value, Art.No. 56 655 ............................................................................ 33
Table 5-39: Bit assignment, error value, Art.Nos. 56 661 / 56 663 ............................................................ 33
Table 5-42: Bit assignment, error value function, channels X1 00…X1 07 Art.Nos. 56 681 / 56 691........ 34
Table 5-43: Value assignment, error value................................................................................................. 34
Table 5-44: Settings of Parameter Word 0 ................................................................................................. 35
Table 5-45: Settings of Counter 0............................................................................................................... 35
Table 5-46: Settings of Counter 1............................................................................................................... 36
Table 5-47: Counter 0 comparison value ................................................................................................... 36
Table 5-48: Comparison value Counter 1................................................................................................... 36
96 V 1.0
Table 5-49: Counter 0 counter status..........................................................................................................36

Table 5-50: Counter 1 counter status..........................................................................................................36
Table 5-51: Permissible values for the control byte ....................................................................................37
Table 5-52: Supported indexes of SAP 0 of Cube67 CNT2 4xM12 – Art.No. 56 750 ................................37
Table 5-53: Bit assignment, input / diagnostic input function, Art.No. 56 760 ............................................39
Table 5-54: Value definition, input / diagnostic input function, Art.No. 56 760 ...........................................39
Table 5-55: Bit assignment, input NO contact / NC contact function, Art.No. 56 760.................................39
Table 5-56: Value definition, input NO contact / NC contact function, Art.No. 56 760................................39
Table 5-57: Bit assignment, input / output function, Art.No. 56 760............................................................39
Table 5-58: Value definition, input / output function, Art.No. 56 760...........................................................39
Table 5-59: Bit assignment, error action, Art.No. 56 760............................................................................40
Table 5-60: Value definition, error action, Art.No. 56 760...........................................................................40
Table 5-61: Bit assignment, error value, Art.No. 56 760.............................................................................40
Table 5-62: Value definition, error value, Art.No. 56 760............................................................................40
Table 5-63: Value definition, RS485 operating mode, Art.No. 56 760 ........................................................41
Table 5-64: Value definition, RS485 operating mode, Art.No. 56 760 ........................................................41
Table 5-65: Value definition, RS485 send, Art.No. 56 760 .........................................................................41
Table 5-66: Value definition, RS485 echo, Art.No. 56 760 .........................................................................41
Table 5-67: Value definition, RS485 handshake, Art.No. 56 760 ...............................................................41
Table 5-70: Settings of logic function ..........................................................................................................43
Table 5-71: Selecting the measuring range Art.Nos. 56 700 / 56 701 / 56 730..........................................44
Table 5-72Additional settings Art.Nos. 56 700 / 56 701..............................................................................45
Table 5-73: Module operating mode, Art.Nos. 56 740 / 56 748 ..................................................................46
Table 5-74: Overview of connectivity, Art.No. 56 740 .................................................................................46
Table 5-752: Channel operating mode format (2) Art.No. 56 740...............................................................47
Table 5-76: Thermocouple selection Art.No. 56 748...................................................................................47
Table 5-77: Channel operating mode (1) - Cube67 AO4 C 4xM12 – Art. Nos. 56 710 / 56 720 ................47
Table 5-78: Channel operating mode (2) - Cube67 AO4 C 4xM12 – Art. Nos. 56 710 / 56 720 ................48
Table 5-79: Error value format, Art.No. 56 710 ...........................................................................................48
Table 5-80: Attributes of Class 100 Instance 1 ...........................................................................................50
Table 5-81: Attributes of Class 101 of all instances ....................................................................................51
Table 5-82: Sequence of input data of the Cube67 System .......................................................................55
Table 5-83: Sequence of the output data of the Cube67 System ...............................................................55
Table 5-84: Overview of I/O data lengths....................................................................................................56
Table 5-85: Format of bus node input data .................................................................................................57
Table 5-86: Input word for Cube67 I/O modules with M12 connection and max. 16 inputs .......................58
Table 5-87: Input word for Cube67 I/O modules with M12 connection and max. 8 inputs .........................58
Table 5-88: Input word for Cube67 I/O modules with M8 or valve connection and max. 8 inputs..............58
Table 5-89: Input word for Cube67 I/O modules with terminal block and max. 16 inputs...........................58
Table 5-90: Output word for Cube67 I/O modules with M12 connection and max. 16 outputs ..................59
Table 5-91: Output word for Cube67 I/O modules with M12 connection and max. 4 outputs ....................59
Table 5-92: Output byte for Cube67 I/O modules with M8 or valve connection and max. 8 outputs..........59
Table 5-93: Output byte for Cube67 I/O modules with valve connection and max. 16 outputs..................59
Table 5-94: Output byte for Cube67 I/O modules with terminal connection and max. 8 outputs ...............59
Table 5-95: Output word for Cube67 I/O modules with M12 connection and max. 32 outputs ..................60
Table 5-96: Input data for Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760 .............................................61
Table 5-97: Description of bit assignment, Byte Status_0, Art.No. 56 760.................................................61
Table 5-98: Description of bit assignment, Byte Status_1, Art.No. 56 760.................................................61
Table 5-99: Description of bit assignment, Byte Status_2 (communication status), Art.No. 56 760 ..........62
Table 5-100: Output data for Cube67 DIO4 RS485 E 3xM12 – Art. No. 56 760 ........................................63
Table 5-101: Bit assignment, Byte 0 : Ctrl_0...............................................................................................63
Table 5-104: Input bytes for Cube67 CNT2 C 4xM12 – Art. No. 56 750 ....................................................64
Table 5-105: Bit assignment, Byte Stat_0 / Stat_1 .....................................................................................64
Table 5-106: Output data for Cube67 CNT2 C 4xM12 – Art. No. 56 750 ...................................................65
Table 5-107: Bit assignment Byte Ctrl_0 / Ctrl_1 ........................................................................................65
V 1.0 97
Table 5-108: Response of gate signal........................................................................................................ 65

Table 5-109: Response of up/down signal ................................................................................................. 65
Table 5-110: Input byte for Cube67 Logic module with M12 connection ................................................... 66
Table 5-111: Input data format for AI4 (U) / (I) / RTD /TH, Motorola format............................................... 67
Table 5-112: Input data format for AI4 (U) / (I) / RTD /TH, Intel format...................................................... 67
Table 5-113: Output data format for AO4 (U) / (I) Motorola format ............................................................ 67
Table 5-114: Output data format for AO4 (U) / (I) Intel format ................................................................... 67
Table 5-115: Representation of the analog values of input modules, Art. Nos. 56 700 / 56 701 / 56 730. 68
Table 5-116: Representation of analog values of output modules, Art. Nos. 56 710 / 56 720................... 69
Table 5-117: Representation of analog values of input module, Art. No. 56 740....................................... 70
Table 5-118: Representation of analog values of input module, Art. No. 56 748....................................... 71
Table 6-1: Format of bus node input data .................................................................................................. 77
Table 6-2: Bus node diagnostic, Class 100 Instance 1 .............................................................................. 78
Table 6-3: Bus node diagnostic, Class 100 Instance 1 Attribute 6............................................................. 78
Table 6-4: Bus node diagnostic, Class 100 Instance 1 Attribute 8............................................................. 78
Table 6-5: Communication/configuration diagnostic word.......................................................................... 79
Table 6-6: Module diagnostic word............................................................................................................. 79
Table 6-7: Group diagnostic format, (Class 101, Instance (Module No.) Attribute 14) .............................. 80
Table 6-8: Description of the DeviceNet displays....................................................................................... 81
Table 6-9: Status of system communication at bus node........................................................................... 82
Table 6-10: Status of sensor and system power supply at bus node......................................................... 82
Table 6-11: Status of actuator power supply at bus node .......................................................................... 83
Table 6-12: Status of system communication............................................................................................. 85
Table 6-13: Status of sensor and system power supply (bus in display) ................................................... 85
Table 6-14: Status of internal actuator power supply (bus in display)........................................................ 86
Table 6-15: Status of external power display (Art. Nos. 56 600, 56 640)................................................... 86
Table 6-16: M12 sockets – LED diagnostic display.................................................................................... 86
Table 6-17: Relationship between signal-logic image and LED response input ........................................ 87
Table 6-18: Relationship between signal-logic image and LED response output ...................................... 87
Table 6-19: M12 socket – LED diagnostic display AI4 (U) / (I)................................................................... 88
Table 6-20: M12 socket – LED diagnostic display AO4 (U) / (I)................................................................. 88
Table 6-21: M12 sockets – LED diagnostic display AI4 RTD..................................................................... 88
Table 6-22: M12 sockets – LED diagnostic display AI4 TH ....................................................................... 89
Table 6-23: 6-pin M12 sockets – LED display ............................................................................................ 90
Table 6-24: DIAG LED display.................................................................................................................... 91
98 V 1.0

HDB e 10

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

HDB e 10

Încărcat de

Drepturi de autor:

Formate disponibile

Handbuch

Bus System Manual

Art. No. 56 507 Cube67 BN-DN

- For use in combination with SW Version 1.xx -

Manual Art. No. 56 984 Version 1.0

1.2 Symbols and Safety Instructions..................................................................................................1

2 Safety Instructions .................................................................................................. 3

2.2 Intended Purpose ...........................................................................................................................4

2.3 Qualified Personnel........................................................................................................................5

3 Configuration Notes ................................................................................................ 6

3.2 System Data ....................................................................................................................................7

3.3 Information for First-Time Users ..................................................................................................8

3.4 System Cables ................................................................................................................................9

3.5 Calculating the Line Length ........................................................................................................10

3.6 System Connectors......................................................................................................................11

3.7 System Power Supply ..................................................................................................................12

3.8 Wire Cross-Sections ....................................................................................................................14

3.9 Electromagnetic Compatibility (EMC) ........................................................................................15

4 Installation and Wiring .......................................................................................... 19

5.2 Cube67 Standard EDS Generator............................................................................................... 23

5.3 Assigning and Generating DeviceNet Addresses and Baud Rates........................................ 24

5.4 Configuration ............................................................................................................................... 25

5.5 Parameterization .......................................................................................................................... 27

5.5.5.13 Use of Error Value..............................................................................................................48

5.6 Mapping of I/O Data......................................................................................................................54

5.7 Format of I/O Data ........................................................................................................................57

5.8 Step by Step: Startup Example ...................................................................................................73

6.2 Displays on Bus Node..................................................................................................................81

6.2.3.3 Internal System Connection: Undervollage of Sensor Power Supply ............................... 83

6.3 Displays of the Digital I/O Modules............................................................................................ 85

6.4 Displays of Analog I/O Modules ................................................................................................. 88

6.5 Displays on Power Distributor.................................................................................................... 90

6.6 Displays on Valve DO16/DO8/DO32 and Cable DIO8 / M16 ..................................................... 91

7 Extended Functions in I/O Modules .................................................................... 94

7.2 SAP Format................................................................................................................................... 94

8 List of Figures ....................................................................................................... 95

9 List of Tables ......................................................................................................... 96

Manual Supplements / Corrections

Version Section Supplement / Correction Date/Name

1 About this Manual

Cube67 System Manual, Art. No. 56 970

Cube67 Bus System Manual Profibus Art. No. 56 980

1.1 Overview of Chapters

1.2 Symbols and Safety Instructions

2.1 Explanation of Symbols

2.1.1 Use of Notes

2.1.2 Use of Hazard Warnings

2.1.3 Use of Numbering in Figures

2.1.4 Use of Action Instructions

2.2 Intended Purpose

The products described in this manual

• meet the requirements specified in the

• EMC Directive (89/336/EEC)

2.3 Qualified Personnel

Weiterbildung in der Automatisierungstechnik (Advanced Training in Automation Technology)

These are persons who

3.1 DeviceNet System Description

You will find us and the ODVA on the web at:

www.murrelektronik.com, www.cube67.com, www.odva.org und www.can-cia.com

Trunk Leitung (Fernleitung) 3 2

Figure 3-2: DN system topology

3.2 System Data