turck BL67-8DI-P, BL67-4DI-N, BL67-8DI-PD, BL67-4DI-PD, BL67-16DI-P User Manual

USER

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

MANUAL

BL67­MULTIPROTOCOL
GATEWAY
FOR
ETHERNET

Sense it! Connect it! Bus it! Solve it!

All brand and product names are trademarks or registered

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

concerned.

trade marks of the owner

Edition 02/2015

© Hans Turck GmbH, Muelhe

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
permission of Hans Turck GmbH & Co. KG, Muelheim an der Ruhr.

Subject to alterations without notice

der Ruhr

im an

distributed by means of electronic systems without written

Table of contents

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

1About this manual

1.1 Documentation concept .................................................................................................................................1-2

1.1.1 Additional documentation .................................................................................................................................................................1-2

1.2 Explanation of symbols used..........................................................................................................................1-3

1.2.1 Further notes ...........................................................................................................................................................................................1-3

1.3 General notes...................................................................................................................................................1-4

1.3.1 Prescribed use ......................................................................................................................................................................................... 1-4

1.3.2 Notes concerning planning/installation of this product ......................................................................................................... 1-4

1.4 List of revisions ................................................................................................................................................1-5

2 BL67 philosophy

2.1 The basic concept ............................................................................................................................................2-2

2.1.1 Flexibility ...................................................................................................................................................................................................2-3

2.1.2 Easy to handle .........................................................................................................................................................................................2-3

2.2 The BL67 components.....................................................................................................................................2-4

2.2.1 Gateways ...................................................................................................................................................................................................2-4

2.2.2 Electronic modules ................................................................................................................................................................................2-5

2.2.3 Base modules...........................................................................................................................................................................................2-5

2.2.4 End plate....................................................................................................................................................................................................2-6

3 Properties: Gateway

3.1 General technical data ....................................................................................................................................3-3

3.1.1 Function.....................................................................................................................................................................................................3-3

3.1.2 Version overview .................................................................................................................................................................................... 3-3

3.2 Supported I/O-modules (protocol dependent) .............................................................................................3-4

3.3 QuickConnect (QC) and Fast Start-Up (FSU)..................................................................................................3-6

3.4 Technical data..................................................................................................................................................3-7

3.4.1 Top view BL67-GW-EN (VN < 03-00) ...............................................................................................................................................3-7

3.4.2 Top view BL67-GW-EN (VN ≥ 03-00) ...............................................................................................................................................3-8

3.4.3 Gateway structure..................................................................................................................................................................................3-8

3.4.4 Technical data..........................................................................................................................................................................................3-9

3.5 Connection options ...................................................................................................................................... 3-13

3.5.1 Fieldbus connection .......................................................................................................................................................................... 3-13

3.5.2 Voltage supply via 7/8"-connector ............................................................................................................................................... 3-14

3.5.3 Service-interface female PS/2 connector (VN < 03-00).......................................................................................................... 3-15

3.5.4 Service interface Mini-USB (VN ≥ 03-00) ..................................................................................................................................... 3-16

3.6 Address assignment ..................................................................................................................................... 3-17

3.6.1 Default setting of the gateway....................................................................................................................................................... 3-18

3.6.2 Address setting via rotary coding switch (rotary mode)....................................................................................................... 3-19

3.6.3 Address setting via BootP-mode (300)........................................................................................................................................3-20

3.6.4 Address setting via DHCP-mode (400) ........................................................................................................................................3-20

3.6.5 Address setting via PGM-mode (500) .......................................................................................................................................... 3-21

3.6.6 Address setting via the mode PGM-DHCP (universal mode, 600) ..................................................................................... 3-22

D300815 0215- BL67 multiprotocol

i

3.6.7 F_Reset (reset to factory settings, 900)....................................................................................

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.8 Addressing via I/O-ASSISTANT 3 (FDT/DTM) ............................................................................................................................. 3-23

3.6.9 Address assignment via Web server (only VN ≥ 03-00)..........................................................................................................3-26

3.7 Reset to factory settings............................................................................................................................... 3-27

3.8 Web server - remote access/configuration (only VN ≥ 03-00) ................................................................... 3-28

3.8.1 Safety in the web server ....................................................................................................................................................................3-28

3.8.2 IP address................................................................................................................................................................................................3-28

3.8.3 Home........................................................................................................................................................................................................3-29

3.8.4 Gateway Diagnostics ..........................................................................................................................................................................3-29

3.8.5 Ethernet Statistics ................................................................................................................................................................................3-30

3.8.6 Links.......................................................................................................................................................................................................... 3-31

3.8.7 Login/password....................................................................................................................................................................................3-31

3.8.8 Change Admin Password..................................................................................................................................................................3-32

3.8.9 Network Configuration ...................................................................................................................................................................... 3-33

3.8.10 Gateway Configuration .....................................................................................................................................................................3-34

3.8.11 Slot Parameters.....................................................................................................................................................................................3-35

3.8.12 Usage of mobile devices ................................................................................................................................................................... 3-36

3.8.13 Web server logout ............................................................................................................................................................................... 3-36

3.8.14 Deactivating the web server............................................................................................................................................................3-37

3.9 Status and Control Word of the BL67-stations ........................................................................................... 3-38

3.9.1 Status Word............................................................................................................................................................................................3-38

3.9.2 Control Word .........................................................................................................................................................................................3-38

....................................................3-22

3.10 SET button ..................................................................................................................................................... 3-39

3.11 Status indicators/diagnostic messages gateway ....................................................................................... 3-40

3.11.1 Diagnostic messages via LEDs ........................................................................................................................................................3-40

3.12 Parameters of the I/O-modules .................................................................................................................. 3-43

3.13 Diagnostics of the I/O-modules ................................................................................................................... 3-44

4 Implementation of EtherNet/IP™

4.1 The EtherNet/IP™ Communications Profile .................................................................................................. 4-2

4.1.1 Communications Profile for BL67 .................................................................................................................................................... 4-3

4.2 QC - QuickConnect .......................................................................................................................................... 4-4

4.2.1 General ...................................................................................................................................................................................................... 4-4

4.2.2 QuickConnect in BL67 .......................................................................................................................................................................... 4-4

4.3 Device Level Ring (DLR).................................................................................................................................. 4-6

4.4 Diagnostic messages via the process data ................................................................................................... 4-7

4.4.1 Summarized Diagnostics .................................................................................................................................................................... 4-7

4.4.2 Scheduled Diagnostics ........................................................................................................................................................................ 4-7

4.5 Classes and Instances of the EtherNet/IP™ stations..................................................................................... 4-8

4.5.1 EtherNet/IP™ Standard Classes ......................................................................................................................................................... 4-8

4.5.2 Identity Object (0×01) .......................................................................................................................................................................... 4-9

4.5.3 Assembly Object (0×04) ....................................................................................................................................................................4-11

4.5.4 TCP/IP Interface Object (0×F5)........................................................................................................................................................4-14

4.5.5 Ethernet Link Object (0×F6).............................................................................................................................................................4-18

4.5.6 DLR Object (0×47) ...............................................................................................................................................................................4-21

4.5.7 QOS Object (0×48)...............................................................................................................................................................................4-22

D300815 0215- BL67 multiprotocolii

4.6 VSC-Vendor Specific Classes........................................................................................................................ 4-23

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.6.1 Class instance of the VSC .................................................................................................................................................................. 4-23

4.6.2 Gateway Class (VSC 100, 64h) ......................................................................................................................................................... 4-24

4.6.3 Process Data Class (VSC102, 66h).................................................................................................................................................. 4-27

4.6.4 Miscellaneous Parameters Class (VSC 126) ................................................................................................................................ 4-29

5 Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)

5.1 General notes...................................................................................................................................................5-2

5.1.1 Used hard-/ software............................................................................................................................................................................. 5-2

5.2 Network configuration....................................................................................................................................5-3

5.2.1 Configuration of the network in "RS Logix 5000" .......................................................................................................................5-3

5.2.2 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 Setting outputs .................................................................................................................................................................................... 5-12

5.4.2 Example program................................................................................................................................................................................ 5-13

5.5 Activating QuickConnect ............................................................................................................................ 5-15

6 Implementation of Modbus TCP

6.1 Common Modbus description ........................................................................................................................6-2

6.2 Implemented Modbus functions....................................................................................................................6-6

6.3 Modbus registers.............................................................................................................................................6-7

6.3.1 Structure of the packed in-/output process data .................................................................................................................... 6-11

6.3.2 Register 100Ch: "Gateway status" ................................................................................................................................................. 6-14

6.3.3 Register 1130h: "Modbus connection mode" ........................................................................................................................... 6-15

6.3.4 Register 1131h: "Modbus Connection Timeout" ..................................................................................................................... 6-15

6.3.5 Register 0×113C and 0×113D: "Restore Modbus-Connection-Parameters".................................................................. 6-15

6.3.6 Register 0×113E and 0×113F: "Save Modbus-Connection-Parameters"......................................................................... 6-15

6.4 The Service Object ........................................................................................................................................ 6-16

6.5 Bit areas: mapping of input-discrete- and coil-areas ................................................................................ 6-18

6.6 Output module behavior in case of an error .............................................................................................. 6-19

7 Application example: BL67-GW-EN with Modbus TCP (CODESYS Win V3)

7.1 Used hard-/software........................................................................................................................................7-2

7.1.1 Hardware...................................................................................................................................................................................................7-2

7.1.2 Software.....................................................................................................................................................................................................7-2

7.2 Network configuration....................................................................................................................................7-3

7.3 Programming with CODESYS .........................................................................................................................7-4

7.3.1 Predefined feature sets ........................................................................................................................................................................7-4

7.3.2 Creating a new project .........................................................................................................................................................................7-5

7.3.3 Defining the communication settings............................................................................................................................................7-7

7.3.4 Adding the Ethernet Adapter ............................................................................................................................................................7-9

7.3.5 Adding the Modbus master............................................................................................................................................................. 7-10

7.3.6 Adding a Modbus TCP slave............................................................................................................................................................ 7-11

D300815 0215- BL67 multiprotocol

iii

7.3.7 Programming (example program) ..............................................................................................

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

7.3.8 CODESYS: Global variables ............................................................................................................................................................... 7-14

7.3.9 Modbus channels................................................................................................................................................................................. 7-15

7.3.10 Building, login and start ....................................................................................................................................................................7-27

7.3.11 Reading out the process data ......................................................................................................................................................... 7-29

7.3.12 Diagnosis evaluation .......................................................................................................................................................................... 7-30

..................................................7-13

8 Implementation of PROFINET

8.1 PROFINET......................................................................................................................................................... 8-2

8.2 FSU - Fast Start-Up (prioritized startup)....................................................................................................... 8-4

8.2.1 General ...................................................................................................................................................................................................... 8-4

8.2.2 FSU in BL67............................................................................................................................................................................................... 8-4

8.3 MRP (Media Redundancy Protocol)............................................................................................................... 8-5

8.4 Address assignment ....................................................................................................................................... 8-5

8.5 GSDML file ....................................................................................................................................................... 8-6

8.6 Default values ................................................................................................................................................. 8-6

8.7 Diagnosis in PROFINET ................................................................................................................................... 8-7

8.7.1 Gateway Error codes ............................................................................................................................................................................ 8-7

8.7.2 Channel-specific error codes of the I/O-modules ...................................................................................................................... 8-8

8.8 Parameterization ......................................................................................................................................... 8-12

8.8.1 Gateway parameters...........................................................................................................................................................................8-12

8.8.2 I/O module parameters .....................................................................................................................................................................8-15

8.9 Description of user data for acyclic services............................................................................................... 8-16

8.9.1 Description of the acyclic gateway user data............................................................................................................................8-16

8.9.2 Description of the acyclic module user data .............................................................................................................................8-17

9 Application example: BL67-GW-EN with PROFINET (S7)

9.1 Application example ...................................................................................................................................... 9-2

9.1.1 General ...................................................................................................................................................................................................... 9-2

9.1.2 Example network ................................................................................................................................................................................... 9-2

9.1.3 New project in the SIMATIC Manager ............................................................................................................................................ 9-3

9.1.4 Setting the PG/PC-interface ............................................................................................................................................................... 9-3

9.1.5 Installation of the GSDML-files.......................................................................................................................................................... 9-4

9.1.6 Adding PROFINET network nodes ................................................................................................................................................... 9-8

9.1.7 Configuring the BL67-station ..........................................................................................................................................................9-10

9.1.8 Scanning the network for PROFINET nodes...............................................................................................................................9-11

9.1.9 PROFINET neighborhood detection via LLDP ........................................................................................................................... 9-13

9.1.10 Online topology detection ............................................................................................................................................................... 9-16

9.1.11 Fast Start-Up - configuration of fieldbus nodes .......................................................................................................................9-17

9.2 Diagnosis with Step 7 ................................................................................................................................... 9-19

9.2.1 Diagnostic messages in the hardware configuration.............................................................................................................9-19

9.2.2 Diagnostic telegram with error code ...........................................................................................................................................9-20

10 Guidelines for station planning

10.1 Module arrangement.................................................................................................................................... 10-2

10.1.1 Random module arrangement .......................................................................................................................................................10-2

D300815 0215- BL67 multiprotocoliv

10.2 Complete planning....................................................................................................................................... 10-3

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

10.3 Maximum system extension ........................................................................................................................ 10-3

10.4 Creating potential groups ........................................................................................................................... 10-4

10.5 Plugging and pulling electronics modules................................................................................................. 10-4

10.6 Extending an existing station...................................................................................................................... 10-5

10.7 Firmware download ..................................................................................................................................... 10-6

11 Guidelines for Electrical Installation

11.1 General notes................................................................................................................................................ 11-2

11.1.1 General....................................................................................................................................................................................................11-2

11.1.2 Cable routing ........................................................................................................................................................................................ 11-2

11.1.3 Lightning protection.......................................................................................................................................................................... 11-3

11.1.4 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 Ensuring electromagnetic compatibility .................................................................................................................................... 11-5

11.3.2 Grounding of inactive metal components................................................................................................................................. 11-5

11.3.3 PE connection....................................................................................................................................................................................... 11-5

11.3.4 Earth-free operation ........................................................................................................................................................................... 11-5

11.3.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 Changing the IP address of a PC/ network interface card ......................................................................... 12-2

12.1.1 Changing the IP address in Windows .......................................................................................................................................... 12-2

12.1.2 Changing the IP address via PACTware™ FDT/DTM (I/O-ASSISTANT V3) ...................................................................... 12-4

12.2 Deactivating/ adapting the firewall in Windows ....................................................................................... 12-5

12.3 Addressing via DHCP.................................................................................................................................... 12-7

12.4 Nominal current consumption of modules on Ethernet ........................................................................... 12-9

12.5 Ident codes of the BL67-modules.............................................................................................................. 12-11

13 Glossary

14 Index

D300815 0215- BL67 multiprotocol

v

D300815 0215- BL67 multiprotocolvi

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

1 About this manual

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

1.1 Documentation concept.................................................................................................................... 2

1.1.1 Additional documentation ...............................................................................................................................................................2

1.2 Explanation of symbols used ............................................................................................................ 3

– Warnings .............................................................................................................................................................................................3

1.2.1 Further notes .........................................................................................................................................................................................3

1.3 General notes .................................................................................................................................... 4

1.3.1 Prescribed use .......................................................................................................................................................................................4

1.3.2 Notes concerning planning/installation of this product .......................................................................................................4

1.4 List of revisions ................................................................................................................................. 5

D300815 0215- BL67 multiprotocol 1-1

About this manual

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

1.1 Documentation concept

This manual contains all information about the multiprotocol-gateway of the product line BL67 (BL67­GW-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: BL6

 Modbus TCP

– chapter 6, Implementation of Modbus TCP

– chapter 7, Application example: BL67-GW-EN with Modb

 PROFINET

7-GW-EN with EtherNet/IP™ (Allen Bradley)

us TCP (CODESYS Win V3)

– chapter 8, Implementation of PROFINET

– chapter 9, Application example: BL67-GW-EN with PROFINET (S7)

Addition
electrical installation, etc.

ally, the manual contain protocol-independent guideline for station configuration, the

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-

D300815 0215- BL67 multiprotocol1-2

Explanation of symbols used

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

1.2 Explanation of symbols used

Warnings

Action-related warnings are placed next to potentially dangerous work steps and are marked by

phic symbols. Each warning is initiated by a warning sign and a signal word that expresses the grav-

gra
ity of the danger. The warnings have absolutely to be observed.

DANGER!

DANGER indicates an immediatel
injury, if not avoided.

WARNING!

WARNING indicates a potentially dangerous situatio
injury, if not avoided.

CAUTION!

WARNING indicates a potentially dangerous situatio
injury, if not avoided.

y dangerous situation, with high risk, the death or severe

n with medium risk, the death or severe

n with medium risk, the death or severe

1.2.1 Further notes

 CALL TO ACTION

This symbol identifies steps that the user has to perform.

 RESULTS OF ACTION

This symbol identifies relevant results of steps

ATTENTION!

ATTENTION indicates a situation that may lead to property

NOTE

In NOTES you find tips, recommendations and important information. The notes facilitate
work, provide more informat
ing the correct procedure.

TECHNICAL BASICS

The TECHNICAL BASICS offer technical information, basics
information lead to a better understanding of the device functions for example. The experi­enced user can skip this information.

ion on specific actions and help to avoid overtime by not follow-

damage, if it is not avoided.

and background information. This

D300815 0215- BL67 multiprotocol

1-3

About this manual

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

1.3 General notes

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-gateways. It has been
specially conceived for personnel with the necessary qualifications.

1.3.1 Prescribed use

The devices described in this manual must be used only
the respective technical descriptions, and only with certified components and devices from third party
manufacturers.

Appropriate transport, storage, deployment and mounting as well as careful operating and thorough
maintenance guarantee the trouble-free and safe operation of these devices.

in applications prescribed in this manual or in

1.3.2 Notes concerning planning/installation of this product

All respective safety measures and accident protection guidelines must be considered carefully and
without exception.

D300815 0215- BL67 multiprotocol1-4

List of revisions

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

1.4 List of revisions

In comparison to the previous manual edition, the following changes/revisions have been made.

Table 1-1:
List of revisions

Chapter Topic new changed

3 QuickConnect (QC) and Fast Start-Up (FSU) (page 3-6) x

Ethernet-connection for QC-/FSU-applications (page 3-13) x

Parameters of the I/O-modules (page 3-43) x

Diagnostics of the I/O-modules (page 3-44) x

4 QuickConnect in BL67 (page 4-4) x

Device Level Ring (DLR) (page 4-6) x

5 Activating QuickConnect (page 5-15) x

8 PROFINET (page 8-2) x

FSU - Fast Start-Up (priorisierter Hochlauf) (page 8-4) x

MRP (Media Redundancy Protokoll) (page 8-5) x

9 Fast Start-Up - configuration of fieldbus nodes (page 9-17) x

NOTE

The publication of this manual renders a

ll previous editions invalid.

D300815 0215- BL67 multiprotocol

1-5

About this manual

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

D300815 0215- BL67 multiprotocol1-6

2 BL67 philosophy

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

2.1 The basic concept.............................................................................................................................. 2

2.1.1 Flexibility .................................................................................................................................................................................................3

2.1.2 Easy to handle .......................................................................................................................................................................................3

2.2 The BL67 components ....................................................................................................................... 4

2.2.1 Gateways.................................................................................................................................................................................................4

2.2.2 Electronic modules ..............................................................................................................................................................................5

– Power feeding modules.................................................................................................................................................................5

2.2.3 Base modules.........................................................................................................................................................................................5

2.2.4 End plate..................................................................................................................................................................................................6

D300815 0215- BL67 multiprotocol 2-1

BL67 philosophy

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

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-, RS232-module,...).

A complete BL67 station counts as one station on the bus and therefore occupies one fieldbus address

given fieldbus structure.

in any
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 mod­ules are

not dependent on the fieldbus used.

D300815 0215- BL67 multiprotocol2-2

The basic concept

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

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 main­tenance purposes, without having to disconnect the field wiring from the base modules.

D300815 0215- BL67 multiprotocol

2-3

BL67 philosophy

A

B

C

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

2.2 The BL67 components

Figure 2-1:
BL67 station

A Gateway
B Electronic

e

modul

C Base module

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/O-ASSIS­TANT.

Figure 2-2:
BL67 gateway

D300815 0215- BL67 multiprotocol2-4

The BL67 components

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

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 hav­ing 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 nec­essary f
ply voltage for the outputs cannot be guaranteed.

The adjoining power supply module and modules to the left are potentially isolated.

or building groups of modules with different potentials within a BL67 station, or if the rated sup-

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

NOTE

For detailed information about the individual BL67 I/
ters 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.

O components, please refer to the chap-

D300815 0215- BL67 multiprotocol

2-5

BL67 philosophy

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Figure 2-4:
Example of a base
module

 1 × 7/8" (for Power Feeding-modules)

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 protec­tion class IP67.

Figure 2-5:
End plate

D300815 0215- BL67 multiprotocol2-6

3 Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.1 General technical data ...................................................................................................................... 3

3.1.1 Function...................................................................................................................................................................................................3

3.1.2 Version overview ..................................................................................................................................................................................3

3.2 Supported I/O-modules (protocol dependent) ................................................................................. 4

3.3 QuickConnect (QC) and Fast Start-Up (FSU)...................................................................................... 6

3.4 Technical data ................................................................................................................................... 7

3.4.1 Top view BL67-GW-EN (VN < 03-00) .............................................................................................................................................7

3.4.2 Top view BL67-GW-EN (VN ≥ 03-00) .............................................................................................................................................8

3.4.3 Gateway structure................................................................................................................................................................................8

– BL67-GW-EN < VN 03-00................................................................................................................................................................8

–BL67-GW-EN ≥ VN 03-00................................................................................................................................................................9

3.4.4 Technical data .......................................................................................................................................................................................9

3.5 Connection options ......................................................................................................................... 13

3.5.1 Fieldbus connection ........................................................................................................................................................................ 13

–BL67-GW-EN (VN ≥ 03-00)......................................................................................................................................................... 13

– Ethernet-connection for QC-/FSU-applications.................................................................................................................13

3.5.2 Voltage supply via 7/8"-connector ............................................................................................................................................. 14

3.5.3 Service-interface female PS/2 connector (VN < 03-00) .......................................................................................................15

– Connection with I/O-ASSISTANT-connection cable......................................................................................................... 15

– Connection using commercially available cables ............................................................................................................. 15

3.5.4 Service interface Mini-USB (VN ≥ 03-00)................................................................................................................................... 16

3.6 Address assignment........................................................................................................................ 17

– LED behavior................................................................................................................................................................................... 17

3.6.1 Default setting of the gateway..................................................................................................................................................... 18

– Resetting the IP-address, switch position "000" ................................................................................................................ 18

3.6.2 Address setting via rotary coding switch (rotary mode).....................................................................................................19

3.6.3 Address setting via BootP-mode (300)...................................................................................................................................... 20

3.6.4 Address setting via DHCP-mode (400) ...................................................................................................................................... 20

3.6.5 Address setting via PGM-mode (500) ........................................................................................................................................21

3.6.6 Address setting via the mode PGM-DHCP (universal mode, 600)................................................................................... 22

– Permanent IP-address assignment using the Rockwell BOOTP/DHCP-server........................................................ 22

– PROFINET ......................................................................................................................................................................................... 22

3.6.7 F_Reset (reset to factory settings, 900) ..................................................................................................................................... 22

3.6.8 Addressing via I/O-ASSISTANT 3 (FDT/DTM)...........................................................................................................................23

3.6.9 Address assignment via Web server (only VN ≥ 03-00) ....................................................................................................... 26

3.7 Reset to factory settings ................................................................................................................. 27

3.8 Web server - remote access/configuration (only VN ≥ 03-00) ......................................................... 28

3.8.1 Safety in the web server.................................................................................................................................................................. 28

3.8.2 IP address ............................................................................................................................................................................................. 28

3.8.3 Home ..................................................................................................................................................................................................... 29

3.8.4 Gateway Diagnostics .......................................................................................................................................................................29

3.8.5 Ethernet Statistics ............................................................................................................................................................................. 30

3.8.6 Links ....................................................................................................................................................................................................... 31

3.8.7 Login/password ................................................................................................................................................................................. 31

D300815 0215- BL67 multiprotocol 3-1

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.8 Change Admin Password.......................................................................................................

3.8.9 Network Configuration....................................................................................................................................................................33

– Change network parameters (port settings, IP address, etc.)........................................................................................33

3.8.10 Gateway Configuration ...................................................................................................................................................................34

– Configuration of the field bus interface ................................................................................................................................34

– Reboot ...............................................................................................................................................................................................34

– Reset to Factory Defaults............................................................................................................................................................34

3.8.11 Slot Parameters ..................................................................................................................................................................................35

– Parameterization of the in-/outputs.......................................................................................................................................35

3.8.12 Usage of mobile devices .................................................................................................................................................................36

3.9 Web server logout........................................................................................................................... 37

3.9.1 Deactivating the web server..........................................................................................................................................................37

3.10 Status and Control Word of the BL67-stations................................................................................38

3.10.1 Status Word .........................................................................................................................................................................................38

– Meaning of the status bits..........................................................................................................................................................38

3.10.2 Control Word.......................................................................................................................................................................................38

3.11 SET button....................................................................................................................................... 39

3.12 Status indicators/diagnostic messages gateway............................................................................ 40

3.12.1 Diagnostic messages via LEDs ......................................................................................................................................................40

.........................................................32

3.13 Parameters of the I/O-modules ...................................................................................................... 43

3.14 Diagnostics of the I/O-modules....................................................................................................... 44

D300815 0215- BL67 multiprotocol3-2

General technical data

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.1 General technical data

3.1.1 Function

The BL67-GW-EN (> VN 03-00) is used as multiprotocol-interface between the BL67-system and the
Ethernet-protocols Modbus TCP, EtherNet/IP™ and PROFINET.

3.1.2 Version overview

Please observe, that the previous versions of the gateway did not support all protocols.

 Version < VN 03-0

BL67-gateway supports only the Ethernet protocol

–Modbus TCP

 Version VN

BL67-gateway supports the Ethernet protocols

–Modbus TCP

0

03-01

– EtherNet/IP™

 Version ≥ VN

BL67-gateway supports the Ethernet protocols

–Modbus TCP

– EtherNet/IP™

–PROFINET

03-02

NOTE

´The multi protocol Ethernet gateway replaces all previous versions and is completely
compatible.

On

ly the LED-designation has changed. Please find detailed information under Diagnostic

messages via LEDs (page 3-40).

D300815 0215- BL67 multiprotocol

3-3

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.2 Supported I/O-modules (protocol dependent)

Table 3-1:

List of supported
modules

Module EtherNet/IP™ Modbus TCP PROFINET

Digital input modules

BL67-4DI-P

BL67-4DI-N

BL67-4DI-PD

BL67-8DI-P

BL67-4DI-N

BL67-8DI-PD

BL67-16DI-P















Analog input modules

BL67-2AI-I

BL67-2AI-V

BL67-2AI-PT

BL67-2AI-TC









BL67-4AI-TC

BL67-4AI-V/I

Digital output modules

BL67-4DO-0.5A-P

BL67-4DO-2A-P

BL67-4DO-2A-N

BL67-4DO-4A-P

BL67-8DO-0.5A-P

BL67-8DO-0.5A-N

BL67-16DO-0.1A-P

Analog output modules

BL67-2AO-I

BL67-2AO-V

BL67-4AO-V

Relay modules

























BL67-8DO-R-NO



D300815 0215- BL67 multiprotocol3-4

Supported I/O-modules (protocol dependent)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Table 3-1:

List of supported
modules

Module EtherNet/IP™ Modbus TCP PROFINET

Digital combi modules

BL67-4DI4DO-PD

BL67-8XSG-P

BL67-8XSG-PD







Analog combi modules

BL67-2AI2AO-V/I

BL67-4AI4AO-V/I





Technology modules

BL67-1RS232

BL67-1RS485/422

BL67-1SSI

BL67-1CVI

BL67-1CNT/ENC











BL67-2RFID-A

BL67-2RFID-S

Power distribution modules

BL67-PF-24VDC







D300815 0215- BL67 multiprotocol

3-5

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.3 QuickConnect (QC) and Fast Start-Up (FSU)

The gateway BL67-GW-EN (VN ≥ 03-00) supports QuickConnect- and Fast Start-Up (see also QuickCon-

nect in BL67 (page 4-4) or PROFINET (page 8-2).

The following table shows the BL67 electronic modules, which are ready for QuickConnect or respec­tively Fast Start-Up.

Table 3-2:
Modules ready for
QuickConnect or
Fast Start-Up
BL67 modules

Module Ready for QC/FSU from VN

BL67-4DI-P VN 01-03

BL67-4DI-PD

VN 01-07

BL67-8DI-P VN 01-03

BL67-8DI-PD VN 01-06

BL67-16DI-P VN 01-01

BL67-4DO-0.5A-P VN 01-07

BL67-4DO-2A-P VN 01-07

BL67-4DO-4A-P VN 01-01

BL67-8DO-0.5A-P VN 01-07

BL67-16DO-0.1A-P VN 01-07

BL67-8XSG-P VN 01-01

BL67-8XSG-PD VN 01-06

BL67-4DI4DO-PD VN 01-06

BL67-PF-24VDC VN 01-03

NOTE

The start up behavior of the complete BL67-sta

tion is changed if modules which are not ready
for QC or FSU are used within a station. The start up time of a station is determined by the
slowest module.
In this case, QuickConnect or respectively Fast Start-Up can not be guaranteed.

D300815 0215- BL67 multiprotocol3-6

Technical data

A

C

E

G

H

F

I

J

K

D

B

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.4 Technical data

3.4.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

page 3-39)

(s.

E Service interface
F Rotary coding

switches

G Module bus LED
H Designation
I Status LED
J LEDs for the

er supply

Pow
monitoring

K Ethernet LEDs

D300815 0215- BL67 multiprotocol

3-7

Properties: Gateway

A

C

E

G

H

F

I

J

K

D

B

mC

V

i

5 VDC

24 VDC

BL67­Systembus

communi-

cation

bus

V

0

Power

bus

V

sens

PE
GND

service

interface

5

4

3

2

1

Ethernet

interface

short circuit

protection

memory

module bus

interface

PS/2

Ethernet

3

2

1

4

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.4.2 Top view BL67-GW-EN (VN ≥ 03-00)

Figure 3-2:
Top view BL67-

≥

GW-EN (VN

00)

A Power supply
B Ethernet 1
C Ethernet 2
D SET button

page 3-39)

(s.

E Service-inter-

ace, no function

f

F Rotary coding

switches

G Module bus LED
H Designation
I Status LED
J LEDs for the

Pow
monitoring

K Ethernet LEDs

03-

er supply

3.4.3 Gateway structure

BL67-GW-EN < VN 03-00

The BL67 gateway has the following structure:

gure 3-3:

Fi
Gateway struc­ture < VN 03-00

D300815 0215- BL67 multiprotocol3-8

Technical data

mC

V

i

5 VDC

24 VDC

BL67­system bus

Communi-’

cation

bus

V

0

Power

bus

V

sens

PE
GND

5

4

3

2

1

Short circuit

protection

Memory

Module bus
interface

Eth1

2

1

4

3

Service

USB

Switch

2

1

4

3

Eth2

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Figure 3-4:
Gateway struc-

≥

VN 03-00

ture

BL67-GW-EN ≥ VN 03-00

The BL67 gateway has the following structure:

3.4.4 Technical data

Table 3-3:
Technical data
Ethernet gateway

Supply voltage

Requirements for the power supply according to EN 61131-2

Sy

stem supply V

)24 V DCused to generate the galvani-

I (UB

Permissible range 18 to 30 VDC

Field supply V

(UL)24 V DC

O

Permissible range 18 to 30 VDC

I

sys

I

MB

I

VI

600 mA current consumption CPU +

max. 1.3 A maximum output current of

max. 4 A short-circuit and overload pro-

cally isolated module bus sup­ply

module bus at maximum sys­tem extension

module bus supply

tection of the sensor supply
from gateway or power feeding
module

D300815 0215- BL67 multiprotocol

3-9

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Protocol properties

Modbus TCP

Addr

Supported Function Codes FC1, FC2, FC3, FC4, FC5, FC6, FC15, FC16, FC23

Number of connections 8

EtherNet/IP™

Address assignment according to EtherNet/IP™ standard

Quick Connect (QC) < 150 ms see QuickConnect (QC) and Fast

ess assignment Static IP (rotary coding switches), BOOTP, DHCP

Start-Up (FSU) (page 3-6)

Device Level Ring (DLR) supported (≥ VN 03-

04)

see Device Level Ring (DLR)

(page 4-6)

Number of connections 3

PROFINET

Address assignment DCP

MinCycleTime 1 ms

Fast Start-Up (FSU) < 150 ms see QuickConnect (QC) and Fast

Start-Up (FSU) (page 3-6)

Diagnosis according to PROFINET Alarm Handling

Topology detection supported

Automatic address assignment supported

Media Redundancy Protocol (MRP) supported (³VN 03-

04)

see MRP (Media Redundancy

Protokoll) (page 8-5)

LLDP supported see PROFINET neighborhood

detection via LLDP (page 9-13)

Isolation voltages

(Ethernet/service interface) 500 V AC

U

RS

U

EN

500 V AC

(Ethernet/module bus)

U

sys

(VO/VI to U

U

field

sys

/service interface

)

1000 V DC

1000 V DC

Ambient conditions

Ambient temperature

–t

–t

40 to +70 °C/-40 to 158 °F

Ambient

40 to +85 °C/-40 to 185 °F

Store

D300815 0215- BL67 multiprotocol3-10

Technical data

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

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

–SO

2

–H

S 1.0 ppm (rel. humidity < 75 %, no condensation)

2

10 ppm (rel. humidity < 75 %, no condensation)

Vibration resistance according to IEC 61131-2

– 10 to 57 Hz, constant amplitude 0.075

yes

mm/ 0.003 inch, 1 g

– 57 to 150 Hz, constant acceleration 1 g 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, semi-sinusoidal 15 g

threshold/11 ms, each in ± direction per space coordi­nate

Repetitive shock resistance according to IEC 68-2-29, 1000 shocks, semi-sinusoidal

25 g threshold/6 ms, each in ± direction per space coor­dinate

Drop and topple/

according to IEC 68-2-31/IEC 68-2-32 1

free fall

– Height of fall (weight < 10 kg) 1.0 m

– Height of fall (weight 10 to 40 kg) 0.5 m

–Test runs 7

Emitted interference

High-frequency, radiated acc. to EN 55011 class A

Electromagnetic compatibility (EMC) according to EN 61131-2/EN 50082-2 (industry)

Static electricity according to EN 61 000­4-2

– Discharge through air (direct) 8 kV

– 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

D300815 0215- BL67 multiprotocol

3-11

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

A I/O-line-length ≤

30 m

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

Reliability

Pull/plug cycles of electronic modules 20

Housing material PC-V0 (Lexan)

Size

Width x length x height (mm/inch) 64,5 × 145,0 × 77,5/2,54 × 5,71 × 3,05

WARNING!

This device can cause radio disturbances in residential

areas and in small industrial areas (res­idential, business and trading). In this case, the operator can be required to take appropriate
measures to suppress the disturbance at his own cost.

D300815 0215- BL67 multiprotocol3-12

Connection options

3

2

1

4

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.5 Connection options

3.5.1 Fieldbus connection

Table 3-4:
Fieldbus connec­tion

Figure 3-5:
M12 female con­nector

Table 3-5:
Pin assignment

BL67-GW-EN (VN ≥ 03-00) BL67-GW-EN (VN < 03-00)

Ethernet connection 2 x M12 (female connector)

M1

2 Ethernet-switch,
4 pole, D-coded
acc. to IAONA specification

BL67-GW-EN (VN ≥ 03-00)

The switch allows linear topology.

Pin-no.

1 TD+ Transmission Data +

2 RD+ Receive Data +

3 TD- Transmission Data -

4 RD- Receive Data -

Ethernet-connection for QC-/FSU-applications

1 x M12 (female connector)
4 pole, D-coded
acc. to IAONA specification

NOTE

Please observe the following for QuickConnect (
– do not use a crossover-cable

–

ETH1 = connector for incoming Ethernet-line
ETH1 = connector for outgoing Ethernet-line

–

QC)- and Fast Start-Up (FSU)-applications:

D300815 0215- BL67 multiprotocol

3-13

Properties: Gateway

3

2

51

4

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.5.2 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­tor for power sup­ply

Table 3-6:
Pin assignment of

7/8" connector

the

Pin-

Color 7/8" Designation

No.

1 Black GND

2 blue GND

3 green/yellow PE Protective earth

4 Brown V

) Feed-in of nominal voltage for input modules

I (UB

(sensor supply V
of the system supply voltage

5 white V

(UL) Feed-in of nominal voltage for output modules

O

(can be switched off separately).

)); also used for the generation

sens

D300815 0215- BL67 multiprotocol3-14

Connection options

34

61

52

54321

9678

34

1

6

2

5

12345

6987

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.5.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 soft­ware 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 (IOASS

Ident-no.: 6827133)

 Commercially available PS/2 cable with adapter cable SUB-D/PS/2

on with I/O-ASSISTANT-connection cable

Figure 3-7:
PS/2 male con­nector on the con­nection cable to
the gateway (top
view)

Connecti

The I/O-ASSISTANT-cables have a PS/2 male connector (connection for female connector on gateway)

d a SUB-D female connector (connection for male connector on PC).

an

ISTANT-ADAPTERKABEL-BL20/BL67;

Figure 3-8:
9-pole SUB-D
female connector
on the cable for
connecting to PC
(top view)

Figure 3-9:
PS/2 male con­nector on the con­nection cable to
the gateway (top
view)

Connection using commercially available cables

A further possibility to connect PC an

d 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 exten-

sion cable)

 1 x adapter cable (PS/2 female connector/SUB-D female connector) (commercially available exten-

sion cable for a PC mouse)

Figure 3-10:
PS/2 female con­nector on the
gateway (top
view)

D300815 0215- BL67 multiprotocol

3-15

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Pin assignment

e table below shows the pin assignment when using a PS/2 cable and adapter:

Th

Table 3-7:
Pin assignment
when using PS/2
cable and adapter

A not supported

by all adapter
cables

PS/2 9-pole serial interface on PC

Pin-no. Standard

PS/2 mal
nector

e con-

BL67 gateway:
PS/2 female
connector

1CLK+5 V

(from gate­way)

2 GND GND 5 GND

3DATAnot used––

4 n.c. (DATA2) TxD 2 RxD

5+5 V/CtrlMode7RTS

6 n.c. (CLK2) RxD 3 TxD

3.5.4 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.

Pin-no. Male connector

A DTR, DSR

4, 6

D300815 0215- BL67 multiprotocol3-16

Address assignment

x10

x1

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

000: 192.168.1.254
1 - 254: static rotary
300: BootP
400: DHCP
500: PGM
600: PGM-DHCP
900: F_Reset

x 100

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6 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

ATTENTION!

Deficient screwing

Protectio

 Tighten the screws in the base modules correctly.

ATTENTION!

Damaged sealing

Protectio

 Check the sealing at the left module bus connector of the base modules for correct fit and
damage.

module bus.

n class IP 67 not guaranteed

n class IP 67 not guaranteed

Figure 3-11:
Rotary coding
switches at the
gateway

LED behavior

T

During the start-up, the flashing LED "BUS" (red/green) displays that
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.

the station is waiting for address

D300815 0215- BL67 multiprotocol

3-17

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.1 Default setting of the gateway

The object provides the following control functions:

IP address 192.168.1.254
subnet mask 255.255.255.0
default gateway 192.168.1.1

NOTE

The stations can be reset by the user to these
To reset the module, set the three coding-switches on the gateway to "000" followed by a
power-on reset.

NOTE

After every change of the address-mode, a v

Resetting the IP-address, switch position "000"

With this setting the DIP-switches to "00

192.168.1.254 for IP-based services (seeDefault setting of the gateway (page 3-18)).

default settings at any time.

oltage reset must be carried done.

0" followed by a voltage reset, the module is set to the address

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 IP address to the default values.

the device to another mode after having reset

D300815 0215- BL67 multiprotocol3-18

Address assignment

×10

×1

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

100×

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.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

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

rotary mode.

NOTE

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.

NOTE

After changing the position of the rotary coding-switches, a

voltage reset must be carried out

to store the new address.

D300815 0215- BL67 multiprotocol

3-19

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.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
server, are stored in the module’s EEPROM.

If the gateway is subsequently switched to rotary- or PGM-mode, the settings carried out via
BootP (IP address, subnet mask, etc) will be read from the module’s EEPROM.

3.6.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-7).

In order to activate the DHCP-mode, the rotary coding-switches have to be set to "400".

assigned to the gateway by the BootP-

NOTE

The IP address, as well as the default subnet mask
server, are stored in the module’s EEPROM.

If the gateway is subsequently switched to rotary- or PGM-mode, the settings carried out via
BootP (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

 In "dynamic allocation", DHCP assigns an IP address to

time, or until the client explicitly relinquishes the address, the address can be re-assigned.

 In "manual allocation", a client's IP address is assign

used simply to convey the assigned address to the client.

PROFINET

Please assure, that in PROFINET-applications, the address assigned
the address, which is assigned in the configuration tool.

DHCP-server assigns a permanent IP address to a client.

assigned to the gateway by the DHCP-

a client for a limited period of time. After this

ed by the network administrator, and DHCP is

via a BootP-server corresponds to

D300815 0215- BL67 multiprotocol3-20

Address assignment

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.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, subn
ule’s internal EEPROM.

PROFINET

Please assure, that in PROFINET-applications, the
corresponds to the address, which is assigned in the configuration tool.

et mask, etc.) are read from the mod-

address assigned via a I/O-ASSISTANT 3 (FDT/DTM)

D300815 0215- BL67 multiprotocol

3-21

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.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 V3 (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-7)).

Permanent IP-address assignment using the Rockwell BOOTP/DHCP-server

The Rockwell BOOTP/DHCP-server can also be use

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

d to assign a permanent IP-address.

modules.

3.6.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 IP address to the default values.

the device to another mode after having reset

D300815 0215- BL67 multiprotocol3-22

Address assignment

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.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 according
to the application by using the Busaddress Management function of the BL Service Ethernet interface
(TCP/IP) in the software I/O-ASSISTANT 3 (FDT/DTM).

Figure 3-13:
Busaddress
management

D300815 0215- BL67 multiprotocol

3-23

Properties: Gateway

A

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Figure 3-14:

arching

Se
network­Nodes in the
Busaddress
management

A Search function

in the Busad­dress manage­ment

NOTE

The access of the II/O-ASSISTANT 3 (FDT/DTM) to the sta

tion is only possible, if the station

already has an IP-address (see Address assignment (page 3-17))
and if it is operated in switch position PGM or PGM-DHCP-mode.

NOTE

When using Windows XP as operating system, difficultie

s 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.

D300815 0215- BL67 multiprotocol3-24

Address assignment

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Figure 3-15:

IP address
Change IP address

D300815 0215- BL67 multiprotocol

3-25

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.6.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) (παγε 3 28).

NOTE

The access of the web server to the station is only possible
address, Address assignment (page 3-17).

and if it is operated in switch position PGM or PGM-DHCP-mode.

Figure 3-16:

Web server with
network
Configuration

, if the station already has an IP

D300815 0215- BL67 multiprotocol3-26

Reset to factory settings

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.7 Reset to factory settings

Besides the hardware rest using the rotary coding switches (seeF_Reset (reset to factory settings, 900)

(page 3-22)), the TURCK IP Address Tool as well as the web server (see Reset to Factory Defaults (page
3-34)) offer the possibility to reset the devices to the factory settings.

Figure 3-17:
IP Address Tool,
reset to factory
settings

Figure 3-18:
Web server reset
to factory settings

r

D300815 0215- BL67 multiprotocol

3-27

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8 Web server - remote access/configuration (only VN ≥ 03-00)

3.8.1 Safety in the web server

In the web server, a default-password is assigned in the BL67-devices for the administrator access.

We strongly recommend to use an individual password,
third party!

This should be done in the context of the network se
the modules are placed.

3.8.2 IP address

In the delivery status, neither an address nor a PROFINET name is stored into the devices.

In order to be able to access the device per web server, the web server can be opened using the IP
address 192.168.1.254.

If the PC used for the configuration is situated in the same IP network, page

http://192.168.1.254

can be opened in order to initially change some settings.

in order to avoid possible misuse by a

curity concept for the complete facility in which

D300815 0215- BL67 multiprotocol3-28

Web server - remote access/configuration (only VN ≥ 03-00)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.3 Home

The web server's start page shows general device information, network settings, etc.

The menu items "Station Diagnostics", "Ethernet Statistics" and "Links" can also be accessed read-only
without an administrator access.

Figure 3-19:
"Home" page of
the web server of
the BL67-gateway

3.8.4 Gateway Diagnostics

Diagnostic messages of the device are displayed on the "Gateway Diagnostics"-page.

Figure 3-20:
Diagnostics in the
web server

D300815 0215- BL67 multiprotocol

3-29

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.5 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.

Figure 3-21:
Ethernet Statistics

D300815 0215- BL67 multiprotocol3-30

Web server - remote access/configuration (only VN ≥ 03-00)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.6 Links

This page contains for example a link to the product page on the TURCK-homepage.

3.8.7 Login/password

In order to obtain administrator rights and thus full access to the extended functions of the web server
(Network Configuration, Station Configuration, etc.), you have to log-on to the web server as adminis­trator.

For the first login use the default password "password".

The default-password should be changed by the administrator. To do so, please follow the instructions
under Change Admin Password (page 3-32).

NOTE

Executing the "Reset to Factory Default

s" also resets the password to "password".

Figure 3-22:
Webserver "home"
page

D300815 0215- BL67 multiprotocol

3-31

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.8 Change Admin Password

Please define an individual password for administrator rights.

default password "password"

NOTE

A device reset via "Reset to Factory Defaults" (
also resets the password to "password".

Figure 3-23:
Change Admin
Password

see also Reset to Factory Defaults (page 3-34))

Change password

ange the password for the module in the web server mask.

 Ch

 Write the changes into the device via "Submit".

 Execute a device restart (by a power supply reset or by pressing the set button).

 The device has accepted the new settings, the settings are active

NOTE

"Reset" only resets the changes done in the web ser

ver mask back to the original values. The

function does not influence the device itself.

D300815 0215- BL67 multiprotocol3-32

Web server - remote access/configuration (only VN ≥ 03-00)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.9 Network Configuration

On the "Network Configuration"-page, network-relevant settings can be changed.

Figure 3-24:
Web server with
network
Configuration

Change network parameters (port settings, IP a

The device's network settings can be c

hanged under "Network Configuration" only by users having

administrator rights.

NOTE

The access of the web server to the station is only possible
address, Address assignment (page 3-17).

ddress, etc.)

, if the station already has an IP

Change network parameters

ange the network parameters in the web server mask

 Ch

 Write the changes into the device via "Submit".

 The device has accepted the new settings, the settings are active

NOTE

"Reset" only resets the changes done in the web ser
function does not influence the device itself.

D300815 0215- BL67 multiprotocol

ver mask back to the original values. The

3-33

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.10 Gateway Configuration

Configuration of the field bus interface

Figure 3-25:
Web server
"Gateway
Configuration"

The "Gateway Configuration"-page serves for para

meterizing the device's fieldbus interface.

 Deactivating an Ethernet protocol or the web server

 Changing the EtherNet/IP™ configuration

 Assigning a PROFINET device name

 Activating the watchdog for MODBUS TCP

Reboot

"Reboot" executes a power-cycle at the device.

Reset to Factory Defaults

Resets the device to the default settings

(factory settings).

D300815 0215- BL67 multiprotocol3-34

Web server - remote access/configuration (only VN ≥ 03-00)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Gateway Configuration

 Chan

ge the configuration in the web server mask

 Write the changes into the device via "Submit".

 The device has accepted the new settings, the settings are active

NOTE

"Reset" only resets the changes done in the web ser
function does not influence the device itself.

3.8.11 Slot Parameters

Parameterization of the in-/outputs

The "Parameters"-page is used to parameter

Figure 3-26:
Web server
"Parameters"

ver mask back to the original values. The

ize the module's I/O-channels.

Change parameters

ange the parameters for the module in the web server mask.

 Ch

 Write the changes into the device via "Submit".

 Execute a device restart (by a power supply reset or by pressing the set button).

D300815 0215- BL67 multiprotocol

3-35

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

e device has accepted the new settings, the settings are active

 Th

NOTE

"Reset" only resets the changes done in the web ser
function does not influence the device itself.

3.8.12 Usage of mobile devices

The internal web server has a responsive design. This means, the web functions can also be executed
using a mobile device, e.g. a smartphone.

The web content is automatically adapted to the smaller display in order to assure an optimized web
server representation.

The BL67-gateway and the mobile device have to be nodes of the same network. Please assure there­fore that the IP addresses of both devices are part of the same subnet (e.g. 255.255.255.0).

In addition to that, a WLAN access has to be available for the mobile device.

ver mask back to the original values. The

Figure 3-27:
Access to the web
server via smart­phone

3.8.13 Web server logout

In order to disconnect a logged in user/PC with administrator rights from the web server, a logout is
necessary.

If only the web browser is closed, the last active access is reactivated when opening the web server
again from the same PC, which means, possibly with all administrator rights.

D300815 0215- BL67 multiprotocol3-36

Web server - remote access/configuration (only VN ≥ 03-00)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.8.14 Deactivating the web server

NOTE

If, for safety reasons, the web server has to be
the protocol specific mechanisms (Modbus TCP: parameter registers, seepage 6-8/
EtherNet/IP™: Class Instance Attribute, see page 4-26/PROFINET: GSDML configuration, see

page 8-15) as well as via the web server itself (see page 3-34).

If the web server is deactivated using the web server itself, further access to it is only possible
following a device reset to the factory settings (see page 3-22).

deactivated completely, this can be done via

D300815 0215- BL67 multiprotocol

3-37

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.9 Status and Control Word of the BL67-stations

For E therNet/IP™ and Mod bus T CP, the Status as well as the Control Word are mapped into the station's
process data.

 EtherNet/IP™

EtherNet/IP™, the mapping can be disabled (see Gateway Class (VSC 100, 64h), and GW Status

In

gister (page 4-25)).

Re

 Modbus TCP → see Register 100Ch: Gateway status (page 6-14)

 PROFINET → see Diagnose bei PROFINET (page 8-8)

3.9.1 Status Word

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Sta

tus 0V

O

low

1- FCE- MB

V

O

high

I

i

Overc.

-I/O Cfg

--Diag

Warn.

Wdg

I/O
CFG

I/O
COM

V

I

low

Warn
VI

high

Table 3-8:

Meaning of the status bits

Meaning of the status bits

Name Meaning

Diag Warn Group diagnostics of the device. At least one

I/O Cfg

The station configuration has changed.

Warn.

high Load voltage too high (> 30 V DC).

V

O

V

low Load voltage too low (< 18 V DC).

O

V

high System supply voltage too high (> 30 V DC).

I

V

low System supply voltage too low (< 18 V DC).

I

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)

I/O-module sends active diagnosis.

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.

3.9.2 Control Word

The Control Word has no function at the moment, it is reserves for further use.

D300815 0215- BL67 multiprotocol3-38

SET button

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.10 SET button

The SET-button at the gateway serves to take-over the Current Configuration of the BL67-station as
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
Modbus TCP. In PROFINET, the Required Configuration is defined by the master.

SET-Taster is necessary in EtherNet/IP™ as well as for

D300815 0215- BL67 multiprotocol

3-39

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.11 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 communica

 monitoring of the Ethernet communication

 monitoring of the gateway status

Diagnostics messages are indicated in two different ways:

 via the LEDs

 via the respective configura

tion software

tion via the module bus

3.11.1 Diagnostic messages via LEDs

Table 3-9:
LED displays

Every BL67-gateway for Ethernet displays the following statuses via LEDs:

 2 LEDs for the module bus commun

GW and IOs

 1 LED for diagnostics

 VN <03-00:

LED for the field bus communication: MS

1

VN ≥ 03-00:
2 LEDs for the field bus communication: ERR and BUS

 2 LEDs at each Ethernet-connector for the Ethernet-communication LINK

 3 LEDs for monitoring the vo

LED Status Meaning Remedy

GW off No power supply of the CPU. Check the system power supply

green Firmware active, gateway ready -

green
flashing,
1 Hz

ication (module bus-LEDs):

/ACT1 and LINK/ACT2

ltage supply (system: VCC/inputs: VI/outputs: Vo).

at t

he gateway.

Station is in the Force Mode of
the I/O-ASSISTANT.

If LED "IOs" red, then Firmware download necessary

green
flashing,
4 Hz

red Hardware error

irmware running, hardware

F
error.

Replace the gateway.

D300815 0215- BL67 multiprotocol3-40

Status indicators/diagnostic messages gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Table 3-9:
LED displays

LED Status Meaning Remedy

GW Red CPU not ready, VCC too low →

possible causes:

– too many modules at the gate-

way

– short-circuit in connected

module

– gateway hardware error.

red flashing,

Wink-command received

– Check the system power sup-

ply at the gateway and the
cabling.

– Unmount excessively mounted

modules.

– Replace the gateway, if neces-

sary.

1 Hz

ERR off Station running –

Red

A diagnostic message from
gateway or I/O-modules is

– Check the diagnostic mes-

sages.

pending.

IO off No power supply of the CPU. Check the system power supply

he gateway.

at t

green The modules configured corre-

­spond to the modules in the sta­tion, communication running.

green flashing,
1 Hz

Red CPU not ready, V

Red
flashing, 1 Hz

Red
flashing, 4 Hz

IO red/green

flashing, 1 Hz

Station is in the Force Mode of
the I/O-ASSISTANT.

too low →

CC

possible causes:

– too many modules at the gate-

way

– short-circuit in connected

module

– gateway hardware error.

Non adaptable
changes in the configuration of
the module bus nodes.

No communication
via the module bus.

The current and configured

–

module list do not match but
the data exchange proceeds as
normal.

– SET button is pushed and V

is

O

missing.

Deactivate the Force Mode of
the I/O-ASSISTANT.

– Check the system power sup-

ply at the gateway and the
cabling.

– Unmount excessively mounted

modules.

– Replace the gateway, if neces-

sary.

– Compare the configured BL67-

station and the current config­uration.

– Check the physical BL67-sta-

tion for defective or incorrectly
plugged electronic modules.

– At least one module has to be

plugged and has to be able to
communicate with the gate­way.

– Check the physical BL67-sta-

tion for pulled or new but not
planned modules.

– Check the system power sup-

ply at the gateway.

D300815 0215- BL67 multiprotocol

3-41

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Table 3-9:
LED displays

LED Status Meaning Remedy

V

CC

V

O

green Module bus and CPU OK -

off No supply of CPU or short-circuit

of the module bus supply.

green Supply of outputs OK –

green,
flashing, 1 Hz

green,

Undervoltage V
ning.

Overvoltage V

; system run-

O

; system running.

O

– Check the voltage supply at the

gateway.

– Check the system power sup-

ply at the gateway.

flashing, 4 Hz

off Voltage supply missing

V

I

green VI OK –

red Short circuit or over-load at sen-

sor supply V

→ sensor supply

sens

– Automatic restart when

debugging.

is switched off.

green,
flashing, 1 Hz

green,

Undervoltage V

; system run-

I

ning.

Overvoltage VI; system running.

– Check the system power sup-

ply at the gateway.

flashing, 4 Hz

off Voltage supply missing

LINK/ACTx green Link established,100 Mbps

green,

ernet traffic, 100 Mbps

Eth

flashing

yellow Link established,10 Mbps

yellow

Ethernet traffic, 10 Mbps

flashing

off No Ethernet link. – Check the Ethernet-connec-

BUS
(MS)

green Displays the logical connection

a Master

to

green,

Gateway ready for operation

flashing

red Gateway error:

– IP address conflict
–gateway in RESTORE-mode
– F_Reset activated

red/green – Auto-negotiation

and/or

– Autonegotiation and/or wait-

ing for DHCP-/BootP-address
assignment.

tion.

– Check the IP-addresses in the

network

– Check the position of the DIP-

switches

The gateway waits for IP­address assignment. Wait for
the address assignment to be
finished.

D300815 0215- BL67 multiprotocol3-42

Parameters of the I/O-modules

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.12 Parameters of the I/O-modules

NOTE

The description of the parameters for the BL67 I
I/O module" (D300529www.turck.de.

/O modules is part of the user manual "BL67

D300815 0215- BL67 multiprotocol

3-43

Properties: Gateway

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

3.13 Diagnostics of the I/O-modules

NOTE

The description of the diagnostics
I/O module" (D300529www.turck.de.

for the BL67 I/O modules is part of the user manual "BL67

D300815 0215- BL67 multiprotocol3-44

4 Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.1 The EtherNet/IP™ Communications Profile....................................................................................... 2

4.1.1 Communications Profile for BL67...................................................................................................................................................3

4.2 QC - QuickConnect............................................................................................................................. 4

4.2.1 General.....................................................................................................................................................................................................4

4.2.2 QuickConnect in BL67 ........................................................................................................................................................................4

– QuickConnect via Configuration Assembly............................................................................................................................5

– Quick Connect via Class Instance Attribute............................................................................................................................5

– QuickConnect via web server ......................................................................................................................................................5

4.3 Device Level Ring (DLR) .................................................................................................................... 6

4.4 Diagnostic messages via the process data........................................................................................ 7

4.4.1 Summarized Diagnostics...................................................................................................................................................................7

4.4.2 Scheduled Diagnostics.......................................................................................................................................................................7

4.5 Classes and Instances of the EtherNet/IP™ stations .......................................................................... 8

4.5.1 EtherNet/IP™ Standard Classes .......................................................................................................................................................8

4.5.2 Identity Object (0×01) ........................................................................................................................................................................9

4.5.3 Assembly Object (0×04).................................................................................................................................................................. 11

– Process data instances ................................................................................................................................................................ 12

– Configuration Assembly............................................................................................................................................................. 12

– Mapping of process data............................................................................................................................................................ 13

4.5.4 TCP/IP Interface Object (0×F5) ..................................................................................................................................................... 14

4.5.5 Ethernet Link Object (0×F6) .......................................................................................................................................................... 18

4.5.6 DLR Object (0×47) ............................................................................................................................................................................. 21

4.5.7 QOS Object (0×48) ............................................................................................................................................................................ 22

4.6 VSC-Vendor Specific Classes ........................................................................................................... 23

4.6.1 Class instance of the VSC................................................................................................................................................................ 23

4.6.2 Gateway Class (VSC 100, 64h)....................................................................................................................................................... 24

– Class instance ................................................................................................................................................................................. 24

– Object Instance 1...........................................................................................................................................................................24

– Object Instance 2...........................................................................................................................................................................25

4.6.3 Process Data Class (VSC102, 66h) ................................................................................................................................................ 27

– Class instance ................................................................................................................................................................................. 27

– Object instance 1, standard output process data (compressed) ................................................................................ 27

– Object Instance 3, diagnostic instance ................................................................................................................................. 28

– Object Instance 4, COS/CYCLIC instance .............................................................................................................................. 28

4.6.4 Miscellaneous Parameters Class (VSC 126) .............................................................................................................................. 29

– Instance 1 (port 1)/Instance 2 (port 2) ................................................................................................................................... 29

D300815 0215- BL67 multiprotocol 4-1

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.1 The EtherNet/IP™ Communications Profile

TECHNICAL BASICS

EtherNet/IP™ is based on a connection-oriented communi
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.

I/O Messages

I/O Messages serve to exchange high priority pr
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.

Explicit Messages

Explicit Messages are used to tra
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.

cation model. This means that it is

ocess and application data over the network.

nsmit low-priority configuration data, general management

D300815 0215- BL67 multiprotocol4-2

The EtherNet/IP™ Communications Profile

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.1.1 Communications Profile for BL67

BL67 behaves as an EtherNet/IP™ Server in the network; the scanner of the higher-level controller oper­ates as a EtherNet/IP™ Client.

The following EtherNet/IP™ communications types are supported:

 Unicast

 Multicast

 Cyclic Connection

 Unconnected (UCMM) Explicit Messaging

 Connected Explicit Messaging

TECHNICAL BASICS
Unicast

A po

int-to-point connection that exists between two nodes only.

Multicast

A packet with a special destination address, wh
willing to receive.

ich multiple nodes on the network may be

COS I/O Connection

COS (Change Of State) I/O Connections establish event-controlled connections. This means

at the EtherNet/IP™ devices generate messages as soon as a change of status occurs.

th

Cyclic I/O Connection

Messages are triggered time-control
tor.

UCMM

The EtherNet/IP™ gateway offers th
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 syste
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. Receiv­ing nodes decode this key to know whether they must accept the data or not.

led in Cyclic I/O connections by means of a time genera-

e option of establishing explicit messaging via the UCMM

m. For most communications between nodes, a connection is

D300815 0215- BL67 multiprotocol

4-3

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.2 QC - QuickConnect

4.2.1 General

QuickConnect enables a PLC to build up connections to EtherNet/IP™ devices in less than 300 ms after
switching-on the power supply for the EtherNet/IP™ network. This fast start up of devices is above all
necessary for robotic tool changes for example in the automobile industry.

NOTE

Please read Et
the correct Ethernet-cabling in QC-applications with BL67,

4.2.2 QuickConnect in BL67

The TURCK BL67-gateway BL67-GW-EN (VN ≥ 03-00) supports QuickConnect.

QuickConnect is activated:

hernet-connection for QC-/FSU-applications (page 3-13) for information about

 via the configuration data in the PLC-program per

Assembly Class
(see also chapter 5.5, Activating QuickConnect (page 5-15))

or

 via Class Instance Attribute in

P/IP Interface Object 245 (0×F5), instance 1, attribute 12 (0×C0)

TC

NOTE

Activating QuickConnect also activa

Auto-negotiation
Transmission speed
Duplex
Topology
AutoMDIX

0×04, Configuration Assembly 106, bit 9 = 1

ted the automatic setting of all necessary port-properties:

= deactivated
= 100BaseT
= Full duplex
= linear
= deactivated

D300815 0215- BL67 multiprotocol4-4

QC - QuickConnect

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

QuickConnect via Configuration Assembly

Figure 4-1:
Configuration
Assembly

The Configuration Assembly is part of
station's configuration in the RS Logix-software by Rockwell Automation.

NOTE

Further information about the configuration of BL67-stations in the Rockwell software RS
Logix can

(Allen Bradley).

be found in chapter 5, Application example: BL67-GW-EN with EtherNet/IP™

the Assembly Class of the device and is defined during the

Quick Connect via Class Instance Attribute

Activate QuickConnect via Class Instance Att

Class Instance Attribute Value

245 (0×F5) 1 (0×F6) 12 (0×0C) 0: disabled (default)

QuickConnect via web server

QuickConnect can also be activated or deactiva

chapter 3.8.10, Gateway Configuration (page 3-34)

ribute using the following setting:

1: enabled

ted using the device's web server, see also

D300815 0215- BL67 multiprotocol

4-5

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.3 Device Level Ring (DLR)

The BL67-GW-EN (≥ VN 03-04) supports DLR.

TECHNICAL BASICS

The Device Level Ring (DLR)-redundancy protocol is used to increase the sta
EtherNet/IP™ networks.

DLR-capable products provide an integrated switch and can thus be integrated into a ring
topology.
The DLR-protocol is used to recognize a ring fault. In case of an interruption of the data line,
data are sent through an alternative network section, so that the network can be reconfigured
as soon as possible.
DLR-capable network nodes are provided with extended diagnostic functions which enable
the devices to localize errors and thus decrease the time for error search and maintenance.

bility of

D300815 0215- BL67 multiprotocol4-6

Diagnostic messages via the process data

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.4 Diagnostic messages via the process data

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 process data mappings (page

4-13 ff.).

2 different forms of diagnostic data handling are provided:

 Summarized diagnostics

 Scheduled Diagnostics

4.4.1 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-13).

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-24)

1

4.4.2 Scheduled Diagnostics

If scheduled diagnostics is activated (Process Data Class (VSC102, 66h) (page 4-27)), the manufacturer
specific diagnostic bits are mapped into the station's process data(page 4-7 ff.).

The scheduled diagnostic data is placed at the end of the input data and after the summarized
diagnostic data (see page 4-13).

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.

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

00Slot-no. of the module which sends an emergency-frame.

1

Status of diagnostic message:
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-24)

n Module diagnostics from the module actually referenced by the round-

robin mechanism.

D300815 0215- BL67 multiprotocol

4-7

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.5 Classes and Instances of the EtherNet/IP™ stations

4.5.1 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

es

Class

Class Code

01 (0×01)

04 (0×04)

245 (0×F5)

246 (0×F6)

71 (0×47)

72 (0×48)

Object name

Identity Object (0×01)

Assembly Object (0×04)

TCP/IP Interface Object (0×F5)

Ethernet Link Object (0×F6)

DLR Object (0×47)

QOS Object (0×48)

D300815 0215- BL67 multiprotocol4-8

Classes and Instances of the EtherNet/IP™ stations

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.5.2 Identity Object (0×01)

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

Table 4-3:
Instance attri­bute, obje

ct

instance 1

Attr. No.

1 (0×01)

2 (0×02)

6 (0×06)

7 (0×07)

Object insta

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

Attribute name Get/

Type Value

Set

REVISION G UINT 1

MAX OBJECT INSTANCE G UINT 1

MAX CLASS ATTRIBUTE G UINT 7

MAX INSTANCE ATTRIBUTE G UINT 7

nce 1 - instance attribute

Attribute name Get/

Type Description

Set

VENDOR G UINT Contains the vendor ID.

TURCK = 48

PRODUCT TYPE G UINT Indicates the general type of product.

Communications Adapter

= 0×0C

12

dec

PRODUCT CODE G UINT Identifies a particular product within a device

type.
Default: 27247

dec =

6A6F

4 (0×04)

5 (0×05)

6 (0×06)

7 (0×07)

REVISION

Major Minor

G STRUCT

OF:
USINT
USINT

Revision of the item the Identity Object is
representing.
0×01
0×06

DEVICE STATUS G WORD see Table 4-4: Device Status

SERIAL NUMBER G UDINT Contains the ident-no. of the product (3 last

bytes of the MAC-ID).

PRODUCT NAME

G STRUCT

OF:
LENGTH
NAME

USINT

STRING

[13]

D300815 0215- BL67 multiprotocol

4-9

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Device Status

Table 4-4:
Device Status

Table 4-5:
Common ser-

ces

vi

Bit

0 to 1

2

3

4 to 7

8 to 15

Common services

Service code

01 (0×01)

05 (0×05)

Name Definition

reserved default = 0

Configured TRUE = 1

→ The application of the device has been configured
(≠ default-settings).

reserved default = 0

Extended Device
Status

reserved default = 0

Class Instance Service name

yes yes Get_Attribute_All

no yes Reset

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

Returns a predefined list of the object‘s attributes.

Starts the reset service for the device.

14 (0×0E)

yes yes Get_Attribute_Single

Returns the contents of a specified attribute.

D300815 0215- BL67 multiprotocol4-10

Classes and Instances of the EtherNet/IP™ stations

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.5.3 Assembly Object (0×04)

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

Table 4-7:
Instance

ribute

Att

Table 4-8:
Common ser-

ces

vi

Attr. No.

1 (0×01)

2 (0×02)

stance attribute

In

Attr. No.

3 (0×03)

4 (0×04)

Common services

Service code

14 (0×0E)

Attribute name Get/

REVISION G UINT 2

MAX OBJECT INSTANCE G UINT 104

Attribute name Get/

DATA S ARRAY OF

SIZE G UINT UINT Number of bytes in attr. 3

Class Instance Service name

no yes Get_Attribute_Single

Type Value

Set

Type Description

Set

BYTE

256 or variable

D300815 0215- BL67 multiprotocol

4-11

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Process data instances

Instance 101

Contains the station’s input data (static

2 Bytes status information (see page 3-38)

+ process data

Instance 102

Contains the station’s output data (static leng

2 Bytes Control data (mapped, but not defined)

+ process data

Instance 103 and Instance 104

length 256 bytes).

th 256 bytes).

In- and output assembly instances with variable assembly
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
0×67, attribute 0×04) and can be from 2 to 496 bytes large.

Configuration Assembly

Instance 106

 14 byte configuration data

Byte 9, bit 1 is used to activate QuickConnect in

Assembly (page 4-5)).

the station (see also QuickConnect via Configuration

sizes. The assembly size is pre-calculated to

the Assembly Object (instance

D300815 0215- BL67 multiprotocol4-12

Classes and Instances of the EtherNet/IP™ stations

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Mapping of process data

Table 4-9:
Data mapping
for
BL67-GW-EN

The process data image of the BL67-gateways is

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

 16-bit output data is reached and fu

 An input module, whose process data length cannot be completely incorporated in the preceding

rd, follows on from another input module

wo

 An output module, whose process data length cannot be completely incorporated in the preceding

rd, follows on from another output module 16-bit input data is reached and further input

wo
modules follow

Produced D
(word no.)

0 Status Word of the gateway

1 to n Input data of modules

ata

rther output modules follow

Eingangsdaten

Mapping can be disabled using attr. 138 in VSC100, object instance
2, page 4-24)

An example mapping can be found in chapter 5.3, I/O data

mapping (page 5-10).

depicted in WORD-format (16 bit).

input modules follow

n + x Summarized diagnostic data (page 4-7) of individual length (1 bit

per module which sends diagnostics).
Can be enabled/disabled using VSC102, Object instance 3, attr.
104, page 4-27 ff.
(x = the no. of following bytes depending on the no. of slices within
the station)

n + y Scheduled diagnostic data (page 4-7). Can be enabled/disabled

using VSC102, Object instance 3, attr. 105, page 4-27 ff.
(y = data length for the scheduled diagnostics set according to the
properties of the modules attached to the gateway)

Consumed Data

ord no.)

(w

0 Control word of the gateway. The mapping can be disabled using

1- n Output data of modules

Note

The data mapping can be structured individually. All parts ex
of the station can be enabled/disabled independently from each other.

Ausgangsdaten

attribute 139 "GW CONTROL REGISTER" in the Gateway Class (VSC

100), object instance 2 (see page 4-26).

An example mapping can be found in chapter 5, I/O data mapping

(page 5-10).

cept for the in- and out-put data

D300815 0215- BL67 multiprotocol

4-13

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.5.4 TCP/IP Interface Object (0×F5)

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

Table 4-11:
Instance attri-

object

bute,
instance 1

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

Object insta

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

4 (0×04)

Attribute name Get/

Set

REVISION G UINT 1

MAX OBJECT INSTANCE G UINT 1

NUMBER OF INSTANCES G UINT 1

nce 1: Instance attribute

Attribute name Get/

STATUS G DWORD Interface status (see page 4-15, Table 4-13:

CONFIGURATION
CAPABILITY

CONFIGURATION
CONTROL

PHYSICAL LINK
OBJECT

Type Description

Set

Interface Status)

G DWORD Interface Capability Flag (see page 4-15, Table

4-14: Configuration Capability)

G/S DWORD Interface Control Flag (see page 4-16, Table 4-

15: Configuration Control)

G STRUCT

Type Value

5 (0×05)

6 (0×06)

Path size UINT Number of 16 bit words: 0×02

Path: Padded

EPATH

INTERFACE
CONFIGURATION

IP address G UDINT Actual IP address

NETWORK MASK G UDINT Current network mask

GATEWAY ADDR. G UDINT Actual default gateway

NAME SERVER G UDINT 0 = no name server address configured

NAME SERVER 2 G UDINT 0 = no secondary name server address config-

DOMAIN NAME G UDINT 0 = no Domain Name configured

HOST NAME G STRING 0 = no Host Name configured (see page 4-16)

G Structure

of:

0×20, 0×F6, 0×24, 0×01

TCP/IP Network Interface Configuration (see

page 4-16)

ured

D300815 0215- BL67 multiprotocol4-14

Classes and Instances of the EtherNet/IP™ stations

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Table 4-11:
Instance attri­bute, obje
instance 1

Table 4-12:
Common ser-

ces

vi

ct

Attr. No.

10 (0×0A)

11 (0×0B)

12 (0×0C)

Common Services

Service code

14 (0×0E)

16 (0×10)

 Interface Status

The Sta
Refer to the state diagram, Figure 4-2: TCP/IP object state diagram (acc. to CIP Spec., Vol.2, Rev. 1.1)
for

Attribute name Get/

ACD Enable S BOOL Activates ACD (Address Conflict Detection)

Last Conflict
detected

Quick Connect G/S BOOL 0 = deactivate

Class Instance Service name

yes yes Get_Attribute_Single

no yes Set_Attribute_Single

tus attribute indicates the status of the TCP/IP network interface.

a description of object states as they relate to the Status attribute.

Type Description

Set

G/S STRUCT

of:

0 = deactivated
1 = activated
If ACD is activated, attribute 11 (0×0B) contains
the return value.

Contains information about the last detected
conflict, ACD diagnostics parameter

1 = activate

Table 4-13:
Interface Status

Table 4-14:
Configuration

ability

Cap

Bit(s)

0-3

4 to 31

 Configuration Capability

Bit(s)

0

1

2

Name Definition

Interface Configuration
Status

reserved

The Configuration Capability indicates the
capability.

Name Definition value

BOOTP Client The device is capable of obtaining its

DNS Client The device is capable of resolving host

DHCP Client The device is capable of obtaining its

Indicates the status of the Interface Configuration attribute:
0 = The Interface Configuration attribute has not been config­ured
1 = The Interface Configuration attribute contains valid config­uration.
2 to 15: reserved

device’s support for optional network configuration

1

network configuration via BOOTP.

0

names by querying a DNS server.

1

network configuration via DHCP.

D300815 0215- BL67 multiprotocol

4-15

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

 Configuration Control

e Configuration Control attribute is used to control network configuration options.

Th

Table 4-15:
Configuration
Control

Bit(s)

0-3

4

5-31

 Interface Configuration

Name Definition

Startup
Configuration

DNS Enable Always 0.

reserved Set to 0.

This attribute
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 0×09) 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.

contains the configuration parameters required to operate as a TCP/IP node.

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

 Host Name

Host Name attribute contains the device’s host name.

The
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 0215- BL67 multiprotocol4-16

Classes and Instances of the EtherNet/IP™ stations

Non-existent

Obtaining initial

configuration

Waiting

for

configuration

Applying

configuration

TCP/IP network

interface configured

Status = 0×00000001

Powerup/ Reset

BOOTP/DHCP
response received

BOOTP/DHCP
disabled and
stored config.
valid

Set_Attributes
request received

Change interface
configuration

Status =
0×00000000

Configuration applied

BOOTP OR
DHCP enabled

BOOTP/DHCP
disabled and
stored config. valid

Status =
0×00000000

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Figure 4-2:
TCP/IP object
state diagram
(acc. to CIP
Spec., Vol.2, Rev.

1.1)

D300815 0215- BL67 multiprotocol

4-17

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.5.5 Ethernet Link Object (0×F6)

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

Table 4-17:
Instance attri­bute

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

stance attributes (instance 1 = port 1/instance 2 = port 2)

In

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

6 (0×06)

Attribute name Get/

REVISION G UINT 1

MAX OBJECT INSTANCE G UINT 1

NUMBER OF INSTANCES G UINT 1

Attribute name Get/

INTERFACE SPEED G UDINT Speed in megabits per second

INTERFACE FLAGS G DWORD see Table 4-18: Interface flags

PHYSICAL
ADDRESS

INTERFACE
CONTROL

Control Bits WORD Table 4-19: Interface control - control bits

Type Description

Set

(e.g., 10, 100, 1000, etc.)

G ARRAY OF

USINT

S STRUCT OF: Allows port-wise changes of the Ethernet-

Contains the interface’s MAC address
(TURCK: 00:07:46:××:××:××)

settings

Type Value

Set

Table 4-18:
Interface flags

Forced Interface
Speed

7 (0×07)

10 (0×0A) INTERFACE LABEL

Bits Name Definition Default value

0

1

INTERFACE TYPE

Link Status Indicates whether or not the Ethernet

Half/full duplex 0 = half duplex;

UINT Table 4-19: Interface control - control bits

Depends on appli-

802.3 communications interface is
connected to an active network.
0 = inactive link
1 = active link.

1 = full duplex
If the Link Status flag is 0, the value of the
Half/Full Duplex flag is indeterminate.

cation

Depends on appli­cation

D300815 0215- BL67 multiprotocol4-18

Classes and Instances of the EtherNet/IP™ stations

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Table 4-18:
Interface flags

Bits

2 to 4 Negotiation Status Indicates the status of the automatic

5

6

Name Definition Default value

duplex detection (Autonegotiation)
0 = Autonegotiation in progress
1 = Autonegotiation and speed detection
failed.
Using default values for speed and duplex
(10 Mbps/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.

Manual Setting
Requires Reset

Local Hardware Fault 0 = interface detects no local hardware

0 = interface can activate changes to link
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

fault
1 = a local hardware fault is detected

Depends on appli­cation

0

0

D300815 0215- BL67 multiprotocol

4-19

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Table 4-19:
Interface con-

- control bits

trol

Bits

0

1 Forced Duplex Mode If bit "Auto-negotiate" is 0, bit "Forced

2-15

Forced Interface Speed

If the Auto-negotiate bit is 0, the "F
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 0×09 (Invalid Attribute
Value).

Name Definition Default value

Auto-negotiate 0 = Autonegotiation deactivated

1 = Autonegotiation activated

Depends on appli­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
0×09 (Invalid Attribute Value).
If auto-negotiation is enabled, attempting
to set the Forced Duplex Mode bits shall
result in a error code 0×0C (Object State
Conflict).

reserved

orced Interface Speed" bits indicate the speed at which the interface

cation

Table 4-20:
Common

rvices

Se

If auto-negotiation is enabled, attempting to set the Forced Interface Speed bits shall result in a error
code 0×0C (Object State Conflict).

Common Services

Service code

14 (0×0E)

16 (0×10)

Class Instance Service name

yes yes Get_Attribute_Single

no yes Set_Attribute_Single

D300815 0215- BL67 multiprotocol4-20

Classes and Instances of the EtherNet/IP™ stations

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.5.6 DLR Object (0×47)

The object DLR contains the configuration and status interface of the DLR protocol. The DLR protocol
enables the use of an Ethernet ring topology.

Class attributes

Table 4-21:
Class attributes

Table 4-22:
Instance attri­bute

Attr. No.

1 (0×01)

stance attribute

In

Attr. No.

1 (0×01)

2 (0×02)

10 (0×0A)

12 (0×0C)

Attribute name Get/

Set

REVISION G UINT 1

Attribute name Get/

NETWORK
TOPOLOGY

NETWORK
STATUS

ACTIVE SUPER­VISOR ADDR.

CAPABILITY
FLAGS

Type Description

Set

G USINT Current network topology mode

0 = linear
1 = ring topology

G USINT status of the gateway network

0 = normal
1 = ring error
2 = unexpected loop detected

G STRUCT of: IP and/or MAC address of the active ring

supervisor

G DWORD Describes the DLR capabilities of the device

0 = Announce-based Ring Node

Type Value

Table 4-23:
Common

rvices

Se

Common Services

Service code

14 (0×0E)

Class Instance Service name

yes yes Get_Attribute_Single

D300815 0215- BL67 multiprotocol

4-21

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.5.7 QOS Object (0×48)

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 attribute

Table 4-24:
Instance attri­bute

Table 4-25:
Common

rvices

Se

Attr. No.

4 (0×04)

5 (0×05)

6 (0×06)

07 (0×07)

08 (0×08)

Common

Service code

14 (0×0E)

16 (0×10)

Services

Attribute name Get/

DSCP Urgent S USINT DSCP value for CIP transport class 0/1 Urgent

DSCP Scheduled S USINT DSCP value for CIP transport class 0/1 Sched-

DSCP High S USINT DSCP value for CIP transport class 0/1 High

DSCP Low S USINT DSCP value for CIP transport class 0/1 Low

DSCP Explicit S USINT DSCP value for CIP explicit messages (trans-

Class Instance Service name

yes yes Get_Attribute_Single

no yes Set_Attribute_Single

Type Description

Set

priority messages

uled priority messages

priority messages

priority messages

port class 2/3 and UCMM)

D300815 0215- BL67 multiprotocol4-22

VSC-Vendor Specific Classes

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.6 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

ecific Classes

Sp

Class Code

dec.

ex.)

(h

100 (64h) Gateway Class, page 4-24 Contains data and settings concerning the

102 (66h) Process Data Class, page 4-27 Contains process data

126 (1Ah) Miscellaneous Parameters Class, page 4-29 Describes the EtherNet/IP™-Port proper-

Name

4.6.1 Class instance of the VSC

NOTE

The class instance attribute
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

Attr. No.

dec.

ex.)

(h

Attribute name

Description

fieldbus-specific part of the BL67-stations.

ties

s are the same for each Vendor Specific Class.

Get/

Type Description

Set

100
(64h)

101
(65h)

102
(66h)

103
(67h)

Class revision GUINT States the revision number of the class

(Maj. Rel. *1000 + Min. Rel.).

Max. instance GUSINT Contains the number of the highest instance

of an object created on this level in the class
hierarchy.

# of instances GUSINT Contains the number of Object Instances

created in this class.

MAX CLASS ATTRI­BUTE

GUSINT Contains the number of the last Class Attri-

bute to be implemented.

D300815 0215- BL67 multiprotocol

4-23

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.6.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 C
instance for the VSC.

ject Instance 1

Ob

lass instance of the VSC (page 4-23) for the description of the class

Table 4-28:
Object Instance
1
Boot instance

Attr. No.

dec.

ex.)

(h

100
(64h)

101
(65h)

102
(66h)

103
(67h)

104
(68h)

Attribute name

MAX INSTANCE
ATTRIBUTE

Hardware revision GSTRUCT Contains the hardware revision number of the

Firmware revision GSTRUCT Contains the firmware revision of the boot

Service tool ident
number

Hardware
info

Get/

Type Description

Set

GUSINT Contains the number of the last object attri-

bute to be implemented.

station (USINT Maj./USINT Min.)

firmware (maj./min.).

GUDINT Contains the BOOT ID number that serves as

an identification number for the software I/O­ASSISTANT

GSTRUCT 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

D300815 0215- BL67 multiprotocol4-24

VSC-Vendor Specific Classes

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Object Instance 2

Table 4-29:
Object instance
2, gateway
instance

Attr. No.

dec.

ex.)

(h

109
(6Dh)

Attribute name

Get/

Type Description

Set

Status register 2 GSTRUCT 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"

e configuration has been changed in an

Th

incompatible way.
– Bit 10: "I/O Communication Lost Error"

Communication on the internal module bus

disturbed.

Voltage errors

–Bit 09: "U

too low" System voltage (VI) too

sys

low (< 18 VDC).
–Bit 08: "U

too high" System voltage (VI) too

sys

high (< 30 VDC).
–Bit 07: "U

too low" Load voltage (VO) too low

L

(< 18 VDC).
– Bit 06: reserved
– Bit 05: reserved
– Bit 04: reserved

Warnings

– Bit 03: "I/O Cfg Modified Warning" The station

nfiguration has changed.

co
– Bit 02: reserved
– Bit 01: reserved
– Bit 00: "I/O Diags Active W arning" At leas t 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
(0×8A)

GW Status
Register

Get/

DWORD Allows to enable/disable the status register

Set

which is part of the input data.
0 = deactivated
1 = activated (default)

D300815 0215- BL67 multiprotocol

4-25

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Table 4-29:
Object instance
2, gateway
instance

Attr. No.

dec.

ex.)

(h

139
(0×8B)

140
(0×8C)

Attribute name

GW Control
Register

Disable Protocols Get/

Get/
Set

Get/
Set

Set

Type Description

DWORD Allows to enable/disable the control register

which is part of the output data.
0 = deactivated
1 = activated (default)

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

D300815 0215- BL67 multiprotocol4-26

VSC-Vendor Specific Classes

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.6.3 Process Data Class (VSC102, 66h)

This class contains the process-relevant information.

Class instance

NOTE

Please refer to paragraph Class instance
instance for the VSC.

of the VSC, page 4-23 for the description of the class

Table 4-30:
Object instance
1, standard
input process

com-

data (
pressed)

Table 4-31:
Object instance
2, standard out­put proc
(compressed)

ess data

Object insta

Attr. No.

dec. (hex.)

100 (64h) MAX INSTANCE

101 (65h) Attribute list GARRAY OF

102 (66h) Packed process

103 (67h) Process data byte

Object instance 2, standard output process data (compressed)

Attr. No.

dec. (hex.)

100 (64h) MAX INSTANCE

nce 1, standard output process data (compressed)

Attribute name Get/

Set

GUSINTContains the number of the last object

ATTRIBUTE

GARRAY OF

input data

GUSINTThe number of bytes that are exchanged

count

Attribute name Get/

Set

GUSINTContains the number of the last object

ATTRIBUTE

Type Description

attribute to be implemented.

List of all attributes that are supported by

USINT

WORD

Type Description

this instance.

Input process data, 16-bit aligned,
compressed.

with this Instance.

attribute to be implemented.

101 (65h) Attribute list GARRAY OF

102 (66h) Packed process

input data

103 (67h) Process data byte

count

D300815 0215- BL67 multiprotocol

USINT

G/S ARRAY OF

WORD

GUSINTThe number of bytes that are exchanged

List of all attributes that are supported by
this Instance.

Output process data, 16-bit aligned,
compressed.

with this Instance.

4-27

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

Object Instance 3, diagnostic instance

Table 4-32:
Object Instance
3, diagnostic
instance

Table 4-33:
Object Instance

COS/CYCLIC

4,
instance

Attr. No.

dec. (hex.)

104 (68h) GW

105 (69h) GW

106 (6Ah) reserved -

Object Instance 4, COS/CYCLIC instance

Attr. No.

dec.

ex.)

(h

Attribute name Get/ Set Type Description

G/S BOOL 0 = disabled
Summarized diag­nostics

G/S BOOL 0 = disabled
manufacturer
specific diagnos­tics (scheduled
diagnostics)

Attribute name

Get/

Set

Type Description

1 = yes
1 bit of diagnosis mapped at the end of the
input data image (page 4-7).
Changes become valid after a start-up!

1 = yes
The channel-specific diagnostic bits are
mapped into the process input data (see

page 4-7).

Changes become valid after a start-up!

104 (68h) COS data

mapping

G/S ENUM

USINT

The actual data are loaded to the non-vola­tile 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 0215- BL67 multiprotocol4-28

VSC-Vendor Specific Classes

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

4.6.4 Miscellaneous Parameters Class (VSC 126)

Instance 1 (port 1)/Instance 2 (port 2)

Table 4-34:
Object instance

A default

setting

Attr. No.

dec.

ex.)

(h

109 (6Dh) Ethernet port

112 (70h)

Attribute name Get/

parameters

IO controller
software revision

Type Description

Set

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)

G DWORD The number of instances of this parameter

depends on the number of I/O controllers.

D300815 0215- BL67 multiprotocol

4-29

Implementation of EtherNet/IP™

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

D300815 0215- BL67 multiprotocol4-30

5 Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

5.1 General notes .................................................................................................................................... 2

5.1.1 Used hard-/ software ..........................................................................................................................................................................2

– Hardware.............................................................................................................................................................................................2

– Software...............................................................................................................................................................................................2

5.2 Network configuration ..................................................................................................................... 3

5.2.1 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

5.2.2 Downloading the I/O configuration..............................................................................................................................................8

5.3 I/O data mapping ............................................................................................................................ 10

5.4 Process data access ......................................................................................................................... 12

5.4.1 Setting outputs .................................................................................................................................................................................. 12

5.4.2 Example program.............................................................................................................................................................................. 13

5.5 Activating QuickConnect................................................................................................................ 15

D300815 0215- BL67 multiprotocol 5-1

Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

5.1 General notes

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™ Bridge 1756 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

D300815 0215- BL67 multiprotocol5-2

Network configuration

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

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 communica
interface card, both devices have to be hosts in the same network.

achieve this, you have either:

To

 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.6,

Address assignment (page 3-17),.

or

 to change the IP address of the used PC or network interface card (for detailed information, please

read Changing the IP address of a PC/ network interface card (page 12-2).

tion between the BL67-station and a PLC/ PC or a network

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

er the information related to the controller depending on your configuration, as well as a name

1 Ent

for the project.

Figure 5-1:
Configuration
of the controller

2 Your project will be opened offline.

D300815 0215- BL67 multiprotocol

5-3

Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

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/IP™ interface to the controller.

Figure 5-2:
Add EtherNet/IP™
Bridge

Figure 5-3:
EtherNet/IP™
Bridge properties

3 Enter the necessary device properties (name, IP-address etc.) in the dialog box which is opened.

D300815 0215- BL67 multiprotocol5-4

Network configuration

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

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:

d Generic

Ad
Ethernet mod­ule

Figure 5-5:
Configuring the
BL67­station

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.

D300815 0215- BL67 multiprotocol

5-5

Application example: BL67-GW-EN with EtherNet/IP™ (Allen Bradley)

A

Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [e-mail]

NOTE

If the variable Assembly Instances 103 and 104 (see page 4-11)
Parameters have to be set according to the actual station configuration.
This 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: Eth-

erNet/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×04 and Assembly Class (0×04), Instance 0×68, Attr. 0×04.

Figure 5-6:
EtherNet/IP™
report (PLC
configuration)

A Data to enter

into assembly
instances in RS
Logix

are used, the Connection

0×67, Attr.

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

D300815 0215- BL67 multiprotocol5-6