Turck BL67 - Ethernet/IP Instructions for use

BL67 –

USER MANUAL

FOR

ETHERNET/IP

All brand and product names are trademarks or registered trade marks of the owner concerned.

Edition 09/2011

© Hans Turck GmbH, Muelheim an der Ruhr

All rights reserved, including those of the translation.

No part of this manual may be reproduced in any form (printed, photocopy, microfilm or any other process) or processed, duplicated or distributed by means of electronic systems without written permission of Hans Turck GmbH & Co. KG, Muelheim an der Ruhr.

Subject to alterations without notice

Warning!

Before commencing the installation

Disconnect the power supply of the device.

Ensure that devices cannot be accidentally restarted.

Verify isolation from the supply.

Earth and short circuit.

Cover or enclose neighboring units that are live.

Follow the engineering instructions of the device concerned.

Only suitably qualified personnel in accordance with EN 50 110-1/-2 (VDE 0 105 Part 100) may work on this device/system.

Before installation and before touching the device ensure that you are free of electrostatic charge.

The functional earth (FE) must be connected to the protective earth (PE) or to the potential equalization. The system installer is responsible for implementing this connection.

Connecting cables and signal lines should be installed so that inductive or capacitive interference do not impair the automation functions.

Install automation devices and related operating elements in such a way that they are well protected against unintentional operation.

Suitable safety hardware and software measures should be implemented for the I/O interface so that a line or wire breakage on the signal side does not result in undefined states in the automation devices.

Ensure a reliable electrical isolation of the low voltage for the 24 volt supply. Only use power supply units complying with IEC 60 364-4-41 (VDE 0 100 Part 410) or HD 384.4.41 S2.

Deviations of the mains voltage from the rated value must not exceed the tolerance limits given in the specifications, otherwise this may cause malfunction and dangerous operation.

Emergency stop devices complying with IEC/EN 60 204-1 must be effective in all operating modes of the automation devices. Unlatching the emergency-stop devices must not cause restart.

Devices that are designed for mounting in housings or control cabinets must only be operated and controlled after they have been installed with the housing closed. Desktop or portable units must only be operated and controlled in enclosed housings.

Measures should be taken to ensure the proper restart of programs interrupted after a voltage dip or failure. This should not cause dangerous operating states even for a short time. If necessary, emergency-stop devices should be implemented.

Wherever faults in the automation system may cause damage to persons or property, external measures must be implemented to ensure a safe operating state in the event of a fault or malfunction (for example, by means of separate limit switches, mechanical interlocks etc.).

The electrical installation must be carried out in accordance with the relevant regulations (e. g. with regard to cable cross sections, fuses, PE).

All work relating to transport, installation, commissioning and maintenance must only be carried out by qualified personnel. (IEC 60 364 and HD 384 and national work safety regulations).

All shrouds and doors must be kept closed during operation.

Table of Contents

1

1.1

About this manual

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

1.2

General information........................................................................................................................................1-3

1.2.1

Prescribed use .........................................................................................................................................................................................1-3

1.2.2

Notes concerning planning /installation of this product ........................................................................................................1-3

1.3

1.4

Description of symbols used ..........................................................................................................................1-4

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

2 BL67 philosophy

2.1

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

2.1.1

Flexibility ...................................................................................................................................................................................................2-2

2.1.2

Convenient handling ............................................................................................................................................................................2-2

2.2

BL67 components ............................................................................................................................................2-3

2.2.1

Gateways ...................................................................................................................................................................................................2-3

2.2.2

Electronic modules ................................................................................................................................................................................2-4

2.2.3

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

2.2.4

End plate ...................................................................................................................................................................................................2-5

3 EtherNet/IP

3.1

System description .........................................................................................................................................3-2

3.1.1

Network-topology..................................................................................................................................................................................3-3

3.1.2

Addressing on EtherNet/IP .................................................................................................................................................................3-4

3.1.3

Network classes.......................................................................................................................................................................................3-4

3.1.4

Checking the communication via "ping-signals"........................................................................................................................3-5

3.1.5

ARP (Address Resolution Protocol) ..................................................................................................................................................3-6

4

4.1

4.2

Technical features

General .............................................................................................................................................................4-2

Function ...........................................................................................................................................................4-3

4.3

Technical data .................................................................................................................................................4-4

4.3.1

Gateway structure..................................................................................................................................................................................4-4

4.4

Connection possibilities..................................................................................................................................4-7

4.4.1

Field bus connection.............................................................................................................................................................................4-7

4.4.2

Power Supply via 7/8" connector .....................................................................................................................................................4-7

4.4.3

Service interface connection..............................................................................................................................................................4-8

4.5

Address setting for EtherNet/IP .................................................................................................................. 4-11

4.5.1

LED-behavior ........................................................................................................................................................................................ 4-11

4.5.2

Default setting of the gateway....................................................................................................................................................... 4-11

4.5.3

Address setting via the rotary-mode ........................................................................................................................................... 4-12

4.5.4

Address setting via BootP-mode ................................................................................................................................................... 4-13

4.5.5

Address setting via DHCP-mode ................................................................................................................................................... 4-14

4.5.6

Address setting via PGM-mode...................................................................................................................................................... 4-15

4.5.7

Address setting via PGM-DHCP...................................................................................................................................................... 4-15

D300888 – BL67 for EtherNet/IP – 0911

i

4.5.8

Address setting via the software I/O-ASSISTANT .....................................................................................................................4-16

4.6

SET button ..................................................................................................................................................... 4-18

4.7

Status indicators/ diagnostic messages gateway ...................................................................................... 4-19

4.7.1

Diagnostic messages via LEDs ........................................................................................................................................................4-19

4.7.2

Diagnostic messages via the process data .................................................................................................................................4-21

4.8

Status and Control word of the gateway .................................................................................................... 4-23

4.8.1

Status word ............................................................................................................................................................................................4-23

4.8.2

Control word .........................................................................................................................................................................................4-23

4.9

Module specific diagnostic messages ...............................................................................................4-24

5 Implementation of EtherNet/IP

5.1

The EtherNet/IP Communications Profile ..................................................................................................... 5-3

5.1.1

I/O Messages ........................................................................................................................................................................................... 5-3

5.1.2

Communications Profile of the BL67 EtherNet/IP gateway.................................................................................................... 5-4

5.2

Classes and instances of the EtherNet/IP-gateway ...................................................................................... 5-5

5.2.1

EtherNet/IP Standard Classes ............................................................................................................................................................ 5-5

5.2.2

Identity Object ........................................................................................................................................................................................ 5-6

5.2.3

Message Router Object........................................................................................................................................................................ 5-7

5.2.4

Assembly Object ..................................................................................................................................................................................5-12

5.2.5

Connection Manager Object ...........................................................................................................................................................5-16

5.2.6

Port Object .............................................................................................................................................................................................5-16

5.2.7

TCP/IP Interface Object......................................................................................................................................................................5-17

5.2.8

Ethernet Link Object ...........................................................................................................................................................................5-21

5.3

VSC-Vendor Specific Classes ........................................................................................................................ 5-23

5.3.1

Class instances of the VSC ................................................................................................................................................................5-25

5.3.2

Gateway Class (VSC 100) ...................................................................................................................................................................5-26

5.3.3

Terminal Slot Class (VSC 101) ..........................................................................................................................................................5-28

5.3.4

Process Data Class (VSC102) ............................................................................................................................................................5-30

5.3.5

Power Supply Module Class (VSC103)..........................................................................................................................................5-32

5.3.6

Digital Input Module Class (VSC104) ............................................................................................................................................5-34

5.3.7

Digital Output Module Class (VSC105).........................................................................................................................................5-36

5.3.8

Analog Input Voltage Module Class (VSC106)...........................................................................................................................5-38

5.3.9

Analog Output Voltage Module Class (VSC107).......................................................................................................................5-40

5.3.10

Analog Input Current Module Class (VSC108)...........................................................................................................................5-42

5.3.11

Analog Output Current Module Class (VSC109) .......................................................................................................................5-44

5.3.12

Analog Input RTD Module Class (VSC110)..................................................................................................................................5-46

5.3.13

Analog Input THERMO Module Class (VSC111) ........................................................................................................................5-50

5.3.14

RS232 Module Class (VSC114) .........................................................................................................................................................5-53

5.3.15

RS4xx Module Class (VSC115) .........................................................................................................................................................5-60

5.3.16

SSI Module Class (VSC116)................................................................................................................................................................5-67

5.3.17

Digital Versatile Module Class (VSC117) ......................................................................................................................................5-75

5.3.18

Analog Versatile Module Class (VSC118).....................................................................................................................................5-79

5.3.19

CVI Module Class (VSC119)...............................................................................................................................................................5-82

5.3.20

RFID-S module class (VSC124).........................................................................................................................................................5-85

ii


6 Application example: BL67 gateway at Allen Bradley PLC

6.1

General .............................................................................................................................................................6-2

6.1.1

Prerequisites for this example ...........................................................................................................................................................6-2

6.2

Network configuration....................................................................................................................................6-3

6.3

Changing the IP address of a PC/ network interface card ............................................................................6-4

6.3.1

Changing the IP address in Windows 2000/ Windows XP.......................................................................................................6-4

6.3.2

Changing the IP address in Windows NT.......................................................................................................................................6-6

6.3.3

Changing the IP address via I/O-ASSISTANT V3 ..........................................................................................................................6-7

6.4

Address setting at the gateway................................................................................................................... 6-12

6.4.1

Address setting via DHCP-mode .................................................................................................................................................. 6-12

6.5

Setting-up communications with the software tool "RSLinx" .................................................................. 6-15

6.6

Configuration of the network in "RSLogiX 5000" ...................................................................................... 6-16

6.6.1

Configuration of the controller ...................................................................................................................................................... 6-16

6.6.2

Configuration of a BL67 station ..................................................................................................................................................... 6-18

6.6.3

Downloading the I/O configuration............................................................................................................................................. 6-20

6.7

Examples for I/O data mapping................................................................................................................... 6-22

6.7.1

Mapping report via I/O-ASSISTANT .............................................................................................................................................. 6-25

6.8

Example for process data access ................................................................................................................. 6-26

6.8.1

Setting outputs at BL67-8DO-0.5A-P ........................................................................................................................................... 6-26

7 Guidelines for station planning

7.1

Module arrangement ......................................................................................................................................7-2

7.1.1

Random module arrangement..........................................................................................................................................................7-2

7.2

Complete planning..........................................................................................................................................7-3

7.3

Maximum system extension...........................................................................................................................7-4

7.3.1

Creating potential groups...................................................................................................................................................................7-5

7.4

7.5

Plugging and pulling electronic modules .....................................................................................................7-6

Extending an existing station.........................................................................................................................7-6

7.6

Firmware download ........................................................................................................................................7-6

8 Guidelines for electrical installation

8.1

General notes...................................................................................................................................................8-2

8.1.1

General .......................................................................................................................................................................................................8-2

8.1.2

Cable routing ...........................................................................................................................................................................................8-2

8.1.3

Cable routing inside and outside of cabinets ..............................................................................................................................8-2

8.1.4

Lightning protection.............................................................................................................................................................................8-3

8.1.5

Transmission media...............................................................................................................................................................................8-3

8.2

Potential relationships....................................................................................................................................8-4

8.2.1

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

8.3

Electromagnetic compatibility (EMC) ............................................................................................................8-5

8.3.1

Ensuring Electromagnetic Compatibility.......................................................................................................................................8-5


iii

8.3.2

Grounding of inactive metal components ................................................................................................................................... 8-5

8.3.3

PE connection ......................................................................................................................................................................................... 8-5

8.3.4

Earth-free operation ............................................................................................................................................................................. 8-5

8.3.5

Mounting rails ......................................................................................................................................................................................... 8-6

iv


8.4

Shielding of cables ..........................................................................................................................................8-7

8.5

Potential compensation..................................................................................................................................8-8

8.5.1

Switching inductive loads ...................................................................................................................................................................8-8

8.5.2

Protection against Electrostatic Discharge (ESD.........................................................................................................................8-8

9

9.1

Appendix

Nominal current consumption of modules at Ethernet ..............................................................................9-2

10

11

Glossary

Index


v

vi


1 About this manual

1.1

1.2

1.2.1

1.2.2

1.3

1.4

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

General information ......................................................................................................................... 3

Prescribed use...................................................................................................................................... 3

Notes concerning planning /installation of this product....................................................................... 3

Description of symbols used ............................................................................................................. 4

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


1-1


1.1

Documentation concept

This manual contains information about the BL67 Ethernet gateway with EtherNet/IP.

The following chapters contain a short BL67 system description, a description of the field bus system

Ethernet, exact information about function and structure of the BL67 EtherNet/IP gateway as well as all bus specific information concerning the connection to automation devices, the maximum system extension etc.

The bus-independent I/O-modules for BL67 as well as all further fieldbus-independent chapters like mounting, labelling etc. are described in a separate manual.

BL67 I/O-modules (TURCK-Documentation-No.: German D300572/ English D300529)

Furthermore, the manual mentioned above contains a short description of the project planning and diagnostics software for TURCK I/O-systems, the engineering software I/O-ASSISTANT.

1-2


General information

1.2

General information

Attention

Please read this section carefully. Safety aspects cannot be left to chance when dealing with electrical equipment.

This manual contains all necessary information about the prescibed use of the TURCK BL67 gateways for Ethernet.

It has been specially conceived for personnel with the necessary qualifications.

1.2.1

Prescribed use

Danger

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

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

1.2.2

Notes concerning planning /installation of this product

Danger

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


1-3


1.3

Description of symbols used

Danger

This sign can be found next to all notes that indicate a source of hazards. This can refer to danger to personnel or damage to the system (hardware and software) and to the facility.

This sign means for the operator: work with extreme caution.

Attention

This sign can be found next to all notes that indicate a potential hazard.

This can refer to possible danger to personnel and damages to the system (hardware and software) and to the facility.

Note

This sign can be found next to all general notes that supply important information about one or more operating steps. These specific notes are intended to make operation easier and avoid unnecessary work due to incorrect operation.

1-4


List of revisions

1.4

List of revisions

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

Table 1:

List of revisions

Chapter

4

5

Subject/

Description

Status and Control word of the gateway (page

4-23)

Assembly Object,

Mapping of process data (page

5-13)

RFID-A support, Process Data Class (VSC102) (page

5-30)

RFID-S module class (VSC124) (page 5-85)

new

X

changed deleted

X

X

X

Note

The publication of this manual renders all previous editions invalid.


1-5


1-6


2 BL67 philosophy

2.1

2.1.1

2.1.2

2.2

2.2.1

2.2.2

2.2.3

2.2.4

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

Flexibility ............................................................................................................................................... 2

Convenient handling............................................................................................................................. 2

BL67 components.............................................................................................................................. 3

Gateways.............................................................................................................................................. 3

Electronic modules ............................................................................................................................... 4

– Power feeding modules..................................................................................................................... 4

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

End plate .............................................................................................................................................. 5


2-1

BL67 philosophy

2.5

The basic concept

BL67 is a modular IP67 I/O-system for use in industrial automation. It connects the sensors and actuators in the field to the higher-level master.

BL67 offers modules for practically all applications:

Digital input and output modules

Analog input and output modules

Technology modules (RS232 interface,...)

A complete BL67 station counts as one station on the bus and therefore occupies one fieldbus address in any given fieldbus structure. A BL67 station consists of a gateway, power distribution modules and I/

O-modules.

The connection to the relevant fieldbus is made via the bus-specific gateway, which is responsible for the communication between the BL67 station and the other fieldbus stations.

The communication within the BL67 station between the gateway and the individual BL67 modules is realized via an internal module bus.

Note

The gateway is the only fieldbus-dependent module on a BL67 station. All other BL67 modules are not dependent on the fieldbus used.

2.5.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 industries.

2.5.2

Convenient handling

All BL67 modules, with the exception of the gateway, consist of a base module and an electronic module.

The gateway and the base modules are snapped onto a mounting rail or are directly mounted onto a mounting plate. The electronic modules are plugged onto the appropriate base modules.

After disconnection of the load, the electronic modules can be plugged or pulled when the station is being commissioned or for maintenance purposes, without having to disconnect the field wiring from the base modules.

2-2


BL67 components

2.6

BL67 components

Figure 1:

BL67 station

B

A gateway

Belectronic

module

Cbase module

A

C

2.6.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-ASSISTANT.

Figure 2:

BL67 gateway


2-3

BL67 philosophy

2.6.2

Electronic modules

Electronic modules contain the functions of the BL67 modules (Power Feeding modules, digital and analog input/output modules, technology modules).

Electronic modules are plugged onto the base modules and are not directly connected to the wiring.

They can be plugged or pulled when the station is being commissioned or for maintenance purposes, without having to disconnect the field wiring from the base modules.

Figure 3: electronic module

Power feeding modules

Power Feeding modules distribute the required 24 V DC field voltage to the I/O-modules. They are necessary for building groups of modules with different potentials within a BL67 station, or if the rated supply voltage for the outputs cannot be guaranteed.

Power Feeding modules are potentially isolated from the gateway, the adjoining power supply module and the I/O-modules to the left side.

Note

For detailed information about the individual BL67 I/O components, please refer to the chapters 2 to 8 of the manual "BL67- I/O-modules" (TURCK Documentation-No.: German

D300572; English: D300529).

2-4


BL67 components

2.6.3

Base modules

The field wiring is connected to the base modules.

These are available in the following connection variations:

1 x M12, 2 x M12, 2 x M12-P, 4 x M12, 4 x M12-P

4 x M8, 8 x M8

1 x M12-8

1 × M23, 1 x M23-19

1 x 7/8" (for Power Feeding Module)

Figure 4: example of a base module

2.6.4

End plate

An end plate on the right-hand side physically completes the BL67 station.

It protects the module bus connections of the last base module in a station and guarantees the protection class IP67.

Figure 5: end plate


2-5

BL67 philosophy

2-6


3 EtherNet/IP

3.1

3.1.1

3.1.2

3.1.3

3.1.4

3.1.5

System description ........................................................................................................................... 2

– IP (Internet Protocol).......................................................................................................................... 2

– TCP (Transmission Control Protocol) ................................................................................................ 2

Network-topology................................................................................................................................. 3

– Transmission media........................................................................................................................... 3

Addressing on EtherNet/IP ................................................................................................................... 4

– Ethernet MAC-ID ............................................................................................................................... 4

– IP address.......................................................................................................................................... 4

Network classes ................................................................................................................................... 4

Checking the communication via "ping-signals".................................................................................. 5

ARP (Address Resolution Protocol) ...................................................................................................... 6


3-1

EtherNet/IP

3.1

System description

Ethernet Industrial Protocol (EtherNet/IP) is a communication system for industrial applications.

It is used to exchange time-critical application information between industrial devices such as simple I/

O devices (sensors/actuators) or even complex control devices (robots, programmable logic controllers, etc.).

EtherNet/IP is an open network because it uses:

IEEE 802.3 Physical and Data Link standard

Ethernet TCP/IP protocol suite (Transmission Control Protocol/Internet Protocol), the Ethernet industry standard.

Common Industrial Protocol (CIP), the protocol that provides real-time I/O messaging and information/peer-to-peer messaging. ControlNet and DeviceNet networks also use CIP.

Note

For further infomation about CIP and EtherNet/IP™, please contact also the user organization

ODVA (www.odva.org).

IP (Internet Protocol)

The Internet Protocol is a connection-free transport protocol. Since the protocol does not use acknowledgement messages, telegrams can get lost. Therefore it is not suitable for safe data transfer.

The main functions of the internet protocol are the addressing of hosts and the fragmentation of data packages.

TCP (Transmission Control Protocol)

The Transmission Control Protocol (TCP) is a connection-oriented transport protocol and is based on the Internet Protocol. A safe and error-free data transport can be guaranteed by means of certain error diagnostic mechanisms. For example, the acknowledgement and time monitoring of telegrams.

3-2



UDP/IP (User Datagram Protocol)

UDP/IP provides the fast, efficient data transport necessary for real-time data exchange. To make

EtherNet/IP successful, CIP has been added on top of TCP/UDP/IP to provide a common application layer.

Figure 6:

EtherNet/IP in

OSI 7 layer model

User

Layer

Semi

Devices

Pneu

Valve

AC

Drives

Position

Controllers

Other

Profiles

Application Object Library

Application

Layer

Transport and Data

Link Layer

DeviceNet

DLL

Transport

Physical

Layer

DeviceNet physical layer

Application Layer

Explicit, I/O, Routing

ControlNet

DLL

Transport

ControlNet physical layer

Encapsulation

UDP

TCP

IP

Ethernet physical layer tbd tbd

ATM, Firewire,

USB, Blue Tooth

Ethernet/IP

3.1.1

Network-topology

EtherNet/IP network uses an active star topology in which groups of devices are connected point-topoint to a switch.

Products with both transmission speeds (10 and 100 Mbit/s) can be used in the same network and most

Ethernet switches will negotiate the speed automatically.

Transmission media

For communication via Ethernet, different transmission media can be used:

coaxial cable (10Base5)

optical fibre (10BaseF)

twisted two-wire cable (10BaseT) with shielding (STP) or without shielding (UTP)


3-3

EtherNet/IP

3.1.2

Addressing on EtherNet/IP

Ethernet MAC-ID

The Ethernet MAC-ID is a 6-byte-value which serves to identify an Ethernet device. The MAC-ID is determined for each device by the IEEE (Institute of Electrical and Electronics Engineers, New York).

The first 3 bytes of the MAC-ID contain a manufacturer identifier (Turck: 00:07:46:xx:xx:xx). The last 3 bytes can be chosen freely by the manufacturer for each device and contain a serial number.

The MAC-ID can be read from the module using the software tool "I/O-ASSISTANT".

IP address

Each Ethernet-host receives its own IP address. In addition, the node knows its netmask and the IP address of the default gateway.

The IP address is a 4-byte-value which contains the address of the network to which the node is connected as well as the host address in the network.

The IP address of the BL67-GW-EN-IP gateway is predefined as follows:

IP address: 192.168.1.××× netmask: 255.255.255.0

gateway: 192.168.1.001

The netmask shows which part of the IP address defines the network as well as the network class, and which part of the IP address defines the single node in the network.

In the example mentioned above, the first 3 bytes of the IP address define the network. They contain the subnet-ID 192.168.1.

The last byte of the IP address defines the node’s address within the network.

Note

In order to build communication between a PC and an Ethernet-module, both have to be nodes on the same network.

If necessary, the nodes’ network addresses have to be adapted one to another. Please read

Chapter 5, ’’Changing the IP address of a PC/ network interface card’’, Page 5-5.

3.1.3

Network classes

The available networks are divided into the different network classes A, B, and C.

Figure 7:

Network classes

Class

A

B

C

Network addresses

1.×××.×××.×××-126.×××.×××.×××

128.0.×××.××× -191.255.×××.×××

192.0.0.××× - 223.255.255.×××

Bytes for net address

Bytes for host address

No. of possible networks/ hosts

1

2

3

3

2

1

126/ 2

24

2

14

/ 2

16

2

21

/ 256

According to their predefined address 192.168.1.××× BL67 gateways are nodes on a Class C network.

3-4



3.1.4

Checking the communication via "ping-signals"

You can check the communication between nodes in a network using ping-signals in the DOS-prompt of your PC.

For that purpose, enter the command "ping" and the IP address of the network node to be checked.

If the node answers the ping-signal, it is ready for communication and takes part in the data transfer.

Figure 8: ping-signal


3-5

EtherNet/IP

3.1.5

ARP (Address Resolution Protocol)

In each TCP/IP-capable computer, ARP serves to clearly assign the worldwide unique hardware addresses (MAC-IDs) to the single IP addresses of the network nodes via internal tables.

Using ARP in the DOS-prompt, every node in a network can be clearly identified via its MAC-ID.

Write a ping command for the respective station/ IP address: (example: "x:\\ping 192.168.1.100").

Via the command "x:\\arp -a", the MAC-ID (00-07-46-ff-60-13) for this IP address is determined. This

MAC-ID clearly identifies the network node.

Figure 9:

Determination of the MAC-ID of a BL67 module via ARP

3-6


4.5

4.5.1

4.5.2

4.5.3

4.5.4

4.5.5

4.5.6

4.5.7

4.5.8

4.6

4.7

4.7.1

4.7.2

4 Technical features

4.1

4.2

4.3

4.3.1

4.4

4.4.1

4.4.2

4.4.3

4.8

4.8.1

4.8.2

4.9

General.............................................................................................................................................. 2

Function ............................................................................................................................................ 3

Technical data .................................................................................................................................. 4

Gateway structure ................................................................................................................................ 4

Connection possibilities.................................................................................................................... 7

Field bus connection ............................................................................................................................ 7

– Ethernet-connector............................................................................................................................ 7

– DeviceNet-connector ........................................................................................................................ 7

Power Supply via 7/8" connector ......................................................................................................... 7

Service interface connection ................................................................................................................ 8

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

– Connection using commercially available cables.............................................................................. 9

Address setting for EtherNet/IP ...................................................................................................... 11

LED-behavior...................................................................................................................................... 11

Default setting of the gateway............................................................................................................ 11

Address setting via the rotary-mode .................................................................................................. 12

Address setting via BootP-mode ....................................................................................................... 13

Address setting via DHCP-mode ....................................................................................................... 14

Address setting via PGM-mode ......................................................................................................... 15

Address setting via PGM-DHCP ........................................................................................................ 15

Address setting via the software I/O-ASSISTANT.............................................................................. 16

SET button....................................................................................................................................... 18

Status indicators/ diagnostic messages gateway ........................................................................... 19

Diagnostic messages via LEDs .......................................................................................................... 19

Diagnostic messages via the process data........................................................................................ 21

– Summarized diagnostics ................................................................................................................ 21

– Scheduled diagnostics .................................................................................................................... 22

Status and Control word of the gateway ........................................................................................ 23

Status word ........................................................................................................................................ 23

Control word....................................................................................................................................... 23

Module specific diagnostic messages ............................................................................................. 24


4-1


4.1

General

This chapter contains the general technical description of the BL67 gateway for EtherNet/IP.

This chapter describes: the technical data, the connection possibilities, the addressing of the gateway etc.

4-2


Function

4.2

Function

The gateway for EtherNet/IP is the connection between the BL67 I/O-modules and the EtherNet/IPnetwork.

The gateway is a communication adapter according to CIP specification that handles the entire process data traffic between the I/O-level and the fieldbus and generates diagnostic information for higherlevel nodes and the software tool I/O-ASSISTANT.

Note

A description of a possible DeviceNet-Master-function of EtherNet/IP gateways can be found in a separate manual (D301118) which can be downloaded from the TURCK homepage www.turck.com.


4-3


4.3

Technical data

Figure 10:

BL67-GW-EN-IP

Apower supply

BEthernet

CBL Remote (see

manual

D301118)

DSET-button

Eservice-

interface

Frotary coding

switches

Gmodule bus LED

Hdesignation

Istatus LED

JLEDs for

supply voltage monitoring

Kn.c.

LEthernet LEDs

F

E

D

C

B

A

G

J

K

L

H

I

4.3.1

Gateway structure

The BL67 gateway has the following structure:

Figure 11:

Gateway structure

service interface mC

PS/2 memory

1

2

2

1

4

3

Ethernet

5

3

4

V i

Ethernet interface

5 VDC

24 VDC module bus interface short circuit protection

BL67-

Systembus communication bus

V

0

Power bus

V sens

PE

GND

4-4


Technical data

Table 2:

Technical data

Ethernet gateway

Supply voltage

Demands on the voltage supply acc. to EN 61131-2

System supply V

I

(U

B

) permissible range

24 VDC

18 to 30 VDC

Field supply V

O

(U

L

) permissible range

I sys

24 VDC

18 to 30 VDC

600 mA

I

I

MB

VI max. 1,3 A max. 4 A used to generate the galvanically isolated module bus supply current consumption CPU + module bus at maximum system extension maximum output current of module bus supply short-circuit and overload protection of the sensor supply from gateway or power feeding module

Isolation voltages

U

RS

(Ethernet/ service interface)

U

EN

(Ethernet/ module bus)

U sys

(V

O

/V

I to U sys

)

Ambient conditions

Ambient temperature

– t

Ambient

– t

Store

Relative humidity

Climatic tests

Noxious gas

Resistance to vibration

Protection class

Shock resistant

Topple and fall/ free fall

Emitted interference

High-frequency, radiated

Immunity to interference

500 V AC

500 V DC

1000 V DC

0 to +55 °C /32 to 131 °F

- 25 to +85 °C / - 13 to 185 °F according to IEC 61131-2 according to IEC 61131-2 according to IEC 68068-42/43 according to IEC 61131-2

IP 67 according to IEC 60529 according to IEC 61131-2 according to IEC 61131-2 according to EN 55011, Class A


4-5


AI/O-line-length

≤ 30 m

Static electricity

Electromagnetic HF fields according to IEC 61131-2 according to IEC 61131-2

Fast transients (Burst) according to IEC 61131-2

Conducted interferences induced by HF fields according to IEC 61000-4-6

10 V

Criteria A

High energy transients (Surge)

A

voltage supply according to IEC 61000-4-5

0,5 kV CM, 12

Ω/ 9 μF

0,5 kV DM, 2

Ω/ 18 μF

Criteria B

Reliability

Operational life MTBF

Electronics modules pull/plug cycles

Dimensions

Width x length x height

(mm/inch) min. 120000 h

20

64,5 x 145,0 x 77,5 /

2,54 x 5,71 x 3,05

Danger

This device can cause radio disturbances in residential areas and in small industrial areas

(residential, business and trading). In this case, the operator can be required to take appropriate measures to suppress the disturbance at his own cost.

4-6


Connection possibilities

4.4


4.4.1

Field bus connection

Ethernet-connector

The connection to Ethernet is realized via a 4-pole and D-coded female connector on the gateway according to CIP-standards.

Figure 12:

M12-female connector

1

4 3

2

Table 3:

Pin assignment of the Ethernet connector

2

3

Pin-No.

1

4

TD+

RD+

TD-

RD-

Transmission Data +

Receive Data +

Transmission Data -

Receive Data -

DeviceNet-connector

For the description of a possible DeviceNet funciton of an EtherNet/IP gateway, please refer to the separate manual D301118.

4.4.2

Power Supply via 7/8" connector

The power supply is realized via a 7/8" male connector on the gateway.

Figure 13: power supply via 7/8" male connector

1

2

5

4

3

Table 4:

Pin assignment of the 7/8" power supply connector

Pin-

No.

1

2

3

4

5

Color 7/8"

black blue

GND

GND green/yellow PE brown V

I

(U

B

) white V

O

(U

L

)

Description

Protective earth

Feed-in of nominal voltage for input modules

(sensor supply); also used for the generation of the system supply voltage

Feed-in of nominal voltage for output modules

(can be switched off separately)


4-7


4.4.3

Service interface connection

Two types of cables can be used to connect the service interface (female PS/2 connector) to a PC for the purpose of using

I/O-ASSISTANT (project planning and diagnostic software).

special I/O-ASSISTANT-connection cable from TURCK

(IOASSISTANT-ADAPTERKABEL-BL20/BL67; Ident-no.: 6827133)

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

Note

Furthermore, in Ethernet/IP networks, the connection to the software I/O-ASSISTANT can also be realized directly via the Ethernet bus cable.

Figure 14:

BL67-gateway connected to PC via special cable

Connection with I/O-ASSISTANT-connection cable

B

C

A

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

Figure 15:

PS/2 male connector on the connection cable to the gateway (top view)

5

4 3

6 1

2

Figure 16:

9-pole SUB-D female connector on the cable for connecting to PC

(top view)

5 4 3 2 1

9 8 7 6

4-8



Figure 17:

Connection between PC and

BL67 gateway via commercially available cable

ASUB-D- female

BPS/2-female <–>

PS/2-male

CPS/2-male

Connection using commercially available cables

A further possibility to connect PC and BL67 gateway is to use a commercially available connection and adapter cable.

The connection shown in the following figure (PS2-male/ PS2-male) is a 6-wire 1:1 connection.

B

A

C

The following two cables are necessary:

1 x PS/2 cable (PS/2 male connector/PS/2 male connector) (commercially available keyboard extension cable)

1 x adapter cable (PS/2 female connector/SUB-D female connector) (commercially available extension cable for a PC mouse)

Figure 18:

PS/2 female connector on the gateway

(top view)

2

3 4

1 6

5

Figure 19:

9-pole SUB-D male connector on PC (top view)

1 2 3 4 5

6 7 8 9


4-9


Pin assignment

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

Table 5:

Pin assignment when using PS/2 cable and adapter

PS/2

Pin-No.

Standard PS/2 male connector

Anot supported by

all adapter cables.

1

2

CLK

GND

3

4

DATA n.c. (DATA2)

5

6

+5V n.c. (CLK2)

BL67 gateway: PS/2 female connector

Pin-No.

Male connector

+5V

(from gateway)

GND not connected

TxD

/CtrlMode

RxD

9-pole serial interface on PC

4, 6

A

5

–

2

7

3

DTR, DSR

GND

–

RxD

RTS

TxD

4-10


Address setting for EtherNet/IP

4.5


Addressing the BL67 EtherNet/IP gateway can be done via different modes:

rotary mode (manual addressing via rotary coding-switches)

PGM mode (manual addressing via software)

BootP mode, DHCP mode (automatic addressing via BootP/DHCP-server at the boot-up of the gateway).

Setting the address mode is done through the 3 rotary coding-switches on the gateway.

Note

It is not necessary to address the station’s internal module bus.

Attention

The cover of the decimal rotary coding-switches must be closed by tightening the screw after use.

The seal in the cover must not be damaged or slipped.

The protection class IP67 can only be guaranteed when the cover is closed correctly.

4.5.1

LED-behavior

During it’s start-up, the module waits for the address setting via the BootP-server. This is indicated by the red flashing "MS" LED. The LED begins to flash green as soon as the address setting via the server is completed. The station is ready for communication.

4.5.2

Default setting of the gateway

The gateway’s default-settings are as follows:

IP address subnet mask default gateway

192.168.001.254

255.255.255.000

192.168.001.001

Note

The gateway can be reset by the user to these default settings at any time.

To reset the gateway, set the three coding-switches on the gateway to "000" followed by a power-on reset.


4-11


Figure 20:

Decimal rotary coding-switches for the EtherNet/

IP address setting

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3 x 100 x 10 x 1

000: 192.168.1.254

1 - 254: static rotary

300: BootP

400: DHCP

500: PGM

600: PGM-DHCP

Attention

After every change of the address-mode, a voltage reset must be carried done.

4.5.3

Address setting via the rotary-mode

When using the rotary-mode, the last byte of the gateway’s IP address can be set via the rotary codingswitches on the gateway.

Note

All other network settings are stored in the module’s non-volatile EEPROM and can not be changed in the rotary-mode.

Addresses in the range from 1 to 254 can be allocated. Addresses 0 and 255 are reserved for broadcast messages in the subnet.

4-12



The following example shows the setting of address 173.

Figure 21:

Address setting

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

× 100

× 10

× 1

Attention

The settings carried out in the rotary-mode are not stored in the module’s EEPROM. Thus, they will get lost in case of a subsequent address-assignment via a BootP/ DHCP or PGM.

Attention

After changing the position of the rotary coding-switches, a voltage reset must be done to store the new address.

4.5.4

Address setting via BootP-mode

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 must be set to "300".

Figure 22:

BootP-mode

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

× 100

× 10

× 1


4-13


Note

The IP address, as well as the default subnet mask assigned to the gateway by the BootPserver, are stored in the gateway’s non-volatile memory.

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.

4.5.5

Address setting via DHCP-mode

Address setting is carried out by a DHCP-server in the network after the start-up of the gateway.

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

Figure 23:

DHCP-Modus

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

× 100

× 10

× 1

Note

The IP address, as well as the default subnet mask assigned to the gateway by the DHCPserver, are stored in the gateway’s non-volatile memory.

If the gateway is subsequently switched to rotary- or PGM-mode, the settings carried out via

DHCP (IP address, subnet mask, etc) will read from the module’s EEPROM.

DHCP supports three mechanisms for IP address allocation:

In "automatic allocation", the DHCP-server assigns a permanent IP address to a client.

In "dynamic allocation", DHCP assigns an IP address to a client for a limited period of time. After this time, or until the client explicitly relinquishes the address, the address can be re-assigned.

In "manual allocation", a client's IP address is assigned by the network administrator, and DHCP is used simply to convey the assigned address to the client.

4-14



4.5.6

Address setting via PGM-mode

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 must be set to "500".

Figure 24:

PGM-mode

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

× 100

× 10

× 1

Note

In the PGM-mode, all network settings (IP address, subnet mask, etc.) are read from the module’s internal EEPROM.

Settings carried out in the rotary-mode are stored in the module’s non-volatile EEPROM.

4.5.7

Address setting via PGM-DHCP

This mode operates exactly like the PGM-mode except that when the gateway is initially powered in this mode it will broadcast its MAC ID (similar to DHCP mode).

But, in contrast to the regular DHCP mode, the DHCP transmission on startup can be enabled/disabled via TCP Object attributes in EthernetIP.

In order to activate the PGM-DHCP-mode, the rotary coding-switches must be set to "600".

Figure 25:

PGM-DHCPmode

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

8

9

7

6

0

5

1

2

4

3

× 100

× 10

× 1

The I/O-ASSISTANT can also be used to set the IP Address in this mode.

This mode is the Out-of-the-Box mode fo the gateway and provides powerful and convenient Start-up features.


4-15


1 DHCP start up –if network contains DHCP server and/or automated configuration setup

2 Easy Rockwell BOOTP/DHCP-Server manipulation allowing TCP object access.

4.5.8

Address setting via the software I/O-ASSISTANT

The software-tool I/O-ASSISTANT enables direct access to the Ethernet-network via the fieldbus cable.

Naturally, access to the single station via the service interface at the gateway is also possible.

The IP address, as well as the subnet mask of the TURCK Ethernet modules, can be changed according to the application by using the Busaddress Management function of the BL Service Ethernet interface in the I/O-ASSISTANT V3.

Changes in the network-configuration are only accepted in the PGM-mode and the PGM-DHCP mode

(see

Seite 4-15 ) of the gateway (see Seite 4-15

).

Figure 26:

Opening the

Busaddress management

4-16



Figure 27:

Search the network for nodes

The network connected to the used network card can be scanned using the “Search“ function of the

Busaddress management.

Figure 28:

Change the IP address of a node

Attention

Please observe that, if the system integrated Windows-firewall is activated, difficulties may occur during the communication between the module and the Address-tool. The firewall may possibly inhibit the access of the tool on Ethernet.

Note

For further information about the Busaddress management in the software tool I/O-

ASSISTANT, please read the online help delivered with the tool.


4-17


4.6

SET button

The Current Configuration of the BL67 EtherNet/IP station is saved as the Actual Configuration when the SET button on the gateway is pressed for approximately 10 seconds; it is also saved to the both the

Temp-Required Configuration Memory and the Required Configuration Memory. The LED "GW" flashes.

In addition to that, pressing the SET button reads a possible BL Remote subnet connected to the gateway (see separate manual D301118).

4-18


Status indicators/ diagnostic messages gateway

4.7


The gateway sends the following diagnostic messages:

undervoltage monitoring for system- and field supply,

monitoring of the station status,

monitoring of the communication via the internal module bus,

monitoring of the communication to Ethernet

monitoring of the gateway status

Diagnostic messages are displayed in different ways:

via the LEDs

via the gateway’s status-word in the process data

via the respective configuration software

4.7.1

Diagnostic messages via LEDs

Every BL67 gateway displays the following statuses via LEDs:

2 LEDs for module bus communication (module bus LEDs): GW and IOs

2 LEDs for the Ethernet communication (fieldbus-LEDs): LNK/ACT and MS.

3 LEDs for monitoring the voltage supply (system, V

CC

/ inputs, V

i

/ outputs, V

o

).

1 LED for the BL Remote-function of the gateway (see separate manual D301118)

Table 6:

LED-displays

LED

GW

Status

Off

Green

Green, flashing,

1 Hz

Green, flashing,

4 Hz

Red

Meaning Remedy

CPU not supplied.

Firmware active, gateway ready to operate and transmit

Firmware not active.

-

If LED "IOs" red

→ Firmware download necessary

Firmware active, gateway hardware defect.

Replace the gateway.

Controller is not ready, VCC level is not within the required range

→ possible reasons:

– too many modules connected to the gateway

– short circuit in connected module

– hardware error in gateway

– Check wiring at the gateway and the voltage supply.

– Dismount modules

– Replace the gateway.


4-19


Table 6:

LED-displays

LED

IO

V

V

CC

O

Status Meaning Remedy

Off

Green

Green, flashing

1 Hz

Green, flashing

4Hz

Red

Red flashing,

1 Hz

Red flashing, 4

Hz no module bus communication

Red/green flashing, 1 Hz

Off

Maximum number of modules at the gateway is exceeded.

– Check the number of modules connected to the gateway, dismount modules

Controller is not ready, V

CC

level is not within the required range

→ possible reasons:

– too many modules connected to the gateway

– short circuit in connected module

– hardware error in

– gateway

– Check wiring at the gateway and the voltage supply.

– Dismount modules

– Replace the gateway.

Non-adaptable modification of the physically connected station.

– Compare the planned BL67 station with the physical station.

– Check the physical station for defective or incorrectly fitted electronics modules.

Adaptable modification of the physically connected station; data transfer possible

CPU not supplied

– At least one module has to be plugged and has to be able to communicate with the gateway.

– Check the physical station for pulled or new but not planned modules.

Green

Off

CPU not supplied.

Module bus is running, the configured module bus station corresponds to the physically connected station, communication is active.

-

Station is in the

I/O-ASSISTANT Force Mode.

– Check the voltage supply at the gateway.

– Deactivate the

I/O-ASSISTANT Force Mode.

Module bus and CPU running

No voltage supply.

– Check the system supply at the gateway.

-

Check the system supply at the gateway.

Green

Green flashing, 1 Hz

Green flashing, 4 Hz

Output supply ok.

Undervoltage V

O

, system running

Overvoltage V

O

, system running

– Check the system supply at the gateway

4-20



Table 6:

LED-displays

LED Status Meaning Remedy

V

I

LNK/

ACT

MS

Off

Green

Green, flashing, 1Hz

No voltage supply.

sensor supply ok.

undervoltage V

I

, system running

– Check the wiring of the voltage supply at the gateway

-

– Check the wiring of the voltage supply at the gateway

Green, flashing, 4Hz

Red

Off

Green

Green flashing Ethernet Traffic 100 Mbit/s

Yellow Link, 10 Mbit/s

Ethernet Traffic 10 Mbit/s Yellow, flashing

Green

Overvoltage V

I

, system running

Short circuit or overload at sensor supply

→ sensor supply is switched off

– Automatic restart when debugging.

No Ethernet link

Link, 100 Mbit/s

– Check the Ethernet-connection

Green, flashing

Displays an active CIP Class 1

I/O connection

Gateway is ready for operation

Red

Red, flashing

Gateway indicates error

DHCP/BootP search of settings

4.7.2

Diagnostic messages via the process data

Besides the evaluation of diagnostic data via Explicit Messages, BL67 for EtherNet/IP offers the possibility of mapping diagnostic data into the gateways’ process data.

2 different forms of diagnostic data handling are provided:

Summarized Diagnostics

Scheduled Diagnostics

Summarized diagnostics

Note

The Summarized Diagnostics possibility is only implemented in gateways with Rev.

≥ 1.3.0.16.

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 slice the bit will be set to "1".


4-21


Values:

0 = ok

1 = module sends diagnostics, wrong module or module pulled (acc. to VSC 100, Gateway Class, Attr.

116,

Seite 5-26

).

The diagnostic bits are placed at the end of the input data. The diagnostic data start WORD aligned (see

Seite 5-15 ).

Scheduled diagnostics

Note

The Scheduled Diagnostics possibility is only implemented in gateways with Rev.

≥ 1.3.0.16.

The scheduled diagnostic data map 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

0 0

1 n

Data

Slot number of the module which sends the diagnostic data.

State of the 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, Seite 5-26

)

Module diagnostics from the module actually referenced by the round robin mechanism.

The scheduled diagnostic data is placed at the end of the input data and after the summarized diagnositic data (see

Seite 5-15

).

4-22


Status and Control word of the gateway

4.8

Status and Control word of the gateway

4.8.1

Status word

The gateways status word is mapped into the process data (see also

Mapping of process data (page

5-13)

and contains common diagnostic messages such as:

gateway errors

module bus errors

voltage errors

configuration/ diagnostic warnings

Table 7:

Status Word

Bit-No.

Meaning

15

14

13

12

11

"I/O Controller Error„The communication controller for the I/O-system is faulty.

"Force Mode Active Error" The Force Mode is activated.

reserved

4

3

6

5

8

7

10

9

2

1

0

"I/O CfgModified Error“ The I/O-configuration has been changed and is now incompatible.

"I/O Communication Lost Error" No communication on the I/O module bus.

"U sys

too low" System supply voltage too low (< 18 VDC).

"U sys

too high" System supply voltage too high (> 30 VDC).

"U

L

too low" Load voltage too low (< 18 VDC).

"U

L

too high" Load voltage too high (> 30 VDC)

"I sys

too high" Overload of the system voltage supply.

reserved

"I/O CfgModified Warning" reserved

"I/O DiagActive Warning" At least one I/O-module sends active diagnostics.

It can also be accessed via the Gateway Class VSC 100, Object Instance 2, Gateway Instance, attribute

109 (0×6D) "STATUS REGISTER 2" (for detailed information, see

STATUS REGISTER 2 (page 5-26)

.

4.8.2

Control word

The control word is mapped into the station‘s process data. At present, it is not used but reserved for

further use (see also Mapping of process data (page 5-13) .


4-23


4.9

Module specific diagnostic messages

Detailed module specific diagnostic messages can be read out from Gateway Class VSC 100, Object

Instance 2, Gateway Instance, attribute 116 (0×74)

MODULE DIAG SUMMARY .

4-24


5 Implementation of EtherNet/IP

5.1

5.1.1

5.1.2

The EtherNet/IP Communications Profile ......................................................................................... 3

I/O Messages........................................................................................................................................ 3

Communications Profile of the BL67 EtherNet/IP gateway.................................................................. 4

– Point to point ..................................................................................................................................... 4

– Multicast ............................................................................................................................................ 4

– COS I/O Connection.......................................................................................................................... 4

– Cyclic I/O Connection ....................................................................................................................... 4

– UCMM ............................................................................................................................................... 4

– Connected Explcit messaging........................................................................................................... 4

5.2

5.2.1

5.2.2

5.2.3

5.2.4

Classes and instances of the EtherNet/IP-gateway ........................................................................... 5

EtherNet/IP Standard Classes.............................................................................................................. 5

Identity Object ...................................................................................................................................... 6

Message Router Object........................................................................................................................ 7

– Message Router Request/Response Formats .................................................................................. 8

Assembly Object ................................................................................................................................ 12

– Instance 101 .................................................................................................................................... 13

– Instance 102 .................................................................................................................................... 13

– Instance 103 + Instance 104 ........................................................................................................... 13

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

– Data mapping for gateways with rev. < 1.3.0.16............................................................................. 14

– Data mapping for gateways with rev.

≥ 1.3.0.16 ............................................................................15

Connection Manager Object .............................................................................................................. 16

Port Object ......................................................................................................................................... 16

TCP/IP Interface Object...................................................................................................................... 17

Ethernet Link Object ........................................................................................................................... 21

5.2.5

5.2.6

5.2.7

5.2.8

5.3

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

5.3.1

5.3.2

5.3.3

5.3.4

5.3.5

5.3.6

5.3.7

Class instances of the VSC ................................................................................................................ 25

Gateway Class (VSC 100)................................................................................................................... 26

– Object instances.............................................................................................................................. 26

Terminal Slot Class (VSC 101)............................................................................................................ 28

– Object instance................................................................................................................................ 28

Process Data Class (VSC102) ............................................................................................................ 30

– Object instance 1, standard input process data (compressed) ..................................................... 30

– Object instance 2, standard output process data (compressed) .................................................... 30

– Object instance 3, diagnostic instance .......................................................................................... 31

– Object instance 4, COS/CYCLIC instance ...................................................................................... 31

Power Supply Module Class (VSC103) .............................................................................................. 32

– Object instance................................................................................................................................ 32

Digital Input Module Class (VSC104).................................................................................................. 34

– Object instance................................................................................................................................ 34

Digital Output Module Class (VSC105)............................................................................................... 36

– Object instance................................................................................................................................ 36

5.3.8

5.3.9

Analog Input Voltage Module Class (VSC106) ................................................................................... 38

– Object instance................................................................................................................................ 38

Analog Output Voltage Module Class (VSC107) ................................................................................ 40

– Object instance................................................................................................................................ 40

5.3.10

Analog Input Current Module Class (VSC108) ................................................................................... 42

– Object instance................................................................................................................................ 42

5.3.11

Analog Output Current Module Class (VSC109) ................................................................................ 44

– Object instance................................................................................................................................ 44


5-1

Implementation of EtherNet/IP

5.3.12

Analog Input RTD Module Class (VSC110) ........................................................................................46

– Object instance................................................................................................................................46

5.3.13

Analog Input THERMO Module Class (VSC111) ................................................................................50

– Object instance................................................................................................................................50

5.3.14

RS232 Module Class (VSC114) ..........................................................................................................53

– Object instance................................................................................................................................53

5.3.15

RS4xx Module Class (VSC115) ..........................................................................................................60

– Object instance................................................................................................................................60

5.3.16

SSI Module Class (VSC116) ...............................................................................................................67

– Object instance................................................................................................................................67

5.3.17

Digital Versatile Module Class (VSC117) ............................................................................................75

– Oject Instance..................................................................................................................................75

5.3.18

Analog Versatile Module Class (VSC118) ...........................................................................................79

– Object instance................................................................................................................................79

5.3.19

CVI Module Class (VSC119) ...............................................................................................................82

– Object instance................................................................................................................................82

5.3.20

RFID-S module class (VSC124) ..........................................................................................................85

– Object Instance ..............................................................................................................................85

5-2


The EtherNet/IP Communications Profile

5.1

The EtherNet/IP Communications Profile

EtherNet/IP is based on a connection-oriented communication model. This means that it is only possible to exchange data via specified connections assigned to the devices.

Communication between the nodes in the EtherNet/IP network can be carried out either via I/O

Messages or Explicit Messages.

5.1.1

I/O Messages

I/O Messages serve to exchange high priority process and application data over the network.

Communication between the slaves in the EtherNet/IP network is carried out according to the Server/

Client Model, which means a producing application transmits data to another or a number of consuming applications. It is quite possible that information is passed to a number of Application

Objects in a single device.


5-3


Explicit Messages

Explicit Messages are used to transmit low-priority configuration data, general management data or diagnostic data between two specific devices. This is a point-to-point connection in a Server/Client

System that requires a request from a client always to be confirmed by a response from the server.

Explicit messages, whether connected or unconnected, use the Message Router (for detailed information, read

section "Message Router Request/Response Formats“ , page 5-8 ).

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.

5.1.2

Communications Profile of the BL67 EtherNet/IP gateway

The EtherNet/IP gateway behaves as an EtherNet/IP Server in the network; the scanner of the higherlevel controller operates as a EtherNet/IP Client.

The following EtherNet/IP communications types are supported:

Point to Point or Multicast

Cyclic I/O Connection

Unconnected (UCMM) Explicit Messaging

Connected Explicit Messaging

Point to point

A connection that exists between two nodes only.

Multicast

A packet with a special destination address, which multiple nodes on the network may be willing to receive.

COS I/O Connection

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

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

Cyclic I/O Connection

Messages are triggered time-controlled in Cyclic I/O connections by means of a time generator.

UCMM

The EtherNet/IP gateway offers the option of establishing explicit messaging via the UCMM port

(Unconnected Message Manager Port).

UCMM-based explicit messaging is normally used for random, non-periodic requests. It is not recommended for frequent messaging because the UCMM input queue in a product is typically limited to just a few messages. Once this limit is reached, subsequent requests are ignored and must be retried.

Connected Explcit messaging

CIP is a connection-based system. For most communications between nodes, a connection is used.

A connection is a path or a virtual circuit between two or more end points in a system. The purpose is to transfer data in the most efficient manner possible.

The Connection ID is a number that is associated with a communication relationship. Receiving nodes decode this key to know whether they must accept the data or not.

5-4


Classes and instances of the EtherNet/IP-gateway

5.2


5.2.1

EtherNet/IP Standard Classes

The BL67 gateway supports the following EtherNet/IP Standard Classes in accordance with the CIP specification.

Table 8:

EtherNet/IP

Standard

Classes

Class

Code

01

(0×01)

Object-Name Description

02

(0×02)

04

(0×04)

06

(0×06)

Identity

Message Router

Assembly

The Identity Object is required on all devices and provides general information about the device. It enables clear and unambiguous identification of modules. Contains information such as manufacturer name, product type, ident number, revision number etc.

The Message Router Object provides a messaging connection point through which a Client may address a service to any object class or instance residing in the physical device.

The Assembly Object binds attributes of multiple objects, which allows data to or from each object to be sent or received over a single connection. Assembly objects can be used to bind input data or output data. The terms ”input” and ”output” are defined from the network’s point of view. An input will produce data on the network and an output will consume data from the network.

Connection

Manager

The Connection Manager Class allocates and manages the internal resources associated with both I/O and Explicit

Messaging Connections. The specific instance generated by the

Connection Manager Class is referred to as a Connection

Instance or a Connection Object.

Parameter Object currently not supported 15

(0×0F)

244

(0×F4)

245

(0×F5)

246

(0×F6)

Port Object Provides a standard way of describing a device’s ports.

TCP/IP Interface

Object

Ethernet Link

Object

Contains the device TCP/IP-related configuration information.

Contains link-specific counters and status information for an

Ethernet 802.3 communications interface.


5-5


5.2.2

Identity Object

The following description of the Identity Object is taken from the CIP specification, Vol. 1, Rev. 2.1, by

ODVA & ControlNet International Ltd. and adapted to BL67.

Class attributes

Table 9:

Class attributes

Attr. No.

1 (0×01)

2 (0×02)

6 (0×06)

7 (0×07)

Attribute Name

REVISION

MAX OBJECT INSTANCE

MAX CLASS ATTRIBUTE

MAX INSTANCE ATTRIBUTE

Table 10:

Instance attributes

Instance attributes

Attr. No.

1 (0×01)

Attribute Name

Get/

Set

VENDOR G

2 (0×02)

3 (0×03)

4 (0×04)

5 (0×05)

6 (0×06)

7 (0×07)

PRODUCT TYPE

PRODUCT CODE

REVISION

Major Minor

DEVICE STATUS

SERIAL NUMBER

PRODUCT NAME

LENGTH

NAME

G

G

G

G

G

G

Type

Get/

Set

G

G

G

G

Type

UINT

UINT

UINT

UINT

Description

Value

1

1

7

7

UINT

UINT

UINT

Contains the vendor ID, managed by the

Open DeviceNet Vendor Association, Inc.

(ODVA) and ControlNet International (CI):

TURCK = 48

Indicates the general type of product.

Communications Adapter

12 dez

= 0×0C

Identifies a particular product within a device type.

Default: 27229

STRUCT OF:

USINT

USINT

Revision of the item the Identity Object is representing.

0x01

0x02

WORD

UDINT

See Table 11: Device Status

Contains the ident-no. of the product (3 last bytes of the MAC-ID).

STRUCT OF

USINT

STRING

[13]

BL67-GW-EN-IP

5-6



Table 11:

Device Status

Device Status

Bit

0 to 1

2

3

4 to 7

Name

reserved

Configured reserved

Extended Device Status

Definition

Default = 0

TRUE

→ The application of the device has been configured (

≠ default-settings).

Default = 0

0011 = No I/O connections 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

Default = 0

Table 12:

Common services

8 to 15 reserved

Common Services

Service Code Class

01 (0x01) yes

Instance

yes

05 (0x05)

14 (0x0E)

16 (0x10) no yes no yes yes no

Service Name

Get_Attribute_All

Returns a predefined listing of this objects attributes.

Reset

Starts the Reset service for the device.

Get_Attribute_Single

Returns the contents of a specified attribute.

Set_Attribute_Single

Modifies a single attribute.

5.2.3

Message Router Object

This object provides a messaging connection point through which a Client may address a service to any object class or instance residing in the physical device.

The following description of the Message Router Object is taken from the CIP specification, Vol. 1, Rev.

2.1 by ODVA & ControlNet International Ltd. and adapted to BL67.


Attribute Name Type Value

Table 13:

Class attributes

Attr. No.

1 (0×01)

4 (0×04)

5 (0×05)

6 (0×06)

7 (0×07)

REVISION

OPTIONAL ATTRIBUTE NUMBER

OPTIONAL SERVICE NUMBER

MAX CLASS IDENTIFIER

MAX INSTANCE ATTRIBUTE

G

G

G

Get/

Set

G

G

UINT

UINT

UINT

UINT

UINT

0

7

1

0

2


5-7


Table 14:



Attr. No.

1 (0×01)

Attribute Name

Get/

Set

OBJECT LIST G

NUMBER

CLASSES

G

G

Type Description

STRUCT OF Structure with an array of object classcodes supported by the device.

UINT Depending

ARRAY of

UINT

UINT

Number of the classes supported by the gateway.

Count of the maximum number of connections supported.

Table 15:

Common services

2 (0×02) MAX NUMBER OF

CONNECTIONS

G

Common Services


01 (0x01) yes

14 (0x0E) yes

Instance

yes yes

Message Router Request/Response Formats

Message Router Request Format:

Service Name

Get_Attribute_All


Table 16:

Message Router

Request

Parameter

Service

Request Data

Data Type

USINT

Request Path Size USINT

Request Path Padded EPATH

Array of octed

Description

Service code of the request.

Number of 16 bit words in the "Request Path".

Array of bytes containing the information for the path of request (class ID, Instance ID, etc.) for this transaction.

Additional service specific data to be delivered in the

Explicit Messaging Request.

Message Router Response Format:

Table 17:

Message Router

Request

Parameter

Reply Service

General Status

Data Type

SINT

USINT

Description

Reply service code.

General Status Code according to CIP specification.

See Table 18: General Status Codes according to CIP spec.

Number of 16 bit words in "Additional Status".

Size of

Additional Status

USINT

Additional Status Array of USINT

Response Data Array of octet

Additional status.

Response data from request or additional error data if an error was indicated in "General Status".

5-8



Table 18:

General Status

Codes according to CIP spec.

Status

Code (hex)

Status Name

00

01

02

Success

Connection failure

03

Description

Service successfully performed by the object specified.

A connection related service failed along the connection path.

Resource unavailable Resources needed for the object to perform the requested service were unavailable.

Invalid parameter value

See Status Code 0x20, which is the preferred value to use for this condition.

04

05

Path segment error The path segment identifier or the segment syntax was not understood by the processing node. Path processing shall stop when a path segment error is encountered.

Path destination unknown

The path is referencing an object class, instance or structure element that is not known or is not contained in the processing node. Path processing shall stop when a path destination unknown error is encountered.

06

07

08

09

0A

0B

0C

Partial transfer

Connection lost

Service not supported

Only part of the expected data was transferred.

The messaging connection was lost.

The requested service was not implemented or was not defined for this Object Class/Instance.

Invalid attribute value Invalid attribute data detected.

Attribute list error An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero status.

Already in requested mode/state

The object is already in the mode/state being requested by the service.

Object state conflict The object cannot perform the requested service in its current mode/state.

0D

0E

0F

10

11

12

13

Object already exists The requested instance of object to be created already exists.

Attribute not settable A request to modify a non-modifiable attribute was received.

Privilege violation A permission/privilege check failed.

Device state conflict The device’s current mode/state prohibits the execution of the requested service.

Reply data too large The data to be transmitted in the response buffer is larger than the allocated response buffer.

Fragmentation of a primitive value

Not enough data

The service specified an operation that will fragment a primitive data value, i.e. half a REAL data type.

The service did not supply enough data to perform the specified operation.


5-9


Table 18:

General Status


Status

Code (hex)

Status Name

14 Attribute not supported

15

16

17

Too much data

Object does not exist

Service fragmentation sequence not in progress

Description

The attribute specified in the request is not supported.

The service supplied more data than expected.

The object specified does not exist in the device.

The fragmentation sequence for this service is not currently active for this data.

18

19

1A

1B

1C

1D

1E

1F

20

21

22

No stored attribute data

Store operation failure

Routing failure, request packet too large

Routing failure, response packet too large

Missing attribute list entry data

The attribute data of this object was not saved prior to the requested service.

The attribute data of this object was not saved due to a failure during the attempt.

The service request packet was too large for transmission on a network in the path to the destination. The routing device was forced to abort the service.

The service response packet was too large for transmission on a network in the path from the destination. The routing device was forced to abort the service.

The service did not supply an attribute in a list of attributes that was needed by the service to perform the requested behavior.

Invalid attribute value list

The service is returning the list of attributes supplied with status information for those attributes that were invalid.

Embedded service error

An embedded service resulted in an error.

Vendor specific error A vendor specific error has been encountered. The Additional

Code Field of the Error Response defines the particular error encountered. Use of this General Error Code should only be performed when none of the Error Codes presented in this table or within an Object Class definition accurately reflect the error.

Invalid parameter A parameter associated with the request was invalid. This code is used when a parameter does not meet the requirements of this specification and/or the requirements defined in an

Application Object Specification.

Write-once value or medium already written

Invalid Reply

Received

An attempt was made to write to a write-once medium (e.g.

WORM drive, PROM) that, has already been written, or to modify a value that cannot be changed once established.

An invalid reply is received (e.g. reply service code does not match the request service code, or reply message is shorter than the minimum expected reply size). This status code can serve for other causes of invalid replies.

5-10



Table 18:

General Status


Status

Code (hex)

Status Name

23 to 24

25

Description

Reserved by CIP for future extensions

Key Failure in path The Key Segment that was included as the first segment in the path does not match the destination module. The object specific status shall indicate which part of the key check failed.

26

27

Path Size Invalid The size of the path which was sent with the Service Request is either not large enough to allow the Request to be routed to an object or too much routing data was included.

Unexpected attribute in list

An attempt was made to set an attribute that is not able to be set at this time.

28

29

2A

2B to CF

D0 to FF

Invalid Member ID The Member ID specified in the request does not exist in the specified Class/Instance/Attribute

Member not settable A request to modify a non-modifiable member was received

Group 2 only server general failure

This error code may only be reported by DeviceNet Group 2

Only servers with 4K or less code space and only in place of

Service not supported, Attribute not supported and Attribute not settable.

Reserved by CIP for future extensions

Reserved for Object

Class and service errors

This range of error codes is to be used to indicate Object Class specific errors. Use of this range should only be performed when none of the Error Codes presented in this table accurately reflect the error that was encountered.


5-11


5.2.4

Assembly Object

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 Assembly Object is taken from the CIP specification, Vol. 1, Rev. 2.1 by

ODVA & ControlNet International Ltd. and adapted to BL67.


Type Value

Table 19:

Class attributes

Attr. No.

1 (0×01)

2 (0×02)

Attribute Name

REVISION

MAX OBJECT INSTANCE


Attr. No.

Attribute Name

Table 20:


1 (0×01)

2 (0×02)

NUMBER OF MEMBERS

IN LIST

MEMBER LIST

Get/

Set

G

G

Get/

Set

G

G

UINT

UINT

Type

UINT

2

2

Description

0 (no dynamic)

3 (0×03)

4 (0×04)

DATA

SIZE

S

G

ARRAY of STRUCT

UINT UINT Packed

EPATH

ARRAY OF BYTE

Depends on Instance.

UINT Number of bytes in Attr. 3

256

Table 21:

Common services

Common Services


01 (0x01) yes

14 (0x0E) no

Instance

yes yes

Service Name

Get_Attribute_All


5-12



Instance 101

Contains the station’s input data (static length 256 bytes).

2 Bytes status information (see

page 5-26

)

+ process data

Instance 102

Contains the station’s output data (static length 256 bytes).

2 Bytes Control data (mapped, but not defined)

+ process data

Instance 103 + Instance 104

In- and output assembly instances with variable assembly sizes. The assembly size is precalculated to support the stations I/O-configuration, RFID Command interface configuration, enabled diagnostics, etc.

input assembly instance: 103

output assembly instance: 104

The size of each assembly instance can be retrieved through the assembly object, instance 0x67, attribute: 0x04 and can vary between 2 and 496 bytes.

Mapping of process data

The process image of the BL67 gateway is depicted in WORD format (16 bit). The process data of successive modules of the same type, with process data of less than 1 word, are grouped together until

16 bits of process data is reached.

The process data is written in a new word when:

16-bit input data is reached and further input modules follow

16-bit output data is reached and further output modules follow

An input module, whose process data length cannot be completely incorporated in the preceding word, follows on from another input module

An output module, whose process data length cannot be completely incorporated in the preceding word, follows on from another output module.


5-13


Example station

– Module A: Gateway

– Module B: BL67-4DI-P

– Module C: BL67-2AI-V

– Module D: BL67-8DI-P

– Module E: BL67-4DI-P

– Module F: BL67-8DI-P

– Module G: BL67-8DO-0.5A-P

– Module H: BL67-2AO-I

– Module I: BL67-4DO-0.5A-P

– Module J: BL67-8DI-P

– Module K: BL67-8DO-0.5A-P

Table 22:

Process image of example station

3

4

1

2

Data mapping for gateways with rev. < 1.3.0.16

Input data (WORD format) (Bit 15...

→ ...0)

Produced data

(word no.)

0

5

Consumed data

(word no.)

2

3

0

1

4

Status word (A15 ... A0) of the gateway

(see also STATUS REGISTER 2 (page 5-26)

B3 ... B0

C15 ... C0

C31 ... C16

E3 ... E0; D7 ... D0

J7 ... J0; F7 ... F0

Output data (WORD format) (Bit 15...

→ ... 0)

Control word of the gateway (mapped, but not defined)

G7 ... G0

H15 ... H0

H31 ... H16

K7 ... K0; I3 ... I0

The example station transmits 6 word input data and 5 word output data accordingly.

Note

For more information about data mapping, please read also

chapter 6 ,

Examples for I/O data mapping (page 6-22)

and

Mapping report via I/O-ASSISTANT (page 6-25)

.

5-14



Data mapping for gateways with rev.

≥ 1.3.0.16

Input data

Table 23:

Data mapping for gateways with rev.

≥

1.3.0.16

Produced Data

(word no.)

0

1 to n n + y n + z

Status word of the gateway (bit assignement, see

STATUS REGISTER 2 , page 5-26

.

(Mapping can be disabled using attribute 139 "

GW Status Register

" in

”Gateway Class (VSC 100)”, Object Instance 2, page 5-27 )

Input data of modules.

Mapping similar to mapping of gateways with older firmware (see above

Data mapping for gateways with rev. < 1.3.0.16 (page 5-14) ).

Summarized diagnostic data ( page 4-21 ) of individual length.

Can be enabled/disabled using VSC102, Object instance 3, attr. 104,

page 5-30

ff.

(y= the no. of following bytes depending on the no. of slices within the station)

Scheduled diagnostic data (

page 4-22

). Can be enabled/disabled using VSC102, Object instance 3, attr. 105,

page 5-30

ff.

(z = data length for the scheduled diagnostics set according to the properties of the modules attached to the gateway)

Output data Consumed Data

(word no.)

0

1- n

Control word of the gateway (mapped, but not defined)

(Mapping can be disabled using attribute 139 "

GW Control Register " in

”Gateway Class (VSC 100)”, Object Instance 2, page 5-27 )

Output data of the modules.

Mapping similar to mapping of gateways with older firmware (see above

Data mapping for gateways with rev. < 1.3.0.16 (page 5-14) ).

Note

The data mapping can be structured individually. All parts except for the in- and output data of the station can be enabled/ disabled independently from each other.


5-15


5.2.5

Connection Manager Object

This object is used for connection and connectionless communications, including establishing connections across multiple subnets.

The following description of the Connection Manager Object is taken from the CIP specification, Vol. 1,

Rev. 2.1 by ODVA & ControlNet International Ltd. and adapted to BL67.

Common Services

Table 24:

Common services


84 (0x54) no

Instance

yes

78 (0x4E)

82 (0x52) no no yes yes

Service Name

FWD_OPEN_CMD

(Opens a connection)

FWD_CLOSE_CMD

(Closes a connection)

UNCONNECTED_SEND_CMD

(Unconnected Send Service. Only originating devices and devices that route between links need to implement).

5.2.6

Port Object

The following description of the Port Object is taken from the CIP specification, Vol. 1, Rev. 2.1 by ODVA

& ControlNet International Ltd. and adapted to BL67.


Type Value

Table 25:

Class attributes

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

8 (0×08)

9 (0×09)

Attribute Name

REVISION

MAX OBJECT

INSTANCE

NUMBER OF

INSTANCES

ENTRY PORT

ALL PORTS

G

G

G

Get/

Set

G

G

UINT

UINT

UINT

1

1

1

UINT

ARRAY of

STRUCT UINT

UINT

1

0,0 for class

4,2 for TCP_IP_PORT

5-16



Table 26:


Table 27:

Common services


Attr. No.

Attribute Name

1 (0×01)

2 (0×02)

3 (0×03)

ATTRIBUTE PORT

TYPE

ATTRIBUTE PORT

NUMBER

ATTRIBUTE PORT

OBJECT

Get/

Set

G

Type

UINT

G UINT

G UINT

EPATH

Logical path

Description

4 for TCP_IP_PORT

2

2

0x12, 0x02

0x00, 0x00

Common Services

Class Service

Code

01 (0x01)

14 (0x0E) yes yes

Instance

yes yes

Service Name

Get_Attribute_All


5.2.7

TCP/IP Interface Object

The following description of the TCP/IP Interface Object is taken from the CIP specification, Vol. 2, Rev.

1.1 and adapted to BL67.


Type Value

Table 28:

Class attributes

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

6 (0×06)

7 (0×07)

Attribute Name

REVISION

MAX OBJECT

INSTANCE

NUMBER OF

INSTANCES

MAX CLASS

IDENTIFIER

MAX INSTANCE

ATTRIBUTE

Get/

Set

G

G

G

G

G

UINT

UINT

UINT

UINT

UINT

1

1

1

7

6


5-17


Table 29:


Table 30:

Common services


Attr. No.

1 (0×01)

Attribute Name

Get/

Set

STATUS G

2 (0×02)

3 (0×03)

4 (0×04)

5 (0×05)

5 (0×05)

6 (0×06)

CONFIGURATION

CAPABILITY

CONFIGURATION

CONTROL

PHYSICAL LINK

OBJECT

Path size

Path

INTERFACE

CONFIGURATION

IP ADDRESS

NETWORK MASK

DOMAIN NAME

HOST NAME

G

G/S

G

G

GATEWAY ADDRESS G

NAME SERVER G

NAME SERVER 2

G

G

G

G


DWORD

DWORD

DWORD

Interface status

(see

page 5-19

)

Interface Capability Flag

(see

page 5-19

)

Interface Control Flag

(see

page 5-19

)

Structure of:

UINT Number of 16 bit words:

0×02

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

EPATH

Structure of:

UDINT

UDINT

UDINT

UDINT

UDINT

UDINT

STRING

TCP/IP Network Interface

Configuration (see

Current IP address

page 5-19

Current network mask

Current default gateway

)

0 = no name server address configured

0 = no secondary name server address configured

0 = no Domain Name configured

0 = no Host Name configured (see

page

5-20 )

Common Services

Class Service

Code

01 (0x01)

02 (0x02)

14 (0x0E)

16 (0×10) yes

Instance

yes no no yes yes no yes

Service Name

Get_Attribute_All

Set_Attribute_All


Set_Attribute_Single

5-18



Interface Status

The Status attribute indicates the status of the TCP/IP network interface.

Refer to the state diagram,

Figure 29: TCP/IP object state diagram (acc. to CIP Spec., Vol.2, Rev. 1.1)

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

Table 31:

Interface Status

Bit(s)

0-3

Name

Interface Configuration Status

Definition

Indicates the status of the Interface Configuration attribute:

0 = The Interface Configuration attribute has not been configured

1 = The Interface Configuration attribute contains valid configuration.

2 to 15 = Reserved

4 to 31 reserved

Configuration Capability

The Configuration Capability indicates the device’s support for optional network configuration capability.

Table 32:

Configuration

Capability

Bit(s)

0

1

2

Name

BOOTP Client

DNS Client

DHCP Client

Definition

The device is capable of obtaining its network configuration via BOOTP.

The device is capable of resolving host names by querying a DNS server.

The device is capable of obtaining its network configuration via DHCP.

Configuration Control

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

Value

1

0

1

Table 33:

Configuration

Control

Bit(s)

0-3

Name

Startup Configuration

Definition

Determines how the device shall obtain its initial configuration at start-up.

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

Always 0

Set to 0.

4

5-31

DNS Enable

Reserved

Interface Configuration

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

To modify the Interface Configuration attribute, get the Interface Configuration attribute first, change the desired parameters, then set the attribute.

The TCP/IP Interface Object applies the new configuration upon completion of the Set service. If the value of the Startup Configuration bits (Configuration Control attribute) is 0, the new configuration is stored in non-volatile memory.


5-19


The device does not reply to the set service until the values are safely stored to non-volatile memory.

An attempt to set any of the components of the Interface Configuration attribute to invalid values results in an error (status code 0x09) returned from the Set service.

If initial configuration is obtained via BOOTP or DHCP, the Interface Configuration attribute components are all zeros until the BOOTP or DHCP reply is received.

Upon receipt of the BOOTP or DHCP reply, the Interface Configuration attribute shows the configuration obtained via BOOTP/DHCP.

Host Name

The Host Name attribute contains the device’s host name.

The host name attribute is used when the device supports the DHCP-DNS Update capability and has been configured to use DHCP upon start up.

The mechanism allows the DHCP client to transmit its host name to the DHCP server. The DHCP server then updates the DNS records on behalf of the client. The host name attribute does not need to be set for the device to operate normally. The value of the Host Name attribute, if it is configured, is used for the value of the FQDN option in the DHCP request. If the Host Name attribute has not been configured, then the device shall not include the FQDN option in the DHCP request.

Figure 29:

TCP/IP object state diagram

(acc. to CIP

Spec., Vol.2, Rev.

1.1)

Non-existent

Status =

0×00000000

Powerup

/

Reset

Obtaining initial configuration

BOOTP/DHCP disabled and stored config. valid

BOOTP OR

DHCP enabled

Waiting for configuration

Set_Attributes request received

Status =

0×00000000

BOOTP/DHCP response received

Applying configuration

Configuration applied

BOOTP/DHCP disabled and stored config.

valid

Change interface configuration

TCP/IP network interface configured

Status = 0×00000001

5-20



5.2.8

Ethernet Link Object

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.


Type Value

Table 34:

Class attributes

Attr. No.

1 (0×01)

2 (0×02)

3 (0×03)

6 (0×06)

7 (0×07)

Attribute Name

REVISION

MAX OBJECT

INSTANCE

NUMBER OF

INSTANCES

MAX CLASS

IDENTIFIER

MAX INSTANCE

ATTRIBUTE


Attr. No.

Attribute Name

Table 35:


1 (0×01) INTERFACE SPEED

Get/

Set

G

G

G

G

G

Get/

Set

G

UINT

UINT

UINT

UINT

UINT

Type

1

1

1

7

6

Description

2 (0×02)

3 (0×03)

INTERFACE FLAGS G

PHYSICAL ADDRESS G

UDINT

DWORD

ARRAY OF

USINTs

Speed in megabits per second

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

see Table 36: Interface flags

Contains the interface’s MAC address

(TURCK: 00:07:46:××:××:××)


5-21


Table 36:

Interface flags

Bits

0

1

2 to 4

5

6

Name

Link Status

Half / Full Duplex

Negotiation Status

Definition

Indicates whether or not the Ethernet

802.3 communications interface is connected to an active network.

0 = inactive link

1 = active link.

Default-Value

Depends on application

0 = half duplex;

1 = full duplex

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


Indicates the status of link auto-negotiations.

0 = Auto-negotiation in progress

1 = Auto-negotiation and speed detection failed.

Using default values for speed and duplex (10Mbps/half duplex).

2 = Auto negotiation failed but detected speed (default: half duplex).

3 = Successfully negotiated speed and duplex.

4 = Auto-negotiation not attempted.

Forced speed and duplex.


Manual Setting

Requires Reset

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

1

Local Hardware Fault 0 = interface detects no local hardware fault

1 = a local hardware fault is detected

0

Common services

Table 37:

Common services

Service

Code

01 (0x01)

14 (0x0E)

Class

yes yes

Instance

yes yes

76 (0×4C) no yes

Service Name

Get_Attribute_All


Enetlink_Get_and_Clear

5-22


VSC-Vendor Specific Classes

5.3


In addition to supporting the above named CIP Standard Classes, the BL67 gateway for EtherNet/IP supports the below vendor specific classes.

The VSC describing the possible DeviceNet-master function (VSC 122 and VSC 123) of an EtherNet/IP gateway can be found in a separate manual (D301118).

It is possible to gain read (G= Get) and/or write (S= Set) access to the attributes of classes described in the following:

Table 38:

VSC-Vendor

Specific Classes

Class Code

100 (0×64)

101 (0×65)

102 (0×66)

103 (0×67)

104 (0×68)

105 (0×69)

106 (0×6A)

107 (0×6B)

108 (0×6C)

109 (0×6D)

110 (0×6E)

111 (0×6F)

112 (0×70)

113 (0×71)

114 (0×72)

115 (0×73)

116 (0×74)

117 (0×75)

Name

Gateway Class, page 5-26

Description

Contains data concerning the gateway.

Terminal Slot Class,

page 5-28

Process Data Class, page 5-30

Power Supply Module Class, page

5-32

Digital Input Module Class,

page 5-34

Contains data concerning the base modules

Contains process data

Describes the power distribution modules

Describes the modules of the type BL67-*DI-*

Digital Output Module Class, page

5-36

Describes the modules of the type BL67-*DO-*

Analog Input Voltage Module Class,

page 5-38

Describes the modules of the type

BL67-*AI-V

Analog Output Voltage Module

Class, page 5-40


BL67-*AO-V

Analog Input Current Module Class,

page 5-42

Describes the modules of the type BL67-*AI-I

Describes the modules of the type BL67-*AO-I Analog Output Current Module

Class, page 5-44

Analog Input RTD Module Class,

page 5-46

Analog Input THERMO Module

Class, page 5-50


BL67-*AI- PT


BL67-*AI-TC reserved reserved

-

-

RS232 Module Class, page 5-53

modules of the type

BL67-1RS232

RS4xx Module Class,

page 5-60

SSI Module Class, page 5-67


BL67-1RS422/485


BL67-1SSI

Digital Versatile Module Class,

page

5-75


BL67-4DI4DO, BL67-8XSG etc.


5-23


Table 38:

VSC-Vendor

Specific Classes

Class Code

100 (0×64)

118 (0×76)

119 (0×77)

122 (0×7A)

123 (0×7B)

124 (0×7C)

Name

Gateway Class, page 5-26

Analog Versatile Module Class,

page 5-79

CVI Module Class,

page 5-82

DeviceNet™ Master Class

DeviceNet™ Slave Class

RFID -S Module Class,

page 5-85

Description

Contains data concerning the gateway.


BL67-xAI/AO-x

Describes the modules of the type BL67-1CVI

Description in a separate manual ( D301118

“DeviceNet™-Master User Manual“ ).


BL67-2RFID-S

5-24



5.3.1

Class instances of the VSC

Note

Class instance attributes are the same for each Vendor Specific Class.

Class-specific Object instances and the corresponding attributes are explained below for the different VSC.

The general VSC - Class instance attributes are defined as follows:


Table 39:

Class instance

Attr. No.

100 (0×64)

Attribute Name

Get/

Set

CLASS

REVISION

G

101 (0×65) MAX INSTANCE G

102 (0×66)

103 (0×67)

# OF INSTANCES

MAX CLASS

ATTRIBUTE

G

G

UINT

USINT

USINT

USINT

States the revision number of the class:

Maj. Rel. *1000 + Min. Rel..

Contains the number of the highest instance of an object created on this level in the class hierarchy.

Contains the number of Object instances created in this class.

Contains the number of the last Class

Attribute to be implemented.


5-25


5.3.2

Gateway Class (VSC 100)

The Gateway Class contains all the parameters of the BL67 system and the gateway.

Note

Please refer to paragraph Class instances of the VSC, page 5-25 , for the description of the class

instances for VSC.

Table 40:

Object instance

2, Gateway

Instance

Object instances

Attr. No.

109

(0×6D)

Attribute Name

Get/

Set

STATUS

REGISTER 2

G


STRUCT Gateway-Status contains general gateway status information:

Gateway

– Bit 15: "I/O Controller Error"

The communication controller for the I/Osystem is faulty.

– Bit 14: "Force Mode Active Error" The

Force Mode is activated.

– Bit 13: reserved

– Bit 12: reserved

Module bus

– Bit 11: "I/O Cfg Modified Error" The I/Oconfiguration has been changed and is now incompatible.

– Bit 10: "I/O Communication Lost Error" No communication on the I/O module bus.

Voltage errors

Bit 09: "U sys

too low" System supply voltage too low (< 18 VDC).

Bit 08: "U sys too high" System supply voltage too high (> 30 VDC).

Bit 07: "U

L

too low" Load voltage too low

(< 18 VDC).

Bit 06: "U

L

too high" Load voltage too high

(> 30 VDC)

Bit 05: "I sys

too high" Overload of the system voltage supply.

Bit 04: reserved

Warnings

Bit 03: "I/O Cfg Modified Warning"

Bit 02: reserved

Bit 01: reserved

Bit 00: "I/O Diags Active Warning" At least one I/O-module sends active diagnosics.

5-26



Table 40:

Object instance

2, Gateway

Instance

Attr. No.

115

(0×73)

Attribute Name

Get/

Set

ON IO

CONNECTION

TIMEOUT

G/S

116

(0×74)

MODULE DIAG

SUMMARY

G


ENUM

USINT

ARRAY OF

STRUCT

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

The gateway makes no further changes to the data of the I/O modules. The outputs are held.

Contains diagnostic information for all modules.

ARRAY OF STRUCT:

USINT SLOT #:

Indicates the slot number (module position) with diagnostic messages.

BYTE SLOT FLAGS:

Offers slot-related information.

Bit 7 = module missing

Bit 6 = false module plugged

DWORD DIAG:

Contains the module diagnostic information. Module diagnostic bits that are not used are indicated by a "0".

117-137

(0×75 -

(0×89)

138

(0×8A)

139

(0×8B) reserviert

GW Status

Register

GW Control

Register

Get/Set

Get/Set

UINT

UINT

Allows to enable/disable the GW status register which is part of the input data.

Allows to enable/disable the GW cotnrol register which is part of the output data.


5-27


5.3.3

Terminal Slot Class (VSC 101)

This class contains parameters and data for the base modules.

Note


instance for the VSC.

Table 41:

Object instances

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set

Max object attribute

Module present

G

G

Type

USINT

BOOL

102

(66h)

Slot state G ENUM

USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

Module ID

Module diag bit count

G

G

Module param bit count

G

Module diag bit count

G

Description

DWORD

UINT

UINT

UINT

Contains the number of the last object attribute to be implemented.

0 = module missing, base module without electronic module.

1 = module is plugged

NOT USED (0):

A non-occupied slot is not taking part in process data traffic. It is not responding to data transmitted or received via I/O

Connection Messages.

PROCESSING (1):

A BL67 module, recognized by the fieldbus is occupying a slot. Data transfer is taking place with the other fieldbus devices via I/

O Connection Messages.

ALLOCATED (2):

The slot is not occupied, but has been reserved for a certain electronic module.

The process data are set to 0.

WRONG MODULE (3):

The wrong module has been plugged in the slot, meaning, it supports process data lengths that were not previously defined or it is a different type of module. This false module will not be made known to the fieldbus and will not take part in process data traffic. The process data for this slot are set to 0.

Contains the ID of the BL67 module.

States the number of diagnostic bits of the module.

States the number of parameter bits of the module.

States the number of input bits (produced bits) of the module.

5-28



Table 41:

Object instances

Attr. No.

dec.

(hex.)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

111

(6Fh)

112

(70h)

113

(71h)

114

(72h)

Attribute name

Get/

Set

Module output bit count

G

Module submode G

Module group count

Diag

Param input output

Referenced

VSC

G

G

G/S

G

G/S

G

115

(73h)

116

(74h)

Referenced VSC instance

Module registered

Index

G

G/S


UINT

USINT

USINT

ARRAY OF

BYTE

ARRAY OF

BYTE

ARRAY OF

BYTE

ARRAY OF

BYTE

USINT

USINT

ENUM

USINT

States the number of output bits

(consumed bits) of the module.

Contains the submode ID of the BL67 module.

States the number of internal groups of the module.

Contains the diagnostic information of the module.

Contains the parameters of the module.

Contains the input data (produced data) of the module.

Contains the output data (consumed data) of the module.

The VSC that represents this BL67 module.

If this module is contained in the internal gateway library, then it is listed in a specific

VSC that describes the typical attributes of the module.

The VSC Instance that represents this BL67 module. If this module is contained in the internal gateway library, then it is listed in a specific VSC that describes the typical attributes of the module.

Contains the index numbers specified in all the module lists.


5-29


5.3.4

Process Data Class (VSC102)

This class contains the process-relevant information.

Note



Table 42:

Object instance

1, standard input process data

(compressed)

Object instance 1, standard input process data (compressed)

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

102

(66h)

103

(67h)

Attribute name


Attribute list

Standard packed process input data

Process data byte count

Get/

Set

G

G

G

G

Type

USINT

ARRAY OF

USINT

ARRAY OF

WORD

USINT

Description


List of all attributes that are supported by this Instance.

Input process data, 16-bit aligned, compressed.

The number of bytes that are exchanged with this Instance.

Note

The following object instances (Object instance 2 to Object instance 8) are only valid for gateways with Rev.

≥ 1.3.0.16.

Table 43:

Object instance

2, standard output process data

(compressed)

Object instance 2, standard output process data (compressed)

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

102

(66h)

103

(67h)

Attribute name


Attribute list

Standard packed process output data

Get/

Set

G

G

G/S

Process data byte count

G

Type

USINT

ARRAY OF

USINT

ARRAY OF

WORD

USINT

Description


List of all attributes that are supported by this Instance.

Output process data, 16-bit aligned, compressed.

The number of bytes that are exchanged with this Instance.

5-30



Object instance 3, diagnostic instance

Attribute name Get/ Set Type

Table 44:

Object instance

3, diagnostic instance

Attr. No.

dec.

(hex.)

104

(68h)

GW summarized diagnostics

G/S BOOL

105

(69h)

GW scheduled diagnostics

G/S BOOL

Description

0 = disabled

1 = enabled: 1 bit of diagnosis per slot mapped at the end of the input data image

( page 4-21 ).

The actual data is loaded to the nonvolatile memory of the gateway. Changes become valid after a start-up!

0 = disabled

1 = enabled: time sliced module related data block using a round robin mechanism

( page 4-22 ).

The actual data is loaded to the nonvolatile memory of the gateway. Changes become valid after a start-up!

106

(6Ah)

107

(6Bh)

108

(6Ch) reserved

I-MAP summarized diags

I-MAP scheduled diags

G

G

USINT

USINT

Contains the number of summarized diagnostic bytes.

Changes become valid after a start-up!

Contains the number of scheduled diagnostics bytes.

Changes become valid after a start-up!

Table 45:

Object instance

4, COS/CYCLIC instance

Object instance 4, COS/CYCLIC instance

Attr. No.

dec.

(hex.)

104

(68h)

Attribute name G

et/

S

et

COS data mapping

G/S

Type

ENUM

USINT

Description

Currently not supported


5-31


5.3.5

Power Supply Module Class (VSC103)

This class contains all the relevant information and parameters for the power distribution modules.

Note



Table 46:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

Terminal slot number

Module ID

Module order number

Module order name

Module revision

Module type ID

G

G

G

G

G

G

Description

USINT

SHORT

STRING

USINT

ENUM

USINT




The slot number of the base module belonging to the module (base module to the right of the gateway = No. 1).

Corresponds to the respective Instance

Number within the TERMINAL SLOT

CLASS.

Contains the module ID.

DWORD

UDINT Contains the ident number of the module.

Contains the name of the module, for example, "BL67-PF-24VDC"

Contains the revision number of the module firmware.

Describes the module type:

– 0×00: type of module unknown (default)

– 0×01: digital module

– 0×11: analog voltage mod.

– 0×12: analog current mod.

– 0×13: analog RTD mod.

– 0×14: analog THERMO mod.

– 0×1F: analog volt./curr. mod.

– 0×22: counter/incr. encoder 32bit

– 0×28: SSI interface

– 0×31: starter, mechanical

– 0×32: starter, electronical

– 0×41: RS232 mod.

– 0×42: RS485/RS422 mod.

– 0×46: RFID module

– 0×51: CVI mod.

5-32



Table 46:

Object instance

Attr. No.

dec.

(hex.)

108

(6Ch)

Attribute name

Get/

Set

Module command interface

G/S

Type

ARRAY

Module response interface

G ARRAY 109

(6Dh

110

(6Eh)

111

(6Fh)

Diag size

Diag

G

G

UINT

WORD

112

(70h)

Module registered index

G ENUM

USINT

Description

The control interface of the BL67 module.

ARRAY OF:

BYTE: Control byte sequence

Response interface of the BL67 module.

ARRAY OF:

BYTE: Response byte sequence

Indicates the number of diagnostic bits of the module.


WORD:

Bit for bit assignment according to module specification.



5-33


5.3.6

Digital Input Module Class (VSC104)

This Class contains all information and parameters for digital input modules.

Note



Table 47:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

Module ID

Module order number

Module order name

G

G

G

106 (6Ah) Module revision

107 (6Bh) Module type ID

G

G

108 (6Ch)

109 (6Dh

110 (6Eh)



Produced data size

G/S

G

G

Description

Contains the number of the last object attribute to be implemented






CLASS.


Contains the ident number of the module.

DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

UINT

Contains the name of the module, for example,

"BL67-4DI-P".



– see attribute 107 (6Bh) on page 5-32


ARRAY OF:



ARRAY OF:


Contains information concerning the range of data produced by the module.

5-34



Table 47:

Object instance

Attr. No.

dec.

(hex.)

111 (6Fh)

Attribute name

Get/

Set

Produced data G

Type

DWORD

112

(70h)

113

(71h)

114

(72h)

115

(73h)

116

(74h)

Diag size

Diag

Param size

Params

Module registered

Index

G

G

G

G/S

G

UINT

DWORD

UINT

DWORD

ENUM

USINT

Description

Contains the input data of the module.

DWORD: Bit for bit assignment according to module specification.

Contains information concerning the range of the diagnostic data of the module.



Contains information concerning the range of parameters of the module.





5-35


5.3.7

Digital Output Module Class (VSC105)

This Class contains all information and parameters for digital output modules.

Note

Please refer to paragraph

section "Class instances of the VSC“ , page 5-25 , for the description

of the class instance for the VSC.

Table 48:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name

Module revision

Module type ID



Consumed data size

G

G

G

G

G

G/S

G

G

Description







CLASS.



DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

UINT

Contains the name of the module, for example, "BL67-4DO-0.5A-P".





ARRAY OF:



ARRAY OF:


Contains information concerning the range of data consumed by the module.

5-36



Table 48:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

Attribute name

Get/

Set

Consumed data G

112

(70h)

113

(71h)

114

(72h)

115

(73h)

116

(74h)

Diag size

Diag

Param size

Params

Module registered

Index

G

G

G

G/S

G

Type

DWORD

UINT

DWORD

UINT

DWORD

ENUM

USINT

Description

Contains the output data of the module.

DWORD:


Contains information concerning the range of the diagnostic data of the module.


DWORD:


Contains information concerning the range of parameters of the module.


DWORD:




5-37


5.3.8

Analog Input Voltage Module Class (VSC106)

This Class contains all information and parameters for analog input modules (voltage).

Note




Table 49:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name

Module revision

Module type ID




G

G

G

G

G

G/S

G

G

Description







CLASS.



DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

ENUM

USINT


"BL67-2AI-V".





ARRAY OF:



ARRAY OF:



5-38



Table 49:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

112 - 119

(70h - 77h)

Attribute name

Number of supported channels

Produced data

Get/

Set

G

G

Type

USINT

INT

120 - 127

(78h - 7Fh)

128 - 135

(80h - 87h)

Diag data

Mode parameter data

G

G/S

BYTE

BYTE

Description

States the number of analog input channels supported by this module

Instance.

Contains the data transmitted by the analog input module of channels No. 1 to

No. 8.

Only those channels are supported that are contained in attribute 111, „Number of supported channels“.

Attribute 112 contains the data for channel

1, attribute 119 for channel 8.

Contains the diagnostic data of the channels 1 to 8 of the analog input module.

Only those channels are supported that are defined in attribute 111, Number of supported channels.



BYTE diag:

Bit0:

0 = ok

1 = measurement value range error

Bit1 to 7: reserved

Contains the diagnostic data of the channels 1 to 8 of the analog input module. Only those channels are supported that are defined in attribute

111, „Number of supported channels“.

Attribute 128 contains the data for channel 1, attribute 135 for channel 8.

BYTE mode:

Bit0: Voltage mode:

0 =0....10 V

1 =-10 V10 V....+10 V

Bit 1: Value representation

0 =Integer (15 Bit + sign)

1 =12 Bit (left-justified)

Bit 2: Diagnostic:

0 = enable

1 = disable

Bit 3 to 7: reserved


5-39


5.3.9

Analog Output Voltage Module Class (VSC107)

This Class contains all information and parameters for analog output modules (voltage).

Note




Table 50:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name

Module revision

Module type ID



Module registered

Index

G

G

G

G

G

G/S

G

G

Description







CLASS.



DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

ENUM

USINT


"BL67-2AO-V".





ARRAY OF:



ARRAY OF:



5-40



Table 50:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

112 - 119

(70h - 77h)

Attribute name


Consumed data

Get/

Set

G

G

Type

USINT

INT

120 - 127

(78h - 7Fh)

128 - 135

(80h - 87h)

136 - 143

(88h - 8Fh)

Diag data

Mode parameter data

Fault value parameter data

G

G/S

G/S

BYTE

BYTE

INT

Description


Instance.

Contains the data received by the analog output module of channels No. 1 to No. 8.

Only those channels are supported that are contained in attribute 111,„Number of supported channels“.



Contains the diagnostic data of the channels 1 to 8 of the analog output module.

Only those channels are supported that are defined in attribute 111, „Number of supported channels“.



BYTE diag:


Contains the diagnostic data of the channels 1 to 8 of the analog output module. Only those channels are supported that are defined in attribute



BYTE mode:

Bit0: Voltage mode:

0 = 0....10 V

1 = -10 V....+10 V

Bit1: Value representation

0 = Integer (15 Bit + sign)

1 = 12 Bit (left-justified)

Bit2 to 7: reserved

Contains the Fault Value-Definition of the channels 1 to 8 of the analog output modules.





5-41


5.3.10

Analog Input Current Module Class (VSC108)

This Class contains all information and parameters for analog input modules (current).

Note




Object instance

The Object instances/ attributes of the analog input modules (current) correspond to those of the analog input modules (voltage). Differences are only to be found in the attributes no. 112 to 135 that concern the measurement ranges of the modules (current or voltage measurements).


Table 51:

Object instance

Attr. No.

dec.

(hex.)

112 - 119

(70h - 77h)

Attribute name

Get/

Set

Produced data G INT

120 - 127

(78h - 7Fh)

Diag data G BYTE

Contains the data transmitted by the analog input module of channels No. 1 to

No. 8.








BYTE diag:

Bit 0:

0 = ok


Bit 1:

0 =ok

1 =open circuit; only in measurement range: 4 to 20mA


5-42



Table 51:

Object instance

Attr. No.

dec.

(hex.)

128 - 135

(80h - 87h)

Attribute name

Get/

Set

Mode parameter data

G/S

Type

BYTE

Description

Contains the diagnostic data of the channels 1 to 8 of the analog input module. Only those channels are supported that are defined in attribute



BYTE mode:

Bit 0: Current mode:

0 = 0 to 20mA

1 = 4 to 20mA

Bit 1: Value representation:



Bit 2: Diagnostic:

0 = enable

1 = disable

Bit 3 to 7:reserved


5-43


5.3.11

Analog Output Current Module Class (VSC109)

This Class contains all information and parameters for analog output modules (current).

Note




Object instance

The Object instances/attributes of the analog output modules (current) correspond to those of the analog output modules (voltage). Differences are only to be found in the attributes no. 112 to 143 that concern the measurement ranges of the modules (current or voltage measurements).


Table 52:

Object instance

Attr. No.

dec.

(hex.)

112 - 119

(70h - 77h)

Attribute name

Get/

Set

Consumed data G INT

120 - 127

(78h - 7Fh)

128 - 135

(80h - 87h)

Diag data

Mode parameter data

G

G/S

BYTE

BYTE

Contains the data received by the analog output module of channels No. 1 to No. 8.




Contains the diagnostic data of the channels 1 to 8 of the analog output module.




BYTE diag:


Contains the diagnostic data of the channels 1 to 8 of the analog output module. Only those channels are supported that are defined in attribute



BYTE mode:

Bit 0: Current mode:

0 = 0 to 20mA

1 = 4 to 20mA

Bit 1: Value representation:



Bit 2 to 7:reserved

5-44



Table 52:

Object instance

Attr. No.

dec.

(hex.)

136 - 143

(88h - 8Fh)

Attribute name

Get/

Set

Fault value parameter data

G/S

Type

INT

Description

Contains the Fault Value-Definition of the channels 1 to 8 of the analog output modules.





5-45


5.3.12

Analog Input RTD Module Class (VSC110)

This Class contains all information and parameters for analog input modules for PT100/NI sensors

(current).

Note




Table 53:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name

Module revision

Module type ID



Module registered

Index

G

G

G

G

G

G/S

G

G

Description







CLASS.



DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

ENUM

USINT

Contains the name of the module, for example, "BL67-2AI-PT".





ARRAY OF:



ARRAY OF:



5-46



Table 53:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

112 - 119

(70h - 77h)

Attribute name


Produced data

Get/

Set

G

G

Type

USINT

INT

120 - 127

(78h - 7Fh)

Diag data G BYTE

Description


Instance.

Contains the data received by the analog input module of channels No. 1 to No. 8.

Only those channels are supported that are contained in attribute 111, Number of supported channels.







BYTE diag:

Bit 0:

0 = ok


Bit 1:

0 = ok

1 = open circuit

Bit 2:

0 = ok

1 = short-circuit


5-47


Table 53:

Object instance

Attr. No.

dec.

(hex.)

128 -135

(80h -87h)

Attribute name

Get/

Set

Mode parameter data

G/S

Type

BYTE

Description





BYTE mode:

Bit 0: Mains suppression

0 = 50Hz mains suppression


Bit 1: value representation:

0 = Integer (15 Bit + sign)

1 = 12 Bit (left-justified)

Bit 2: Diagnose:

0 = release

1 = block

Bit 3:Channel:

0 = activate channel

1 = deactivate channel

Bit 4: Measurement mode:

0 = 2-wire

1 = 3-wire


5-48



Table 53:

Object instance

Attr. No.

dec.

(hex.)

136 -143

(88h - 8Fh)

Attribute name

Get/

Set

Sensor parameter data

G/S

Type

ENUM

USINT

Description

Contains the sensor-specific parameter data of the channels 1 to 8 of the analog input module.




ENUM USINT:

Element:

0: PT100, -200...850°C

1:PT100, -200...150°C

2: NI100, -60...250°C

3:NI100, -60...150°C

4:PT200, -200...850°C

5: PT200, -200...150°C

6: PT500, -200...850°C

7: PT500, -200...150°C

8: PT1000, -200...850°C

9: PT1000, -200...150°C

10: NI1000, -60...250°C

11: NI1000, -60...150°C

12: resistance: 0...100

Ω


Ω


Ω


Ω

16 to 255: reserved


5-49


5.3.13

Analog Input THERMO Module Class (VSC111)

This Class contains all information and parameters for analog input modules for thermocouples.

Note




Table 54:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name

Module revision

Module type ID



Module registered

Index

G

G

G

G

G

G/S

G

G

Description







CLASS.



DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

ENUM

USINT


"BL67-2AI-TC".





ARRAY OF:



ARRAY OF:



5-50



Table 54:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

112 - 119

(70h - 77h)

Attribute name


Produced data

Get/

Set

G

G

Type

USINT

INT

120 - 127

(78h - 7Fh)

128 - 135

(80h - 87h)

Diag data

Mode parameter data

G

G/S

BYTE

BYTE

Description


Instance.

Contains the data received by the analog input module of channels No. 1 to No. 8.








BYTE diag:

Bit 0:

0 = ok


Bit 1:

0 =ok

1 =open circuit

Bit 2 to 7:reserved





BYTE mode:

Bit 0: Mains suppression



Bit 1: value representation:



Bit 2: Diagnose:

0 = release

1 = block

Bit 3:Channel:

0 = activate channel




5-51


Table 54:

Object instance

Attr. No.

dec.

(hex.)

136 - 143

(88h - 8Fh)

Attribute name

Get/

Set

Sensor parameter data

G/S

Type

ENUM

USINT

Description

Contains the sensor-specific parameter data of the channels 1 to 8 of the analog input module.




ENUM USINT:

Element:

0: Type K -270....1370 °C

1: Type B 100....1820 °C

2: Type E -270....1000 °C

3: Type J -210....1200 °C

4: Type N -270....1300 °C

5: Type R -50....1760 °C

6: Type S -50....1540 °C

7: Type T -270....400 °C

8: ±50mV

9: ±100mV

10: ±500mV

11: ±1000mV

12 to 255: reserved

5-52



5.3.14

RS232 Module Class (VSC114)

This Class contains all information and parameters for RS232 modules.

Note




Table 55:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name

Module revision number

Module type ID



Module registered

Index

G

G

G

G

G

G/S

G

G

Description







CLASS.



DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

ENUM

USINT


"BL67-1RS232".





ARRAY OF:



ARRAY OF:

BYTE: Response-byte sequence



5-53


Table 55:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

Attribute name

Get/

Set


RX byte count

G

G 112

(70h)

113

(71h)

RX count G

Type

USINT

USINT

USINT

114

(72h)

115 (73h)

TX count acknowledge

Status

G

G

Description

USINT

BOOL


Instance.

Number of the valid bytes (0 to 7) in this data segment.

This value is transferred together with every data segment of the process input data.

The RX count values are sequential:

00->01->10->11->00....

(decimal: 0->1->2->3->0....)

Errors in this sequence show the loss of data segments.

This value is a copy of the value TX count.

TX count has been transmitted together with the last data segment of the process output data.

TX count acknowledge is an acknowledge for the successful transmission of the data segment with TRANSMIT count.

0 = The communication with the data terminal equipment (DTE) is disturbed. A diagnostic message is generated if the parameter "Diagnostics“ is set to "0/ release“. The diagnostic data show the cause of the communication disturbance.

The user has to set back this bit in the process output data by using STATRES.

1 = The communication with the data terminal equipment (DTE) is error free,

5-54



Table 55:

Object instance

Attr. No.

dec.

(hex.)

116

(74h)

Attribute name

Get/

Set

Process diagnostics data

G

117

(75h)

118

(76h)

119

(77h)

RX data

RX data and release

TX byte count

G

G

G/S


BYTE

ARRAY OF

BYTE

ARRAY OF

BYTE

USINT

Contains the diagnostic information:

The diagnostic data are part of the process input data, if ACTIVE MODE = 1 or 2bytes

"ctrl/status header" is set.

Diagnostics messages:

– Bit 0 to Bit 2: reserved

– Bit 3:

0 = ok

1 = parameter error:

The set parameter values are not supported.

– Bit 4:

0 = ok

1 = hardware failure:

The module has to be replaced, e.g.

EEPROM or UART may be defect.

– Bit 5:

0 = ok

1 = handshake error:

The DTE connected to the module does not answer a XOFF or RTS handshake. This may cause a overflow in the internal receive-buffer.

– Bit 6:

0 = ok

1 = frame error:

The module has to be parameterized to be adapted to the data structure of the connected DTE. A frame error occurs if the parameterization (number of data bits, stop bits, parity) is not correct.

– Bit 7:

0 = ok

1 = buffer overflow:

Overflow in the RX-buffer.


Defines the receive-data (0...7).

Defines the data received via RS232 (0...7)

+ acknowledge for reception

Number of the valid user data bytes in this data segment. I


5-55


Table 55:

Object instance

Attr. No.

dec.

(hex.)

120

(78h)

Attribute name

Get/

Set

TX count G/S

121

(79h)

122

(7Ah)

123

(7Bh)

124

(7Ch)

125

(7Dh)

RX count acknowledge

Status reset control

Process control data

TX data

TX data and release

G/S

G/S

G/S

G/S

S


USINT

USINT

This value is transferred together with every data segment.

The TX count values are sequential:

00->01->10->11->00....

(decimal: 0->1->2->3->0....)


This value is a copy of RX count.

RX count has been transmitted together with the last data segment of the process input data.

RX count acknowledge is an acknowledge for the successful transmission of the data segment with RX count.

BOOL STATRES:

This bit is set to reset the STAT bit in the process input data.

With the change from 1 to 0 the status bit is reset

(from 0 to 1).

If this bit is 0, all changes in TRANSMIT

BYTE count, TRANSMIT count and RECEIVE count acknowledge are ignored.

Flushing the transmit-/ receive-buffer with process control data (Attr. 123)

is possible.

If this bit is 1 or with the change from 0 to

1, the flushing of the transmit-/ receivebuffer with process control data (Attr. 123)

is not possible.

BYTE Bit 0 = transmit-buffer flush,

Bit 1 = receive-buffer flush

Defines the transmit-data (0...7) ARRAY OF

BYTE

ARRAY OF

BYTE

Defines the data to be transmitted via

RS232 (0...7) + transmission is released/ charged immediately

126

(7Eh) reserved

5-56



Table 55:

Object instance

Attr. No.

dec.

(hex.)

127

(7Fh)

Attribute name

Get/

Set

Diagnostics G

Type

WORD

128

(80h)

Active mode G/S BOOL

Description

Contains the diagnostic messages (low byte):



– Bit 3:

0 = ok



– Bit 4:

0 = ok




– Bit 5:

0 = ok



– Bit 6:

0 = ok

1 = frame error:

The module has to be para-meterized to be adapted to the data structure of the connected DTE. A frame error occurs if the parameterization (number of data bits, stop bits, parity) is not correct.

– Bit 7:

0 = ok



– High byte: reserved

0 = 1byte ctrl/status header: The diagnostic data are not part of the process input data, 7 bytes of user data are available.

1 = 2byte ctrl/status header: The diagnostic data are part of the process input data, 6 bytes of user data are available.


5-57


Table 55:

Object instance

Attr. No.

dec.

(hex.)

129

(81h)

Attribute name

Get/

Set

Bit rate G/S

Type

ENUM

USINT

130

(82h)

131

(83h)

132

(84h)

133

(85h)

134

(86h)

Disable diagnostics

Flow control

Data width

Parity

Stop bits

G/S

G/S

G/S

G/S

G/S

BOOL

ENUM

USINT

ENUM

USINT

ENUM

USINT

ENUM

USINT

Description

Used to set the baudrate for the gateway:

0 = reserved,

1 = 300 bps

2 = 600 bps

3 = 1200 bps

4 = 2400 bps

5 = 4800 bps

6 = 9600 bps

7 = 14400 bps

8 = 19200 bps

9 = 28800 bps

10 = 38400 bps

11 = 57600 bps

12 = 115200 bps

...

15 = reserved)

0 = released:

The diagnostic function is activated.

1 = blocked:

The diagnostic function is deactivated.

0 = off: data flow control is deactivated

1 = XON/XOFF

Software-handshake is activated

2 = RTS/CTS

Hardware-handshake is activated

3 = reserved

0 = 7 bits

1 = 8 bits

0 = none

1 = odd

The number of the bits set to 1 is odd (incl. data and parity bit).

2 = even

The number of the bits set to 1 is even (incl. data and parity bit).

Number of the stop bits.

0 = 1 bit

1 = 2 bits

5-58



Table 55:

Object instance

Attr. No.

dec.

(hex.)

135

(87h)

Attribute name

Get/

Set

XON character

G/S

Type

USINT

136

(88h)

XOFF character

G/S USINT

Description

XON character

This sign is used to start the data transfer to the data terminal equipment (DTE) with the activation of the software handshake.

0 - 255 default: 17/ 11h

XOFF character

This sign is used to stop the data transfer to the data terminal equipment (DTE) with the activation of the software handshake.

(0 - 255) default: 19/ 13h


5-59


5.3.15

RS4xx Module Class (VSC115)

This Class contains all information and parameters for RS485/422 modules.

Note




Table 56:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)


G USINT

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name


Module type ID



Module registered

Index

G

G

G

G

G

G/S

G

G

Description







CLASS.



DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

ENUM

USINT


"BL67-1RS485/422".





ARRAY OF:



ARRAY OF:



5-60



Table 56:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

Attribute name

Get/

Set


RX byte count

G

G 112

(70h)

113

(71h)

RX count G

Type

USINT

USINT

USINT

114

(72h)

115 (73h)

TX count acknowledge

Status

G

G

Description

USINT

BOOL


Instance.

Number of the valid bytes (0 to 7) in this data segment.

This value is transferred together with every data segment of the process input data.

The RX count values are sequential:

00->01->10->11->00....

(decimal: 0->1->2->3->0....)


This value is a copy of the value TX count.

TX count has been transmitted together with the last data segment of the process output data.

TX count acknowledge is an acknowledge for the successful transmission of the data segment with TRANSMIT count.

0 = The communication with the data terminal equipment (DTE) is disturbed. A diagnostic message is generated if the parameter "Diagnostics“ is set to "0/ release“. The diagnostic data show the cause of the communication disturbance.

The user has to set back this bit in the process output data by using STATRES.

1 = The communication with the data terminal equipment (DTE) is error free.


5-61


Table 56:

Object instance

Attr. No.

dec.

(hex.)

116

(74h)

Attribute name

Get/

Set

Process diagnostics data

G

117

(75h)

118

(76h)

119

(77h)

RX data

RX data and release

TX byte count

G

G

G/S


BYTE

ARRAY OF

BYTE

ARRAY OF

BYTE

USINT

Contains the diagnostic information:

The diagnostic data are part of the process input data, if ACTIVE MODE = 1 or 2bytes ctrl/status header is set.



– Bit 3:

0 = ok



– Bit 4:

0 = ok




– Bit 5:

0 = ok



– Bit 6:

0 = ok

1 = frame error:


– Bit 7:

0 = ok




Defines the receive-data (0...7).

Defines the data received via RS485/422

(0...7) + acknowledge for reception

Number of the valid user data bytes in this data segment. I

5-62



Table 56:

Object instance

Attr. No.

dec.

(hex.)

120

(78h)

Attribute name

Get/

Set

TX count G/S

121

(79h)

122

(7Ah)

123

(7Bh)

124

(7Ch)

125

(7Dh)

RX count acknowledge

Status reset control

Process control data

TX data

TX data and release

G/S

G/S

G/S

G/S

S


USINT

USINT

This value is transferred together with every data segment.

The TX count values are sequential:

00->01->10->11->00....

(decimal: 0->1->2->3->0....)


This value is a copy of RX count.

RX count has been transmitted together with the last data segment of the process input data.

RX count acknowledge is an acknowledge for the successful transmission of the data segment with RX count.

BOOL STATRES:

This bit is set to reset the STAT bit in the process input data.

With the change from 1 to 0 the status bit is reset

(from 0 to 1).

If this bit is 0, all changes in TRANSMIT

BYTE count, TRANSMIT count and RECEIVE count acknowledge are ignored.

Flushing the transmit-/ receive-buffer with process control data (Attr. 123)

is possible.

If this bit is 1 or with the change from 0 to

1, the flushing of the transmit-/ receivebuffer with ROCESS control data (Attr. 123)

is not possible.

BYTE Bit 0 = transmit-buffer flush,

Bit 1 = receive-buffer flush

Defines the transmit-data (0...7) ARRAY OF

BYTE

ARRAY OF

BYTE

Defines the data to be transmitted via

RS485/422 (0...7) + transmission is released/ charged immediately

126

(7Eh) reserved


5-63


Table 56:

Object instance

Attr. No.

dec.

(hex.)

127

(7Fh)

Attribute name

Get/

Set

Diagnostics G

Type

WORD

128

(80h)

Active mode G/S BOOL

Description

Contains the diagnostic messages (low byte):



– Bit 3:

0 = ok



– Bit 4:

0 = ok




– Bit 5:

0 = ok



– Bit 6:

0 = ok

1 = frame error:


– Bit 7:

0 = ok



– High byte: reserved

0 = 1byte ctrl/status header: The diagnostic data are not part of the process input data, 7 bytes of user data are available.

1 = 2byte ctrl/status header: The diagnostic data are part of the process input data, 6 bytes of user data are available.

5-64



Table 56:

Object instance

Attr. No.

dec.

(hex.)

129

(81h)

Attribute name

Get/

Set

Bit rate G/S

Type

ENUM

USINT

130

(82h)

131

(83h)

132

(84h)

133

(85h)

134

(86h)

Disable diagnostics

Flow control

Data width

Parity

Stop bits

G/S

G/S

G/S

G/S

G/S

BOOL

ENUM

USINT

ENUM

USINT

ENUM

USINT

ENUM

USINT

Description

Used to set the baudrate for the gateway:

0 = reserved,

1 = 300 bps

2 = 600 bps

3 = 1200 bps

4 = 2400 bps

5 = 4800 bps

6 = 9600 bps

7 = 14400 bps

8 = 19200 bps

9 = 28800 bps

10 = 38400 bps

11 = 57600 bps

12 = 115200 bps

...

15 = reserved)

0 = released:

The diagnostic function is activated.

1 = blocked:

The diagnostic function is deactivated.

0 = off: data flow control is deactivated

1 = XON/XOFF

Software-handshake is activated

2 = RTS/CTS

Hardware-handshake is activated

3 = reserved

0 = 7 bits

1 = 8 bits

0 = none

1 = odd

The number of the bits set to 1 is odd (incl. data and parity bit).

2 = even

The number of the bits set to 1 is even (incl. data and parity bit).

Number of the stop bits.

0 = 1 bit

1 = 2 bits


5-65


Table 56:

Object instance

Attr. No.

dec.

(hex.)

135

(87h)

Attribute name

Get/

Set

XON character

G/S

136

(88h)

137

(89h)

XOFF character

RSXX

Modus

G/S

Type

USINT

USINT

G/S ENUM

USINT

Description

XON character

This sign is used to start the data transfer to the data terminal equipment (DTE) with the activation of the software handshake.

0 - 255 default: 17/ 11h

XOFF character

This sign is used to stop the data transfer to the data terminal equipment (DTE) with the activation of the software handshake.

(0 - 255) default: 19/ 13h

0 = RS422:

Parameterization as 422

1 = RS485:

Parameterization as 485

5-66



5.3.16

SSI Module Class (VSC116)

This Class contains all information and parameters for SSI-modules.

Note




Table 57:

Object instance

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

102

(66h)


G

Type

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)

109

(6Dh

110

(6Eh)

Module ID

Module order number

Module order name


Module type ID



Module registered

Index

G

G

G

G

G

G/S

G

G

Description

USINT

BOOL

USINT

DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY

ARRAY

ENUM

USINT







CLASS.



Contains the name of the module, for example, "BL67-1SSI".





ARRAY OF:



ARRAY OF:




5-67


Table 57:

Object instance

Attr. No.

dec.

(hex.)

111

(6Fh)

112

(70h)

Attribute name

Get/

Set


Diagnostics and status

G

G

Type

USINT

WORD

Description


Instance.

Bit 0:

0 = No enabled status signal is active

(SSI_STSx = 0).

1 = group diagnostics

At least one enabled status signal is active

(SSI_STSx = 1).

Bit 1:

0 = SSI encoder signal present.

1 = SSI error/open circuit

SSI encoder signal faulty. (e.g. due to a cable break).

Bit 2:

0 = A comparison of the register contents has produced the following result:

(REG_SSI_POS)

≤ (REG_UPPER_LIMIT)

1 = error POS > UPPER LIMIT

A comparison of the register contents has produced the following result:

(REG_SSI_POS) > (REG_UPPER_LIMIT)

Bit 3:


(REG_SSI_POS)

≥ (REG_LOWER_LIMIT)

1 = error POS < LOWER LIMIT


(REG_SSI_POS) < (REG_LOWER_LIMIT)

Bit 4

0 = The parameter set of the module has been accepted.

1 = parameterization error

Operation of the module is not possible with the present parameter set.

Bit 5 to 6

<reserved>

Bit 7

0 = The SSI encoder is read cyclically.

1 = SSI communication suspended

Communication with the SSI encoder is stopped as STOP = 1 (process output) or

ERR_PARA = 1.

5-68



Table 57:

Object instance

Attr. No.

dec.

(hex.)

112

(70h)

Attribute name

Get/

Set


G

Type

WORD

Description

Bit 8


(REG_SSI_POS)

≠ (REG_CMP1)

1 = CMP1 register value matches POS


(REG_ SSI_POS) = (REG_CMP1)

Bit 9

0 = Default status, i.e. the register contents have not yet matched

(REG_SSI_POS) = (REG_CMP1) since the last reset.

1= CMP1 flag set

The contents of the registers match:

(REG_SSI_POS) = (REG_CMP1). This marker must be reset with bit 9 of the control attribute.

Bit 10


(REG_SSI_POS) < (REG_CMP1)

1 = POS

≥ CMP1 register value


(REG_ SSI_POS)

≥ (REG_CMP1)

Bit 11


(REG_SSI_POS)

≠ (REG_CMP2)

1 = CMP2 register value matches POS


(REG_ SSI_POS) = (REG_CMP29

Bit 12

0 = Default status, i.e. the register contents have not yet matched (REG_SSI_POS) =

(REG_CMP2) since the last reset.

1 = CMP2 flag set

The contents of the registers match:

(REG_SSI_POS) = (REG_CMP2).

This marker must be reset with bit 12 of the control attribute.


5-69


Table 57:

Object instance

Attr. No.

dec.

(hex.)

112

(70h)

Attribute name

Get/

Set


G

113

(71h)

Result write operation

G

Type

WORD

WORD

Description

Bit 13


(REG_SSI_POS) < (REG_CMP2)

1 = POS

≥ CMP2 register value. A comparison of the register contents has produced the following result:

(REG_SSI_POS)

≥ (REG_CMP2)

Bit 14

0 = The SSI encoder values are incremented or the values are constant.

1 = counting downwards

The SSI encoder values are decremented.

Bit 15

0 = The SSI encoder values are decremented or the values are constant.

1 = counting upwards

The SSI encoder values are incremented.

Bit 0 to 5 <reserved>

Bit 6:

0 = No modification of the data in the register bank by process output, i.e.

"Write operation" = 0.

A write job would be accepted with the next telegram of process output data.

(handshake for data transmission to the register.)

1 = control register write acknowledged A modification of the register contents by a process output was initiated, i.e.

"Write operation" = 1.

A write job would not be accepted with the next telegram of process output data.

Bit 7:

0 = The writing of user data for process output to the register addressed with

"Address write register" in the process output data could not be executed.

1 = control register write accepted

The writing of user data for process output to the register addressed with "Address write register" in the process output data could be executed successfully.

5-70



Table 57:

Object instance

Attr. No.

dec.

(hex.)

114

(72h)

Attribute name

Get/

Set

Result in read operation

G

115

(73x)

116

(74h)

117

(75h)

Address read register

Value read register

Control

G

G

G/S

Type

BYTE

UINT

DWORD

WORD

Description

Bit 0 to 6: <reserved>

Bit 7:

0 = The reading of the register stated in

"Address read register" was accepted and executed. The content of the register is located in "Value read register".

1 = register read operation aborted

The reading of the register stated in

"Address read register" was not accepted.

"Value read register" is zero.

Address of the input register with contents stated in "Value read register" when

"Result read operation“ = 0.

Content of the register to be read if "Result read operation“= 0.

If "Result read operation“ = 1,

"Value read register" = 0.


Bit 7:

0 = Request to read the SSI encoder cyclically

1 = suspend communication requested

Request to interrupt communication with the encoder

Bit 8:

0 = Default status, i.e. the data bits 8 to 10 of the “Diagnostics and status“ attribute always have the value 0, irrespective of the actual SSI encoder value.

1 = compare/flag CMP1 active Comparison active, i.e. the data bits 8 to 10 of the

“Diagnostics and status“ attribute always have a value based on the result of the comparison with the actual SSI encoder value.

Bit 9:

0 = Default status, i.e. reset of Bit 9 of the

“Diagnostics and status“ attribute not active.

1 = clear CMP1 flag Reset of bit 9 of the

“Diagnostics and status“ attribute active.

Bit 10: <reserved>


5-71


Table 57:

Object instance

Attr. No.

dec.

(hex.)

117

(75h)

Attribute name

Get/

Set

Control G/S

118

(76h)

119

(77h)

120

(78h)

121

(79h)

122

(7Ah)

Address read register

Address write register

Value write register

Write operation

Write register and execute

G/S

G/S

G/S

G/S

S


UINT

UINT

DWORD

0 = Default status, i.e. the data bits 11 to 13 of the “Diagnostics and status“ attribute always have the value 0, irrespective of the actual SSI encoder value.

1 = compare/flag CMP2 active Comparison active, i.e. the data bits 11 to 13 of the

“Diagnostics and status“ attribute always have a value based on the result of the comparison with the actual SSI encoder value.

Bit 12:

0 = Default status, i.e. no reset of Bit 12 of the “Diagnostics and status“ attribute active.

1 = clear CMP2 flag Reset of bit 12 of the

“Diagnostics and status“ attribute active.


Address of the register with contents stated in "Value read register" when

"Result read operation“ 7 = 0.

Address of the register to be written with

"Value write register".

Value to be written to the register with the address stated at "Address write register".

BOOL 0 = Default status, i.e. there is no request to overwrite the content of the register address stated at "Address write register" with "Value write register". Bit 6 of the

"Result write operation“" attribute is reset

(=0) if necessary.

1 = Request to overwrite the content of the register at the address "Address write register" with "Value write register".

STRUCT OF

UINT

DWORD

The structure contains both parts:

– Address of the register to be written.

– Value to be written.

The write operation is executed without checking whether a write job is already present.

5-72



Table 57:

Object instance

Attr. No.

dec.

(hex.)

123 (7Bh)

Attribute name

Get/

Set

Diagnostics G

Type

WORD

124

(7Ch)

Check mode G/S WORD

Description

Bit 0:

0 = No enabled status signal is active

(SSI_STSx = 0).

1 = group diagnostics

At least one enabled status signal is active (SSI_STSx = 1).

Bit 1:

0 = SSI encoder signal present.

1 = SSI error/open circuit SSI encoder signal faulty.

(e.g. due to a cable break).

Bit 2:


(REG_SSI_POS)

≤ (REG_UPPER_LIMIT)

1 = error POS > UPPER LIMIT A comparison of the register contents has produced the following result:

(REG_SSI_POS) > (REG_UPPER_LIMIT)

Bit 3:


(REG_SSI_POS)

≥ (REG_LOWER_LIMIT)

1 = error POS < LOWER LIMIT A comparison of the register contents has produced the following result:

(REG_SSI_POS) < (REG_LOWER_LIMIT)

Bit 4:

0 = The parameter set of the module has been accepted.

1 = parameterization error

Operation of the module is not possible with the present parameter set.



Bit 5:

0 = ZERO test of data cable.

1 = disable SSI error detection

After the last valid bit, a ZERO test of the data cable is not carried out.



5-73


Table 57:

Object instance

Attr. No.

dec.

(hex.)

125

(7Dh)

Attribute name

Get/

Set

Invalid bits LSB G/S

126

(7Eh)

128

(80h)

129

(81h)

130

(82h)

Bit rate

Frame length

Kind of coding SSI

Invalid bits MSB

G/S

G/S

G/S

Type

USINT

ENUM

USINT

USINT

BOOL

USINT

Description

Number of invalid bits on the LSB side of the position value supplied by the SSI encoder. The meaningful word width of the position value transferred to the module bus master is as follows: FRAME

LENGTH - INVALID BITS MSB -

INVALID BITS LSB.

The invalid bits on the LSB side are removed by shifting the position value to the right, starting with the LSB.

(Default 0 Bit = 0 hex

). INVALID BITS MSB +

INVALID BITS LSB must always be less than

FRAME LENGTH.

0 = 1 Mbps

1 = 500 kbps

2 = 250 kbps

3 = 100 kbps

4 = 125 kbps

5 = 83 kbps

6 = 71 kbps

7 = 62.5 kbps

8 to 15 <reserved>

Number of bits of the SSI data frame.

FRAME LENGTH must always be greater than

INVALID_BITS.

A

Default: 25 = 19 hex

0 = Binary code

1 = GRAY code

Number of invalid bits on the MSB side of the position value supplied by the SSI encoder. The meaningful word width of the position value transferred to the module bus master is as follows:

FRAME LENGTH -

INVALID BITS MSB -

INVALID BITS LSB.

The invalid bits on the MSB side are zeroed by masking the position value. I

NVALID BITS MSB

+ INVALID BITS LSB must always be less than FRAME LENGTH.

Default: 0 = 0 hex

5-74



5.3.17

Digital Versatile Module Class (VSC117)

This class contains all information and parameters for digital versatile modules.

Attention

In this class, chosen parameter options can only be deactivated by activating another option of this parameter.

Note




Oject Instance

Table 58:

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)


Module ID

Module order number

Module order name

Module revision

Module type ID


G

G

G

G

G

G

G/S

Description

USINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY







CLASS.


DWORD







ARRAY OF:



5-75


Table 58:

Object instance

Attr. No.

dec.

(hex.)

109

(6Dh)

Attribute name

Get/

Set


G

Type

ARRAY

110

(6Eh)

Module registered

Index

111

(6Fh)

112

(70h)

Input data

Module input channel count

Module output

Channel count

Module input_1 113

(71h)

114

(72h)

Module input_2

G

G

G

G

G

ENUM

USINT

USINT

USINT

DWORD

DWORD

Description


ARRAY OF:



Contains the number of input channels supported by the module.

Contains the number of output channels supported by the module.

Input data of the module (according to channels).


Output data

115

(73h)

Module output_1 G

116

(74h)

Module output _2

Diagnosis data

G

117

(75h)

Open circuit error_1

G

G 118

(76h)

119

(77h)

Open circuit error_2

Short circuit output error_1

G

120

(78h)

121

(79h)

Short circuit output error_2

Short circuit sensor error_1

G

G

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

Output data of the module (according to channels).


This attribute contains diagnosis information about open circuit errors

(according to channels).



This attribute contains diagnosis information about output short-circuits




This attribute contains diagnosis information about sensor short-circuits


5-76



Table 58:

Object instance

Attr. No.

dec.

(hex.)

122

(7Ah)

Attribute name

Get/

Set

Short circuit sensor error_2

G

123

(7Bh)

124

(7Ch)

Parameter data

125

(7Dh)

126

(7Eh)

135

(87h)

136

(88h)

137

(89h)

131

(83h)

132

(84h)

133

(85h)

134

(86h)

127

(7Fh)

128

(80h)

129

(81h)

130

(82h)

Cable error_1

Cable error_2

Open circuit monitoring mode_1

Open circuit monitoring mode_2

Invert input data_1

Invert input data_2

Invert output data_1

Invert output data_2 reserved reserved

Auto recovery output_1

Auto recovery output_2 reserved reserved

Retriggered recovery output_1

G

G

G/S

G/S

G/S

G/S

G/S

G/S

-

-

G/S

G/S

-

-

G/S

Type

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

-

-

DWORD

DWORD

-

-

DWORD

Description

This attribute contains diagnosis information about sensor short-circuits


This attribute contains open-circuit diagnosis information (channel 1 to 32).

This attribute contains open-circuit diagnosis (channel 33 to 64).

Enables the open-circuit monitoring

(channel 1 to 32).

Enables the open-circuit monitoring

(channel 33 to 64).

The input signal is inverted (channel 1 to

32).

The input signal is inverted (channel 33 to

64).

The output signal is inverted (channel 1 to

32).

The output signal is inverted (channel 33 to 64).

-

-

The outputs switch on automatically after an overload.

The outputs switch on automatically after an overload.

-

-

The outputs (channel 1 to 32) have to be retriggered in case of an overload.


5-77


Table 58:

Object instance

Attr. No.

dec.

(hex.)

138

(8Ah)

139

(8Bh)

140

(8Ch)

141

(8Dh)

142

(8Eh)

143

(8Fh)

144

(90h)

145

(91h)

146

(92h)

147

(93h)

148

(94h)

Attribute name

Get/

Set

Retriggered recovery output_2

Enable high side output driver_1

Enable high side output driver_2

Enable low side output driver_1

Enable low side output driver_2

Filter 2500

μs

Channel 1

Filter 2500

μs

Channel 2

Fault value

Fault value

Block diagnostics

Block diagnostics

G/S

G/S

G/S

G/S

G/S

G/S

G/S

G/S

G/S

G/S

G/S

Type

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

DWORD

Description

The outputs (channel 33 to 64) have to be retriggered in case of an overload.

the side output driver of channels (channel 1 to 32).

the side output driver of channels (channel 33 to 64).

Enables the low side output driver of channels (channel 1 to 32).

Enables the low side output driver of channels (channel 33 to 64).

Enables the input filter of the channel

(channel 1 to 32).

Enables the input filter of the channel

(channel 33 to 64).

Activates the fault value for the channel

(channel 1 to 32).

Activates the fault value for the channel

(channel 33 to 64).

Channel specific diagnostic information is blocked (channel 1 to 32).

Channel specific diagnostic information is blocked (channel 33 to 64).

5-78



5.3.18

Analog Versatile Module Class (VSC118)

This class contains all information and parameters for analog versatile modules.

Attention


Note




Object instance

Table 59:

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)


Module ID

Module order number

Module order name

Module revision

Module type ID


G

G

G

G

G

G

G/S

Description

USINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY







CLASS.


DWORD







ARRAY OF:



5-79


Table 59:

Object instance

Attr. No.

dec.

(hex.)

109

(6Dh)

Attribute name

Get/

Set


G

Type

ARRAY

110

(6Eh)

111

(6Fh)



112

(70h)

Input data

Module output

Channel count

Channel_1 113

(71h)

...

128

(80h)

129

(81h) to

144

(90h)

Channel_16 reserved

Diagnosis data

145 (91h) Range error

G

G

G

G

G

G

G

146 (92h)

147

(93h)

Open circuit error

Short circuit output error

148 (94h) reserved

149 (95h) to 164

(A4h) reserved

G

G

ENUM

USINT

USINT

USINT

UINT

UINT

UINT

Description


ARRAY OF:





Input data of the module, channel 1.

Input data of the module, channel 16.

Output data of the module.

WORD

WORD

DWORD

This attribute contains diagnosis information errors in the measurement value range (according to channels).





5-80



Table 59:

Object instance

Attr. No.

dec.

(hex.)

Parameter data

165

(A5h)

...

Operating mode_ channel 1

180

(B4h)

Attribute name

Operating mode_ channel 16

Get/

Set

G/S

G/S

181 (B5h) Representation mode _channel_1

G/S

...

196 (C4h)

197

(C5h)

Representation mode

_channel_16

Block diagnostics

G/S

Type

ENUM

USINT

ENUM

USINT

ENUM

USINT

WORD

Description

Parameter for setting the operating mode of the respective channel:


1 = -10 V...+10 V

2 = 0 V...+10 V

3 = 0 mA...20 mA

4 = 4 mA...20 mA

Parameter for setting the type of value representation for the respective channel:

0 = default

1 = 16 bit integer

2 = 12 bit left justified + diagnostics

Channel specific diagnostic information is blocked.


5-81


5.3.19

CVI Module Class (VSC119)

This class contains all information and parameters for the modules BL67-1CVI.

Attention


Note




Object instance

Table 60:

Object instance

Attr. No.

dec.

(hex.)

100

(64h)

101

(65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102

(66h)

103

(67h)

104

(68h)

105

(69h)

106

(6Ah)

107

(6Bh)

108

(6Ch)


Module ID

Module order number

Module order name

Module revision

Module type ID


G

G

G

G

G

G

G/S

Description

USINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY







CLASS.


DWORD







ARRAY OF:


5-82



Table 60:

Object instance

Attr. No.

dec.

(hex.)

109

(6Dh)

Attribute name

Get/

Set


G

Type

ARRAY

ENUM

USINT

118

(76h)

...

125

(7Dh)

110

(6Eh)

Module registered

Index

111

(6Fh)

112

(70h)

Input data


Module output

Channel count

G

G

G

113

(71h)

114

(72h)

Output data

Module input_1

Module input_2

G

G

115

(73h)

116

(74h)

Module output_1

Module output _2

Diagnosis data

G

G

117

(75h)

Common error

G

G Valve node_1 error

...

Valve node_8 error

G

USINT

USINT

DWORD

DWORD

DWORD

DWORD

BYTE

BYTE

BYTE

Parameter data

126

(7Eh)

Guard time

127

(7Fh)

Life time factor

G/S

G/S

USINT

USINT

Description


ARRAY OF:









This attribute contains diagnosis information about common errors of the module.

This attribute contains diagnosis information about errors of the connected node no. 1.

This attribute contains diagnosis information about errors of the connected node no. 8.

Setting the Guard-Time in steps of 100 ms

(value 0 to 255); default 3 = 300 ms

Factor which defines how often a node is allowed not to answer a request or to exceed the Guard-Time (values 0 to 255); default = 3


5-83


Table 60:

Object instance

Attr. No.

dec.

(hex.)

128

(80h)

Attribute name

Get/

Set

CANopen baudrate

G/S

129

(81h)

130

(81h) reserved

Common config

-

G/S

131

(82h)

...

Node_1 output length

138 (8Ah) Node_8 output length

G/S

G/S

139

(8Bh)

...

146 (92h)

147 (93h)

148 (94h)

Node_1 input length

Node_8 input length

Guarding

Activation

G/S

G/S

G/S

G/S

Type

ENUM

USINT

-

Description

Setting the baudrate for CANopen:

0 = 1000k

1 = reserved

2 = 500k

3 = 250k

4 = 125k

A

5 = 50k

6 = 20k

7 = 10k

-

DWORD

USINT

USINT

USINT

USINT

BYTE

BYTE

Activation of the bus terminating resistor:

0 = no terminating resistor

A

1 = terminating resistor active

Defines the length of the output data of the respective node:

0 = 0 bit

1 = 4 bit

2 = 8 bit

3 = 12 bit

4 = 16 bit

5 = 24 bit

6 = 32 bit

Defines the length of the input data of the respective node:

0 = 0 bit

1 = 4 bit

2 = 8 bit

3 = 12 bit

4 = 16 bit

5 = 24 bit

6 = 32 bit

Activates the node guarding (according to channels).

Node activation (according to channels).

5-84



5.3.20

RFID-S module class (VSC124)

This class contains all information and parameters for the modules BL20-2RFID-S.

Attention


Note

Please refer to paragraph section "Class instances of the VSC“ , page 5-25

, for the description of the class instances for VSC.

Object Instance

Note

The object instances of VSC 124 represent the individual RFID-S channels, not the complete modules!

Tabelle 61:

Object instance

Attr. no.

dec. (hex.)

100 (64h)

101 (65h)

Attribute name

Get/

Set


Module present

G

G

Type

USINT

BOOL

102 (66h)

103 (67h)

104 (68h)

107 (6Bh)


Module ID

Module order number

105 (69h) Module order name

106 (6Ah) Module revision

Module type ID

108 (6Ch) Module command interface

G

G

G

G

G

G

G/S

Description

USINT

DWORD

UDINT

SHORT

STRING

USINT

ENUM

USINT

ARRAY



1 = electronics module is plugged




CLASS.



Contains the name of the module, for example, "BL20-2RFID-S".


Describes the module type: see attribute 107 (6Bh) on

page 5-32

The control interface of the module.

ARRAY OF:



5-85


Tabelle 61:

Object instance

Attr. no.

dec. (hex.)

Attribute name

Get/

Set

109 (6Dh) Module response interface

G

110 (6Eh)

111 (6Fh)

112 (70h)

113 (71h)

114 (72h)

Diag size

Diag


G

Module output data

G

Module input data G

115 (73h)

116 (74h)

Bypass time channel 1

Bypass time channel 2

G

G

G/S

G/S

Type

ARRAY

UINT

WORD

ENUM

USINT

ARRY OF

BYTE

ARRY OF

BYTE

WORD

WORD

Description

Response interface of the module.

ARRAY OF:


Indicates the number of diagnostic bits of the module.


WORD:



Process data output information.

Process data input information.

Bypass time in ms

Bypass time in ms

Note

For further information concerning the RFID communication interfaces see the special

RFID documentation which can be downloaded from www.turck.com.

5-86


6.2

6.3

6.3.1

6.3.2

6.3.3

6.4

6.4.1

6.5

6.6

6.6.1

6.6.2

6.6.3

6.7

6.7.1

6.8

6.8.1

6 Application example: BL67 gateway at Allen Bradley PLC

6.1

6.1.1

General.............................................................................................................................................. 2

Prerequisites for this example .............................................................................................................. 2

– Example station ................................................................................................................................. 2

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

Changing the IP address of a PC/ network interface card ................................................................. 4

Changing the IP address in Windows 2000/ Windows XP ................................................................... 4

Changing the IP address in Windows NT............................................................................................. 6

Changing the IP address via I/O-ASSISTANT V3................................................................................. 6

– Deactivating/ adapting the firewall in Windows XP ........................................................................... 9

Address setting at the gateway ...................................................................................................... 12

Address setting via DHCP-mode ...................................................................................................... 12

Setting-up communications with the software tool "RSLinx"......................................................... 15

Configuration of the network in "RSLogiX 5000" ........................................................................... 16

Configuration of the controller............................................................................................................ 16

Configuration of a BL67 station.......................................................................................................... 18

Downloading the I/O configuration..................................................................................................... 19

Examples for I/O data mapping ...................................................................................................... 22

Mapping report via I/O-ASSISTANT ................................................................................................... 24

Example for process data access ..................................................................................................... 26

Setting outputs at BL67-8DO-0.5A-P ................................................................................................ 26


6-1

Application example: BL67 gateway at Allen Bradley PLC

6.1

General

The following example shows detailed information about the connection of a BL67 station for

EtherNet/IP to an Allen Bradley PLC.

6.1.1

Prerequisites for this example

In order to configure BL67 devices and to build up communications with the Allen Bradley ControlLogix

PLC over EtherNet/IP, the following software tools and hardware devices are necessary.

Software:

RSLinX - used to establish communication over EtherNet/IP

RSLogix 5000 - used to configure the controller and the other network hosts

Hardware used in this example:

Allen Bradley PLC 1756-L55/ A 1756-M12/A LOGIX5555,

Ethernet Bridge 1756-ENBT/A

BL67 station with a gateway BL67-GW-EN-IP with EtherNet/IP protocol

Example station

The following station is used in this application example:

Table 62:

Example station

Module Data width

Process input Process output Alignment

5

6

3

4

1

2

GW

0

7

8

9

10

BL67-GW-EN-IP

BL67-2AI-I

BL67-4DI-P

BL67-8DI-PD

BL67-2AI-TC

BL67-8XSG-PD

BL67-4DI-PD

BL67-8DI-P

BL67-8DO-0.5A-P

BL67-2AO-V

BL67-2AI-I

BL67-1RS232

2 words

4 bits

8 bits

2 words

8 bits

4 bits

8 bits

-

-

2 words

4 words

-

-

-

-

8 bits

-

-

8 bits

2 words

-

4 words word by word bit by bit bit by bit word by word bit by bit bit by bit bit by bit bit by bit word by word word by word word by word

6-2


Network configuration

6.2

Network configuration

The BL67 gateways are delivered with the default IP address 192.168.1.×××.

Note

In order to build up the communication between the BL67 gateway and a PLC/ PC or a network interface card, both devices have to be hosts in the same network.

To achieve this, you have whether

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 4 ,

Address setting for EtherNet/IP , page 4-11

.

or

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

read the following section "Changing the IP address of a PC/ network interface card“

,

page 6-4

).


6-3


6.3

Changing the IP address of a PC/ network interface card

6.3.1

Changing the IP address in Windows 2000/ Windows XP

The IP address is changed in the "Control Panel" in "Network and Dial-up Connections":

1 Open the folder "Local Area Connection" and open the dialog "Local Area Connection Properties" via the button "Properties" in the dialog "Local Area Connection Status".

2 Mark "Internet Protocol (TCP/IP)" and press the "Properties"-button to open the dialog "Internet

Protocol (TCP/IP) Properties".

Figure 30:

Local Area

Connection

Properties

6-4



Figure 31:

Changing the

PC’s IP address

3 Activate "Use the following IP address" and assign an IP address of the network mentioned above to the PC/ Network interface card (see the following figure).


6-5


6.3.2

Changing the IP address in Windows NT

1 Open the folder "Network" in the Control Panel.

2 Activate TCP/IP connection in the tab "Protocols" and click the "Properties" button.

Figure 32:

Network configuration WIN NT

Figure 33:

Specify

IP address

3 Activate "Specify IP address " and set the address as follows.

6-6



6.3.3

Changing the IP address via I/O-ASSISTANT V3

The Busaddress Management DTM in the software I/O-ASSISTANT offers the possibility to browse the whole Ethernet network for connected nodes and to change their IP address as well as the subnet mask according to the application.

Select the used network card under "Online available devices"and browse the connected network by pressing the search button.

Figure 34:

Busaddress

Management in the

I/O-ASSISTANT

Attention

If Windows XP is used as operating system, problems with the system internal firewall may occur.

It may eventually inhibit the access of the I/O-ASSISTANT to the Ethernet. Please adapt your firewall settings accordingly or deactivate it completely (see also

Deactivating/ adapting the firewall in Windows XP

,

page 6-9 ).


6-7


Figure 35:

Address changing for selected nodes

The network is browsed for connected nodes which are then listed in the Busaddress Management.

It is now possible to change the address settings for all nodes in the list or only for the selected one.

Mark the selected node, enter a new IP address and apply this address by confirming the changes using the "Apply" button.

Note

For further information about the I/O-ASSISTANT, it’s functions and it’s handling, please read the online help of the software.

6-8



Figure 36:

Deactivating the Windows firewall

Deactivating/ adapting the firewall in Windows XP

If you use Windows XP as operating system, problems may occur when changing the IP addresses via the I/O-ASSISTANT.

In this case, you can deactivate the system integrated Windows XP firewall completely or adapt it to your application.

Deactivating the firewall

Open the "Windows Firewall" dialog in the control panel of your PC and deactivate it as follows:


6-9


Figure 37:

Activating the

Windows firewall

Adapting the firewall

The firewall remains active, the option "Don’t allow exceptions" it deactivated:

In the "Exceptions"-tab, add the I/O-ASSISTANT to "Programs and Services".

Pressing the button "Add Program..." opens the dialog "Add a Program". Select the I/O-ASSISTANT from the list of installed programs.

6-10



Figure 38:

"Exceptions"tab

If necessary, use the button "Browse..." to choose the file

"IOassistant.exe" from the installation directory of the software.

Despite an active firewall, the I/O-ASSISTANT is now able to browse the network for hosts and the address changing via the software is possible for the connected nodes.


6-11


6.4

Address setting at the gateway

6.4.1

Address setting via DHCP-mode

In this application example, the IP address is set via DHCP using the software tool "BootP/DHCP-Server" version 2.3.2.0 from Rockwell Automation.

Figure 39:

BootP-Server from Rockwell

Automation

Addresses in the range from 1 to 254 can be allocated in the examplary default subnet 192.168.1. The addresses 0 and 255 are reserved for broadcast messages in the subnet.

Note

The rotary coding switches on the gateway must be set to "400" or "600" in order to enable the DHCP-Mode or respectively the PGM-DHCP-mode.

6-12


Address setting at the gateway

Figure 40:

DHCP-request of BL67 gateway

After having been connected to the network, the BL67 sends DHCP requests to the server using its

MAC-ID.

Figure 41:

Setting the IP address via

DHCP

A double click on the request-entry opens the "New Entry" dialog box in which an IP address can be assigned to the module’s

MAC-ID.


6-13


Figure 42:

Setting the IP address via

DHCP

The BootP/DHCP-Server sends the IP Address via BootP/DHCP to the BL67 gateway and, after a few seconds, the gateway answers with its new IP address when having stored it.

The "Relation list" can be stored for further applications. It can serve for permanent assignment of defined IP addresses to MAC-IDs/ modules.

Attention

If the BootP/DHCP-server is shut down, the BL67 gateway loses the IP address after a power reset!

6-14


Setting-up communications with the software tool "RSLinx"

6.5

Setting-up communications with the software tool "RSLinx"

Before the EtherNet/IP network can be configured, access to EtherNet/IP must be established using the software "RSLinx" (version 2.43.01) from Rockwell Automation.

The following example explains the creation of a connection via the Allen Bradley EtherNet/IP interface.

The selection of the EtherNet/IP Driver module is done using the "Communications

→ Configure

Drivers" command.

Select the driver type category "EtherNet/IP Driver".

Once the driver type has been selected, click the "Add new" button and choose a name for the new

EtherNet/IP Driver.

Figure 43:

Selecting the

EtherNet/IP

Driver module

Figure 44:

Scanning the

EtherNet/IP

network via

RSWho

The connection to EtherNet/IP is established following successful configuration driver

In RSLinx, the "Autobrowse" function can be used to scan the network. All hosts in the network, which is defined by the settings of your network card, will be found.


6-15


6.6

Configuration of the network in "RSLogiX 5000"

The EtherNet/IP hosts (PLC, EtherNet/IP interface, I/O modules) have to be configured using the software "RSLogix 5000" (in this example version 15) from Rockwell Automation.

Start RSLogix and open a new project using the "File" menu.

Figure 45:

Creating a new project in

RSLogix

6.6.1

Configuration of the controller

Enter the information related to the controller depending on your configuration, as well as a name for the project.

Figure 46:

Configuration of the controller

6-16

Your project will be opened offline. In order to configure the network, please right-click "I/O

Configuration" and select "new Module" to add the first host, the EtherNet/IP bridge, to the network.



Figure 47:

Selection of the

EtherNet/IP bridge

Open "Communications" and select the bridge. In this example this would be 1756-ENBT/A.

Figure 48:

Major Revision of the EtherNet/

IP Bridge

Enter the "Major Revision" of your EtherNet/IP bridge and click "OK".

Figure 49:

Configuring the

EtherNet/IP

Bridge

In the following dialog box "New Module" enter the a name for the bridge and define its IP Address (in this example 192.168.1.100).

In the following dialog box "Module Properties: Local..." press "OK". You may also browse offline through the module properties when you click "Next". At this point there is no need for further entry action. If "Next" is selected, the "Module Properties" window displays information that will be available


6-17


when the module is online. The configuration of the interface is completed. Press "Finish" to close the dialog box.

6.6.2

Configuration of a BL67 station

Add the BL67 to the I/O configuration by using a right-click on the EtherNet/IP bridge module 1756-

ENBT/A and select "New Module".

Figure 50:

Adding the BL67 station to the I/

O configuration

Figure 51:

Add generic

Ethernet module

Open "Communications" and select the entry "Generic Ethernet Module" to configure a BL67 gateway.

6-18



Figure 52:

Configuration of BL67 gateway

For the Assembly Instances 101 and 102, the Connection Parameters (input and output size = 256 Byte each) are static and have to be set as follows:

Note

If the variable Assembly Instances 103 and 104 (see

page 5-12

) are used, the

Connection Parameters have to be set according to the actual station configuration which means, the in- and output sizes have to match the sizes definitely required by the station. This required in- and output size (2 to max. 496 Byte) can be read out using Assembly Class (0×04),

Instance 0×67, Attr. 0×04 and Assembly Class (0×04), Instance 0×68, Attr. 0×04.

Figure 53:

Set connection options for BL67

In the "Connection" tab set the "Requested Packet Interval" (RPI) to 10 ms, which normally should be the default setting. For BL67, the successfully tested RPI range is 5 and higher.


6-19


6.6.3

Downloading the I/O configuration

If the configuration of the network is completed, it can be downloaded to the controller by using for example the "Communication

→ Download" command.

Figure 54:

Downloading the configuration

Figure 55:

Downloading the configuration

In the "Download" dialog box, start the download by pressing the "Download" button.

Figure 56:

Error message

If an error message is generated, warning, that the communication path can not be found, please open the "Path" menu (see

Figure 57: ), select your controller and press "Set Project Path" (see Figure 58:

).

6-20



Figure 57:

Communication Path

Figure 58:

Communication Path

Figure 59:

Controller Tags

If the correct communication path is set, it is possible to download the configuration.

Once the I/O configuration is downloaded and the controller is in "Run" or "Remote Run" mode, the I/

O-data mapping of the BL67 station is shown in the "Controller Tags":

The controller tags for BL67 are divided into:

BL67_Turck: C - the station’s mapped configuration data

BL67_Turck: I - the station’s mapped input data

BL67_Turck: O - the station’s mapped output data


6-21


6.7

Examples for I/O data mapping

Each module is now accessible via the controller tags for viewing input data and/or forcing outputs.

The data mapping depends on the data width of each module connected to the gateway.

Table 63:

Example station

Module

GW BL67-GW-EN-IP

0

1

BL67-2AI-I

BL67-4DI-P

2

3

4

5

BL67-8DI-PD

BL67-2AI-TC

BL67-8XSG-PD

BL67-4DI-PD

6

7

8

9

10

BL67-8DI-P

BL67-8DO-0.5A-P

BL67-2AO-V

BL67-2AI-I

BL67-1RS232

-

-

4 bits

8 bits

2 words

4 words

Data width

Process input

1 status word

2 words

4 bits

8 bits

2 words

8 bits

-

-

Process output

1 control word

-

-

8 bits

-

-

8 bits

2 words

-

4 words

6-22



Table 64:

Data mapping for the example station

A

I.Data [0]

= Byte 0 of mapped input data

According to the I/O data widths of the modules in the example station (see

Table 63: Example station ),

the I/O data mapping for the example station is the following:

Module

GW

0

1

2

3

4

5

BL67-GW-EN-IP

BL67-2AI-I

BL67-4DI-P

BL67-8DI-PD

BL67-2AI-TC

BL67-8XSG-PD

BL67-4DI-PD

I/O data word in RSLogix

– Input data:

A

BL67:I.Data [0]; Status Word

– Output data:

BL67:O.Data [0]; Command Word

– Input data:

BL67:I.Data [1]; Channel 0


– Input data:

BL67:I.Data [3]; Bits 0 to 3 for channels 0 to 3.

– Input data:


– Input data:

BL67:I.Data [4]; Channel 0:

BL67:I.Data [5]; Channel 1:

– Input data


– Output data:

BL67:O.Data [1]; Bits 0 to 7, for channels 0 to 7.

– Input data



6-23


Module

6 BL67-8DI-P

7 BL67-8DO-0.5A-P

8 BL67-2AO-V

9 BL67-2AI-I

10 BL67-1RS232

I/O data word in RSLogix

– Input data



– Output data:

BL67:O.Data [1]; Bits 8 to 15, for channels 0 to 7.

– Output data:

BL67:O.Data [2]; Channel 0

BL67:O.Data [3]; Channel 1

– Input data:



– Input data:

BL67:I.Data [10 - 13]

– Output data:

BL67:O.Data [4 - 7]

6-24



6.7.1

Mapping report via I/O-ASSISTANT

An EtherNet/IP I/O mapping report can be generated for each individual station by means of the software tool I/O-ASSISTANT.

Figure 60:

I/O mapping report in software tool

I/O-ASSISTANT


6-25


6.8

Example for process data access

6.8.1

Setting outputs at BL67-8DO-0.5A-P

Example:

To set the outputs "0", "3" and "6" at module no. 7 in the example station (BL67-8DO-0.5A-P), bit 8, bit

11 and bit 14 in output data word 1 (BL67:O.Data [1]) have to be set (see above

Table 64: Data mapping for the example station

).

Figure 61:

Setting outputs at module no. 7

6-26


7 Guidelines for station planning

7.1

7.1.1

7.2

7.3

7.3.1

7.4

7.5

7.6

Module arrangement ........................................................................................................................ 2

Random module arrangement.............................................................................................................. 2

Complete planning ........................................................................................................................... 3

Maximum system extension ............................................................................................................. 4

Creating potential groups ..................................................................................................................... 4

Plugging and pulling electronic modules ......................................................................................... 6

Extending an existing station ........................................................................................................... 6

Firmware download .......................................................................................................................... 6


7-1

Guidelines for station planning

7.1

Module arrangement

7.1.1

Random module arrangement

The arrangement of the I/O-modules within a BL67 station can basically be chosen at will.

Nevertheless, it can be useful with some applications to group certain modules together.

7-2


Complete planning

7.2

Complete planning

The planning of a BL67 station should be thorough to avoid faults and increase operating reliability.

Attention

If there are more than two empty slots next to one another, the communication is interrupted to all following BL67 modules.


7-3


7.3

Maximum system extension

A BL67 station can consist of a gateway and a maximum of 32 modules (equivalent to 1 m station length).

The following overview shows the maximum number of channels possible under these conditions:

The entire station is made up of the respective channel type only.

Table 65:

Maximum system extension

Module type

BL67-4DI-P

Alimited due to the

high current consumption

(max. 1,5 A) on the module bus

(5 V)

BL67-8DI-P

BL67-4DO-xA-P

BL67-8DO-xA-P

BL67-16DO-0.1A-P

BL67-4DI4DO-PD

BL67-8XSG-PD

BL67-2AI-x

BL67-2AI-PT

BL67-2AI-TC

BL67-4AI-V/I

BL67-2AO-I

BL67-2AO-V

BL67-1RS232

BL67-1RS485/422

BL67-1SSI

BL67-1CVI

128

64

50

A

10

A

256

64

64

64

128

256

512

256

maximum number

Channels Modules

128

256

32

32

32

32

32

32

21

A

26

A

32

21

26

32

A

A

32

32

25

A

10

A

32

32

32

32

Attention

Ensure that a sufficient number of Power Feeding modules are used if the system is extended to its maximum.

Note

If the system limits are exceeded, the software I/O-ASSISTANT generates an error message when the user activates the command “Station

→ Verify“.

7-4


Maximum system extension

7.3.1

Creating potential groups

Power Feeding modules can be used to create potential groups. The potential isolation of potential groups to the left of the respective power distribution modules is provided by the base modules.


7-5


7.4

Plugging and pulling electronic modules

BL67 enables the pulling and plugging of electronic modules without having to disconnect the field wiring. The BL67 station remains in operation if an electronic module is pulled.

The voltage and current supplies as well as the protective earth connections are not interrupted.

Attention

If the field and system supplies remain connected when electronic modules are plugged or pulled, short interruptions to the module bus communications can occur in the BL67 station.

This can lead to undefined statuses of individual inputs and outputs of different modules.

7.5

Extending an existing station

Attention

Please note that extensions to the station (mounting further modules) should be carried out only when the station is in a voltage-free state.

7.6

Firmware download

Firmware can be downloaded via the service interface on the gateway using the software tool I/O-

ASSISTANT. More information is available in the program’s online help.

Attention

The station should be disconnected from the fieldbus when downloading.

Firmware must be downloaded by authorized personnel only.

The field level must be isolated.

7-6


8 Guidelines for electrical installation

8.3

8.3.1

8.3.2

8.3.3

8.3.4

8.3.5

8.4

8.5

8.5.1

8.5.2

8.1

8.1.1

8.1.2

8.1.3

8.1.4

8.1.5

8.2

8.2.1

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

General ................................................................................................................................................. 2

Cable routing ........................................................................................................................................ 2

Cable routing inside and outside of cabinets ....................................................................................... 2

– Cable routing outside buildings......................................................................................................... 2

Lightning protection.............................................................................................................................. 3

Transmission media.............................................................................................................................. 3

Potential relationships ..................................................................................................................... 4

General ................................................................................................................................................. 4

Electromagnetic compatibility (EMC) ............................................................................................... 5

Ensuring Electromagnetic Compatibility .............................................................................................. 5

Grounding of inactive metal components ............................................................................................ 5

PE connection ...................................................................................................................................... 5

Earth-free operation.............................................................................................................................. 5

Mounting rails ....................................................................................................................................... 5

Shielding of cables ............................................................................................................................ 7

Potential compensation.................................................................................................................... 8

Switching inductive loads..................................................................................................................... 8

Protection against Electrostatic Discharge (ESD ................................................................................. 8


8-1

Guidelines for electrical installation

8.1

General notes

8.1.1

General

Cables should be grouped together, for example: signal cables, data cables, heavy current cables, power supply cables.

Heavy current cables and signal or data cables should always be routed in separate cable ducts or bundles. Signal and data cables must always be routed as close as possible to ground potential surfaces

(for example support bars, cabinet sides etc.).

8.1.2

Cable routing

Correct cable routing prevents or suppresses the reciprocal influencing of parallel routed cables.

8.1.3

Cable routing inside and outside of cabinets

To ensure EMC-compatible cable routing, the cables should be grouped as follows:

Various types of cables within the groups can be routed together in bundles or in cable ducts.

Group 1:

shielded bus and data cables

shielded analog cables

unshielded cables for DC voltage

≤ 60 V

unshielded cables for AC voltage

≤ 25 V

Group 2:

unshielded cables for DC voltage > 60 V and

≤ 400 V

unshielded cables for AC voltage > 25 V and

≤ 400 V

Group 3:

unshielded cables for DC and AC voltages > 400 V

The following group combination can be routed only in separate bundles or separate cable ducts (no minimum distance apart):

Group 1/group 2

The group combinations:

Group 1/group 3 and group 2/group 3

must be routed in separate cable ducts with a minimum distance of 10 cm apart. This is equally valid for inside buildings as well as for inside and outside of switchgear cabinets.

Cable routing outside buildings

Outside of buildings, cables should be routed in closed (where possible), cage-type cable ducts made of metal. The cable duct joints must be electrically connected and the cable ducts must be earthed.

Danger

Observe all valid guidelines concerning internal and external lightning protection and grounding specifications when routing cables outside of buildings.

8-2


General notes

8.1.4

Lightning protection

The cables must be routed in double-grounded metal piping or in reinforced concrete cable ducts.

Signal cables must be protected against overvoltage by varistors or inert-gas filled overvoltage arrestors. Varistors and overvoltage arrestors must be installed at the point where the cables enter the building.

8.1.5

Transmission media

For a communication via Ethernet, different transmission media can be used:

coaxial cable (10Base5)

optical fibre (10BaseF)

twisted two-wire cable (10BaseT) with shielding (STP) or without shielding (UTP).

Note

Turck offers a variety of cable types for fieldbus lines as premoulded or bulk cables with different connectors.

The ordering information for the available cable types can be found in the BL67 catalog.


8-3


8.2

Potential relationships

8.2.1

General

The potential relationship of a EtherNet/IP system realized with BL67 modules is characterized by the following:

The system supply of gateway and I/O-modules as well as the field supply are realized via one power feed at the gateway.

All BL67 modules (gateway, Power Feeding and I/O-modules), are connected capacitively via base modules to the mounting rails.

The block diagram shows the arrangement of a typical BL67 station.

Figure 62:

Block diagram of a BL67 station

fieldbus gateway

5 V

I/O-module I/O-module power feeding module bus

I >

V i

V o

GND

PE

I >

PE logic

V i

GND V o

PE PE V i

GND V o

2 O

2 I

8-4


Electromagnetic compatibility (EMC)

8.3

Electromagnetic compatibility (EMC)

BL67 products comply in full with the requirements pertaining to EMC regulations.

Nevertheless, an EMC plan should be made before installation. Hereby, all potential electromechanical sources of interference should be considered such as galvanic, inductive and capacitive couplings as well as radiation couplings.

8.3.1

Ensuring Electromagnetic Compatibility

The EMC of BL67 modules is guaranteed when the following basic rules are adhered to:

Correct and large surface grounding of inactive metal components.

Correct shielding of cables and devices.

Proper cable routing – correct wiring.

Creation of a standard reference potential and grounding of all electrically operated devices.

Special EMC measures for special applications.

8.3.2

Grounding of inactive metal components

All inactive metal components (for example: switchgear cabinets, switchgear cabinet doors, supporting bars, mounting plates, tophat rails, etc.) must be connected to one another over a large surface area and with a low impedance (grounding). This guarantees a standardized reference potential area for all control elements and reduces the influence of coupled disturbances.

In the areas of screw connections, the painted, anodized or isolated metal components must be freed of the isolating layer. Protect the points of contact against rust.

Connect all free moving groundable components (cabinet doors, separate mounting plates, etc.) by using short bonding straps to large surface areas.

Avoid the use of aluminum components, as its quick oxidizing properties make it unsuitable for grounding.

Danger

The grounding must never – including cases of error – take on a dangerous touch potential.

For this reason, always protect the ground potential with a protective cable.

8.3.3

PE connection

A central connection must be established between ground and PE connection (protective earth).

8.3.4

Earth-free operation

Observe all relevant safety regulations when operating an earthfree system.


8-5


8.3.5

Mounting rails

All mounting rails must be mounted onto the mounting plate with a low impedance, over a large surface area, and must be correctly earthed.

Figure 63:

Mounting options

ATS 35

BMounting rail

CMounting plate

DTS 35

Mount the mounting rails over a large surface area and with a low impedance to the support system using screws or rivets.

Remove the isolating layer from all painted, anodized or isolated metal components at the connection point. Protect the connection point against corrosion (for example with grease; caution: use only suitable grease).

8-6


Shielding of cables

8.4

Shielding of cables

Shielding is used to prevent interference from voltages and the radiation of interference fields by cables. Therefore, use only shielded cables with shielding braids made from good conducting materials

(copper or aluminum) with a minimum degree of coverage of 80 %.

The cable shield should always be connected to both sides of the respective reference potential (if no exception is made, for example, such as high-resistant, symmetrical, analog signal cables). Only then can the cable shield attain the best results possible against electrical and magnetic fields.

A one-sided shield connection merely achieves an isolation against electrical fields.

Attention

When installing, please pay attention to the following...

– the shield should be connected immediately when entering the

– system,

– the shield connection to the shield rail should be of low

– impedance,

– the stripped cable-ends are to be kept as short as possible,

– the cable shield is not to be used as a bonding conductor.

If the data cable is connected via a SUB-D connector, the shielding should never be connected via pin 1, but to the mass collar of the plug-in connector.

The insulation of the shielded data-cable should be stripped and connected to the shield rail when the system is not in operation. The connection and securing of the shield should be made using metal shield clamps. The shield clamps must enclose the shielding braid and in so doing create a large surface contact area. The shield rail must have a low impedance (for example, fixing points of 10 to 20 cm apart) and be connected to a reference potential area.

The cable shield should not be severed, but routed further within the system (for example, to the switchgear cabinet), right up to the interface connection.

Note

Should it not be possible to ground the shield on both sides due to switching arrangements or device specific reasons, then it is possible to route the second cable shield side to the local reference potential via a capacitor (short connection distances). If necessary, a varistor or resistor can be connected parallel to the capacitor, to prevent disruptive discharges when interference pulses occur.

A further possibility is a double-shielded cable (galvanically separated), whereby the innermost shield is connected on one side and the outermost shield is connected on both sides.


8-7


8.5

Potential compensation

Potential differences can occur between installation components that are in separate areas and these

are fed by different supplies,

have double-sided conductor shields which are grounded on different installation components.

A potential-compensation cable must be routed to the potential compensation.

Danger

Never use the shield as a potential compensation.

A potential compensation cable must have the following characteristics:

Low impedance. In the case of compensation cables that are routed on both sides, the compensation line impedance must be considerably smaller than that of the shield connection

(max. 10 % of shield connection impedance).

Should the length of the compensation cable be less than 200 m, then its cross-section must be at least 16 mm

2

/ 0.025 inch

2

. If the cable length is greater than 200 m, then a cross-section of at least

25 mm

2

/ 0.039 inch

2 is required.

The compensation cable must be made of copper or zinc coated steel.

The compensation cable must be connected to the protective conductor over a large surface area and must be protected against corrosion.

Compensation cables and data cables should be routed as close together as possible, meaning the enclosed area should be kept as small as possible.

8.5.1

Switching inductive loads

In the case of inductive loads, a protective circuit on the load is recommended.

8.5.2

Protection against Electrostatic Discharge (ESD

Attention

Electronic modules and base modules are at risk from electrostatic discharge when disassembled. Avoid touching the bus connections with bare fingers as this can lead to ESD damage.

8-8


9 Appendix

9.1

Nominal current consumption of modules at Ethernet ................................................................... 2


9-1

Appendix

9.1

Nominal current consumption of modules at Ethernet

Current consumptions on 24 V DC

Table 66: nominal current consumptions of the modules at Ethernet

Module

BL67-GW-EN-IP

Power supply modules

BL67-PF-24VDC

Digital input modules

BL67-4DI-P

BL67-8DI-P

BL67-4DI-PD

BL67-8DI-PD

BL67-4DI-N

BL67-8DI-N

Analog input modules

BL67-2AI-I

BL67-2AI-V

BL67-2AI-PT

BL67-2AI-TC

Digital output modules

BL67-4DO-0.5A-P

BL67-4DO-2A-P

BL67-8DO-0.5A-P

BL67-4DO-2A-N

BL67-8DO-0.5A-N

BL67-16DO-0.1A-P

Analog output modules

BL67-2AO-I

BL67-2AO-V

Digital combi modules

BL67-4DI/4DO-PD

BL867-8XSG-PD

≤ 9 mA

≤ 9 mA

≤ 9 mA

≤ 35 mA

≤ 35 mA

≤ 8 mA

≤ 8 mA

≤ 10 mA

≤ 10 mA

≤ 13 mA

≤ 10 mA

≤ 9 mA

≤ 9 mA

≤ 9 mA

≤ 24 mA

≤ 24 mA

≤ 9 mA

≤ 12 mA

≤ 17 mA

≤ 35 mA

≤ 35 mA

9-2


Nominal current consumption of modules at Ethernet

Table 66: nominal current consumptions of the modules at Ethernet

Module

Technology modules

BL67-1RS232

BL67-1RS485/422

BL67-1SSI

BL67-1CVI

Current consumptions on 24 V DC

≤ 28 mA

≤ 20 mA

≤ 32 mA

≤ 24 mA

Note

Please find any information about the bus-independent, module specific current consumptions in the manual "BL67- I/O-modules" (TURCK-Documentation No.: German

D300572/ English D300527).


9-3

Appendix

9-4


10 Glossary

A

B

Acknowledge

Acknowledgment of a signal received.

Active metal component

Conductor or conducting component that is electrically live during operation.

Address

Identification number of, e.g. a memory position, a system or a module within a network.

Addressing

Allocation or setting of an address, e. g. for a module in a network.

ARP

Used to definitely allocate the hardware addresses (MAC-IDs) assigned worldwide to the IP addresses of the network clients via internal tables.

Analog

Infinitely variable value, e. g. voltage. The value of an analog signal can take on any value, within certain limits.

Automation device

A device connected to a technical process with inputs and outputs for control. Programmable logic controllers

(PLC) are a special group of automation devices.

Baud

Baud is a measure for the transmission speed of data. 1 Baud corresponds to the transmission of one bit per second (bit/s).

Baud rate

Unit of measurement for measuring data transmission speeds in bit/s.

Bidirectional

Working in both directions.

Bonding strap

Flexible conductor, normally braided, that joins inactive components, e. g. the door of a switchgear cabinet to the cabinet main body.

Bus

Bus system for data exchange, e. g. between CPU, memory and I/O levels. A bus can consist of several parallel cables for data transmission, addressing, control and power supply.

Bus cycle time

Time required for a master to serve all slaves or stations in a bus system, i. e. reading inputs and writing outputs.

Bus line

Smallest unit connected to a bus, consisting of a PLC, a coupling element for modules on the bus and a module.


10-1

Glossary

C

D

E

Bus system

All units which communicate with one another via a bus.

Capacitive coupling

Electrical capacitive couplings occur between cables with different potentials. Typical sources of interference are, for example, parallel-routed signal cables, contactors and electrostatic discharges.

Check-back interface

The check-back interface is the interface from the counter module to the internal module bus. The bits and bytes are converted by the gateway from the respective type of communication applicable to the fieldbus in to the module-specific bits and bytes.

Coding elements

Two-piece element for the unambiguous assignment of electronic and base modules.

Configuration

Systematic arrangement of the I/O-modules of a station.

Control interface

The control interface is the interface from the internal module bus to the counter module. The commands and signals directed to the counter module are converted by the gateway from the respective type of communication applicable to the fieldbus in to the module-specific bits and bytes.

CPU

Central Processing Unit. Central unit for electronic data processing, the processing core of the PC.

DHCP

Client-Server-protocol which reduces the effort of assigning IP addresses or other parameters. Serves for dynamic and automatic configuration of devices.

Digital

A value (e. g. a voltage) which can adopt only certain statuses within a finite set, mostly defined as 0 and 1.

DIN

German acronym for German Industrial Standard.

EDS

Electronic Device Data Sheet which contains standardized DeviceNet station descriptions. They simplify the planning of the DeviceNet nodes.

EIA

Electronic Industries Association – association of electrical companies in the United States.

Electrical components

All objects that produce, convert, transmit, distribute or utilize electrical power (e. g. conductors, cable, machines, control devices).

EMC

Electromagnetic compatibility – the ability of an electrical part to operate in a specific environment without fault and without exerting a negative influence on its environment.

10-2


F

G

H

I

EN

German acronym for European Standard.

ESD

Electrostatic Discharge.

Field power supply

Voltage supply for devices in the field as well as the signal voltage.

Fieldbus

Data network on sensor/actuator level. A fieldbus connects the equipment on the field level. Characteristics of a fieldbus are a high transmission security and real-time behavior.

Force Mode

Software mode which enables the user to set his plant to a required state by forcing certain variables on the input and output modules.

GND

Abbreviation of ground (potential "0").

Ground

Expression used in electrical engineering to describe an area whose electrical potential is equal to zero at any given point. In neutral grounding devices, the potential is not necessarily zero, and one speaks of the ground reference.

Ground connection

One or more components that have a good and direct contact to earth.

Ground reference

Potential of ground in a neutral grounding device. Unlike earth whose potential is always zero, it may have a potential other than zero.

Hexadecimal

System of representing numbers in base 16 with the digits 0... 9, and further with the letters A, B, C, D, E and F.

Hysteresis

A sensor can get caught up at a certain point, and then "waver" at this position. This condition results in the counter content fluctuating around a given value. Should a reference value be within this fluctuating range, then the relevant output would be turned on and off in rhythm with the fluctuating signal.

I/O

Input/output.

Impedance

Total effective resistance that a component or circuit has for an alternating current at a specific frequency.

Inactive metal components

Conductive components that cannot be touched and are electrically isolated from active metal components by insulation, but can adopt voltage in the event of a fault.


10-3

Glossary

L

M

Inductive coupling

Magnetic inductive couplings occur between two cables through which an electrical current is flowing. The magnetic effect caused by the electrical currents induces an interference voltage. Typical sources of interference are for example, transformers, motors, parallel-routed network and HF signal cables.

Intelligent modules

Intelligent modules are modules with an internal memory, able to transmit certain commands (e. g. substitute values and others).

IP

Abbreviation for Internet-Protocol, protocol for the packet-oriented and connectionless transport of data packets from a transmitter to a receiver crossing different networks.

Lightning protection

All measures taken to protect a system from damage due to overvoltages caused by lightning strike.

Low impedance connection

Connection with a low AC impedance.

LSB

Least Significant bit

Mass

All interconnected inactive components that do not take on a dangerous touch potential in the case of a fault.

Master

Station in a bus system that controls the communication between the other stations.

Module bus

The module bus is the internal bus in a station. The modules communicate with the gateway via the module bus which is independent of the fieldbus.

MSB

Most Significant bit

Ping

Implementation of an echo-protocol, used for testing whether a particular host is operating properly and is reachable on the network from the testing host.

PLC

Programmable Logic Controller.

Potential compensation

The alignment of electrical levels of electrical components and external conductive components by means of an electrical connection.

Potential free

Galvanic isolation of the reference potentials in I/O-modules of the control and load circuits.

10-4


R

S

Potential linked

Electrical connection of the reference potentials in I/O-modules of the control and load circuits.

Protective earth

Electrical conductor for protection against dangerous shock currents. Generally represented by PE (protective earth).

Radiation coupling

A radiation coupling appears when an electromagnetic wave hits a conductive structure. Voltages and currents are induced by the collision. Typical sources of interference are for example, sparking gaps (spark plugs, commutators from electric motors) and transmitters (e. g. radio), that are operated near to conducting structures.

Reaction time

The time required in a bus system between a reading operation being sent and the receipt of an answer. It is the time required by an input module to change a signal at its input until the signal is sent to the bus system.

Reference potential

Potential from which all voltages of connected circuits are viewed and/or measured.

Repeater

Amplifier for signals transmitted via a bus.

Root-connecting

Creating a new potential group using a power distribution module. This allows sensors and loads to be supplied individually.

RS 485

Serial interface in accordance with EIA standards, for fast data transmission via multiple transmitters.

Serial

Type of information transmission, by which data is transmitted bit by bit via a cable.

Setting parameters

Setting parameters of individual stations on the bus and their modules in the configuration software of the master.

Shield

Conductive screen of cables, enclosures and cabinets.

Shielding

Description of all measures and devices used to join installation components to the shield.

Short-circuit proof

Characteristic of electrical components. A short-circuit proof part withstands thermal and dynamic loads which can occur at its place of installation due to a short circuit.

Station

A functional unit or I/O components consisting of a number of elements.


10-5

Glossary

T

U

TCP

Abbreviation for Transmission Control Protocol, connection-oriented transport protocol within the Internet protocol suite. Certain error detection mechanisms (i.e. acknowledgements, time-out monitoring) can guarantee a safe and error free data transport.

Terminating resistance

Resistor on both ends of a bus cable used to prevent interfering signal reflections and which provides bus cable matching. Terminating resistors must always be the last component at the end of a bus segment.

To ground

Connection of a conductive component with the grounding connection via a grounding installation.

Topology

Geometrical structure of a network or the circuitry arrangement.

UDP

Abbreviation for User Datagram Protocol. UDP is an transport protocol for the connectionless data between

Ethernet hosts.

Unidirectional

Working in one direction.

10-6


11 Index

A

addressing

.................................................................... 4-11

APR (Address Resolution Protocol)

............................... 3-6

B

base modules

................................................................. 2-5

basic concept

................................................................. 2-2

C

classes

–analog input current modules

.................................. 5-42

–analog input RTD modules

........................................ 5-46

–analog input THERMO modules

................................ 5-50

–analog input voltage modules

.................................. 5-38

–analog output current modules

................................ 5-44

–analog output voltage modules

............................... 5-40

–analog versatile modules

.......................................... 5-79

–Assembly Object

........................................................ 5-12

–Connection Manager Object

..................................... 5-16

–CVI module class

........................................................ 5-82

–digital input modules

................................................ 5-34

–digital output modules

.............................................. 5-36

–digital versatile modules

........................................... 5-75

–Ethernet Link Object

.................................................. 5-21

–Ethernet/IP standard

.................................................... 5-5

–Identity Object

............................................................. 5-6

–Message Router Object

............................................... 5-7

–Port Object

................................................................. 5-16

–power supply modules

.............................................. 5-32

–process data

............................................................... 5-30

–RFID modules

............................................................. 5-85

–RS232 modules

.......................................................... 5-53

–RS4xx modules

........................................................... 5-60

–SSI modules

................................................................ 5-67

–TCP/IP Interface Object

.............................................. 5-17

–terminal slots

.............................................................. 5-28

–VSC-Vendor Specific Classes

...................................... 5-23

communications profile

................................................. 5-3

Consumed Data

........................................................... 5-14

Control word

............................................ 4-23

,

5-14

,

5-15

COS I/O connection

........................................................ 5-4

Cyclic I/O connection

..................................................... 5-4

D

Data mapping

.............................................................. 5-14

E

earth-free operation

....................................................... 8-5

electromagnetic compatibility

...................................... 8-5

electronic modules

........................................................ 2-4

electrostatic discharge

................................................... 8-8

EMC

................................................................................. 8-5

end plate

........................................................................ 2-5

ESD, electrostatic discharge

.......................................... 8-8

Ethernet

.......................................................................... 3-4

–IP address

..................................................................... 3-4

–MAC-ID

.......................................................................... 3-4

–manufacturer identifier

................................................ 3-4

–netmask

........................................................................ 3-4

–network classes

............................................................ 3-4

–subnet ID

...................................................................... 3-4

explicit messages

............................................................ 5-4

F

firmware download

........................................................ 7-6

flexibility

.......................................................................... 2-2

G

gateway

–addressing

.................................................................. 4-11

–BOOTP-mode

.............................................................. 4-13

–DHCP-mode

................................................................ 4-14

–PGM-mode

.................................................................. 4-15

–rotary-mode

..................................................... 4-12

,

6-12

–structure

....................................................................... 4-4

–technical data

............................................................... 4-4

gateways

......................................................................... 2-3

I

I/O messages

................................................................... 5-3

inductive loads, protective circuit

................................. 8-8

input assembly instance

............................................... 5-13

Instance 101

.................................................................. 5-13

Instance 102

.................................................................. 5-13

Instance 103

.................................................................. 5-13

Instance 104

.................................................................. 5-13

IP (Internet Protocol)

...................................................... 3-2

IP address

........................................................................ 3-4

–PC

.................................................................................. 6-4

L

LED behavior

................................................................. 4-19

LEDs

–Diagnostic Messages

.................................................. 4-19

–Status Indicators

......................................................... 4-19

M

module arrangement

..................................................... 7-2

mounting rail

.................................................................. 8-6

N

network configuration

................................................... 6-1

O

output assembly instance

............................................ 5-13

P

PE connection

................................................................. 8-5

pin assignment

–field bus connection

.................................................... 4-7

–power supply

................................................................ 4-7

planning

.......................................................................... 7-3


11-1

Index

plugging, electronic modules

....................................... 7-6

potential group

.............................................................. 7-5

potential relationships

................................................... 8-4

potential-compensation cable

...................................... 8-8

power feeding modules

................................................. 2-4

prescribed use

................................................................ 1-3

process data

................................................................. 5-13

Produced Data

............................................................. 5-14

protection class IP67

.............................................. 2-2

,

2-5

pulling, electronic modules

........................................... 7-6

R

RSLinx

........................................................................... 6-15

S

service interface

............................................................. 4-8

shielding

......................................................................... 8-7

station extension

............................................................ 7-6

status information

........................................................ 5-13

Status word

.............................................. 4-23

,

5-14

,

5-15

symbols

.......................................................................... 1-4

system extension, maximum

......................................... 7-4

T

TCP (Transmission Control Protocol)

............................. 3-2

TCP/IP host

..................................................................... 3-4

transport, appropriate

................................................... 1-3

U

UCMM

............................................................................. 5-4

W

WIN 2000

........................................................................ 6-4

WIN NT

............................................................................ 6-6

WIN XP

............................................................................ 6-4

11-2


www.turck.com

Hans Turck GmbH & Co. KG

45472 Mülheim an der Ruhr

Germany

Witzlebenstraße 7

Tel. +49 (0) 208 4952-0

Fax +49 (0) 208 4952-264

E-Mail [email protected]

Internet www.turck.com

Turck BL67 - Ethernet/IP Instructions for use

BL67 –

USER MANUAL

FOR

ETHERNET/IP

Warning!

Before commencing the installation

Table of Contents

1 About this manual

2 BL67 philosophy

3 EtherNet/IP

4 Technical features

5 Implementation of EtherNet/IP

6 Application example: BL67 gateway at Allen Bradley PLC

7 Guidelines for station planning

8 Guidelines for electrical installation

9 Appendix

10 Glossary

11 Index

Index

www.turck.com

Related manuals

Table of contents

Turck BL67 - Ethernet/IP Instructions for use

BL67 –

USER MANUAL

FOR

ETHERNET/IP

Warning!

Before commencing the installation

Table of Contents

1 About this manual

2 BL67 philosophy

3 EtherNet/IP

4 Technical features

5 Implementation of EtherNet/IP

6 Application example: BL67 gateway at Allen Bradley PLC

7 Guidelines for station planning

8 Guidelines for electrical installation

9 Appendix

10 Glossary

11 Index

Index

www.turck.com

Related manuals

BL67-PG-EN-IP

BL67-PG-EN

BL67-GW-EN-PN

Opus One

C0911

BL67 I/O Modules

turck

BL67-PG-DP

AL1020

BL67-GW-EN

Table of contents