netTAP NT 50 - Gateway Devices UM 18 EN

User Manual
netTAP NT 50
Gateway Devices
Hilscher Gesellschaft für Systemautomation mbH

www.hilscher.com
DOC091202UM18EN | Revision 18 | English | 2022-07 | Released | Public
Introduction 2/92
Table of Contents
1 INTRODUCTION ......................................................................................................... 5
1.1 About the User Manual ...............................................................................................5
1.1.1 Obligation to read and understand the Manual .................................................... 5
1.1.2 List of Revisions ................................................................................................... 5
1.1.3 Conventions in this Manual .................................................................................. 6
1.2 Reference to Hardware, Software and Firmware .......................................................7
1.3 Contents of the Product DVD .....................................................................................8
1.3.1 Directory Structure of the DVD ............................................................................. 8
1.3.2 Device Description Files ....................................................................................... 9
1.3.3 Documentation for netTAP NT 50 ...................................................................... 10
2 SAFETY .................................................................................................................... 12
2.1 General Note ............................................................................................................12
2.2 Intended Use ............................................................................................................12
2.3 Personnel Qualification .............................................................................................12
2.4 References Safety ....................................................................................................12
2.5 Safety Instructions to avoid Personal Injury ..............................................................13
2.5.1 Danger of unsafe System Operation .................................................................. 13
2.6 Safety Instructions to avoid Property Damage .........................................................14
2.6.1 Power disconnect during firmware or configuration download ........................... 14
2.6.2 Device Destruction by exceeding allowed Supply Voltage ................................ 15
2.6.3 Exceeding the maximum number of allowed write/delete accesses .................. 15
2.6.4 Danger of unsafe System Operation .................................................................. 15
2.7 Labeling of Safety Messages ....................................................................................16
3 DESCRIPTION AND REQUIREMENTS ................................................................... 17

3.1 Device Description ....................................................................................................17
3.2 Device Types and Protocol Conversions ..................................................................18
3.2.1 Device Names .................................................................................................... 18
3.2.2 Protocol Conversions ......................................................................................... 19
3.3 System Requirements ..............................................................................................20
3.4 Configuration Requirements .....................................................................................21
4 DEVICE DRAWINGS AND CONNECTIONS ............................................................ 22

4.1 Device and Dimensioned Drawings ..........................................................................22
4.2 Positions of LEDs and Control Elements ..................................................................23
4.2.1 Range of Values for the Address Switches ........................................................ 23
4.3 Connections ..............................................................................................................24
4.3.1 X1 Top Connection ............................................................................................. 24
4.3.2 X2 Front Connection........................................................................................... 24
4.3.3 X3 Bottom Connection ....................................................................................... 28
4.4 Schematic Diagram - Galvanic Isolation ...................................................................32
4.4.1 Galvanic Isolation of NT 50-xx-EN Devices ....................................................... 32
4.4.2 Galvanic Isolation of NT 50-xx-RS ..................................................................... 33
4.4.3 Galvanic Isolation of NT 50-RS-EN .................................................................... 34
netTAP NT 50 | Gateway Devices

DOC091202UM18EN | Revision 18 | English | 2022-07 | Released | Public © Hilscher, 2010-2022
Introduction 3/92
5 NT 50 MOUNTING AND DISMOUNTING ................................................................. 35
5.1 DIN Top Hat Rail Mounting of the NT 50 ..................................................................35
5.2 Removing the NT 50 from the DIN Top Hat Rail ......................................................35
6 COMMISSIONING .................................................................................................... 36
6.1 Load Firmware and Configuration ............................................................................36
6.1.1 Download Configuration Files from the PC ........................................................ 36
6.1.2 Potential Differences for Device Types NT 50-xx-RS and NT 50-RS-EN .......... 37
6.2 Start-up Behavior ......................................................................................................37
6.3 Resetting the NT50 to the factory setting .................................................................38
7 TROUBLESHOOTING .............................................................................................. 39
7.1 Failure in 10 MBit/s Half Duplex Mode and Workaround ..........................................40
8 LEDS ......................................................................................................................... 41
8.1 System LEDs ............................................................................................................41
8.2 LEDs Real Time Ethernet Protocols .........................................................................42
8.2.1 LEDs EtherNet/IP Scanner (Master) .................................................................. 42
8.2.2 LEDs EtherNet/IP Adapter (Slave) ..................................................................... 43
8.2.3 LEDs Open Modbus/TCP ................................................................................... 44
8.2.4 LEDs PROFINET IO Controller .......................................................................... 45
8.2.5 LEDs PROFINET IO-RT-Device ........................................................................ 46
8.3 LEDs Fieldbus Protocols ..........................................................................................47
8.3.1 LED PROFIBUS DP Master ............................................................................... 47
8.3.2 LED PROFIBUS DP Slave ................................................................................. 47
8.3.3 LED CANopen Master ........................................................................................ 48
8.3.4 LED CANopen Slave .......................................................................................... 49
8.3.5 LED DeviceNet Master ....................................................................................... 50
8.3.6 LED DeviceNet Slave ......................................................................................... 50
8.3.7 LED CC-Link Slave............................................................................................. 51
8.4 LEDs Serial Protocols ...............................................................................................52
8.4.1 LED Modbus RTU .............................................................................................. 52
8.4.2 LED ASCII .......................................................................................................... 52
9 TECHNICAL DATA ................................................................................................... 53

9.1 Technical Data netTAP 50 Gateway .........................................................................53
9.2 Technical Data of Real-Time Ethernet Communication Protocols ............................55
9.2.1 EtherNet/IP Scanner (Master) Link .................................................................... 55
9.2.2 EtherNet/IP Adapter (Slave) ............................................................................... 56
9.2.3 Open Modbus/TCP ............................................................................................. 57
9.2.4 PROFINET IO-RT-Controller Link ...................................................................... 58
9.2.5 PROFINET IO-RT-Device .................................................................................. 59
9.3 Technical Data Fieldbus Protocols ...........................................................................60
9.3.1 CANopen Master Link ........................................................................................ 60
9.3.2 CANopen Slave .................................................................................................. 61
9.3.3 CC-Link Slave..................................................................................................... 62
9.3.4 DeviceNet Master Link ....................................................................................... 63
9.3.5 DeviceNet Slave ................................................................................................. 64
9.3.6 PROFIBUS DP Master Link ............................................................................... 65

Introduction 4/92
9.3.7 PROFIBUS DP Slave ......................................................................................... 66
9.4 Technical Data serial Protocols ................................................................................67
9.4.1 ASCII .................................................................................................................. 67
9.4.2 Modbus RTU Master/Slave ................................................................................ 68
10 WIRING INSTRUCTIONS ......................................................................................... 69

10.1 Assembly of D-Sub Connectors ................................................................................70
10.2 Ethernet ....................................................................................................................71
10.3 PROFIBUS ...............................................................................................................72
10.4 CANopen ..................................................................................................................74
10.5 DeviceNet .................................................................................................................75
10.6 CC-Link .....................................................................................................................77
10.7 RS-232 ......................................................................................................................79
10.8 RS-422 ......................................................................................................................80
10.9 RS-485 ......................................................................................................................82
11 DECOMMISSIONING/DISPOSAL............................................................................. 84
11.1 Put the Device out of Operation ................................................................................84
11.2 Disposal of Waste Electronic Equipment ..................................................................84
12 APPENDIX ................................................................................................................ 85
12.1 Legal Notes ...............................................................................................................85
12.2 Registered Trademarks ............................................................................................89
12.3 List of Figures ...........................................................................................................90
12.4 List of Tables ............................................................................................................90
12.5 Contacts ....................................................................................................................92

Introduction 5/92
1 Introduction
1.1 About the User Manual
This user manual describes the hardware, installation, commissioning, and
operation of the netTAP NT 50 series of gateways.
1.1.1 Obligation to read and understand the Manual

Important!
 To avoid personal injury and to avoid property damage to your system
or to your device, you must read and understand all instructions in the
manual and all accompanying texts to your device, before installing and
operating your device.
 First read the Safety Instructions in the safety chapter.
 Obey to all Safety Messages in the manual.
 Keep the product DVD providing the product manuals.
1.1.2 List of Revisions

Revision Date Chapter Revisions
14 2018-12-10 Firmware version V1.2
2.6.1 Section Power disconnect during firmware or configuration download
added.
2.6.3 Section Exceeding the maximum number of allowed write/delete ac-
cesses added.
3.4 Section Configuration Requirements updated.
9.1 Storage temperature: 40 °C … +85 °C
9.2, 9.3, 9.4 Sections updated.
15 2019-08-06 6.3 Section Resetting the NT50 to the factory setting added.
16 2021-06-22 4.3.2.5 Section X2 for Device Type NT 50-RS-EN: Note “no galvanic isolation”
added.
17 2022-04-27 9.1 Section Technical Data netTAP 50 Gateway: UKCA sign added.
18 2022-07-25 9.1 Section Technical Data netTAP 50 Gateway: Altitude added.
Table 1: List of Revisions

Introduction 6/92
1.1.3 Conventions in this Manual

Operation instructions, a result of an operation step or notes are marked as
follows:
Operation Instructions:
 <instruction>
or
1. <instruction>
2. <instruction>
Results:
 <result>
Notes:
Important: <important note>
Note: <note>
<note, where to find further information>
Numbering:
... reference to the figure used in that section. If the numbers refer-
ence to a section outside the current section then a cross reference to that
section and figure is indicated.

Introduction 7/92
1.2 Reference to Hardware, Software and Firmware

Hardware
Device Type Revision Port X2 Port X3
NT 50-CO-EN 2 CANopen Ethernet
NT 50-CO-RS 2 CANopen Ethernet + Serial
NT 50-CC-EN 2 CC-Link Ethernet
NT 50-CC-RS 2 CC-Link Ethernet + Serial
NT 50-DN-EN 2 DeviceNet Ethernet
NT 50-DN-RS 2 DeviceNet Ethernet + Serial
NT 50-DP-EN 2 PROFIBUS DP Ethernet
NT 50-DP-RS 2 PROFIBUS DP Ethernet + Serial
NT 50-RS-EN 2 Serial Ethernet
Table 2: Reference to Hardware
Software
Software Version
SYCON.net 1.500 or higher
Table 3: Reference to Software
Firmware
Firmware for the protocol conversion see section Protocol Conversions on
page 19.

Introduction 8/92
1.3 Contents of the Product DVD

The product DVD gateway solutions for the netTAP NT 50 contains:
• Setup program for the configuration and diagnostic software SYCON.net
and for the Ethernet Device Configuration software.
• Documentation
• Firmware
• Device Description Files (GSD, GSDML, EDS, ...)
• Video-Audio Tutorials
• Example projects for SYCON.net
1.3.1 Directory Structure of the DVD

All manuals on this DVD are delivered in the Adobe Acrobat® Reader for-
mat (PDF).
Directory Name Description
Documentation Documentation in the Acrobat® Reader Format (PDF)
Electronic Data Device Description File
Sheets (e.g. EDS,
GSD, GSDML)
Firmware Loadable Firmware
fscommand Files used during installation
Setups & Drivers Configuration and diagnostic software SYCON.net
USB Driver (not relevant for NT 50)
Debugger software for netSCRIPT (not relevant for NT 50)
Lua for Windows (not relevant for NT 50)
Supplements & Example projects for SYCON.net
Examples Example files for netSCRIPT (not relevant for NT 50)
Links to websites about Modbus
Device recovery (not relevant for NT 50)
Training & Po- Videos about commissioning
dcasts
Table 4: Directory Structure of the gateway solution DVD

Introduction 9/92
1.3.2 Device Description Files
The directory EDS on the DVD provides device description files for the
netTAP NT 50 device.
netTAP NT 50 as File name
CC-Link Slave nt50-cc-ccs_1.csp (for one Remote Device Station),
nt50-cc-ccs_2.csp (for two Remote Device Stations),
nt50-cc-ccs_3.csp (for three Remote Device Stations),
nt50-cc-ccs_4.csp (for four Remote Device Stations),
nt50-cc-ccs_io_1.csp (for one Remote IO Station)
CANopen Slave NT50_CO_COS.EDS
DeviceNet Slave NT50_DN_DNS.EDS
EtherNet/IP Adapter HILSCHER NT 50-EN EIS V1.1.EDS
PROFIBUS DP Slave HIL_0C99.GSD
PROFINET IO-Device GSDML-V2.2-HILSCHER-NT 50-EN PNS-20150106-
074400.xml
Table 5: Device Description Files for netTAP NT 50 on the DVD
The device description files are for the configuration of the used master.

Introduction 10/92
1.3.3 Documentation for netTAP NT 50

The following documentation overview gives information, for which items
you can find further information in which manual.
Note: Further information: All manuals listed in the overview below can be
found in the Documentation directory on the DVD delivered, in the Adobe
Acrobat® Reader format (PDF).
Basic documentation for netTAP NT 50

You always need the following documents:
Manual Contents Document Name
User Manual netTAP NT 50 netTAP NT 50 - Gateway Devices UM xx EN.pdf
Installation, Operation and Hardware (this manual)
User Manual Software Installation Software Installation - Gateway Solutions UM

Gateway Solutions xx EN.pdf
User Manual Ethernet Device Configuration Ethernet Device Configuration OI xx EN.pdf
Assignment of an IP Address for the netTAP
NT 50
Operating Instruc- Configuration of Gateway and Proxy Devices Configuration of Gateway and Proxy Devices
tion Manual netTAP, netBRICK and netLINK OI xx EN.pdf
Step by step description of the configuration of
the netTAP NT 50.
Configuration of the netTAP NT 50 as
EtherNet/IP Adapter,
Open Modbus/TCP,
PROFINET IO Device,
CANopen Slave,
CC-Link Slave,
DeviceNet Slave,
PROFIBUS DP Slave,
Modbus RTU Master/Slave,
ASCII.
Table 6: Basic Documentation for netTAP NT 50
netTAP NT 50 with EtherNet/IP Scanner/Master Link

You need the following additional documents, if you use the protocol
EtherNet/IP Scanner/Master on the gateway device:
Manual Contents Document name
Operating Instruc- DTM for EtherNet/IP Scanner devices EtherNetIP Scanner DTM OI xx EN.pdf
tion Manual
Operating Instruc- Generic DTM from EDS File EtherNet/IP EtherNetIP Generic Adapter DTM EDS OI xx EN.pdf
tion Manual Adapter Devices
Operating Instruc- Generic DTM for EtherNet/IP Adapter devices EtherNetIP Generic Adapter DTM OI xx EN.pdf
tion Manual
Table 7: Additional Documentation for netTAP NT 50 with EtherNet/IP Scanner/Master Link

Introduction 11/92
netTAP NT 50 with PROFINET IO Controller Link
PROFINET IO Controller on the gateway device:
Operating Instruc- DTM for PROFINET IO Controller devices PROFINET IO Controller DTM OI xx EN.pdf
tion Manual
Operating Instruc- Generic DTM for PROFINET IO Device devic- PROFINET IO Generic Device DTM IO xx EN.pdf
tion Manual es
Table 8: Additional Documentation for netTAP NT 50 with PROFINET IO Controller Link
netTAP NT 50 with CANopen Master Link

CANopen Master on the gateway device:
Operating Instruc- DTM for CANopen Master devices CANopen Master DTM OI xx EN.pdf
tion Manual
Operating Instruc- Generic DTM for CANopen Slave devices CANopen Generic Slave DTM OI xx EN.pdf
tion Manual
Table 9: Additional Documentation for netTAP NT 50 with CANopen Master Link
netTAP NT 50 with DeviceNet Master Link

DeviceNet Master on the gateway device:
Operating Instruc- DTM for DeviceNet Master devices DeviceNet Master DTM OI xx EN.pdf
tion Manual
Operating Instruc- Generic DTM for DeviceNet Slave devices DeviceNet Generic Slave DTM OI xx EN.pdf
tion Manual
Table 10: Additional Documentation for netTAP NT 50 with DeviceNet Master Link
netTAP NT 50 with PROFIBUS DP Master Link

PROFIBUS DP Master on the gateway device:
Operating Instruc- DTM for PROFIBUS DP Master devices PROFIBUS DP Master DTM OI xx EN.pdf
tion Manual
Operating Instruc- Generic DTM for PROFIBUS DP Slave devic- PROFIBUS DP Generic Slave DTM OI xx EN.pdf
tion Manual es
Table 11: Additional Documentation for netTAP NT 50 with PROFIBUS DP Master Link
netTAP NT 50 with ASCII

ASCII on the gateway device:
User Manual ASCII Handshake Mechanism ASCII – Handshake Mechanism UM xx EN.pdf
Table 12: Additional Documentation for netTAP NT 50 with ASCII

Safety 12/92
2 Safety
2.1 General Note
The user manual, the accompanying texts and the documentation are writ-
ten for the use of the products by educated personnel. When using the
products, all safety instructions and all valid legal regulations have to be
obeyed. Technical knowledge is presumed. The user has to assure that all
legal regulations are obeyed.
2.2 Intended Use

Devices described in this manual:
• NT 50-CC-EN,
• NT 50-CC-RS,
• NT 50-CO-EN,
• NT 50-CO-RS,
• NT 50-DN-EN,
• NT 50-DN-RS,
• NT 50-DP-EN,
• NT 50-DP-RS,
• NT 50-RS-EN,
are devices for communication and connect two communication networks.
The NT 50 devices work as a gateway between these two networks.
The NT 50 devices are in a compact housing and suitable for DIN rail
mounting according to DIN EN 60715.
The devices should be operated only in an environment appropriate to the
technical data.
2.3 Personnel Qualification

The netTAP NT 50 Gateway must only be installed, configured and re-
moved by qualified personnel. Job-specific technical skills for people pro-
fessionally working with electricity must be present concerning the following
topics:
• Safety and health at work
• Mounting and attaching of electrical equipment
• Measurement and Analysis of electrical functions and systems
• Evaluation of the safety of electrical systems and equipment
• Installing and Configuring IT
2.4 References Safety

[1] ANSI Z535.6-2006 American National Standard for Product Safety Information in
Product Manuals, Instructions, and Other Collateral Materials
[2] IEC 60950-1, Information technology equipment - Safety -
Part 1: General requirements,
(IEC 60950-1:2005, modified); German Edition EN 60950-1:2006
[3] EN 61340-5-1 and EN 61340-5-2 as well as IEC 61340-5-1 and IEC 61340-5-2

Safety 13/92
2.5 Safety Instructions to avoid Personal Injury

To ensure your own personal safety and to avoid personal injury, you nec-
essarily must read, understand and follow the following safety instructions
and all safety messages in this manual about danger causing personal inju-
ry, before you install and operate your netTAP NT 50 device.
2.5.1 Danger of unsafe System Operation

To prevent harm of persons, do not remove this device under runtime con-
ditions before you can not guarantee further a safe and secure operation of
the plant.

Safety 14/92
2.6 Safety Instructions to avoid Property Damage

To avoid property damage respectively device destruction of the netTAP
NT 50 device, you necessarily must read, understand and follow the follow-
ing safety instructions and all safety messages in this manual about danger
causing property damage, before you install and operate your netTAP
NT 50 device.
2.6.1 Power disconnect during firmware or configuration download

If during the process of downloading a firmware or configuration
• the power supply to the device is interrupted, or
• the power supply to a PC with the software application is interrupted, or
• a reset to the device is done,
this may lead to the following consequences:
Loss of device parameters, firmware corruption
• The firmware download or the configuration download is interrupted and
remains incomplete.
• The firmware or the configuration database will be corrupted and device
parameters will be lost.
• Device damage may occur as the device cannot be rebooted.
Whether these consequences occur depends on when the power discon-
nect occurs during the download.
 During configuration download process, do not interrupt the power sup-
ply to the PC or to the device, and do not perform a reset!
Otherwise you might be forced to send in your device for repair.
Power drop during write and delete accesses in the file system
The FAT file system in the netX firmware is subject to certain limitations in
its operation. Write and delete accesses in the file system (firmware up-
date, configuration download etc.) can destroy the FAT (File Allocation Ta-
ble) if the accesses cannot be completed if the power drops. Without a
proper FAT, a firmware may not be found and cannot be started.
Make sure that the power supply to the device is not interrupted during
write and delete accesses in the file system (firmware update, configuration
download, etc.).

Safety 15/92
2.6.2 Device Destruction by exceeding allowed Supply Voltage

Adhere for all netTAP NT 50 device described in this manual the instruction
hereafter:
The netTAP NT 50 may only be operated with the specified supply voltage.
Make sure that the limits of the allowed range for the supply voltage are not
exceeded. A supply voltage above the upper limit can cause severe dam-
age to the netTAP NT 50! A supply voltage below the lower limit can cause
malfunction in the netTAP NT 50. The allowed range for the supply voltage
is defined by the tolerances specified in this manual.
The data on the mandatory supply voltage for the netTAP NT 50 device
you find in the section System Requirements on page 20. There the re-
quired and permitted supply voltage for the netTAP NT 50 device is pro-
vided inclusively the permitted tolerance range.
2.6.3 Exceeding the maximum number of allowed write/delete ac-

cesses
This device uses a serial Flash chip for storing remanent data, such as
firmware, configuration, etc. This chip allows a maximum of 100 000
write/delete accesses which is sufficient for a standard device operation.
Writing/deleting the chip excessively (e.g. in order to change configuration
or name of station) will exceed the maximum number of allowed
write/delete accesses and, thus, result in damage to the device. If, e.g., the
configuration is changed every hour, the maximum number will be reached
after 11.5 years. If, e.g., it is changed every minute, the maximum number
will already be reached after approx. 69 days.
Avoid exceeding the maximum number of allowed write/delete accesses by
excessive writing.
2.6.4 Danger of unsafe System Operation

To prevent property damage, do not remove this device under runtime con-
ditions before you can not guarantee further a safe and secure operation of
the plant.

Safety 16/92
2.7 Labeling of Safety Messages

• The Section Safety Messages at the beginning of a chapter are pin-
pointed particularly. They are highlighted with a specific safety symbol
and a signal word according to the degree of endangerment. Inside the
safety message the danger is exactly named.
• The Integrated Safety Messages within a instruction description are
highlighted with a signal word according to the degree of endangerment
and possibly by an principle symbol. Inside the safety message the dan-
ger is exactly named.
Safety Sort of Warning or Principle
Symbol
Warning of Personal Injury and Property Damage Message
USA: Warning of Personal Injury
As in the scope of the ANSI Z535 Standard (for USA) instructions to a property damage message may
not contain a warning triangle, this property damage messages are listed separatly for the USA.
Warning of Damages by Electrostatic Discharge
Table 13: Safety Symbols and Sort of Warning or Principle
Signal Word Meaning Meaning (USA)

Indicates a Property Damage Message. Indicates a Property Damage Message.
Note Indicates an important note in the manual. Indicates an Important Note in the Manual.
Table 14: Signal Words
In this document all Safety Instructions and Safety Messages are designed
according both to the international used safety conventions as well as to
the ANSI Z535 standard, refer to reference safety [S1].

Description and Requirements 17/92
3 Description and Requirements

3.1 Device Description
The netTAP NT 50 devices described in this manual are communication
devices that are connecting two networks to each other. The NT 50 devices
are operating as gateway between both networks.
The netTAP NT 50 is a device with two interface ports. Its principle func-
tionality is illustrated in the figure below. The function of the device is de-
termined by the loaded firmware and the loaded configuration.
Figure 1: Function NT 50
The interface X2 is a fieldbus interface, the interface X3 may be an Ether-

net or a serial interface (RS).
The fieldbus interface X2 is located at the front of the device. The Ethernet
respectively the serial interface is located at the bottom of the device (X3).
Basically it is possible to connect either to port X2 or X3 to a host or to field
devices.
The netTAP NT 50 device is configured by a PC and the software SY-
CON.net. Online diagnosis is possible via the same interface. The Ethernet
interface of the netTAP NT 50 device is used for configuration and for diag-
nostic. This PC is a part of the Ethernet network.
Information about the configuration of the device with SYCON.net soft-
ware is in the manual Configuration of Gateway and Proxy Devices OI xx
EN.pdf on the product DVD in the directory Documentation.

The gateway functionality is determined by the loadable firmware.
The firmware buffers the cyclic send and receive data of the protocol at port
X2 and the protocol of port X3 internally. The configuration tool enables the
flexible mapping of the receive data of protocol X2 to send data of the pro-
tocol X3 and vice versa.
Status information of the protocol at port X2 can be mapped into the send
data of the protocol at port X3 and vice versa.
The firmware of netTAP NT 50 as gateway does not support acyclic com-
munications or services of the supported protocols.
If the device is operated in a bus system as a master, then exactly one
slave can be connected. Thus, for example for protocols with master func-
tionality the designation „PROFIBUS DP Master Link“ means, that one
PROFIBUS DP Slave can be connected.
3.2 Device Types and Protocol Conversions

3.2.1 Device Names
The descriptive device name of netTAP devices consists of the following
parts
1. Device Type netTAP 50

2. Network on port X2 (upper port on the device), in the example DP for
PROFIBUS DP.
3. Network on port X3 (port at the bottom of the device) , in the example
RE for Real-time Ethernet
The following communication systems are currently supported at the prima-

ry network X2:
Code 2 Supported Communication System
CC CC-Link
CO CANopen
DN DeviceNet
DP PROFIBUS DP
RS Serial (Modbus RTU or ASCII)
Table 15: Network on port X2 (Primary Network)
The following communication systems are currently supported at the sec-

ondary network X3:
Code 3 Supported Communication System
EN Ethernet (1* RJ45)
RS Serial (Modbus RTU or ASCII) (RJ45)
Table 16: Network on port X3 (Secondary Network)

3.2.2 Protocol Conversions
The following table lists the protocol conversion and the necessary netTAP
NT 50 device type.
Device Name Protocol at X2 Protocol at X3 Firmware File Firm-
ware
Version
NT 50-CC-EN CC-Link Slave EtherNet/IP Adapter/Slave N5CCSEIS.NXF 1.2
EtherNet/IP Scanner/Master (1) N5CCSEIM.NXF
PROFINET IO Device N5CCSPNS.NXF
PROFINET IO Controller (1) N5CCSPNM.NXF
Open Modbus/TCP N5CCSOMB.NXF
NT 50-CC-RS CC-Link Slave ASCII N5CCSASC.NXF
Modbus RTU Master / Slave N5CCSMBR.NXF
NT 50-CO-EN CANopen Master EtherNet/IP Adapter/Slave N5COMEIS.NXF
(for one slave) PROFINET IO Device N5COMPNS.NXF
Open Modbus/TCP N5COMOMB.NXF
CANopen Slave EtherNet/IP Adapter/Slave N5COSEIS.NXF
EtherNet/IP Scanner/Master (1) N5COSEIM.NXF
PROFINET IO Device N5COSPNS.NXF
PROFINET IO Controller (1) N5COSPNM.NXF
Open Modbus/TCP N5COSOMB.NXF
NT 50-CO-RS CANopen Master ASCII N5COMASC.NXF
(for one slave) Modbus RTU Master / Slave N5COMMBR.NXF
CANopen Slave ASCII N5COSASC.NXF
Modbus RTU Master / Slave N5COSMBR.NXF
NT 50-DN-EN DeviceNet Master EtherNet/IP Adapter/Slave N5DNMEIS.NXF
(for one slave) PROFINET IO Device N5DNMPNS.NXF
Open Modbus/TCP N5DNMOMB.NXF
DeviceNet Slave EtherNet/IP Adapter/Slave N5DNSEIS.NXF
EtherNet/IP Scanner/Master (1) N5DNSEIM.NXF
PROFINET IO Device N5DNSPNS.NXF
PROFINET IO Controller (1) N5DNSPNM.NXF
Open Modbus/TCP N5DNSOMB.NXF
NT 50-DN-RS DeviceNet Master ASCII N5DNMASC.NXF
(for one slave) Modbus RTU Master / Slave N5DNMMBR.NXF
DeviceNet Slave ASCII N5DNSASC.NXF
Modbus RTU Master / Slave N5DNSMBR.NXF
NT 50-DP-EN PROFIBUS DP Master EtherNet/IP Adapter/Slave N5DPMEIS.NXF
(for one slave) PROFINET IO Device N5DPMPNS.NXF
Open Modbus/TCP N5DPMOMB.NXF
PROFIBUS DP Slave EtherNet/IP Adapter/Slave N5DPSEIS.NXF
EtherNet/IP Scanner/Master (1) N5DPSEIM.NXF
PROFINET IO Device N5DPSPNS.NXF
PROFINET IO Controller (1) N5DPSPNM.NXF
Open Modbus/TCP N5DPSOMB.NXF
NT 50-DP-RS PROFIBUS DP Master ASCII N5DPMASC.NXF
(for one slave) Modbus RTU Master / Slave N5DPMMBR.NXF
PROFIBUS DP Slave ASCII N5DPSASC.NXF
Modbus RTU Master / Slave N5DPSMBR.NXF
NT 50-RS-EN ASCII EtherNet/IP Adapter/Slave N5ASCEIS.NXF
Ethernet/IP Scanner/Master (1) N5ASCEIM.NXF
PROFINET IO Device N5ASCPNS.NXF
PROFINET IO Controller (1) N5ASCPNM.NXF
Open Modbus/TCP N5ASCOMB.NXF
Modbus RTU Master/Slave EtherNet/IP Adapter/Slave N5MBREIS.NXF
EtherNet/IP Scanner/Master (1) N5MBREIM.NXF
PROFINET IO Device N5MBRPNS.NXF
PROFINET IO Controller (1) N5MBRPNM.NXF
Open Modbus/TCP N5MBROMB.NXF
Table 17: List of Protocol Conversion and NT 50 Device Type
3.3 System Requirements

The netTAP NT 50 device must be mounted on a DIN-rail according to DIN
EN 60715.
A suitable power supply is required. The voltage to be applied must be in
the allowed range 24 V ± 6 V DC. The power supply must be able to deliver
at least a current of 100 mA at 24 V.
Power supply is possible via pins 1 (GND) and 2 (24V) of the netTAP NT
50 power supply connector located on the upper side of the device.
Device Destruction!
 The voltage must not exceed 30 V significantly, otherwise the device
may be destroyed or damaged.
In order to avoid damage caused by overheating or freezing, it is necessary

that the temperature of the device does not exceed the limits of the allowed
temperature range.
The following preconditions must additionally be met in order to operate the
Gateway device successfully:
1. The Gateway device must have been provided with the correctly suiting
firmware.
2. The Gateway device must have been configured correctly using the
SYCON.net configuration software.

3.4 Configuration Requirements

The configuration software SYCON.net must be installed on a PC. The re-
quirements for the PC are:
• PC with 1 GHz processor or higher
• Windows® 7 (32-Bit and 64-Bit) SP1,
Windows® 8 (32-Bit and 64-Bit),
Windows® 8.1 (32-Bit and 64-Bit),
Windows® 10 (32-Bit and 64-Bit)
• Administrator privilege required for installation
• Microsoft .NET Framework 4.0
• Internet Explorer 5.5 or higher
• Free disk space: min. 400 MByte
• RAM: min. 512 MByte, recommended 1024 MByte
• Graphic resolution: min. 1024 x 768 pixel
• Keyboard and Mouse
• USB interface
• Restriction: Touch screen is not supported.
Note: If the project file is used on a further PC,

 this PC must also comply with the above system requirements,
 the device description files of the devices used in the project must be
imported into the configuration software SYCON.net on the new PC,
 and the DTMs of the devices used in the project must also be installed
on that further PC.
In order to download the product DVD, you need an Internet access.

Device Drawings and Connections 22/92
4 Device Drawings and Connections

4.1 Device and Dimensioned Drawings
Side view Front view
with Combicon con- with D-Sub male with D-Sub female

nector connector connector
Bottom View
with RJ45 Socket with RJ45 Socket with RJ45 Socket

Device type NT 50-CC-EN NT 50-CO-EN NT 50-DP-EN
NT 50-CC-RS NT 50-CO-RS NT 50-DP-RS
NT 50-DN-EN NT 50-RS-EN
NT 50-DN-RS
Figure 2: Device Drawings
In the drawing above:

X1 Connector for Power Supply
X2 and X3 Communication interfaces
Dimensions of the power supply plug X1 in mm

4.2 Positions of LEDs and Control Elements

Meaning of the elements
Connector X1 for power supply

SYS-LED
APL-LED
COM-LED
LED, depends on protocol at X2
LED, depends on protocol at X2
Rotary address switch, factor 10
Rotary address switch, factor 1
The address switches can be activated with

SYCON.net version 1.351 (or higher) and can
be used with firmware version 1.1 (or higher)
for PROFIBUS DP Slave, DeviceNet Slave,
CANopen Slave and CC-Link Slave.
Section Range of Values for the Address
Switches on this page lists the range of values
for each protocol.
LED, green, LINK at X3

LED, yellow, ACT respectively Rx/Tx
(activity) at X3
Figure 3: LEDs and Control Elements
4.2.1 Range of Values for the Address Switches

Protocol Valid range of values
PROFIBUS DP Slave 0 … 99 (station address)
DeviceNet Slave 0 … 63 (MAC ID)
CANopen Slave 0 … 99 (Node ID)
Protocol Valid range of values Number of Stations
CC-Link Slave 1 … 64 1 The number of sta-
tions depends on the
1 … 63 2
configuration
1 … 62 3
1 … 61 4
Figure 4: Range of Values for the Address Switches

4.3 Connections
4.3.1 X1 Top Connection
The power supply of the netTAP 50 device has to be connected to the
power connector X1 . The power supply voltage must be in the range be-
tween 18 V and 30 V DC. The plug is included in delivery.
Supply Voltage Pin Assignment
Supply Volta- Pin Signal Description
ge
1 0V/ Ground of supply voltage
GND
Mini Combicon 2 24 V +24 V supply voltage
Table 18: Supply Voltage Pin Assignment
4.3.2 X2 Front Connection

4.3.2.1 X2 for Device Type NT 50-CO-xx
CANopen Pin Assignment
CANopen Pin Signal Description
2 CAN L CAN Low bus line
3 ISO CAN ground
GND
7 CAN H CAN High bus line
1, 4, 5,
Important note and strongly
9-pole 6, 8, 9
recommended: Leave these pins
sub-D male.
unconnected! Otherwise there is
a high risk of a device damage.
Shield PE Metal shell on PE
Table 19: CANopen Pin Assignment
Please note the wiring instructions in section CANopen on page 74.
4.3.2.2 X2 for Device Type NT 50-CC-xx

CC-Link Pin Assignment
CC-Link Pin Signal Description
1 DA Data positive
2 DB Data negative
3 DG Data ground
4 SLD Shield, internally connected to common ground
5 FG Field ground, internally connected to common
ground
Socket, female
Table 20: CC-Link Pin Assignment
Please note the wiring instructions in section CC-Link on page 77.

4.3.2.3 X2 for Device Type NT 50-DN-xx

DeviceNet Pin Assignment
DeviceNet Pin Signal Description
1 ISO GND Common ground
DeviceNet-power supply.
2 CAN L CAN Low signal
3 Drain Shield
4 CAN H CAN High signal
COMBICON 5 V+ +24 V DeviceNet-power supply

Socket, female
Table 21: DeviceNet Pin Assignment
Please note the wiring instructions in section DeviceNet on page 75.

4.3.2.4 X2 for Device Type NT 50-DP-xx
RS-485 PROFIBUS Pin Assignment
PROFIBUS Pin Signal Description
3 Rx/Tx + Receive- / Transmit data positive
4 CNTR-P Control signal for repeater (direction control)
5 ISO GND Data ground
6 VP Power supply positive
8 Rx/Tx - Receive- / Transmit data negative
9-pole sub-D
socket,
female
Table 22: PROFIBUS RS-485 Pin Assignment
A pull up resistor of 100 kΩ is connected device internally at “Rx / Tx +“.

A pull down resistor of 100 kΩ is connected device internally at “Rx / Tx -“.
Please note the wiring instructions in section PROFIBUS on page 72.

4.3.2.5 X2 for Device Type NT 50-RS-EN
Device Damage!
 Make sure that the NT 50 device and the remote device (via RS-232,
RS-422 respectively RS-485) have the same potential. Otherwise a
compensating current may cause device damage, because the serial in-
terface of the NT 50 device has no galvanic isolation to its power sup-
ply.
RS-232 Pin Assignment

RS-232 Pin Signal Description
1 GND Reference potential, ground of power supply
6 RxD Receive data
8 TxD Transmit data
9-pole sub-D sock-

et, male
Table 23: RS-232 Pin Assignment
Please note the wiring instructions in section RS-232 on page 79.

4 RxD + Receive data positive
5 RxD - Receive data negative
6 TxD + Transmit data positive
8 TxD - Transmit data negative
9-pole sub-D sock-
et, male
A pull up resistor of 10 kΩ is connected device internally at “RxD +“.

A pull down resistor of 10 kΩ is connected device internally at “RxD -“.


4 RxD/TxD+ Receive data / Transmit data positive
5 RxD/TxD- Receive data / Transmit data negative
9-pole sub-D sock-

et, male
A pull up resistor of 10 kΩ is connected device internally at “RxD/TxD +“.

A pull down resistor of 10 kΩ is connected device internally at “RxD/TxD -“.

4.3.3 X3 Bottom Connection

4.3.3.1 X3 for Device Type NT 50-xx-EN
Ethernet on RJ45 Pin Assignment
Ethernet Pin Signal Description
1 TX+ Transmit data positive
2 TX– Transmit data negative
3 RX+ Receive data positive
4 Term 1 Connected and terminated to PE via RC
combination*
5 Term 1
6 RX– Receive data negative
7 Term 2 Connected and terminated to PE via RC
RJ45 socket, fe- combination*
male 8 Term 2
* Bob Smith Termination
Table 26: Ethernet RJ45 Pin Assignment
Important: Please note for the use of hubs and switches the wiring in-
structions in section Ethernet on page 71.
4.3.3.2 X3 for Device Type NT 50-xx-RS

For this device type, the Ethernet interface is required for the configuration
of the device. It may be necessary for diagnostic purpose to use a Y cable,
which separates the serial interface (RS) and the Ethernet interface.
Device Damage!
 Make sure that the NT 50 device and the remote device (via RS-232,
RS-422 respectively RS-485) have the same potential. Otherwise a
compensating current may cause device damage, because the serial in-
terface of the NT 50 device has no galvanic isolation to its power sup-
ply.
Device Damage!
 Make sure that only a 4-wire Ethernet cable is used (with pin 1, 2, 3 and
6), if no Y cable for separation of the Ethernet and serial interface is
used. On pin 4, 5, 7 and 8 on the NT 50 device are the signals for the
serial interface. If you transfer these signal via an Ethernet cable to the
connected device (e. g. to a switch) this may cause a device damage of
the used devices.

RS-232 and Ethernet on RJ45 Pin Assignment

1 Ethernet TX+ Transmit data positive *
2 Ethernet TX– Transmit data negative *
3 Ethernet RX+ Receive data positive *
4 RS232 3,3 V Data potential 'High', not usable as power
supply. Ri appr. 300 Ω.
5 RS232 GND Data reference potential, ground of power
supply
6 Ethernet RX– Receive data negative *
7 RS232 TxD Transmit data
RJ45 socket, fe-
8 RS232 RxD Receive data
male
PE Metal case on PE
Table 27: RJ45 Ethernet / RS-232 Pin Assignment
The figure on the right shows a Y

cable adapter for the separation of
the RS-232 and the Ethernet signal
lines.
Make sure that there is no interrup-
tion of the shield connection when
preparing the cable.
Make sure that the TxD signal of
one device is connected to the RxD
signal of the other device for a RS-
232 connection.
An Ethernet connection is neces-
sary for configuration and diagnos-
tic.
You can use a direct cable con-

nection to the RS-232 remote
device as shown on the right.
An Ethernet cable is required for
configuration of the device as
shown on the left, which has to be
plugged into the X3 RJ45 socket
instead of the RS-232 cable dur-
ing configuration of the NT 50
device.
Diagnostic is not possible while
the RS-232 interface is used with
the cable shown at the right.


2 Ethernet TX– Transmit data negative *
4 RS422 RxD - Receive data negative
5 RS422 RxD + Receive data positive
7 RS422 TxD - Transmit data negative
8 RS422 TxD + Transmit data positive
RJ45 socket, fe-
male PE Metal housing on PE

lines.
Make sure that the TxD+ signal of
one device is connected to the
RxD+ signal of the other device for
a RS-422 connection. Make sure
that the TxD- signal of one device is
connected to the RxD- signal of the
other device for a RS-422 connec-
tion.

device.


2 Ethernet TX– Transmit data negative
4 RS485 RxD/TxD - Receive data / Transmit data negative
5 RS485 RxD/TxD + Receive data / Transmit data positive
7 not used
8 not used
RJ45 socket, fe-
male PE metal housing on PE
* Bob Smith Abschluss

lines.
Make sure that the RxD/TxD+ sig-
nal of one device is connected to
the RxD/TxD+ signal of the other
device for a RS-485 connection.
Make sure that the RxD/TxD- signal
of one device is connected to the
RxD/TxD- signal of the other device
for a RS-485 connection.

device.

4.4 Schematic Diagram - Galvanic Isolation

The following schematic diagrams illustrate the internal connection between
the different connectors. This gives you the chance to properly install the
device in accordance with the potential equalization concept of your plant.
Note: The PE connection (potential equalization) of the device is done via

the DIN rail.
4.4.1 Galvanic Isolation of NT 50-xx-EN Devices

The device types NT 50-CC-EN, NT 50-CO-EN, NT 50-DP-EN and
NT 50-DN-EN has three galvanically isolated areas. The coupling to PE is
shown in the following figure and in the following table.
Figure 5: Galvanic Isolation of NT 50-xx-EN Devices
Area
galv. Iso- Coupling against PE
Con- Protocol Coupling Functional earthing to PE
lation potential
nection
-
HF Cf = 10 nF / 500 V,
X1 no Lf = 47 μH -
Cx1 4 * 10 nF / 500 V
CC-Link inductive Cx2 3,3 nF / 1000 V directly to Combicon Pin 4

X2 directly via the metal con-
CANopen optically Cx2 1 MΩ // 15 nF / 1000 V
nection of the D-Sub-male
connector
DeviceNet optically Cx2 1 MΩ // 15 nF / 1000 V 1 MΩ // 15 nF 1000 V

Combicon Pin 3
directly via the metal con-
Profibus DP inductive Cx2 1 MΩ // 2,2 nF/ 1000 V
nection of the D-Sub female
connector
Directly via the metal con-
Ethernet inductive Cx3 6 * 75 Ω, 1 nF / 2000 V
nection of RJ 45 sockets
X3
Table 30: Coupling NT 50-xx-EN Devices

4.4.2 Galvanic Isolation of NT 50-xx-RS

The device types NT 50-CC-RS, NT 50-CO-RS, NT 50-DN-RS and
NT 50-DN-RS has three galvanically isolated areas. The coupling to PE is
shown in the following figure and in the following table.
Figure 6: Galvanic Isolation of NT 50-xx-RS Devices
Area
galv. Iso- Coupling against PE Functional earthing to
Connec- Protocol Coupling
lation potential PE
tion
HF Cf = 10 nF / 500 V,
X1 - no Lf = 47 μH no
Cx1 4 * 10 nF / 500 V
CC-Link inductive Cx2 3,3 nF / 1000 V directly

X2
CANopen optisch Cx2 1 MΩ // 15 nF / 1000 V directly via the metal
connection of the D-Sub
male connector
DeviceNet optically Cx2 1 MΩ // 15 nF / 1000 V Combicon Pin 3

1 MΩ // 15 nF 1000V
Profibus DP inductive Cx2 1 MΩ // 2,2 nF / 1000 directly via the metal

V connection of the D-Sub
female connector
Directly via the metal
Ethernet, inductive Cx3 2 * 75 Ω, 1 nF / 2000 V
connection of RJ 45
only for diag-
X3 Teil sockets
nostic
RS232 Directly via the metal
RS422 connection of RJ 45
X3 Teil RS485 no sockets
Table 31: Coupling NT 50-xx-RS Devices

4.4.3 Galvanic Isolation of NT 50-RS-EN

The device type NT 50-RS-EN has three galvanically isolated areas. The
coupling to PE is shown in the following figure and in the following table.
Figure 7: Galvanic Isolation of NT 50 -RS-EN Devices
Area
galv. Isola- Coupling against PE Functional earthing to
Connec- Protocol Coupling
tion potential PE
tion
-
HF Cf = 10 nF / 500 V,
X1 no Lf = 47 μH no
Cx1 4 * 10 nF / 500 V
RS232 HF Cf = 10 nF, directly via the metal

X2 RS422 Lf = 47 μH connection of the D-Sub
no female connector
RS485
Cx1 4 * 10 nF / 500 V
Directly via the metal
Ethernet inductive Cx3 6 * 75Ω + 10 nF / 2000 V
connection of RJ 45
X3
sockets
Table 32: Coupling NT 50-RS-EN Devices

NT 50 Mounting and Dismounting 35/92
5 NT 50 Mounting and Dismounting

The devices can be mounted side-by-side without any gap. On the top side,
the devices should have a minimum distance of 20 mm to the next device.
The air ventilation slots of the device must not be covered by any objects.
5.1 DIN Top Hat Rail Mounting of the NT 50

Mount the top hat rail according to DIN EN 60715 for the netTAP device
horizontally at the intended location. The DIN top hat rail has to be con-
nected with the potential equalization conductor (PE).
Push the device onto the top hat rail

from above .
Then press the device against the
mounting surface, according to ar-
row .
Figure 8: Mounting the netTAP NT 50 device onto the top-hat rail
Afterwards connect the 24 V supply voltage to the device. Grounding is

done via a grounding contact located at the backside of the device connect-
ing it electrically to the top-hat rail.
5.2 Removing the NT 50 from the DIN Top Hat Rail

In order to remove the netTAP from the top-hat rail, first remove the power
supply cable and all data cables from the device.
To release the device from the top-

hat rail, use a screw driver, which
you put at the clip in the center of
the device. By pressing slightly the
screw driver in direction of arrow
the lock at the top-hat rail is re-
leased. You can then easily pull the
device off the top-hat rail in direction
of arrow .
Figure 9: Removing the NT 50 device from the Top-Hat Rail

Commissioning 36/92
6 Commissioning
6.1 Load Firmware and Configuration
The device delivered without loaded firmware and configuration.
It is necessary that a firmware and configuration is loaded into the device
for commissioning.
The device can be configured before or after mounting via the RJ45 Ether-
net interface at the bottom of the device. A PC with SYCON.net software is
necessary for configuration.
For communication from SYCON.net software to the netTAP NT 50 device
via Ethernet, it is necessary to assign an IP address to the netTAP NT 50
device. This is done with the Ethernet Device Setup Software, which is in-
stalled together with SYCON.net software.
Information about this is in the manual Configuration of Gateway and

Proxy Devices OI xx EN.pdf on the product DVD in the directory Docu-
mentation.
Note: The IP address, which was set with the Ethernet Device Setup
Software, is set permanently. A PROFINET IO Controller may change
this IP address.
6.1.1 Download Configuration Files from the PC

1. The configuration can be created and saved offline with or without real
device on a standard PC with the software SYCON.net. The configura-
tion can be downloaded into the device in two steps afterwards
2. The selected firmware and configuration has to be transferred in two
steps via an Ethernet connection into the device.
The configuration is stored in the device in a non-volatile flash memory.
Once set the data will be available after each power cycle.
These steps are described in the operating instruction manual Configu-
ration of Gateway and Proxy Devices OI xx EN.pdf.
So it is possible to transfer the configuration into the device before or after
mounting the device at its place of use.
Information about this is in the manual Configuration of Gateway and

Proxy Devices OI xx EN.pdf on the product DVD in the directory „Docu-
mentation“.
Important: Do not interrupt the communication during the download of

the firmware into the netTAP NT 50 device.
If the communication to the netTAP NT 50 device is interrupted during
download of the firmware, the power supply for the device must not
switch off till the next complete download of the firmware into the device,
because otherwise the functionality of the device is destroyed. Then the
device has to be send back for repair to the manufacturer.

Commissioning 37/92
6.1.2 Potential Differences for Device Types NT 50-xx-RS and NT 50-

RS-EN
Device Destruction!
Make sure that for the NT 50-xx-RS and the NT 50-RS-EN device and
the remote device (via RS-232, RS-422 respectively RS-485) have the
same potential. Otherwise a compensating current may cause device
damage, because the serial interface of the NT 50 device has no galvan-
ic isolation to its power supply.
6.2 Start-up Behavior

The firmware and the configuration data are loaded from the FLASH
memory into the RAM of the NT 50 device after return of the power supply
and subsequently the firmware is started. This process can take several
seconds (appr. 4 seconds) depending on the size of the configuration data.

Commissioning 38/92
6.3 Resetting the NT50 to the factory setting

Firmware and base firmware have a function to reset the NT 50 device to
the factory setting.
The function "Reset to factory setting" formats the file system and deletes
all firmware and configuration data files. After switching the NT 50 device
off and on again, the firmware will restart with the factory setting.
Prerequisites
In order to be able to use the function "Reset to factory setting", the NT 50
device must have the following firmware version:
• Base firmware V1.2.0.0 (or higher), if only a base firmware is in the the
NT 50 device.
Or
• Base firmware V1.2.0.0 (or higher) and firmware V1.2.0.0 (or higher)
The NT 50 device recognizes the function "Reset to factory setting" only if
• the rotary switches are set to 90 with power-on and
• the setting is performed within 15 s after power-on.
Steps required to reset the NT50 to the factory setting

To reset the NT 50 deviec to the factory setting, use rotary switches and
to set the following sequence of values after power-on:
90 → 99 → 90 → 91 → 90.
 Switch the NT 50 power supply off.
 Set rotary switch to 9.
 Switch the NT 50 power supply on.
 Set rotary switch back to 0.
 Set rotary switch back to 0.
 If the NT 50 device has recognized the sequence, the device is reset to
factory setting now.
If the NT 50 device has not recognized the sequence or rotary switch
is not changed within 15 s after power-on, the NT 50 deviec will use val-
ue 90 as the address.

Troubleshooting 39/92
7 Troubleshooting
Two methods for troubleshooting exist:
• The visual analysis of the LED conditions of the device
• The analysis via the Ethernet port along with the configuration tool SY-
CON.net.
The following overview describes the error conditions that may be detected
by a visual check of the LEDs.
In order to find the correct position of the LEDs please follow the chapter
Positions of LEDs and Control Elements from page 23. The numbers in the
column LED state is referencing the position number in the device drawing.
LED state Remedy
No LED is on The device is not powered or the device has a malfunction and needs replace-
ment.
After a power cycle the device has not found a valid firmware and remains in
SYS LED flashes
bootloader mode. The device has to be send back to the manufacturer for re-
yellow/green at 1 Hz
pair.
The device has a malfunction and needs replacement.
SYS LED is permanet yel-
low
The device has not found a firmware. The device has to be send back to the
SYS LED flashes yellow
manufacturer for repair.
after Power On
SYS LED is permanet The device is well initialized. Further analysis is possible with the LED APL.
green, Follow the chapter System LEDs on page 41.
APL LED on red flashing or
red on
The communication via port X2 or/and port X3 is not in data exchange mode.
APL LED flashing green
See chapter System LEDs on page 41.
Table 33: NT 50 Troubleshooting
The device is operational just in case the illustrated error conditions do not
met. Further protocol specific error diagnostics via the LEDs is possible by
reading on the chapter “LEDs”
In deep diagnostics is possible at any time via the Ethernet diagnostic port
of the device and a PC with the software SYCON.net.
In case of trouble you should make sure that you have downloaded a cor-
rect signal mapping to the device via SYCON.net
For some protocols it is necessary to synchronize data via a handshake be-
tween the gateway and the superordinated PLC. Please make sure that the
handshake mechanism is kept.

Troubleshooting 40/92
7.1 Failure in 10 MBit/s Half Duplex Mode and Workaround

Only devices NT 50-xx-EN respectively NT 50 xx-RS are affected that were
produced before 2011 and have a serial number below the serial number
listed in the following table:
Device Type NT 50 Serial Number below
NT 50-CC-EN 20023
NT 50-CC-RS 20022
NT 50-CO-EN 20023
NT 50-CO-RS 20019
NT 50-DN-EN 20019
NT 50-DN-RS 20019
NT 50-DP-EN 20025
NT 50-DP-RS 20026
NT 50-RS-EN 20023
Affected Hardware
Hardware with the communication controller netX 50, netX 100 or
netX 500; netX/Internal PHYs.
When can this Failure occur?

When using standard Ethernet communication with 10 MBit/s half duplex
mode, the PHY gets stuck in case of network collisions. Then no further
network communication is possible. Only device power cycling allows
Ethernet communication again.
This problem can only occur with Ethernet TCP/UDP IP, EtherNet/IP or
Modbus TCP protocols when using hubs at 10 MBit/s. The issue described
above is not applicable for protocols which use 100 MBit/s or full duplex
mode.
Solution / Workaround:
Do not use 10 MBit/s-only hubs. Use either switches or 10/100 MBit/s Dual
Speed hubs, to make sure the netX Ethernet ports are connected with 100
MBit/s or in full duplex mode.
This erratum is fixed with all components of the ‘Y’ charge (9 digit charge
number shows ‘Y’ at position 5 (nnnnYnnnn).
Reference
“Summary of 10BT problem on EthernetPHY”,
RenesasElectronics Europe, April 27, 2010

LEDs 41/92
8 LEDs
8.1 System LEDs
LED Color State Meaning
SYS Duo LED yellow/green
(green) On Operating System running. further diagnostic

see APL LED.
(yel- On This state may occur only briefly.

low) If this LED stays permanently yellow, then a
hardware failure is possible.
Flashing Error state! Boot loader active.
(yellow yellow/green
/green)
Off Power supply for the device is missing or
(off)
hardware failure.

APL Duo LED red/green
On The communication on X2 and X3 is in cyclic
(green) data exchange and the gateway function is
executed
Blinking with netTAP is initialized, but the communication
(green) 2 s off, on X2 is not in cyclic data exchange.
0,5 s on
Blinking with netTAP is initialized, but the communication
(green) 2 s off, on X3 is not in cyclic data exchange.
0,5 s on,
0,5 s off,
0,5 s on,
Blinking with netTAP is initialized, but the configuration for
(red) 2 s off, the communication protocol on X2 is missing
0,5 s on or has an error
Blinking with netTAP is initialized, but the configuration for
(red) 2 s off, the communication protocol on X3 is missing
0,5 s on, or has an error
0,5 s off,
0,5 s on,
On netTAP has detected an error during the ini-
(red) tialization: Missing configuration, error in con-
figuration or internal error
Figure 10: LEDs

LEDs 42/92
8.2 LEDs Real Time Ethernet Protocols

8.2.1 LEDs EtherNet/IP Scanner (Master)
The subsequent table describes the meaning of the LEDs for the Real-Time
Ethernet device when the firmware of the EtherNet/IP Scanner (Master)
protocol is loaded to the device.
MS Duo LED red/green
Number in On Device operational: If the device is operating correctly, the module status
(green)
the device indicator shall be steady green.
drawing:
(green) Flashing Standby: If the device has not been configured, the module status indicator
shall be flashing green.
(red) On Major fault: If the device has detected a non-recoverable major fault, the
module status indicator shall be steady red.
(red) Flashing Minor fault: If the device has detected a recoverable minor fault, the mod-
ule status indicator shall be flashing red. NOTE: An incorrect or inconsistent
configuration would be considered a minor fault.
Flashing Self-test: While the device is performing its power up testing, the module
(red/green) status indicator shall be flashing green/red.
(off) Off No power: If no power is supplied to the device, the module status indicator
shall be steady off.
NS Duo LED red/green
Number in On Connected: If the device has at least one established connection (even to
(green)
the device the Message Router), the network status indicator shall be steady green.
drawing:
(green) Flashing No connections: If the device has no established connections, but has
obtained an IP address, the network status indicator shall be flashing green.
(red) On Duplicate IP: If the device has detected that its IP address is already in use,
the network status indicator shall be steady red.
(red) Flashing Connection timeout: If one or more of the connections in which this device
is the target has timed out, the network status indicator shall be flashing red.
This shall be left only if all timed out connections are reestablished or if the
device is reset.
Flashing Self-test: While the device is performing its power up testing, the network
(off) Off Not powered, no IP address: If the device does not have an IP address (or
is powered off), the network status indicator shall be steady off.
LINK/RJ45 LED green
Number in
(green) On A connection to the Ethernet exists
the device
drawing: (off) Off The device has no connection to the Ethernet
ACT/RJ45 LED yellow

Number in
(yellow) Flashing The device sends/receives Ethernet frames
the device
drawing
Table 34: LEDs EtherNet/IP Scanner (Master)

LEDs 43/92
8.2.2 LEDs EtherNet/IP Adapter (Slave)

Ethernet device when the firmware of the EtherNet/IP Adapter (Slave) pro-
tocol is loaded to the device.
MS Duo LED red/green
Number in
the device (green) On Device operational: If the device is operating correctly, the module status
drawing: indicator shall be steady green.
(green) Flashing Standby: If the device has not been configured, the module status indicator
shall be flashing green.
(red) On Major fault: If the device has detected a non-recoverable major fault, the
module status indicator shall be steady red.
(red) Flashing Minor fault: If the device has detected a recoverable minor fault, the mod-
ule status indicator shall be flashing red. NOTE: An incorrect or inconsistent
configuration would be considered a minor fault.
Flashing Self-test: While the device is performing its power up testing, the module
(off) Off No power: If no power is supplied to the device, the module status indicator
shall be steady off.
NS Duo LED red/green
Number in On Connected: If the device has at least one established connection (even to
(green)
the device the Message Router), the network status indicator shall be steady green.
drawing:
(green) Flashing No connections: If the device has no established connections, but has
obtained an IP address, the network status indicator shall be flashing green.
(red) On Duplicate IP: If the device has detected that its IP address is already in use,
the network status indicator shall be steady red.
(red) Flashing Connection timeout: If one or more of the connections in which this device
is the target has timed out, the network status indicator shall be flashing red.
This shall be left only if all timed out connections are reestablished or if the
device is reset.
Flashing Self-test: While the device is performing its power up testing, the network
(off) Off Not powered, no IP address: If the device does not have an IP address (or
is powered off), the network status indicator shall be steady off.
LINK/RJ45 LED green
Number in
the device
drawing: (off) Off The device has no connection to the Ethernet
ACT/RJ45 LED yellow

Number in
the device
drawing:
Table 35: LEDs EtherNet/IP Adapter (Slave)

LEDs 44/92
8.2.3 LEDs Open Modbus/TCP

Ethernet device when the firmware of the Open Modbus/TCP protocol is
loaded to the device.
RUN Duo LED red/green
Number Off Not Ready
(off)
in the OMB task is not ready
device
drawing (green) Flashing cyclic Ready, not configured yet
with 1Hz OMB task is ready and not configured yet
(green) Flashing cyclic Waiting for Communication:
with 5Hz OMB task is configured
(green) On Connected:
OMB task has communication – at least one TCP connection is es-
tablished
ERR Duo LED red/green
Number Off No communication error
(off)
in the
device (red) Flashing cyclic System error
drawing: with 2Hz
(On/Off Ratio =
25 %)
(red) On Communication error active
LINK/RJ LED green

Number
in the
device (off) Off The device has no connection to the Ethernet
drawing:
ACT/RJ LED yellow

Number
in the
device
drawing:
Table 36: LEDs Open Modbus/TCP

LEDs 45/92
8.2.4 LEDs PROFINET IO Controller

Ethernet device when the firmware of the PROFINET IO-RT Controller pro-
tocol is loaded to the device.
SF Duo LED red/green
Name in the (red) On (together with BF „red ON“)
device draw- No valid Master license
ing: Flashing cy- System error: Invalid configuration, Watchdog error or internal error
(red)
clic at 2 Hz
(off) Off No error
BF Duo LED red/green

Name in the (red) On No Connection: No Link.
device draw- or (together with SF „red ON“)
ing: No valid Master license
(red) Flashing cy- Configuration fault: not all configured IO-Devices are connected.
clic at 2 Hz
(off) Off No error
LINK LED green
RJ45
On A connection to the Ethernet exists
(green)
(off) Off The device has no connection to the Ethernet
RX/TX LED yellow

RJ45
(yel- Flashing The device sends/receives Ethernet frames
low)
Table 37: LEDs PROFINET IO-RT Controller

LEDs 46/92
8.2.5 LEDs PROFINET IO-RT-Device

Ethernet device when the firmware of the PROFINET IO-RT-Device proto-
col is loaded to the device.
SF Duo LED red/green
Number in On Watchdog timeout; channel, generic or extended diagnosis present; sys-
(red)
the device tem error
drawing:
(red) Flashing DCP signal service is initiated via the bus
cyclic at 2 Hz
(for 3 sec.)
(off) Off No error
BF Duo LED red/green
Number in On No configuration; or low speed physical link; or no physical link
(red)
the device
drawing: (red) Flashing No data exchange
cyclic at 2 Hz
(off) Off No error
LINK/RJ45 LED green
On A connection to the Ethernet exists
(green)
(off) Off The device has no connection to the Ethernet
RX/TX/RJ45 LED yellow
(yel- Flashing The device sends/receives Ethernet frames

low)
Table 38: LEDs PROFINET IO-RT-Device

LEDs 47/92
8.3 LEDs Fieldbus Protocols

8.3.1 LED PROFIBUS DP Master
The subsequent table describes the meaning of the LEDs for the cifX card
fieldbus when the firmware of the PROFIBUS DP Master protocol is loaded
to the device.
cifX Card with 1 Communication LED (current Hardware Revision)
COM Duo LED red/green
(green) Flashing acy- No configuration or stack error

clic
(green) Flashing cy- Profibus is configured, but bus communication is not yet released from
clic the application
(green) On Communication to all Slaves is established
(red) Flashing cy- Communication to at least one Slave is disconnected

clic
(red) On Communication to one/all Slaves is disconnected
Table 39: LEDs PROFIBUS DP Master – 1 Communication LED
8.3.2 LED PROFIBUS DP Slave

The subsequent table describes the meaning of the LED for the device
when the firmware of the PROFIBUS DP Slave protocol is loaded to the
device.
(green) On RUN, cyclic communication.
(red) On Wrong configuration at PROFIBUS-DP side.
(red) Flashing cy- STOP, no communication, connection error.

clic
(red) Flashing acy- Not configured.

clic
Table 40: LEDs PROFIBUS DP Slave

LEDs 48/92
8.3.3 LED CANopen Master

The subsequent table describes the meaning of the LEDs for the fieldbus
device when the firmware of the CANopen Master protocol is loaded to the
device.
CAN Duo LED red/green
Off RESET: The device is executing a reset
(off)
(green) Single flash STOPPED: The device is in STOPPED state
(green) Blinking PREOPERATIONAL: The device is in the PREOPERATIONAL state
(green) On OPERATIONAL: The device is in the OPERATIONAL state
(red) Single flash Warning Limit reached: At least one of the error counters of the CAN
controller has reached or exceeded the warning level (too many error
frames).
(red) Double Error Control Event: A guard event (NMT Slave or NMT-master) or a
flash heartbeat event (Heartbeat consumer) has occurred.
(red) On Bus Off: The CAN controller is bus off
Table 41: LEDs CANopen Master
LED State Definition for CANopen Master for the CAN LED
Indicator state Definition
On The indicator is constantly on.
Off The indicator is constantly off.
Flickering The indicator turns on and off with a frequency of 10 Hz: on for 50 ms, followed by off for
50 ms.
Blinking The indicator turns on and off with a frequency of 2,5 Hz: on for 200 ms, followed by off
for 200 ms.
Single Flash The indicator shows one short flash (200 ms) followed by a long off phase (1,000 ms).
Double Flash The indicator shows a sequence of two short flashes (each 200 ms), separated by a
short off phase (200 ms). The sequence is finished by a long off phase (1,000 ms).
Table 42: LED State Definition for CANopen Master for the CAN LED

LEDs 49/92
8.3.4 LED CANopen Slave

The subsequent table describes the meaning of the LEDs for the device
when the firmware of the CANopen Slave protocol is loaded to the device.
CAN Duo LED red/green
Off RESET: The device is executing a reset
(off)
(green) Single flash STOPPED: The device is in STOPPED state
(green) Blinking PREOPERATIONAL: The device is in the PREOPERATIONAL state
(green) On OPERATIONAL: The device is in the OPERATIONAL state

Flickering Auto Baud Rate Detection active: The Device is in the Auto Baud Rate
(red/green) (alternatively Detection mode
red / green)
(red) Single flash Warning Limit reached: At least one of the error counters of the CAN
controller has reached or exceeded the warning level (too many error
frames).
(red) Double flash Error Control Event: A guard event (NMT Slave or NMT-master) or a
heartbeat event (Heartbeat consumer) has occurred.
(red) On Bus Off: The CAN controller is bus off
Table 43: LEDs CANopen Slave
LED State Definition for CANopen Slave for the CAN LED
Indicator state Definition
On The indicator is constantly on.
Off The indicator is constantly off.
Flickering The indicator turns on and off with a frequency of 10 Hz: on for 50 ms, followed by off for 50 ms.
Blinking The indicator turns on and off with a frequency of 2,5 Hz: on for 200 ms, followed by off for
200 ms.
Single Flash The indicator shows one short flash (200 ms) followed by a long off phase (1,000 ms).
Double Flash The indicator shows a sequence of two short flashes (each 200 ms), separated by a short off pha-
se (200 ms). The sequence is finished by a long off phase (1,000 ms).
Table 44: LED State Definition for CANopen Slave for the CAN LED

LEDs 50/92
8.3.5 LED DeviceNet Master

when the firmware of the DeviceNet Master protocol is loaded to the de-
vice.
MNS Duo LED red/green
(green) On Device is online and has one or more connections in the established
state
(green) Flashing Device is online and has no connection in the established state
Green/Red/ Selftest after power on:
(green/red/ Off Green on for 0,25 s, then red on for 0,25 s, then off
off)
(red) Flashing Connection timeout
(red) On Critical connection failure; device has detected a network error: duplicate
MAC-ID or sever error in CAN network (CAN-bus off)
(off) Off After start of the device and during duplicate MAC-ID check
Table 45: LEDs DeviceNet Master
8.3.6 LED DeviceNet Slave

when the firmware of the DeviceNet Slave protocol is loaded to the device.
MNS Duo LED red/green
(green) On Device is online and has one or more connections in the established
state
(green) Flashing Device is online and has no connection in the established state
Green/Red/ Selftest after power on:
(green/red/ Off Green on for 0,25 s, then red on for 0,25 s, then off
off)
(red) On Critical connection failure; device has detected a network error: duplicate
MAC-ID or sever error in CAN network (CAN-bus off)
(red) Flashing Connection timeout
(off) Off After start of the device and during duplicate MAC-ID check
Table 46: LEDs DeviceNet Slave

LEDs 51/92
8.3.7 LED CC-Link Slave

The subsequent table describes the meaning of the LEDs for the
NT 50-CC-xx device when the firmware of the CC-Link Slave protocol is
loaded on X2 to the device.
L RUN Duo LED red/green
L ERR
Off 1. Before participating in the network
Name in the (off)
2. Unable to detect carrier
device 3. Timeout
drawing: 4. Resetting hardware
COM On Receive both refresh and polling signals or just the refresh signal normally,
(green) after participating in the network.
(red) Blinking The switch setting has been changed from the setting at the reset cancella-
tion (blinks for 0.4 sec.).
(red) On 1. CRC error

2. Address parameter error (0, 65 or greater is set including the number of
occupied stations)
3. Baud rate switch setting error during cancellation of reset
(5 or greater)
Table 47: LEDs CC-Link Slave X2

LEDs 52/92
8.4 LEDs Serial Protocols

8.4.1 LED Modbus RTU
The subsequent table describes the meaning of the LEDs for the Modbus
RTU protocol.
with On The device has a valid configuration for Modbus RTU and is ready for
protocol at (green) Modbus communication respectively sends/receives Modbus RTU
X2 telegrams
(red) On Communication error:

The device works as Modbus RTU Master:
with
- the slave device answered with a error (Modbus Exception), e. g.
protocol at
functioncode not supported, access to invalid register addresses or coil
X3
addresses
- receive error detected, e. g. parity error or checksum error - timeout
(slave device does not answer)
The device works as Modbus RTU Slave:
- the Modbus RTU Master device uses an invalid functioncode
- the Modbus RTU Master device has accessed an invalid register ad-
dresses or coil addresses
- receive error detected, e. g. parity error or checksum error
- timeout (application does not answer or answers with error)
The error display is set back with the next error free Modbus telegram
sequence
(off) Off During initialisation or invalid Modbus RTU configuration or missing
power supply
Table 48: LEDs Modbus RTU Protocol
8.4.2 LED ASCII

The subsequent table describes the meaning of the LEDs for the ASCII
protocol.
with Flashing cyclic The device sends/receive data

(green)
protokocol with 5 Hz
at X2
(green) On The device is ready for serial communication
(red) Flashing cyclic The device is configured and is in the state stop
with
with 5 Hz
protocol at
X3 (red) Flashing cyclic The device is not configured
with 1 Hz
(off) Off During initialisation or missing power supply
Table 49: LEDs ASCII Protocol

Technical Data 53/92
9 Technical Data
9.1 Technical Data netTAP 50 Gateway
NT 50 Parameter Value
Communication control- Type netX 50
ler
Memory RAM 8 MB SDRAM
FLASH 4 MB serial Flash
Diagnostic Interface Socket RJ45 Socket 4-pin Ethernet
Display LED Display SYS System Status
APL Application Status
COM Communication Status
LINK Link
ACT Activity
Power supply Voltage 24 V ± 6 V DC
Current at 24 V (typical- 72 mA
ly) 150 mA with short circuit at the output of PROFIBUS
Continuous short
circuit may cause
device damage
Power Consumption 1,8 W
Connector Mini-COMBICON, 2-pin
Environmental conditions Ambient temperature 0 … + 60 °C
(operation)
Ambient temperature -40 °C … +85 °C
(storage)
Humidity 10 % … 95 %, non-condensing
Device Dimensions (L x W x H) 100 x 26 x 66 mm (without connector)
Weight Appr. 80 g
Mounting on DIN rail EN 60715
Protection Class IP 20
RoHS Yes
EMC CE Sign Yes
UKCA Sign Yes
Emission EN 55011 / BS EN 55011
Immunity EN 61131-2 / BS EN 61131-2
Configuration Software SYCON.net
Table 50: Technical Data NT 50 (Part 1)

NT 50 Parameter Value
Ethernet Interface Transmission rate 100 MBit/s
for the device types: 10 MBit/s (depending on loaded
NT 50-DP-EN, firmware)
NT 50-CO-EN,
Interface Type 100 BASE-TX, isolated
NT 50-DN-EN,
NT 50-RS-EN 10 BASE-TX (depending on
loaded firmware), isolated
Half duplex/Full duplex supported (at 100 MBit/s)
Auto-Negotiation supported (depending on load-
ed firmware)
Auto-Crossover supported
Connector 1 * RJ45
PROFIBUS Interface Transmission rate 9,6 kBit/s,
for the device types 19,2 kBit/s,
NT 50-DP-EN 31,25 kBit/s,
45,45 kBit/s,
93,75 kBit/s,
187,5 kBit/s,
500 kBit/s,
1,5 MBit/s,
3 MBit/s,
6 MBit/s,
12 MBit/s
Interface Type RS 485, optically isolated
Connector SubD female, 9-pin
CANopen Interface Transmission rate 10 kBit/s,
for the device type: 20 kBit/s,
NT 50-CO-XX 50 kBit/s,
100 kBit/s,
125 kBit/s,
250 kBit/s,
500 kBit/s,
800 kBit/s,
1 MBit/s
Interface Type ISO 11898, optically isolated
Connector SubD male, 9-pin
DeviceNet Interface Transmission rate 125 kBit/s,
for the device type: 250 kBit/s,
NT 50-DN-EN 500 kBit/s
Interface Type ISO 11898, optically isolated
Connector COMBICON, 5-pin
Serial Interface Interface Type RS-232, RS-422, RS-485
for the device type:
Connector RJ45
NT 50-xx-RS Ethernet and serial interface
together in one connector
Table 51: Technical Data NT 50 (Part 2)

9.2 Technical Data of Real-Time Ethernet Communication

Protocols
9.2.1 EtherNet/IP Scanner (Master) Link
Parameter Description
Maximum number of EtherNet/IP connections 1 connections for implicit (to one Adapter/Slave only)
Maximum number of cyclic input data 504 bytes
Maximum number of cyclic output data 504 bytes
IO Connection type Cyclic, minimum 1 ms (depending on the used number of input
and output data)
UCMM, Class 3 Supported
Predefined standard objects Identity Object
Message Route Object
Assembly Object
Connection Manager
Ethernet Link Object
TCP/IP Object
ACD (Address Conflict Detection) Supported
DHCP Supported
BOOTP Supported
Baud rates 10 and 100 MBit/s
Data transport layer Ethernet II, IEEE 802.3
Integrated switch Supported
Limitations No acyclic user data communication
CIP Sync Services are not implemented
TAGs are not supported
Reference to stack version V2.10
Table 52: Technical Data EtherNet/IP Scanner (Master) Link Protocol

9.2.2 EtherNet/IP Adapter (Slave)

Maximum number of input data 504 bytes
Maximum number of output data 504 bytes
IO Connection 1 explicit owner, up to 2 listen only
IO Connection type Cyclic, minimum 1 ms
UCMM Supported
Predefined standard objects Identity Object
Message Route Object
Assembly Object
Connection Manager
Ethernet Link Object
TCP/IP Object
ACD (Address Conflict Detection) Supported
DHCP Supported
BOOTP Supported
Integrated switch Supported
Limitations No acyclic user data communication
CIP Sync Services are not implemented
TAGs are not supported
DLR not supported (ring topology)
Reference to firmware/stack version V2.13
Table 53: Technical Data EtherNet/IP Adapter (Slave) Protocol

9.2.3 Open Modbus/TCP

Maximum number of input data 256 Registers
Maximum number of output data 256 Registers
Maximum number of client connections 16
Acyclic communication Read/Write Register:
- Max. 125 Registers per Read Telegram (FC 3, 4, 23),
- Max. 121 Registers per Write Telegram (FC 23),
- Max. 123 Registers per Write Telegram (FC 16)
Read/Write Coil:
- Max. 2000 Coils per Read Telegram (FC 1, 2),
- Max. 1968 Coils per Write Telegram (FC 15)
Modbus Function Codes 1,
2,
3,
4,
5,
6,
7,
15,
16,
23 (Function code 23 in server mode only)
Protocol Mode Client or Server
Table 54: Technical Data Open Modbus/TCP Protocol

9.2.4 PROFINET IO-RT-Controller Link

Maximum number of PROFINET IO Devices 1 (to one IO Device only)
Maximum number of cyclic input data 1440 bytes (including IOPS and IOCS)
Maximum number of cyclic output data 1440 bytes (including IOPS and IOCS)
Supported Protocols RTC – Real Time Cyclic Protocol, Class 1
RTA – Real Time Acyclic Protocol
DCP – Discovery and configuration Protocol
CL-RPC – Connectionless Remote Procedure Call
Context management by CL-RPC Supported
Minimum cycle time 1 ms
Different IO-Devices can be configured with different cycle times
Baud rate 100 MBit/s
Full-Duplex mode
Configuration File Maximum 1 MByte
Limitations Read/Write Record not supported
No Alarm processing
RT over UDP not supported
Multicast communication not supported
DHCP is not supported
Only one IOCR per IO Device
NameOfStation of IO Controller CANNOT be set using the DCP
SET NameOfStation service but only at start-up while configuring
the IO Controller
The buffer for IO-Device diagnosis data will be overwritten in case
of multiple diagnostic events. Only one (the last) event is stored at
the same time. If a single event produces more than 200 bytes of
diagnosis data, only the first 200 bytes will be taken care of.
The usable (minimum) cycle time depends on the number of used
IO Devices, the number of used input and output data. The cycle-
time, the number of configured IO Devices and the amount of IO
data depend on each other. For example it is not possible due to
performance reasons to have 128 IO Devices communication with
cycle-time 1ms.
The size of the bus configuration file is limited by the size of the
RAM Disk (1 MByte)
Only one API (API = 0) is supported. Any Profile requesting a
different API is currently not supported.
WriteMultiple-Record service is not supported
Table 55: Technical Data PROFINET IO RT Controller Link Protocol

9.2.5 PROFINET IO-RT-Device

Supported protocols RTC – Real Time Cyclic Protocol, Class 1 (unsynchronized)
RTA – Real Time Acyclic Protocol
DCP – Discovery and configuration Protocol
CL-RPC – Connectionless Remote Procedure Call
LLDP – Link Layer Discovery Protocol
SNMP – Simple Network Management Protocol
Used Protocols (subset) UDP, IP, ARP, ICMP (Ping)
Topology recognition LLDP, SNMP V1, MIB2, physical device
VLAN- and priority tagging yes
Context Management by CL-RPC Supported
Minimum cycle time 10 ms
Baud rate 100 MBit/s
Limitations No acyclic user data transfer
RT over UDP not supported
Multicast communication not supported
Only one device instance is supported
DHCP is not supported
RT Classes 2 and 3 are not supported
FastStartUp is not supported
Media Redundancy is not supported
Access to the submodule granular status bytes (IOPS & IOCS) is not
supported
The amount of configured IO-data influences the minimum cycle time
that can be reached.
Supervisor-AR is not supported, Supervisor-DA-AR is supported
Only 1 Input-CR and 1 Output-CR are supported
Multiple WriteRequests are not supported
Table 56: Technical Data PROFINET IO Device Protocol

9.3 Technical Data Fieldbus Protocols

9.3.1 CANopen Master Link
Maximum number of CANopen nodes 1 (to one node only)
Maximum number of receive PDOs 64
Maximum number of transmit PDOs 64
Exchange of process data Via PDO transfer:
- synchronized,
- remotely requested and
- event driven (change of date)
Functions Emergency message (consumer)
Node guarding / life guarding, heartbeat
PDO mapping
NMT Master
SYNC protocol (producer)
Simple boot-up process, reading object 1000H for identification
Baud rates 10 kBits/s,
20 kBits/s,
50 kBits/s,
100 kBits/s,
125 kBits/s,
250 kBits/s,
500 kBits/s,
800 kBits/s,
1 MBits/s
Data transport layer CAN Frames
CAN Frame type 11 Bit
Limitations SDO-Upload/Download for user data transfer not supported
Table 57: Technical Data CANopen Master Link Protocol

9.3.2 CANopen Slave

Objects 2200, 2201, 2202, 2203 each with up to 128 bytes
Objects 2000, 2001, 2002, 2003 each with up to 128 bytes
Maximum number of receive PDOs 64
Maximum number of transmit PDOs 64
Exchange of process data Via PDO transfer
- synchronized,
- remotely requested and
- event driven (change of date, event timer)
Functions Node guarding / life guarding, heartbeat
PDO mapping
NMT Slave
SYNC protocol (consumer)
SDO upload/download (server, for configuration)
Emergency message (producer)
20 kBits/s,
50 kBits/s,
100 kBits/s,
125 kBits/s,
250 kBits/s,
500 kBits/s,
800 kBits/s,
1 MBits/s
Auto baudrate detection is supported
Data transport layer CAN Frames
CAN Frame type for CANopen 11 Bit
Limitations Timestamp (producer/consumer) not supported on application
level.
Table 58: Technical Data CANopen Slave Protocol
Configuration of the node address

The CANopen node address can be configured by SYCON.net or by ad-
dress switches. The address switches can be activated with SYCON.net
version 1.351 (or higher) and can be used with firmware version 1.1 (or
higher).

9.3.3 CC-Link Slave

Firmware works according to CC-Link Version 2.0:
Station Types Remote Device Station (up to 4 occupied stations)
Maximum input data 368 bytes
Maximum output data 368 bytes
Input data remote device station 112 bytes (RY) and 256 bytes (RWw)
Output data remote device station 112 bytes (RX) and 256 bytes (RWr)
Extension cycles 1, 2, 4, 8
Baud rates 156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10 MBit/s
Limitation Intelligent Device Station not supported
Firmware works according to CC-Link Version 1.11:
Station Types Remote I/O station,
Remote device station’ (up to 4 occupied stations)
Maximum input data 48 bytes
Maximum output data 48 bytes
Input data remote I/O station 4 bytes (RY)
Output data remote I/O station 4 bytes (RX)
Input data remote device station 4 bytes (RY) and 8 bytes (RWw) per occupied station
Output data remote device station 4 bytes (RX) and 8 bytes (RWr) per occupied station
Baud rates 156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10 MBit/s
Firmware
Table 59: Technical Data CC-Link-Slave Protocol
Configuration of the station number

The CC-Link station number can be configured by SYCON.net or by ad-
dress switches. The address switches can be activated with SYCON.net
higher).

9.3.4 DeviceNet Master Link

Maximum number of DeviceNet slaves 1 (one slave only)
Maximum number of total cyclic input data 255 bytes
Maximum number of total cyclic output data 255 bytes
Maximum Configuration data 1000 bytes
Connections Bit Strobe
Change of State
Cyclic
Poll
Explicit Peer-to-Peer Messaging (Only for parameterization)
Fragmentation Explicit and I/O
UCMM Supported
Objects Identity Object (Class Code 0x01)
Message Router Object (Class Code 0x02)
DeviceNet Object (Class Code 0x03)
Connection Object (Class Code 0x05)
Acknowledge Handler Object (Class Code 0x06)
250 kBit/s,
500 kBit/s
Auto baudrate detection is not supported
Data transport layer CAN frames
Limitations User data transfer through the gateway only via IO connections
Table 60: Technical Data DeviceNet Master Link Protocol

9.3.5 DeviceNet Slave

Connections Poll
Change-of-state
Cyclic
Bit-strobe
Fragmentation Explicit and I/O
UCMM Not supported
250 kBit/s,
500 kBit/s
Data transport layer CAN frames
Limitations Access to Application Object only via IO connection
Table 61: Technical Data DeviceNet Slave Protocol
Configuration of the MAC ID

The DeviceNet MAC ID can be configured by SYCON.net or by address
switches. The address switches can be activated with SYCON.net version
1.351 (or higher) and can be used with firmware version 1.1 (or higher).

9.3.6 PROFIBUS DP Master Link

Maximum number of PROFIBUS DP slaves 1 (to one slave only)
Configuration data Max. 244 bytes
Parameterization data 7 bytes standard parameters
Max. 237 bytes application specific parameters
Baud rate 9,6 kBits/s,
19,2 kBits/s,
31,25 kBits/s,
45,45 kBits/s
93,75 kBits/s,
187,5 kBits/s,
500 kBits/s,
1, 5 MBits/s,
3 MBits/s,
6 MBits/s,
12 MBit/s
Data transport layer PROFIBUS FDL
Limitations DP V1 services class 1 and 2 are not supported
DP V2 services are not implemented
Table 62: Technical Data PROFIBUS DP Master Link Protocol

9.3.7 PROFIBUS DP Slave

Maximum number of modules Max. 4 input modules and max. 4 output modules,
max. 24 modules when using manual setting
Baud rate 9,6 kBits/s,
19,2 kBits/s,
31,25 kBits/s,
45,45 kBits/s
93,75 kBits/s,
187,5 kBits/s,
500 kBits/s,
1, 5 MBits/s,
3 MBits/s,
6 MBits/s,
12 MBit/s
Auto baudrate detection is supported
Data transport layer PROFIBUS FDL
Limitations DP V1 services class 1 and 2 to transfer user data are not sup-
ported
SSCY1S – Slave to slave communication state machine not im-
plemented
Data exchange broadcast not implemented
I&M0 with fixed settings only
Reference to firmware/stack version V2.10
Table 63: Technical Data PROFIBUS DP Slave Protocol
Configuration of the station address

The PROFIBUS station address can be configured by SYCON.net or by
address switches. The address switches can be activated with SYCON.net
higher).

9.4 Technical Data serial Protocols

9.4.1 ASCII
Parameter Description and Value Range
Maximum telegram length 512 bytes
Data bits 7, 8 bits
Stop bits 1, 2 bit(s)
Parity None, even, odd
Baud rate 300 bit/s,
600 bit/s,
1200 bit/s,
2400 bit/s,
4800 bit/s,
9600 bit/s,
19200 bit/s,
38400 bit/s,
57600 bit/s,
115200 bit/s
Duplex Half-duplex
Flow control None
Indicator for end of received telegram On receipt of a fixed number of characters
On receipt of termination character(s)
Elapse of character delay time
Timing parameter Response timeout
Receive watchdog time
Send cycle time
Character delay time
Number of send buffers 1
Number of receive buffers 1
Number of transmission retries 1
Maximum number of structure elements of a send 10
telegram
Maximum number of structure elements of a receive 10
telegram
Structure elements Start character(s),
Device address,
Object index or start address,
Command identifier,
Data area with length information,
Data area with termination character(s),
End character(s),
Checksum,
Character(s) without meaning (fix length)
Checksum methods CRC8,
CRC16,
CRC32,
Exor
Table 64: Technical Data ASCII Protocol

9.4.2 Modbus RTU Master/Slave

Parameter Description and Value Range
Maximum number of input data 256 Registers
Maximum number of output data 256 Registers
Acyclic communication Read/Write Register,
Maximum 125 Registers per Read Telegram (FC 3, 4),
Maximum 123 Registers per Write Telegram (FC 16),
Maximum 118 Registers per Write Telegram (FC 23),
Maximum 118 Registers per Read Telegram (FC 23)
Read/Write Coil,
Maximum 2000 Coils per Read Telegram (FC 1, 2),
Maximum 1968 Coils per Write Telegram (FC 15)
Function Codes Modbus Master 1, 2, 3, 4, 5, 6, 15, 16
Function Codes Modbus Slave 1, 2, 3, 4, 5, 6, 7, 8, 15, 16, 23
Mode Modbus Master or Modbus Slave
Baud rates 1200 bit/s,
2400 bit/s,
4800 bit/s,
9600 bit/s,
19200 bit/s,
38400 bit/s,
57600 bit/s,
115200 bit/s
Data bits 8 bits
Stop bits 1, 2 bit(s)
Parity None, even, odd
Limitations Broadcast not supported
Table 65: Technical Data Modbus RTU Protocol

Wiring Instructions 69/92
10 Wiring Instructions
Please note the wiring instructions for the corresponding protocol specifica-
tions, otherwise a perfect function of the device is not guaranteed.
Use shielded cables, where the shield at both end should be connect ex-
tensively with the potential equalization. Cables for communication should
be layed/placed as far away as possible from cables transferring energy, to
avoid EMC influence caused by switching operation from cables transfer-
ring energy.

10.1 Assembly of D-Sub Connectors

The design of the bus cabling is an essential factor for the proper function
of communication. Therefore, special attention should be paid to the cable
connections with its connectors. Particularly, ensure good shield connec-
tion.
The shield must be connected as follows
1. Dismantle the cable.
2. Pull back the shielding from the cable sheathing.
3. Reduce the shielding that later it is covered by the nozzle.
4. Push a nozzle or shrinking tube over the cable sheathing that at the
cable end a zone of 5 to 8 mm remains free.
5. Connect the wire ends with the connector
6. Then push the cable in the plug to the bare braided shield under the
strain relief.
7. Fix the strain relief with screws.
The cable connection should look like shown below:
Figure 11: D-Sub Cable Assemblies
Fixing screw UNC.

Metallic plug collar
Strain relief for connecting the shielding with the connector housing
Shrinking tube or nozzle to cover the shielding and for bend protec-
tion
Cable shielding pulled back over the cable sheathing
Metallic or metallized connector housing

10.2 Ethernet
Use of Hubs and Switches
For the corresponding communication systems, the use of hubs and/or
switches is either forbidden or allowed. The following table shows the ac-
ceptable use of hubs and switches by each communication system:
Communication System Hub Switch
EtherCAT forbidden only allowed between EtherCAT Master
and first EtherCAT Slave
(100 MBit/s, Full Duplex)
EtherNet/IP allowed allowed
(10 MBit/s/100 MBit/s,
Full or Half Duplex, Auto-Negotiation)
Open Modbus/TCP allowed allowed
(10 MBit/s/100 MBit/s,
Full or Half Duplex, Auto-Negotiation)
POWELINK allowed forbidden
PROFINET IO RT forbidden Only allowed, if the switch supports ‚Pri-
ority Tagging’ and LLDP
(100 MBit/s, Full Duplex)
SERCOS III forbidden forbidden
Table 66: Use of Hubs and Switches
When using older NT 50-xx-EN respectively NT 50 xx-RS devices, then fol-

low:
Failure of the Network Communication

 Do not operate hardware with the communication controllers netX 50,
netX100 or netX 500 with the protocols Ethernet TCP/UDP/IP, Ether-
Net/IP or Modbus TCP at 10 MBit/s in half-duplex mode, otherwise fail-
ure of the network communication can occure.
 Use only switches or 10/100 MBit/s dual-speed hubs and ensure that
the network operates at 100 MBit/s and in full-duplex mode.
For further information refer to section Failure in 10 MBit/s Half Duplex

Mode and Workaround on page 40.

10.3 PROFIBUS
Please ensure that termination resistors are available at both ends of the
cable. If special PROFIBUS connectors are being used, these resistors are
often found inside the connector and must be switched on. For baud rates
above 1.5 MBaud use only special connectors, which also include addition-
al inductance.
It is not permitted to have T-stubs on PROFIBUS high baud rates. Use only
a special cable which is approved for PROFIBUS-DP. Make a solid connec-
tion from the cable shield to ground at every device and make sure that
there is no potential difference between the grounds at the devices.
If the Hilscher device is linked with only one other device on the bus, they
must be at the ends of the bus line. The reason is that these devices must
deliver the power supply for the termination resistors. Otherwise the Master
can be connected at any desired position.
Figure 12: PROFIBUS-DP-Network
Up to 32 PROFIBUS devices can be connected to one bus segment. If

several bus segments are linked to each other with repeaters, there can be
up to 127 devices on the network.
Only PROFIBUS certified cable, preferably the cable type A, should be
used.

The maximum length of a bus segment depends on the baudrate used, see
the following table.
Baud rate in kBit/s Max. distance in m
9,6 1.200
19,2 1.200
93,75 1.200
187,5 1.000
500 400
1.500 200
3.000 100
6.000 100
12.000 100
Table 67: PROFIBUS Segment Length in Dependence of the Baud Rate
The following table contains the most important electrical dsata concerning
PROFIBUS certified cable:
Parameter Value
Impedance 135…165 Ω
Capacity < 30 pF/m
Loop resistance 110 Ω/km
Wire gauge 0,64 mm
Table 68: Characteristics of PROFIBUS certified Cable

10.4 CANopen
Please use only CAN certified cable with the following characteristics:
Parameter Value
Impedance 120 Ω ± 12 Ω
Capacity per < 50 pF/m
units length
Table 69: Characteristics of CAN certified Cable
Figure 13: Termination CANopen Network
At the ends of the network there must be two resistors of 120 Ω to termi-
nate the cable. It is allowed to use repeaters to increase the number of
nodes, which may be connected, or to increase the maximum cable length.
The CAN segment length in dependence of the Baud rate or corresponding
Loop Resistance and Wire Gauge is given in the following table:
Baud rate Max. distance Loop Resistance Wire Gauge
in kBit/s s
10 1000 m <26 Ω/km 0,75...0,80 mm2
20 1000 m <26 Ω/km 0,75...0,80 mm2
50 1000 m <26 Ω/km 0,75...0,80 mm2
125 500 m <40 Ω/km 0,50...0,60 mm2
250 250 m <40 Ω/km 0,50...0,60 mm2
500 100 m <60 Ω/km 0,34...0,60 mm2
800 50 m <60 Ω/km 0,34...0,60 mm2
1.000 30 m 70 Ω/km 0,25...0,34 mm2
Table 70: CAN Segment Length in dependence of the Baud rate or corresponding Loop Re-
sistance and Wire Gauge

10.5 DeviceNet
Up to 64 DeviceNet devices can be linked together over the bus. The max-
imum length of the bus cable depends on the used baud rate and the used
cable type. Only special proved DeviceNet cable should be used.
The maximum length of the DeviceNet cable depends from the baud rate
and from the chosen cable type. In the following table, these are listed in
the following table:
Baudrate in kbit/s Maximum length of Maximum length of
cable (thick cable) cable (thick cable)
125 500 m 100 m
250 250 m 100 m
500 100 m 100 m
Table 71: Maximum length in dependence from the Baud Rate for DeviceNet Cables
The data line cables must match the following conditions:

Data line Impedance Capacity Loop Re- Wire
cable sistance Gauge
(Diameter)
Thick 120 Ohm <39,4 pf/m <22,6 Ohm/km 2 * 1.1 mm
Thin 120 Ohm <39,4 pf/m <91,8 Ohm/km 2 * 0,6 mm
Table 72 Characteristics of DeviceNet Data Line Cable
The power supply cables must match the following conditions:

Power Loop Re- Wire Gauge
supply sistance (Diameter)
cable
Thick <11,8 Ohm/km 2 * 1.4 mm
Thin <57,4 Ohm/km 2 * 0,7 mm
Table 73: Characteristics of DeviceNet Power Supply Cable
Figure 14: DeviceNet Network
Please ensure that termination resistors with 120 Ohm are available at both
ends of the cable.
Further devices can be connected via T-stubs to the bus cable. The maxi-
mum length of all T-stubs is 6 m. The whole length of the bus cable and all

T-stubs does not exceed the maximum length listed in the following table.
There are two different types of cables. If both cables types are used within
the same network, the maximum length is:
Max. distance Baud rate in
kBits/s
Lthick + 5 x Lthin <= 500 m at 125 kBaud
Lthick + 2,5 x Lthin <= 250 m at 250 kBaud
Lthick + Lthin <= 100 m at 500 kBaud
Table 74: DeviceNet Segment Length in dependence of the Baud rate
The DeviceNet cable contains the data line cables and the power supply
cables.

10.6 CC-Link
Use only a special cable which is approved for CC-Link. CC-Link specifies
several shielded three-core Twisted Pair cables. It is recommended to use
only one type of cable for an installation. Please ensure that termination re-
sistors are available at both ends of the cable. The value of the termination
resistor depends on the used type of cable and can be 100, 110 and 130 Ω,
respectively.
The following illustration displays the basic network structure.
Figure 15: CC-Link Network
(*) The termination resistor depends on the used cable type (see CC-Link
Cable Wiring Manual).
The maximum length of one bus segment depends on the used baud rate.
The structure of the network can be built up without or with branches. The
details listed here are taken from the "CC link Cable Wiring manual" from
July 2004. Also further details are contained there. The document is ready
for download on http://www.cc-link.org.
Note: For CC-Link V2.00 the cable specification V1.10 has not been
changed.

Only trunk line, without branches:

Baud rate max. Length cab- max. Length ca- max. length high
le V1.00 ble V1.10 and flexible V1.10
cable V1.00 with (Type 50%)
high capacity
156 kbps 1200 m 1200 m 600 m
625 kbps 600 m 900 m 450 m
2,5 Mbps 200 m 400 m 200 m
5 Mbps 150 m 160 m 80 m
10 Mbps 100 m 100 m 50 m
Table 75: Maximum length
Note: Further cable types are available with which however only lower
maximum lengths can be reached.
Trunk line with branch lines:

baud rate 156 kbps 625 kbps
max. length trunk line 500 m 100 m
max. number of devices in 6 6
branch line
max. cable length of branch 8m 8m
line
max. length of all branch 200 m 50 m
lines
Table 76: Maximum length
Further devices can be connected via T-branches to the bus cable only at
the baud rates 156 kbps and 625 kbps. The maximum length of all T-stubs
is limited to 8 m. The whole length of the bus cable and all T-branches does
not exceed the maximum length listed in the following table.
Minimum Distance:
Between two devices a minimum distance is to be kept.
Distance between CC-Link CC-Link cable V1.00 CC-Link cable V1.10
devices
Remote device to next re- 0.3 m or more 0.2 m or more
mote device
Remote device to next Mas- 1 m or more 0.2 m or more
ter and/or intelligent device
Table 77: Minimum distance between two devices

10.7 RS-232
Device Damage!
 Make sure that the NT 50 device and the remote device via RS-232
have the same potential or insert a galvanic isolation, to avoid compen-
sation current between the used devices.
The RS232 interface (EIA-232) is a point-to-point connection of two com-

munication devices. Only shielded cables have to be used. No termination
resistors are required.
Take care of the pin assignment at the communication partner. This de-
cides, whether you need a so called null modem cable with crossed pin as-
signments.
Figure 16: RS-232 Null-Modem Cable Connection
* Pinning of the remote device: see device description of the used de-
vice.
Conductor length and transmission rates
In the EIA-232 norm a maximum cable ca- max. baud max. length
rate
pacitance of 2500 pF is allowed for a RS232
connection. 19.200 15 m
Cables of such capacitance may have the 57.600 5m

following lengths depending on the baud rate 115.200 <2 m
Higher length can be achieved with cables of extraordinarily low capaci-

tance.
Pin assignmet for connector X2 see section X2 for Device Type NT 50-RS-
EN on page 26.
Pin assignmet for connector X3 see section X3 for Device Type NT 50-xx-
RS on page 28.

10.8 RS-422
Device Damage!
The lines of this industry bus interface are operated in push-pull action, four
lines are required which can be controlled in half duplex or full duplex
mode. This interface has been designed for one master and at maximum
10 slaves. Using repeaters, using even more slaves is possible.
Cable lengths of up to 1.2 km (at low baud rates) and data transmission
rates of up to 10 MBit/s (at maximally 12 m length of line) are possible. The
maximum useable transmission rate depends on the technical data of the
used devices.
The following illustration shows wiring for RS-422:
Figure 17: RS-422 Wiring
Bus Requirements:
The bus cable must be a shielded 4.wire twisted pair cable. Each pair of
wires has to be used for exactly one data transmission direction. The shield
should be connected at both ends to the potential equalization system.
On each end, the bus requires a termination resistor (LT) of 90 Ω to 150 Ω
between the lines. This value depends on the characteristic wave imped-
ance of the cable.
The pull-up and pull-down resistors should have a resistance of 390 Ω up to
650 Ω.

Cable Requirements:
The workmanship of bus cabling is an important factor of the reliable opera-
tion and also for the electromagnetic compatibility and emission. It is man-
datory to use shielded twisted-pair cables. The shield of the cable must
consist of a copper wire mesh.
Parameter Value
Characteristic wave 150 Ω ± 15 Ω
impedance
Capacitance < 30 pF/m
Wire gauge 0,64 mm
Table 78: Electric Requirements to RS-422 Cables
The following lengths of lines can be achieved:

Max. overall length of Max. Baud rate Max. length of a single
line branch line
120 m 1 MBit/s 0,3 m
600 m 500 kBit/s 0,6 m
1200 m 100 kBit/s 1,5 m
Table 79: RS-422 Conductor Length and Transmission Rates

10.9 RS-485
Device Damage!
The lines of this industry bus interface are operated in push-pull action, only
two lines are required which can be controlled in half duplex or full duplex
mode. The advantage of the 2-wire technology mainly consists in the multi-
master capability. In principle, each participant is able to exchange data
with any other participant. However, synchronous send attempts of two or
more participants must be prevented by the applied protocol. The RS-485
interface allows the connection of up to 32 transmitters and receivers using
a protocol. (With repeaters even more participants are possible.)
Nowadays, RS-485 supports cable lengths of up to 1.2 km (see Table 70:
RS-485 Cable Lengths on page 83) and data transmission rates of up to 1
MBit/s. The maximum useable transmission rate depends on the technical
data of the used devices.
The following illustration shows wiring for RS-485:
Figure 18: RS-485 Wiring

Bus requirements:
The bus cable must be a shielded twisted pair cable where the shield
should be connected at both ends with large contact areas to the potential
equalization system.
On each end, the bus requires a termination resistor (LT) between the lines
D1 und D0 of approximately the amount of the characteristic wave imped-
ance of the cable, which usually amounts to a value between 120 Ω and
220 Ω.
The pull-up and pull-down resistors should have a value of 390 Ω up to
650 Ω.
Cable requirements:
The workmanship of bus cabling is an important factor of the reliable opera-
tion and also for the electromagnetic compatibility and emission. It is man-
datory to use shielded twisted-pair cables. The shield of the cable must
consist of a copper wire mesh.
Parameter Value
Characteristic wave 150 Ω ± 15 Ω
impedance
Capacitance < 30 pF/m
Wire gauge 0,64 mm
Table 80: Electric Requirements to RS-485 Cables
The following lengths of lines can be achieved:

Max. overall length of Max. Baud rate Max. length of a single
line branch line
120 m 1 MBit/s 0,3 m
600 m 500 kBit/s 0,6 m
1200 m 100 kBit/s 1,5 m
Table 81: RS-485 Cable Lengths

Decommissioning/Disposal 84/92
11 Decommissioning/Disposal
11.1 Put the Device out of Operation
Danger of unsafe System Operation!
 To prevent property damage, do not remove this device under runtime

conditions before you can not guarantee further a safe and secure opera-
tion of the plant.
• Disconnect the communication cables from the device.

• Disconnect the plug for power supply.
• Remove the device as described in section Removing the NT 50 from
the DIN Top Hat Rail on page 35.
11.2 Disposal of Waste Electronic Equipment

According to the European Directive 2012/19/EG “Waste Electrical and
Electronic Equipment (WEEE)”, waste electronic equipment may not be
disposed of as household waste. As a consumer, you are legally obliged to
dispose of all waste electronic equipment according to national and local
regulations.
Waste Electronic Equipment

 This product must not be treated as household waste.
 This product must be disposed of at a designated waste electronic
equipment collecting point.

Appendix 85/92
12 Appendix
12.1 Legal Notes
Copyright
© Hilscher Gesellschaft für Systemautomation mbH
All rights reserved.
The images, photographs and texts in the accompanying materials (in the
form of a user's manual, operator's manual, Statement of Work document
and all other document types, support texts, documentation, etc.) are pro-
tected by German and international copyright and by international trade and
protective provisions. Without the prior written consent, you do not have
permission to duplicate them either in full or in part using technical or me-
chanical methods (print, photocopy or any other method), to edit them us-
ing electronic systems or to transfer them. You are not permitted to make
changes to copyright notices, markings, trademarks or ownership declara-
tions. Illustrations are provided without taking the patent situation into ac-
count. Any company names and product designations provided in this doc-
ument may be brands or trademarks by the corresponding owner and may
be protected under trademark, brand or patent law. Any form of further use
shall require the express consent from the relevant owner of the rights.
Important notes
Utmost care was/is given in the preparation of the documentation at hand
consisting of a user's manual, operating manual and any other document
type and accompanying texts. However, errors cannot be ruled out. There-
fore, we cannot assume any guarantee or legal responsibility for erroneous
information or liability of any kind. You are hereby made aware that descrip-
tions found in the user's manual, the accompanying texts and the documen-
tation neither represent a guarantee nor any indication on proper use as
stipulated in the agreement or a promised attribute. It cannot be ruled out
that the user's manual, the accompanying texts and the documentation do
not completely match the described attributes, standards or any other data
for the delivered product. A warranty or guarantee with respect to the cor-
rectness or accuracy of the information is not assumed.
We reserve the right to modify our products and the specifications for such
as well as the corresponding documentation in the form of a user's manual,
operating manual and/or any other document types and accompanying
texts at any time and without notice without being required to notify of said
modification. Changes shall be taken into account in future manuals and do
not represent an obligation of any kind, in particular there shall be no right
to have delivered documents revised. The manual delivered with the prod-
uct shall apply.
Under no circumstances shall Hilscher Gesellschaft für Systemautomation
mbH be liable for direct, indirect, ancillary or subsequent damage, or for
any loss of income, which may arise after use of the information contained
herein.

Appendix 86/92
Liability disclaimer
The hardware and/or software was created and tested by Hilscher Gesell-
schaft für Systemautomation mbH with utmost care and is made available
as is. No warranty can be assumed for the performance or flawlessness of
the hardware and/or software under all application conditions and scenarios
and the work results achieved by the user when using the hardware and/or
software. Liability for any damage that may have occurred as a result of us-
ing the hardware and/or software or the corresponding documents shall be
limited to an event involving willful intent or a grossly negligent violation of a
fundamental contractual obligation. However, the right to assert damages
due to a violation of a fundamental contractual obligation shall be limited to
contract-typical foreseeable damage.
It is hereby expressly agreed upon in particular that any use or utilization of
the hardware and/or software in connection with
• Flight control systems in aviation and aerospace;
• Nuclear fusion processes in nuclear power plants;
• Medical devices used for life support and
• Vehicle control systems used in passenger transport
shall be excluded. Use of the hardware and/or software in any of the follow-
ing areas is strictly prohibited:
• For military purposes or in weaponry;
• For designing, engineering, maintaining or operating nuclear systems;
• In flight safety systems, aviation and flight telecommunications systems;
• In life-support systems;
• In systems in which any malfunction in the hardware and/or software
may result in physical injuries or fatalities.
You are hereby made aware that the hardware and/or software was not
created for use in hazardous environments, which require fail-safe control
mechanisms. Use of the hardware and/or software in this kind of environ-
ment shall be at your own risk; any liability for damage or loss due to im-
permissible use shall be excluded.

Appendix 87/92
Warranty
Hilscher Gesellschaft für Systemautomation mbH hereby guarantees that
the software shall run without errors in accordance with the requirements
listed in the specifications and that there were no defects on the date of ac-
ceptance. The warranty period shall be 12 months commencing as of the
date of acceptance or purchase (with express declaration or implied, by
customer's conclusive behavior, e.g. putting into operation permanently).
The warranty obligation for equipment (hardware) we produce is 36
months, calculated as of the date of delivery ex works. The aforementioned
provisions shall not apply if longer warranty periods are mandatory by law
pursuant to Section 438 (1.2) BGB, Section 479 (1) BGB and Section 634a
(1) BGB [Bürgerliches Gesetzbuch; German Civil Code] If, despite of all
due care taken, the delivered product should have a defect, which already
existed at the time of the transfer of risk, it shall be at our discretion to ei-
ther repair the product or to deliver a replacement product, subject to timely
notification of defect.
The warranty obligation shall not apply if the notification of defect is not as-
serted promptly, if the purchaser or third party has tampered with the prod-
ucts, if the defect is the result of natural wear, was caused by unfavorable
operating conditions or is due to violations against our operating regulations
or against rules of good electrical engineering practice, or if our request to
return the defective object is not promptly complied with.
Costs of support, maintenance, customization and product care

Please be advised that any subsequent improvement shall only be free of
charge if a defect is found. Any form of technical support, maintenance and
customization is not a warranty service, but instead shall be charged extra.
Additional guarantees
Although the hardware and software was developed and tested in-depth
with greatest care, Hilscher Gesellschaft für Systemautomation mbH shall
not assume any guarantee for the suitability thereof for any purpose that
was not confirmed in writing. No guarantee can be granted whereby the
hardware and software satisfies your requirements, or the use of the hard-
ware and/or software is uninterruptable or the hardware and/or software is
fault-free.
It cannot be guaranteed that patents and/or ownership privileges have not
been infringed upon or violated or that the products are free from third-party
influence. No additional guarantees or promises shall be made as to
whether the product is market current, free from deficiency in title, or can be
integrated or is usable for specific purposes, unless such guarantees or
promises are required under existing law and cannot be restricted.

Appendix 88/92
Confidentiality
The customer hereby expressly acknowledges that this document contains
trade secrets, information protected by copyright and other patent and
ownership privileges as well as any related rights of Hilscher Gesellschaft
für Systemautomation mbH. The customer agrees to treat as confidential all
of the information made available to customer by Hilscher Gesellschaft für
Systemautomation mbH and rights, which were disclosed by Hilscher Ge-
sellschaft für Systemautomation mbH and that were made accessible as
well as the terms and conditions of this agreement itself.
The parties hereby agree to one another that the information that each par-
ty receives from the other party respectively is and shall remain the intellec-
tual property of said other party, unless provided for otherwise in a contrac-
tual agreement.
The customer must not allow any third party to become knowledgeable of
this expertise and shall only provide knowledge thereof to authorized users
as appropriate and necessary. Companies associated with the customer
shall not be deemed third parties. The customer must obligate authorized
users to confidentiality. The customer should only use the confidential in-
formation in connection with the performances specified in this agreement.
The customer must not use this confidential information to his own ad-
vantage or for his own purposes or rather to the advantage or for the pur-
pose of a third party, nor must it be used for commercial purposes and this
confidential information must only be used to the extent provided for in this
agreement or otherwise to the extent as expressly authorized by the dis-
closing party in written form. The customer has the right, subject to the ob-
ligation to confidentiality, to disclose the terms and conditions of this
agreement directly to his legal and financial consultants as would be re-
quired for the customer's normal business operation.
Export provisions
The delivered product (including technical data) is subject to the legal ex-
port and/or import laws as well as any associated regulations of various
countries, especially such laws applicable in Germany and in the United
States. The products / hardware / software must not be exported into such
countries for which export is prohibited under US American export control
laws and its supplementary provisions. You hereby agree to strictly follow
the regulations and to yourself be responsible for observing them. You are
hereby made aware that you may be required to obtain governmental ap-
proval to export, reexport or import the product.

Appendix 89/92
12.2 Registered Trademarks

Windows® XP, Windows® Vista and Windows® 7 are registered trademarks
of Microsoft Corporation.
Adobe-Acrobat® is a registered trademark of the Adobe Systems Incorpo-
rated.
CANopen® is a registered trademark of CAN in AUTOMATION - Interna-
tional Users and Manufacturers Group e.V (CiA), Nürnberg.
CC-Link® is a registered trademark of Mitsubishi Electric Corporation, To-
kyo, Japan.
DeviceNet® and EtherNet/IP® are trademarks of ODVA (Open DeviceNet
Vendor Association, Inc).
Modbus® is a registered trademark of Schneider Electric.
PROFIBUS and PROFINET are registered trademarks of PROFIBUS Inter-
national, Karlsruhe.
All other mentioned trademarks are property of their respective legal own-
ers.

Appendix 90/92
12.3 List of Figures

Figure 1: Function NT 50 17
Figure 2: Device Drawings 22
Figure 3: LEDs and Control Elements 23
Figure 4: Range of Values for the Address Switches 23
Figure 5: Galvanic Isolation of NT 50-xx-EN Devices 32
Figure 6: Galvanic Isolation of NT 50-xx-RS Devices 33
Figure 7: Galvanic Isolation of NT 50 -RS-EN Devices 34
Figure 8: Mounting the netTAP NT 50 device onto the top-hat rail 35
Figure 9: Removing the NT 50 device from the Top-Hat Rail 35
Figure 10: LEDs 41
Figure 11: D-Sub Cable Assemblies 70
Figure 12: PROFIBUS-DP-Network 72
Figure 13: Termination CANopen Network 74
Figure 14: DeviceNet Network 75
Figure 15: CC-Link Network 77
Figure 16: RS-232 Null-Modem Cable Connection 79
Figure 17: RS-422 Wiring 80
Figure 18: RS-485 Wiring 82
12.4 List of Tables

Table 1: List of Revisions 5
Table 2: Reference to Hardware 7
Table 3: Reference to Software 7
Table 4: Directory Structure of the gateway solution DVD 8
Table 5: Device Description Files for netTAP NT 50 on the DVD 9
Table 6: Basic Documentation for netTAP NT 50 10
Table 7: Additional Documentation for netTAP NT 50 with EtherNet/IP Scanner/Master Link 10
Table 8: Additional Documentation for netTAP NT 50 with PROFINET IO Controller Link 11
Table 9: Additional Documentation for netTAP NT 50 with CANopen Master Link 11
Table 10: Additional Documentation for netTAP NT 50 with DeviceNet Master Link 11
Table 11: Additional Documentation for netTAP NT 50 with PROFIBUS DP Master Link 11
Table 12: Additional Documentation for netTAP NT 50 with ASCII 11
Table 13: Safety Symbols and Sort of Warning or Principle 16
Table 14: Signal Words 16
Table 15: Network on port X2 (Primary Network) 18
Table 16: Network on port X3 (Secondary Network) 18
Table 17: List of Protocol Conversion and NT 50 Device Type 19
Table 18: Supply Voltage Pin Assignment 24
Table 19: CANopen Pin Assignment 24
Table 20: CC-Link Pin Assignment 24
Table 21: DeviceNet Pin Assignment 25
Table 22: PROFIBUS RS-485 Pin Assignment 25
Table 23: RS-232 Pin Assignment 26
Table 26: Ethernet RJ45 Pin Assignment 28
Table 27: RJ45 Ethernet / RS-232 Pin Assignment 29
Table 30: Coupling NT 50-xx-EN Devices 32
Table 31: Coupling NT 50-xx-RS Devices 33
Table 32: Coupling NT 50-RS-EN Devices 34
Table 33: NT 50 Troubleshooting 39
Table 34: LEDs EtherNet/IP Scanner (Master) 42
Appendix 91/92
Table 35: LEDs EtherNet/IP Adapter (Slave) 43
Table 36: LEDs Open Modbus/TCP 44
Table 37: LEDs PROFINET IO-RT Controller 45
Table 38: LEDs PROFINET IO-RT-Device 46
Table 39: LEDs PROFIBUS DP Master – 1 Communication LED 47
Table 40: LEDs PROFIBUS DP Slave 47
Table 41: LEDs CANopen Master 48
Table 42: LED State Definition for CANopen Master for the CAN LED 48
Table 43: LEDs CANopen Slave 49
Table 44: LED State Definition for CANopen Slave for the CAN LED 49
Table 45: LEDs DeviceNet Master 50
Table 46: LEDs DeviceNet Slave 50
Table 47: LEDs CC-Link Slave X2 51
Table 48: LEDs Modbus RTU Protocol 52
Table 49: LEDs ASCII Protocol 52
Table 50: Technical Data NT 50 (Part 1) 53
Table 51: Technical Data NT 50 (Part 2) 54
Table 52: Technical Data EtherNet/IP Scanner (Master) Link Protocol 55
Table 53: Technical Data EtherNet/IP Adapter (Slave) Protocol 56
Table 54: Technical Data Open Modbus/TCP Protocol 57
Table 55: Technical Data PROFINET IO RT Controller Link Protocol 58
Table 56: Technical Data PROFINET IO Device Protocol 59
Table 57: Technical Data CANopen Master Link Protocol 60
Table 58: Technical Data CANopen Slave Protocol 61
Table 59: Technical Data CC-Link-Slave Protocol 62
Table 60: Technical Data DeviceNet Master Link Protocol 63
Table 61: Technical Data DeviceNet Slave Protocol 64
Table 62: Technical Data PROFIBUS DP Master Link Protocol 65
Table 63: Technical Data PROFIBUS DP Slave Protocol 66
Table 64: Technical Data ASCII Protocol 67
Table 65: Technical Data Modbus RTU Protocol 68
Table 66: Use of Hubs and Switches 71
Table 67: PROFIBUS Segment Length in Dependence of the Baud Rate 73
Table 68: Characteristics of PROFIBUS certified Cable 73
Table 69: Characteristics of CAN certified Cable 74
Table 70: CAN Segment Length in dependence of the Baud rate or corresponding Loop Resistance and
Wire Gauge 74
Table 71: Maximum length in dependence from the Baud Rate for DeviceNet Cables 75
Table 72 Characteristics of DeviceNet Data Line Cable 75
Table 73: Characteristics of DeviceNet Power Supply Cable 75
Table 74: DeviceNet Segment Length in dependence of the Baud rate 76
Table 75: Maximum length 78
Table 76: Maximum length 78
Table 77: Minimum distance between two devices 78
Table 78: Electric Requirements to RS-422 Cables 81
Table 79: RS-422 Conductor Length and Transmission Rates 81
Table 80: Electric Requirements to RS-485 Cables 83
Table 81: RS-485 Cable Lengths 83

Appendix 92/92
12.5 Contacts
Headquarters Japan
Hilscher Japan KK
Germany Tokyo, 160-0022
Hilscher Gesellschaft für Systemautomation mbH Phone: +81 (0) 3-5362-0521
Rheinstraße 15 E-mail: [email protected]
D-65795 Hattersheim Support
Phone: +49 (0) 6190 9907-0 Phone: +81 (0) 3-5362-0521
Fax: +49 (0) 6190 9907-50 E-mail: [email protected]
E-mail: [email protected]
Support Republic of Korea
Phone: +49 (0) 6190 9907-990 Hilscher Korea Inc.
E-mail: [email protected] 13494, Seongnam, Gyeonggi
Phone: +82 (0) 31-739-8361
Subsidiaries E-mail: [email protected]
Support
China Phone: +82 (0) 31-739-8363
Hilscher Systemautomation (Shanghai) Co. Ltd. E-mail: [email protected]
200010 Shanghai
Phone: +86 (0) 21-6355-5161 Austria
E-mail: [email protected] Hilscher Austria GmbH
Support 4020 Linz
Phone: +86 (0) 21-6355-5161 Phone: +43 732 931 675-0
E-mail: [email protected] E-mail: [email protected]
Support
France Phone: +43 732 931 675-0
Hilscher France S.a.r.l. E-mail: [email protected]
69800 Saint Priest
Phone: +33 (0) 4 72 37 98 40 Switzerland
E-mail: [email protected] Hilscher Swiss GmbH
Support 4500 Solothurn
Phone: +33 (0) 4 72 37 98 40 Phone: +41 (0) 32 623 6633
Support
India Phone: +41 (0) 32 623 6633
Hilscher India Pvt. Ltd. E-mail: [email protected]
Pune, Delhi, Mumbai, Bangalore
Phone: +91 8888 750 777 USA
E-mail: [email protected] Hilscher North America, Inc.
Support Lisle, IL 60532
Phone: +91 8108884011 Phone: +1 630-505-5301
Support
Italy Phone: +1 630-505-5301
Hilscher Italia S.r.l. E-mail: [email protected]
20090 Vimodrone (MI)
Phone: +39 02 25007068
Support
Phone: +39 02 25007068


netTAP NT 50 - Gateway Devices UM 18 EN

Uploaded by

Copyright:

Available Formats

netTAP NT 50 - Gateway Devices UM 18 EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

netTAP NT 50 - Gateway Devices UM 18 EN

Uploaded by

Copyright:

Available Formats

User Manual

Hilscher Gesellschaft für Systemautomation mbH

3 DESCRIPTION AND REQUIREMENTS ................................................................... 17

4 DEVICE DRAWINGS AND CONNECTIONS ............................................................ 22

netTAP NT 50 | Gateway Devices

9 TECHNICAL DATA ................................................................................................... 53

netTAP NT 50 | Gateway Devices

10 WIRING INSTRUCTIONS ......................................................................................... 69

netTAP NT 50 | Gateway Devices

1.1.1 Obligation to read and understand the Manual

1.1.2 List of Revisions

netTAP NT 50 | Gateway Devices

1.1.3 Conventions in this Manual

<note, where to find further information>

netTAP NT 50 | Gateway Devices

1.2 Reference to Hardware, Software and Firmware

netTAP NT 50 | Gateway Devices

1.3 Contents of the Product DVD

1.3.1 Directory Structure of the DVD

netTAP NT 50 | Gateway Devices

netTAP NT 50 | Gateway Devices

1.3.3 Documentation for netTAP NT 50

Basic documentation for netTAP NT 50

User Manual Software Installation Software Installation - Gateway Solutions UM

netTAP NT 50 with EtherNet/IP Scanner/Master Link

netTAP NT 50 | Gateway Devices

netTAP NT 50 with CANopen Master Link

netTAP NT 50 with DeviceNet Master Link

netTAP NT 50 with PROFIBUS DP Master Link

netTAP NT 50 with ASCII

netTAP NT 50 | Gateway Devices

2.2 Intended Use

2.3 Personnel Qualification

2.4 References Safety

netTAP NT 50 | Gateway Devices

2.5 Safety Instructions to avoid Personal Injury

2.5.1 Danger of unsafe System Operation

netTAP NT 50 | Gateway Devices

2.6 Safety Instructions to avoid Property Damage

2.6.1 Power disconnect during firmware or configuration download

netTAP NT 50 | Gateway Devices

2.6.2 Device Destruction by exceeding allowed Supply Voltage

2.6.3 Exceeding the maximum number of allowed write/delete ac-

2.6.4 Danger of unsafe System Operation

netTAP NT 50 | Gateway Devices

2.7 Labeling of Safety Messages

Table 13: Safety Symbols and Sort of Warning or Principle

Signal Word Meaning Meaning (USA)

netTAP NT 50 | Gateway Devices

3 Description and Requirements

The interface X2 is a fieldbus interface, the interface X3 may be an Ether-

netTAP NT 50 | Gateway Devices

3.2 Device Types and Protocol Conversions

1. Device Type netTAP 50

The following communication systems are currently supported at the prima-

The following communication systems are currently supported at the sec-

netTAP NT 50 | Gateway Devices

3.3 System Requirements

In order to avoid damage caused by overheating or freezing, it is necessary