12.2.1 Ethernet-Cabling for TBEN-L in FSU Applications101
12.2.2 FSU in TBEN-L101
12.3MRP (Media Redundancy Protocol)102
12.4PROFINET-diagnostics103
12.4.1 TBEN-Lx-16DIP/TBEN-L4-16DIN – Diagnostic Data Mapping103
12.4.2 TBEN-Lx-16DOP/TBEN-L4-16DON – Diagnostic Data Mapping104
12.4.3 TBEN-Lx-8DIP-8DOP – Diagnostic Data Mapping105
12.4.4 TBEN-Lx-16DXP/TBEN-L4-16DXN – Diagnostic Data Mapping106
12.5Parameters107
12.5.1 General Device Parameters (turck-tben)107
12.5.2 Parameters for I/O Channels 108
12.6Description of User Data for Acyclic Services109
12.6.1 Description of the Acyclic Device User Data109
12.6.2 Description of the Acyclic I/O-Channel User Data110
13The Web Server 111
13.1Safety in the Web Server111
13.1.1 Web Server Logout111
13.2IP Address111
13.3Start Page of the Web Server (Home)112
13.4Station Diagnostics113
4
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 7
13.5Ethernet Statistics114
13.6Event Log115
13.7EtherNet/IP™/Modbus TCP Memory Map116
13.8Links117
13.9 Login/Password118
13.10 Change Admin Password119
13.11 Network Configuration120
13.11.1Change Network Parameters (Port Settings, IP Address, etc.)120
13.12 Station Configuration122
13.12.1Configuring the Ethernet Interface122
13.13 Parameters123
13.13.1Parameterization of the In-/ Outputs123
13.14 Using Mobile Devices124
13.15 Web Server Logout124
13.16 Deactivating the Web Server124
14Access via Turck DTMs in PACTware™ 125
14.1General125
14.1.1 Address Setting via DTM125
2017/06
5
Page 8
6
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 9
1About these Instructions
These operating instructions describe the structure, functions and the use of the product and will
help you to operate the product as intended. Read these instructions carefully before using the
product. This is to avoid possible damage to persons, property or the device. Retain the instructions
for future use during the service life of the product. If the product is passed on, pass on these instructions as well.
1.1Target Groups
These instructions are aimed at qualified personnel and must be carefully read by anyone mounting, commissioning, operating, maintaining, dismantling or disposing of the device.
1.2Explanation of Symbols
The following symbols are used in these instructions:
DANGER!
DANGER indicates an immediately dangerous situation, with high risk, the death or severe
injury, if not avoided.
WARNING!
WARNING indicates a potentially dangerous situation with medium risk, the death or
severe injury, if not avoided.
ATTENTION!
ATTENTION indicates a situation that may lead to property damage, if it is not avoided.
NOTE
In NOTES you find tips, recommendations and important information. The notes facilitate
work, provide more information on specific actions and help to avoid overtime by not following the correct procedure.
CALL TO ACTION
This symbol identifies steps that the user has to perform.
RESULTS OF ACTION
This symbol identifies relevant results of steps
2017/06
7
Page 10
About these Instructions
1.3Additional Documents
The following additional documents are available online at www.turck.com:
Data sheet
Quick Start Guide
User manual TBEN-L1
1.4Feedback about these Instructions
We make every effort to ensure that these instructions are as informative and as clear as possible. If
you have any suggestions for improving the design or if some information is missing in the document, please send your suggestions to
techdoc@turck.com.
8
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 11
2Notes on the Product
2.1Product Identification
These instructions apply to the compact multiprotocol I/O modules for Ethernet TBEN-L4 and
TBEN-L5 (TBEN-Lx).
2.1.1Scope of Delivery
TBEN-L4 or respectively TBEN-L5 device
Closure caps for 7/8'' connectors
Closure caps for M12 female connectors
Quick Start Guide
2.1.2Legal Requirements
The device falls under the following EU directives:
2014/30/EU (electromagnetic compatibility)
2.1.3Manufacturer and Service
Hans Turck GmbH & Co. KG
Witzlebenstraße 7
45472 Muelheim an der Ruhr
Germany
Turck supports you with your projects, from initial analysis to the commissioning of your application. The Turck product database contains software tools for programming, configuration or commissioning, data sheets and CAD files in numerous export formats. You can access the product database at the following address:
Should you have any further questions, please contact the sales and service team in Germany under
the following telephone numbers:
Sales: +49 208 4952-380
Technology: +49 208 4952-390
Internet:
Outside Germany, please contact your local Turck representative.
www.turck.com/support
www.turck.de/products
2017/06
9
Page 12
Notes on the Product
10
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 13
3For Your Safety
The product is designed according to state-of-the-art technology. However, residual risks still exist.
Observe the following warnings and safety notices to prevent damage to persons and property.
Turck accepts no liability for damage caused by failure to observe these warning and safety notices.
3.1Intended Use
The devices are only intended for use in industrial applications.
Thanks to the Turck multiprotocol technology, the compact multiprotocol I/O modules for Ethernet
can be operated in the three Ethernet protocols PROFINET, EtherNet/IP™ and Modbus TCP. The
modules detect the bus protocol automatically during the start-up.
The TBEN-Lx devices provide eight M12 female connectors for the connection of up to 16 digital
sensors or actuators.
The devices may only be used as described in this manual. Any other usage shall be considered
improper and Turck shall not be held liable for any resulting damage.
3.2General Safety Instructions
The device may only be assembled, installed, operated and maintained by professionally trained
personnel.
The device may only be used in accordance with applicable national and international regula-
tions, standards and laws.
The device only meets the EMC requirements for industrial areas and is not suitable for use in res-
idential areas.
2017/06
11
Page 14
For Your Safety
12
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 15
4Product Description
218
230.5
C4C5C6C7
6.3
38.8
60.4
C0C1C2C3
24
30.2
X2
X1
P2
P1
The devices are designed in a fully encapsulated housing with degree of protection IP65/IP67/
IP69K. For the connection of digital sensors and actuators, the devices provide eight or respectively
sixteen input or output channels or respectively sixteen freely configurable digital I/O channels
which can be used as in- or output. The terminals for the digital I/Os are M12 sockets. Two M12 sockets are provided for the Ethernet connection. The power supply connectors are designed as 4-pole
(TBEN-L4) or 5-pole (TBEN-L5) 7/8" connectors.
4.1Device Overview
Fig. 1: Size
4.1.1Dimensions
The devices are provided with multi-color LEDs for displaying information:
Supply voltage
Group and bus errors
Status
Diagnostics
2017/06
13
Page 16
Product Description
4.2Properties and Features
Multiprotocol: EtherNet/IP™-Device, Modbus TCP-Slave, or PROFINET-Device
Channel-related short-circuit diagnosis of outputs
Slot-related short-circuit diagnosis of the sensor/actuator supply voltage
Voltage supply via 7/8'' connectors
–
TBEN-L5: 5-pole
– TBEN-L4: 4-pole
Two 4-pole M12-connectors for Ethernet
Integrated Ethernet-switch for building up a line-topology.
Transmission speed 10 Mbps/100 Mbps
Integrated web server
LED displays and diagnostics
Fibre-glass reinforced housing
Shock and vibration tested
Fully potted module electronics
Degree of protection IP65/IP67/IP69K
Programmable via ARGEE/FLC
14
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 17
4.3Protocols
Multi Protocol Functionality
The compact I/O-devices of the TBEN-L product line combine the three Ethernet-protocols
Modbus TCP (description page 49 ff.),
EtherNet/IP™ (description page 65) and
PROFINET (description page 99 ff.)
in one device.
A multi-protocol device can be operated without intervention of the user (which means, without
changes in the parameterization) in all of the three Ethernet protocols mentioned.
During the start-up, after a power-on, the module runs in "snooping" mode and detects the Ethernet protocol which requests a link connection by listening the traffic.
If a protocol is detected, the device is set automatically to the respective protocol. After this an
access to the device from other protocols is read-only.
4.3.1Explicit/Manual Protocol Selection
The protocol can also be determined manually. This skips the snooping-phase and the device is permanently set to the selected protocol. An access to the device from other protocols is read-only.
The explicit protocol selection allows thus an additional locking mechanism.
4.3.2Protocol Dependent Functions
PROFINET
Fast Start-UP (FSU), see FSU - Fast Start-Up (prioritized startup), page 101
Topology discovery
Address assignment via LLDP
MRP, see MRP (Media Redundancy Protocol), page 102
EtherNet/IP™
QuickConnect (QC), see QuickConnect in TBEN, page 68
DLR (Device Level Ring), see Device Level Ring (DLR), page 69
2017/06
15
Page 18
Product Description
16
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 19
5Configuring
This chapter describes the configuration of the Ethernet-connection.
Details concerning the necessary protocol-specific configurations (Modbus TCP, EtherNet/IP™,
PROFINET) can be found in the respective sub-chapters
5.1Device Configuration Files
The actual device configuration files for the devices can be downloaded from the Turck home page
www.turck.com.
Information about the protocol-specific files can be found in the respective sub-chapters.
Setting the address mode is done through the 3 rotary coding-switches on the gateway.
Fig. 2: Decimal rotary coding-switches for address setting
ATTENTION!
Protective cover opened
Protection class IP65/IP67/IP69K not guaranteed
Screw the protective cover over the switches firmly
Check if seal of the protective cover is correctly placed
5.2.1Mode: Static Rotary
When using the rotary-mode, the last byte of the station’s IP address can be set via the rotary coding
switches.
Switch position 000: in TURCK devices used to reset the device to the default IP address (see
Resetting the IP Address, Switch Position "000", page 20).
Switch position 001: normally reserved for the default-gateway
Switch position 002…254: valid IP address range
Switch position 255: normally used for broadcast messages in the subnet.
We therefore recommend addresses in the range of
NOTE
After every change of the address-mode, a voltage reset must be done.
002…254.
18
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 21
5.2.2Mode: BootP (300)
Switch position: 300
Address setting is carried out by a BootP-server in the network after the start-up of the gateway.
PROFINET
Please assure, that in PROFINET-applications, the address assigned via a BootP-server corresponds
to the address, which is assigned in the configuration tool.
5.2.3Mode: DHCP (400)
Switch position: 400
Address setting is carried out by a DHCP-server in the network after the start-up of the device.
NOTE
The IP address, as well as the default subnet mask assigned to the station by the BootPserver, are stored permanently in the station’s EEPROM.
If the station is switched from BootP-mode to rotary- or PGM-mode, the settings carried
out in BootP-mode (IP address, subnet mask, etc) will be read from the device’s EEPROM.
NOTE
The IP address, as well as the default subnet mask assigned to the station by the DHCPserver, are stored permanently in the station’s EEPROM.
If the station is switched from DHCP-mode to rotary- or PGM-mode, the settings carried
out in DHCP-mode (IP address, subnet mask, etc) will be read from the device’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. DHCP is
used simply to convey the assigned address to the client.
PROFINET
Please assure, that in PROFINET-applications, the address assigned via a BootP-server corresponds
to the address, which is assigned in the configuration tool.
2017/06
19
Page 22
Configuring
5.2.4Mode: PGM (500)
Switch position: 500
The PGM-mode enables access of the Turck DTMs to the device’s network settings.
NOTE
In the PGM-mode, all network settings (IP address, subnet mask, etc.) are send to the
device’s internal EEPROM and stored permanently.
5.2.5Mode: PGM-DHCP (600)
Switch position: 600
The device sends DHCP-requests until a IP address is assigned (DHCP-server, PROFINET-controller).
The assigned IP-address is stored to the device and the DHCP-client is stopped.
Even after a restart of the device, the device sends no further DHCP-requests.
PROFINET
This mode assures a PROFINET-compliant operation of the modules.
NOTE
If a DHCP-server is used within the network, problems may occur during IP-assignment.
In this case, both, the DHCP-server as well as the PROFINET-controller (via DCP), try an IPaddress-assignment.
5.2.6Resetting the IP Address, Switch Position "000"
With this setting the DIP-switches to "000" followed by a voltage reset, the device is set to the
address 192.168.1.254 for IP-based services (see Default Setting of the Device, page 21).
NOTE
Setting "000" is no operation mode! After having reset the IP address to the default values,
the device has to be set to another mode.
20
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 23
Default Setting of the Device
The default-settings are as follows:
IP address192.168.1.254
Subnet mask255.255.255.0
Default gateway 192.168.1.1
NOTE
The devices can be reset by the user to these default settings at any time.
To reset the module, set the three coding-switches on the gateway to "000" followed by a
voltage reset.
ATTENTION!
Protective cover opened
Protection class IP65/IP67/IP69K not guaranteed
Screw the protective cover over the switches firmly
Check if seal of the protective cover is correctly placed
5.2.7Factory Reset (F_Reset), Switch Position "900"
F_Reset (Reset to factory setting)
Switch position: 900
This mode sets all device-settings back to the default values and deletes all data in the device's internal flash.
NOTE
Setting 900 is no operation mode! Please set the device to another mode after having
reset the IP address to the default values.
ATTENTION!
Protective cover opened
Protection class IP65/IP67/IP69K not guaranteed
Screw the protective cover over the switches firmly
Check if seal of the protective cover is correctly placed
5.2.8Functional Difference: Switch Position "000" and "900"
Reset of...
IP address, subnet mask, gateway
Parameters–
PROFINET device name–
Switch position
000900
2017/06
21
Page 24
Configuring
x10
x1
x100
x10
x1
x 100
5.2.9Address Setting via DTM
In a respective frame application e.g. PACTware™, the Turck DTMs allow direct access to Ethernet.
The IP address, as well as the subnet mask of the Ethernet devices, can be changed according to the
application by using the Busaddress Management function of the BL Service Ethernet interface
(TCP/IP) in the DTM.
Further information about using the DTMs can be found in chapter 14, Access via Turck DTMs in
PACTware™, page 125.
5.2.10Address Setting via Web Server
The device's network settings can be changed under "Network Configuration" only by users having
administrator rights.
Further information concerning the web server of the TBEN-L devices and it's use can be found
under chapter 13, The Web Server, page 111
5.3SET Button
.
The Set-button is placed left to the rotary coding switches under the cover at the device.
Pushing the Set-button causes a device-restart
Fig. 3: SET button
ATTENTION!
Protective cover opened
Protection class IP65/IP67/IP69K not guaranteed
Screw the protective cover over the switches firmly
Check if seal of the protective cover is correctly placed
.
22
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 25
6Mounting
218 [5.58]
M6 (2x)
max. 1.5 Nm
The devices must be attached to a level, pre-drilled and grounded mounting surface.
Attach the module to the mounting surface with two M6 screws. The maximum tightening
torque for the screws is 1.5 Nm.
Fig. 4: Attaching the device to the mounting plate
2017/06
23
Page 26
Mounting
6.1Grounding the Device
6.1.1Grounding and Shielding Concept
The grounding and shielding concept of the TBEN-L modules allows the fieldbus and I/O parts to be
grounded separately.
The grounding clip (1) at the M12 connectors for the fieldbus connection (P1, P2) connects the
shield of the fieldbus lines.
The grounding ring (2) is attached below the grounding clip and connects the functional ground of
the 7/8" connector (pin 3) for the power supply with the functional ground of the M12 connector
(pin 5) for connecting the sensors and actuators.
The grounding screw (3) connects the device with the system's reference potential.
24
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 27
6.1.2Grounding the Device (FE)
The grounding clip and the metal ring are connected to each other. A mounting screw through the
bottom mounting hole in the module connects the shielding of the fieldbus lines to the functional
ground of the power supply and the connected devices and to the reference potential of the system.
If a common reference potential is not required, remove the grounding clip to disconnect the fieldbus shield or attach the module with a plastic screw.
Removing the Grounding Clip
Use a flat standard screwdriver to lever the grounding clip upwards and remove it.
Fig. 7: Removing the grounding clip
Mounting the Grounding Clip
Insert the grounding clip between the fieldbus connectors (using a screwdriver if necessary) so
that it makes contact with the metal housing of the connector.
The shield of the fieldbus lines lies flush to the grounding clip.
Fig. 8: Mounting the grounding clip
2017/06
25
Page 28
Mounting
26
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 29
7Connecting
v
4
1
3
2
P1, P2
1 = TX +
2 = RX +
3 = TX –
4 = RX –
ange = FE
7.1Connecting the Devices to Ethernet
For the connection to Ethernet, the device has an integrated autocrossing switch with two 4-pin
M12 Ethernet sockets. The maximum tightening torque is 0.6 Nm.
Fig. 9: M12 Ethernet sockets
Connect the device to the field bus according to the pin assignment shown below.
Fig. 10: Pin assignment Ethernet connectors
7.1.1Ethernet-Connection for QC/FSU Applications
NOTE
Please observe the following for QuickConnect (QC)- and Fast Start-Up (FSU)-applications
with TBEN-L:
do not use a crossover-cable
–
– ETH1 = connector for incoming Ethernet-line
– ETH2 = connector for outgoing Ethernet-line
Further information concerning QuickConnect and FSU can be found here:
QC - QuickConnect, page 67
FSU - Fast Start-Up (prioritized startup), page 101
2017/06
27
Page 30
Connecting
1 BK = V2 (–)
2 BU = V1 (–)
3 GNYE = FE
4 BN = V1 (+)
5 WH = V2 (+)
For the connection to the power supply and the feeding through of the power, the device has two
5-pin 7/8" connectors.
The power supply connectors are designed as 4-pole (TBEN-L4) or 5-pole (TBEN-L5) 7/8" connectors.
V1 and V2 are galvanically isolated. The maximum tightening torque is 0.8 Nm.
Connect the device to the power supply according to the pin assignment shown below.
Supply voltage 7/8", 5-pole
Pin assignment
X1= voltage IN
X2 = voltage OUT for supplying the next node
Supply voltage 7/8", 4-pole
Pin assignment
NOTE
V1 and V2 are fed and monitored separately. In case of an undercut of the admissible voltage, the connectors are switched-off according to the module's supply concept (see Supply concept (see Supply Concept, page 29).
In case of an undervoltage at V2, the "POWER" LED changes from green to red. In case of
an undervoltage at V1, the "POWER" LED is turned off.
The behavior of the LED POWER can be configured via the parameter "LED-behavior (PWR)
at V2 undervoltage)".
V1 = supply voltage 1 (incl. supply of electronics)
V2 = supply voltage 2
X1= voltage IN
X2 = voltage OUT for supplying the next node
V1 = supply voltage 1 (incl. supply of electronics)
V2 = supply voltage 2
28
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 31
7.2.1Supply Concept
V1
V2
V1V2V1
V2
All TBEN-S-devices are supplied via two separate voltages V1 and V2.
The I/O-channels are therefore consequently separated into the different potential groups "detachable I/O" (supplied through V2) and "non-detachable" I/O (supplied through V1).
This allows a safety shutdown of parts of an installation via emergency-off circuits even when using
the highly flexible 16DXP-module variants.
V1 = supply of module electronics and the respective connectors
V2 = supply of device electronics and the respective connectors (separately detachable)
TBEN-Lx-16DIxTBEN-Lx-16DOx
TBEN-L1x-8DIP-8DOxTBEN-Lx-16DXx
V1
V2
2017/06
Fig. 11: Device supply – overview
29
Page 32
Connecting
5 FE
4 BK
1 BN +
3 BU –
3 BU –
2 WH
v
C0...C7
5 FE
4 BK
1 BN +
3 BU –
3 BU –
2 WH
v
C0...C3
7.3Connecting Digital Sensors and Actuators
The device has eight 5-pin M12 connectors for connecting digital sensors and actuators. The maximum tightening torque is 0.8 Nm.
Fig. 12: M12 connector for connecting digital sensors and actuators
7.3.1Inputs
Connect the digital sensors to the device according to the pin assignment shown below.
TBEN-Lx-16DIP/TBEN-L4-16DIN
v
1 = V
2
2 = Signal In
3 = GND V1
3
1
5
C0...C7
4
4 = Signal In
5 = FE
TBEN-Lx-8DIP-8DOP
v
1 = V
2
2 = Signal In
3 = GND V1
3
1
5
C0...C3
4
4 = Signal In
5 = FE
aux
aux
1
1
30
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 33
7.3.2Outputs
5 FE
4 BK
1 BN +
3 BU –
3 BU –
2 WH
v
C0...C7
Sensor
or
Actuator
Sensor
or
Actuator
5 FE
4 BK
1 BN +
2 WH
3 BU –
v
C0...C7
4
1
3
2
5
v
1 = V
aux
2
2 = Signal Out
3 = GND V2
4 = Signal Out
5 = FE
C4...C7
4
1
3
2
5
v
1 = V
aux
1
2 = Signal In/Out
3 = GND V1
4 = Signal In/Out
5 = FE
C0...C3
4
1
3
2
5
v
1 = V
aux
2
2 = Signal In/Out
3 = GND V2
4 = Signal In/Out
5 = FE
C4...C7
5 FE
4 BK
1 BN +
3 BU –
3 BU –
2 WH
v
C0...C7
Sensor
or
Actuator
Sensor
or
Actuator
Connect the digital actuators to the device according to the pin assignment shown below.
TBEN-Lx-16DOP/TBEN-L4-16DON
TBEN-Lx-8DIP-8DOP
4 BK
5 FE
1 BN +
2 WH
3 BU –
v
C4...C7
7.3.3In- and Outputs
Connect the digital sensors and actuators to the device according to the pin assignment shown
below.
TBEN-Lx-16DXP/TBEN-Lx-16DXN
2017/06
31
Page 34
Connecting
32
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 35
8Device Characteristics
Rotary switches
ERR
BUS
µC
Supply
µC
+4–2+5–1FE
3
V1V2
+4–2+5–1FE
3
V1V2
X1X2
IN Diag
IN Diag
V1 DiagV2 Diag
OUT Diag
OUT Diag
P2P1
4
1
3
2
4
1
3
2
ETH2ETH1
Ethernet
Ethernet
1 V
AUX1
4 IN
2 IN
3 V1 –
5 FE
120 mA
Input
Input
1 V
AUX2
4 OUT
2 OUT
3 V2 –
5 FE
120 mA
Output
Output
V1 +
V1 +
V2 +
V2 +
IN Diag
OUT Diag
IN Diag
OUT Diag
1 V
AUX1
4 IN/OUT
2 IN/OUT
3 V1 –
5 FE
120 mA
In/Output
I/O
1 V
AUX2
4 IN/OUT
2 IN/OUT
3 V2 –
5 FE
120 mA
In/Output
I/O
V1 +
V2 +
Bus
Bus
P2P1
PROFIBUS
PROFIBUS
Bus
4
1
3
2
5
4
1
3
2
5
8.1Block Diagrams
Fig. 13: Block diagrams
2017/06
33
Page 36
Device Characteristics
8.2General Technical Data
Supply voltage
V1 (incl. electronics supply)24 V DC
Permissible range
V224 V DC
Permissible range
Potential isolation Galvanic isolation of V1 and V2
Connectors
Ethernet2 x M12-connector (OUT), 4-pole, D-coded
power supply
– TBEN-L47/8" connector, 4-pole
– TBEN-L57/8" connector, 5-pole
In-/outputsM12 connector, 5-pole
Permissible torques
– Ethernet 0.6 Nm
– I/O channels/supply.0.8 Nm
– Mounting (M6 screws) 1.5 Nm
– Protective cap0.5 Nm
Isolation voltages
V1 to V2500 V AC
V1/V2 to the field bus500 V AC
Protocol properties
Modbus TCP
Address assignment
Supported Function Codes
Number of connections
EtherNet/IP™
Address assignment
Quick Connect (QC)
Device Level Ring (DLR)
Number of connections
PROFINET
Address assignment
MinCycleTime
Fast Start-Up (FSU)
Diagnostics
Topology detection
Automatic address assignment
Media Redundancy Protocol (MRP)
18 … 30 V DC
18 … 30 V DC
Static IP (rotary coding switches), BOOTP, DHCP
FC1, FC2, FC3, FC4, FC5, FC6, FC15, FC16, FC23
8
according to EtherNet/IP™ standard
< 150 ms
supported
3
DCP
1 ms
< 150 ms
according to PROFINET Alarm Handling
supported
supported
supported
34
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 37
Mounting
Mounting2 mounting holes, ? 6.3 mm
Mounting distance device to device 50 mm
Valid for operation in the ambient temperatures mentioned below, with sufficient ventilation as well as maximum load (horizontal mounting).
At low simultaneity factors and low ambient temperatures, mounting distances of < 50 mm may be possible.
Tests
Vibration test according to EN 60068-2-6/ IEC 68-2-47,
acceleration up to 20 g
Drop and topple according to IEC 60068-2-31/IEC 60068-2-32 1
Shock testaccording to EN 60068-2-27
EMCaccording to EN 61131-2
Ambient conditions
Temperature range
– Operating temperature - 40 °C to + 70 °C
– Storage/transport- 40 °C to + 85°C
Operating altitudemax. 5000 m
Protection class
IP65/IP67/IP69K
Housing
Size60.4 × 230.4 × 24 mm (w × l ×h)
Material Fibre-glass reinforced Polyamide (PA6-GF30)
Window material Lexan
Screw material 303 Stainless Steel
halogen-free yes
2017/06
35
Page 38
Device Characteristics
8.3TBEN-Lx-16DIP/TBEN-L4-16DIN
TBEN-Lx-16DIP offers sixteen digital inputs for 3-wire PNP sensors.
TBEN-Lx-16DIN offers sixteen digital inputs for 3-wire NPN sensors.
8.3.1Technical Data
power supply
Nominal value24 V DC from operating voltage
Permissible range18 … 30 V DC
Operational current (from V
Sensor/actuator supply VAUX
Digital inputs
Number of channels16
Input type
– TBEN-Lx-16DIPPNP
– TBEN-L4-16DINNPN
Switching threshold EN 61131-2 type 3, PNP or NPN
Signal voltage, low level< 5 V
High level signal voltage > 11 V
Low level signal current< 1.5 mA
High level signal current> 2 mA
Switch-on delay2.5 ms
Type of input diagnosischannel diagnostics
Potential isolationgalvanic isolation to the field bus
)< 150 mA
1
1
Supply connector C0-C7 from V1
120 mA per connector, short-circuit proof
8.3.2Wiring Diagram
Connecting the Devices to Ethernet, page 27
Connect Power Supply, page 28
Connecting Digital Sensors and Actuators, page 30
36
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 39
8.3.3Parameters for I/O Channels
Parameter nameValueDescription
Digital input
Invert digital input (Inv. DIx)
Pulse stretching
input
Further information about the parameters can be found in the fieldbus specific chapters.
EtherNet/IP™: Digital Versatile Module Class (VSC117), page 95 ff.
Modbus TCP: Register Mapping of the TBEN-L Devices, page 57 ff.
PROFINET: Parameters, page 107
8.3.4Diagnostic Messages
0 = no
1 = yesInverts the digital input signal.
0 - 255The input signal is stretched to a time between 10
control IP addresses in
the network
wait for the device to be
ready for operation
44
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 47
LEDColorStatusMeaningRemedy
0 to 15
TBEN-Lx-16DIP/
TBEN-L4-16DIN
TBEN-Lx-16DOP/
TBEN-L4-16DON
TBEN-Lx-16DXP/
TBEN-L4-16DXN
Greenon AInput active, 24 V at input
Redblinking AOverload of the supply voltage at
the respective connector
Both LEDs at the connector are
blinking
offInput active
Greenon AOutput active
Red onOutput active,
Overload/short-circuit at output
blinking AShort-circuit at the supply voltage
for the respective connector. Both
LEDs at the connector are blinking
offOutput inactive
Greenon AOutput or input active
Red on output active, overload/overcur-
rent at output
blinking AShort-circuit at the supply voltage
for the respective connector. Both
LEDs at the connector are blinking
offOutput or input active
Check the sensor supply
Check the sensor supply
Check the sensor supply
0 to 7
TBEN-Lx-8DIP-8DOP Greenon AInput active, 24 V at input
Redblinking AShort-circuit at the supply voltage
for the respective connector. Both
LEDs at the connector are blinking
off
Check the sensor supply
8 to 15
TBEN-Lx-8DIP-8DOPGreenon AOutput active
Redon Output active,
Overload/short-circuit at output
blinking AShort-circuit at the supply voltage
for the respective connector. Both
LEDs at the connector are blinking
off Output inactive
Check the sensor supply
2017/06
Can also occur in combination
A
45
Page 48
Device Characteristics
8.7.2Status and Control Word of the TBEN-L Devices
The Status as well as the Control Word are mapped into the module's process data.
EtherNet/IP™
In EtherNet/IP™, the mapping can be disable
Regis-ter, page 93 and GW Control Register, page 93).
ATTENTION!
Activate/deactivate the Status and Control Word in EtherNet/IP™
Changes
Observe that activating/deactivating the Status and Control Word causes changes in
Modbus TCP
see Register 0x100C: Station Status, page 61
PROFINET
see PROFINET-diagnostics, page 103
Status Word
in the process data mapping
the process data mapping.
d (see Gateway Class (VSC 100), GW Status
Status0V2–-----Diag
Meaning of the status bits
NameMeaning
Diag
Warn
V2V2 too low (< 18 V DC).
V1V1 too low (< 18 V DC).
COMError in the device, the internal communication is disturbed.
CFGThe I/O-configuration has be changed and is no longer compatible.
FCEForce Mode Active Error
Control Word
The Control word is reserved.
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Warn
1
–FCE–-CFGCOMV1–
Group diagnostics of the device. At least 1 channel sends diagnostics.
The Force Mode is activated, which means, the actual output values may no match the ones
defined and sent by the field bus.
46
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 49
9ARGEE/FLC
The ARGEE/FLC programming software can be downloaded from the download area at the Turck
homepage.
The Zip archive "SW_ARGEE_Environment_Vx.x.zip" contains the software and the documentation
for the programming environment.
2017/06
47
Page 50
ARGEE/FLC
48
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 51
10Modbus TCP
Modbus Application Layer
Modbus TCP
TCP
IP
andere
Master/Slave
Client/Server
Physical layer
Modbus plus
Physical layer
Rsxxx
Physical layer
Ethernet
Physical layer
10.1General Modbus Description
NOTE
The following description of the Modbus protocol is taken from the Modbus Application
Protocol Specification V1.1 of Modbus-IDA.
Modbus is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks.
The industry’s serial de facto standard since 1979, Modbus continues to enable millions of automation devices to communicate. Today, support for the simple and elegant structure of Modbus continues to grow.
The Internet community can access Modbus at a reserved system port 502 on the TCP/IP stack.
Modbus is a request/reply protocol and offers services specified by function codes. Modbus function codes are elements of Modbus request/reply PDUs (Protocol Data Unit).
Currently, the following sub protocols are implemented:
TCP/IP over Ethernet. (used for the TBEN-L modules and described in the following)
Asynchronous serial transmission over a variety of media (wire: RS232, RS422, RS485, optical:
fiber, radio, etc.)
Modbus PLUS, a high speed token passing network.
Schematic representation of the Modbus Communication Stack (according to Modbus Application
Protocol Specification V1.1 of Modbus-IDA):
2017/06
49
Page 52
Modbus TCP
10.1.1Protocol Description
The Modbus protocol defines a simple protocol data unit (PDU) independent of the underlying
communication layers.
The mapping of Modbus protocol on specific buses or network can introduce some additional fields
on the application data unit (ADU).
The Modbus application data unit is built by the client that initiates a Modbus transaction.
The function code indicates to the server what kind of action to perform.
The Modbus application protocol establishes the format of a request initiated by a client.
The field function code of a Modbus data unit is coded in one byte. Valid codes are in the range of
1... 255 decimal (128 – 255 reserved for exception responses).
When a message is sent from a Client to a Server device the function code field tells the server what
kind of action to perform. Function code "0" is not valid.
Sub-function codes are added to some function codes to define multiple actions.
The data field of messages sent from a client to server devices contains additional information that
the server uses to take the action defined by the function code. This can include items like discrete
and register addresses, the quantity of items to be handled, and the count of actual data bytes in
the data field.
The data field may be non-existent (= 0) in certain kinds of requests, in this case the server does not
require any additional information. The function code alone specifies the action.
If no error occurs related to the Modbus function requested in a properly received Modbus ADU the
data field of a response from a server to a client contains the data requested. #
50
If an error related to the Modbus function requested occurs, the field contains an exception code
that the server application can use to determine the next action to be taken.
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 53
Data model
The data model distinguishes four basic data types:
Data typeObject typeAccessComment
Discrete InputsBitRead This type of data can be provided by an I/O system.
CoilsBitread/writeThis type of data can be alterable by an application pro-
gram.
Input
registers
Holding registers
16-bit
(Word)
16-bit
(Word)
Read This type of data can be provided by an I/O system.
read/writeThis type of data can be alterable by an application pro-
gram.
For each of these basic data types, the protocol allows individual selection of 65536 data items, and
the operations of read or write of those items are designed to span multiple consecutive data items
up to a data size limit which is dependent on the transaction function code.
It’s obvious that all the data handled via Modbus (bits, registers) must be located in device application memory.
Access to these data is done via defined access-addresses (see „Modbus Registers“, page 54).
2017/06
51
Page 54
Modbus TCP
The example below shows the data structure in a device with digital and analog in- and outputs.
TBEN-L devices have only one data block, which can be accessed via different Modbus functions.
The access can be carried out either via registers (16-bit-access) or, for some of them, via single-bitaccess.
Fig. 14: Picture of the data memory of the TBEN-L modules
52
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 55
10.2Implemented Modbus Functions
The TBEN-L stations for Modbus TCP support the following functions for accessing process data,
parameters, diagnostics and other services.
Function codes
No. Function
Description
1
2
3
4
5
6
15
16
23
Read Coils
Reading multiple output bits.
Read Discrete Inputs
Reading multiple input bits.
Read Holding Registers
Reading multiple output registers.
Read Input Registers
Reading multiple input registers.
Write Single Coil
Writing a single output bit.
Write Single Register
Writing a single output register.
Write Multiple Coils
Writing multiple output bits.
Write Multiple Registers
Writing multiple output registers.
Read/Write Multiple Registers
Reading and writing of multiple registers
2017/06
53
Page 56
Modbus TCP
10.3Modbus Registers
NOTE
For the register mapping of the different Modbus addressing methods see
(siehe page 55).
Address (hex.)Access
ro = read only
rw = read/
write
0x0000 to 0x01FFroPacked process data of outputs (process data length of
0x0800 to 0x09FFrwPacked process data of outputs (process data length of
Description
devices, see Data Width of the I/O-Modules in the
Modbus-Register Area, page 56
devices, see Data Width of the I/O-Modules in the
)
Modbus-Register Area, page 56)
0x1000 to 0x1006roStation Identifier
0x100CroStations-Status (siehe
0x1012roProcess image length in bit for the digital
output modules
0x1013roProcess image length in bit for the digital
input modules
0x1017roRegister mapping revision
Register mapping revision (always 1, if not, mapping is
incompatible with this description)
0x1020roWatchdog, actual time [ms]
0x1120rwWatchdog predefined time [ms] (default: 0)
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 63
10.5.5Meaning of the Register Bits
NameMeaning
I/O data
DIxDI = digital input
DOxDO = digital output
CxC = connector
PxP = pin
Diagnostics
DiagWarnsee Register 0x100C: Station Status, page 61
V
1
V
2
COM
CFG
FCE
I/O DiagGroup diagnostics of I/Os
SCSxShort-circuit at the supply voltage for the respective connector.
SCOxOvercurrent at the respective output
Parameters See "parameters"-section for the respective module type in chapter 8.
10.6Register 0x100C: Station Status
This register contains a general module status.
BitNameDescription
Device
15–-
14FCEThe Force Mode is activated, which means, the actual output
13–-
12–-
Module bus
11CFGConfiguration error
10COMInternal communication disturbed
Voltage errors
9V
8–-
7V
6–-
5–-
4 –-
System power supply too low (< 18 V DC).
1
V2 too low (< 18 V DC).
2
values may no match the ones defined and sent by the field
bus.
2017/06
61
Page 64
Modbus TCP
BitNameDescription
Warnings
3–-
2–-
1–-
0DiagWarnDiagnostics available at the device.
10.7Register 0x1130: Modbus Connection Mode
This register defines the behavior of the Modbus connections:
BitName
– Description
15 to 2 reserved
1
0
MB_ImmediateWritePermission
– 0: With the first write access, a write authorization for the respective Modbus-connection is
requested. If this request fails, an exception response with exception-code 0x01 is generated. If
the request is accepted, the write access is executed and the write authorization remains active
until the connection is closed.
– 1: The write authorization for the respective Modbus-connection is already opened during the
connection establishment. The first Modbus-connection thus receives the write authorization,
all following connections don’t (only if bit 0 = 1).
MB_OnlyOneWritePermission
– 0: all Modbus-connections receive the write authorization
– 1: Only one Modbus-connection can receive the write permission. A write permission is opened
until a Disconnect. After the Disconnect the next connection which requests a write access
receives the write authorization.
10.8Register 0x1131: Modbus Connection Timeout
This register defines after which time of inactivity a Modbus-connection is closed through a Disconnect.
10.8.1Behavior of the BUS LED
In case of a Connection Timeout the BUS LED's behavior is as follows:
Connection-Timeout BUS-LED
time-outgreen, blinking
62
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 65
10.9Register 0x113C and 0x113D: Restore Modbus-Connection-Parameters
Registers 0x113C and 0x113D serve for resetting the parameter-register 0x1120 and 0x1130 to
0x113B to the default settings.
For this purpose, write 0x6C6F to register 0x113C. To activate the reset of the registers, write 0x6164
("load") within 30 seconds in register 0x113D.
Both registers can also be written with one single request using the function codes FC16 and FC23.
The service resets the parameters without saving them. This can be achieved by using a following
"save" service.
10.10Register 0x113E and 0x113F: Save Modbus-Connection-Parameters
Registers 0x113E and 0x113F are used for the non-volatile saving of parameters in registers 0x1120
and 0x1130 to 0x113B.
For this purpose, write 0x7361 to register 0×113E. To activate the saving of the registers, write
0x7665 ("save") within 30 seconds in register 0x113F.
Both registers can also be written with one single request using the function codes FC16 and FC23.
10.11Bit Areas: Mapping of Input Discrete- and Coil-Areas
As described before, the digital in and outputs can be read and, in case of outputs, be written in the
data area for the packed in- and output data.
NOTE
In the packed process data, the digital I/O data are stored following the variable in- and
output data area of the intelligent I/Os, which means they are stored with a variable offset,
depending on the station’s I/O-configuration.
In order to set for example a single output (single coil), the following functions are available for reading and writing single bits:
FC1 ("Read Coils"),
FC2 ("Read Discrete Inputs"),
FC 5 ("Write Single Coil")
FC15 ("Write Multiple Coils")
Data mapping of input discrete and coil areas:
Mapping: input discrete area
Contains all digital inputs starting with offset "0".
Mapping: coil area
Contains all digital outputs starting with offset "0".
2017/06
63
Page 66
Modbus TCP
10.12Error Behavior (Watchdog)
10.12.1 Behavior of Outputs
In case of a failure of the Modbus communication, the outputs’ behavior is as follows, depending on
the defined time for the Watchdog (register 0x1120, page 54):
Watchdog = 0 ms (default)
outputs hold the momentary value in case of an error
Watchdog > 0 ms
outputs switch to
NOTE
Setting the outputs to predefined substitute values is not possible in Modbus TCP. Eventually parameterized substitute values will not be used.
10.12.2 Behavior of the BUS LED
0 after the watchdog time has expired (setting in register 0×1120).
If the Watchdog has tripped, the BUS LED behaves as follows:
Watchdog BUS-LED
trippedconstantly red
10.13Parameters and Diagnostic Messages of the I/O Channels
NOTE
Please find explanations regarding parameters and diagnostic messages in the section
Register Mapping of the TBEN-L Devices, page 57.
64
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 67
11EtherNet/IP™
11.1The 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.
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.
Explicit Messages
Explicit Messages are used to transmit low-priority configuration data, general management data
or diagnostic data between two specific devices. This is a point-to-point connection in a Server/Client System that requires a request from a client always to be confirmed by a response from the
server.
Message Router Response
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.
11.1.1Communications Profile for TBEN-L
TBEN-L behaves as an EtherNet/IP™ Server in the network; the scanner of the higher-level controller
operates as a EtherNet/IP™ Client.
The following EtherNet/IP™ communications types are supported:
Unicast
Multicast
Cyclic Connection
Unconnected (UCMM) Explicit Messaging
Connected Explicit Messaging
Unicast
A point-to-point connection that exists between two nodes only.
Multicast
A packet with a special destination address, which multiple nodes on the network may be willing to
receive.
2017/06
65
Page 68
EtherNet/IP™
COS I/O Connection
COS (Change Of State) I/O Connections establish event-controlled connections. This means that the
EtherNet/IP™ devices generate messages as soon as a change of status occurs.
Cyclic I/O Connection
Messages are triggered time-controlled in Cyclic I/O connections by means of a time generator.
UCMM
The EtherNet/IP™ gateway offers the option of establishing explicit messaging via the UCMM port
(Unconnected Message Manager Port).
UCMM-based explicit messaging is normally used for random, non-periodic requests.
It is not recommended for frequent messaging because the UCMM input queue in a product is typically limited to just a few messages. Once this limit is reached, subsequent requests are ignored and
must be retried.
Connected Explicit Messaging
CIP is a connection-based system. For most communications between nodes, a connection is used.
A connection is a path or a virtual circuit between two or more end points in a system. The purpose
is to transfer data in the most efficient manner possible.
The Connection ID is a number that is associated with a communication relationship. Receiving
nodes decode this key to know whether they must accept the data or not. Receiving nodes decode
this key to know whether they must accept the data or not.
11.2EDS-File
The actual EDS-files for TBEN-L can be downloaded from the Turck home page www.turck.com.
DeviceZIP-file
TBEN-Lx-16DIP/
TBEN-L4-16DIN
TBEN-Lx-16DOP/
TBEN-L4-16DON
TBEN-Lx-8DIP-8DOP
TBEN-Lx-16DXP/
TBEN-L4-16DXN
TBEN-L45_ETHERNETIP.zip
66
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 69
11.3Diagnostic Messages via Process Data
Besides the evaluation of diagnostic data via Explicit Messages, TBEN-L with EtherNet/IP™ o ffers the
possibility of mapping diagnostic data into the process data (see also the devices‘ process data
mappings (page 78 ff.).
2 different forms of diagnostic data handling are provided:
Summarized diagnostics
Scheduled diagnostics (manufacturer specific)
11.3.1Summarized Diagnostics
The summarized diagnostic data mode will send back the bit "I/O Diag" which indicates that one of
the device channels sends a diagnosis.
This bit will be "0" if there are no diagnostic flags set on the device. This bit is set to "1" if there are
diagnostics pending.
The scheduled diagnostics feature (Process Data Class (VSC102), page 93) is used for mapping the
channel diagnostic bits into the device's process data (siehe page 78) ff..
Bit "SchedDiag"
0 = no mapping of channel diagnostics into the process data
1 = mapping of channel diagnostics into the process data activated
11.4QC - QuickConnect
QuickConnect enables a PLC to build up connections to EtherNet/IP™ nodes in less than 300 ms
after switching-on the power supply for the EtherNet/IP™ network. The fast start-up is necessary for
fast tool changing applications at robot arms for example in the automobile industry.
The TBEN-L-devices support FSU with a start-up time of < 150 ms.
Ethernet-Cabling for TBEN-L in QC-Applications
Please read Ethernet-Connection for QC/FSU Applications, page 27 for information about the
correct Ethernet-cabling in QC-applications with TBEN-L.
2017/06
67
Page 70
EtherNet/IP™
11.4.1QuickConnect in TBEN
Turck TBEN-L devices support QuickConnect.
QuickConnect is activated:
via the device’s web server
via the configuration data in the PLC program via
Assembly Class 0x04, Configuration Assembly 106, bit 0 = 1
Activating QuickConnect also activated the automatic setting of all necessary portproperties:
Auto-negotiation
Transmission speed
Duplex
Topology
AutoMDIX
QuickConnect via Configuration Assembly
The Configuration Assembly is part of the Assembly Class of the device and is defined during the
device's configuration in the RS Logix-software tool by Rockwell Automation.
= deactivated
= 100BaseT
= Full duplex
= linear
= deactivated
68
Fig. 15: Configuration Assembly
Quick Connect via Class Instance Attribute
Activate QuickConnect via Class Instance Attribute with the following settings:
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 71
QuickConnect via Web Server
QuickConnect can also be activated or deactivated using the device's web server, see also chapter
13.12, Station Configuration, page 122.
11.5Device Level Ring (DLR)
The Device Level Ring (DLR)-redundancy protocol is used to increase the stability of EtherNet/IP™
networks.
DLR-capable products provide an integrated switch and can thus be integrated into a ring topology.
The DLR-protocol is used to recognize a ring fault. In case of an interruption of the data line, data are
sent through an alternative network section, so that the network can be reconfigured as soon as
possible.
DLR-capable network nodes are provided with extended diagnostic functions which enable the
devices to localize errors and thus decrease the time for error search and maintenance.
2017/06
69
Page 72
EtherNet/IP™
11.6EtherNet/IP™ Standard Classes
The TBEN-L stations support the following EtherNet/IP™ Standard Classes in accordance with the
CIP specification.
Class CodeObject name
01 (0x01)Identity Object (0x01)
04 (0x04)Assembly Object (0x04)
06 (0x06)Connection Manager Object (0x06)
245 (0xF5)TCP/IP Interface Object (0xF5)
246 (0xF6)Ethernet Link Object (0xF6)
11.6.1Identity Object (0x01)
The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev.
2.1 by ODVA & ControlNet International Ltd. and adapted to TBEN-L.
Class Attributes
Attr. No.Attribute nameGet/
1 (0x01)REVISIONGUINT1
2 (0x02)MAX OBJECT INSTANCEGUINT1
6 (0x06)MAX CLASS ATTRIBUTEGUINT7
7 (0x07)MAX INSTANCE ATTRIBUTEGUINT7
Instance Attributes
Attr. No.Attribute nameGet/
1 (0x01)VENDORGUINTContains the vendor ID.
2 (0x02)PRODUCT TYPEGUINTShows the general product type.
3 (0x03)PRODUCT CODEGUINTIdentifier for a specific product of a device
4 (0x04)REVISION
Major Minor
TypeDescription
Set
GSTRUCT
OF:
USINT
USINT
TypeValue
Set
TURCK = 48
Communications Adapter
= 0x0C
12
dec
type.
default: 27247
Revision of the item the Identity Object is representing.
0x01
0x06
dec =
6A6F
70
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 73
5 (0x05)DEVICE STATUSGWORDSee page 71
6 (0x06)SERIAL NUMBERGUDINTContains the ident-no. of the product (3 last
7 (0x07)PRODUCT NAME
Device Status
BitNameDefinition
0 to 1reserveddefault = 0
2ConfiguredTRUE = 1
3reserveddefault = 0
4 to 7Extended Device Sta-
8 to 15reserveddefault = 0
LENGTH
NAME
tus
bytes of the MAC-ID).
GSTRUCT
OF:
USINT
STRING
[13]
The application of the device has been configured (
default-settings).
0011 = no I/O connection established
0110 = at least one I/O connection in run mode
0111 = at least one I/O connection established, all in IDLE
mode
All other settings = reserved
e. g.:
TBEN-L5-16DXP
Common Services
Service code
01 (0x01)yesyesGet_Attribute_All
05 (0x05)noyesReset
14 (0x0E)yesyesGet_Attribute_Single
16 (0x10)nonoSet_Attribute_Single
11.6.2Assembly Object (0x04)
Assembly Objects bind attributes of multiple objects to allow data to or from each object to be sent
or received over a single connection.
The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev.
2.1 by ODVA & ControlNet International Ltd. and adapted to TBEN-L.
Class Attributes
Attr. No.Attribute nameGet/
1 (0x01)REVISIONGUINT2
2 (0x02)MAX OBJECT INSTANCEGUINT104
Class
InstanceService name
Returns a predefined list of the object‘s attributes.
Starts the reset service for the device.
Returns the contents of a specified attribute.
Modifies a single attribute.
TypeValue
Set
2017/06
71
Page 74
EtherNet/IP™
Instance Attributes
Attr. No.Attribute nameGet
3 (0x03)DATASARRAY OF
4 (0x04)SIZEGUINT Number of bytes in attr. 3
Common Services
Service code
01 (0x01)yesyesGet_Attribute_All
14 (0x0E)noyesGet_Attribute_Single
Configuration Assembly
TBEN-L stations support Configuration Assembly. It enables an EDS-based configuration/parameterization of the devices in the PLC software (if supported by the PLC).
Instance 106
The Configuration Assembly contains:
10 byte configuration data
+ x byte parameter data of the respective device
Class
TypeDescription
/
Set
BYTE
256 or variable
InstanceService name
Configuration Assembly
ModuleStandard bytesModule specific
parameter data
TBEN-Lx-16DIP/
TBEN-L4-16DIN
TBEN-Lx-16DOP/
TBEN-L4-16DON
TBEN-Lx-8DIP-8DOP10 byte16 byte26
TBEN-Lx-16DXP/
TBEN-L4-16DXN
10 byte21 byte31
10 byte4 byte14
10 byte26 byte36
total
72
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
EN DO15 EN DO14 EN DO13 EN DO12 EN DO11 EN DO10EN DO9EN DO8
Pulse stretching input 0
Pulse stretching input 1
Pulse stretching input 2
Pulse stretching input 3
Pulse stretching input 4
Pulse stretching input 5
Pulse stretching input 6
Pulse stretching input 7
Pulse stretching input 8
Pulse stretching input 9
Pulse stretching input 10
Pulse stretching input 11
Pulse stretching input 12
Pulse stretching input 13
Pulse stretching input 14
Pulse stretching input 15
Reserved
Reserved
Quick
Connect
76
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 79
Module Configuration Data
Parameter name
= default
A
Quick Connect0 = controlled recovery
ValueMeaning
1 = activated
ETH x Port Setup0 = AutonegotiationThe port is set to autonegotiation.
1 = 100BT/FDFix setting of the communication parameters
for the Ethernet port to:
– 100BaseT
– Full duplex
LED behavior (PWR) at V2
undervoltage
0 = redPWR-LED constant red at V2 undervoltage.
1 = greenPWR-LED is blinking green at V2 undervoltage.
2017/06
77
Page 80
EtherNet/IP™
11.6.3Process Data Instances
Instance 101
Contains the device’s input data (static length 256 bytes).
2 Bytes status information
+ process data
Instance 102
Contains the device’s output data (static length 256 bytes).
2 bytes control data (mapped, but not defined)
+ process data
Instance 103 and Instance 104
In- and output assembly instances with variable assembly sizes. The assembly size is pre-calculated
to support the stations I/O-configuration, enabled diagnostics, etc.
Input Assembly Instance: 103
Output Assembly Instance: 104
The effective size of the Assembly Instance can be determined using the Assembly Object (
0×67, attribute 0x04) and can be from 2 to 496 bytes large.
Process Data Mapping TBEN-Lx-16DIP/TBEN-L4-16DIN
Scheduled diagnostic data mode
Default setting, see page 67
IN = 8 byte
OUT = 2 byte
INByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Status0
1
Inputs2
3
Diagnostics
OUT ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Control0
3
4
5
6
1
V
2
------
-FCE--CFGCOMV
DI7
C3P2
DI15
C7P2
DI6
C3P4
DI14
C7P4
DI5
C2P2
DI13
C6P2
C2P4
C6P4
-------I/O Diag
--
Sched
Diag
SCS7SCS6SCS5SCS4SCS3SCS2SCS1SCS0
--------
Control word (MSB)
Control word (LSB)
instance
Diag
Warn
-
DI0
C0P4
DI8
C4P4
DI4
DI12
DI3
C1P2
DI11
C5P2
DI2
C1P4
DI10
C5P4
1
DI1
C0P2
DI9
C4P2
-----
78
Meaning of the Process Data Bits, page 84.
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 81
No diagnostics,
status- and control-word can be deactivated, see page 44.
IN = 4 byte
OUT = 2 byte
INByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Status0
1
Inputs2
3
OUTByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Control0
1
-------
-FCE--CFGCOMV
DI7
C3P2
DI15
C7P2
DI6
C3P4
DI14
C7P4
DI5
C2P2
DI13
C6P2
DI4
C2P4
DI12
C6P4
Control word (MSB)
Control word (LSB)
Meaning of the Process Data Bits, page 84.
Process Data Mapping TBEN-Lx-16DOP/TBEN-L4-16DON
DI3
C1P2
DI11
C5P2
DI2
C1P4
DI10
C5P4
1
DI1
C0P2
DI9
C4P2
Diag
Warn
-
DI0
C0P4
DI8
C4P4
Scheduled diagnostic data mode
default setting, see also page 67.
IN = 8 byte
OUT = 4 byte
INByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Status0
1
Diagnostics
OUTByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Control0
Outputs2
2
3
4
5
6
7
1
3
V
2
-FCE--CFGCOMV
------
1
-------I/O Diag
--
Sched
Diag
-----
SCS7SCS6SCS5SCS4SCS3SCS2SCS1SCS0
SCO7SCO6SCO5SCO4SCO3SCO2SCO1SCO0
SCO15SCO14SCO13SCO12SCO11SCO10SCO9SCO8
--------
Control word (MSB)
Control word (LSB)
DO7
C3P2
DO15
C7P2
DO6
C3P4
DO14
C7P4
DO5
C2P2
DO13
C6P2
DO4
C2P4
DO12
C6P4
DO3
C1P2
DO11
C5P2
DO2
C1P4
DO10
C5P4
DO1
C0P2
DO9
C4P2
Diag
Warn
-
DO0
C0P4
DO8
C4P4
2017/06
Meaning of the Process Data Bits, page 84.
79
Page 82
EtherNet/IP™
No diagnostics,
status- and control-word can be deactivated, see page 44.
IN = 2 byte
OUT = 4 byte
INByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Status0
1
OUTByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Control0
1
Outputs2
3
V
2
------
-FCE--CFGCOMV
Control word (MSB)
Control word (LSB)
DO7
C3P2
DO15
C7P2
DO6
C3P4
DO14
C7P4
DO5
C2P2
DO13
C6P2
DO4
C2P4
DO12
C6P4
DO3
C1P2
DO11
C5P2
DO2
C1P4
DO10
C5P4
1
DO1
C0P2
DO9
C4P2
Diag
Warn
-
DO0
C0P4
DO8
C4P4
Meaning of the Process Data Bits, page 84.
Process Data Mapping TBEN-Lx-8DIP-8DOP
Scheduled diagnostic data mode
Default setting, see page 67
IN = 8 byte
OUT = 4 byte
INByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Status0
1
Inputs2
3
Diagnostics
OUTByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Control0
Outputs2
4
5
6
7
1
3
V
2
------
-FCE--CFGCOMV
DI7
C3P2
DI6
C3P4
--------
-------I/O Diag
--
SCS7SCS6SCS5SCS4SCS3SCS2SCS1SCS0
SCO15SCO14SCO13SCO12SCO11SCO10SCO9SCO8
DO15
C7P2
DO14
C7P4
--------
DI5
C2P2
Sched
Diag
DO13
C6P2
Diag
Warn
1
DI4
C2P4
DI3
C1P2
DI2
C1P4
DI1
C0P2
DI0
C0P4
-----
Control word (MSB)
Control word (LSB)
DO12
C6P4
DO11
C5P2
DO10
C5P4
DO9
C4P2
DO8
C4P4
-
80
Meaning of the Process Data Bits, page 84.
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 83
No diagnostics,
status- and control-word can be deactivated, seepage 44
IN = 4 byte
OUT = 4 byte
INByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Status0
1
Inputs2
3
OUTByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Control0
1
Outputs2
3
V
2
------
-FCE--CFGCOMV
DI7
C3P2
DI6
C3P4
DI5
C2P2
DI4
C2P4
--------
Control word (MSB)
Control word (LSB)
DO15
C7P2
DO14
C7P4
DO13
C6P2
DO12
C6P4
--------
.
DI3
C1P2
DO11
C5P2
DI2
C1P4
DO10
C5P4
1
DI1
C0P2
DO9
C4P2
Meaning of the Process Data Bits, page 84.
Diag
Warn
-
DI0
C0P4
DO8
C4P4
2017/06
81
Page 84
EtherNet/IP™
Process Data Mapping TBEN-Lx-16DXP/TBEN-L4-16DXN
Scheduled diagnostic data mode
Default setting, see page 67
IN = 10 byte
OUT = 4 byte
INByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Status0
1
Inputs2
3
Diagnostics
OUTByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Control0
Outputs2
4
5
6
7
8
9
1
3
V
2
-FCE--CFGCOMV
DI7
C3P2
DI15
C7P2
------
1
DI6
C3P4
DI14
C7P4
DI5
C2P2
DI13
C6P2
DI4
C2P4
DI12
C6P4
DI3
C1P2
DI11
C5P2
DI2
C1P4
DI10
C5P4
DI1
C0P2
DI9
C4P2
-------I/O Diag
--
Sched
Diag
-----
SCS7SCS6SCS5SCS4SCS3SCS2SCS1SCS0
SCO7SCO6SCO5SCO4SCO3SCO2SCO1SCO0
SCO15SCO14SCO13SCO12SCO11SCO10SCO9SCO8
--------
Control word (MSB)
Control word (LSB)
DO7
C3P2
DO15
C7P2
DO6
C3P4
DO14
C7P4
DO5
C2P2
DO13
C6P2
DO4
C2P4
DO12
C6P4
DO3
C1P2
DO11
C5P2
DO2
C1P4
DO10
C5P4
DO1
C0P2
DO9
C4P2
Diag
Warn
-
DI0
C0P4
DI8
C4P4
DO0
C0P4
DO8
C4P4
Meaning of the Process Data Bits, page 84.
82
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 85
No diagnostics,
status- and control-word can be deactivated, see page 44.
The Status attribute indicates the status of the TCP/IP network interface.
Refer to the state diagram,Fig. 16: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.
Bit(s)NameDefinition
0-3Interface Configuration
Status
4 to 31reserved
Configuration Capability
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
The Configuration Capability indicates the device’s support for optional network configuration
capability.
Bit(s)NameDefinitionValue
0BOOTP ClientThe device is capable of obtaining its net-
work configuration via BOOTP.
1DNS ClientThe device is capable of resolving host
names by querying a DNS server.
2DHCP ClientThe device is capable of obtaining its net-
work configuration via DHCP.
Configuration Control
1
0
1
The Configuration Control attribute is used to control network configuration options.
Bit(s)NameDefinition
0-3Startup-
Configuration
4DNS EnableAlways 0
5-31reservedSet to 0
Determines how the device shall obtain its initial configuration.
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
86
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 89
Interface Configuration
Non-existent
Obtaining initial
configuration
Waiting
for
configuration
Applying
configuration
TCP/IP network
interface configured
Status = 0×00000001
Powerup/ Reset
BOOTP/DHCP
response received
BOOTP/DHCP
disabled and
stored config.
valid
Set_Attributes
request received
Change interface
configuration
Status =
0×00000000
Configuration applied
BOOTP OR
DHCP enabled
BOOTP/DHCP
disabled and
stored config. valid
Status =
0×00000000
This attribute contains the configuration parameters required to operate as a TCP/IP node.
To modify the Interface Configuration attribute, get the Interface Configuration attribute first,
change the desired parameters, then set the attribute.
The TCP/IP Interface Object applies the new configuration upon completion of the Set service. If
the value of the Startup Configuration bits (Configuration Control attribute) is 0, the new
configuration is stored in non-volatile memory.
The device does not reply to the set service until the values are safely stored to non-volatile
memory.
An attempt to set any of the components of the Interface Configuration attribute to invalid
values results in an error (status code 0x09) returned from the Set service.
If initial configuration is obtained via BOOTP or DHCP, the Interface Configuration attribute
components are all 0 until the BOOTP or DHCP reply is received.
Upon receipt of the BOOTP or DHCP reply, the Interface Configuration attribute shows the
configuration obtained via BOOTP/DHCP.
Host Name
This 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.
2017/06
Fig. 16: TCP/IP object state diagram (acc. to CIP Spec., Vol.2, Rev. 1.1)
87
Page 90
EtherNet/IP™
11.6.6Ethernet Link Object (0xF6)
The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev.
1.1 by ODVA & ControlNet International Ltd. and adapted to TBEN-L.
Class Attributes
Attr. No.Attribute nameGet/
1 (0x01)REVISIONGUINT1
2 (0x02)MAX OBJECT INSTANCEGUINT1
3 (0x03)NUMBER OF INSTANCESGUINT1
6 (0x06)MAX CLASS IDENTIFIER GUINT7
7 (0x07)MAX INSTANCE ATTRIBUTEGUINT 6
Instance Attributes
Attr. No.Attribute nameGet
1 (0x01)INTERFACE SPEEDGUDINTSpeed in Mbit/s
2 (0x02)INTERFACE FLAGSGDWORD
3 (0x03)PHYSICAL
6 (0x06)INTERFACE
7 (0x07)INTERFACE TYPE(siehe page 89)
10 (0x0A)INTERFACE LABEL
ADDRESS
CONTROL
TypeValue
Set
TypeDescription
/
Set
(e. g. 10, 100, 1000, etc.)
GARRAY OF
USINT
2 WORDAllows port-wise changes of the Ethernet-set-
Contains the interface’s MAC address
(Turck: 00:07:46:××:××:××)
tings
88
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 91
Interface Flags
BitsName
0Link StatusIndicates whether or not the Ethernet 802.3
1Half/full duplex0 = half duplex
2 to 4Negotiation StatusIndicates the status of the automatic
5Manual Setting
Requires Reset
6Local Hardware Fault 0 = interface detects no local hardware fault
Definition
communications interface is connected to an
active network.
0 = inactive link
1 = active link
1 = full duplex
If the L ink S tatus flag is 0, D uple x bit c anno t be
defined.
Duplex detection (autonegotiation)
0 = autonegotiation running
1 = autonegotiation and speed detection
failed
Using default values for speed and duplex
(10Mbps/half duplex).
2 = autonegotiation failed but detected speed
(default: half duplex).
3 = successfully negotiated speed and duplex.
4 = autonegotiation not attempted. Forced
speed and duplex.
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 = a local hardware fault is detected
Default value
Depends on
application
Depends on
application
Depends on
application
0
0
Common Services
Service code
01 (0x01)yesyesGet_Attribute_All
14 (0x0E)yesyesGet_Attribute_Single
76 (0x4C)no yesEnetlink_Get_and_Clear
Class
InstanceService name
2017/06
89
Page 92
EtherNet/IP™
11.7VSC-Vendor Specific Classes
In addition to supporting the above named CIP Standard Classes, the TBEN-L stations support the
vendor specific classes described in the following.
Class Code
dec.
(hex.)
100 (0x64)Gateway Class, page 91Contains data and settings concerning the
102 (0x66)Process Data Class, page 93contains the process data
117 (0x75)Digital Versatile Module Class,
126 (0x1A)Miscellaneous Parameters Class, page 97Describes the EtherNet/IP™-Port properties
NameDescription
11.7.1Class Instance of the VSCs
NOTE
The class instance attributes are the same for each Vendor Specific Class.
The class-specific Object Instances and the corresponding attributes are explained in the
paragraphs for the different VSC.
The general VSC - class instance attributes are defined as follows.
Attr. No.
dec.
(hex.)
100
(0x64)
101
(0x65)
102
(0x66)
103
(0x67)
Attribute nameGet/
Class revisionGUINTContains the revision number of the class
Max. instanceGUSINTContains the number of the highest
# of instancesGUSINTContains the number of Object Instances
Max. class attributeGUSINTContains the number of the last class attri-
field bus-specific part of the TBEN-L stations.
page 95Describes the I/O channels
TypeDescription
Set
(maj. rel. *1000 + min. rel.).
instance of an object created on this level
in the class hierarchy.
created in this class.
bute to be implemented.
90
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 93
11.7.2Gateway Class (VSC 100)
This class contains all information concerning the whole module not the different
I/O channels.
Class Instance
NOTE
Please refer to section Class Instance of the VSCs, page 90 for the description of the class
instance for the VSC.
Object Instance 1
Attr. No.
dec.
(hex.)
100
(0x64)
101
(0x65)
102
(0x66)
103
(0x67)
104
(0x68)
Attribute nameGet/
TypeDescription
Set
Max object attribute
Hardware revisionGSTRUCTContains the hardware revision number of
Firmware revisionGSTRUCTContains the revision number of the boot
Service tool ident
number
Hardware
Info
GUSINTContains the number of the last object
attribute to be implemented.
the module (USINT Maj./USINT Min.)
firmware (Maj./Min.).
GUDINTContains the BOOT ID number that serves
as an identification number for the DTM.
GSTRUCTContains module hardware information
(UINT):
– count (number of the following entries)
– CLOCK FREQUENCY (kHz)
– MAIN FLASH (in kB)
– MAIN FLASH SPEED (ns)
– SECOND FLASH (kB)
– RAM (kB),
– RAM SPEED (ns),
– RAM data WIDTH (bit),
– SERIAL EEPRPOM (kbit)
– RTC SUPPORT (in #)
– AUTO SERVICE BSL SUPPORT (BOOL)
– HDW SYSTEM
2017/06
91
Page 94
EtherNet/IP™
Object Instance 2
Attr. No.
dec.
(hex.)
109
(0x6D)
115
(0x73)
Attribute nameGet/
TypeDescription
Set
Status register 2GSTRUCTThe Status Word contains general station
status information,
Device
– Bit 15: reserved
– Bit 14: "Force Mode Active Error" The
Force Mode is activated (FCE).
– Bit 13: reserved
– Bit 12: reserved
Internal bus
– Bit 11: "I/O Cfg Modified Error" (CFG)
Configuration error
– Bit 10: "I/O Communication Lost Error"
(COM)
Internal communication disturbed
Voltage errors
– Bit 09: "V1 too low"
V1 < 18 V DC
– Bit 08: reserved
– Bit 07: "V2 too low"
V2 < 18 V DC
– Bit 06: reserved
– Bit 05: reserved
– Bit 04: reserved
Warnings
– Bit 03: reserved
– Bit 02: reserved
– Bit 01: reserved
– Bit 00: "I/O Diags Active Warning"
(DiagnWarn) At least one I/O-channel
sends active diagnostics.
ON IO
CONNECTION
TIMEOUT
G/SENUM
USINT
Reaction to the I/O connection exceeding
the time limit.
SWITCH IO FAULTED (0):
The channels are switched to substitute
value.
SWITCH IO OFF (1):
The outputs are switched to 0.
SWITCH IO HOLD (2):
No further changes to the I/O-data. The
outputs are held.
92
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 95
Attr. No.
dec.
(hex.)
138
(0x8A)
139
(0x8B)
140
(0x8C)
Attribute nameGet/
GW Status
Register
GW Control Register
Disable ProtocolsGet/setUINTDeactivation of the used Ethernet proto-
11.7.3Process Data Class (VSC102)
This class contains the process-relevant information.
Class Instance
TypeDescription
Set
Get/setDWORDActivates or deactivates the mapping of
the status word into the device's input
data.
Get/setDWORDActivates or deactivates the mapping of
the status word into the device's input
data.
col.
bit assignment
Bit 0 = EtherNet/IP™ (can not be disabled
via EtherNet/IP™-interface)
Bit 1 = Modbus/TCP
Bit 2 = PROFINET
Bit 3 - 14 = reserved
Bit 15 = web server
NOTE
Please refer to section Class Instance of the VSCs, page 90 for the description of the class
instance for the VSC.
Object instance 1, standard output process data (compressed)
This instance is not supported.
Object instance 2, standard output process data (compressed)
This instance is not supported.
Object Instance 3, diagnostic instance
Attr. No.
dec. (hex.)
104 (0x68)GW
105 (0x69)GW
106 (0x6A)reserved-
Attribute name
Summarized
diagnostics)
scheduled diagnostics (manufacturer specific
diagnostics)
Get/
TypeDescription
Set
G/SBOOL0 = inactive
1 = active: 1 bit of diagnosis mapped at the
end of the input data image (
Changes become valid after a start-up!
G/SBOOL0 = inactive
1 = activated: Used for activating the map-
ping of the channel-specific diagnostic
bits into the process input data (
Changes become valid after a start-up!
page 67).
page 67).
2017/06
93
Page 96
EtherNet/IP™
Object Instance 4, COS/CYCLIC instance
Attr. No.
dec.
(hex.)
104 (0x68)COS data
Attribute nameGet/
mapping
TypeDescription
Set
G/SENUM
USINT
The actual data are loaded to the non-vol-
atile memory of the device.
Changes become valid after a start-up!
0 = standard: Data of COS message
input data.
1 = process input data (only the process
data input image is transferred to scanner)
2 to 7: reserved
94
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 97
11.7.4Digital Versatile Module Class (VSC117)
This class contains all information and parameters for the device’s I/O channels.
Object Instance
Attr. No.
dec.
(hex.)
100 (0x64)Max object
101 (0x65)reserved-
102 (0x66)reserved-
103 (0x67)Module IDGDWORDContains the device ID
104 (0x68)Module order num-
105 (0x69)Module order
106 (0x6A)Module
107 (0x6B)Module type IDGENUM
108 (0x6C)Module command
109 (0x6D)Module response
110 (0x6E)Module
111 (0x6F)Module input
112 (0x70)Module output
Attribute nameGet/
Set
GUSINTContains the number of the last object
attribute
GUDINTContains the ident number of the device.
ber
GSHORT
name
GUSINTContains the revision number of the
revision
G/SARRAYThe device's command interface.
interface
GARRAYThe device's response interface.
interface
GENUM
registered index
GUSINTContains the number of input channels
channel count
GUSINTContains the number of output channels
channel count
TypeDescription
attribute to be implemented.
Contains the device name
STRING
device
Describes the device type:
USINT
USINT
0x01: digital device
ARRAY OF:
BYTE: Control byte sequence
ARRAY OF:
BYTE: Response byte sequence
Contains the index numbers specified in
all the station lists.
supported by the station.
supported by the station.
2017/06
95
Page 98
EtherNet/IP™
Attr. No.
dec.
Attribute nameGet/
Set
TypeDescription
(hex.)
Input data
113 (0x71)Module input_1GDWORDInput data of the respective I/Os.
114 (0x72)Module input_2GDWORDInput data of the respective I/Os.
Output data
115 (0x73)Module output_1GDWORDOutput data of the respective I/Os.
116 (0x74)Module output_2GDWORDOutput data of the respective I/Os.
...
Diagnostics
119 (0x77)Short circuit output
GDWORD Overcurrent at output
error_1
120 (0x78)Short circuit output
GDWORD Overcurrent at output
error_2
121 (0x79)Short circuit V
AUX
GDWORDOvercurrent at sensor/actuator supply
error_1
122 (0x7A)Short circuit V
AUX
GDWORDOvercurrent at sensor/actuator supply
error_2
...
Parameter data
127 (0x7F)Invert input data_1G/SDWORD The input signal is inverted (channel 0 to
15).
...
133 (0x85)Auto recovery out-
put_1,
G/SDWORD The outputs switch on automatically after
an overload (output 0 to 15).
...
137 (0x89)Re-triggered
recovery output_1
G/SDWORD The outputs (channel 0 to 15) have to be
re-triggered in case of an overload.
...
139 (0x8b)Enable high side
output driver_1
G/SDWORD Enables the high side output driver of
channels (channel 0 to 15).
...
96
149 (0x95)
to
164 (0xA4)
Pulse stretching
input x
G/SByteThe input signal is stretched to a time
between 10 to 2550 ms.
Default setting:
0 = pulse stretching deactivated
(standard signal = 2,5 ms)
Example:
10 = signal of 100 ms
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Page 99
11.7.5Miscellaneous Parameters Class (VSC 126)
Instance 1/Instance 2
Attr. No.
dec.
(hex.)
109 (0x6D)Ethernet port
112 (0x70)IO Controller Soft-
Attribute nameGet/
Parameters
ware revision
TypeDescription
Set
G/SDWORD0 = autonegotiate, autoMDIX A
1 = 10BaseT, half duplex, linear topology
(AutoMDIX disabled)
2 = 100BaseT, full duplex, linear topology
(AutoMDIX disabled)
3 = 100BaseT, half duplex, linear topology
(AutoMDIX disabled)
4 = 100BaseT, full duplex, linear topology
(AutoMDIX disabled)
GDWORD The number of instances of this parameter
depends on the number of I/O controllers.
2017/06
97
Page 100
EtherNet/IP™
98
Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | more@turck.com | www.turck.com
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.