BL67 - multiprotocol gateway for Ethernet

BL67 - multiprotocol gateway for Ethernet
BL67 MULTIPROTOCOL
GATEWAY
for
ETHERNET
Sense it! Connect it! Bus it! Solve it!
All brand and product names are trademarks or registered trade marks of the owner
concerned.
Edition 07/2013
© Hans Turck GmbH, Muelheim an der Ruhr
All rights reserved, including those of the translation.
No part of this manual may be reproduced in any form (printed, photocopy, microfilm or any
other process) or processed, duplicated or distributed by means of electronic systems
without written permission of Hans Turck GmbH & Co. KG, Muelheim an der Ruhr.
Subject to alterations without notice
Table of contents
1
About this manual
1.1
Documentation concept .................................................................................................................................1-2
1.1.1
Additional documentation .................................................................................................................................................................1-2
1.2
Description of symbols used ..........................................................................................................................1-3
1.3
General ............................................................................................................................................................1-4
1.3.1
1.3.2
Prescribed use .........................................................................................................................................................................................1-4
Notes concerning planning/ installation of this product ........................................................................................................1-4
2
BL67 philosophy
2.1
The basic concept ............................................................................................................................................2-2
2.1.1
2.1.2
Flexibility ...................................................................................................................................................................................................2-3
Easy to handle .........................................................................................................................................................................................2-3
2.2
BL67 components ............................................................................................................................................2-4
2.2.1
2.2.2
2.2.3
2.2.4
Gateways ...................................................................................................................................................................................................2-4
Electronic modules ................................................................................................................................................................................2-5
Base modules...........................................................................................................................................................................................2-5
End plate....................................................................................................................................................................................................2-6
3
Properties: gateway and I/O-modules
3.1
Function ...........................................................................................................................................................3-3
3.1.1
Version overview ....................................................................................................................................................................................3-3
3.2
Supported I/O-modules ..................................................................................................................................3-4
3.3
Technical data..................................................................................................................................................3-6
3.3.1
3.3.2
3.3.3
Top view BL67-GW-EN (VN < 03-00) ...............................................................................................................................................3-6
Top view BL67-GW-EN (VN ≥ 03-00) ..............................................................................................................................................3-7
Gateway structure..................................................................................................................................................................................3-7
3.4
Connection possibilities............................................................................................................................... 3-12
3.4.1
3.4.2
3.4.3
3.4.4
Fieldbus connection........................................................................................................................................................................... 3-12
Voltage supply via 7/8“-connector ............................................................................................................................................... 3-12
Service-interface female PS/2 connector (VN < 03-00).......................................................................................................... 3-13
Service interface Mini-USB (VN ≥ 03-00).................................................................................................................................... 3-14
3.5
Address assignment ..................................................................................................................................... 3-15
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.5.7
3.5.8
3.5.9
Default setting of the gateway....................................................................................................................................................... 3-16
Address setting via rotary coding switch (rotary mode)....................................................................................................... 3-17
Address setting via BootP-mode (300)........................................................................................................................................ 3-18
Address setting via DHCP-mode (400) ........................................................................................................................................ 3-18
Address setting via PGM-mode (500) .......................................................................................................................................... 3-19
Address setting via the mode PGM-DHCP (universal mode, 600)..................................................................................... 3-20
F_Reset (reset to factory settings, 900) ....................................................................................................................................... 3-20
Addressing via I/O-ASSISTANT 3 (FDT/DTM)............................................................................................................................. 3-21
Address assignment via Web server (only VN ³ 03-00) .......................................................................................................... 3-24
3.6
Web server - remote access/ configuration (only VN ≥ 03-00) ................................................................. 3-25
3.6.1
3.6.2
IP address ............................................................................................................................................................................................... 3-25
Access rights ......................................................................................................................................................................................... 3-25
D300815 0713- BL67 Multiprotocol
i
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
3.6.8
3.6.9
Login / password..................................................................................................................................................................................3-26
Network Configuration......................................................................................................................................................................3-26
Gateway Configuration .....................................................................................................................................................................3-27
Station Diagnostics .............................................................................................................................................................................3-27
Ethernet Statistics ................................................................................................................................................................................3-27
Links..........................................................................................................................................................................................................3-27
Change Admin Password..................................................................................................................................................................3-28
3.7
Status and Control Word of the BL67-stations........................................................................................... 3-29
3.7.1
3.7.2
Status Word............................................................................................................................................................................................3-29
Control Word.........................................................................................................................................................................................3-29
3.8
SET-button..................................................................................................................................................... 3-30
3.9
Status indicators/diagnostic messages gateway ....................................................................................... 3-31
3.9.1
Diagnostic messages via LEDs ........................................................................................................................................................3-31
3.10
Parameters of the modules .......................................................................................................................... 3-34
3.10.1
3.10.2
3.10.3
3.10.4
3.10.5
3.10.6
3.10.7
Digital input modules ........................................................................................................................................................................3-34
Analog input modules .......................................................................................................................................................................3-35
Digital output modules .....................................................................................................................................................................3-39
Analog output modules ....................................................................................................................................................................3-40
Digital combi modules.......................................................................................................................................................................3-43
Analog combi modules .....................................................................................................................................................................3-44
Technology modules..........................................................................................................................................................................3-48
3.11
Diagnostic messages of the modules.......................................................................................................... 3-57
3.11.1
3.11.2
3.11.3
3.11.4
3.11.5
3.11.6
3.11.7
3.11.8
Power distribution modules ............................................................................................................................................................3-57
Digital input modules ........................................................................................................................................................................3-57
Analog input modules .......................................................................................................................................................................3-58
Digital output modules .....................................................................................................................................................................3-61
Analog output modules ....................................................................................................................................................................3-63
Digital combi modules.......................................................................................................................................................................3-63
Analog combi modules .....................................................................................................................................................................3-65
Technology modules..........................................................................................................................................................................3-67
4
Implementation of EtherNet/IP
4.1
The EtherNet/IP Communications Profile ..................................................................................................... 4-2
4.1.1
4.1.2
4.1.3
I/O Messages ........................................................................................................................................................................................... 4-2
Explicit Messages ................................................................................................................................................................................... 4-2
Communications profile of the BL67-gateway ........................................................................................................................... 4-2
4.2
Diagnostic messages via the process data ................................................................................................... 4-4
4.2.1
4.2.2
Summarized Diagnostics .................................................................................................................................................................... 4-4
Scheduled Diagnostics ........................................................................................................................................................................ 4-4
4.3
Classes and Instances of the EtherNet/IP-stations....................................................................................... 4-5
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
EtherNet/IP Standard Classes ............................................................................................................................................................ 4-5
Identity Object (0x01)........................................................................................................................................................................... 4-6
Assembly Object (0x04)....................................................................................................................................................................... 4-8
TCP/IP Interface Object (0xF5) ........................................................................................................................................................4-11
Ethernet Link Object (0xF6)..............................................................................................................................................................4-15
DLR Object (0x47) ................................................................................................................................................................................4-18
QOS Object (0x48) ...............................................................................................................................................................................4-19
ii
D300815 0713- BL67 Multiprotocol
4.4
VSC-Vendor Specific Classes........................................................................................................................ 4-20
4.4.1
4.4.2
4.4.3
4.4.4
Class instance of the VSC.................................................................................................................................................................. 4-20
Gateway Class (VSC 100, 64h) ......................................................................................................................................................... 4-21
Process Data Class (VSC102, 66h) .................................................................................................................................................. 4-24
Miscellaneous Parameters Class (VSC 126) ................................................................................................................................ 4-26
5
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
5.1
General .............................................................................................................................................................5-2
5.1.1
Used hard-/ software.............................................................................................................................................................................5-2
5.2
Network configuration....................................................................................................................................5-3
5.2.1
5.2.2
Configuration of the network in "RS Logix 5000" .......................................................................................................................5-3
Downloading the I/O configuration................................................................................................................................................5-8
5.3
I/O data mapping.......................................................................................................................................... 5-10
5.4
Process data access ...................................................................................................................................... 5-12
5.4.1
5.4.2
Setting outputs .................................................................................................................................................................................... 5-12
Example program................................................................................................................................................................................ 5-13
6
Implementation of Modbus TCP
6.1
Common Modbus description ........................................................................................................................6-2
6.1.1
6.1.2
Protocol description..............................................................................................................................................................................6-3
Data model ...............................................................................................................................................................................................6-4
6.2
Implemented Modbus functions....................................................................................................................6-5
6.3
Modbus-registers ............................................................................................................................................6-6
6.4
Structure of the packed in-/ output process data ...................................................................................... 6-10
6.4.1
6.4.2
Packed input process data............................................................................................................................................................... 6-10
Packed output process data............................................................................................................................................................ 6-11
6.5
Data width of the I/O-modules in the modbus-register area.................................................................... 6-12
6.5.1
6.5.2
6.5.3
6.5.4
6.5.5
Register 100Ch: "Gateway status" ................................................................................................................................................. 6-13
Register 1130h: „Modbus-Connection-Mode“.......................................................................................................................... 6-14
Register 1131h: „Modbus-Connection-Timeout“ .................................................................................................................... 6-14
Register 0x113C and 0x113D: „Restore Modbus-Connection-Parameters”................................................................... 6-14
Register 0x113E and 0x113F: „Save Modbus-Connection-Parameters“.......................................................................... 6-14
6.6
The Service-Object ....................................................................................................................................... 6-15
6.7
Bit areas: mapping of input-discrete- and coil-areas ................................................................................ 6-18
6.8
Output module behavior in case of an error .............................................................................................. 6-19
7
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
7.1
Used hard-/ software.......................................................................................................................................7-2
7.1.1
7.1.2
Hardware ...................................................................................................................................................................................................7-2
Software.....................................................................................................................................................................................................7-2
7.2
Network configuration....................................................................................................................................7-3
D300815 0713- BL67 Multiprotocol
iii
7.3
Programming with CoDeSys .......................................................................................................................... 7-4
7.3.1
7.3.2
7.3.3
7.3.4
7.3.5
7.3.6
7.3.7
7.3.8
7.3.9
7.3.10
7.3.11
7.3.12
Predefined feature sets........................................................................................................................................................................ 7-4
Creating a new project ........................................................................................................................................................................ 7-5
Defining the communication settings ........................................................................................................................................... 7-7
Adding the Ethernet Adapter............................................................................................................................................................ 7-9
Adding the Modbus master .............................................................................................................................................................7-10
Adding a Modbus TCP slave ............................................................................................................................................................7-11
Programming (example program) ................................................................................................................................................7-13
CoDeSys: Global variables ................................................................................................................................................................7-14
Modbus channels.................................................................................................................................................................................7-15
Building, login and start ....................................................................................................................................................................7-27
Reading out the process data .........................................................................................................................................................7-29
Diagnosis evaluation ..........................................................................................................................................................................7-30
8
Implementation of PROFINET®
8.1
Address assignment ....................................................................................................................................... 8-2
8.2
GSDML-file....................................................................................................................................................... 8-3
8.3
Default-values ................................................................................................................................................. 8-3
8.4
Diagnosis in PROFINET® ................................................................................................................................. 8-4
8.4.1
8.4.2
Gateway Error codes ............................................................................................................................................................................ 8-4
Channel -specific error codes of the I/O-modules .................................................................................................................... 8-5
8.5
Parameterization ............................................................................................................................................ 8-9
8.5.1
8.5.2
8.5.3
Gateway parameters............................................................................................................................................................................. 8-9
I/O-module-parameters ....................................................................................................................................................................8-12
Parameter "module parameterization"........................................................................................................................................8-12
8.6
Description of user data for acyclic services............................................................................................... 8-13
8.6.1
8.6.2
Description of the acyclic gateway user data............................................................................................................................8-13
Description of the acyclic module user data .............................................................................................................................8-14
9
Application example: BL67-GW-EN with PROFINET® (S7)
9.1
Application example ...................................................................................................................................... 9-2
9.1.1
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
9.1.8
9.1.9
9.1.10
General ...................................................................................................................................................................................................... 9-2
Example network ................................................................................................................................................................................... 9-2
New project in the Simatic Manager .............................................................................................................................................. 9-3
Setting the PG/PC-interface............................................................................................................................................................... 9-3
Installation of the GSDML-files.......................................................................................................................................................... 9-4
Adding PROFINET® network nodes ................................................................................................................................................. 9-8
Configuring the BL67-station ..........................................................................................................................................................9-10
Scanning the network for PROFINET® nodes.............................................................................................................................9-12
PROFINET® neighborhood detection via LLDP .........................................................................................................................9-14
Online topology detection...............................................................................................................................................................9-17
9.2
Diagnostics with Step 7 ................................................................................................................................ 9-18
9.2.1
9.2.2
Diagnostic messages in the hardware configuration.............................................................................................................9-18
Diagnostic telegram with error code ...........................................................................................................................................9-19
10
Guidelines for station planning
10.1
Module arrangement.................................................................................................................................... 10-2
iv
D300815 0713- BL67 Multiprotocol
10.1.1 Random module arrangement....................................................................................................................................................... 10-2
10.2
Complete planning....................................................................................................................................... 10-3
10.3
Maximum system extension........................................................................................................................ 10-4
10.4
Creating potential groups ........................................................................................................................... 10-6
10.5
Plugging and pulling electronics modules................................................................................................. 10-6
10.6
Extending an existing station...................................................................................................................... 10-6
10.7
Firmware download ..................................................................................................................................... 10-6
11
Guidelines for Electrical Installation
11.1
General notes................................................................................................................................................ 11-2
11.1.1
11.1.2
11.1.3
11.1.4
General .................................................................................................................................................................................................... 11-2
Cable routing ........................................................................................................................................................................................ 11-2
Lightning protection.......................................................................................................................................................................... 11-3
Transmission media............................................................................................................................................................................ 11-3
11.2
Potential relationships................................................................................................................................. 11-4
11.2.1 General .................................................................................................................................................................................................... 11-4
11.3
Electromagnetic compatibility (EMC) ......................................................................................................... 11-5
11.3.1
11.3.2
11.3.3
11.3.4
11.3.5
Ensuring electromagnetic compatibility .................................................................................................................................... 11-5
Grounding of inactive metal components................................................................................................................................. 11-5
PE connection....................................................................................................................................................................................... 11-5
Earth-free operation ........................................................................................................................................................................... 11-5
Mounting rails....................................................................................................................................................................................... 11-6
11.4
Shielding of cables ....................................................................................................................................... 11-7
11.5
Potential compensation............................................................................................................................... 11-8
11.5.1 Switching inductive loads ................................................................................................................................................................ 11-8
11.5.2 Protection against Electrostatic Discharge (ESD) .................................................................................................................... 11-8
12
Appendix
12.1
Data image of the technology modules ..................................................................................................... 12-2
12.1.1 1RS232/ 1RS485-module .................................................................................................................................................................. 12-2
12.1.2 SSI module ............................................................................................................................................................................................. 12-6
12.2
Changing the IP address of a PC/ network interface card ....................................................................... 12-12
12.2.1 Changing the IP address in Windows ........................................................................................................................................12-12
12.2.2 Changing the IP address via PACTware™ FDT/DTM (I/O-ASSISTANT V3) ....................................................................12-14
12.3
Deactivating/ adapting the firewall in Windows ..................................................................................... 12-15
12.4
Addressing via DHCP.................................................................................................................................. 12-17
12.5
Nominal current consumption of modules on Ethernet ......................................................................... 12-19
12.6
Ident codes of the BL67-modules............................................................................................................. 12-21
13
Glossary
14
Index
D300815 0713- BL67 Multiprotocol
v
vi
D300815 0713- BL67 Multiprotocol
1
About this manual
1.1
Documentation concept.................................................................................................................... 2
1.1.1
Additional documentation .................................................................................................................... 2
1.2
Description of symbols used ............................................................................................................ 3
1.3
General ............................................................................................................................................. 4
1.3.1
1.3.2
Prescribed use...................................................................................................................................... 4
Notes concerning planning/ installation of this product....................................................................... 4
D300815 0713- BL67 Multiprotocol
1-1
About this manual
1.1
Documentation concept
This manual contains all information about the multiprotocol-gateway of the product line BL67 (BL67GW-EN).
In addition to a short BL67-system description and the protocol-independent properties of the gateway
and if necessary of the I/O-modules (technical properties, diagnostics, parameters, etc.), the following
chapters contain two protocol-dependent chapters respectively.
The protocol-dependent chapters contain on the one hand the protocol-specific gateway-properties
and on the other hand an application example for the respective Ethernet-protocol, describing the
device's connection to automation devices.
„ EtherNet/IP™
– chapter 4, Implementation of EtherNet/IP
– chapter 5, Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
„ Modbus TCP
– chapter 6, Implementation of Modbus TCP
– chapter 7, Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
„ PROFINET®
– chapter 8, Implementation of PROFINET®
– chapter 9, Application example: BL67-GW-EN with PROFINET® (S7)
Additionally, the manual contain protocol-independent guideline for station configuration, the
electrical installation, etc..
1.1.1
Additional documentation
„ BL67 I/O-modules (TURCK-documentation no.: German D300572; English D300529).
The bus-independent I/O-modules of the BL67-system as well as all bus independent information
as mounting, labeling etc. are described in a separate manual.
In addition to that, the manual contains a short description of the I/O-ASSISTANT, the project
planning and configuration software tool for TURCK I/O-systems.
1-2
D300815 0713- BL67 Multiprotocol
Description of symbols used
1.2
Description of symbols used
Danger
This sign can be found next to all notes that indicate a source of hazards. This can refer to
danger to personnel or damage to the system (hardware and software) and to the facility.
This sign means for the operator: work with extreme caution.
Attention
This sign can be found next to all notes that indicate a potential hazard.
This can refer to possible danger to personnel and damages to the system (hardware and
software) and to the facility.
Note
This sign can be found next to all general notes that supply important information about one
or more operating steps.
These specific notes are intended to make operation easier and avoid unnecessary work due
to incorrect operation.
D300815 0713- BL67 Multiprotocol
1-3
About this manual
1.3
General
Attention
Please read this section carefully. Safety aspects cannot be left to chance when dealing with
electrical equipment.
This manual includes all information necessary for the prescribed use of the BL67-GW-EN. It has been
specially conceived for personnel with the necessary qualifications.
1.3.1
Prescribed use
Appropriate transport, storage, deployment and mounting as well as careful operating and thorough
maintenance guarantee the trouble-free and safe operation of these devices.
Danger
The devices described in this manual must be used only in applications prescribed in this
manual or in the respective technical descriptions, and only with certified components and
devices from third party manufacturers.
1.3.2
Notes concerning planning/ installation of this product
Danger
All respective safety measures and accident protection guidelines must be considered
carefully and without exception.
1-4
D300815 0713- BL67 Multiprotocol
2
BL67 philosophy
2.1
The basic concept.............................................................................................................................. 2
2.1.1
2.1.2
Flexibility ............................................................................................................................................... 3
Easy to handle ...................................................................................................................................... 3
2.2
BL67 components.............................................................................................................................. 4
2.2.1
2.2.2
Gateways.............................................................................................................................................. 4
Electronic modules ............................................................................................................................... 5
– Power Feeding-modules ................................................................................................................... 5
Base modules....................................................................................................................................... 5
End plate............................................................................................................................................... 6
2.2.3
2.2.4
D300815 0713- BL67 Multiprotocol
2-1
BL67 philosophy
2.1
The basic concept
BL67 is a modular I/O system of protection class IP67 for use in industrial automation. It connects the
sensors and actuators in the field with the higher-level master.
BL67 offers modules for practically all applications:
„ Digital input and output modules
„ Analog input and output modules
„ Technology modules (SSI interface, RS232 interface,...)
A complete BL67 station counts as one station on the bus and therefore occupies one fieldbus address
in any given fieldbus structure.
A BL67 station consists of a gateway, power distribution modules and I/O modules.
The connection to the relevant fieldbus is made via the bus-specific gateway, which is responsible for
the communication between the BL67 station and the other fieldbus stations.
The communication within the BL67 station between the gateway and the individual BL67 modules is
regulated via an internal module bus.
Note
The gateway is the only fieldbus-dependent module on a BL67 station. All other BL67
modules are not dependent on the fieldbus used.
2-2
D300815 0713- BL67 Multiprotocol
The basic concept
2.1.1
Flexibility
A BL67 station can contain modules in any combination, which means it is possible to adapt the system
to practically all applications in automated industry.
2.1.2
Easy to handle
All BL67 modules of the standard line, with the exception of the gateway, consist of a base module and
an electronics module.
The gateway and the base modules are either snapped onto a mounting rail or are directly mounted
onto the machine frame. The electronic modules are plugged onto the appropriate base modules.
The electronics modules can be plugged or pulled when the station is being commissioned or for
maintenance purposes, without having to disconnect the field wiring from the base modules.
D300815 0713- BL67 Multiprotocol
2-3
BL67 philosophy
2.2
BL67 components
Figure 2-1:
BL67-station
Agateway
Belectronic
module
Cbase module
B
C
A
2.2.1
Gateways
The gateway connects the fieldbus to the I/O modules. It is responsible for handling the entire process
data and generates diagnostic information for the higher-level master and the software tool I/OASSISTANT.
Figure 2-2:
BL67-gateway
2-4
D300815 0713- BL67 Multiprotocol
BL67 components
2.2.2
Electronic modules
The standard electronics modules contain the I/O-functions of the BL67 modules (power distribution
modules, digital and analog input/output modules, and technology modules).
They are plugged onto the base modules and are not directly connected to the wiring and can be
plugged or pulled when the station is being commissioned or for maintenance purposes, without
having to disconnect the field wiring from the base modules.
Figure 2-3:
Example of an
electronic module
Power Feeding-modules
Power Feeding modules distribute the required 24 V DC field voltage to the I/O-modules. They are
necessary for building groups of modules with different potentials within a BL67 station, or if the rated
supply voltage for the outputs cannot be guaranteed.
Power Feeding modules are potentially isolated from the adjoining power supply module and the I/Omodules to the left side.
Note
For detailed information about the individual BL67 I/O components, please refer to the
chapters 2 to 8 of the manual "BL67- I/O-modules" (TURCK Documentation-No.: German
D300572; English: D300529).
The "Appendix" to the manual mentioned above contains (amongst others) a list of all BL67
components and the assignment of electronic modules to base modules.
2.2.3
Base modules
The field wiring is connected to the base modules.
These are available in the following connection variations:
„ 1 × M12, 2 × M12, 2 × M12-P, 4 × M12, 4 × M12-P
„ 4 × M8, 8 × M8
„ 1 × M12-8
„ 1 × M23, 1 × M23-19
D300815 0713- BL67 Multiprotocol
2-5
BL67 philosophy
„ 1 × 7/8’’ (for Power Feeding-modules)
Figure 2-4:
Example of a base
module
2.2.4
End plate
An end plate on the right-hand side physically completes the BL67 station.
It protects the module bus connections of the last base module in a station and guarantees the
protection class IP67.
Figure 2-5:
End plate
2-6
D300815 0713- BL67 Multiprotocol
3
Properties: gateway and I/O-modules
3.1
Function ............................................................................................................................................ 2
3.2
Supported I/O-modules .................................................................................................................... 3
3.3
Technical data ................................................................................................................................... 5
3.3.1
3.3.2
3.3.3
Top view BL67-GW-EN (VN < 03-00) .................................................................................................. 5
Top view BL67-GW-EN (VN ≥ 03-00) ................................................................................................. 6
Gateway structure ................................................................................................................................ 6
– BL67-GW-EN < VN 03-00 ................................................................................................................. 6
– BL67-GW-EN ≥ VN 03-00 ................................................................................................................ 7
3.4
Connection possibilities.................................................................................................................. 11
3.4.1
3.4.4
Fieldbus connection ........................................................................................................................... 11
– BL67-GW-EN (VN < 03-00) ............................................................................................................. 11
– BL67-GW-EN (VN ≥ 03-00)............................................................................................................. 11
Voltage supply via 7/8“-connector ..................................................................................................... 11
Service-interface female PS/2 connector (VN < 03-00) ..................................................................... 12
– Connection with I/O-ASSISTANT-connection cable ....................................................................... 12
– Connection using commercially available cables............................................................................ 12
Service interface Mini-USB (VN ≥ 03-00) .......................................................................................... 13
3.5
Address assignment........................................................................................................................ 14
3.4.2
3.4.3
3.5.7
3.5.8
3.5.9
– LED behavior ................................................................................................................................... 14
Default setting of the gateway............................................................................................................ 15
– Resetting the IP-address, switch position "000"............................................................................. 15
Address setting via rotary coding switch (rotary mode) ..................................................................... 16
Address setting via BootP-mode (300)............................................................................................... 17
Address setting via DHCP-mode (400)............................................................................................... 17
Address setting via PGM-mode (500) ................................................................................................ 18
Address setting via the mode PGM-DHCP (universal mode, 600)..................................................... 19
– Permanent IP-address assignment using the Rockwell BOOTP/DHCP-server .............................. 19
– PROFINET® ..................................................................................................................................... 19
F_Reset (reset to factory settings, 900).............................................................................................. 19
Addressing via I/O-ASSISTANT 3 (FDT/DTM) .................................................................................... 20
Address assignment via Web server (only VN ≥ 03-00) .................................................................... 23
3.6
Web server - remote access/ configuration (only VN ≥ 03-00) ....................................................... 24
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
3.6.8
3.6.9
IP address........................................................................................................................................... 24
Access rights ...................................................................................................................................... 24
Login / password ................................................................................................................................ 25
Network Configuration........................................................................................................................ 25
Gateway Configuration ....................................................................................................................... 26
Station Diagnostics............................................................................................................................. 26
Ethernet Statistics .............................................................................................................................. 26
Links ................................................................................................................................................... 26
Change Admin Password ................................................................................................................... 27
3.7
Status and Control Word of the BL67-stations................................................................................ 28
3.7.1
Status Word........................................................................................................................................ 28
– Meaning of the status bits ............................................................................................................... 28
Control Word ...................................................................................................................................... 28
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.7.2
D300815 0713- BL67 Multiprotocol
3-1
Properties: gateway and I/O-modules
3.8
SET-button ...................................................................................................................................... 29
3.9
Status indicators/diagnostic messages gateway ............................................................................ 30
3.9.1
Diagnostic messages via LEDs ..........................................................................................................30
3.10
Parameters of the modules ............................................................................................................. 33
3.10.1
3.10.2
3.10.3
3.10.4
3.10.5
3.10.6
3.10.7
Digital input modules ..........................................................................................................................33
Analog input modules.........................................................................................................................34
Digital output modules........................................................................................................................38
Analog output modules ......................................................................................................................39
Digital combi modules ........................................................................................................................42
Analog combi modules .......................................................................................................................43
Technology modules ..........................................................................................................................47
3.11
Diagnostic messages of the modules .............................................................................................. 56
3.11.1
3.11.2
3.11.3
3.11.4
3.11.5
3.11.6
3.11.7
3.11.8
Power distribution modules................................................................................................................56
Digital input modules ..........................................................................................................................56
Analog input modules.........................................................................................................................57
Digital output modules........................................................................................................................60
Analog output modules ......................................................................................................................62
Digital combi modules ........................................................................................................................62
Analog combi modules .......................................................................................................................64
Technology modules ..........................................................................................................................66
3-2
D300815 0713- BL67 Multiprotocol
Function
3.1
Function
The BL67-GW-EN is used as multiprotocol-interface between the BL67-system and the Ethernet-protocols Modbus TCP, EtherNet/IP™ and PROFINET (> VN 03-00).
3.1.1
Version overview
Please observe, that the previous version of the gaetway did only support the Modbus TCP protocol.
„ Version < VN 03-00
BL67-gateway supports only the Ethernet protocol
– Modbus TCP
„ Version VN 03-01
BL67-gateway supports only the Ethernet protocol
– Modbus TCP
– EtherNet/IP™
„ Version ≥ VN 03-02
BL67-gateway supports the Ethernet protocols
– Modbus TCP
– EtherNet/IP™
– PROFINET®
Note
The multiprotocol gateway replaces all earlier versions and is fully compatible.
Only the LED-designation has changed. Please find detailed information under Diagnostic
messages via LEDs (page 3-31).
D300815 0713- BL67 Multiprotocol
3-3
Properties: gateway and I/O-modules
3.2
Supported I/O-modules
Table 3-1:
Module
EtherNet/IP™
Modbus TCP
PROFINET®
List of supported
modules
Digital input modules
BL67-4DI-P
9
9
9
BL67-4DI-N
9
9
9
BL67-4DI-PD
9
9
9
BL67-8DI-P
9
9
9
BL67-8DI-N
9
9
9
BL67-8DI-PD
9
9
9
BL67-16DI-P
9
9
9
BL67-2AI-I
9
9
9
BL67-2AI-V
9
9
9
BL67-2AI-PT
9
9
9
BL67-2AI-TC
9
9
9
BL67-4AI-TC
9
9
9
BL67-4AI-V/I
9
9
9
BL67-4DO-0.5A-P
9
9
9
BL67-4DO-2A-P
9
9
9
BL67-4DO-2A-N
9
9
9
BL67-4DO-4A-P
9
9
9
BL67-8DO-0.5A-P
9
9
9
BL67-8DO-0.5A-N
9
9
9
BL67-16DO-0.1A-P
9
9
9
BL67-2AO-I
9
9
9
BL67-2AO-V
9
9
9
BL67-4AO-V
9
9
9
9
9
9
Analog input modules
Digital output modules
Analog output modules
Relay modules
BL67-8DO-R-NO
3-4
D300815 0713- BL67 Multiprotocol
Supported I/O-modules
Table 3-1:
Module
EtherNet/IP™
Modbus TCP
PROFINET®
List of supported
modules
Digital combi modules
BL67-4DI4DO-PD
9
9
9
BL67-8XSG-P
9
9
9
BL67-8XSG-PD
9
9
9
BL67-2AI2AO-V/I
9
9
9
BL67-4AI4AO-V/I
9
9
9
BL67-1RS232
9
9
9
BL67-1RS485/422
9
9
9
BL67-1SSI
9
9
9
BL67-1CVI
9
9
9
BL67-1CNT/ENC
9
9
9
Analog combi modules
Technology modules
9
BL67-2RFID-A
BL67-2RFID-S
9
9
9
9
9
9
Power distribution modules
BL67-PF-24VDC
D300815 0713- BL67 Multiprotocol
3-5
Properties: gateway and I/O-modules
3.3
Technical data
3.3.1
Top view BL67-GW-EN (VN < 03-00)
Figure 3-1:
Front view
A power supply
B Ethernet
C not used
D SET-button
E service interface
F rotary coding
switches
G module bus LED
H designation
I status LED
J LEDs for the
power supply
monitoring
K Ethernet LEDs
G
F
H
E
D
I
J
K
C
B
A
3-6
D300815 0713- BL67 Multiprotocol
Technical data
3.3.2
Top view BL67-GW-EN (VN ≥ 03-00)
Figure 3-2:
Top view BL67GW-EN (VN ≥ 0300)
G
F
H
A power supply
B Ethernet 1
C Ethernet 2
D SET-button
E service-interface, no function
F rotary coding
switches
G module bus LED
H designation
I status LED
J LEDs for the
power supply
monitoring
K Ethernet LEDs
E
I
J
D
K
C
B
A
3.3.3
Gateway structure
BL67-GW-EN < VN 03-00
The BL67 gateway has the following structure:
Figure 3-3:
Gateway structure < VN 03-00
BL67Systembus
service
interface
mC
memory
PS/2
4
Ethernet
interface
2
1
3
communication
bus
module bus
interface
Ethernet
5
1
2
3
4
V0
5 VDC
Vi
24 VDC
Power
bus
short circuit
protection
Vsens
PE
GND
D300815 0713- BL67 Multiprotocol
3-7
Properties: gateway and I/O-modules
BL67-GW-EN ≥ VN 03-00
The BL67 gateway has the following structure:
Figure 3-4:
Gateway structure≥ VN 03-00
BL67system bus
Service
mC
USB
Switch
4
3
2
1
Eth2
Communi-’
cation
bus
2
1
Eth1
Memory
4
3
5
1
2
3
4
Module bus
interface
V0
5 VDC
Vi
24 VDC
Power
bus
Short circuit
protection
Vsens
PE
GND
3-8
D300815 0713- BL67 Multiprotocol
Technical data
Table 3-2:
supply voltage
Technical data
Ethernet gateway Requirements for the power supply according to EN 61131-2
System supply VI (UB)
Admissible range
Field supply VO (UL)
Admissible range
24 V DC
18 to 30 VDC
used to generate the galvanically isolated module bus supply
24 V DC
18 to 30 VDC
Isys
600 mA
current consumption CPU +
module bus at maximum system extension
IMB
max. 1.3 A
maximum output current of
module bus supply
IVI
max. 4 A
short-circuit and overload protection of the sensor supply
from gateway or power feeding
module
Isolation voltages
URS
(Ethernet/
service interface)
500 V AC
UEN
(Ethernet/ module bus)
500 V AC
Usys
(VO/VI to Usys)
1000 V DC
Ufield / service interface
1000 V DC
Ambient conditions
Ambient temperature
– tAmbient
-25 to +70 °C (-13 to 158 °F)
(- 40 to +70 °C / -40 to 158 °F on request)
– tStore
40 to +85 °C (40 to 185 °F)
Relative humidity
5 to 95 % (internal), Level RH-2, no condensation (at 45 °C storage);
according to IEC 61131-2
Climatic tests
according to IEC 61131-2
Corrosive gas
according to IEC 60068-2-42/43
– SO2
10 ppm (rel. humidity < 75 %, no condensation)
– H2S
1.0 ppm (rel. humidity < 75 %, no condensation)
Vibration resistance
according to IEC 61131-2
D300815 0713- BL67 Multiprotocol
3-9
Properties: gateway and I/O-modules
– 10 to 57 Hz, constant amplitude 0.075 mm / 0.003 inch,
1g
yes
– 57 to 150 Hz, constant acceleration 1g
yes
– Mode of vibration
Frequency sweeps with a change in speed of 1 Octave/min
– Period of oscillation
20 frequency sweeps per axis of coordinate
Protection class
according to IEC 60529, IP67
Shock resistance
according to IEC 68-2-27,18 shocks, sinusoidal half-wave 15 g peak
value/11 ms, in each case in ± direction per space coordinate
Repetitive shock resistance
according to IEC 68-2-29, 1000 shocks, semi-sinusoidal 25 g threshold/6 ms, each in ± direction per space coordinate
Drop and topple/
free fall
according to EN 68-2-31/ IEC 68-2-32
– Drop height
(weight < 10 kg)
1.0 m
– Drop height
(weight 10 to 40 kg)
0.5 m
– Test runs
7
Emitted interference
High-frequency, radiated
Electromagnetic compatibility
(EMC)
acc. to EN 55011 class A
according to EN 61131-2/EN 50082-2 (industy)
Static electricity according to
EN 61 000-4-2
– Discharge through air (direct) 8 kV
A I/O-line-length ≤
30 m
3-10
– Relay discharge
(indirect)
4 kV
Electromagnetic
HF fields
according to IEC 61131-2
Fast transients (Burst)
according to IEC 61131-2
Conducted
interferences
induced by HF fields
according to IEC 61000-4-6
10 V
Criteria A
High energy
transients A
Power supply
according to IEC 61000-4-5
0,5 kV CM, 12Ω/ 9 μF
0,5 kV DM, 2Ω/ 18 μF
Criteria B
D300815 0713- BL67 Multiprotocol
Technical data
Reliability
Pull/plug cycles of
electronic modules
housing material
20
PC-V0 (Lexan)
Size
Width x length x height
(mm/inch)
64,5 × 145,0 × 77,5 / 2,54 × 5,71 × 3,05
Danger
This device can cause radio disturbances in residential areas and in small industrial areas (residential, business and trading). In this case, the operator can be required to take appropriate
measures to suppress the disturbance at his own cost.
D300815 0713- BL67 Multiprotocol
3-11
Properties: gateway and I/O-modules
3.4
3.4.1
Connection possibilities
Fieldbus connection
BL67-GW-EN (VN < 03-00)
The connection to Ethernet is realized via a 4-pole and D-coded female connector on the gateway
according to IAONA-standards.
BL67-GW-EN (VN ≥ 03-00)
The connection to Ethernet is realized via a 4-pole and D-coded integrated switch on the gateway
according to IAONA-standards.
The switch allows linear topology.
Figure 3-5:
M12 female connector,
Table 3-3:
Pin assignment
3.4.2
2
1
4
3
Pin-no.
1
TD+
Transmission Data +
2
RD+
Receive Data +
3
TD-
Transmission Data -
4
RD-
Receive Data -
Voltage supply via 7/8“-connector
The power supply of the BL67 station is realized via a 7/8" male connector on the gateway.
Figure 3-6:
male 7/8" connec- 1
tor for power sup2
ply
Table 3-4:
PinPin assignment of no.
the 7/8" connector
3-12
5
4
3
Color
7/8“
Designation
1
black
GND
2
blue
GND
3
green/yellow
PE
Protective earth
4
brown
VI (UB)
Feed-in of nominal voltage for input modules
(sensor supply Vsens)); also used for the generation
of the system supply voltage
5
white
VO (UL)
Feed-in of nominal voltage for output modules
(can be switched off separately).
D300815 0713- BL67 Multiprotocol
Connection possibilities
3.4.3
Service-interface female PS/2 connector (VN < 03-00)
The female PS/2 connector is used to connect the gateway to the project planning and diagnostic software I/O-ASSISTANT.
The service interface is designed as a 6 pole mini-DIN-connection.
Two types of cables can be used to connect the service interface (female PS/2 connector) to a PC for the
purpose of using I/O-ASSISTANT (project planning and diagnostic software).
„ special I/O-ASSISTANT-connection cable from TURCK (IOASSISTANT-ADAPTERKABEL-BL20/BL67;
Ident-no.: 6827133)
„ Commercially available PS/2 cable with adapter cable SUB-D/ PS/2
Connection with I/O-ASSISTANT-connection cable
The I/O-ASSISTANT-cables have a PS/2 male connector (connection for female connector on gateway)
and a SUB-D female connector (connection for male connector on PC).
Figure 3-7:
PS/2 male connector on the connection cable to
the gateway (top
view)
4 3
5
2
6
Figure 3-8:
9-pole SUB-D
female connector
on the cable for
connecting to PC
(top view)
1
5
4
9
3
8
2
7
1
6
Connection using commercially available cables
A further possibility to connect PC and BL67 gateway is to use a commercially available connection and
adapter cable.
The connection shown in the following figure (PS2-male/ PS2-male) is a 6-wire 1:1 connection.
The following two cables are necessary:
„ 1 x PS/2 cable (PS/2 male connector/PS/2 male connector) (commercially available keyboard extension cable)
„ 1 x adapter cable (PS/2 female connector/SUB-D female connector) (commercially available extension cable for a PC mouse)
Figure 3-9:
PS/2 male connector on the connection cable to
the gateway (top
view)
Figure 3-10:
PS/2 female connector on the
gateway (top
view)
3 4
5
2
1
1
6
2
6
3
7
4
8
5
9
D300815 0713- BL67 Multiprotocol
3-13
Properties: gateway and I/O-modules
Pin configuration
The table below shows the pin assignment when using a PS/2 cable and adapter:
Table 3-5:
PS/2
Pin assignment
Pin-no.
when using PS/2
cable and adapter
A not supported
by all adapter
cables
3.4.4
9-pole serial interface on PC
Standard
BL67 gateway:
PS/2 male con- PS/2 female
nector
connector
Pin-no.
Male connector
1
CLK
+5 V
(from gateway)
4, 6 A
DTR, DSR
2
GND
GND
5
GND
3
DATA
not used
–
–
4
nicht verbunden (DATA2)
TxD
2
RxD
5
+5 V
/CtrlMode
7
RTS
6
nicht verbunden (CLK2)
RxD
3
TxD
Service interface Mini-USB (VN ≥ 03-00)
The access of the software I/O-ASSISTANT 3 (FDT/DTM) via the service-interface (Mini-USB) is not
supported.
For a connection to the gateway via I/O-ASSISTANT 3 (FDT/DTM) is done via Ethernet.
3-14
D300815 0713- BL67 Multiprotocol
Address assignment
3.5
Address assignment
Setting the address mode is done through the 3 rotary coding-switches on the gateway.
Note
It is not necessary to address the station’s internal module bus.
Attention
The cover of the decimal rotary coding-switches must be closed by tightening the screw after
use.
The seal in the cover must not be damaged or slipped.
The protection class IP67 can only be guaranteed when the cover is closed correctly.
Figure 3-11:
Rotary coding
switches at the
gateway
9 0 1
8
2
7
3
x 100
6 5 4
9 0 1
8
2
7
3
x 10
6 5 4
9 0 1
8
2
7
3
x1
6 5 4
000: 192.168.1.254
1 - 254: static rotary
300: BootP
400: DHCP
500: PGM
600: PGM-DHCP
900: F_Reset
t
LED behavior
During the start-up, the flashing LED "BUS" (red/green) displays that the station is waiting for address
assignment per DHCP/BOOTP/autonegotiation.
As soon as the address assignment is done, the LED flashes green and the station is ready for
communicating in the network.
D300815 0713- BL67 Multiprotocol
3-15
Properties: gateway and I/O-modules
3.5.1
Default setting of the gateway
The object provides the following control functions:
IP-address
Subnet mask
default gateway
192.168.1.254
255.255.255.0
192.168.1.1
Note
The stations can be reset by the user to these default settings at any time.
To reset the module, set the three coding-switches on the gateway to "000" followed by
apower-on reset.
Note
After every change of the address-mode, a voltage reset must be carried done.
Resetting the IP-address, switch position "000"
With this setting the DIP-switches to "000" followed by a voltage reset, the module is set to the address
192.168.1.254 for IP-based services (see Default setting of the gateway (page 3-16)).
This setting allows for example the I/O-ASSISTANT 3 (FDT/DTM) to communicate with the station, the
device's WEB-server can be accessed using the IP-address 192.168.1.254.
Note
This setting is no operation mode! Please set the device to another mode after having reset
the IP address to the default values.
3-16
D300815 0713- BL67 Multiprotocol
Address assignment
3.5.2
Address setting via rotary coding switch (rotary mode)
When using the rotary-mode, the last byte of the station’s IP address can be set via the rotary coding
switches.
Note
All other network settings are stored in the module’s non-volatile EEPROM and can not be
changed in rotary mode.
Addresses from 1 to 254 can be set. The addresses 0 and 255 are used for Broadcast-messages in the
subnet.
The following example shows the setting of address 173.
Figure 3-12:
Address setting
9 0 1
2
8
3
7
× 100
6 5 4
9 0 1
2
8
3
7
× 10
6 5 4
9 0 1
2
8
3
7
×1
6 5 4
Attention
The settings carried out in the rotary-mode are not stored in the module’s EEPROM. Thus, they
will get lost in case of a subsequent address-assignment via a BootP/ DHCP or PGM.
Attention
After changing the position of the rotary coding-switches, a voltage reset must be carried out
to store the new address.
D300815 0713- BL67 Multiprotocol
3-17
Properties: gateway and I/O-modules
3.5.3
Address setting via BootP-mode (300)
Address setting is carried out by a BootP-server in the network after the start-up of the gateway.
In order to activate the BootP-mode, the rotary coding-switches have to be set to "300".
Note
The IP address, as well as the default subnet mask assigned to the gateway by the BootPserver, are stored in the module’s EEPROM.
If the gateway is subsequently switched to rotary- or PGM-mode, the settings carried out
viaBootP (IP address, subnet mask, etc) will be read from the module’s EEPROM.
3.5.4
Address setting via DHCP-mode (400)
Address setting is carried out by a DHCP-server in the network after the start-up of the gateway (see also
Addressing via DHCP (page 12-17).
In order to activate the DHCP-mode, the rotary coding-switches have to be set to "400".
Note
The IP address, as well as the default subnet mask assigned to the gateway by the DHCPserver, are stored in the module’s EEPROM.
If the gateway is subsequently switched to rotary- or PGM-mode, the settings carried out
viaBootP (IP address, subnet mask, etc) will be read from the module’s EEPROM.
DHCP supports three mechanisms for IP address allocation:
„ In "automatic allocation", the DHCP-server assigns a permanent IP address to a client.
„ In "dynamic allocation", DHCP assigns an IP address to a client for a limited period of time. After this
time, or until the client explicitly relinquishes the address, the address can be re-assigned.
„ In "manual allocation", a client's IP address is assigned by the network administrator, and DHCP is
used simply to convey the assigned address to the client.
PROFINET
Please assure, that in PROFINET -applications, the address assigned via a BootP-server corresponds to
the address, which is assigned in the configuration tool.
3-18
D300815 0713- BL67 Multiprotocol
Address assignment
3.5.5
Address setting via PGM-mode (500)
The PGM-mode enables access of the software I/O-ASSISTANT to the module’s network settings.
In order to activate the PGM-mode, the rotary coding-switches have to be set to "500".
Note
In the PGM-mode, all network settings (IP address, subnet mask, etc.) are read from the
module’s internal EEPROM.
PROFINET
Please assure, that in PROFINET -applications, the address assigned via a I/O-ASSISTANT 3 (FDT/DTM)
corresponds to the address, which is assigned in the configuration tool.
D300815 0713- BL67 Multiprotocol
3-19
Properties: gateway and I/O-modules
3.5.6
Address setting via the mode PGM-DHCP (universal mode, 600)
In order to activate the PGM-DHCP-mode, the rotary coding-switches have to be set to "600".
The device sends DHCP-requests until it gets a permanent address.
The DHCP-client in the device is deactivated as soon as the devices gets a permanent address via the I/
O-ASSISTANT 3 (FDT/DTM), the Web-server or the PROFINET®-controller.
If the IP-address assignment is done via BOOTP/DHCP-server, the device usually gets a new IP-address
after every start-up (see also Addressing via DHCP (page 12-17)).
Permanent IP-address assignment using the Rockwell BOOTP/DHCP-server
The Rockwell BOOTP/DHCP-server can also be used to assign a permanent IP-address.
For that purpose, deactivate the DHCP-client in the respective device using "Disable BOOTP/DHCP" in
the BOOTP/DHCP-server The device stores the set IP-address even after start-up.
PROFINET®
This mode assures a PROFINET®-compliant operation of the modules.
3.5.7
F_Reset (reset to factory settings, 900)
This mode sets all device-settings back to the default values and deletes all data in the device's internal
flash.
Note
This setting is no operation mode! Please set the device to another mode after having reset
the IP address to the default values.
3-20
D300815 0713- BL67 Multiprotocol
Address assignment
3.5.8
Addressing via I/O-ASSISTANT 3 (FDT/DTM)
The software-tool I/O-ASSISTANT 3 (FDT/DTM) enables direct access to the Ethernet-network via the
Ethernet cable.
The IP address, as well as the subnet mask of the TURCK Ethernet stations, can be changed accordingto
the application by using the Busaddress Management function of the BL Service Ethernet interface
(TCP/IP) in the softwareI/O-ASSISTANT 3 (FDT/DTM).
Figure 3-13:
Busaddress
management
D300815 0713- BL67 Multiprotocol
3-21
Properties: gateway and I/O-modules
Figure 3-14:
Searching
networkNodes in the
Busaddress
management
A Search function
in the Busaddress management
A
Note
The access of the II/O-ASSISTANT 3 (FDT/DTM) to the station is only possible, if the station
already has an IP-address (see Address assignment (page 3-15)) and if it is operated in switch
position PGM or PGM-DHCP-mode.
Note
When using Windows XP as operating system, difficulties may occur with system-integrated
firewall.
It may inhibit the access of PACTware™ (I/O-ASSISTANT V3) to the Ethernet-network. In this
case, please adapt your firewall respectively or deactivate it.
3-22
D300815 0713- BL67 Multiprotocol
Address assignment
Figure 3-15:
IP address
change
D300815 0713- BL67 Multiprotocol
3-23
Properties: gateway and I/O-modules
3.5.9
Address assignment via Web server (only VN ≥ 03-00)
The device's network settings can be changed under "Network Configuration" only by users having
administrator rights.
Further information concerning the web server of the FGEN-devices and it's use can be found under
Web server - remote access/ configuration (only VN ³ 03-00) (page 3-25).
Note
The access of the IO-ASSISTANT to the station is only possible, if the station already has an IPaddress, Address assignment (page 3-15).
and if it is operated in switch position PGM or PGM-DHCP-mode.
Figure 3-16:
Web server with
Network
Configuration
3-24
D300815 0713- BL67 Multiprotocol
Web server - remote access/ configuration (only VN ³ 03-00)
3.6
Web server - remote access/ configuration (only VN ≥ 03-00)
3.6.1
IP address
Open the web server by entering the device's IP-address in your web browser.
IF no IP-address is assigned to the device (DHCP-, BootP-server etc.), then the web server can be opened
using the default IP-address 192.168.1.254.
3.6.2
Access rights
Without administrator rights, data as general product data and diagnosis data are read only.
In order to achieve administrator rights, please log-on to the web server, see Login / password (page
3-26).
Figure 3-17:
Web server of
the BL67-station
D300815 0713- BL67 Multiprotocol
3-25
Properties: gateway and I/O-modules
3.6.3
Login / password
Login to the web server by using the default-password "password".
The default-password can be changed by the administrator at every time under Change Admin
Password (page 3-28) .
Note
A reset of the device to the default-settings using the switch position
900 "F_Reset" also causes a reset of the password to "password".
Figure 3-18:
Web server
"Home" screen
3.6.4
Network Configuration
On the "Network Configuration"-page, network-relevant settings can be changed.
Figure 3-19:
Web server
"Network
Configuration"
3-26
D300815 0713- BL67 Multiprotocol
Web server - remote access/ configuration (only VN ³ 03-00)
3.6.5
Gateway Configuration
The "Gateway Configuration"-page serves for parameterizing the device's fieldbus interface.
Figure 3-20:
Web server
„Gateway
Configuration"
3.6.6
Station Diagnostics
Diagnostic messages of the device are displayed on the "Station Diagnostics"-page.
3.6.7
Ethernet Statistics
The page "Ethernet Statistics" shows information like the port-status, telegram and error counters etc.
The page can above all be useful for analyzing network problems.
3.6.8
Links
This page contains for example a link to the product page on the TURCK-homepage.
D300815 0713- BL67 Multiprotocol
3-27
Properties: gateway and I/O-modules
3.6.9
Change Admin Password
Please define an individual password for administrator rights.
Default-password: „password“
Note
A reset of the device to the default-settings using the switch position
"F_Reset" also causes a reset of the password to "password".
Figure 3-21:
Change Admin
Password
3-28
D300815 0713- BL67 Multiprotocol
Status and Control Word of the BL67-stations
3.7
Status and Control Word of the BL67-stations
For EtherNet/IP™ and Modbus TCP, the Status as well as the Control Word are mapped into the station's
process data.
„ EtherNet/IP™
In EtherNet/IP, the mapping can be disabled (see Gateway Class (VSC 100, 64h), and GW Status
Register (page 4-22)).
„ Modbus TCP → see Register 100Ch: Gateway status (page 6-13)
„ PROFINET → see Diagnosis in PROFINET® (page 8-4)
3.7.1
Status Word
Status
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
VO
low
VO
high
Ii
Overc.
-
I/O Cfg
Warn.
-
-
Diag
Warn
1
-
FCE
-
MB
Wdg
I/O
CFG
I/O
COM
VI
low
VI
high
Meaning of the status bits
Table 3-6:
Name
Meaning
Diag Warn
Summarized diagnosis of the device. At least one I/O-module sends active diagnosis.
I/O Cfg
Warn.
The station configuration has changed.
VO high
Load voltage too high (> 30 V DC).
VO low
Load voltage too low (< 18 V DC).
VI high
System supply voltage too high (> 30 V DC).
VI low
System supply voltage too low (< 18 V DC).
I/O COM
I/O Communication Lost Error
No Communication on the module bus.
I/O CFG
I/O CfgModified Error
The I/O-configuration has be changed and is no longer compatible.
MB Wdg
Modbus Watchdogs Error
A timeout occurred in the modbus-communication.
(only for Modbus TCP)
FCE
Force Mode Active Error
The Force Mode is activated, which means, the actual output values may no match the
ones defined and sent by the field bus.
Meaning of the
status bits
3.7.2
Control Word
The Control Word has no function at the moment, it is reserves for further use.
D300815 0713- BL67 Multiprotocol
3-29
Properties: gateway and I/O-modules
3.8
SET-button
The SET-button at the gateway serves to take-over the Current Configuration of the BL67-stationas
Required Configuration to the gateway’s non-volatile memory.
Please press the button for approx. 10 seconds in order to store the Current Configuration as Required
Configuration (reference configuration).
Note
Storing the Current Configuration via SET-Taster is necessary in EtherNet/IP™ as well as for
Modbus TCP. In PROFINET®, the Required Configuration is defined by the master.
3-30
D300815 0713- BL67 Multiprotocol
Status indicators/diagnostic messages gateway
3.9
Status indicators/diagnostic messages gateway
The gateway sends out the following diagnostic information:
„ undervoltage monitoring for system and field supply
„ monitoring of the BL67-station
„ monitoring of the internal communication via the module bus
„ monitoring of the Ethernet communication
„ monitoring of the gateway status
Diagnostics messages are indicated in two different ways:
„ via the LEDs
„ via the respective configuration software
3.9.1
Diagnostic messages via LEDs
Every BL67-gateway for Ethernet displays the following statuses via LEDs:
„ 2 LEDs for the module bus communication (module bus-LEDs):
GW and IOs
„ 1 LED for diagnostics
„ VN <03-00:
1 LEDs for the field bus communication: MS
VN ≥ 03-00:
2 LEDs for the field bus communication: ERR and BUS
„ je 2 LEDs for the Ethernet-communication LINK/ACT1 and LINK/ACT2
„ 3 LEDs for monitoring the voltage supply (system, VCC/ inputs, Vi/ outputs, Vo).
Table 3-7:
LED-displays
LED
Status
Meaning
Remedy
GW
OFF
No power supply of the CPU.
Check the system power supply
at the gateway.
green
Firmware active, gateway ready
-
green
flashing,
1 Hz
Station is in the Force Mode of
the I/O-ASSISTANT.
If LED “IOs“ red, then
firmware-download necessary
green
flashing,
4 Hz
firmware not running, hardware
error.
Replace the gateway.
red
Hardware failure
D300815 0713- BL67 Multiprotocol
3-31
Properties: gateway and I/O-modules
Table 3-7:
LED-displays
LED
Status
Meaning
GW
red
CPU not ready, VCC too low. → – Check the system power suppossible causes:
ply at the gateway and the
– too many modules at the gate- cabling.
way
– Unmount excessively mounted
– short-circuit in connected
modules.
module
– Replace the gateway, if neces– gateway hardware error.
sary.
red flashing,
1 Hz
Wink-command received
OFF
Station running
–
red
A diagnostic message from
gateway or I/O-modules is
pending.
– Check the diagnostic messages.
OFF
No power supply of the CPU.
Check the system power supply
at the gateway.
green
The modules configured corre- spond to the modules in the station, communication running.
ERR
IO
green flashing, Station is in the Force Mode of
1 Hz
the I/O-ASSISTANT.
3-32
Remedy
Deactivate the Force Mode of
the I/O-ASSISTANT.
red
– Check the system power supCPU not ready, VCC too low →
possible causes:
ply at the gateway and the
– too many modules at the gate- cabling.
way
– Unmount excessively mounted
– short-circuit in connected
modules.
module
– Replace the gateway, if neces– gateway hardware error.
sary.
red
flashing, 1 Hz
Non adaptable
– Compare the configured BL67changes in the configuration of
station and the current configthe module bus nodes.
uration.
– Check the physical BL67-station for defective or incorrectly
plugged electronic modules.
red
flashing, 4 Hz
No communication
via the module bus.
– At least one module has to be
plugged and has to be able to
communicate with the gateway.
IO
red / green
flashing, 1 Hz
The current and configured
module list do not match but
the data exchange proceeds as
normal.
– Check the physical BL67-station for pulled or new but not
planned modules.
VCC
green
Module bus and CPU OK
-
OFF
No supply of CPU or short-circuit – Check the voltage supply at the
of the module bus supply.
gateway.
D300815 0713- BL67 Multiprotocol
Status indicators/diagnostic messages gateway
Table 3-7:
LED-displays
LED
Status
Meaning
Remedy
VO
green
Supply of outputs OK
–
green,
flashing, 1 Hz
Undervoltage VO; system running.
– Check the system power supply at the gateway.
green,
flashing, 4 Hz
Overvoltage VO; system running.
OFF
No power supply.
–
green
VI OK
–
red
Short circuit or over-load at sen- – Automatic restart when
sor supply Vsens → sensor supply debugging.
is switched off.
green,
flashing, 1 Hz
Undervoltage VI; system running.
green,
flashing, 4 Hz
Overvoltage VI; system running.
OFF
No power supply.
green
Link established,100 Mbps
green,
flashing
Ethernet traffic (100 Mbps)
yellow
Link established,10 Mbps
yellow
flashing
Ethernet traffic (10 Mbps)
OFF
No Ethernet link.
green
Displays the logical connection
to a Master
green,
flashing
Gateway ready for operation
red
Gateway error:
– IP address conflict
– gateway in RESTORE-mode
– F_Reset activated
– Check the IP-addresses in the
network
– Check the position of the DIPswitches
red / green
– auto-negotiation
and / or
– waiting for DHCP- / BootPaddress assignment.
The gateway waits for IPaddress assignment. Wait for
the address assignment to be
finished.
VI
LINK/ACT1 /
LINK/ACT2
BUS
(MS)
D300815 0713- BL67 Multiprotocol
– Check the system power supply at the gateway.
– Check the system power supply at the gateway.
– Check the Ethernet-connection.
3-33
Properties: gateway and I/O-modules
3.10
Parameters of the modules
3.10.1
Digital input modules
„ BL67-4DI-PD
Table 3-8:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0
0 to 3
A default
setting
Input filter channel
0 to 3
0 = deactivate A
– input filter: 0.25 ms
1 = activate:
– input filter: 2.5 ms
1
0 to 3
digital input channel 0 to
3
0 = normal A
– input signal not inverted
1 = inverted:
– input signal inverted, conversion of the
effective signal direction for sensors
2
0, 1
operation mode group 1/ 0 = normal
2
– Input is evaluated as input
1 = open-circuit monitoring
– Module works in the mode for open-circuit
monitoring.
→ group 1 (channel 0 and 2) or
2 (channel 1 and 3)
„ BL67-8DI-PD
Table 3-9:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0
0 to 7
A default
setting
Input filter channel
0 to 7
0 = deactivate A
– input filter: 0.25 ms
1 = activate:
– input filter: 2.5 ms
1
0 to 7
digital input channel 0 to
7
0 = normal A
– input signal not inverted
1 = inverted:
– input signal inverted, conversion of the
effective signal direction for sensors
2
0, 1, 2, 3
operation mode group 1/ 0 = normal
4
– Input is evaluated as input
1 = open-circuit monitoring
– Module works in the mode for open-circuit
monitoring. → group:
1 (channel 0/4), 2 (channel 1/5),
3 (channel 2/6), 4 (channel 3/7)
3-34
D300815 0713- BL67 Multiprotocol
Parameters of the modules
3.10.2
Analog input modules
„ BL67-2AI-I (1 byte parameters per channel)
Table 3-10:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0/1
0
current mode
A default
setting
0 = 0...20 mA A
1 = 4...20 mA
1
value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
2
Diagnosis
0 = activate A
1 = deactivate
3
Channel
0 = activate A
1 = deactivate
„ BL67-2AI-V (1 byte parameters per channel)
Table 3-11:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0/1
0
voltage mode
A default
setting
0 = 0...10 V A
1 = -10...+10 V
1
value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
2
Diagnosis
0 = activate A
1 = deactivate
3
Channel
0 = activate A
1 = deactivate
D300815 0713- BL67 Multiprotocol
3-35
Properties: gateway and I/O-modules
„ BL67-2AI-PT (2 byte parameters per channel)
Table 3-12:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0/2
0
Mains suppression
A default
setting
0 = 50 Hz A
0 = 60 Hz
1
2
Value
representation
Diagnosis
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
0 = release A
1 = block
3
Channel
0 = activate A
1 = deactivate
1/3
7 to 4
element
0000 = Pt100, -200...850 °CA
0001 = Pt100, -200...150 °C
0010 = Ni100, -60...250 °C
0011 = Ni100, -60...150 °C
0100 = Pt200, -200...850 °C
0101 = Pt200, -200...150 °C
0110 = Pt500, -200...850 °C
0111 = Pt500, -200...150 °C
1000 = Pt1000, -200...850 °C
1001 = Pt1000, -200...150 °C
1010 = Ni1000, -60...250 °C
1011 = Ni1000, -60...150 °C
1100 = resistance, 0...100 Ω
1101 = resistance, 0...200 Ω
1110 = resistance, 0...400 Ω
1111 = resistance, 0...1000 Ω
0
Measurement mode
0 = 2 wire A
1 = 3 wire
3-36
D300815 0713- BL67 Multiprotocol
Parameters of the modules
„ BL67-2AI-TC (2 byte parameters per channel)
Table 3-13:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0/1
0
Mains suppression
A default
setting
0 = 50 Hz A
0 = 60 Hz
1
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
2
Diagnosis
0 = release A
1 = block
3
Channel
0 = activate A
1 = deactivate
7 to 4
D300815 0713- BL67 Multiprotocol
Element
0000 = Type K, -270...1370 °CA
0001 = Type B, +100....1820 °C
0010 = Type E, -270...1000 °C
0011 = Type J, -210...1200 °C
0100 = Type N, -270...1300 °C
0101 = Type R, -50...1760 °C
0110 = Type S, -50...1540 °C
0111 = Type T, -270...400 °C
1000 = ± 50 mV
1001 = ± 100 mV
1010 = ± 500 mV
1011 = ± 1000 mV
1100 to
11111 = reserved
3-37
Properties: gateway and I/O-modules
„ BL67-4AI-TC (1 byte parameters per channel)
Table 3-14:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0 to 3
A default
setting
0
reserved
1
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
2
Diagnosis
0 = release A
1 = block
3
Channel
0 = activate A
1 = deactivate
7 to 4
Element
0000 = Type K, -270...1370 °CA
0001 = Type B, +100....1820 °C
0010 = Type E, -270...1000 °C
0011 = Type J, -210...1200 °C
0100 = Type N, -270...1300 °C
0101 = Type R, -50...1760 °C
0110 = Type S, -50...1540 °C
0111 = Type T, -270...400 °C
1000 = ± 50 mV
1001 = ± 100 mV
1010 = ± 500 mV
1011 = ± 1000 mV
1100 = Type K, -454..2498 °F
1101 = Type J, -346...2192 °F
1110 = Type C, 0...2315°C
11111 = Type G, 0...2315°C
„ BL67-4AI-V/I (1 byte parameters per channel)
Table 3-15:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0 to 3
0
range
A default
setting
0 = 0...10 V/ 0...20 mA A
1 = -10...+10 V/ 4...20 mA
1
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
2
Diagnosis
0 = release A
1 = block
3
Channel
0 = activate A
1 = deactivate
4
Operation mode
0 = voltage A
1 = current
3-38
D300815 0713- BL67 Multiprotocol
Parameters of the modules
3.10.3
Digital output modules
„ BL67-16DO-0.1A-P
Table 3-16:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0
0
Open circuit current LSB
(channel 0 to 7)
1+2
reserved
3
Open circuit current MSB 0 to 12 A
– current below which an open circuit diag(channel 8 to 15)
nosis is generated: "Value" × 10 mA
4
Short-circuit current LSB
(channel 0 to 7)
5+6
reserved
7
Short-circuit current MSB 0 A to 12
– current above which a short-circuit diagno(channel 8 to 15)
sis is generated: "Value" × 10 mA
0
DiaOverCur
A default
setting
1
0 to 12 A
– current below which an open circuit diagnosis is generated: "Value" × 10 mA
0 A to 12
– current above which a short-circuit diagnosis is generated: "Value" × 10 mA
0 = short-circuit diagnosis off
1 = short-circuit diagnosis on A
1
DiaOpeLoa
0 = open circuit diagnosis off A
1 = open circuit diagnosis on
2 to 7
D300815 0713- BL67 Multiprotocol
reserved
3-39
Properties: gateway and I/O-modules
3.10.4
Analog output modules
„ BL67-2AO-I
Table 3-17:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0
0
current mode
A default
setting
0 = 0...20 mA A
1 = 4...20 mA
1
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
2
reserved
3
Channel
0 = activate A
1 = deactivate
4 to 7
3-40
reserved
1
Substitute value
Low byte
2
Substitute value
High byte
In Modbus, it is not possible the give out a substitute value in case of an error, see also page
6-19.
D300815 0713- BL67 Multiprotocol
Parameters of the modules
„ BL67-2AO-V
Table 3-18:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0
0
voltage mode
A default
setting
0 = 0...10 V A
1 = -10...+10 V
1
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
2
reserved
3
Channel
0 = activate A
1 = deactivate
4 to 7
reserved
1
Substitute value
Low byte
2
Substitute value
High byte
D300815 0713- BL67 Multiprotocol
In Modbus, it is not possible the give out a substitute value in case of an error, see also page
6-19.
3-41
Properties: gateway and I/O-modules
„ BL67-2AI-V (3 byte per channel)
– channel 0 = bit 0 - 2
– channel 4 = bit 3 - 5
– channel 2 = bit 6 - 8
– channel 3 = bit 9 - 11
Table 3-19:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
0/3/6/9
0 to 3
Operation mode
A default
setting
00 00 = voltage, -10 ... 10 VDC standard A
0001 = voltage, 0 ... 10 VDC standard
0010 = voltage,-10 ... 10 VDC PA (NE 43)
0011 = voltage, 0 ... 10 VDC PA (NE 43)
0100 = voltage, -10 ... 10 VDC ext. range
0101 = voltage, 0 ... 10 VDC ext. range
0110 to 1110 reserved
1111 = deactivate
4
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
5
Diagnosis
0 = release
1 = block
6+7
3-42
Behavior on module bus
error Ax
1/4/7/10
Substitute value
Low byte
2/5/8/11
Substitute value
High byte
output substitute value A
hold current value
In Modbus, it is not possible the give out a substitute value in case of an error, see also page
6-19.
D300815 0713- BL67 Multiprotocol
Parameters of the modules
3.10.5
Digital combi modules
„ BL67-4DI4DO-PD
Table 3-20:
Module parameters
A default
setting
Byte
Bit
Parameter name
Value
– Meaning
0
0 to 3
Digital input channel 0 to
3
0 = deactivate A
– input filter: 0.25 ms
1 = activate:
– input filter: 2.5 ms
1
0 to 3
digital input channel 0 to
3
0 = normal A
– input signal not inverted
1 = inverted:
– input signal inverted, conversion of the
effective signal direction for sensors
2
0 to 3
Output at overcurrent
channel 4 to 7
0 = automatic recovery A
– the output switches-on automatically after
a short-circuit
1 = controlled recovery
– The output is manually switched-off and on
again.
„ BL67-8XSG-PD
Table 3-21:
Module parameters
A default
setting
Byte
Bit
Parameter name
Value
– Meaning
0
0 to 7
input filter
channel 0 to 7
0 = deactivate A
– input filter: 0.25 ms
1 = activate:
– input filter: 2.5 ms
1
0 to 7
Digital input
channel 0 to 7
0 = normal A
– input signal not inverted
1 = inverted:
– input signal inverted, conversion of the
effective signal direction for sensors
2
0 to 7
Output at overcurrent
channel 0 to 7
0 = automatic recovery A
– the output switches-on automatically after
a short-circuit
1 = controlled recovery
– The output is manually switched-off and on
again.
3
0 to 7
output
0 = deactivate
1 = activate:
– selective activation of outputs of the module
D300815 0713- BL67 Multiprotocol
3-43
Properties: gateway and I/O-modules
3.10.6
Analog combi modules
„ BL67-2AI2AO-V/I (4 byte per channel)
– channel 0 = bit 0 - 3
– channel 1 = bit 4 - 7
Table 3-22:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
Inputs
A default
setting
0/4
0 to 3
Operation mode
00 00 = voltage, -10 ... 10 VDC standard A
0001 = voltage, 0 ... 10 VDC standard
0010 = voltage,-10 ... 10 VDC PA (NE 43)
0011 = voltage, 0 ... 10 VDC PA (NE 43)
0100 = voltage, -10 ... 10 VDC ext. range
0101 = voltage, 0 ... 10 VDC ext. range
0110 = reserved
0111 = reserved
1000 = 0 ... 20 mA Standard
1001 = 4 ... 20 mA Standard
1010 = 0 ... 20 mA PA (NE 43)
1011 = 4 ... 20 mA PA (NE 43)
1100 = 0 ... 20 mA ext. range
1101 = 4 ... 20 mA ext. range
1111 = deactivate
4
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
5
Diagnosis
0 = release
1 = block
3-44
D300815 0713- BL67 Multiprotocol
Parameters of the modules
Table 3-23:
Outputs
1/5
0 to 3
Operation mode
00 00 = voltage, -10 ... 10 VDC standard A
0001 = voltage, 0 ... 10 VDC standard
0010 = voltage,-10 ... 10 VDC PA (NE 43)
0011 = voltage, 0 ... 10 VDC PA (NE 43)
0100 = voltage, -10 ... 10 VDC ext. range
0101 = voltage, 0 ... 10 VDC ext. range
0110 to 1110 = reserved
1111 = deactivate
4
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
5
Diagnosis
0 = release
1 = block
6+7
Behavior on module bus
error Ax
2/6
Substitute value
Low byte
3/7
Substitute value
High byte
D300815 0713- BL67 Multiprotocol
output substitute value A
hold current value
In Modbus, it is not possible the give out a substitute value in case of an error, see also page
6-19.
3-45
Properties: gateway and I/O-modules
„ BL67-4AI4AO-V/I (4 byte per channel)
– channel 0 = bit 0 - 3
– channel 1 = bit 4 - 7
– channel 2 = bit 8 - 11
– channel 3 = bit 12 - 15
Table 3-24:
Module parameters
A default
setting
Byte
Bit
Parameter name
Value
0 to 3
Operation mode
00 00 = voltage, -10 ... 10 VDC standard A
Inputs
0/4/8/12
0001 = voltage, 0 ... 10 VDC standard
0010 = voltage,-10 ... 10 VDC PA (NE 43)
0011 = voltage, 0 ... 10 VDC PA (NE 43)
0100 = voltage, -10 ... 10 VDC ext. range
0101 = voltage, 0 ... 10 VDC ext. range
0110 = reserved
0111 = reserved
1000 = 0 ... 20 mA Standard
1001 = 4 ... 20 mA Standard
1010 = 0 ... 20 mA PA (NE 43)
1011 = 4 ... 20 mA PA (NE 43)
1100 = 0 ... 20 mA ext. range
1101 = 4 ... 20 mA ext. range
1111 = deactivate
4
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
5
Diagnosis
0 = release
1 = block
3-46
D300815 0713- BL67 Multiprotocol
Parameters of the modules
Table 3-24:
Module parameters
Byte
Bit
Parameter name
Value
0 to 3
Operation mode
00 00 = voltage, -10 ... 10 VDC standard A
Outputs
1/5/9/13
0001 = voltage, 0 ... 10 VDC standard
0010 = voltage,-10 ... 10 VDC PA (NE 43)
0011 = voltage, 0 ... 10 VDC PA (NE 43)
0100 = voltage, -10 ... 10 VDC ext. range
0101 = voltage, 0 ... 10 VDC ext. range
0110 to 1110 = reserved
1111 = deactivate
4
Value representation
0 = Integer (15 bit + sign) A
1 = 12 bit (left-justified)
5
Diagnosis
0 = release
1 = block
6+7
Behavior on module bus
error Ax
2/6/10/14
Substitute value
Low byte
3/7/11/15
Substitute value
High byte
D300815 0713- BL67 Multiprotocol
output substitute value A
hold current value
In Modbus, it is not possible the give out a substitute value in case of an error, see also page
6-19.
3-47
Properties: gateway and I/O-modules
3.10.7
Technology modules
„ BL67-1RS232
Table 3-25:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
A default
setting
0
3 to 0
Data rate
0000 = 300 bps
0001 = 600 bps
0010 = 1200 bps
0100 = 2400 bps
0101 = 4800 bps
0110 = 9600 bps A
0111 = 14400 bps
1000 = 19200 bps
1001 = 28800 bps
1010 = 38400 bps
1011 = 57600 bps
1100 = 115200 bps
...
reserved
5.4
reserved
-
6
DisableReducedCtrl
Constant setting:
The diagnostic messages are shown in Byte 6
of the process input data (independently from
“Diagnosis").
Byte 6 of the process output data contains 2
bits, with which the receive or transmit buffer
can be cleared.
Byte 7 contains the status or control byte. User
data are represented in Bytes 0 - 5.
7
Diagnosis
0 = release A
1 = block
1
0
Stop bits
0 = 1 bit A
1 = 2 bit
2.1
Parity
00 = none
01 = odd A
– The parity bit is set so that the total number
of bits (data bits plus parity bit) set to 1 is
odd.
10 = even
– The parity bit is set so that the total number
of bits (data bits plus parity bit) set to 1 is
even.
3-48
D300815 0713- BL67 Multiprotocol
Parameters of the modules
Table 3-25:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
A default
setting
1
3
Data bits
0=7A
– The number of data bits is 7.
1+8
– The number of data bits is 8.
5.4
Data flow control
00 = none A
– Data flow control is switched off.
01 = XON/XOFF
– Software handshake (XON/XOFF) is
switched on.
10 = RTS/CTS
– Hardware handshake (RTS/CTS) is switched
on.
7.6
reserved
2
XON character
This character is used to start the transmission
of data from the data terminal device if the
software handshake is active.
3
XOFF character
This character is used to stop the transmission
of data from the data terminal device if the
software handshake is active.
D300815 0713- BL67 Multiprotocol
3-49
Properties: gateway and I/O-modules
„ BL67-1RS485/422
Table 3-26:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
A default
setting
0
3 to 0
Data rate
0000 = 300 bps
0001 = 600 bps
0010 = 1200 bps
0100 = 2400 bps
0101 = 4800 bps
0110 = 9600 bps A
0111 = 14400 bps
1000 = 19200 bps
1001 = 28800 bps
1010 = 38400 bps
1011 = 57600 bps
1100 = 115200 bps
...
reserved
4
Select RS485
0 = parameterization of the module as RS422
1 = parameterization of the module as RS485
5
reserved
6
DisableReducedCtrl
Constant setting:
The diagnostic messages are shown in Byte 6
of the process input data (independently from
“Diagnosis").
Byte 6 of the process output data contains 2
bits, with which the receive or transmit buffer
can be cleared.
Byte 7 contains the status or control byte. User
data are represented in Bytes 0 - 5.
7
Diagnosis
0 = release A
1 = block
1
0
Stop bits
0 = 1 bit A
1 = 2 bit
2.1
Parity
00 = none
01 = odd A
– The parity bit is set so that the total number
of bits (data bits plus parity bit) set to 1 is
odd.
10 = even
– The parity bit is set so that the total number
of bits (data bits plus parity bit) set to 1 is
even.
3-50
D300815 0713- BL67 Multiprotocol
Parameters of the modules
Table 3-26:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
A default
setting
1
3
Data bits
0=7A
– The number of data bits is 7.
1+8
– The number of data bits is 8.
„ BL67-1SSI
Table 3-27:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
A default
setting
0
1
4 to 0
reserved
5
Sensor
data cable
test
7.6
reserved
3 to 0
Number of
invalid bits
(LSB)
D300815 0713- BL67 Multiprotocol
0 = activate A
– ZERO test of data cable.
1 = deactivate
– After the last valid bit, a ZERO test of the
data cable is not carried out.
0000 to 1111:
Number of invalid bits on the LSB side of the
position value supplied by the SSI encoder.
The meaningful word width of the position
value transferred to the module bus master is
as follows:
SSI_FRAME_LEN -INVALID_BITS_MSBINVALID_BITS_LSB.
The invalid bits on the LSB side are removed
by shifting the position value to the right,
starting with the LSB.
(Default 0 bit = 0×0).
INVALID_BITS_MSB +INVALID_BITS_LSB must
always be less than SSI_FRAME_LEN.
3-51
Properties: gateway and I/O-modules
Table 3-27:
Module parameters
Byte
Bit
Parameter name
Value
– Meaning
A default
setting
1
2
3
6 to 4
Number of
invalid bits
(MSB)
7
reserved
3 to 0
Data rate
7 to 4
reserved
5 to 0
Number of
data frame bits
6
reserved
7
Data type
000 to 111
Number of invalid bits on the LSB side of the
position value supplied by the SSI encoder.
The meaningful word width of the position
value transferred to the module bus master is
as follows:
SSI_FRAME_LEN - INVALID_BITS_MSB INVALID_BITS_LSB.
Number of invalid bits on the MSB side of the
position value supplied by the SSI encoder.
INVALID_BITS_MSB +INVALID_BITS_LSB must
always be less than SSI_FRAME_LEN.
Default: 0 = 0hex
0000 = 1000000 bps
0001 = 500000 bps A
0010 = 250000 bps
0011 = 125000 bps
0100 = 100000 bps
0101 = 83000 bps
0110 = 71000 bps
0111 = 62500 bps
...
reserved
00000 to 100000
Number of bits of the SSI data frame.
SSI_FRAME_LEN must always be greater than
INVALID_BITS.
Default: 25 = 19hex
binary coded A
– SSI encoder sends data in binary code
GRAY coded
– SSI encoder sends data in GRAY code
3-52
D300815 0713- BL67 Multiprotocol
Parameters of the modules
„ BL67-1CVI
Table 3-28:
parameters
BL67-1CVI
Parameter name
Meaning
CfgNode 1
Configuration of the first connected node
(seeTable 3-29:)
...
Table 3-29:
CfgNode 8
Configuration of the eighth connected node
(seeTable 3-29:)
GuardTime
Setting the guard time in
steps of 100ms (default 3 = 300ms)
(default 3 = 300ms)
Life Time Factor
Default 3
Config
Different configuration settings (see Table 3-30:)
Bit
Parameter name
Configuration possibilities of the
CANopen-Nodes
Value
– Meaning
0
NodeActive
0 = inactive/ not present A
1 = active
1
NodeGuarding
0 = inactive A
1 = active
Node guarding is activated.
2 to 4
InLen
000 = 0 bit A
001 = 4 bit
010 = 8 bit
011 = 12 bit
100 = 16 bit
101 = 24 bit
110 = 32 bit
111 = reserved
5 to 7
OutLen
000 = 0 bit A
001 = 4 bit
010 = 8 bit
011 = 12 bit
100 = 16 bit
101 = 24 bit
110 = 32 bit
111 = reserved
D300815 0713- BL67 Multiprotocol
3-53
Properties: gateway and I/O-modules
Table 3-30:
Configuration
possibilities for
CANopen
3-54
Bit
Parameter name
Value
– Meaning
0 to 2
Baud rate
000 = 1000k
001 = reserved
010 = 500k
011 = 250k
100 = 125k A
101 = 50k
110 = 20k
111 = 10k
3
Termination
0 = no terminating resistor A
1 = terminating resistor active
– Activation of the terminating resistor.
4 to 7
reserved
D300815 0713- BL67 Multiprotocol
Parameters of the modules
„ BL67-1CNT/ENC
Table 3-31:
Byte
Parameters of the
BL67-1CNT/ENC
A Default
setting
0
Parameter name
0 +1
Input filter (A, B)
00 = 500 kHz A
01 = 50 kHz
10 = 5 kHz
11 = reserved
2+3
Signal evaluation (A,
B)
00 = 1 x: rising edge at A
01 = 1 x: falling edge at A
10 = 2 x: both edges at A A
11 = 4 x: both edges at A and B
4
Count direction
0 = up A
1 = down
5
reserved
6
Input B
0 = normal A
7
Input A
0 = normal A
1 = inverted
1
0
PullUp Z
0 = off A
1 = on
1
Function DI3
0 = input A
1 = encoder-GND
2
Function DO3
0 = output A
1 = encoder power supply
3
Encoder signal
0 = Push-pull input A
1 = RS422-input
4
reserved
5
Synchronization with
Z
0 = singleA
Input Z
0 = normal A
1 = periodical
6
7
D300815 0713- BL67 Multiprotocol
3-55
Properties: gateway and I/O-modules
Table 3-31:
Byte
Parameters of the
BL67-1CNT/ENC
Parameter name
2
3
0-2
Threshold input A, B,
Z
0000 = 1V
0001 = 1.5 V
0010 = 2 V
0011 = 2.5 V
0100 = 3 V
0101 = 4 V
0110 = 5 V
0111 = 6 V
1000 = 7 V
1001 = 8 V
1010 = 9 V
1011 = 10 V A
1100 = 12 V
1101 = 14 V
1110 = 16 V
1111 = 18 V
Gate function
000 = Counter permanently inactive
001 = DI0 is HW-gate
010 = DI1 is HW-gate
011 = DI2 is HW-gate
100 = DI3 is HW-gate
101 = Z is gate
100 = only SW-gate A
111 = reserved
3
Gate
0 = normal A
4
Count mode
0 = encoder A
1 = pulse and direction
5
Measurement mode
0 = frequency measurement A
1 = period duration measurement
3-56
4 - 13
reserved
14
REG_AUX_ADR
15
reserved
0 to 127
Default: 48
D300815 0713- BL67 Multiprotocol
Diagnostic messages of the modules
3.11
3.11.1
Diagnostic messages of the modules
Power distribution modules
„ BL67-PF-24VDC
Table 3-32:
BL67-PF-24VDC
Diagnostic Bit
byte
n
3.11.2
Diagnosis
0
Undervoltage VI
1
Undervoltage VO
2
overcurrent sensor II(current consumption too high)
Digital input modules
„ BL67-4DI-PD
Table 3-33:
BL67-4DI-PD
Diagnostic Bit
byte
n
n+1
Diagnosis
0
Overcurrent sensor 1 (channel 0)
1
Overcurrent sensor 2 (channel 1)
2
Overcurrent sensor 3 (channel 2)
3
Overcurrent sensor 4 (channel 3)
0
open circuit K1 (channel 0 and 2)
1
open circuit K2 (channel 1 and 3)
„ BL67-8DI-PD
Table 3-34:
BL67-8DI-PD
Diagnostic Bit
byte
n
n+1
Diagnosis
0
Overcurrent sensor 1 (sensor supply A)
1
Overcurrent sensor 2 (sensor supply B)
2
Overcurrent sensor 3 (sensor supply C)
3
Overcurrent sensor 4 (sensor supply D)
0
open circuit K1 (channel 0 and 4)
1
open circuit K2 (channel 1 and 5)
2
open circuit K 3 (channel 2 and 6)
3
open circuit K4 (channel 3 and 7)
D300815 0713- BL67 Multiprotocol
3-57
Properties: gateway and I/O-modules
3.11.3
Analog input modules
„ BL67-2AI-I
Table 3-35:
BL67-2AI-I
Diagnostic Bit
byte
A only detected
n
when the cur(channel 0)
rent range is set
from 4to 20 mA
n+1
(channel 1)
Diagnosis
0
measurement value range error A
1
Open circuit
0
measurement value range error A
1
Open circuit
„ BL67-2AI-V
Table 3-36:
BL67-2AI-V
Diagnostic Bit
byte
Diagnosis
n
(channel 0)
0
Measurement value range error
n+1
(channel 1)
0
Measurement value range error
„ BL67-2AI-PT
Table 3-37:
BL67-2AI-PT
Diagnostic Bit
byte
A threshold:
n
1% of the posi- (channel 0)
tive measurement range end
value
B threshold:
5 Ω (loop resistance)
n+1
(channel 1)
3-58
Diagnosis
0
measurement value range error A
(Underflow diagnostics in temperature measurement ranges only)
1
Open circuit
2
Short circuit B
(in temperature measurement ranges only)
0 to 7
identical to channel 0
D300815 0713- BL67 Multiprotocol
Diagnostic messages of the modules
„ BL67-2AI-TC
Table 3-38:
BL67-2AI-TC
Diagnostic Bit
byte
A threshold:
n
1 % of the positive measurement range end
value
B threshold:
5 Ω (loop resistance)
n+1
(channel 1)
Diagnosis
0
Measurement value range error
1
Open circuit B
(in temperature measurement ranges only)
3
No Pt1000 sensor found (cold junction compensation)
4 to 7
reserved
0 to 7
identical to channel 0
D300815 0713- BL67 Multiprotocol
3-59
Properties: gateway and I/O-modules
„ BL67-4AI-TC
Table 3-39:
BL67-2AI-TC
Diagnostic Bit
byte
A threshold:
n
1 % of the positive measurement range end
value
B threshold:
5 Ω (loop resistance)
Diagnosis
0
Measurement value range error
1
Open circuit B
(in temperature measurement ranges only)
2
No Pt1000 sensor found (cold junction compensation)
3
Common Mode voltage out of range, channel 0 and 1 (explanation see
below)
4 to 6
reserved
7
Hardware failure
n+1
(channel 1)
0 to 7
identical to channel 0
n+2
(channel 2)
0
Measurement value range error
1
Open circuit B
(in temperature measurement ranges only)
2
No Pt1000 sensor found (cold junction compensation)
3
Common Mode voltage out of range, channel 2 and 3 (explanation see
below)
4 to 6
reserved
7
Hardware failure
0 to 7
identical to channel 2
n+3
(channel 3)
Common Mode voltage out of range
Potential difference between measurement voltages too high.
Monitoring of the potential difference between the measurement voltages within one sensor group
(sensor groups: channel 0/1 or channel 2/3).
Remedy:
– Check the isolation of the sensors.
– In case of non- insulated sensors, check the potential equalization between the sensors.
–
3-60
If non-insulated sensors are used, it can be necessary to connect the sensors to channels
of different sensor groups (i.e. channel 1 and channel 3).
D300815 0713- BL67 Multiprotocol
Diagnostic messages of the modules
„ BL67-4AI-V/I
Table 3-40:
BL67-4AI-V/I
3.11.4
Diagnostic Bit
byte
Diagnosis
n
(channel 0)
0
Measurement value range error
n+x
(channel 1
to 3)
0
Measurement value range error
Digital output modules
„ BL67-4DO-xA-P
Table 3-41:
Diagnostic Bit
BL67-4DO-0.5A-P byte
n
Diagnosis
0
overcurrent (short-circuit channel 0)
1
overcurrent (short-circuit channel 1)
2
overcurrent (short-circuit channel 2)
3
overcurrent (short-circuit channel 3)
„ BL67-8DO-0.5A-P
Table 3-42:
Diagnostic Bit
BL67-8DO-0.5A-P byte
n
Diagnosis
0
overcurrent (short-circuit channel 0)
1
overcurrent (short-circuit channel 1)
2
overcurrent (short-circuit channel 2)
3
overcurrent (short-circuit channel 3)
4
overcurrent (short-circuit channel 4)
5
overcurrent (short-circuit channel 5)
6
overcurrent (short-circuit channel 6)
7
overcurrent (short-circuit channel 7)
D300815 0713- BL67 Multiprotocol
3-61
Properties: gateway and I/O-modules
„ BL67-16DO-0.1A-P
Table 3-43:
Diagnostic Bit
BL67-16DO-0.1A-P byte
n
n+1
Diagnosis
0
Short-circuit or/ and open circuit channel 0
1
Short-circuit or/ and open circuit channel 1
...
...
6
Short-circuit or/ and open circuit channel 6
7
Short-circuit or/ and open circuit channel 7
0
Short-circuit or/ and open circuit channel 8
1
Short-circuit or/ and open circuit channel 9
...
...
6
Short-circuit or/ and open circuit channel 14
7
Short-circuit or/ and open circuit channel 15
„ BL67-4DO-2A-N
Table 3-44:
BL67-4DO-2A-N
Diagnostic Bit
byte
Diagnosis
n
0
overcurrent (short-circuit channel 0)
1
overcurrent (short-circuit channel 1)
2
overcurrent (short-circuit channel 2)
3
overcurrent (short-circuit channel 3)
„ BL67-8DO-0.5A-N
Table 3-45:
Diagnostic Bit
BL67-8DO-0.5A-N byte
n
3-62
Diagnosis
0
overcurrent (short-circuit channel 0)
1
overcurrent (short-circuit channel 1)
2
overcurrent (short-circuit channel 2)
3
overcurrent (short-circuit channel 3)
4
overcurrent (short-circuit channel 4)
5
overcurrent (short-circuit channel 5)
6
overcurrent (short-circuit channel 6)
7
overcurrent (short-circuit channel 7)
D300815 0713- BL67 Multiprotocol
Diagnostic messages of the modules
3.11.5
Analog output modules
„ BL67-4AO-V
– channel 0: Byte 0 (inputs) + byte 1 (outputs)
– channel 1: Byte 2 (inputs) + byte 3 (outputs)
Table 3-46:
BL67-4AO-V
Diagnostic Bit
byte
n
(channel 0)
3.11.6
Diagnosis
0
Measurement value range error
1
reserved
2
reserved
3
Owerflow/Underflow
4-6
reserved
7
Hardware failure
n+1
Channel 1 identical to channel 0
n+2
Channel 2 identical to channel 0
n+3
Channel 3 identical to channel 0
Digital combi modules
„ BL67-4DI4DO-PD
Table 3-47:
Diagnostic Bit
BL67-4DI4DO-PD byte
n
n+1
Diagnosis
0
Overcurrent sensor 1 (input 0)
1
Overcurrent sensor 2 (input 1)
2
Overcurrent sensor 3 (input 2)
3
Overcurrent sensor 4 (input 3)
0
Overcurrent K1 (output 0)
1
Overcurrent K2 (output 1)
2
Overcurrent K3 (output 2)
3
Overcurrent K4 (output 3)
D300815 0713- BL67 Multiprotocol
3-63
Properties: gateway and I/O-modules
„ BL67-8XSG-PD
Table 3-48:
BL67-8XSG-PD
Diagnostic Bit
byte
Diagnosis
n
0
Overcurrent sensor 1 (sensor supply A)
1
Overcurrent sensor 2 (sensor supply B)
2
Overcurrent sensor 3 (sensor supply C)
3
Overcurrent sensor 4 (sensor supply D)
0
Overcurrent K1 (channel 0)
1
Overcurrent K2 (channel 1)
2
Overcurrent K3 (channel 2)
3
Overcurrent K4 (channel 3)
4
Overcurrent K5 (channel 4)
5
Overcurrent K6 (channel 5)
6
Overcurrent K7 (channel 6)
7
Overcurrent K8 (channel 7)
n+1
3-64
D300815 0713- BL67 Multiprotocol
Diagnostic messages of the modules
3.11.7
Analog combi modules
„ BL67-2AI2AO-V/I
– channel 0: Byte 0 (inputs) + byte 1 (outputs)
– channel 1: Byte 2 (inputs) + byte 3 (outputs)
Table 3-49:
BL67-2AI2AO-V/I
Diagnostic Bit
byte
Diagnosis
Inputs
A A wire break
0/2
diagnosis is only
possible in the
operation mode
4 to 20 mA.
0
Measurement value range error
1
Wire break A
2
reserved
3
Owerflow/Underflow
4-6
reserved
7
Hardware failure
0
Measurement value range error
1
reserved
2
reserved
3
Owerflow/Underflow
4-6
reserved
7
Hardware failure
Outputs
1/3
D300815 0713- BL67 Multiprotocol
3-65
Properties: gateway and I/O-modules
„ BL67-4AI4AO-V/I
– channel 0: Byte 0 (inputs) + byte 1 (outputs)
– channel 1: Byte 2 (inputs) + byte 3 (outputs)
– channel 2: Byte 4 (inputs) + byte 5 (outputs)
– channel 3: Byte 6 (inputs) + byte 7 (outputs)
Table 3-50:
BL67-4AI4AO-V/I
Diagnostic Bit
byte
Diagnosis
Inputs
A A wire break
0/2/4/6
diagnosis is only
possible in the
operation mode
4 to 20 mA.
0
Measurement value range error
1
Wire break A
2
reserved
3
Owerflow/Underflow
4-6
reserved
7
Hardware failure
0
Measurement value range error
1
reserved
2
reserved
3
Overflow/Underflow
4-6
reserved
7
Hardware failure
Outputs
1/3/5/7
3-66
D300815 0713- BL67 Multiprotocol
Diagnostic messages of the modules
3.11.8
Technology modules
„ BL67-1RS232
Table 3-51:
BL67-1RS232
Diagnostic Bit
byte
Diagnosis
n
3
Parameterization error
4
Hardware failure
5
Data flow control error
6
frame error
7
buffer overflow
„ BL67-1RS485/422
Table 3-52:
Diagnostic Bit
BL67-1RS485/422 byte
n
Diagnosis
3
Parameterization error
4
Hardware failure
5
Data flow control error
6
frame error
7
buffer overflow
„ BL67-1SSI
Table 3-53:
BL67-1SSI
Diagnostic Bit
byte
Diagnosis
n
0
SSI group diagnostics
1
Open circuit
2
sensor value overflow
3
sensor value underflow
4
Parameterization error
D300815 0713- BL67 Multiprotocol
3-67
Properties: gateway and I/O-modules
„ BL67-1CVI
Table 3-54:
Diagnostic data
BL67-1CVI
Table 3-55:
Diagnostic data
CANopen-node
(DiagNode x)
Table 3-56:
Global diagnosis
CVI-module
(DiagCVI)
3-68
Diagnostic Bit
byte
Name
n
0 to 3
DiagNode1 (see Table 3-55:)
4 to 7
DiagNode 2 (see Table 3-55:)
...
...
...
n+3
0 to 3
DiagNode 7 (see Table 3-55:)
4 to 7
DiagNode 8 (see Table 3-55:)
n+4
DiagCVI (see Table 3-56:)
n+5
reserved
Bit
Name
0
Emergencies transmitted since module start.
1
Node transmitted emergencies
2
Communication error transmitted since module start/ Guard Time
3
Communication error/Guard Time timeout
Bit
Name
0
Emergencies transmitted since module start.
1
Node address not within permissible range (1-8)
2
Overcurrent VC (valve power supply)
3
Overcurrent VE (valve electronic power supply)
D300815 0713- BL67 Multiprotocol
Diagnostic messages of the modules
„ BL67-1CNT/ENC
Table 3-57:
Diagnosis of the
BL67-1CNT/ENC
Diagnostic
byte
Bit
Name
Meaning
0
0
STS_UFLW
Underflow
Counter value below lower limit of counter range.
1
STS_OFLW
Overflow
Counter value exceeded upper limit of counter range.
2-6
reserved
7
ERR_PARA
Parameter error
Faulty/ inconsistent parameter data.
0
DIA_DO0
Short circuit or overload at output x
1
DIA_DO1
2
DIA_DO2
3
DIA_DO3
4-7
reserved
1
2-7
D300815 0713- BL67 Multiprotocol
reserved
3-69
Properties: gateway and I/O-modules
3-70
D300815 0713- BL67 Multiprotocol
4
Implementation of EtherNet/IP
4.1
The EtherNet/IP Communications Profile ......................................................................................... 2
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
I/O Messages........................................................................................................................................ 2
Explicit Messages................................................................................................................................. 2
Communications profile of the BL67-gateway ..................................................................................... 2
– Unicast .............................................................................................................................................. 2
– Multicast ........................................................................................................................................... 2
– COS I/O Connection ......................................................................................................................... 3
– Cyclic I/O Connection ...................................................................................................................... 3
– UCMM .............................................................................................................................................. 3
– Connected Explicit Messaging ......................................................................................................... 3
Summarized Diagnostics...................................................................................................................... 4
Scheduled Diagnostics......................................................................................................................... 4
4.2
Classes and Instances of the EtherNet/IP-stations............................................................................ 5
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
EtherNet/IP Standard Classes.............................................................................................................. 5
Identity Object (0x01)............................................................................................................................ 6
Assembly Object (0x04)........................................................................................................................ 8
– Process data instances .................................................................................................................... 9
– Mapping of process data ............................................................................................................... 10
TCP/IP Interface Object (0xF5)........................................................................................................... 11
Ethernet Link Object (0xF6) ................................................................................................................ 15
DLR Object (0x47) .............................................................................................................................. 18
QOS Object (0x48).............................................................................................................................. 19
4.3
VSC-Vendor Specific Classes ........................................................................................................... 20
4.3.1
4.3.2
Class instance of the VSC .................................................................................................................. 20
Gateway Class (VSC 100, 64h)........................................................................................................... 21
– Class instance ................................................................................................................................ 21
– Object Instance 1 ........................................................................................................................... 21
– Object Instance 2 ........................................................................................................................... 22
Process Data Class (VSC102, 66h) .................................................................................................... 24
– Class instance ................................................................................................................................ 24
– Object instance 1, standard input process data (compressed) .................................................... 24
– Object Instance 3, diagnostic instance ......................................................................................... 25
– Object Instance 4, COS/CYCLIC instance ..................................................................................... 25
Miscellaneous Parameters Class (VSC 126)....................................................................................... 26
– Instance 1 (port 1)/ Instance 2 (port 2) ........................................................................................... 26
4.3.3
4.3.4
D300815 0713- BL67 Multiprotocol
4-1
Implementation of EtherNet/IP
4.1
The EtherNet/IP Communications Profile
EtherNet/IP is based on a connection-oriented communication model. his means that it is only possible
to exchange data via specified connections assigned to the devices.
Communication between the nodes in the EtherNet/IP network can be carried out either via I/O
Messages or Explicit Messages.
4.1.1
I/O Messages
I/O Messages serve to exchange high priority process and application data over the network.
Communication between the slaves in the EtherNet/IP network is carried out according to the Server/
Client Model,
which means a producing application transmits data to another or a number of consuming
applications. It is quite possible that information is passed to a number of Application Objects in a
single device.
4.1.2
Explicit Messages
Explicit Messages are used to transmit low-priority configuration data, general management data or
diagnostic data between two specific devices. This is a point-to-point connection in a Server/Client
System that requires a request from a client always to be confirmed by a response from the server.
„ Message Router Request
Consists of a service code, path size value, a message router path and service data. An EPATH is used
in the message router path to indicate the target object.
„ Message Router Response
Consists of a service field with the most significant bit set. This is an echo of the service code in the
request message with the most significant bit set. A reserved byte follows the service code, which is
followed by the General Status code.
4.1.3
Communications profile of the BL67-gateway
The EtherNet/IP gateway behaves as an EtherNet/IP Server in the network; the scanner of the higherlevel controller operates as a EtherNet/IP Client.
The following EtherNet/IP communications types are supported:
„ Unicast
„ Multicast
„ Cyclic Connection
„ Unconnected (UCMM) Explicit Messaging
„ Connected Explicit Messaging
Unicast
A point-to-point connection that exists between two nodes only.
Multicast
A packet with a special destination address, which multiple nodes on the network may be willing to
receive.
4-2
D300815 0713- BL67 Multiprotocol
The EtherNet/IP Communications Profile
COS I/O Connection
COS (Change Of State) I/O Connections establish event-controlled connections. This means that the
EtherNet/IP devices generate messages as soon as a change of status occurs.
Cyclic I/O Connection
Messages are triggered time-controlled in Cyclic I/O connections by means of a time generator.
UCMM
The EtherNet/IP gateway offers the option of establishing explicit messaging via the UCMM port
(Unconnected Message Manager Port).
UCMM-based explicit messaging is normally used for random, non-periodic requests.
It is not recommended for frequent messaging because the UCMM input queue in a product is typically
limited to just a few messages. Once this limit is reached, subsequent requests are ignored and must
be retried.
Connected Explicit Messaging
CIP is a connection-based system. For most communications between nodes, a connection is used.
A connection is a path or a virtual circuit between two or more end points in a system. The purpose is
to transfer data in the most efficient manner possible.
The Connection ID is a number that is associated with a communication relationship. Receiving nodes
decode this key to know whether they must accept the data or not.
Besides the evaluation of diagnostic data via Explicit Messages, BL67 with EtherNet/IP offers the
possibility of mapping diagnostic data into the process data (see also the stations‘ process data
mappings (page 4-10 ff.).
2 different forms of diagnostic data handling are provided:
„ summarized diagnostics
„ Scheduled Diagnostics
4.1.4
Summarized Diagnostics
The summarized diagnostic data mode will send back 1 bit for each slice within the station.
This bit will be "0" if there are no diagnostic flags set on the slice. If there are any diagnostic events on
the device, the bit will be set to "1".
The diagnostic bits are placed at the end of the input data. The diagnostic data start WORD aligned (see
page 4-10).
Bit „I/O Diag Warn“
0 = OK, no diagnostics present
at least one module sends diagnostics (acc. to VSC 100, Gateway Class, Attr. 116, page 4-21)
4.1.5
Scheduled Diagnostics
If scheduled diagnostics is activated (Process Data Class (VSC102, 66h) (page 4-24)), the manufacturer
specific diagnostic bits are mapped into the station's process data (page 4-4 ff.).
The scheduled diagnostic data is placed at the end of the input data and after the summarized
diagnostic data (see page 4-10).
The scheduled diagnostic data is a time sliced module related data block, which holds diagnostic data
of all modules with active diagnostics using a round robin mechanism.
D300815 0713- BL67 Multiprotocol
4-3
Implementation of EtherNet/IP
This diagnostic "window" visualizes a specific module diagnostic data for approx. 125 ms and changes
over to the next active diagnostics afterwards. This is done automatically by the gateway.
The data length for the scheduled diagnostics is set according to properties of the modules attached to
the gateway.
word-
Byte
Data
0
0
slot-no. of the module which sends an emergency-frame.
1
Status process release:
bit 5 = 1: diagnostic active
bit 6 = 1: wrong module
bit 7 = 1 Module pulled
(acc. to VSC 100, Gateway Class, Attr. 116, page 4-21)
n
4-4
Module diagnostics from the module actually referenced by the roundrobin mechanism.
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
4.2
4.2.1
Classes and Instances of the EtherNet/IP-stations
EtherNet/IP Standard Classes
The BL67-stations support the following EtherNet/IP Standard Classes in accordance with the CIP
specification.
Table 4-1:
EtherNet/IP™
Standard Classes
Class Code
Object name
01 (0x01)
Identity Object (0x01)
04 (0x04)
Assembly Object (0x04)
245 (0xF5)
TCP/IP Interface Object (0xF5)
246 (0xF6)
Ethernet Link Object (0xF6)
71 (0×47)
DLR Object (0x47)
72 (0×48)
QOS Object (0x48)
D300815 0713- BL67 Multiprotocol
4-5
Implementation of EtherNet/IP
4.2.2
Identity Object (0x01)
The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev. 2.1
by ODVA & ControlNet International Ltd. and adapted to BL67.
Class Attributes
Table 4-2:
Class Attributes
Attr. No.
Attribute name
Get/
Set
Type
Value
1 (0x01)
REVISION
G
UINT
1
2 (0x02)
MAX OBJECT INSTANCE
G
UINT
1
6 (0x06)
MAX CLASS ATTRIBUTE
G
UINT
7
7 (0x07)
MAX INSTANCE ATTRIBUTE
G
UINT
7
Object-instance 1 - instance attributes
Table 4-3:
Instance attributes, objectinstance 1
Attr. No.
Attribute name
Get/ Type
Set
Description
1 (0x01)
VENDOR
G
UINT
Contains the vendor ID.
TURCK = 48
2 (0x02)
PRODUCT TYPE
G
UINT
Indicates the general type of product.
Communications Adapter
12dez = 0x0C
3 (0x03)
PRODUCT CODE
G
UINT
Identifies a particular product within a device
type.
Default: 27247dec = 6A6F
4 (0x04)
REVISION
G
STRUCT
OF:
USINT
USINT
Revision of the item the Identity Object is
representing.
0x01
0x06
Major Minor
5 (0x05)
DEVICE STATUS
G
WORD
see Table 4-4: Device Status
6 (0x06)
SERIAL NUMBER
G
UDINT
Contains the ident-no. of the product (3 last
bytes of the MAC-ID).
7 (0x07)
PRODUCT NAME
G
STRUCT
OF:
LENGTH
NAME
4-6
USINT
STRING
[13]
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
Device Status
Table 4-4:
Device Status
Bit
Name
Definition
0 to 1
reserved
Default = 0
2
Configured
TRUE = 1
→ The application of the device has been configured
(≠ default-settings).
3
reserved
Default = 0
4 to 7
Extended Device
Status
0011 = no I/O connection established
0110 = At least one I/O connection in run mode
0111 = At least one I/O connection established, all in IDLE
mode
All other settings = reserved
8 to 15
reserved
Default = 0
Common Services
Table 4-5:
Service code
Common services
Class
Instance
Service name
01 (0x01)
yes
yes
Get_Attribute_All
Returns a predefined list of the object‘s attributes.
05 (0x05)
no
yes
Reset
Starts the reset service for the device.
14 (0x0E)
yes
yes
Get_Attribute_Single
Returns the contents of a specified attribute.
D300815 0713- BL67 Multiprotocol
4-7
Implementation of EtherNet/IP
4.2.3
Assembly Object (0x04)
Assembly Objects bind attributes of multiple objects to allow data to or from each object to be sent or
received over a single connection.
The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev. 2.1
by ODVA & ControlNet International Ltd. and adapted to BL67.
Class Attributes
Table 4-6:
Class Attributes
Attr. No.
Attribute name
Get/
Set
Type
Value
1 (0x01)
REVISION
G
UINT
2
2 (0x02)
MAX OBJECT INSTANCE
G
UINT
104
Instance Attributes
Table 4-7:
Instance
attribute
Attr. No.
Attribute name
Get/ Type
Set
3 (0x03)
DATA
S
ARRAY OF
BYTE
4 (0x04)
SIZE
G
UINT
Description
UINT Number of bytes in attr. 3
256 or variable
Common Services
Table 4-8:
Service code
Common services
14 (0x0E)
4-8
Class
Instance
Service name
no
yes
Get_Attribute_Single
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
Process data instances
Instance 101
Contains the station’s input data (static length 256 bytes).
2 Bytes status information (see page 3-29)
+ process data
Instance 102
Contains the station’s output data (static length 256 bytes).
2 Bytes Control data (mapped, but not defined)
+ process data
Instance 103 und Instance 104
In- and output assembly instances with variable assembly sizes. The assembly size is pre-calculated to
support the stations I/O-configuration, enabled diagnostics, etc.
„ input assembly instance: 103
„ output assembly instance: 104
The effective size of the Assembly Instance can be determined using the Assembly Object (instance
0×67, attribute 0x04) and can be from 2 to 496 bytes large.
D300815 0713- BL67 Multiprotocol
4-9
Implementation of EtherNet/IP
Mapping of process data
The process data image of the BL67-gateways is depicted in WORD-format (16 bit).
The process data of successive modules of the same type, with process data of less than 1 word, are
grouped together until 16 bits of process data is reached.
The process data is written in a new word when:
„ 16-bit input data is reached and further input modules follow
„ 16-bit output data is reached and further output modules follow
„ An input module, whose process data length cannot be completely incorporated in the preceding
word, follows on from another input module
„ An output module, whose process data length cannot be completely incorporated in the preceding
word, follows on from another output module16-bit input data is reached and further input
modules follow
Table 4-9:
Produced Data
Data mapping for (word no.)
BL67-GW-EN
Input data
0
Status Word of the gateway
Mapping can be disabled using attr. 138 in VSC100, object instance
2, page 4-21)
1 to n
Input data of modules
An example mapping can be found in chapter 5.3, I/O data
mapping (page 5-10).
n+x
Summarized diagnostic data (page 4-4) of individual length (1 bit
per module which sends diagnostics).
Can be enabled/disabled using VSC102, Object instance 3, attr.
104, page 4-24 ff.
(x = the no. of following bytes depending on the no. of slices within
the station)
n+y
Scheduled diagnostic data (page 4-4).Can be enabled/disabled
using VSC102, Object instance 3, attr. 105, page 4-24 ff.
(y = data length for the scheduled diagnostics set according to the
properties of the modules attached to the gateway)
Consumed Data
(word no.)
Output data
0
Control word of the gateway. The mapping can be disabled using
attribute 139 "GW CONTROL REGISTER" in the Gateway Class (VSC
100), object instance 2 (see page 4-23).
1- n
Output data of modules
An example mapping can be found in chapter 5, I/O data mapping
(page 5-10).
Note
The data mapping can be structured individually. All parts except for the in- and out-put data
of the station can be enabled/ disabled independently from each other.
4-10
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
4.2.4
TCP/IP Interface Object (0xF5)
The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev. 1.1
by ODVA & ControlNet International Ltd. and adapted to BL67.
Class Attributes
Table 4-10:
Class Attributes
Attr. No.
Attribute name
Get/
Set
Type
Value
1 (0x01)
REVISION
G
UINT
1
2 (0x02)
MAX OBJECT INSTANCE
G
UINT
1
3 (0x03)
NUMBER OF INSTANCES
G
UINT
1
Object instance 1: instance attribute
Table 4-11:
Instance attributes, objectinstance 1
Attr. No.
Attribute name
Get/ Type
Set
Description
1 (0x01)
STATUS
G
DWORD
Interface status (see page 4-12, Table 4-13:
Interface Status)
2 (0x02)
CONFIGURATION
CAPABILITY
G
DWORD
Interface Capability Flag (see page 4-12, Table
4-14: Configuration Capability)
3 (0x03)
CONFIGURATION
CONTROL
G/S
DWORD
Interface Control Flag (see page 4-13, Table 415: Configuration Control)
4 (0x04)
PHYSICAL LINK
OBJECT
G
STRUCT
5 (0x05)
6 (0x06)
Path size
UINT
Number of 16bit words: 0x02
Path:
Padded
EPATH
0x20, 0xF6, 0x24, 0x01
INTERFACE
CONFIGURATION
G
Structure
of:
TCP/IP Network Interface Configuration (see
page 4-13)
IP address
G
UDINT
Current IP address
NETWORK MASK
G
UDINT
Current network mask
GATEWAY ADDR.
G
UDINT
Current default gateway
NAME SERVER
G
UDINT
0 = no name server address configured
NAME SERVER 2
G
UDINT
0 = no secondary name server address
configured
DOMAIN NAME
G
UDINT
0 = no Domain Name configured
HOST NAME
G
STRING
0 = no Host Name configured (see page 4-13)
D300815 0713- BL67 Multiprotocol
4-11
Implementation of EtherNet/IP
Table 4-11:
Instance attributes, objectinstance 1
Attr. No.
Attribute name
Get/ Type
Set
Description
10 (0x0A)
ACD Enable
S
BOOL
Activates ACD (Address Conflict Detection)
0 = deactivated
1 = activated
If ACD is activated, attribute 11 (0x0B) contains
the return value.
11(0x0B)
Last Conflict
detected
G/S
STRUCT
of:
Contains information about the last detected
conflict, ACD diagnostics parameter
12 (0x0C)
Quick Connect
G/S
BOOL
0 = deactivate
1 = activate
Common Services
Table 4-12:
Service code
Common services
Class
Instance
Service name
14 (0x0E)
yes
yes
Get_Attribute_Single
16 (0x10)
no
yes
Set_Attribute_Single
„ Interface Status
The Status attribute indicates the status of the TCP/IP network interface.
Refer to the state diagram, Figure 4-1: TCP/IP object state diagram (acc. to CIP Spec., Vol.2, Rev. 1.1)
for a description of object states as they relate to the Status attribute.
Table 4-13:
Interface Status
Bit(s)
Name
Definition
0-3
Interface Configuration
Status
Indicates the status of the Interface Configuration attribute:
0 = The Interface Configuration attribute has not been
configured
1 = The Interface Configuration attribute contains valid
configuration.
2 to 15: reserved
4 to 31
reserved
„ Configuration Capability
The Configuration Capability indicates the device’s support for optional network configuration
capability.
Table 4-14:
Configuration
Capability
4-12
Bit(s)
Name
Definition
Value
0
BOOTP Client
The device is capable of obtaining its
network configuration via BOOTP.
1
1
DNS Client
The device is capable of resolving host
names by querying a DNS server.
0
2
DHCP Client
The device is capable of obtaining its
network configuration via DHCP.
1
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
„ Configuration Control
The Configuration Control attribute is used to control network configuration options.
Table 4-15:
Configuration
Control
Bit(s)
Name
Definition
0-3
Startup
Configuration
Determines how the device shall obtain its initial configuration
at
0 = The device shall use the interface configuration values
previously stored (for example, in non-volatile memory or via
hardware switches, etc).
1 to 3: reserved
4
DNS Enable
Always 0.
5-31
reserved
Set to 0.
„ Interface Configuration
This attribute contains the configuration parameters required to operate as a TCP/IP node.
To modify the Interface Configuration attribute, get the Interface Configuration attribute first,
change the desired parameters, then set the attribute.
The TCP/IP Interface Object applies the new configuration upon completion of the Set service. If the
value of the Startup Configuration bits (Configuration Control attribute) is 0, the new configuration
is stored in non-volatile memory.
The device does not reply to the set service until the values are safely stored to non-volatile memory.
An attempt to set any of the components of the Interface Configuration attribute to invalid values
results in an error (status code 0x09) returned from the Set service.
If initial configuration is obtained via BOOTP or DHCP, the Interface Configuration attribute
components are all 0 until the BOOTP or DHCP reply is received.
Upon receipt of the BOOTP or DHCP reply, the Interface Configuration attribute shows the
configuration obtained via BOOTP/DHCP.
„ Host Name
The Host Name attribute contains the device’s host name.
The host name attribute is used when the device supports the DHCP-DNS Update capability and has
been configured to use DHCP upon start up.
The mechanism allows the DHCP client to transmit its host name to the DHCP server. The DHCP
server then updates the DNS records on behalf of the client.
D300815 0713- BL67 Multiprotocol
4-13
Implementation of EtherNet/IP
Figure 4-1:
TCP/IP object
state diagram
(acc. to CIP Spec.,
Vol.2, Rev. 1.1)
Non-existent
Powerup/ Reset
Status =
0×00000000
Obtaining initial
configuration
BOOTP/DHCP
disabled and
stored config. valid
BOOTP OR
DHCP enabled
BOOTP/DHCP
disabled and
stored config.
valid
Waiting
for
configuration
Set_Attributes
request received
Status =
0×00000000
BOOTP/DHCP
response received
Applying
configuration
Configuration applied
Change interface
configuration
4-14
TCP/IP network
interface configured
Status = 0×00000001
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
4.2.5
Ethernet Link Object (0xF6)
The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev. 1.1
by ODVA & ControlNet International Ltd. and adapted to BL67.
Class Attributes
Table 4-16:
Class Attributes
Attr. No.
Attribute name
Get/
Set
Type
Value
1 (0x01)
REVISION
G
UINT
1
2 (0x02)
MAX OBJECT INSTANCE
G
UINT
1
3 (0x03)
NUMBER OF INSTANCES
G
UINT
1
Instance attributes (instance 1 = port 1/ instance 2 = port 2)
Table 4-17:
Instance attributes
Table 4-18:
Interface flags
Attr. No.
Attribute name
Get/ Type
Set
Description
1 (0x01)
INTERFACE SPEED
G
UDINT
Speed in megabits per second
(e.g., 10, 100, 1000, etc.)
2 (0x02)
INTERFACE FLAGS
G
DWORD
see Table 4-18: Interface flags
3 (0x03)
PHYSICAL
ADDRESS
G
ARRAY OF
USINT
Contains the interface’s MAC address
(TURCK: 00:07:46:××:××:××)
6 (0x06)
INTERFACE
CONTROL
S
STRUCT OF: Allows port-wise changes of the Ethernetsettings
Control Bits
WORD
Table 4-19: Interface control - Control bits
Forced Interface
Speed
UINT
Table 4-19: Interface control - Control bits
7 (0x07)
INTERFACE TYPE
10 (0x0A)
INTERFACE LABEL
Bits
Name
Definition
Default value
0
Link Status
Indicates whether or not the Ethernet
802.3 communications interface is
connected to an active network.
0 = inactive link
1 = active link.
Depends on
application
1
Half / Full Duplex
0 = half duplex;
1 = full duplex
If the Link Status flag is 0, the value of the
Half/Full Duplex flag is indeterminate.
Depends on
application
D300815 0713- BL67 Multiprotocol
4-15
Implementation of EtherNet/IP
Table 4-18:
Interface flags
4-16
Bits
Name
Definition
Default value
2 to 4
Negotiation Status
Indicates the status of the automatic
duplex-negotiation (auto-negotiation)
0 = Auto-negotiation in progress
1 = Auto-negotiation and speed detection
failed.
Using default values for speed and duplex
(10Mbps/half duplex).
2 = Auto negotiation failed but detected
speed (default: half duplex). Half duplex
3 = Successfully negotiated speed and
duplex.
4 = Auto-negotiation not attempted.
Forced speed and duplex.
Depends on
application
5
Manual Setting
Requires Reset
0 = interface can activate changes to link
0
parameters (auto-negotiate, duplex mode,
interface speed) automatically
1 = device requires a Reset service to be
issued to its Identity Object in order to
adapt the changes
6
Local Hardware Fault
0 = interface detects no local hardware
fault
1 = a local hardware fault is detected
0
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
Table 4-19:
Bits
Interface control Control bits
Name
Definition
0
Auto-negotiate
0 = Autonegotiation deactivated
1 = Autonegotiation activated
1
Forced Duplex Mode
If bit "Auto-negotiate" is 0, bit "Forced
Duplex Mode" shows if the interface
should work in Full or Half Duplex-mode.
0 = Half Duplex
1 = Full Duplex
Interfaces which do not support the
selected Duplex-mode, send an error code
0x09 (Invalid Attribute Value).
If auto-negotiation is enabled, attempting
to set the Forced Duplex Mode bits shall
result in a error code 0x0C (Object State
Conflict).
2-15
reserved
Default value
Depends on
application
Forced Interface Speed
If the Auto-negotiate bit is 0, the "Forced Interface Speed" bits indicate the speed at which the interface
shall operate. Speed is specified in megabits per second (e.g., for 10 Mbps Ethernet, the Interface Speed
shall be 10).
Interfaces not supporting the requested speed should return a error code 0x09 (Invalid Attribute
Value).
If auto-negotiation is enabled, attempting to set the Forced Interface Speed bits shall result in a error
code 0x0C (Object State Conflict).
Common Services
Table 4-20:
Common
services
Service code
Class
Instance
Service name
14 (0x0E)
yes
yes
Get_Attribute_Single
16 (0x10)
no
yes
Set_Attribute_Single
D300815 0713- BL67 Multiprotocol
4-17
Implementation of EtherNet/IP
4.2.6
DLR Object (0x47)
The Device Level Ring (DLR) Object provides the configuration and status information interface for the
DLR protocol. The DLR protocol enables the use of an Ethernet ring topology.
Class Attributes
Table 4-21:
Class Attributes
Attr. No.
Attribute name
Get/
Set
Type
Value
1 (0x01)
REVISION
G
UINT
1
Instance attributes
Table 4-22:
Instance attributes
Attr. No.
Attribute name
Get/ Type
Set
Description
1 (0x01)
NETWORK
TOPOLOGY
G
USINT
Current network topology mode
0 = linear
1 = ring
2 (0x02)
NETWORK
STATUS
G
USINT
status of the gateway network
0 = normal
1 = ring-error
2 = Unexpected Loop Detected
10 (0x0A)
ACTIVE
SUPERVISOR
ADDR.
G
STRUCT of:
IP and/or MAC address of the active ring
supervisor
12 (0x0C)
CAPABILITY
FLAGS
G
DWORD
Describes the DLR capabilities of the device
0 = Announce-based Ring Node
Common Services
Table 4-23:
Common
services
4-18
Service code
Class
Instance
Service name
14 (0x0E)
yes
yes
Get_Attribute_Single
D300815 0713- BL67 Multiprotocol
Classes and Instances of the EtherNet/IP-stations
4.2.7
QOS Object (0x48)
Quality of Service (QoS) is used for prioritizing or parameterizing of the data transmission of a device.
Each change is only accepted after a power-cycle of the device.
The DSCP-value is part of the EtherNet/IP-data telegram and is used to define data priorities in data
handling.
Instance attributes
Table 4-24:
Instance attributes
Attr. No.
Attribute name
Get/ Type
Set
Description
4 (0x04)
DSCP Urgent
S
USINT
DSCP value for CIP transport class 0/1 Urgent
priority messages
5 (0x05)
DSCP Scheduled
S
USINT
DSCP value for CIP transport class 0/1
Scheduled priority messages
6 (0x06)
DSCP High
S
USINT
DSCP value for CIP transport class 0/1 High
priority messages
07 (0x07)
DSCP Low
S
USINT
DSCP value for CIP transport class 0/1 Low
priority messages
08 (0x08)
DSCP Explicit
S
USINT
DSCP value for CIP explicit messages
(transport class 2/3 and UCMM)
Common Services
Table 4-25:
Common
services
Service code
Class
Instance
Service name
14 (0x0E)
yes
yes
Get_Attribute_Single
16 (0x10)
no
yes
Set_Attribute_Single
D300815 0713- BL67 Multiprotocol
4-19
Implementation of EtherNet/IP
4.3
VSC-Vendor Specific Classes
In addition to supporting the above named CIP Standard Classes, the BL67-stations support the vendor
specific classes described in the following.
Table 4-26:
VSC-Vendor
Specific Classes
4.3.1
Class Code Name
Description
dec.
(hex.)
100 (64h)
Gateway Class, page 4-21
Contains data and settings concerning the
fieldbus-specific part of the BL67-stations.
102 (66h)
Process Data Class, page 4-24
Contains process data
126 (1Ah)
Miscellaneous Parameters Class, page 4-26 Describes the EtherNet/IP™-Port
properties
Class instance of the VSC
Note
The class instance attributes are the same for each Vendor Specific Class.
The class-specific Object Instances and the corresponding attributes are explained in the
paragraphs for the different VSC.
The general VSC - class instance attributes are defined as follows.
Table 4-27:
Class instance
4-20
Attr. No.
Attribute name
Get/ Type
Set
Description
100
(64h)
Class revision
G
UINT
States the revision number of the class
(maj. rel. *1000 + Min. Rel.).
101
(65h)
Max. instance
G
USINT
Contains the number of the highest instance
of an object created on this level in the class
hierarchy.
102
(66h)
# of instances
G
USINT
Contains the number of Object Instances
created in this class.
103
(67h)
Max. class
attribute
G
USINT
Contains the number of the last Class
Attribute to be implemented.
dec.
(hex.)
D300815 0713- BL67 Multiprotocol
VSC-Vendor Specific Classes
4.3.2
Gateway Class (VSC 100, 64h)
This class contains all information which refers to the whole station not to the different
I/O channels.
Class instance
Note
Please refer to paragraph Class instance of the VSC (page 4-20) for the description of the class
instance for the VSC.
Object Instance 1
Table 4-28:
Object Instance 1
Boot instance
Attr. No.
Attribute name
Get/ Type
Set
Description
100
(64h)
Max object
attribute
G
USINT
Contains the number of the last object
attribute to be implemented.
101
(65h)
Hardware revision G
STRUCT
Contains the hardware revision number of the
station (USINT Maj./USINT Min.)
102
(66h)
Firmware revision
G
STRUCT
Contains the revision number of the Boot
Firmware (Maj./Min.).
103
(67h)
Service tool ident
number
G
UDINT
Contains the BOOT ID number that serves as
an identification number for the software I/OASSISTANT
104
(68h)
Hardware
info
G
STRUCT
Contains station hardware information (UINT):
– count (number of the following entries)
– CLOCK FREQUENCY (kHz)
– MAIN FLASH (in kB)
– MAIN FLASH SPEED (ns)
– SECOND FLASH (kB)
– RAM (kB),
– RAM SPEED (ns),
– RAM data WIDTH (bit),
– SERIAL EEPRPOM (kbit)
– RTC SUPPORT (in #)
– AUTO SERVICE BSL SUPPORT (BOOL)
– HDW SYSTEM
dec.
(hex.)
D300815 0713- BL67 Multiprotocol
4-21
Implementation of EtherNet/IP
Object Instance 2
Table 4-29:
Attr. No.
Object instance 2,
gateway instance dec.
Attribute name
Get/ Type
Set
Description
109
(6Dh)
Status register 2
G
STRUCT
The Status Word contains general station
status information:
Station
– Bit 15: reserved
– Bit 14: "Force Mode Active Error" The Force
Mode is activated.
– Bit 13: reserved
– Bit 12: reserved
Internal bus
– Bit 11: "I/O Cfg Modified Error"
The configuration has been changed in an
incompatible way.
– Bit 10: "I/O Communication Lost Error"
Communication on the internal module bus
disturbed.
Voltage errors
– Bit 09: "Usys too low" System voltage (VI) too
low (< 18 VDC).
– Bit 08: "Usys too low" System voltage (VI) too
low (< 18 VDC).
– Bit 07: "UL too low" Load voltage (VO) too low
(< 18 VDC).
– Bit 06: reserved
– Bit 05: reserved
– Bit 04: reserved
Warnings
– Bit 03: "I/O Cfg Modified Warning" The station
configuration has changed.
– Bit 02: reserved
– Bit 01: reserved
– Bit 00: "I/O Diags Active Warning" At least one
I/O-channel sends active diagnostics.
115
(73h)
ON IO
CONNECTION
TIMEOUT
G/S
ENUM
USINT
Reaction to the I/O connection exceeding the
time limit.
SWITCH IO FAULTED (0):
The modules are switched to Faulted State.
SWITCH IO OFF (1):
The gateway switches off the outputs of the
modules.
SWITCH IO HOLD (2):
No further changes to the I/O-data. The
outputs are held.
138
(0x8A)
GW Status
Register
Get/
Set
DWORD
Allows to enable/disable the status register
which is part of the input data.
0 = deactivated
1 = activated (default)
(hex.)
4-22
D300815 0713- BL67 Multiprotocol
VSC-Vendor Specific Classes
Table 4-29:
Attr. No.
Object instance 2,
gateway instance dec.
Attribute name
Get/ Type
Set
Description
139
(0x8B)
GW Control
Register
Get/
Set
DWORD
Allows to enable/disable the control register
which is part of the output data.
0 = deactivated
1 = activated (default)
140
(0x8C)
Disable Protocols
Get/
Set
UINT
Deactivate the other Ethernet-protocols, if
necessary:
0 = EtherNet/IP (can not be disabled via
EtherNet/IP™-interface)
Bit 1 = Modbus/TCP
Bit 2 = PROFINET
Bit 15 = web server
(hex.)
D300815 0713- BL67 Multiprotocol
4-23
Implementation of EtherNet/IP
4.3.3
Process Data Class (VSC102, 66h)
This class contains the process-relevant information.
Class instance
Note
Please refer to paragraph Class instance of the VSC, page 4-20 for the description of the class
instance for the VSC.
Object instance 1, standard input process data (compressed)
Table 4-30:
Attr. No.
Object instance 1,
dec. (hex.)
standard input
process data
(compressed)
Attribute name
Get/
Set
Type
Description
100 (64h)
Max object
attribute
G
USINT
Contains the number of the last object
attribute to be implemented.
101 (65h)
Attribute list
G
ARRAY OF
USINT
List of all attributes that are supported by
this instance.
102 (66h)
Packed process
input data
G
ARRAY OF
WORD
Input process data, 16-bit aligned,
compressed.
103 (67h)
Process data byte
count
G
USINT
The number of bytes that are exchanged
with this Instance.
Object instance 2, standard output process data (compressed)
Table 4-31:
Attr. No.
Object instance 2,
dec. (hex.)
standard output
process data
100 (64h)
(compressed)
4-24
Attribute name
Get/
Set
Type
Description
Max object
attribute
G
USINT
Contains the number of the last object
attribute to be implemented.
101 (65h)
Attribute list
G
ARRAY OF
USINT
List of all attributes that are supported by
this Instance.
102 (66h)
Packed process
input data
G/S
ARRAY OF
WORD
Output process data, 16-bit aligned,
compressed.
103 (67h)
Process data byte
count
G
USINT
The number of bytes that are exchanged
with this Instance.
D300815 0713- BL67 Multiprotocol
VSC-Vendor Specific Classes
Object Instance 3, diagnostic instance
Table 4-32:
Attr. No.
Object Instance 3,
dec. (hex.)
diagnostic
instance
Attribute name
Get/ Set Type
Description
104 (68h)
GW
summarized
diagnostics
G/S
BOOL
0 = disabled
1 = active
1 bit of diagnosis mapped at the end of the
input data image ( page 4-4).
Changes become valid after a start-up!
105 (69h)
GW
manufacturer
specific
diagnostics
(scheduled
diagnostics)
G/S
BOOL
0 = disabled
1 = active
The channel-specifc diagnostic bits are
mapped into the process input data (see
page 4-4).
Changes become valid after a start-up!
106 (6Ah)
reserved
-
Object Instance 4, COS/CYCLIC instance
Table 4-33:
Attr. No.
Object Instance 4,
dec.
COS/CYCLIC
(hex.)
instance
104 (68h)
Attribute name
Get/
Set
Type
Description
COS data
mapping
G/S
ENUM
USINT
The actual data are loaded to the nonvolatile memory of the station.
Changes become valid after a start-up!
0 = standard: Data of COS message
→ input data.
1 = process input data (only the process
data input image is transferred to scanner)
2 to 7: reserved
D300815 0713- BL67 Multiprotocol
4-25
Implementation of EtherNet/IP
4.3.4
Miscellaneous Parameters Class (VSC 126)
Instance 1 (port 1)/ Instance 2 (port 2)
Table 4-34:
Object Instance
Adefault
setting
4-26
Attr. No.
Attribute name
Get/
Set
Type
Description
109 (6Dh)
Ethernet port
parameters
G/S
DWORD
0 = Autonegotiate, AutoMDIX A
1 = 100BaseT, half duplex, linear topology
(AutoMDIX disabled)
2 = 10BaseT, full duplex, linear topology
(AutoMDIX disabled)
3 = 100BaseT, half duplex, linear topology
(AutoMDIX disabled)
4 = 100BaseT, full duplex, linear topology
(AutoMDIX disabled)
112 (70h)
IO controller
software revision
G
DWORD
The number of instances of this parameter
depends on the number of I/O controllers.
dec.
(hex.)
D300815 0713- BL67 Multiprotocol
5
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
5.1
General.............................................................................................................................................. 2
5.1.1
Used hard-/ software............................................................................................................................ 2
– Hardware ........................................................................................................................................... 2
– Software ............................................................................................................................................ 2
5.2
Network configuration ..................................................................................................................... 3
5.2.1
5.2.2
Configuration of the network in "RS Logix 5000"................................................................................. 3
– Configuration of the controller........................................................................................................... 3
– Configuration of the EtherNet/IP Bridge............................................................................................ 4
– Configuring the BL67-station ............................................................................................................ 5
Downloading the I/O configuration....................................................................................................... 8
5.3
I/O data mapping ............................................................................................................................ 10
5.4
Process data access ......................................................................................................................... 12
5.4.1
5.4.2
Setting outputs ................................................................................................................................... 12
Example program ............................................................................................................................... 13
D300815 0713- BL67 Multiprotocol
5-1
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
5.1
General
The following example shows detailed information about the connection of a BL67-station for
EtherNet/IP to an Allen Bradley PLC.
5.1.1
Used hard-/ software
Hardware
Hardware used in this example:
„ Allen Bradley Controller 1756-L30 Logix5572
„ Allen Bradley EtherNet/IP-Bridge1756 EN2TR
„ BL67-GW-EN (> VN 03-00, IP: 192.168.1.112)
– Slot 1: BL67-8XSG-PD
– Slot 2: BL67-8DI-PD
– Slot 3: BL67-2AO-I
– Slot 4: BL67-8DO-0.5A-P
– Slot 5: BL67-4AI-V/I
– Slot 6: BL67-4DO-2A-P
Software
Software used in this example:
„ RS Logix 5000 - used to configure the controller and the other network hosts
5-2
D300815 0713- BL67 Multiprotocol
Network configuration
5.2
Network configuration
BL67-stations are delivered in the address-mode "PGM-DHCP" and can be reached using IP-address
192.168.1.254 .
Note
In order to build up the communication between the BL67-station and a PLC/ PC or a network
interface card, both devices have to be hosts in the same network.
To achieve this, you have either:
„ to adjust the gateway‘s IP address via BootP, DHCP etc. for integrating it into your own network (for
detailed information about the different possibilities for address setting, please read chapter 3.5,
Address assignment (page 3-15), .
or
„ to change the IP address of the used PC or network interface card (for detailed information, please
read the , Changing the IP address of a PC/ network interface card (page 12-12).
5.2.1
Configuration of the network in "RS Logix 5000"
The EtherNet/IP hosts (PLC, EtherNet/IP interface, I/O stations) have to be configured using the software
"RSLogix 5000" (in this example version 15) from Rockwell Automation.
Start RS Logix and open a new project using the "File" menu.
Configuration of the controller
1 Enter the information related to the controller depending on your configuration, as well as a name
for the project.
Figure 5-1:
Configuration of
the controller
2 Your project will be opened offline.
D300815 0713- BL67 Multiprotocol
5-3
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
Configuration of the EtherNet/IP Bridge
1 Open the context menu by right-clicking "Backplane, 1756-A10" and select "New Module" in order
to add the Bridge to the network.
2 Select the appropriate EtherNet/IP-Bridge, in this example "1756-EN2TR" and so add an EtherNet/IPinterface to the controller.
Figure 5-2:
Add EtherNet/IPBridge
3 Enter the necessary device properties (name, IP-address etc.) in the dialog box which is opened.
Figure 5-3:
EtherNet/IPBridge properties
5-4
D300815 0713- BL67 Multiprotocol
Network configuration
Configuring the BL67-station
4 Open the context menu by right-clicking "Ethernet" and select "New Module" in order to add the
BL67-station to the network.
5 Open the entry "Generic Ethernet Module" to configure the station.
Figure 5-4:
Add Generic
Ethernet module
6 Enter the necessary device information, like "Module name" and "Communication format" and
define the station‘s IP-address and the connection parameters.
7 In the Assembly Instances 103 and 104, please enter the connection parameters of the station.
Figure 5-5:
Configuring the
BL67station
D300815 0713- BL67 Multiprotocol
5-5
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
Note
If the variable Assembly Instances 103 and 104 (see page 4-8) are used, the Connection
Parameters have to be set according to the actual station configuration.
That means:
The in- and output sizes have to match the sizes definitely required by the station.
This required in- and output size can be determined as follows:
Create a station report for the station using the TURCK DTMs for BLxx (see also Figure 5-6:
EtherNet/IP™-report (PLC-configuration) (page 5-6))
OR
Read out the correct size of in- and output data via Assembly Class (0×04), Instance 0×67, Attr.
0x04 and Assembly Class (0x04), Instance 0x68, Attr. 0x04.
Figure 5-6:
EtherNet/IP™report (PLCconfiguration)
AData to enter
assembly
instances in RS
Logix
A
8 In the "Connection" tab set the "Requested Packet Interval" (RPI) to 10 ms, which normally should
be the default setting. For BL67, the RPI should be set to 5 ms or higher.
Figure 5-7:
Set connection
options for the
gateway
5-6
D300815 0713- BL67 Multiprotocol
Network configuration
9 The station is now added to the project tree.
Figure 5-8:
Project tree with
stations
D300815 0713- BL67 Multiprotocol
5-7
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
5.2.2
Downloading the I/O configuration
1 If the configuration of the network is completed, it can be downloaded to the controller by using for
example the "Communication → Download" command.
2 In the "Download" dialog box, start the download by pressing the "Download" button.
Figure 5-9:
Download of the
configuration
3 If an error message is generated, warning, that the communication path can not be found, please
open the "Path" menu (see Figure 5-10:), select your controller and press "Set Project Path" (see
Figure 5-11:).
Figure 5-10:
Communication
path
Figure 5-11:
Communication
path
4 If the correct communication path is set, it is possible to download the configuration.
5-8
D300815 0713- BL67 Multiprotocol
Network configuration
5 Once the I/O configuration is downloaded and the controller is in "Run" or "Remote Run" mode, the
I/O-data mapping of the BL67-stations is shown in the "Controller Tags":
Figure 5-12:
Controller Tags
The controller tags are divided into:
„ xxx: C - the station’s mapped configuration data
„ xxx: I - the station’s mapped input data
„ xxx: O - the station’s mapped output data
D300815 0713- BL67 Multiprotocol
5-9
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
5.3
I/O data mapping
Each station is now accessible via the controller tags for viewing input data and/or forcing outputs.
The data mapping depends on process data mappings of the configured BL67-modules (see chapter 4,
Assembly Object (0x04), Mapping of process data (page 4-10) ff.).
The detailed station data mapping can be found in the EtherNet/IP™-report, generated using the BL××PACTware-DTM.
Figure 5-13:
EtherNet/IP™report with data
mapping
5-10
D300815 0713- BL67 Multiprotocol
I/O data mapping
For the example station, the mapping in RS Logix looks as follows:
Figure 5-14:
Mapping of the
BL67station
D300815 0713- BL67 Multiprotocol
5-11
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
5.4
5.4.1
Process data access
Setting outputs
Example:
In order to set outputs "0" and "1" at slot 6 of the station (BL67-4DO-2A-P, see example station), bit 0
and bit 1 in data word 4 (BL67_GW_EN:I.Data [4]) have to be set (see above Figure 5-11:I/O data
mapping (page 5-10)).
Figure 5-15:
Setting outputs at
BL67-4DO-2A-P
5-12
D300815 0713- BL67 Multiprotocol
Process data access
5.4.2
Example program
Figure 5-16:
Example
program
1 The counter counts upwards.
2 The counter value is mapped to the outputs of the two digital output modules in the station (slot 4
and slot 6).
D300815 0713- BL67 Multiprotocol
5-13
Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)
3 The counter is set to „0“ by setting the variable „xReset“ (BOOL) to „1“.
„xReset“ has been defined and mapped to Bit BL67_E_GW_EN:I.Data[1].11 by building an Alias in
the Main Program.
Figure 5-17:
Definition and
mapping of
xReset
5-14
D300815 0713- BL67 Multiprotocol
6
Implementation of Modbus TCP
6.1
Common Modbus description........................................................................................................... 2
6.1.1
6.1.2
Protocol description ............................................................................................................................. 3
Data model ........................................................................................................................................... 4
6.2
Implemented Modbus functions....................................................................................................... 5
6.3
Modbus-registers.............................................................................................................................. 6
6.4
Structure of the packed in-/ output process data ........................................................................... 10
6.4.1
6.4.2
Packed input process data................................................................................................................. 10
– Status/ diagnosis............................................................................................................................. 11
Packed output process data .............................................................................................................. 11
6.5
Data width of the I/O-modules in the modbus-register area .......................................................... 12
6.5.1
6.5.2
6.5.3
6.5.4
6.5.5
Register 100Ch: "Gateway status"..................................................................................................... 13
Register 1130h: „Modbus-Connection-Mode“................................................................................... 14
Register 1131h: „Modbus-Connection-Timeout“............................................................................... 14
Register 0x113C and 0x113D: „Restore Modbus-Connection-Parameters” ..................................... 14
Register 0x113E and 0x113F: „Save Modbus-Connection-Parameters“ .......................................... 14
6.6
The Service-Object .......................................................................................................................... 15
– Indirect reading of registers............................................................................................................. 16
– Indirect writing of registers .............................................................................................................. 17
6.7
Bit areas: mapping of input-discrete- and coil-areas ...................................................................... 18
– Data mapping in the input-discrete- and coil-areas........................................................................ 18
6.8
Output module behavior in case of an error ................................................................................... 19
D300815 0713- BL67 Multiprotocol
6-1
Implementation of Modbus TCP
6.1
Common Modbus description
Note
The following description of the Modbus protocol is taken from the Modbus Application
Protocol Specification V1.1 of Modbus-IDA.
Modbus is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides
client/server communication between devices connected on different types of buses or networks.
The industry’s serial de facto standard since 1979, Modbus continues to enable millions of automation
devices to communicate. Today, support for the simple and elegant structure of Modbus continues to
grow.
The Internet community can access Modbus at a reserved system port 502 on the TCP/IP stack.
Modbus is a request/reply protocol and offers services specified by function codes. Modbus function
codes are elements of Modbus request/reply PDUs (Protocol Data Unit).
It is currently implemented using:
„ TCP/IP over Ethernet. (that is used for the BL67 Modbus gateways and described in the following)
„ Asynchronous serial transmission over a variety of media (wire: RS232, RS422, RS485, optical: fiber,
radio, etc.)
„ Modbus PLUS, a high speed token passing network.
Schematic representation of the Modbus Communication Stack (according to Modbus Application
Protocol Specification V1.1 of Modbus-IDA):
Figure 6-1:
Schematic representation of the
Modbus Communication Stack
Modbus Application Layer
Modbus TCP
TCP
IP
6-2
andere
Modbus plus
Master/Slave
Client/Server
Physical layer
Physical layer
Rsxxx
Physical layer
Ethernet
Physical layer
D300815 0713- BL67 Multiprotocol
Common Modbus description
6.1.1
Protocol description
The Modbus protocol defines a simple protocol data unit (PDU) independent of the underlying
communication layers.
The mapping of Modbus protocol on specific buses or network can introduce some additional fields on
the application data unit (ADU).
Figure 6-2:
Modbus telegram
acc. to ModbusIDA
The Modbus application data unit is built by the client that initiates a Modbus transaction.
The function code indicates to the server what kind of action to perform.
The Modbus application protocol establishes the format of a request initiated by a client.
The field function code of a Modbus data unit is coded in one byte. Valid codes are in the range of 1...
255 decimal (128 – 255 reserved for exception responses).
When a message is sent from a Client to a Server device the function code field tells the server what kind
of action to perform. Function code "0" is not valid.
Sub-function codes are added to some function codes to define multiple actions.
The data field of messages sent from a client to server devices contains additional information that the
server uses to take the action defined by the function code. This can include items like discrete and
register addresses, the quantity of items to be handled, and the count of actual data bytes in the data
field.
The data field may be non-existent (= 0) in certain kinds of requests, in this case the server does not
require any additional information. The function code alone specifies the action.
If no error occurs related to the Modbus function requested in a properly received Modbus ADU the
data field of a response from a server to a client contains the data requested.
Figure 6-3:
Modbus data
transmission (acc.
to Modbus-IDA)
If an error related to the Modbus function requested occurs, the field contains an exception code that
the server application can use to determine the next action to be taken.
Figure 6-4:
Modbus data
transmission (acc.
to Modbus-IDA)
D300815 0713- BL67 Multiprotocol
6-3
Implementation of Modbus TCP
6.1.2
Data model
The data model distinguishes 4 basic data types:
Table 6-1:
Data types for
Modbus
Data Type
Object type
Access
Comment
Discrete Inputs Bit
Read
This type of data can be provided by an I/O
system.
Coils
Bit
Read-Write
This type of data can be alterable by an
application program.
Input
Registers
16-bit, (word)
Read
This type of data can be provided by an I/O
system.
Holding
Registers
16-bit, (word)
Read-Write
This type of data can be alterable by an
application program.
For each of these basic data types, the protocol allows individual selection of 65536 data items, and the
operations of read or write of those items are designed to span multiple consecutive data items up to
a data size limit which is dependent on the transaction function code.
It’s obvious that all the data handled via Modbus (bits, registers) must be located in device application
memory.
Access to these data is done via defined access-addresses (see Modbus-registers, page 6-6).
The example below shows the data structure in a device with digital and analog in- and outputs.
BL67 devices have only one data block, whose data can be accessed via different Modbus functions.
The access can be carried out either via registers (16-bit-access) or, for some of them, via single-bitaccess.
Figure 6-5:
Picture of the data
memory of the
BL67 modules
6-4
D300815 0713- BL67 Multiprotocol
Implemented Modbus functions
6.2
Implemented Modbus functions
The BL67-gateways for Modbus TCP support the following functions for accessing process data,
parameters, diagnostics and other services.
Table 6-2:
Implemented
functions
Function codes
No.
Function
Description
1
Read Coils
Serves for reading multiple output bits.
2
Read Discrete Inputs
Serves for reading multiple input bits.
3
Read Holding Registers
Serves for reading multiple output registers.
4
Read Input Registers
Serves for reading multiple input registers.
5
Write Single Coil
Serves for writing a single output bit.
6
Write Single Register
Serves for writing a single output register.
15
Write Multiple Coils
Serves for writing multiple output bits.
16
Write Multiple Registers
Serves for writing multiple output registers.
23
Read/Write Multiple Registers
Reading and writing of multiple
registers
D300815 0713- BL67 Multiprotocol
6-5
Implementation of Modbus TCP
6.3
Modbus-registers
Note
The following table page 6-7 shows the register mapping for the different Modbus
addressing methods.
Table 6-3:
Modbus registers
of the module
Address
(hex.)
Access A
Description
0x0000 - 0x01FF
ro
packed process data of inputs (process data length of
modules → siehe Table 6-5: Data width of the I/O-modules)
0x0800 - 0x09FF
rw
packed process data of output (process data length of
modules → siehe Table 6-5: Data width of the I/O-modules)
0x1000 - 0x1006
ro
gateway identifier
0x100C
ro
Gateway status (see Table 6-6: Register 100Ch: Gateway
status (page 6-13))
0x1010
ro
process image length in bit for the intelligent output
modules
0x1011
ro
process image length in bit for the intelligent input modules
0x1012
ro
process image length in bit for the digital output modules
0x1013
ro
process image length in bit for the digital input modules
0x1017
ro
register-mapping revision (always 1, if not, mapping is
incompatible with this description)
0x1018 - 0x101A
ro
group diagnostics of I/O-modules 0 to 32 (1 bit per I/O
module)
0x1020
ro
watchdog, actual time [ms]
0x1120
rw
watchdog predefined time [ms] (default: 0), see also Output
module behavior in case of an error (page 6-19))
0x1121
rw
Watchdog reset register
0x1130
rw
Modbus connection mode register, page 6-14
0x1131
rw
Modbus connection timeout in sec. (Def.: 0 = never), page
6-14
0x113C - 0x113D
rw
Modbus parameter restore
(reset of parameters to default values), page 6-14
0x113E - 0x113F
rw
Modbus parameter save
(permanent storing of parameters), page 6-14
0x2000 - 0x207F
rw
service-object, request-area, page 6-15
0x2080 - 0x20FF
ro
service-object, response-area, page 6-15
Aro = read only
rw = read/write
6-6
D300815 0713- BL67 Multiprotocol
Modbus-registers
Table 6-3:
Modbus registers
of the module
Address
(hex.)
Access A
Description
0x2400
ro
System voltage USYS [mV]
0x2401
ro
Load voltage UL [mV]
0x2405
ro
load current IL [mA]
0x27FE
ro
no. of entries in actual module list
0x27FF
rw
no. of entries in reference module list
0x2800 - 0x2840
rw
reference-module-list (max. 32 modules per station × 2
registers for module-ID)
0x2A00 - 0x2A40
ro
actual module-list (max. 32 modules per station × 2 registers
for module-ID)
0x8000 - 0x8400
ro
Process data inputs (max. 32 modules per station × 32
registers for module-ID)
0x9000 - 0x9400
rw
Process data outputs (max. 32 modules per station × 32
registers for module-ID)
0xA000 - 0xA400
ro
Diagnostics (max. 32 modules per station × 32 registers for
module-ID)
0xB000 - 0xB400
rw
Parameters (max. 32 modules per station × 32 registers for
module-ID)
Aro = read only
rw = read/write
The following table shows the register mapping for the different Modbus addressing methods
Table 6-4:
Description
Mapping of BL67GW-EN Modbusregisters (holdingregisters)
Hex
Decimal
5-digit
Modicon
packed input data
0×0000 0×01FF
0 - 511
40001 40512
400001 400512
packed output data
0×0800 0×09FF
2048 2549
42049 42560
402049 402560
gateway identifier
0×1000 0×1006
4096 - 4102 44097 44103
404097 404103
Gateway status
0×100C
4108
44109
404109
process image length in bit for the intelligent
output modules
0x1010
4112
44113
404113
process image length in bit for the intelligent
input modules
0x1011
4113
44114
404114
process image length in bit for the digital
output modules
0x1012
4114
44115
404115
D300815 0713- BL67 Multiprotocol
6-7
Implementation of Modbus TCP
Table 6-4:
Description
Mapping of BL67GW-EN Modbusregisters (holdingregisters)
Hex
Decimal
5-digit
Modicon
process image length in bit for the digital
input modules
0x1013
4115
44116
404116
Register-mapping-revision
0x1017
4119
44120
404120
group diagnostics of I/O-modules 0 to 32
(1 bit per I/O-module)
0x1018 0x101B
4120 - 4122 44121 44123
404121 404123
watchdog, actual time
0x1020
4128
44129
404129
watchdog, predefined time
0x1120
4384
44385
404385
Watchdog reset register
0x1121
4385
44386
404386
Modbus connection mode register
0x1130
4400
44401
404401
Modbus Connection Timeout
in seconds
0x1131
4401
44402
404402
Modbus parameter restore
0x113C 0x113D
4412 4413
44413 44414
404413 404414
Modbus parameter save
0x113E 0x113F
4414 4415
44415 44416
404415 404416
service-object, request-area,
0x2000 0x207F
8192 8319
48193 48320
408193 408320
service-object, response-area,
0x2080 0x20FF
8320 8447
48321 48448
408321 408448
System voltage USYS [mV]
0x2400
9216
49217
409217
Load voltage UL [mV]
0x2401
9217
49218
409218
load current IL [mA]
0x2405
9221
49222
409222
no. of entries in actual module list
0x27FE
10238
-
410239
no. of entries in reference module list
0x27FF
10239
-
410240
reference-module-list (max. 32 modules per
station × 2 registers for module-ID)
0x2800 0x2840
10240 10304
-
410241 410305
Actual module list
(max. 32 modules per station × 2 registers for
module-ID)
0x2A00 0x2A20
10752 10784
-
410753 410785
Slot-related address assignment
Process data inputs (max. 32 modules per
station × 32 registers for module-ID)
6-8
0x8000 0x8400
slot 1
0×8000
32768
-
432769
slot 2
0×8020
32800
-
432801
D300815 0713- BL67 Multiprotocol
Modbus-registers
Table 6-4:
Description
Mapping of BL67GW-EN Modbusregisters (holdingregisters)
slot 3
Hex
Decimal
5-digit
Modicon
0×8040
32832
-
432833
0×83E0
33760
...
slot 32
Process data outputs (max. 32 modules per
station × 32 registers for module-ID)
433761
0x9000 0x9400
slot 1
0×9000
32768
-
432769
slot 2
0×9020
32800
-
432801
slot 3
0×9040
32832
-
432833
0×93E0
33760
...
slot 32
Diagnostics (max. 32 modules per station × 32
registers for module-ID)
433761
0x2000 0xA400
slot 1
0×A000
40960
-
440961
slot 2
0×A020
40992
-
440993
slot 3
0×A040
41034
-
441035
0×A3E0
41952
...
slot 32
Parameters (max. 32 modules per station × 32
registers for module-ID)
441953
0xB000 0xB400
slot 1
0×B000
45056
-
445057
slot 2
0×B020
45088
-
445089
slot 3
0×B040
45120
-
445121
0×B3E0
46048
...
slot 32
D300815 0713- BL67 Multiprotocol
446049
6-9
Implementation of Modbus TCP
6.4
Structure of the packed in-/ output process data
In order to assure a largely efficient access to the process data of a station, the module data are
consistently packed and mapped to a coherent register area.
The I/O-modules are divided into digital and intelligent modules (analog modules, serial interfaces).
Both module types are mapped in separate register ranges.
The data mapping always starts with the mapping of the intelligent modules. Each module occupies as
many Modbus registers as necessary, depending on it’s data width. At least one register is occupied. A
RS232-module, for example, occupies 4 consecutive registers (8 bytes) in the input and in the output
area.
The data byte arrangement is done according to the physical order in the station, from the left to the
right.
The data of the intelligent modules are followed by the data of the digital modules, also
structuredaccording to their physical appearance in the station. The Modbus registers for the digital
data are filled up to 16 bit. This means on the one hand that one Modbus register can contain data of
different digitalmodules and on the other hand that the data of one digital module can be distributed
over multiple registers. Bit 0 of a digital module is thus not necessarily located on a word limit.
Note
An example in chapter 7, page 7-16ff. describes the data mapping.
Additionally, the software I/O-ASSISTANT offers the possibility to create a mapping table for
every station.
6.4.1
Packed input process data
„ input register area: 0000h to 01FFh
0000h
01FFh
intelligent modules,
input data
digital
Input modules
status/
diagnosis
free
Note
Independent of the I/O-configuration, an access to all 512 registers is always possible.
Registers that are not used send "0".
6-10
D300815 0713- BL67 Multiprotocol
Structure of the packed in-/ output process data
Status/ diagnosis
The area "status/diagnosis" comprises a maximum of 9 registers.
The first register contains a common gateway-/station-status.
The following registers (max. 8) contain a group diagnostic bit for each I/O-module which shows
whether a diagnostic message is pending for the relevant module or not.
Status/ diagnosis
n + 0000h
Gateway status
(reg. 100Ch)
6.4.2
n + 0008h
group diagnosis I/O-modules 0...127
(registers 1018h to 101Fh)
Packed output process data
„ output register area: 0800h to 09FFh
0800h
09FFh
intelligent modules,
Output data
digital
Output modules
free
Note
Independent of the I/O-configuration, an access to all 512 registers is always possible.
Registers that are not used send "0" answering a read access, write accesses are ignored.
D300815 0713- BL67 Multiprotocol
6-11
Implementation of Modbus TCP
6.5
Data width of the I/O-modules in the modbus-register area
The following table shows the data width of the BL67-I/O-modules within the modbus register area and
the type of data alignment.
Table 6-5:
Module
Data width of the
– digital inputs
I/O-modules
Process input
Process output
Alignment
BL67-4DI-x
4 Bit
-
bit by bit
BL67-8DI-x
8 Bit
-
bit by bit
BL67-4DO-x
-
4 Bit
bit by bit
BL67-8DO-x
-
8 Bit
bit by bit
BL67-16DO-x
-
16 Bit
bit by bit
– digital outputs
– Analog input modules
BL67-2AI-x
2 words
word by word
– Analog outputs
BL67-2AO-x
2 words
word by word
– Technology modules
6-12
BL67-1RS×××
4 words
4 words
word by word
BL67-1SSI
4 words
4 words
word by word
BL67-1CVI
4 words
4 words
word by word
D300815 0713- BL67 Multiprotocol
Data width of the I/O-modules in the modbus-register area
6.5.1
Register 100Ch: "Gateway status"
This register contains a general gateway/ station status.
Table 6-6:
Register 100Ch:
Gateway status
Bit
Name
Description
Gateway
15
I/O Controller Error
The communication controller for the I/O-system is defective.
14
Force Mode Active
Error
The Force Mode is activated, which means, the actual output
values may no match the ones defined and sent by the field bus.
13
reserved
-
12
Modbus Wdog Error
A timeout occurred in the modbus-communication.
Module bus
11
I/O Cfg Modified
ERROR
The I/O-configuration has be changed and is no longer compatible.
10
I/O Communication
Lost Error
No Communication on the module bus.
Voltage errors
9
VI too low
System supply voltage too low (< 18 V DC).
8
VI too high
System supply voltage too high (> 30 V DC).
7
VO too low
Load voltage too low (< 18 V DC).
6
VO too high
Load voltage too high (> 30 V DC).
5
Isys too high
Overload of the system voltage supply.
4
reserved
-
Warnings
3
I/O Cfg Modified
Warning
The station configuration has changed.
0
I/O Diags Active
Warning
At least one I/O-module sends active diagnosis.
D300815 0713- BL67 Multiprotocol
6-13
Implementation of Modbus TCP
6.5.2
Register 1130h: „Modbus-Connection-Mode“
This register defines the behavior of the Modbus connections:
Table 6-7:
Register 1130h:
Modbus-Connection-Mode
Bit
Name
Description
15 to 2
reserved
1
MB_ImmediateWritePermission
– 0: With the first write access, a write authorization for the respective Modbusconnection is requested. If this request fails, an exception response with exceptioncode 01h is generated. If the request is accepted, the write access is executed and the
write authorization remains active until the connection is closed.
– 1: The write authorization for the respective Modbus-connection is already opened
during the establishment of the connection. The first Modbus-connection thus
receives the write authorization, all following connections don’t (only if bit 0 = 1).
0
MB_OnlyOneWritePermission
– 0: all Modbus-connections receive the write authorization
– 1: only one Modbus-connection can receive the write permission. A write permission
is opened until a Disconnect. After the Disconnect the next connection which
requests a write access receives the write authorization.
6.5.3
Register 1131h: „Modbus-Connection-Timeout“
This register defines after which time of inactivity a Modbus-connection is closed through a Disconnect.
6.5.4
Register 0x113C and 0x113D: „Restore Modbus-Connection-Parameters”
Register 0x113C and 0x113D are used to reset the parameter-register 0x1120 and 0x1130 to 0x113B to
default.
For this purpose, write 0x6C6F to register 0×113E. To activate the reset of the registers, write 0×6164
("load") within 30 seconds in register 0×113D.
Both registers can also be written with one single request using the function codes FC16 and FC23.
The service resets the parameters without saving them. This can be achieved by using a following
"save" service.
6.5.5
Register 0x113E and 0x113F: „Save Modbus-Connection-Parameters“
Registers 0x113E and 0x113F are used for permanent storing the parameters in registers 0x1120 and
0x1130 to 0x113B.
For this purpose, write 0x7361 to register 0×113E. To activate the saving of the registers, write 0×7665
("save") within 30 seconds in register 0×113F.
Both registers can also be written with one single request using the function codes FC16 and FC23.
6-14
D300815 0713- BL67 Multiprotocol
The Service-Object
6.6
The Service-Object
The service-object is used to execute one-time or acyclic services. It is an acknowledge service which
may serve, for example, to parameterize an I/O-module.
2000h
2080h
20FFh
service request area
service response area
The service request area allows write access, the service response area only read access.
„ service request area
2000h
2001h
2002h
2003h
2004h
2005h
207Fh
Servicenumber
reserved
Service
code
Index/ addr
Data-RegCount
optional data
(0...122 registers)
The register service no. in the request area can contain a user defined value which is deleted after the
execution of the service.
The register service code specifies which service is requested.
The register index/addr is optional and the meaning depends on the particular service.
The register data-reg-count contains, depending on the service, the number (0 to 122) of the
transferred or of the requested data registers.
Depending on the service, the optional data area can contain additional parameters and/or other
data to be written.
„ Service-response-area
2080h
2081h
2082h
2083h
2084h
2085h
20FFh
Servicenumber
result
Service
code
Index/ addr
Data-RegCount
optional data
(0...122 registers)
After the execution of a request, the registers service-no., service code and index/addr in the
response area contain a copy of the values in the request area.
Note
The service no. is thus used for a simple handshake on the application level. The application
increases the service no. with every request. The service is blocked, until the service number
in the request area matches the service number in the response area.
The register result shows whether the execution was successful or not.
The register data-reg-count contains the number of data registers (0 to 122).
The optional data area can contain, depending on the service, the requested data.
D300815 0713- BL67 Multiprotocol
6-15
Implementation of Modbus TCP
Supported service numbers:
Table 6-8:
Service code
Supported service
0x0000
numbers
Meaning
no function
0x0003
indirect reading of registers
0x0010
indirect writing of registers
A service request may have the following results:
Table 6-9:
results of the
service request
Service code
Meaning
0x0000
error free execution of service
0xFFFE
Service parameters incorrect/ inconsistent
0xFFFF
service code unknown
Note
The services "indirect reading of registers" and "indirect writing of registers" offer an
additional possibility to access any Modbus register.
Current Modbus-masters support only a limited number of register-areas that can be read or
written during the communication with a Modbus-server. These areas can not be changed
during operation.
In this case, the services mentioned above enables non-cyclic access to registers.
Indirect reading of registers
1 to 122 (Param. Count) Modbus-registers are read, starting with address x (Addr).
„ service-request
2000h
2001h
2002h
Servicenumber
0×0000
0×0003
2003h
2004h
2005h
207Fh
Addr
Count
no meaning
2083h
2084h
2085h
Addr
Count
register contents
„ service response
6-16
2080h
2081h
2082h
Servicenumber
result
0×0003
20FFh
D300815 0713- BL67 Multiprotocol
The Service-Object
Indirect writing of registers
1 to 122 (Param. Count) Modbus-registers are read, starting with address Addr.)
„ service-request
2000h
2001h
2002h
Servicenumber
0×0000
0×0010
2003h
2004h
2005h
207Fh
Addr
Count
register contents
2083h
2084h
2085h
Addr
Count
no meaning
„ service response
2080h
2081h
2082h
Servicenumber
result
0×0010
D300815 0713- BL67 Multiprotocol
20FFh
6-17
Implementation of Modbus TCP
6.7
Bit areas: mapping of input-discrete- and coil-areas
The digital in- and outputs can be read and written (for outputs) as registers in the data area of the
packed in- and output process data.
Note
In the packed process data, the digital I/O data are stored following the variable in- and
output data area of the intelligent modules, which means they are stored with a variable
offset, depending on the station’s I/O-configuration.
In order to set for example a single output (single coil), the following functions are available for reading
and writing single bits:
„ FC1 („Read Coils“),
„ FC2 („Read Discrete Inputs“),
„ FC 5 („Write Single Coil“)
„ FC15 („Write Multiple Coils“)
Data mapping in the input-discrete- and coil-areas
„ Mapping Mapping: input-discrete-area
All digital inputs are stored in this area (offset "0").
„ Mapping Mapping: Coil-area
All digital outputs are stored in this area (offset "0").
6-18
D300815 0713- BL67 Multiprotocol
Output module behavior in case of an error
6.8
Output module behavior in case of an error
In case of a failure of the Modbus communication, the outputs’ behavior is as follows, depending on the
defined time for the Watchdog (register 0x1120, page 6-6):
„ watchdog = 0 ms (default)
→ outputs hold the momentary value
„ watchdog > 0 ms
→ outputs switch to 0 after the watchdog-time has run out.
Note
Please observe that changes in the watchdog time have to be saved per save-command (see
Register 0x113E and 0x113F: „Save Modbus-Connection-Parameters“ (page 6-14)).
Note
Setting the outputs to predefined substitute values is not possible in Modbus TCP. Eventually
parameterized substitute values will not be used.
D300815 0713- BL67 Multiprotocol
6-19
Implementation of Modbus TCP
6-20
D300815 0713- BL67 Multiprotocol
7
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
7.1
Used hard-/ software......................................................................................................................... 2
7.1.1
7.1.2
Hardware .............................................................................................................................................. 2
Software ............................................................................................................................................... 2
7.2
Network configuration ..................................................................................................................... 3
7.3
Programming with CoDeSys ............................................................................................................. 4
7.3.1
7.3.2
7.3.3
Predefined feature sets ........................................................................................................................ 4
Creating a new project ......................................................................................................................... 5
Defining the communication settings ................................................................................................... 7
– Gateway definition............................................................................................................................. 7
– Setting the communication path ....................................................................................................... 8
Adding the Ethernet Adapter ................................................................................................................ 9
Adding the Modbus master ................................................................................................................ 10
Adding a Modbus TCP slave .............................................................................................................. 11
Programming (example program)....................................................................................................... 13
– Small example program .................................................................................................................. 13
CoDeSys: Global variables ................................................................................................................. 14
– Global variable list ........................................................................................................................... 14
Modbus channels ............................................................................................................................... 15
– Modbus data mapping .................................................................................................................... 16
– Setting the Modbus-channels (examples) and data mapping......................................................... 18
Building, login and start...................................................................................................................... 27
Reading out the process data ............................................................................................................ 29
Evaluation of the Status Word of the BL67-Station (%IW1)............................................................... 30
7.3.4
7.3.5
7.3.6
7.3.7
7.3.8
7.3.9
7.3.10
7.3.11
7.3.12
D300815 0713- BL67 Multiprotocol
7-1
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
7.1
7.1.1
Used hard-/ software
Hardware
„ BL67-GW-EN (> VN 03-00, IP: 192.168.1.112)
– Slot 1: BL67-8XSG-PD
– Slot 2: BL67-8DI-PD
– Slot 3: BL67-2AO-I
– Slot 4: BL67-8DO-0.5A-P
– Slot 5: BL67-4AI-V/I
– Slot 6: BL67-4DO-2A-P
7.1.2
Software
„ CoDeSys 3.4, SP3, Patch 1
„ PLC:
CoDeSys Control Win V3 (3.4.3.10)
7-2
D300815 0713- BL67 Multiprotocol
Network configuration
7.2
Network configuration
BL67-stations are delivered in the address-mode "PGM-DHCP" and can
be reached using IP-address 192.168.1.254.
Note
In order to build up the communication between the BL67-gateway and a PC or a network
interface card, both devices have to be hosts in the same network.
To achieve this, you have either
„ to adapt the gateway's IP-address via BootP, DHCP in order to integrate the device into your own
network (detailed information about the different methods of
address assignment can be found unter Address assignment, page 3-15).
or
„ to change the IP address of the used PC or network interface card (for detailed information,
please read the Changing the IP address of a PC/ network interface card, page 12-12).
D300815 0713- BL67 Multiprotocol
7-3
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
7.3
Programming with CoDeSys
Open CoDeSys via "Start → All programs → 3S CoDeSys → CoDeSys → CoDeSys V 3.4“.
7.3.1
Predefined feature sets
In this example, CoDeSys is run with the "Professional feature set" not with the "Standard feature set".
This setting has influence on different CoDeSys functions and can be changed via "Tools → Options..."
in the "Features" under "Predefined feature sets...". For further information concerning this topic, please
read the CoDeSys online help.
Figure 7-1:
Predefined
feature sets
7-4
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.2
Creating a new project
1 Create a new CoDeSys-project using the "File → New project" command.
Figure 7-2:
New project
2 Select "Standard project" and define a project name.
Figure 7-3:
Standard project
D300815 0713- BL67 Multiprotocol
7-5
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
3 Select the PLC used in the project.
In this example, the CoDeSys Control Win V3 is used.
4 Please define also your preferred programming language.
In this example, Structured Text is used.
Figure 7-4:
Selection of
CoDeSys
Control Win V3
5 The new project is created.
6 In CoDeSys, the project tree is build up as follows:
Figure 7-5:
Project tree
Note
If the window "devices" should not be displayed, it can be activated via "View → Devices".
7-6
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.3
Defining the communication settings
Double-clicking the "Device (CoDeSys Control Win V3)" opens the corresponding editors.
The communication path (Gateway) to the HMI is defined in the "Communication Settings" tab.
Gateway definition
1 Use the "Add gateway"-button to open the dialog box "Gateway" and, where necessary, assign a
new gateway name.
2 Keep the setting "localhost" or define an IP-address for the gateway instead.
When using the setting "localhost“, the CoDeSys-communication-gateway of the PC, on which this
CoDeSys-installation is running, is used as programming interface.
Figure 7-6:
Communication
settings
D300815 0713- BL67 Multiprotocol
7-7
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
Setting the communication path
1 Mark the gateway and scan the network via the respective button.
2 The network card of your PC will be found and set as active path.
Figure 7-7:
Setting the
communication
path
7-8
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.4
Adding the Ethernet Adapter
Open again the context menu by right-clicking the Device entry. In the dialog "Add Device" select the
3S Ethernet Adapter under "fieldbusses → Ethernet Adapter" and add it to the project tree.
Figure 7-8:
Adding the
Ethernet Adapter
as device
D300815 0713- BL67 Multiprotocol
7-9
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
7.3.5
Adding the Modbus master
A right-click on the Ethernet-master opens the context menu. Select "Add Device" and add the Modbus
TCP-master to the network.
Figure 7-9:
Adding the
Modbus master
7-10
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.6
Adding a Modbus TCP slave
1 Now, add the Modbus TCP slaves to the project and rename them if necessary.
Figure 7-10:
Selecting a slave
D300815 0713- BL67 Multiprotocol
7-11
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
2 Again, a double-click onto the slave in the project tree opens the respective editors.
3 In the "Modbus TCP Slave“"-tab, set the nodes IP-address (in this example: address 192.168.1.16 ).
All other settings can be kept.
Figure 7-11:
Setting the IP
address at the
slave
7-12
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.7
Programming (example program)
The programming is done under PLC-PRG in the project tree. This example is programmed in
Structured Text (ST) as defined under Creating a new project (page 7-5).
Small example program
1 The counter counts
2 Counter-reset via setting the variable "xReset" (BOOL) to "1".
"xReset" has been defined in the global variables (see also page page 7-14)
Note
The status of process values is only shown in the process image if a program refers to them or
if the function "Always update variables" in the "MobusTCPSlave I/O Mapping" (see „Reading
out the process data“, page 7-29) is enabled.
Figure 7-12:
Example program
D300815 0713- BL67 Multiprotocol
7-13
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
7.3.8
CoDeSys: Global variables
Global variables are defined either in the Global Variable List (see page 7-14) or directly in the I/O
Mappings of the single stations.
Figure 7-13:
Example for
the definition of a
global variable
Global variable list
The creation of a "Global Variable List" is possible, too:
right-click to "APPL → Add object → Global Variable List".
Define the global variables The global variables are also automatically exported when building the
project, if they have been chosen for export in the symbol configuration. (see also Predefined feature
setsFigure 7-1:, page 7-4).
7-14
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.9
Modbus channels
The communication between Modbus TCP master and Modbus slaves is realized through defined
Modbus channels.
These channels are set in the register-tab "Modbus Slave Channel" using the "Add Channel..." button.
The process data of a slave can then be monitored under
"ModbusTCPSlave I/O Mapping" (see 7.3.11, „Reading out the process data“, page 7-29)
Figure 7-14:
Setting the
Modbus channels,
examples
The Modbus communication channels are defined by:
„ "Access Type":
Modbus function code, which defines the access method (bit- or word wise, read or write).
„ "READ Register" or "WRITE Register" →"Offset":
Specification of the start address for the Modbus Slave's register that has to be read or written.
These specifications have to be taken from the slave's Modbus documentation!
D300815 0713- BL67 Multiprotocol
7-15
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
Modbus data mapping
The mapping for the input and output data of a BL67-Modbus-station depends on it's configuration.
The TURCK-software "I/O-ASSISTANT (FDT/DTM" offer the possibility to create a Modbus-report for
each Modbus-station, which shows the in-and output data mapping as well as the parameter- and
diagnostic data mappings for the respective station.
Modbus mapping (I/O-ASSISTANT)
Figure 7-15:
Modbus report Mapping of inand output data
7-16
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
Figure 7-16:
Modbus report Mapping of
parameter and
diagnostic data
Note
Detailed information about the modbus registers of the BL67-stations can be found in the
descriptions in chapter 6.3.
D300815 0713- BL67 Multiprotocol
7-17
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
Setting the Modbus-channels (examples) and data mapping
1 Writing of %QW0 and mapping of the counter value (VAR "Counter", see PLC_PRG, page 7-13) to
the output byte of the station (%QW0).
1.1
Write: %QW0
– Access Type:
Write Single Register (function code 06)
– Write Register, Offset:
0x0802 (see below)
The process output data of the station can be found in register 0×0800.
Figure 7-17:
Mapping of
output data acc.
to Modbus-report
Figure 7-18:
Modbus channel,
counter value,
FC06
7-18
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
1.2
Mapping: counter value to %QW0
– The mapping of the counter value (VAR "Counter") to the station 's output register is done
the the "ModbusTCPSlave I/O Mapping".
Double click the field "variable" in the respective line. Use the "..."-button to open the
dialog box "Input Assistant" .
– Select the variable to be mapped. As "Counter" been defined in PLC_PRG, see
Programming (example program), it can be found there.
Figure 7-19:
Mapping of the
counter value to
%QW0
– Confirm with "OK". The counter value is now mirrored to %QW0 of the station and given
out.
D300815 0713- BL67 Multiprotocol
7-19
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
2 Read:
Bit 0 in register 0x0004 has to be read out
(→ reset the counter (with „xReset“ = 1)
1.3
Read: %IW0
– Access Type:
Read Holding Registers (function code 03)
– Read Register, Offset:
0x0004 (see below)
Figure 7-20:
Mapping of input
data acc. to
Modbus-report
7-20
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
Figure 7-21:
Modbus channel,
read "xReset",
FC03
1.4
Mapping:
"xReset" (global variable) to %IX0.0 in %IW0
– "xReset" is mapped to the first bit in %IW0 of BL67-8DI-PD at slot 2. This is done in the
"ModbusTCPSlave I/O Mapping".
– Double click the field "variable" in the respective line. Use the "..."-button to open the
dialog box "Input Assistant" .
– Select the variable to be mapped. "xReset" can be found in the global variables as it has
been defined there, see CoDeSys: Global variables.
D300815 0713- BL67 Multiprotocol
7-21
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
– Confirm with "OK". A "1" at bit %IX0.0 will now reset the counter to zero.
Figure 7-22:
Mapping of
"xReset" to bit
%IX0.0
7-22
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
3 Read:
→Reading the station's Status Word
– Access Type:
Read Holding Registers (function code 03)
– Read Register, Offset:
0x0004 (see below)
– The station's Status Word is read from register 0×0004 and displayed in &IW1 in the
ModbusTCPSlave I/O Mapping.
Figure 7-23:
Status Word
mapping acc. to
Modbus-report
Figure 7-24:
Setting the
Modbus channel
for reading the
status word
D300815 0713- BL67 Multiprotocol
7-23
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
Figure 7-25:
Status Word in the
process image
7-24
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
4 Write:
Parameters of the station
→
Activating the output for channel 1 at slot1 of the station BL67-8XSG-PD.
Writing parameters is normally done once during the program start and is thus not set as a "normal"
Modbus channel under "ModbusSlave Channel", but as an Initialization channel under "Modbus
Slave Init" (see Figure 7-27: Setting the initialization channel for the parameterization).
– Access Type:
Write Single Register (function code 06)
– Write Register, Offset:
0xB040 (see below)
The parameters of the station can be found in register 0xB040 to 0xB060.
Parameterization of the station
Activating the output for channel 1 at slot1. Register 0xB001, bit 8.
The parameter register is build up as follows:
Figure 7-26:
Assignment of
parameter registers
D300815 0713- BL67 Multiprotocol
7-25
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
A 28 = 256 will be written to register 0×B001, which results from the station's the parameter byte
assignment.
Figure 7-27:
Setting the initialization channel
for the parameterization
7-26
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.10
Building, login and start
1 The WIN V3-PLC has to be running. This is done in the Windows-task bar:
Figure 7-28:
Starting the WIN
V3-PLC
2 Building the program:
Figure 7-29:
Building the
program
3 Login:
Figure 7-30:
Login
D300815 0713- BL67 Multiprotocol
7-27
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
4 Start the program:
Figure 7-31:
Starting the
program
7-28
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
7.3.11
Reading out the process data
The station's process data are shown in the register tab "ModbusTCPSlave I/O Mapping".
Note
In order assure a regular updating of the process data, activate the function "Always update
variables".
Figure 7-32:
Modbus TCP Slave
I/O image with
process data
D300815 0713- BL67 Multiprotocol
7-29
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
7.3.12
Diagnosis evaluation
Evaluation of the Status Word of the BL67-Station (%IW1)
Register 0x0005 contains the Status-word of the Station (see Modbus data mapping (page 7-16)).
According to the definition of the Modbus communication channel (see Setting the Modbus-channels
(examples) and data mapping (page 7-18), it is read from %IW1 of the station image.
Figure 7-33:
Status Word of
the station
7-30
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
the message is to be interpreted as follows:
Status-register
→ %IW 1, bit 0 = 1
→ status message: „DiagWarn“ = active diagnosis
at least one module at the gateway sends a diagnostic message (see also Register 100Ch: "Gateway
status" (page 6-13)).
Register
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0x0005
0
UL
low
-
-
-
I/O Cfg
Warn.
-
-
Diag
Warn
1
-
FCE
-
MB
Wdg
I/O
CFG
I/O
COM
Usys
low
Usys
high
Evaluation on the group diagnosis
In order to identify the modules, which send diagnostic information, the group diagnosis register is
read out. The group diagnosis register always follows the Status word of the gateway in the register
mapping. Its position thus depends on the station configuration.
In this example, the group diagnosis register is register 0×0006. It contains on bit per module in the
BL67-station, which displays whether the module sends diagnostic information or not.
The order of the bits in the registers corresponds to the order of the I/O-modules within the BL67station.
Figure 7-34:
Group diagnosis
register
According to the examples for setting the modbus channels (see Setting the Modbus-channels
(examples) and data mapping (page 7-18)), the following channel is add to read out the group
diagnosis register.
D300815 0713- BL67 Multiprotocol
7-31
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
Read Holding Registers (FC3), register 0×0006, length 1
Figure 7-35:
Channel for
reading out the
group diagnosis
In the example, the group diagnosis is in %IW2:
Figure 7-36:
group diagnosis
→ bit 1 = 1
→ slot 2 sends diagnosis information
→ BL67-8DI-PD (see also Used hard-/ software (page 7-2))
7-32
D300815 0713- BL67 Multiprotocol
Programming with CoDeSys
Evaluation of the module diagnosis information
The diagnosis data of module BL67-8DI-PD at slot 2 of the example station can be found in registers
0×A020 to 0×A03F (see also Modbus TCP-report (Figure 7-16: Modbus report - Mapping of parameter
and diagnostic data (page 7-17)), whereby only register 0×A020 contains diagnosis information.
According to the examples for setting the modbus channels (see Setting the Modbus-channels
(examples) and data mapping (page 7-18)), the following channel is add to read out the module
diagnosis.
Read Holding Registers (FC3), register 0×A020, length 1:
Figure 7-37:
Diagnosis channel
D300815 0713- BL67 Multiprotocol
7-33
Application example: BL67-GW-EN for Modbus TCP (CoDeSys Win V3)
%IW3 in the I/O image of the example station shows the diagnosis information available at slot 2:
Figure 7-38:
Diagnosis data
at slot 2
Meaning:
Bit 1: Overcurrent/ short circuit sensor at channel 1
(see also Diagnostic messages of the modules (page 3-57))
Figure 7-39:
Mapping of
diagnosis data
acc. to Modbus
Report
7-34
D300815 0713- BL67 Multiprotocol
8
Implementation of PROFINET®
8.1
Address assignment.......................................................................................................................... 2
8.2
GSDML-file ........................................................................................................................................ 3
8.3
Default-values................................................................................................................................... 3
8.4
Diagnosis in PROFINET®.................................................................................................................... 4
8.4.1
8.4.2
Gateway Error codes ........................................................................................................................... 4
Channel -specific error codes of the I/O-modules .............................................................................. 5
– Meaning of the error codes for the BL67 I/O-modules ..................................................................... 5
8.5
Parameterization .............................................................................................................................. 9
8.5.1
8.5.2
8.5.3
Gateway parameters ............................................................................................................................ 9
– Description of the gateway-parameters ............................................................................................ 9
I/O-module-parameters ...................................................................................................................... 12
Parameter "module parameterization" ............................................................................................... 12
8.6
Description of user data for acyclic services ................................................................................... 13
8.6.1
8.6.2
Description of the acyclic gateway user data..................................................................................... 13
Description of the acyclic module user data ...................................................................................... 14
D300814 0713- BL67 Modbus TCP
8-1
Implementation of PROFINET®
8.1
Address assignment
Note
In PROFINET® , the connected device is not identified by it’s IP address, but recognized and
addressed by it’s device name.
The selection of a device name for a special IO device can thus be compared to the setting of
the PROFIBUS address for a DP slave.
The device name can be freely chosen.
Note
It is not necessary to address the station’s internal module bus.
8-2
D300814 0713- BL67 Modbus TCP
GSDML-file
8.2
GSDML-file
You can download the actual GSDML file for the gateway BL67-GW-PN “GSDML-V××-Turck-BL67×××.xml“ from our Homepage www.turck.com.
8.3
Default-values
Default-values:
IP-address
192.168.1.254
subnet mask:
255.255.255.0
Name:
Note
When storing the device name or the IP address or when resetting the gateway to the default
values, the GW-LED switches to orange.
During this time, the gateway’s voltage supply must not be interrupted. In case of a power
failure, faulty data will be stored in the gateway.
Note
Resetting the gateway is only possible when the station is not connected to the fieldbus (no
AR active). (no AR active).
D300814 0713- BL67 Modbus TCP
8-3
Implementation of PROFINET®
8.4
Diagnosis in PROFINET®
In PROFINET®, critical events (diagnostic messages) are reported acyclically as alarms.
In addition to information as slot-number, subslot-number, channel type etc., the diagnostic telegrams
contain error codes which define the diagnostic event more precisely.
The error codes are interpreted by the PLC-software or respective function block, so that the diagnostic
messages are normally displayed as plain text.
You will find an example of a diagnostic telegram in chapter 9.2.2, under Diagnostic telegram with error
code (page 9-19).
Please read the following sections, for the meaning of the error codes of the BL67-gateway and the I/
O-modules.
8.4.1
Table 8-1:
gateway
error codes
Gateway Error codes
Value (dec.)
Diagnostics meaning for the gateway
Error codes (1 to 9 according to the standards)
2
Undervoltage:
Undervoltage channel 0: Undervoltage at USYS
Undervoltage channel 1: Undervoltage at UL
Error codes (16 to 31 manufacturer specific)
8-4
16
Parametrization error/ configuration error
– Station configuration changed
→ The configuration is currently deviating from the reference list of modules.
Process data can still be exchanged with the module bus stations which are at
present connected to the module bus. The constellation of the module bus station
that is set in the configuration software of the corresponding controller serves as a
reference.
– Master configuration error
→ Display: Configuration error/ Parameterizing error at channel 1
→ The actual list of modules has been altered in such a manner, that no process
data can be exchanged with the module bus stations which are at present
connected to the module bus.
– Station configuration error
→ Display: Configuration error/ Parameterizing error at channel 0
→ The gateway could not prepare the station’s configuration to be read out.
22
behavior at communication loss
– Module bus error
→ Communication with the module bus station on the module bus is not possible.
D300814 0713- BL67 Modbus TCP
Diagnosis in PROFINET®
8.4.2
Channel -specific error codes of the I/O-modules
The channel-specific diagnostic messages of the I/O-modules using error codes are defined as follows:
Table 8-2:
channel-specific
error codes
Value (dec.)
Diagnosis
Error codes (1 to 9 according to the standards)
1
short circuit
2
undervoltage
4
overload
5
over temperature
6
wire break
7
overshoot upper limit
8
undershoot lower limit
9
error
Error codes (16 to 28 manufacturer specific)
16
Parametrization error/ configuration error
After a validity check, the parameter data are (partially) rejected by the module.
Check the context of parameters. Check the context of parameters.
21
hardware failure
The module detected a hardware failure. Exchange the module.
22
behavior at communication loss
The module detected a communication problem at its ports, e. g. RS232/485/422, SSI
or other interface. Check the connection or the function of the attached devices.
23
Direction error
The direction is detected to be wrong. Check the parameterization or the control
interface versus use case.
24
User software error
The module detected an user application software error. Cold-junction
compensation error
Re-initialize user the application software of the module.
25
Cold-junction compensation error
The module detected a defect or missing cold-junction compensation.
26
Overload sensor supply
The module detected a load dump at the sensor supply.
28
Common error
The module detected an error. Refer to the I/O-module manuals for a more detailed
description of possible errors. Error types can depend on the operation mode and
the parameterization.
Meaning of the error codes for the BL67 I/O-modules
The gateway changes the diagnostic messages sent by the BL67 I/O-modules to PROFINET® error codes.
D300814 0713- BL67 Modbus TCP
8-5
Implementation of PROFINET®
The following table shows, which module message will be changed to which error code.
Table 8-3:
Error Codes /
module diagnostics
Error code
No.
(dec.)
Text
1
Short circuit
2
Undervoltage
3
Overvoltage
4
Overload
4
Overload
Module diagnostics
BL67
I/O module
diagnostic message of the
module
BL67
BL67-PF-24VDC
Undervoltage VI/ Undervoltage
VO
BL67-2RFID-×
Transceiver
Voltage supply error
BL67-RFID-x
Ident-overcurrent (supply of
transceiver is switched-off)
BL67-4DI4DO-PD
Overcurrent Kx
BL67
BL67-8XSG-PD
5
Over temperature
6
Open circuit
BL67
BL67-1CNT/ENC
DIA_DOx
BL67-1CVI
Overcurrent VC (at the valve
power supply)
BL67-2AI-PT
Short circuit
BL67-×DI-PD
Open circuit
BL67-2AI-I
BL67-2AI-PT
BL67-2AI-TC
BL67-4AI-V/I
BL67-4AI4AO-V/I
BL67-1SSI
7
Upper limit value
exceeded
BL67
BL67-1CNT/ENC
STS_OFLW (overflow)
BL67-1SSI
Sensor value overflow
BL67-×AI-×/
BL67-×AO-×
Measurement value range error
(OoR)
BL67-2AI2AO-VI
8-6
D300814 0713- BL67 Modbus TCP
Diagnosis in PROFINET®
Table 8-3:
Error Codes /
module diagnostics
Error code
Module diagnostics
No.
(dec.)
Text
BL67
I/O module
diagnostic message of the
module
8
Underflow lower
limit
BL67
BL67-1CNT/ENC
STS_UFLW (underflow)
BL67-1SSI
Sensor value underflow
BL67-×AI-×/
BL67-×AO-×
Measurement value range error
(OoR)
BL67-2AI2AO-VI
9
Error
BL67
BL67-1CVI
DiagNode x/ DiagCVI:
Emergencies transmitted since
module start.
BL67-×AO-×
Overflow/ underflow OUFL
BL67-4AO-V
16
21
Parameterization
error
Hardware failure
BL67
BL67-1RS×××
Parameterization error
BL67-1SSI
BL67
BL67-1CNT/ENC
Parameterization error,
ERR_PARA
BL67-2RFID-×
Invalid parameter
BL67-2RFID-×
Transceiver hardware error
BL67-1RS×××
Hardware error
BL67-×AO-×
22
Behavior at
communication
loss
BL67
BL67-1CVI
– Communication error
transmitted since module
start/ Guard Time
– Communication error/Guard
Time timeout
BL67-2RFID-×
Parameter not supported by
transceiver
BL67-1RS×××
Data flow control error
23
Direction error
24
User software
error
BL67
BL67-2RFID-×
Software error
25
Cold-junction
compensation
error
BL67
BL67-2AI-TC
No Pt1000 sensor found (cold
junction compensation)
26
Overload sensor
supply
BL67
BL67-×DI-PD
Overcurrent/ short circuit sensor
BL67-4DI4DO-PD
BL67-8XSG-PD
D300814 0713- BL67 Modbus TCP
8-7
Implementation of PROFINET®
Table 8-3:
Error Codes /
module diagnostics
8-8
Error code
No.
(dec.)
Text
27
Unknown error
28
Common error
29
configuration
error
Module diagnostics
BL67
I/O module
diagnostic message of the
module
BL67
BL67-1SSI
SSI group diagnostics
D300814 0713- BL67 Modbus TCP
Parameterization
8.5
Parameterization
8.5.1
Gateway parameters
The BL67-gateways for PROFINET® occupy 4 parameter bytes.
Description of the gateway-parameters
Table 8-4:
gateway
parameters
Byte Bit parameters
A default
0
Value
Meaning
Byte 0
settings
bit 0, bit 1 Output behavior if one module is missing
00
output 0 A
The gateway switches the outputs of modules to "0".
No error information is transmitted. No error
information is transmitted.
01
output substitute
value
The gateway switches the outputs of all modules to
"0" (with the exception of analog output modules).
Error information is transmitted to the analog output
modules. Depending on their configuration, these
modules set their outputs either to "0" or to a default
value, or to maintain the original values. The nonconfigured analog output modules set their outputs
to "0".
10
hold current value The gateway maintains the actual output settings of
all modules (with the exception of analog output
modules). Error information is transmitted to the
analog output modules. Depending on their
configuration, these modules set their outputs either
to "0" or to a default value, or to maintain the original
values. The non-configured analog output modules
set their outputs to "0".
11
exchange process
data
The gateway carries on exchanging process data
with the other module bus stations. No error
information is transmitted.
bit 2, bit 3 Output behavior if one module is wrong
00
output 0 A
The gateway switches the outputs of modules to "0".
No error information is transmitted. No error
information is transmitted.
01
output substitute
value
The gateway switches the outputs of all modules to
"0" (with the exception of analog output modules).
Error information is transmitted to the analog output
modules. Depending on their configuration, these
modules set their outputs either to "0" or to a default
value, or to maintain the original values. The nonconfigured analog output modules set their outputs
to "0".
D300814 0713- BL67 Modbus TCP
8-9
Implementation of PROFINET®
Table 8-4:
gateway
parameters
Byte Bit parameters
0
A default
Value
Meaning
bit 2, bit 3 Output behavior if one module is wrong
10
hold current value The gateway maintains the actual output settings of
all modules (with the exception of analog output
modules). Error information is transmitted to the
analog output modules. Depending on their
configuration, these modules set their outputs either
to "0" or to a default value, or to maintain the original
values. The non-configured analog output modules
set their outputs to "0".
11
exchange process
data
settings
The gateway carries on exchanging process data
with the other module bus stations. No error
information is transmitted.
bit 4, bit 5 Output behavior at communication loss
1
00
output 0 A
The gateway switches the outputs of modules to "0".
No error information is transmitted. No error
information is transmitted.
01
output substitute
value
The gateway switches the outputs of all modules to
"0" (with the exception of analog output modules).
Error information is transmitted to the analog output
modules. Depending on their configuration, these
modules set their outputs either to "0" or to a default
value, or to maintain the original values. The nonconfigured analog output modules set their outputs
to "0".
11
hold current value The gateway maintains the actual output settings of
all modules (with the exception of analog output
modules). Error information is transmitted to the
analog output modules. Depending on their
configuration, these modules set their outputs either
to "0" or to a default value, or to maintain the original
values. The non-configured analog output modules
set their outputs to "0".
Bit 0: reserved
Bit 1: Disable all diagnosis
8-10
0
inactive A
Diagnostic messages and alarms are generated.
1
active
Diagnostic messages and alarms are not generated.
D300814 0713- BL67 Modbus TCP
Parameterization
Table 8-4:
gateway
parameters
A default
Byte Bit parameters
1
Value
Meaning
Bit 2: Disable output power diagnosis
settings
0
inactive A
A monitoring of the field supply VO (from the
gateway and the Power-Feeding modules) is
activated.
If this parameter is set but the parameter
"Diagnostics from modules" (see bit 1) deactivated,
then only the voltage supply at the gateway is
monitored. The voltage supply with VO at the PowerFeeding modules is not monitored at the power
feeding modules.
1
active
An possible over- or undervoltage for VO is not
monitored.
Bit 3:: reserved
Bit 4: I/O-ASSISTANT Force Mode disable
0
inactive A
-
1
active
The I/O-ASSISTANT is not able to access the gateway
via Force Mode.
Bit 5:: reserved
Bit 6: Startup also if configuration does not match
0
inactive A
Changes in the station configuration are stored in the
gateway following a power-on reset.
1
active
If the static configuration is deactivated, a dynamic
configuration take-over is realized directly following
station configuration changes (important for acyclic
parameterization).
Bit 7:: reserved
2
Bit 0: EtherNet/IP deactivated
0
inactive A
1
active
Explicit deactivating of the other Ethernetprotocols as well as of the web server.
Bit 1: Modbus TCP deactivated
0
inactive A
1
active
Bit 2 to Bit 7: reserved
D300814 0713- BL67 Modbus TCP
8-11
Implementation of PROFINET®
Table 8-4:
gateway
parameters
Byte Bit parameters
3
Value
Meaning
Bit 0 to Bit 6: reserved
Bit 7: Web server deactivated
8.5.2
0
inactive A
1
active
Explicit deactivating of the web server
I/O-module-parameters
The description of the single I/O-module-parameters is protocol-independent and can thus be found
in chapter 3.10, Parameters of the modules (page 3-34).
8.5.3
Parameter "module parameterization"
Each parameterizable module, gets the additional parameter "module parameterization" via the
GSDML-file of the gateway.
Note
This parameter is not part of the module parameters, but is only important for the
communication between gateway and the modules.
This parameter extension is always necessary, even if the module is parameterized via a IOsupervisor.
„ "module parameterization" activated
The module receives its parameter settings from the controller, IO-supervisor, I/O-ASSISTANT or
similar.
In this case, parameter changes which were done in the meantime for example by a configuration
tool or similar will be overwritten with the valid parameter data set.
„ "module parameterization" deactivated
Changes in the parameter settings are ignored for the respective module. The stored parameter
data will be used.
Note
If the "module parameterization" is activated and a module is replaced by a new one, the
gateway has to be operated with active USYS, in order to keep the module’s parametersettings for the new module.
UL has to be switched-off and the station has to be separated from the field bus. Now, the
gateway sends the parameters defined for the old module, into the new module.
8-12
D300814 0713- BL67 Modbus TCP
Description of user data for acyclic services
8.6
Description of user data for acyclic services
The acyclic data exchange is done via Record Data CRs (CR→ Communication Relation).
Via these Record Data CRs the reading and writing of the following services is realized:
„ Writing of configuration data
„ Reading and writing of device data
„ Reading of diagnostic data
„ Reading of I/O data
„ Reading of Identification Data Objects (I&M functions)
„ Reading of differences between the expected and the actually plugged modules
8.6.1
Description of the acyclic gateway user data
Table 8-5:
Index
Gateway Application Instance
Name
Data Type
r/w
Comment
1
(0x01)
Gateway parameters
WORD
r/w
Parameter data of the module
2
(0x02)
gateway
designation
STRING
r
Product name of the gateway
3
(0x03)
Gateway revision
STRING
r
Firmware-revision of the gateway
4
(0x04)
Vendor-ID
WORD
r
Ident number for TURCK
5
(0x05)
Gateway-Name
STRING
r
Name assigned to the gateway
6
(0x06)
Gateway type
STRING
r
Device type of the gateway
7
(0x07)
Device-ID
WORD
r
Ident number of the gateway
8 (0x08) to
23 (0x17)
reserved
24
(0x18)
Gateway diagnosis
WORD
r
Diagnosis data of the gateway
025
reserved
(0x19) to 31
(0x1F)
32
(0x20)
Module input list
Array of
BYTE
r
List of all input channels in the
station
33
(0x21)
Module output list
Array of
BYTE
r
List of all output channels in the
station
D300814 0713- BL67 Modbus TCP
8-13
Implementation of PROFINET®
Table 8-5:
Index
Gateway Application Instance
8.6.2
Name
Data Type
r/w
Comment
34
(0x22)
Module diag. list
Array of
BYTE
r
List of all module diagnosis
messages
35
(0x23)
Module parameter list
Array of
BYTE
r
List of all module parameters
36
(0x24) to
45039
(0xAFEF)
reserved
45040
(0xAFF0)
I&M0-functions
r
Identification & Maintenance
45041
(0xAFF1)
I&M1-functions
STRING[54]
r/w
not supported
45042
(0xAFF2)
I&M2-functions
STRING[16]
r/w
45043
(0xAFF3)
I&M3-functions
STRING[54]
r/w
45044
(0xAFF4)
I&M4-functions
STRING[54]
r/w
45045
(0xAFF5)
I&M5-functions
28672
(0x7000)
Gateway parameters
WORD
r/w
activating/ deactivating the
Ethernet-protocols (see also
Gateway parameters (page 8-9))
Name
Data type
r/w
Comment
1
(0x01)
Module parameter
specific
r/w
Parameter of the module
2
(0x02)
Module type
ENUM
UINT8
r
Module type
3
(0x03)
Module version
UINT8
r
Firmware-revision of the module
4
(0x04)
Module ID
DWORD
r
Ident number of the module
Description of the acyclic module user data
Table 8-6:
Index
Module user data
5
reserved
(0x05)
to 18 (0x12)
8-14
D300814 0713- BL67 Modbus TCP
Description of user data for acyclic services
19
(0x13)
Input data
specific
r
Input data of the respective module
specific
r/w
Output data of the respective
module
20
reserved
(0x14) to 22
(0x16)
23
(0x17)
Output data
24 (0x18) to reserved
31 (0x1F)
32 (0x20) to Profile-specific
255 (0xFF)
D300814 0713- BL67 Modbus TCP
These indices are reserved for the data of several module
profiles (e. g. RFID). The definitions of the profile indices
can be found in the respective module descriptions.
8-15
Implementation of PROFINET®
8-16
D300814 0713- BL67 Modbus TCP
9
Application example: BL67-GW-EN with PROFINET® (S7)
9.1
Application example ......................................................................................................................... 2
9.1.1
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.10
General ................................................................................................................................................. 2
Example network .................................................................................................................................. 2
New project in the Simatic Manager .................................................................................................... 3
Setting the PG/PC-interface................................................................................................................. 3
Installation of the GSDML-files............................................................................................................. 4
Adding PROFINET® network nodes .................................................................................................... 8
– Adding a BL67-gateway and configuring the BL67-station .............................................................. 9
Configuring the BL67-station ............................................................................................................. 10
Scanning the network for PROFINET® nodes ................................................................................... 12
– Device name assignment BL67-gateway ........................................................................................ 13
PROFINET® neighborhood detection via LLDP................................................................................. 14
– Necessary setting of the PROFINET® IO-controller ....................................................................... 14
– Configuring the neighborhood detection......................................................................................... 15
Online topology detection .................................................................................................................. 17
9.2
Diagnostics with Step 7................................................................................................................... 18
9.2.1
9.2.2
Diagnostic messages in the hardware configuration ......................................................................... 18
Diagnostic telegram with error code ................................................................................................. 19
9.1.7
9.1.8
9.1.9
D300815 0713- BL67 Multiprotocol
9-1
Application example: BL67-GW-EN with PROFINET® (S7)
9.1
9.1.1
Application example
General
In order to configure the connection of a BL67 multi-protocol gateway for PROFINET® to a Siemens PLC
S7, the software package "SIMATIC Manager" version 5.5 from Siemens is used.
Siemens is used.
9.1.2
Example network
„ Siemens PLC S7, CPU 315-2 PN/DP, 6ES7 315-2EH14-0AB0, V3.2
– device name: pn-io
– IP address: 192.168.1.112
„ FGEN-IOM88-5001
– device name: turck-fgen-107
– IP-address: not assigned, yet
„ FGEN-XSG16-5001
– device name: turck-fgen-90
– IP-address: not assigned, yet
„ BL67-GW-EN
Gateway for connecting PROFINET® to the BL67 example station (see Table 9-1: Example station).
– Device name: not assigned, yet
– IP-address: not assigned, yet
Table 9-1:
Example station
9-2
Module
Data width
Process input
Process output
GW
BL67-GW-EN
1
BL67-8XSG-PD
8 Bit
8 Bit
2
BL67-8DI-PD
8 Bit
-
3
BL67-2AO-I
-
4 Byte
4
BL67-8DO-0.5A-P
-
8 Bit
5
BL67-4AI-V/I
8 Byte
-
6
BL67-4DO-2A-P
-
4 Bit
D300815 0713- BL67 Multiprotocol
Application example
9.1.3
New project in the Simatic Manager
1 Create a new project in the Simatic Manager using the "File →New"-command
2 Add a Simatic station to the project using the "Insert → station..."-command. In this example a
"Simatic 300 station" is used.
Figure 9-1:
Selecting a
Simatic station
The configuration of the PROFINET®-network is then done in the software's hardware configuration
9.1.4
Setting the PG/PC-interface
In order to be able to build up communication between the PLC and your PG/PC via Ethernet, the
respective interface/ network card of the PG/PC has to be activated.
The configuration of the interface is done via the "Set PG/PC Interface" command.
Open this dialog in the Simatic software for example via the "Options → Set PG/PC Interface..."
command or directly in the Windows Control Panel for your PG/PC.
Figure 9-2:
Command "Set
PG/PC Interface..."
D300815 0713- BL67 Multiprotocol
9-3
Application example: BL67-GW-EN with PROFINET® (S7)
9.1.5
Installation of the GSDML-files
1 In the hardware configuration "HW config", open the "Options→ Install GSD file" command in order
to install new GSD-files.
Figure 9-3:
GSD files
install
2 Define the directory for the TURCK GSDML-files by browsing the directories and add the BL67
PROFINET® gateway to the hardware catalog.
Figure 9-4:
Install GSD files
9-4
D300815 0713- BL67 Multiprotocol
Application example
The new gateway can now be found under "PROFINET IO → Additional Field Devices → I/O → TURCK".
Figure 9-5:
BL67 gateway in
the hardware
catalog
3 Chose the profile rack "RACK-300" for the Siemens CPU from the catalog and add it to the network
window.
D300815 0713- BL67 Multiprotocol
9-5
Application example: BL67-GW-EN with PROFINET® (S7)
4 After this, select the Siemens CPU from the hardware catalog. In this example a CPU 315-2 PN/DP,
version 6ES7 315-2EH14-0AB0 (V 3.2). is used.
Figure 9-6:
Selecting the CPU
5 In the dialog "Properties Ethernet Interface", define the IP address and the subnet mask for the S7
CPU and add the subnet using the "New..." button.
Figure 9-7:
Properties
Ethernet interface
9-6
D300815 0713- BL67 Multiprotocol
Application example
Figure 9-8:
Add new Ethernet
subnet
D300815 0713- BL67 Multiprotocol
9-7
Application example: BL67-GW-EN with PROFINET® (S7)
9.1.6
Adding PROFINET® network nodes
The nodes of the example network (see page 9-2) are added to the PROFINET® as follows:
„ FGEN
– FGEN-IOM88-5001, device name: turck-fgen-107
– FGEN-XSG16-5001, device name: turck-fgen-90
Figure 9-9:
Add network
nodes
9-8
D300815 0713- BL67 Multiprotocol
Application example
Adding a BL67-gateway and configuring the BL67-station
Now, the BL67-gateway is selected from the Hardware Catalog and added to the configuration
„ BL67-GW-EN,
– Device name: not assigned, yet
– IP-address: not assigned, yet
1 Select the gateway under "PROFINET IO → Additional Field Devices→ I/O → TURCK → BL67" and
add it to the Ethernet-network.
2 A double-click on the gateway-symbol opens the dialog "Properties TURCK".
3 Enter the gateway’s device name in this dialog.
Figure 9-10:
Dialog:
Properties TURCK
Note
In PROFINET®, the connected device is not identified by it’s IP address, but recognized and
addressed by it’s device name.
The selection of a device name for a special IO device can thus be compared to the setting of
the PROFIBUS address for a DP slave.
Note
When storing the device name or the IP address or when resetting the gateway to the default
values, the GW-LED switches to orange. During this time, the gateway’s voltage supply must
not be interrupted. In case of a power failure, faulty data will be stored in the gateway.
D300815 0713- BL67 Multiprotocol
9-9
Application example: BL67-GW-EN with PROFINET® (S7)
9.1.7
Configuring the BL67-station
After the assignment of the device name, the I/O modules, which are connected to the BL67 gateway,
are added to the station. They have to be selected from the Hardware Catalog in the same order as they
appear physically in the station.
Figure 9-11:
Add I/O-modules
to the station
Add a station
1 Save your hardware configuration via "Station → Save and Compile"
2 and download it to the PLC via "PLC → Download..." command.
9-10
D300815 0713- BL67 Multiprotocol
Application example
The hardware configuration is completed.
Note
If changes in the configuration of a node are made after the download of the
configuration and the starting of the PLC, PROFINET® requires a reset for the respective
device.
This can be done following different ways:
Hardware reset:
– F_RESET at the gateway (see also F_Reset (reset to factory settings, 900) (page
3-20)
Software reset:
– HW Config: "PLC → Ethernet → Edit Ethernet Node...→ Browse", select a
node and execute the reset in the dialog box "Edit Ethernet Node..." via
"Reset".
– other PROFINET®-tool (PST-tool from Siemens, etc.)
D300815 0713- BL67 Multiprotocol
9-11
Application example: BL67-GW-EN with PROFINET® (S7)
9.1.8
Scanning the network for PROFINET® nodes
The Simatic hardware configuration offers the possibility to browse the PROFINET® network using a
broadcast command in order to find active PROFINET® nodes. The active nodes are identified via their
MAC address.
1 Open the respective dialog box by using "PLC → Ethernet →Edit Ethernet Node".
Figure 9-12:
Configure
Ethernet node
2 Browse the network for active network nodes identified by means of their MAC address, by using
the button "Browse" in the field "Ethernet node".
All PROFINET® nodes found in the network answer the command sending their MAC address and
their device name.
3 Select a node and close the dialog with "OK".
The features of the selected node are now shown in the in the dialog "Edit Ethernet Node".
9-12
D300815 0713- BL67 Multiprotocol
Application example
Device name assignment BL67-gateway
If necessary, the device name can now be changed to the needs of the application.
In this example, the following name is assigned to the BL67-gateway:
„ Device name:
turck-bl67-112
Figure 9-13:
Adaptation of the
Ethernet node
configuration
Note
Here, you can also assign an application specific device name to the devices which were
found.
Please observe, that the device name assigned here has to be similar to the device name
assigned to the node in the properties dialog box (see Figure 9-10: Dialog: Properties TURCK).
If this is not guaranteed, the PLC will not be able to clearly identify the node!
D300815 0713- BL67 Multiprotocol
9-13
Application example: BL67-GW-EN with PROFINET® (S7)
9.1.9
PROFINET® neighborhood detection via LLDP
Due to the neighborhood detection, there is no previous PROFINET® name assignment (see Device
name assignment BL67-gateway (page 9-13) is necessary for a new device of the same type and with
an identical process data width in case of a device exchange. The device name and the IP-address will
be assigned to the new device by the neighbor-device configured before (see Configuring the
neighborhood detection (page 9-15)).
Necessary setting of the PROFINET® IO-controller
The neighborhood detection without using a PC or removable media can only be executed if the
function "Support device replacement without exchangeable medium" is activated within the
properties of the PROFINET® IO-controller.
Figure 9-14:
Settings of the
PROFINET® IOcontroller
In case of a device exchange, a new device thus not receives the device name from the removable
medium or the PG but from the IO-controller.
The device name is assigned by means of the devices' port interconnections configured in the topology
definition.
9-14
D300815 0713- BL67 Multiprotocol
Application example
Configuring the neighborhood detection
A neighbor-port can be assigned to each Ethernet-port of a device. In case of a device exchange, this
port is then used to assign the IP-address and the device name to the new device.
The definition of the partner-port is done either in the properties of the devices' Ethernet-ports or
directly in the PROFINET® Topology Editor (see page 9-16).
„ Partner-port definition via port-configuration.
Selection of the port at the neighboring device to which this port is physically connected.
Figure 9-15:
Partner-port definition
(Example)
D300815 0713- BL67 Multiprotocol
9-15
Application example: BL67-GW-EN with PROFINET® (S7)
„ Neighborhood-assignment using the Topology Editor.
The assignment of neighboring devices is done either in the tabular or the graphical view.
The copper ports of the devices are shown in green, the fiber-optic-ports in orange.
Figure 9-16:
PROFINET®
Topology Editor
AExample:
copper port
Bfiber optic port
CExample:
copperconnection
A
B
C
9-16
D300815 0713- BL67 Multiprotocol
Application example
9.1.10
Online topology detection
The Step 7 software allows an offline/online comparison of the configured and the actually present
topology.
1 Start the "Offline/ online comparison" in the Topology Editor using the "Start"-button in the
respective tab.
Figure 9-17:
PROFINET®
Topology Editor
Offline/ online
comparison
D300815 0713- BL67 Multiprotocol
9-17
Application example: BL67-GW-EN with PROFINET® (S7)
9.2
Diagnostics with Step 7
9.2.1
Diagnostic messages in the hardware configuration
The BL67 gateways for PROFINET® show gateway diagnostics and channel-specific module diagnostics
in the hardware configuration of the Step 7-software.
Furthermore a special help text, which clearly specifies the error, is given for each diagnostic message:
Figure 9-18:
Diagnostics
Achannel-specific
module
diagnostics
Bmanufacturer
specific help
texts
A
B
9-18
D300815 0713- BL67 Multiprotocol
Diagnostics with Step 7
9.2.2
Diagnostic telegram with error code
Figure 9-19:
Diagnostic
message
Aslot-no.
Bsubslot-no.
Cerror code
Dplaint text diagnostic message
C
A
B
D
D300815 0713- BL67 Multiprotocol
9-19
Application example: BL67-GW-EN with PROFINET® (S7)
9-20
D300815 0713- BL67 Multiprotocol
10 Guidelines for station planning
10.1
Module arrangement ........................................................................................................................ 2
10.1.1
Random module arrangement.............................................................................................................. 2
10.2
Complete planning ........................................................................................................................... 3
10.3
Maximum system extension ............................................................................................................. 4
10.4
Creating potential groups................................................................................................................. 5
10.5
Plugging and pulling electronics modules ....................................................................................... 5
10.6
Extending an existing station ........................................................................................................... 5
10.7
Firmware download .......................................................................................................................... 5
D300815 0713- BL67 Multiprotocol
10-1
Guidelines for station planning
10.1
10.1.1
Module arrangement
Random module arrangement
The arrangement of the I/O-modules within a BL67 station can basically be chosen at will.
Nevertheless, it can be useful with some applications to group certain modules together.
10-2
D300815 0713- BL67 Multiprotocol
Complete planning
10.2
Complete planning
The planning of a BL67 station should be thorough to avoid faults and increase operating reliability.
Attention
If there are more than two empty slots next to one another, the communication is interrupted
to all following BL67 modules.
D300815 0713- BL67 Multiprotocol
10-3
Guidelines for station planning
10.3
Maximum system extension
A BL67 station can consist of a gateway and a maximum of 32 modules (equivalent to 1 m station
length).
The following overview shows the maximum number of channels possible under these conditions:
„ The entire station is made up of the respective module type only.
Attention
Ensure that a sufficient number of Bus Refreshing and Power Feeding modules are used if the
system is extended to its maximum.
Note
If the system limits are exceeded, the software I/O-ASSISTANT 3 (FDT/DTM) generates an error
message when the user activates the command "Station → Verify station".
Table 10-1:
Maximum
system extension
Alimited due to the
high current
consumption
(max. 1,5 A)
(max. 1,5 A)
on the module
bus (5V)
10-4
Module type
Maximum number
Channels
Modules
BL67-4DI-x
128
32
BL67-8DI-x
256
32
BL67-4DO-xA-P
128
32
BL67-8DO-xA-P
256
32
BL67-8DO-R-NO
256
32
BL67-16DO-0.1A-P
512
32
BL67-4DI4DO-PD
256
32
BL67-8XSG-PD
256
32
BL67-2AI-x
64
32
BL67-2AI-PT
64
32
BL67-2AI-TC
64
32
BL67-4AI-TC
104
26
BL67-4AI-V/I
128
32
BL67-2AO-I
64
32
BL67-2AO-V
42 A
21 A
BL67-4AO-V
84
21
BL67-2AI2AO-V/I
42
21
BL67-4AI4AO-V/I
84
21
BL67-1RS232
9A
9A
BL67-1RS485/422
21
21
D300815 0713- BL67 Multiprotocol
Maximum system extension
BL67-1SSI
21
21
BL67-1CVI
32
32
BL67-1CNT/ENC
21
21
BL67-2RFID-x
8
4
D300815 0713- BL67 Multiprotocol
10-5
Guidelines for station planning
10.4
Creating potential groups
Power Feeding modules can be used to create potential groups. The potential isolation of potential
groups to the left of the respective power distribution modules is provided by the base modules.
10.5
Plugging and pulling electronics modules
BL67 enables the pulling and plugging of electronics modules without having to disconnect the field
wiring. The BL67 station remains in operation if an electronics module is pulled.
The voltage and current supplies as well as the protective earth connections are not interrupted
Attention
If the field and system supplies remain connected when electronics modules are plugged or
pulled, short interruptions to the module bus communications can occur in the BL67 station.
This can lead to undefined statuses of individual inputs and outputs of different modules.
10.6
Extending an existing station
Attention
Please note that extensions to the station (mounting further modules) should be carried out
only when the station is in a voltage-free state.
10.7
Firmware download
For the BL67-GW-EN (< VN 03-00), the firmware can only be downloaded via Ethernet using the
software tool I/O-ASSISTANT 3 (FDT/DTM).
The download using the USB-interface is not supported. More information is available in the program’s
online help.
Attention
The station should be disconnected from the fieldbus when downloading.
Firmware must be downloaded by authorized personnel only.
The field level must be isolated.
10-6
D300815 0713- BL67 Multiprotocol
11 Guidelines for Electrical Installation
11.1
General notes .................................................................................................................................... 2
11.1.1
11.1.2
11.1.3
11.1.4
General ................................................................................................................................................. 2
Cable routing ........................................................................................................................................ 2
– Cable routing inside and outside of cabinets .................................................................................... 2
– Cable routing outside buildings......................................................................................................... 3
Lightning protection.............................................................................................................................. 3
Transmission media.............................................................................................................................. 3
11.2
Potential relationships ..................................................................................................................... 4
11.2.1
General ................................................................................................................................................. 4
11.3
Electromagnetic compatibility (EMC) ............................................................................................... 5
11.3.1
11.3.2
11.3.3
11.3.4
11.3.5
Ensuring electromagnetic compatibility ............................................................................................... 5
Grounding of inactive metal components ............................................................................................ 5
PE connection ...................................................................................................................................... 5
Earth-free operation.............................................................................................................................. 5
Mounting rails ....................................................................................................................................... 6
11.4
Shielding of cables ............................................................................................................................ 7
11.5
Potential compensation.................................................................................................................... 8
11.5.1
11.5.2
Switching inductive loads..................................................................................................................... 8
Protection against Electrostatic Discharge (ESD) ................................................................................ 8
D300815 0713- BL67 Multiprotocol
11-1
Guidelines for Electrical Installation
11.1
11.1.1
General notes
General
Cables should be grouped together, for example: signal cables, data cables, heavy current cables,
power supply cables.
Heavy current cables and signal or data cables should always be routed in separate cable ducts or
bundles. Signal and data cables must always be routed as close as possible to ground potential surfaces
(for example support bars, cabinet sides etc.).
11.1.2
Cable routing
Correct cable routing prevents or suppresses the reciprocal influencing of parallel routed cables.
Cable routing inside and outside of cabinets
To ensure EMC-compatible cable routing, the cables should be grouped as follows:
Various types of cables within the groups can be routed together in bundles or in cable ducts.
Group 1:
„ shielded bus and data cables
„ shielded analog cables
„ unshielded cables for DC voltage ≤ 60 V
„ unshielded cables for AC voltage ≤ 25 V
Group 2:
„ unshielded cables for DC voltage > 60 V
transistor power output ≤ 400 V,
„ unshielded cables for DC voltage > 25 V
transistor power output ≤ 400 V,
Group 3:
„ unshielded cables for DC and AC voltages > 400 V
The following group combination can be routed only in separate bundles or separate cable ducts (no
minimum distance apart):
„ Group 1/Group 2
The group combinations:
Group 1/Group 3 and Group 2/Group 3
must be routed in separate cable ducts with a minimum distance of 10 cm apart. This is equally valid for
inside buildings as well as for inside and outside of switchgear cabinets.
11-2
D300815 0713- BL67 Multiprotocol
General notes
Cable routing outside buildings
Outside of buildings, cables should be routed in closed (where possible), cage-type cable ducts made
of metal. The cable duct joints must be electrically connected and the cable ducts must be earthed.
Danger
Observe all valid guidelines concerning internal and external lightning protection and
grounding specifications when routing cables outside of buildings.
11.1.3
Lightning protection
The cables must be routed in double-grounded metal piping or in reinforced concrete cable ducts.
Signal cables must be protected against overvoltage by varistors or inert-gas filled overvoltage
arrestors. Varistors and overvoltage arrestors must be installed at the point where the cables enter the
building.
11.1.4
Transmission media
For a communication via Ethernet, different transmission media can be used:
„ coaxial cable
10Base2 (thin coax),
10Base5 (thick coax, yellow cable)
„ optical fiber (10BaseF)
„ twisted two-wire cable (10BaseT) with shielding (STP) or without shielding (UTP)
Note
TURCK offers a variety of cable types for fieldbus lines as premoulded or bulk cables with
different connectors.
The ordering information on the available cable types can be taken from the BL67-catalog.
D300815 0713- BL67 Multiprotocol
11-3
Guidelines for Electrical Installation
11.2
11.2.1
Potential relationships
General
The potential relationship of a Ethernet system realized with BL67 modules is characterized by the
following:
„ The system supply of gateway and I/O-modules as well as the field supply are realized via one power
feed at the gateway.
„ All BL67 modules (gateway, Power Feeding and I/O-modules), are connected capacitively via base
modules to the mounting rails.
The block diagram shows the arrangement of a typical BL67 station with Ethernet gateway.
Figure 11-1:
block diagram,
BL67 station
gateway
fieldbus
I/O-module
power feeding
I/O-module
module bus
5V
logic
Logik
I>
Vi
Vo
I>
GND
PE
PE
logic
Logik
logic
PE
Vi GND Vo PE
2O
11-4
Vi GND Vo
2I
D300815 0713- BL67 Multiprotocol
Electromagnetic compatibility (EMC)
11.3
Electromagnetic compatibility (EMC)
BL67 products comply in full with the requirements pertaining to EMC regulations. Nevertheless, an
EMC plan should be made before installation.
Hereby, all potential electromechanical sources of interference should be considered such as galvanic,
inductive and capacitive couplings as well as radiation couplings.
11.3.1
Ensuring electromagnetic compatibility
The EMC of BL67 modules is guaranteed when the following basic rules are adhered to:
„ Correct and large surface grounding of inactive metal components.
„ Correct shielding of cables and devices.
„ Proper cable routing – correct wiring.
„ Creation of a standard reference potential and grounding of all electrically operated devices.
„ Special EMC measures for special applications.
11.3.2
Grounding of inactive metal components
All inactive metal components (for example: switchgear cabinets, switchgear cabinet doors, supporting
bars, mounting plates, tophat rails, etc.) must be connected to one another over a large surface area
and with a low impedance (grounding). This guarantees a standardized reference potential area for all
control elements and reduces the influence of coupled disturbances.
„ In the areas of screw connections, the painted, anodized or isolated metal components must be
freed of the isolating layer. Protect the points of contact against rust.
„ Connect all free moving groundable components (cabinet doors, separate mounting plates, etc.) by
using short bonding straps to large surface areas.
„ Avoid the use of aluminum components, as its quick oxidizing properties make it unsuitable for
grounding.
Danger
The grounding must never – including cases of error – take on a dangerous touch potential.
For this reason, always protect the ground potential with a protective cable.
11.3.3
PE connection
A central connection must be established between ground and PE connection (protective earth).
11.3.4
Earth-free operation
Observe all relevant safety regulations when operating an earthfree system.PE connection
D300815 0713- BL67 Multiprotocol
11-5
Guidelines for Electrical Installation
11.3.5
Mounting rails
All mounting rails must be mounted onto the mounting plate with a low impedance, over a large
surface area, and must be correctly earthed. Use corrosion-resistant mounting rails
Figure 11-2:
Mounting options
ATS 35
Bmounting rail
Cmounting plate
Mount the mounting rails over a large surface area and with a low impedance to the support system
using screws or rivets.
Remove the isolating layer from all painted, anodized or isolated metal components at the connection
point. Protect the connection point against corrosion (for example with grease; caution: use only
suitable grease).
11-6
D300815 0713- BL67 Multiprotocol
Shielding of cables
11.4
Shielding of cables
Shielding is used to prevent interference from voltages and the radiation of interference fields by
cables. Therefore, use only shielded cables with shielding braids made from good conducting materials
(copper or aluminum) with a minimum degree of coverage of 80%.
The cable shield should always be connected to both sides of the respective reference potential (if no
exception is made, for example, such as high-resistant, symmetrical, analog signal cables). Only then
can the cable shield attain the best results possible against electrical and magnetic fields.
A one-sided shield connection merely achieves an isolation against electrical fields.
Attention
When installing, please pay attention to the following...
– the shield should be connected immediately when entering the system,
– the shield connection to the shield rail should be of low impedance,
– the stripped cable-ends are to be kept as short as possible,
– the cable shield is not to be used as a bonding conductor.
If the data cable is connected via a SUB-D connector, the shielding should never be connected
via pin 1, but to the mass collar of the plug-in connector.
The insulation of the shielded data-cable should be stripped and connected to the shield rail when the
system is used in stationary operation The connection and securing of the shield should be made using
metal shield clamps. The shield clamps must enclose the shielding braid and in so doing create a large
surface contact area. The shield rail must have a low impedance (for example, fixing points of 10 to 20
cm apart) and be connected to a reference potential area.
The cable shield should not be severed, but routed further within the system (for example, to the
switchgear cabinet), right up to the interface connection.
Note
Should it not be possible to ground the shield on both sides due to switching arrangements
or device specific reasons, then it is possible to route the second cable shield side to the local
reference potential via a capacitor (short connection distances). If necessary, a varistor or
resistor can be connected parallel to the capacitor, to prevent disruptive discharges when
interference pulses occur.
A further possibility is a double-shielded cable (galvanically separated), whereby the
innermost shield is connected on one side and the outermost shield is connected on both
sides.
D300815 0713- BL67 Multiprotocol
11-7
Guidelines for Electrical Installation
11.5
Potential compensation
Potential differences can occur between installation components that are in separate areas if these
„ are fed by different supplies,
„ have double-sided conductor shields which are grounded on different installation components.
A potential-compensation cable must be routed to the potential compensation.
Danger
Never use the shield as a potential compensation.
Figure 11-3:
potential
compensation
Shield
Potential compensation cable
Reference potential
Reference potential
A potential compensation cable must have the following characteristics:
„ Low impedance. In the case of compensation cables that are routed on both sides, the
compensation line impedance must be considerably smaller than that of the shield connection
(max. 10% of shield connection impedance).
„ Should the length of the compensation cable be less than 200 m, then its cross-section must be at
least 16 mm2 /0.025 inch2. If the cable length is greater than 200 m, then a cross-section of at least
25 mm2 / 0.039 inch2 is required.
„ The compensation cable must be made of copper or zinc coated steel.
„ The compensation cable must be connected to the protective conductor over a large surface area
and must be protected against corrosion.
„ Compensation cables and data cables should be routed as close together as possible, meaning the
enclosed area should be kept as small as possible.
11.5.1
Switching inductive loads
In the case of inductive loads, a protective circuit on the load is recommended.
11.5.2
Protection against Electrostatic Discharge (ESD)
Attention
Electronic modules and base modules are at risk from electrostatic discharge when
disassembled. Avoid touching the bus connections with bare fingers as this can lead to ESD
damage.
11-8
D300815 0713- BL67 Multiprotocol
12 Appendix
12.1
Data image of the technology modules ............................................................................................ 2
12.1.1
1RS232/ 1RS485-module..................................................................................................................... 2
– Process input data (PZDE) ................................................................................................................ 2
– Process output data (PZDA).............................................................................................................. 4
SSI module ........................................................................................................................................... 6
– Process input data (PZDE) ................................................................................................................ 6
– Process output data (PZDA)............................................................................................................ 10
12.1.2
12.2
Changing the IP address of a PC/ network interface card ............................................................... 12
12.2.1
12.2.2
Changing the IP address in Windows ................................................................................................ 12
Changing the IP address via IPACTware™ FDT/DTM (I/O-ASSISTANT V3)..................................... 14
12.3
Deactivating/ adapting the firewall in Windows ............................................................................ 15
12.4
Addressing via DHCP ...................................................................................................................... 17
12.5
Nominal current consumption of modules on Ethernet ................................................................. 19
12.6
Ident codes of the BL67-modules ................................................................................................... 21
D300815 0713- BL67 Multiprotocol
12-1
Appendix
12.1
12.1.1
Data image of the technology modules
1RS232/ 1RS485-module
Process input data
Process input data is data from the connected field device that is transmitted via the BL67-1RSxxx
module to the PLC. The BL67-1RSxxx-module sends the data, received by the device, into a 128-byte
receive-buffer. The module then transmits the data segmented via the module bus and the gateway to
the SPS.
The transmission is realized in a 8-byte format which is structured as follows:
„ 1 status byte is required to ensure trouble-free transmission of the data.
„ 1 byte contains the diagnostics data.
„ 6 bytes are used to contain the user data.
Figure 12-1:
Process input data
SPS
12-2
D300815 0713- BL67 Multiprotocol
Data image of the technology modules
Table 12-1:
designation
Value
Meaning of the
0 - 255
data bits (process BufOvfl; FrameErr;
HndShErr;
HwFailure;
input)
PrmErr
Description
Diagnostic information (correspond to the diagnostic information
in the diagnosis telegram).
These diagnostics are always displayed and independent to the
setting of the parameter „Diagnostics".
STAT
0-1
1: The communication with the data terminal equipment (DTE) is
not disturbed.
0: The communication with the data terminal equipment (DTE) is
disturbed. A diagnosis message is generated if the parameter
"Diagnostics" is set to "0" = release. The diagnostic data show the
cause of the communication disturbance.
The user has to set back this bit in the process output data by using
STATRES.
TX_CNT_ACK
0-3
The value TX_CNT_ACK is a copy of the value TX_CNT. The value
TX_CNT was transferred together with the last data segment of the
process output data.
The value TX_CNT_ACK is a confirmation of successful acceptance
of the data segment using TX_CNT.
RX_CNT
0-3
This value is transferred together with every data segment. The
RX_CNT values are sequential: The RX_CNT values are sequential:
00->01->10->11->00...
(decimal: 0->1->2->3->0...)
Errors in this sequence show the loss of data segments.
RX_BYTE_CNT
0-7
Number of the valid bytes in this data segment.
D300815 0713- BL67 Multiprotocol
12-3
Appendix
Process output data
Process output data are data which are sent from the PLC via the gateway and the BL67-1RS×××module to a connected field device. The data received from the PLC are loaded into the 64-bit transmitbuffer in the BL67-1RS×××-module.
The transmission is realized in a 8-byte format which is structured as follows:
„ 1 control byte is required to ensure trouble-free transmission of the data.
„ 1 byte contains, signals to start the flushing of transmit- and receive buffer.
„ 6 bytes are used to contain the user data.
Figure 12-2:
Process output
data
Table 12-2:
designation
Meaning of the
data bits (process STATRES
output)
12-4
Value
Description
0-1
This bit is set to reset the STAT bit in the process input data.
With the change from 1 to 0 the STAT bit is reset (from 0 to 1).
If this bit is 0, all changes in TX_BYTE_CNT, TX_CNT and
RX_CNT_ACK are ignored. The clearing of the receive and transmit
buffer by RXBUF FLUSH/TXBUF FLUSH is possible.
The value 1 or the transition from 0 to 1 disables the clearing of the
receive and transmit buffer by the RXBUF FLUSH/TXBUF FLUSH.
RXBUF FLUSH
0-1
The RXBUF FLUSH bit is used for clearing the receive buffer.
If STATRES = 1:
A request with RXBUF FLUSH = 1 will be ignored.
If STATRES = 0:
RXBUF FLUSH = 1 will clear the receive buffer.
TXBUF FLUSH
0-1
The TXBUF FLUSH bit is used for clearing the transmit buffer.
If STATRES = 1:
A request with TXBUF FLUSH = 1 will be ignored.
If STATRES = 0:
TXBUF FLUSH = 1 will clear the receive buffer.
D300815 0713- BL67 Multiprotocol
Data image of the technology modules
RX_CNT_ACK
0-3
The value RX_CNT_ACK is a copy of the value RX_CNT. The value
TX_CNT was transferred together with the last data segment of the
process output data.
RX_CNT_ACK has to be set analog to RX_CNT (in the status byte).
RX_CNT_ACK is an acknowledge for the successful transmission of
the data segment with RX_CNT. New data can now be received.
TX_CNT
0-3
This value is transferred together with every data segment. The
TX_CNT values are sequential: The TX_CNT values are sequential:
00 -> 01 -> 10 -> 11 -> 00...
(decimal: 0 -> 1 -> 2 -> 3 -> 0...)
Errors in this sequence show the loss of data segments.
TX_BYTE_CNT
0-7
Number of the valid bytes in this data segment.
D300815 0713- BL67 Multiprotocol
12-5
Appendix
12.1.2
SSI module
Process input data
The field input data is transferred from the connected field device to BL67-1SSI-module.
The process input data is the data that is transferred by the BL67-1SSI-module via a gateway to the PLC.
The transmission is realized in a 8-byte format which is structured as follows:
„ 1 byte contains messages concerning the communication status between the BL67-1SSI module
and the SSI encoder, as well as other results of comparison operations.
„ 1 byte contains the results of comparison operations with the SSI encoder value.
„ 1 byte can be used to transfer status messages of the SSI encoder. This byte also contains an
acknowledgement that the write operation to the register was successful and indication of an active
write operation.
„ When necessary, 1 byte represents the register address of the read data and an acknowledgement
that the read operation was successful.
„ 4 bytes are used for representing the data that was read from the register with the address stated at
REG_RD_ADR.
The following table describes the structure of the 8 x 8 bits of the process input data.
STS (or ERR) contains non-retentive status information, i.e. the bit concerned indicates the actual status.
FLAG describes a retentive flag that is set in the event of a particular event. The bit concerned retains
the value until it is reset.
Figure 12-3:
Process input data
12-6
D300815 0713- BL67 Multiprotocol
Data image of the technology modules
Table 12-3:
designation
Meaning of the
data bits (process
input)
Value
Description
REG_RD_DATA
0... 232-1
Content of the register to be read if REG_RD_ABORT=0.
If REG_RD_ABORT =1, then REG_RD_DATA=0.
REG_RD_ABORT
0
The reading of the register defined in REG_RD_ADR has been
accepted and executed. The content of the register can be found in
the user data (REG_RD_DATA, byte 0-3).
1
Reading of the register defined in REG_RD_ADR has not been
accepted. The user data range (REG_RD_DATA Bytes 0-3) is zero.
REG_RD_ADR
0...63
Address of the register to be read. If the read operation is successful
(REG_RD_ABORT = 0), the user data is located in REG_RD_DATA of
the process input data (bytes 0 to 3).
REG_WR_ACEPT
0
Writing the user data from the process output to the register
addressed with REG_WR_ADR in the process output could not be
done.
1
Writing the user data from the process output to the register
addressed with REG_WR_ADR in the process output was
successful.
0
No modification of the data in the register bank by process output,
i.e. REG_WR = 0.
A write job would be accepted with the next telegram of process
output data.
(handshake for data transmission to the register.)
1
A modification of the register contents by a process output was
initiated, i.e. REG_WR = 1.
A write job would not be accepted with the next telegram of process
output data.
0
These four bits transfer the status bits of the SSI encoder with the
status messages of the SSI module. With some SSI encoders, the
status bits are transferred together with the position value.
REG_WR_AKN
SSI_STS3
1
SSI_STS2
0
1
SSI_STS1
0
1
SSI_STS0
0
1
STS_UP (LED UP)
D300815 0713- BL67 Multiprotocol
0
The SSI encoder values are decremented or the values are constant.
1
The SSI encoder values are incremented.
12-7
Appendix
Table 12-3:
designation
Meaning of the
data bits (process
input)
STS_DN (LED DN)
REL_CMP2
FLAG_CMP2
STS_CMP2
REL_CMP1
FLAG_CMP1
STS_CMP1
STS_STOP
ERR_PARA
12-8
Value
Description
0
The SSI encoder values are incremented or the values are constant.
1
The SSI encoder values are decremented.
0
A comparison of the register contents has produced the following
result:
(REG_SSI_POS) < (REG_CMP2)
1
A comparison of the register contents has produced the following
result:
(REG_SSI_POS) ≥ (REG_CMP2)
0
Default status, i.e. the register contents have not yet matched
(REG_SSI_POS) = (REG_CMP2) since the last reset.
1
The contents of the registers match (REG_SSI_POS) = (REG_CMP2).
This marker must be reset with CLR_CMP2 = 1 in the process output
data.
0
A comparison of the register contents has produced the following
result:
(REG_SSI_POS) ≠ (REG_CMP2)
1
A comparison of the register contents has produced the following
result:
(REG_ SSI_POS) = (REG_CMP2)
0
A comparison of the register contents has produced the following
result:
(REG_SSI_POS) < (REG_CMP1)
1
A comparison of the register contents has produced the following
result:
(REG_ SSI_POS) ≥ (REG_CMP1)
0
Default status, i.e. the register contents have not yet matched
(REG_SSI_POS) = (REG_CMP1) since the last reset.
1
The contents of the registers match (REG_SSI_POS) = (REG_CMP1).
This marker must be reset with CLR_CMP1 = 1 in the process output
data.
0
A comparison of the register contents has produced the following
result:
(REG_SSI_POS) ≠ (REG_CMP1)
1
A comparison of the register contents has produced the following
result:
(REG_ SSI_POS) = (REG_CMP1)
0
The SSI encoder is read cyclically.
1
Communication with the SSI encoder is stopped as STOP = 1
(process output) or
0
The parameter set of the module has been accepted.
1
Operation of the module is not possible with the present parameter
set.
D300815 0713- BL67 Multiprotocol
Data image of the technology modules
Table 12-3:
designation
Meaning of the
data bits (process
input)
STS_UFLW
STS_OFLW
ERR_SSI
SSI_DIAG
D300815 0713- BL67 Multiprotocol
Value
Description
0
A comparison of the register contents has produced the following
result: (REG_SSI_POS) ≥ (REG_LOWER_LIMIT)
1
A comparison of the register contents has produced the following
result: (REG_SSI_POS) < (REG_LOWER_LIMIT)
0
A comparison of the register contents has produced the following
result: (REG_SSI_POS) ≤ (REG_UPPER_LIMIT)
1
A comparison of the register contents has produced the following
result: (REG_SSI_POS) > (REG_UPPER_LIMIT)
0
SSI encoder signal present.
1
SSI encoder signal faulty. (e.g. due to a cable break).
0
No enabled status signal is active (SSI_STSx = 0).
1
At least one enabled status signal is active (SSI_STSx = 1)
12-9
Appendix
Process output data
Field output data is output from an BL67-1SSI-module to a field device.
The process output data is the data that is transferred by the PLC via a gateway to the BL67-1SSImodule.
The transmission is realized in a 8-byte format which is structured as follows:
„ 1 byte contains a Stop bit for interrupting communication with the encoder.
„ 1 byte is used for controlling the comparison operations.
„ 1 byte contains the register address of the data to be written to bytes 0 to 3 of this telegram and a
write request.
„ 1 byte contains the register address for the data that is to be read with the next response telegram.
„ 4 bytes are used for representing the data that is to be written to the register with the address
specified at REG_WR_DATA.
Figure 12-4:
Process output
data
12-10
D300815 0713- BL67 Multiprotocol
Data image of the technology modules
Meaning of the data bits (process output)
Table 12-4:
designation
Meaning of the
data bits (process REG_WR_DATA
output)
Value
Description
0... 232-1
Value which has to be written to the register with the address
REG_WR_ADR.
REG_RD_ADR
0...63
Address of the register which has to be read. If the reading was
successful (REG_RD_ABORT = 0), the user data can be found in
REG_RD_DATA in the status interface (bytes 4-7).
REG_WR
0
Default status, i.e. there is no request to overwrite the content of the
register with the address stated at REG_WR_ADR with
REG_WR_DATA. Bit REG_WR_AKN is reset (0).
1
Request to overwrite the content of the register with address
REG_WR_ADR with REG_WR_DATA.
REG_WR_ADR
0...63
Address of the register, which has to be written with
REG_WR_DATA.
CLR_CMP2
0
Default status, i.e. no reset of FLAG_CMP2 active.
1
Reset of FLAG_CMP2 active.
0
Default status, i.e. the data bits REL_CMP2, STS_CMP2 and
FLAG_CMP2 always have the value 0, irrespective of the actual SSI
encoder value.
1
Comparison active, i.e. the data bits REL_CMP2, STS_CMP2 and
FLAG_CMP2 always have a value based on the result of the
comparison with the SSI encoder value.
0
Default status, i.e. reset of FLAG_CMP1 not active.
1
Reset of FLAG_CMP1 active.
0
Default status, i.e. the data bits REL_CMP1, STS_CMP1 and
FLAG_CMP1 always have the value 0, irrespective of the actual SSI
encoder value.
1
Comparison active, i.e. the data bits REL_CMP1, STS_CMP1 and
FLAG_CMP1 always have a value based on the result of the
comparison with the SSI encoder value.
0
Request to read the SSI encoder cyclically
1
Request to interrupt communication with the encoder
EN_CMP2
CLR_CMP1
EN_CMP1
STOP
D300815 0713- BL67 Multiprotocol
12-11
Appendix
12.2
12.2.1
Changing the IP address of a PC/ network interface card
Changing the IP address in Windows
The IP address is changed in the Control Panel:
„ in Windows 2000/Windows XP under "Network Connections",
„ in Windows 7 under "Network and Sharing Center".
Figure 12-5:
Changing the IP
address in
Windows 2000/
XP
12-12
D300815 0713- BL67 Multiprotocol
Changing the IP address of a PC/ network interface card
Figure 12-6:
Changing the IP
address in
Windows 7
D300815 0713- BL67 Multiprotocol
12-13
Appendix
12.2.2
Changing the IP address via PACTware™ FDT/DTM (I/O-ASSISTANT V3)
The Busaddress Management DTM in the software I/O-ASSISTANT (access via: "Additional functions →
Busaddress Management") offers the possibility to browse the whole Ethernet network for connected
nodes and to change their IP address as well as the subnet mask according to the application (see also ).
Further information about this issue can be found under Addressing via I/O-ASSISTANT 3 (FDT/DTM)
(page 3-21).
Figure 12-7:
Busaddress
Management
12-14
D300815 0713- BL67 Multiprotocol
Deactivating/ adapting the firewall in Windows
12.3
Deactivating/ adapting the firewall in Windows
When using the Windows Firewall, problems may occur while changing IP addresses
via the I/O-ASSISTANT. In this case, you can deactivate the system integrated Windows firewall
completely or adapt it to your application.
„ Deactivating the Windows firewall
Open the "Windows Firewall" dialog in the control panel of your PC and
deactivate it as follows:
Figure 12-8:
Deactivating the
Firewall in
Windows 2000/
XP
Figure 12-9:
Deactivating the
Firewall in
Windows 7
D300815 0713- BL67 Multiprotocol
12-15
Appendix
„ Adapting the Windows firewall
The firewall remains active, the option "Don’t allow exceptions" it deactivated:
Figure 12-10:
Adapting the Firewall in Windows
2000/ XP
Figure 12-11:
Adapting the Firewall in Windows 7
12-16
D300815 0713- BL67 Multiprotocol
Addressing via DHCP
12.4
Addressing via DHCP
In this application example, the IP address is set via DHCP using the software tool "BootP/DHCP-Server"
version 2.3.2.0 from Rockwell Automation.
Figure 12-12:
BootP-Server from
Rockwell
Automation
Addresses in the range from 1 to 254 can be allocated. The addresses 0 and 255 are reserved for
broadcast messages in the subnet.
Note
The rotary coding switches on the gateway must be set to "300" = BootP, "400" = DHCP or
"600" = PGM-DHCP in order to enable the BootP/DHCP-Mode.
(see also chapter 3.5, section Address assignment (page 3-15)).
After having been connected to the network, the BL67 sends DHCP requests to the server using its
MAC-ID.
Figure 12-13:
DHCP-request of
the device
D300815 0713- BL67 Multiprotocol
12-17
Appendix
A double click on the request-entry opens the "New Entry" dialog box in which an IP address can be
assigned to the s MAC-ID.
Figure 12-14:
Setting the IP
address via DHCP
The BootP/DHCP-Server sends the IP Address via BootP/DHCP to the device and, after a few seconds,
the stations answers with its new IP address when having stored it.
Figure 12-15:
Set IP address
Attention
The device looses it's IP-address in case of a power-reset, if the BootP/DHCP-server is shut
down.
12-18
D300815 0713- BL67 Multiprotocol
Nominal current consumption of modules on Ethernet
12.5
Nominal current consumption of modules on Ethernet
Table 12-5:
Nominal current
consumption of
modules on
Ethernet
Module
Nominal current consumptions at 24 V DC
BL67-GW-EN
Power distribution modules
BL67-PF-24VDC
≤ 9 mA
Digital input modules
BL67-4DI-P
≤ 9 mA
BL67-8DI-P
≤ 9 mA
BL67-4DI-PD
≤ 9 mA
BL67-8DI-PD
≤ 9 mA
BL67-4DI-N
≤ 9 mA
BL67-8DI-N
≤ 9 mA
BL67-16DI-P
≤ 9 mA
Analog input modules
BL67-2AI-I
≤ 10 mA
BL67-2AI-V
≤ 10 mA
BL67-2AI-PT
≤ 13 mA
BL67-2AI-TC
≤ 13 mA
BL67-4AI-TC
≤ 15 mA
BL67-4AI-V/I
≤ 12 mA
Digital output modules
BL67-4DO-0.5A-P
≤ 9 mA
BL67-4DO-2A-P
≤ 9 mA
BL67-4DO-4A-P
≤ 9 mA
BL67-8DO-0.5A-P
≤ 9 mA
BL67-4DO-2A-N
≤ 9 mA
BL67-8DO-0.5A-N
≤ 9 mA
BL67-8DO-R-NO
≤ 9 mA
BL67-16DO-0.1A-P
≤ 9 mA
Analog output modules
BL67-2AO-I
D300815 0713- BL67 Multiprotocol
≤ 12 mA
12-19
Appendix
Table 12-5:
Nominal current
consumption of
modules on
Ethernet
Module
Nominal current consumptions at 24 V DC
BL67-2AO-V
≤ 18 mA
BL67-4AO-V
≤ 15 mA
Digital combi modules
BL67-4DI4DO-PD
≤ 9 mA
BL67-8XSG-PD
≤ 9 mA
BL67-8XSG-P
≤ 9 mA
Analog combi modules
Analog combi modules
BL67-4AI4AO-V/I
≤ 15 mA
BL67-2AI42O-V/I
≤ 15 mA
Technology modules
BL67-1RS232
≤ 50 mA
BL67-1RS485/422
≤ 20 mA
BL67-1SSI
≤ 15 mA
BL67-1CVI
≤ 9 mA
BL67-2RFID-x
≤ 9 mA
BL67-1CNT/ENC
≤ 15 mA
Note
Please find any information about the bus-independent, module specific current
consumptions in the manual "BL67- I/O-modules" (TURCK-Documentation No.: German
D300572; English D300529).
12-20
D300815 0713- BL67 Multiprotocol
Ident codes of the BL67-modules
12.6
Ident codes of the BL67-modules
Each module is identified by the gateway using a unique identifier.
Table 12-6:
Module
ident codes
Module
ident code
Digital input modules
BL67-4DI-P
0×410030××
BL67-8DI-P
0×610040××
BL67-4DI-PD
0×015630××
BL67-8DI-PD
0×015640××
BL67-4DI-N
0×420030××
BL67-8DI-N
0×620040××
BL67-16DI-P
0×820050××
Analog input modules
BL67-2AI-I
0×225570××
BL67-2AI-V
0×235570××
BL67-2AI-PT
0×215770××
BL67-2AI-TC
0×215570××
BL67-4AI-TC
0×427790××
BL67-4AI-V/I
0×417790××
Digital output modules
BL67-4DO-0.5A-P
0×413003××
BL67-4DO-2A-P
0×433003××
BL67-4DO-4A-P
0×453003××
BL67-8DO-0.5A-P
0×614004××
BL67-16DO-0.1A-P
0×805505××
BL67-4DO-2A-N
0×443003××
BL67-8DO-0.5A-N
0×624004××
BL67-16DO-0.1A-P
0×805505xx
Analog output modules
BL67-2AO-I
0×220807××
BL67-2AO-V
0×210807××
BL67-4AO-V
0×427A09××
D300815 0713- BL67 Multiprotocol
12-21
Appendix
Table 12-6:
Module
ident codes
Module
ident code
Relay modules
BL67-8DO-R-NO
0×62004××
Digital combi modules
BL67-4DI4DO-PD
0×015633××
BL67-8XSG-PD
0×015744××
BL67-8XSG-P
0×025744××
Analog combi modules
BL67-4AI4AO-V/I
0×419B99××
BL67-2AI42O-V/I
0×217977××
technology modules
ADefault ID of the
module → Is
only transmitted
if the field voltage is missing
during module
power-up
BL67-1RS232
0×014799××
BL67-1RS485/422
0×024799××
BL67-1SSI
0×044799××
BL67-1CVI
0×018B99×× (0×242224××) A
BL67-1CNT/ENC
0×019BA9××
BL67-2RFID-S
0×2179CC××
BL67-2RFID-A
0×017977××
Power distribution modules
BL67-PF-24VDC
12-22
0×063000××
D300815 0713- BL67 Multiprotocol
13 Glossary
A
Acknowledge
Acknowledgment of a signal received.
Active metal component
Conductor or conducting component that is electrically live during operation.
Address
Identification number of, e.g. a memory position, a system or a module within a network.
Addressing
Allocation or setting of an address, e. g. for a module in a network.
ARP
Used to definitely allocate the hardware addresses (MAC-IDs) assigned worldwide to the IP addresses of the
network clients via internal tables.
Analog
Infinitely variable value, e. g. voltage. The value of an analog signal can take on any value, within certain limits.
Automation device
A device connected to a technical process with inputs and outputs for control. Programmable logic controllers
(PLC) are a special group of automation devices.
B
Baud
Baud is a measure for the transmission speed of data. 1 Baud corresponds to the transmission of one bit per
second (bit/s).
Baud rate
Unit of measurement for measuring data transmission speeds in bit/s.
Bidirectional
Working in both directions.
Bonding strap
Flexible conductor, normally braided, that joins inactive components, e. g. the door of a switchgear cabinet to the
cabinet main body.
Bus
Bus system for data exchange, e. g. between CPU, memory and I/O levels. A bus can consist of several parallel
cables for data transmission, addressing, control and power supply.
Bus cycle time
Time required for a master to serve all slaves or stations in a bus system, i.e. reading inputs and writing outputs.
Bus line
Smallest unit connected to a bus, consisting of a PLC, a coupling element for modules on the bus and a module.
D301173 0313 - BL20- Ethernet multiprotocol gateway
13-1
Glossary
Bus system
All units which communicate with one another via a bus.
C
Capacitive coupling
Electrical capacitive couplings occur between cables with different potentials. Typical sources of interference are,
for example, parallel-routed signal cables, contactors and electrostatic discharges.
Check-back interface
The check-back interface is the interface from the counter module to the internal module bus. The bits and bytes
are converted by the gateway from the respective type of communication applicable to the fieldbus in to the
module-specific bits and bytes.
Coding elements
Two-piece element for the unambiguous assignment of electronic and base modules.
Configuration
Systematic arrangement of the I/O-modules of a station.
Control interface
The control interface is the interface from the internal module bus to the counter module. The commands and
signals directed to the counter module are converted by the gateway from the respective type of communication
applicable to the fieldbus in to the module-specific bits and bytes.
CPU
Central Processing Unit. Central unit for electronic data processing, the processing core of the PC.
D
DHCP
Client-Server-protocol which reduces the effort of assigning IP addresses or other parameters. Serves for dynamic
and automatic configuration of devices.
Digital
A value (e. g. a voltage) which can adopt only certain statuses within a finite set, mostly defined as 0 and 1.
DIN
German acronym for German Industrial Standard.
E
EIA
Electronic Industries Association – association of electrical companies in the United States.
Electrical components
All objects that produce, convert, transmit, distribute or utilize electrical power (e. g. conductors, cable, machines,
control devices).
EMC
Electromagnetic compatibility – the ability of an electrical part to operate in a specific environment without fault
and without exerting a negative influence on its environment.
13-2
D301173 0313 - BL20- Ethernet multiprotocol gateway
EN
German acronym for European Standard.
ESD
Electrostatic Discharge.
F
Field power supply
Voltage supply for devices in the field as well as the signal voltage.
Fieldbus
Data network on sensor/actuator level. A fieldbus connects the equipment on the field level. Characteristics of a
fieldbus are a high transmission security and real-time behavior.
Force Mode
Software mode which enables the user to set his plant to a required state by forcing certain variables on the input
and output modules.
G
GND
Abbreviation of ground (potential "0").
Ground
Expression used in electrical engineering to describe an area whose electrical potential is equal to zero at any
given point. In neutral grounding devices, the potential is not necessarily zero, and one speaks of the ground
reference.
Ground connection
One or more components that have a good and direct contact to earth.
Ground reference
Potential of ground in a neutral grounding device. Unlike earth whose potential is always zero, it may have a
potential other than zero.
H
Hexadecimal
System of representing numbers in base 16 with the digits 0… 9, and further with the letters A, B, C, D, E and F.
Hysteresis
A sensor can get caught up at a certain point, and then "waver" at this position. This condition results in the
counter content fluctuating around a given value. Should a reference value be within this fluctuating range, then
the relevant output would be turned on and off in rhythm with the fluctuating signal.
I
I/O
Input/output.
Impedance
Total effective resistance that a component or circuit has for an alternating current at a specific frequency.
D301173 0313 - BL20- Ethernet multiprotocol gateway
13-3
Glossary
Inactive metal components
Conductive components that cannot be touched and are electrically isolated from active metal components by
insulation, but can adopt voltage in the event of a fault.
Inductive coupling
Magnetic inductive couplings occur between two cables through which an electrical current is flowing. The
magnetic effect caused by the electrical currents induces an interference voltage. Typical sources of interference
are for example, transformers, motors, parallel-routed network and HF signal cables.
Intelligent modules
Intelligent modules are modules with an internal memory, able to transmit certain commands (e. g. substitute
values and others).
IP
Abbreviation for Internet-Protocol, protocol for the packet-oriented and connectionless transport of data packets
from a transmitter to a receiver crossing different networks.
L
Lightning protection
All measures taken to protect a system from damage due to overvoltages caused by lightning strike.
Low impedance connection
Connection with a low AC impedance.
LSB
Least Significant bit
M
Mass
All interconnected inactive components that do not take on a dangerous touch potential in the case of a fault.
Master
Station in a bus system that controls the communication between the other stations.
Modbus TCP
The Modbus protocol is part of the TCP/IP protocol.
The communication is realized via function codes, which are implemented into the data telegram. Modbus TCP
uses the Transmission Control Protocol (TCP) for the transmission of the Modbus user protocol in Ethernet-TCPIP networks.
Module bus
The module bus is the internal bus in a station. The modules communicate with the gateway via the module bus
which is independent of the fieldbus.
MSB
Most Significant bit
P
Ping
Implementation of an echo-protocol, used for testing whether a particular host is operating properly and is
reachable on the network from the testing host.
13-4
D301173 0313 - BL20- Ethernet multiprotocol gateway
PLC
Programmable Logic Controller.
Potential compensation
The alignment of electrical levels of electrical components and external conductive components by means of an
electrical connection.
Potential free
Galvanic isolation of the reference potentials in I/O-modules of the control and load circuits.
Potential linked
Electrical connection of the reference potentials in I/O-modules of the control and load circuits.
Protective earth
Electrical conductor for protection against dangerous shock currents. Generally represented by PE (protective
earth).
R
Radiation coupling
A radiation coupling appears when an electromagnetic wave hits a conductive structure. Voltages and currents
are induced by the collision. Typical sources of interference are for example, sparking gaps (spark plugs,
commutators from electric motors) and transmitters (e. g. radio), that are operated near to conducting structures.
Reaction time
The time required in a bus system between a reading operation being sent and the receipt of an answer. It is the
time required by an input module to change a signal at its input until the signal is sent to the bus system.
Reference potential
Potential from which all voltages of connected circuits are viewed and/or measured.
Repeater
Amplifier for signals transmitted via a bus.
Root-connecting
Creating a new potential group using a power distribution module. This allows sensors and loads to be supplied
individually.
RS 485
Serial interface in accordance with EIA standards, for fast data transmission via multiple transmitters.
S
Serial
Type of information transmission, by which data is transmitted bit by bit via a cable.
Setting parameters
Setting parameters of individual stations on the bus and their modules in the configuration software of the
master.
Shield
Conductive screen of cables, enclosures and cabinets.
D301173 0313 - BL20- Ethernet multiprotocol gateway
13-5
Glossary
Shielding
Description of all measures and devices used to join installation components to the shield.
Short-circuit proof
Characteristic of electrical components. A short-circuit proof part withstands thermal and dynamic loads which
can occur at its place of installation due to a short circuit.
Station
A functional unit or I/O components consisting of a number of elements.
T
TCP
Abbreviation for Transmission Control Protocol, connection-oriented transport protocol within the Internet
protocol suite. Certain error detection mechanisms (i.e. acknowledgements, time-out monitoring) can guarantee
a safe and error free data transport.
Terminating resistance
Resistor on both ends of a bus cable used to prevent interfering signal reflections and which provides bus cable
matching. Terminating resistors must always be the last component at the end of a bus segment.
To ground
Connection of a conductive component with the grounding connection via a grounding installation.
Topology
Geometrical structure of a network or the circuitry arrangement.
U
UDP
Abbreviation for User Datagram Protocol. UDP is an transport protocol for the connectionless data between
Ethernet hosts.
Unidirectional
Working in one direction.
13-6
D301173 0313 - BL20- Ethernet multiprotocol gateway
14
Index
A
acyclic services ............................................................. 8-13
address assignment ............................................. 3-15, 8-2
B
base modules ................................................................. 2-5
basic concept ................................................................. 2-2
block diagram, station ................................................. 11-4
C
Cable routing ................................................................ 11-2
cable shield ................................................................... 11-7
classes
–Assembly Object .......................................................... 4-8
–Ethernet Link Object .................................................. 4-15
–Ethernet/IP standard .................................................... 4-5
–Identity Object ............................................................. 4-6
–process data ............................................................... 4-24
–TCP/IP Interface Object .............................................. 4-11
–VSC-Vendor Specific Classes ...................................... 4-20
CoDeSys
–communication path ................................................... 7-8
–communication settings .............................................. 7-7
–Ethernet-adapter ......................................................... 7-9
–Ethernet-master ........................................................... 7-9
–feature sets ................................................................... 7-4
–Global variable list ..................................................... 7-14
–localhost ....................................................................... 7-7
–Modbus-master .......................................................... 7-10
–PLC_PRG ..................................................................... 7-13
D
data image
–SSI ............................................................................... 12-6
device
–BOOTP-mode ............................................................. 3-18
DHCP mode ................................................................ 12-17
diagnosis .................................................... 8-4, 9-18, 9-19
E
earth-free operation ..................................................... 11-5
electrical installation .................................................... 11-2
electronic modules ........................................................ 2-5
electrostatic discharge ................................................. 11-8
EMC ............................................................................... 11-5
empty slot ..................................................................... 10-3
end plate ........................................................................ 2-6
error code ..................................................................... 9-19
error codes
–gateway ........................................................................ 8-4
–I/O-modules ................................................................. 8-5
F
firmware download ...................................................... 10-6
flexibility ......................................................................... 2-3
D300815 0713- BL67 Multiprotocol
G
Gateway
–block diagram ............................................................... 3-7
gateway
–address assignment ........................................... 3-15, 8-2
–Connection possibilities ............................................. 3-12
–DHCP-mode ................................................................ 3-18
–diagnostic messages .................................................. 3-31
–field bus connection .................................................. 3-12
–function ........................................................................ 3-4
–LEDs ............................................................................ 3-31
–parameters ................................................................... 8-9
–PGM-mode .................................................................. 3-19
–status indicators ......................................................... 3-31
–supply voltage .............................................................. 3-9
–technical data ............................................................... 3-6
–voltage supply ............................................................ 3-12
gateways ......................................................................... 2-4
H
hardware ......................................................................... 5-2
I
inductive loads, protective circuit ............................... 11-8
IP address, PC .............................................................. 12-12
L
lightning protection ..................................................... 11-3
M
maintenance ................................................................... 1-4
Modbus TCP
–register .......................................................................... 6-4
Module Application Instance ....................................... 8-14
module arrangement ................................................... 10-2
module diagnostics
–channel specific .......................................................... 9-19
module order ................................................................ 10-2
mounting rail ................................................................ 11-6
N
network configuration ........................................... 5-1, 7-3
O
operation, safe ................................................................ 1-4
operation, trouble-free ................................................... 1-4
outputs, error behavior ................................................ 6-19
P
PE connection ............................................................... 11-5
Pin assignment
–voltage supply ............................................................ 3-12
pin assignment
–field bus connection .................................................. 3-12
plugging, electronic modules ...................................... 10-6
14-1
Index
potential compensation .............................................. 11-8
potential compensation cable .................................... 11-8
potential groups .......................................................... 10-6
potential relationships ................................................. 11-4
Power Feeding-modules ............................................... 2-5
power loss, modules .................................................. 12-19
prescribed use ................................................................ 1-4
process data ................................................................. 4-10
process input
–SSI ............................................................................... 12-6
process input data
–RS232 .......................................................................... 12-2
process output
–SSI ............................................................................. 12-10
projecting/configuration ............................................. 10-3
protection class IP67 ...................................................... 2-2
pulling, electronic modules ......................................... 10-6
S
shield ............................................................................ 11-7
software .......................................................................... 5-2
storage ............................................................................ 1-4
Symbols .......................................................................... 1-3
symbols .......................................................................... 1-3
system extension ......................................................... 10-6
system extension, maximum ....................................... 10-4
T
Terminal Slot Class ....................................................... 4-22
transmission media ...................................................... 11-3
transport ......................................................................... 1-4
transport, appropriate ................................................... 1-4
U
use, prescribed ............................................................... 1-4
user data ....................................................................... 8-13
W
WIN 2000 .................................................................... 12-12
WIN NT ........................................................................ 12-12
WIN XP ........................................................................ 12-12
14-2
D300815 0713- BL67 Multiprotocol
Hans Turck GmbH & Co. KG
45472 Mülheim an der Ruhr
Germany
Witzlebenstraße 7
Tel. +49 (0) 208 4952-0
Fax +49 (0) 208 4952-264
E-Mail [email protected]
Internet www.turck.com
D300815 0713
www.turck.com
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement