Home

netTAP NT 50 - Gateway Devices (User manual)

1. Hm 16 2 1 General Note srair aei 16 2 2 Mende d cy me ee 16 2 3 Personnel QUANG dll accessi dketc onse ut ae 16 2 4 FRETETENCES SAlGLY sus aha 16 2 5 Safety Instructions to avoid Personal INJULY cccccceececececeeeeaeeeseeeeeeeeeeeeaeeeeeees 17 2 5 1 Danger of unsafe System Operation ccccccseeeceeceeeeeeeaeeeeeeaeeeeeeaeeeeesaeeeeeseees 17 2 6 Safety Instructions to avoid Property Damage ccccccecccseccceeeeeeeeseeeeeeeeaeeesaues 17 2 6 1 Device Destruction by exceeding allowed Supply Voltage 17 2 6 2 Danger of unsafe System Operation cccccccseeeeeeceeeeeeeeeeeeeseeeeeeeaeeeeesaeeseeeeees 17 2 7 Labeling of Safety Messages 2220220002200onnnennnonnnnnnnennnne nano nenn nenne nenn nnnnennnnn nenn 18 3 DESCRIPTION AND REQUIREMENTS eeeeeeeene nnne 19 3 1 Device4J3esciplloOl s er bra FU ster o Lc ab ebuted cd E a 19 3 2 Device Types and Protocol Conversions 2 2002200200000nnnnno nenn nano nenne anne nnnnn nenn 20 3 2 1 Device Names age ee ea I ETEN 20 3 2 2 Protocol Conversions T 21 3 3 System Regulrermelbls c rss en 22 3 4 Configuration Requirements 222002200222002n00 nenn nano nenn nano nenne nenne nenn nnns nennen 22 4 DEVICE DRAWINGS AND CONNECTIONS eee 23 4 1 Device and Di
2. 0V Ground of supply voltage GND 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 2 emi eminere ISO CAN ground GND CAN H CAN High bus line a u oe amp 5 Important note and strongly 6 8 recommended Leave these pins ER 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 73 4 3 2 2 X2 for Device Type NT 50 CC xx CC Link Pin Assignment coum Pin sea essen 000000000 a fa Dmapsie 2 baanga 3 DG Dwagemd 4 mo _ Shield internally connected to common ground Field ground internally connected to common ground female Table 20 CC Link Pin Assignment Please note the wiring instructions in section CC Link on page 76 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 26 86 4 3 2 3 X2 for Device Type NT 50 DN xx DeviceNet Pin Assignment Ce ON Mam ISO GND Common ground DeviceNet power supply CANL CAN Low signal CANH 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 74 4 3 2 4 X2 for Device Type NT 50 D
3. 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 version 1 351 or higher and can be used with firmware version 1 1 or higher netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 62 86 9 3 4 DeviceNet Master Link Parameter Description Pam oen 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 Baud rates 125 kBits s 250 kBit s 500 kBit s Auto baudrate detection is not supported Data transport layer CAN frames User data transfer through the gateway only via IO connections Reference to firmware stack version V2 2 X X Table 60 Technical Data DeviceNet Master Link Protocol netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 63 86 9 3 5 DeviceNet Slave Parameter Description Maximum number of cyclic input data 255 bytes Maximum number of cyclic output data 255 bytes Connections Poll Change of state
4. M v n 5V i Pull Up c D1 1 a n YS Ju DO L u Pull Down WU GND Slave1 Slave n m netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 82 86 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 DO of approximately the amount of the characteristic wave imped ance of the cable which usually amounts to a value between 120 and 220 Q The pull up and pull down resistors should have a value of 390 up to 650 Q 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 Q150 impedance Capacitance lt 30 pF m Loop resistance 110 O km 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 Table 81 RS 485 Cable Lengths netTAP NT 50 Gateway Devices DOC091202UM13EN R
5. netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 33 86 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 VIN 18 80Vdc X1 Figure 6 Galvanic Isolation of NT 50 xx RS Devices en galv Iso Coupling against PE Functional earthing to ae Protocol lation Coupling potential PE HF CD Cf 10 nF 500 V is Lf 47 uH no o1 C 4 10nF 500V CC Link Cx2 2 3 3 nF 1000 V directly CANopen optisch Cx2 2 1 MQ 15 nF 1000 V directly via the metal connection of the D Sub male connector DeviceNet optically Cx2 2 1 MQ 15 nF 1000 V Combicon Pin 3 1 MQ 15 nF 1000V Profibus DP inductive Cx2 2 1 MQ 2 2 nF 1000 directly via the metal V connection of the D Sub female connector Directly via the metal connection of RJ 45 Sockets Ethernet inductive Cx3 3 2 75Q 1 nF 2000 V only for diag nostic Directly via the metal connection of RJ 45 sockets Table 31 Coupling NT 50 xx RS Devices netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 34 86 4 4 3 Galvanic Isolation of NT 50 RS EN The device type
6. 17 Shield Figure 16 RS 232 Null Modem Cable Connection Pinning of the remote device see device description of the used devi ce Conductor length and transmission rates In the EIA 232 norm a maximum cable ca pacitance of 2500 pF is allowed for a RS232 connection Cables of such capacitance may have the following lengths depending on the baud rate 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 HS EN on page 27 Pin assignmet for connector X3 see section X3 for Device Type NT 50 xx RS on page 28 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 10 8 RS 422 A 79 86 NOTICE Device Damage Make sure that the NT 50 device and the remote device via RS 422 have the same potential or insert a galvanic isolation to avoid compen sation current between the used devices 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 ra tes of up to 10 MBit s at maximally 12 m length of line are possible
7. e Safety and health at work e Mounting and attaching of electrical equipment e Measurement and Analysis of electrical functions and systems e Evaluation of the safety of electrical systems and equipment e 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 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Safety 17 86 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 in jury 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 2 6 Safety Instructions to avoid Property Damage To avoid property damage respectively device destruction of the netTAP NT 50 device you n
8. Different IO Devices can be configured with different cycle times Baud rate 100 MBit s Full Duplex mode Data transport layer Ethernet Il IEEE 802 3 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 netTAP NT 50 Gateway Devices DOCO
9. F hilsecher COMPETENCE IN COMMUNICATION User Manual netTAP NT 50 Gateway Devices Hilscher Gesellschaft f r Systemautomation mbH www hilscher com DOC091202UM13EN Revision 13 English 2015 01 Released Public Introduction 2 86 Table of Contents 1 INTRODUCTION UE 5 1 1 ADOUNC User MANUA geie a 5 1 1 1 Obligation to read and understand the Manual cccccecseeeeeseeeeeeeeeeeeesaeeeees 5 1 1 2 EISEORREVISIONS Tm ME 6 1 1 3 Conventions in this Manual cccccceecccceeceeceeeeceeeeseeeeeseeecesaeeeeseeeeeseeeseeeessnes 7 1 2 Reference to Hardware Software and Firmware cceceecececeeeececeeeeeeceseeeeeeseeaees 8 1 3 Contents Or the fogucl DYD 5i denda olus ea 9 1 3 1 Directory Structure of the DVD za a esae DA IP EteU dui Use 9 1 3 2 Device Description Files cccccsscccseeccseeceececeuceceeeeceeecaeeceeessueesaueeseeeeeseesees 10 1 3 3 Documentation for netTAP NT 50 seesseeesssesssseeeneeee nennen nnns 11 1 4 EGgOluNDIOS eus ea aa yet aac a A IM re IM f ee Ei euer 13 1 4 1 rein TIN ni 55 Bas eect E Ee E 13 1 4 2 Important INOIOS mee A 13 1 4 3 EXGCIUSION OFLA IY e EP 14 1 4 4 MN GAMO e S 14 1 4 5 EXO lis SO UIANO AS ea ane t atus Sos cttam An tun tua doe 15 1 4 6 Registered Trademarks cccccscccseeccseeceecceuceceuceceeecseeseueeceueeseuesaueeseeeeseeeseas 15 2 light
10. Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 59 86 9 3 Technical Data Fieldbus Protocols 9 3 1 CANopen Master Link Parameter Description Maximum number of CANopen nodes 1 to one node only Maximum number of cyclic input data 512 bytes Maximum number of cyclic output data 512 bytes 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 Table 57 Technical Data CANopen Master Link Protocol netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 60 86 9 3 2 CANopen Slave Parameter Description Maximum number of cyclic input data 512 bytes Objects 2200 2201 2202 2203 each with up to 128 bytes Maximum number of cyclic output data 512 bytes Objects 2000 2001 2002 2003 each with up to 128 bytes 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 prot
11. MBit s 6 MBit s 12 MBit s 10 kBit s 20 kBit s 50 kBit s 100 kBit s 125 kBit s 250 kBit s 500 kBit s 800 kBit s 1 MBit s 125 kBit s 250 kBit s 500 kBit s RJ45 Ethernet and serial interface to gether in one connector Hilscher 2010 2015 Technical Data 54 86 9 2 Technical Data of Real Time Ethernet Communication Protocols 9 2 1 EtherNet IP Scanner Master Link 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 Limitations No acyclic user data communication CIP Sync Services are not implemented TAGs are not supported Table 52 Technical Data EtherNet IP Scanner Master Link Protocol netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 55 86 9 2 2 EtherNet IP Adapter Slave Parameter Description Predefined standard objects Identity Object Message Route Object Assembly Object Connection Manager Ethernet Link Object TCP IP Object Limitations No acyclic user data communication CIP Sync Services are not implemented TAGs are not supported ACD Address Conflict Detection not supported DLR not supported ring topology Table 53 Technical Data EtherNe
12. NXF Modbus RTU Master Slave N5COSMBR NXF NT 50 DN EN DeviceNet Master for one sla EtherNet IP Adapter Slave N5DNMEIS NXF ve PROFINET IO Device N5DNMPNS NXF Open Modbus TCP N5DNMOMB NXF DeviceNet Slave EtherNet IP Adapter Slave N5DNSEIS NXF EtherNet IP Scanner Master 1 NSDNSEIM NXF PROFINET IO Device N5DNSPNS NXF PROFINET IO Controller 1 N5DNSPNM NXF Open Modbus TCP N5DNSOMB NXF NT 50 DN RS DeviceNet Master for one sla ASCII N5DNMASC NXF ve Modbus RTU Master Slave N5DNMMBR NXF DeviceNet Slave ASCII N5DNSASC NXF Modbus RTU Master Slave N5DNSMBR NXF NT 50 DP EN PROFIBUS DP Master for one EtherNet IP Adapter Slave N5DPMEIS NXF PROFINET IO Device N5DPMPNS NXF Open Modbus TCP N5DPMOMB NXF PROFIBUS DP Slave EtherNet IP Adapter Slave N5DPSEIS NXF EtherNet IP Scanner Master 1 NSDPSEIM NXF PROFINET IO Device N5DPSPNS NXF PROFINET IO Controller 1 N5DPSPNM NXF Open Modbus TCP N5DPSOMB NXF NT 50 DP RS PROFIBUS DP Master for one ASCII N5DPMASC NXF 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 NSMBREIM NXF PROFINET IO
13. RS422 RxD Receive data positive X3 netTAP50 The figure on the right shows a Y RJ45 Plug cable adapter for the separation of 29 c the RS 422 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 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 RJ45 Socket tion Ethernet wihte brown RxO white blue TxD X3 netTAP50 You can use a direct cable con X3netTAP50 RJ45 Plug nection to the RS 422 remote RJ45 Plug device as shown on the right 12345678 An Ethernet cable is required for SE configuration of the device as shown on the left which has to be plugged into the X3 RJ45 socket instead of the RS 422 cable dur ing configuration of the NT 50 device Diagnostic is not possible while the RS 422 interface is used with the cable shown at the right _W__ Shield wl RJ45 Plug D Sub 9 Ethernet RS422 Diagnostics PC Remote device netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 31 86 RS 485 and Ethernet on RJ45 Pin Assignment ethernet Pin Signal Deer 12345678 T 6 Ethernet RX Receive data negative To motused 0000
14. The maximum useable transmission rate depends on the technical data of the used devices The following illustration shows wiring for RS 422 T Master lj IA 9v iT L Pull Up ur Pull Down 5V GND i Pull Up T lh E il Pull Down n PESE GND E Slave 1_ Slaven Figure 17 RS 422 Wiring Bus Requirements The bus cable must be a shielded 4 wire twisted pair cable Each pair of wi res 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 O to 150 O 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 O up to 650 Q netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 80 86 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 1500 150 impedance Capacitance lt 30 pF m Loop resistance 110 O km Table 78 Electric Requirements to RS 422 Cables The following
15. con nector Table 50 Technical Data NT 50 Part 1 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data NT 50 Parameter 03 86 Value Ethernet Interface for the device types NT 50 DP EN NT 50 CO EN NT 50 DN EN NT 50 RS EN PROFIBUS Interface for the device types NT 50 DP EN CANopen Interface for the device type NT 50 CO XX DeviceNet Interface for the device type NT 50 DN EN Serial Interface for the device type NT 50 xx RS Transmission rate Interface Type Auto Negotiation 100 MBit s 10 MBit s depending on loaded firmware 100 BASE TX isolated 10 BASE TX depending on loaded firmware isolated Half duplex Full duplex supported at 100 MBit s supported depending on loaded firmware Transmission rate Connector Interface Type Connector Transmission rate Interface Type Connector Interface Type Connector Table 51 Technical Data NT 50 Part 2 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public RS 485 optically isolated Interface Type Transmission rate ISO 11898 optically isolated SubD male 9 pin ISO 11898 optically isolated COMBICON 5 pin RS 232 RS 422 RS 485 9 6 kBit s 19 2 kBit s 31 25 kBit s 45 45 kBit s 93 75 kBit s 187 5 kBit s 500 kBit s 1 5 MBit s 3
16. contractual obligations are lim ited to damages that are foreseeable and typical for this type of contract It is strictly prohibited to use the software in the following areas e for military purposes or in weapon systems e for the design construction maintenance or operation of nuclear facili ties e in air traffic control systems air traffic or air traffic communication sys tems e in life support systems e in systems in which failures in the software could lead to personal injury or injuries leading to death We inform you that the software was not developed for use in dangerous environments requiring fail proof control mechanisms Use of the software in such an environment occurs at your own risk No liability is assumed for damages or losses due to unauthorized use 1 4 4 Warranty Although the hardware and software was developed with utmost care and tested intensively Hilscher Gesellschaft f r Systemautomation mbH does not guarantee its suitability for any purpose not confirmed in writing It can not be guaranteed that the hardware and software will meet your require ments that the use of the software operates without interruption and that the software is free of errors No guarantee is made regarding infringe ments violations of patents rights of ownership or the freedom from inter ference by third parties No additional guarantees or assurances are made regarding marketability freedom of defect of title integr
17. for the PC are e PC with 1 GHz processor or higher e Windows XP SP3 Windows Vista 32 bit SP2 Windows 7 32 bit or Windows 7 64 bit e Administrator rights e Internet Explorer 5 5 or higher e Free disk space min 400 MByte e DVD ROM drive e RAM min 512 MByte recommended 1024 MByte e Graphic resolution min 1024 x 768 pixel e Keyboard and Mouse e USB Note If the project file is saved and opened again or it is used on another PC the system requirements need to match Particularly the DTMs need to be installed on the used PC netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 23 86 4 Device Drawings and Connections 4 1 Device and Dimensioned Drawings Side view Front view 26 mm 60 mm 8 4 mm X1 t 25 5 mm 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 20
18. lengths of lines can be achieved Max overall length of Max Baud rate Max length of a single line branch line Table 79 RS 422 Conductor Length and Transmission Rates netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 10 9 RS 485 A 81 86 NOTICE Device Damage Make sure that the NT 50 device and the remote device via RS 485 have the same potential or insert a galvanic isolation to avoid compen sation current between the used devices 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 81 RS 485 Cable Lengths on page 82 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 i Master
19. netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 10 86 1 3 2 Device Description Files The directory EDS on the DVD provides device description files for the net TAP NT 50 device 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 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 net AP NT 50 on the DVD EtherNet IP Adapter HILSCHER NT 50 EN EIS V1 1 EDS The device description files are for the configuration of the used master netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 11 86 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 gt found in the Documentation directory on the DVD delivered in the Adobe Acrobat Reader format PDF Basic documentation for netTAP NT 50 You always ne
20. 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 e he 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 Sym Safety Symbol Sort of Warning or Principle bol USA 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 dam age message may not contain a warning triangle this property damage messages are listed separatly for the USA lL ia Warning of Damages by Electrostatic Discharge Table 13 Safety Symbols and Sort of Warning or Principle NOTICE 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 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015
21. 000 RJ45 socket fe 8 sf notused 0000000 nile PE metal housing on PE Bob Smith Abschluss Table 29 RJ45 Ethernet RS 485 Pin Assignment X3 netTAP50 The figure on the right shows a Y RJ45 Plug cable adapter for the separation of the RS 485 and the Ethernet signal lines Shield _ _ Make sure that there is no interrup tion of the shield connection when preparing the cable 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 RJ45 Socket D Sub 9 for a RS 485 connection Ethernet RS485 Shield white orange DO blue RxD TxD white blue RxD TxD X3 netTAP50 You can use a direct cable con X3 netTAP50 RJ45 Plug nection to the RS 485 remote RJ45 Plug device as shown on the right 12345678 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 485 cable dur ing configuration of the NT 50 device Diagnostic is not possible while the RS 485 interface is used with the cable shown at the right RJ45 Plug Ethernet RS485 Diagnostics PC Remote device netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Con
22. 091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 58 86 9 2 5 PROFINET IO RT Device Parameter Description Maximum number of cyclic input data 512 bytes Maximum number of cyclic output data 512 bytes Supported protocols RTC Real Time Cyclic Protocol Class 1 and 2 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 Data transport layer Ethernet Il IEEE 802 3 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 Class 2 synchronized IRT flex is not supported RT Class 3 is not supported FastStartUp is not supported Media Redundancy is not supported Access to the submodule granular status bytes IOPS amp 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 RT Device Protocol netTAP NT 50 Gateway Devices DOCO091202UM13EN
23. 1 27 Device description files updated PROFINET IO Device max 512 byte input and max 512 byte output data ASCII max telegram length is 512 bytes Table 1 List of Revisions netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 7 86 1 1 3 Conventions in this Manual Operation instructions a result of an operation step or notes are marked as follows Operation Instructions gt lt instruction gt or 1 instruction 2 instruction Results Y result Notes Important important note Note note note where to find further information Numbering e is m 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 8 86 1 2 Reference to Hardware Software and Firmware Hardware Device Type Port X2 Port X3 NT 50 CO EN CANopen Ethernet NT 50 CO RS 2 CANopen Ethernet Serial NT 50 CC EN CC Link Ethernet NT 50 CC RS CC Link Ethernet Serial NT 50 DP EN PROFIBUS DP Ethernet NT 50 DP RS PROFIBUS DP Ethernet Serial Table 2 Reference to Hardware Software Sowas o esn oo oO SYCON net 1 351 x x or higher Table 3 Referen
24. 10 2015 Device Drawings and Connections 24 86 4 2 Positions of LEDs and Control Elements Meaning of the elements 0 Connector X1 for power supply SYS LED 2 APL LED 3 COM LED 4 LED depends on protocol at X2 LED depends on protocol at X2 6 Rotary address switch factor 10 7 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 9 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 0 99 station address Valid range of values Number of Stations CC Link Slave en The number of sta tions depends on the configuration Figure 4 Range of Values for the Address Switches netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 25 86 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 0 The power supply voltage must be in the range be na 18 V and 30 V DC The plug is included in delivery Voltage Pin Assignment
25. Cyclic Bit strobe Fragmentation Explicit and I O UCMM Not supported Baud rates 125 kBits s 250 kBit s 500 kBit s Auto baudrate detection is not supported Data transport layer CAN frames Access to Application Object only via IO connection Reference to stack version V2 3 x x 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 64 86 9 3 6 PROFIBUS DP Master Link Parameter Description Maximum number of PROFIBUS DP slaves 1 to one slave only Maximum number of cyclic input data 244 bytes Parameterization data 7 bytes standard parameters Max 237 bytes application specific parameters 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 not supported Data transport layer PROFIBUS FDL Limitations Baud rate Configuration data Max 244 bytes 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 Maximum number of cyclic outp
26. Description and Requirements 19 86 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 netTAP O Data Mapping Device The interface X2 is a fieldbus interface the interface X3 may be an Ethernet 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 netIAP NT 50 device is configured by a PC and the software SYCON net Online diagnosis is possible via the same interface The Ethernet interface of the netT AP NT 50 device is used for configuration and for diagnostic This PC is a part of the Ethernet network Figure 1 Function NT 50 m Information about the configuration of the device with SYCON net soft ware is in the manual Configuration of Gateway and Proxy Devices Ol xx EN pdf on the product DVD in the directory Documentation netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 Engli
27. 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Description and Requirements 22 86 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 NOTICE 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
28. 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 6 1 6 1 1 Information about this is in the manual Configuration of Gateway and Proxy Devices Ol xx EN pdf on the product DVD in the directory Docu mentation Note The IP address which was set with the Ethernet Device Setup ooftware is set permanently A PROFINET IO Controller may change this IP address 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 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 Ol 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 Ol xx EN pdf on the product DVD in the directory Docu mentation Important Do not interrupt the communicati
29. Ger man and international copyright law as well as international trade and pro tection provisions You are not authorized to duplicate these in whole or in part using technical or mechanical methods printing photocopying or other methods to manipulate or transfer using electronic systems without prior written consent You are not permitted to make changes to copyright no tices markings trademarks or ownership declarations The included dia grams do not take the patent situation into account The company names and product descriptions included in this document may be trademarks or brands of the respective owners and may be trademarked or patented Any form of further use requires the explicit consent of the respective rights owner 1 4 2 Important Notes The user manual accompanying texts and the documentation were created for the use of the products by qualified experts however errors cannot be ruled out For this reason no guarantee can be made and neither juristic responsibility for erroneous information nor any liability can be assumed Descriptions accompanying texts and documentation included in the user manual do not present a guarantee nor any information about proper use as stipulated in the contract or a warranted feature It cannot be ruled out that the user manual the accompanying texts and the documentation do not correspond exactly to the described features standards or other data of the delivered product No warranty or
30. NT 50 RS EN has three galvanically isolated areas The coupling to PE is shown in the following figure and in the following table X2 VIN 18 30Vdc 7 PrE OA lcu x3 RJ45 Figure 7 Galvanic Isolation of NT 50 RS EN Devices ane galv Isola l Coupling against PE Functional earthing to eme Protocol tion Coupling potential PE HF O Cf 10 nF 500 V no Lf 47 uH cxt OD 4 10 nF 500 V A HF O Cf 10 nF directly via the metal Lf 47 uH connection of the D Sub no female connector et D 4 10nF 500V Directly via the metal connection of RJ 45 Sockets Ethernet inductive Cx3 2 6 750 10 nF 2000 V Table 32 Coupling NT 50 RS EN Devices netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 NT 50 Mounting and Dismounting 35 86 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 sur
31. On Receive both refresh and polling signals or just the refresh signal normally green after participating in the network d 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 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 01 86 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 COM Duo LED red green 3 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 4 with The device works as Modbus RTU Master the slave device answered with a error Modbus Exception e g protocol at f i X3 unctioncode not supported access to invalid register addresses or coil 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
32. P xx RS 485 PROFIBUS Pin Assignment prorsus mm see omen 0000000 a owe contoi sina or repeater drin con s ve Powersupply postive zer 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 kQ is connected device internally at Rx Tx A pull down resistor of 100 kQ is connected device internally at Rx Tx Please note the wiring instructions in section PROFIBUS on page 71 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 27 86 4 3 2 5 X2 for Device Type NT 50 RS EN RS 232 Pin Assignment LM NM NE M e LRD Aeman polenta uud of ponor supply Reference potential ground of power supply ee data 9 pole sub D socket male Table 23 RS 232 Pin Assignment Please note the wiring instructions in section HS 232 on page 78 RS 422 Pin Assignment RS 422 Pin Signal Description Receive data positive 6 TxD Transmitdatapositve aec TxD Transmit data negative 9 pole sub D socket male Table 24 RS 422 Pin Assignment A pull up resistor of 10 KQ is connected device internally at RxD A pull down resistor of 10 KO is connected device internally at RxD Please note the wiring instructions in section RS 422 on page 79 RS 485 Pin Assignment 1 GND Re
33. Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 73 86 10 4 CANopen Please use only CAN certified cable with the following characteristics Capacity per lt 50 pF m units length Table 69 Characteristics of CAN certified Cable Erstes Gerat Letztes Gerat First device Last device CAN_H CAN_H 120 j u CAN_L c B E CAN L 3 CAN_GND CAN GND Figure 13 Termination CANopen Network At the ends of the network there must be two resistors of 120 O 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 1000 m 26 O km 0 75 0 80 mm 1000 m 26 O km 0 75 0 80 mm 1000 m 26 Q km 0 75 0 80 mm Table 70 CAN Segment Length in dependence of the Baud rate or corresponding Loop Re sistance and Wire Gauge netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 74 86 10 5 DeviceNet Up to 64 DeviceNet devices can be linked together over the bus The maximum length of the bus cable depends on the used baud rate and the used cable type Only special proved DeviceNet cable sh
34. SCII Table 15 Network on port X2 Primary Network The following communication systems are currently supported at the sec ondary network X3 Supported Communication System Ethernet 1 RJ45 Serial Modbus RTU or ASCII RJ45 Table 16 Network on port X3 Secondary Network netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Description and Requirements 21 86 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 Firmware Version NT 50 CC EN CC Link Slave EtherNet IP Adapter Slave N5CCSEIS NXF 1 1 x x EtherNet IP Scanner Master 1 NSCCSEIM 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 for one sla EtherNet IP Adapter Slave N5COMEIS NXF ve PROFINET IO Device N5COMPNS NXF Open Modbus TCP N5COMOMB NXF CANopen Slave EtherNet IP Adapter Slave N5COSEIS NXF EtherNet IP Scanner Master 1 NSCOSEIM NXF PROFINET IO Device N5COSPNS NXF PROFINET IO Controller 1 N5COSPNM NXF Open Modbus TCP N5COSOMB NXF NT 50 CO RS CANopen Master for one sla ASCII N5COMASC NXF ve Modbus RTU Master Slave N5COMMBR NXF CANopen Slave ASCII N5COSASC
35. SLD iH L sip i t oANM Ibs I baillos TM DB SLO DB SLO Termination resistor depends on the used cable type see CC Link Cable Wiring Manual 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 77 86 Only trunk line without branches Baud rate max Length max Length ca max length high cable V1 00 ble V1 10 and flexible V1 10 cable V1 00 with Type 50 high capacity 156 kbps 1200 m 1200 m Table 75 Maximum length Note Further cable types are available with which however only lower gt maximum lengths can be reached Trunk line with branch lines max length trunk line 500 m max number of devices in branch line max cable length of branch m line max length of all branch 200 m 50 m lines Table 76 Maximum length Further dev
36. UE 9 4 2 Modbus RTU Master Slave esses 10 WIRING INSTRUCTIONS nmm 10 1 Assembly of D Sub Connectors 10 2 EMNENE TET LT 10 3 PROFIBUS Ss es 22252 Reale 10 4 GANOPE c 10 5 BIS IINE TEUER 10 6 978 d TT 10 7 RO M 10 8 atero P 10 9 BOS oe alo REIN NE T T 11 DECOMMISSIONING DISPOSAL tmm e 11 1 Put the Device out of Operation 11 2 Disposal of Waste Electronic Equipment 12 APPENDIX On Tm 12 1 HENS GOW str IQS ee ee een 12 2 Eisto TV ADISS ee r 12 3 COMMACS rissa Siete ios ial cs ait anda a DEL da pete netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 5 86 1 Introduction 1 1 About the User Manual This user manual describes the hardware installation commissioning and operation of the netT AP 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 m
37. anual Keep the product DVD providing the product manuals netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 6 86 1 1 2 List of Revisions Index Date Chapter Revisions 8 2012 11 09 Firmware Version 1 1 x x 3 4 Section Configuration Requirements updated 7 1 Section Failure in 10 MBit s Half Duplex Mode and Workaround Serial numbers added 8 3 4 Section LED CANopen Slave State for baurate detection added 8 3 7 Section LED CC Link Slave added 9 2 1 Section EtherNet IP Scanner Master Link Address Conflict Detection is sup ported 9 3 2 Section CANopen Slave Event timer added Address switch added Auto baudrate detection is supported 9 3 3 Section CC Link Slave Address switch added 9 3 5 Section DeviceNet Slave Address switch added 9 3 7 Section PROFIBUS DP Slave Maximum number of modules Max 4 input modules and max 4 output mod ules max 24 modules when using manual setting Address switch added 9 2013 02 04 Section Documentation for netTAP NT 50 updated 11 2014 03 10 Section Directory Structure of the DVD updated Section X2 for Device Type NT 50 CO xx Note added that pins 1 4 5 6 8 and 9 have to stay unconnected 12 2014 03 24 9 2 3 Section Open Modbus TCP Information added Maximum number of connec tions is 16 10 4 Maximum cable length for 1 MBit s is 30 m 2015 0
38. ation or usability for certain purposes unless they are required in accordance with the law and cannot be limited Warranty claims are limited to the right to claim rectifica tion netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 15 86 1 4 5 Export Regulations The delivered product including the technical data is subject to export or import laws as well as the associated regulations of different counters in particular those of Germany and the USA The software may not be ex ported to countries where this is prohibited by the United States Export Administration Act and its additional provisions You are obligated to com ply with the regulations at your personal responsibility We wish to inform you that you may require permission from state authorities to export re export or import the product 1 4 6 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 Schne
39. ble and all netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 75 86 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 Linick 5 X Lini lt 500m at 125 kBaud Linick 2 5 x Linin lt 250 m at 250 kBaud Linick Lini lt 100m 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 76 86 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 Q respectively The following illustration displays the basic network structure First device Last device DA DA 100 110 o Lad SS gt i 100 110 130 DB B MM fi DB DG DG
40. ce to Software Firmware Firmware for the protocol conversion see section Protocol Conversions on page 21 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 9 86 1 3 Contents of the Product DVD The product DVD gateway solutions for the netTAP NT 50 contains e Setup program for the configuration and diagnostic software SYCON net and for the Ethernet Device Configuration software e Documentation e Firmware e Device Description Files GSD GSDML EDS e Video Audio Tutorials e 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 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 amp 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 amp 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 amp Podcasts Videos about commissioning Table 4 Directory Structure of the gateway solution DVD
41. e 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 NOTICE 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 A netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 29 86 RS 232 and Ethernet on RJ45 Pin Assignment ethernet Pin Signa Descripfon 12345678 4 RS232 3 3 V Data potential High not usable as power i supply Ri appr 300 Q RS232 GND Data reference potential ground of power supply 6 Ethernet RX Receive data negative RS232 TxD Transmit data RJ45 socket fe male 8 RS232 RxD Receive data si data PE MetalcaseonPE u Bob Smith Termination Table 27 RJ45 Ethernet RS 232 Pin Assignment X3 netTAP50 The figure on the right shows a Y RJ45 Plug cable adapter for the separation of the RS 232 and the Etherne
42. e Definition The indicator is constantly on Off The indicator is constantly off Flickering 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 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 49 86 8 3 5 LED DeviceNet Master The subsequent table describes the meaning of the LEDs for the fieldbus when the firmware of the DeviceNet Master protocol is loaded to the de vice LED Color State Meaning o MNS Duo LED red green 3 green On Device is online and has one or more connections in the established state Flashing Device is online and has no connection in the established state all Ber Green Red Selftest after power on green red Off Green on for 0 25 s then red on for 0 25 s then off e Flashing Connection timeout Q ceo Critical connection failure device has detected a network err
43. e connected as follows 1 2 3 A m T Dismantle the cable Pull back the shielding from the cable sheathing Reduce the shielding that later it is covered by the nozzle Push a nozzle or shrinking tube over the cable sheathing that at the cable end a zone of 5 to 8 mm remains free Connect the wire ends with the connector Then push the cable in the plug to the bare braided shield under the strain relief Fix the strain relief with screws The cable connection should look like shown below Figure 11 D Sub Cable Assemblies netTAP NT 50 Gateway Devices 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 DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 70 86 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 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 Nego
44. ecessarily 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 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 net AP 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 22 There the re quired and permitted supply voltage for the netT AP NT 50 device is pro vided inclusively the permitted tolerance range 2 6 2 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Safety 18 86 2 Labeling of Safety Messages e he Section Safety Messages at
45. ed the following documents Manua Contents DowmetMame 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 Ol xx EN pdf Assignment of an IP Address for the netT AP NT 50 Operating Instruc Configuration of Gateway and Proxy Devices Configuration of Gateway and Proxy Devices tion Manual netTAP netBRICK and netLINK Ol 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 Ol 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 tion Manual Table 7 Additional D
46. er Link Additional Documentation for netTAP NT 50 with PROFIBUS DP Master Link Additional Documentation for netT AP NT 50 with ASCII Safety Symbols and Sort of Warning or Principle Signal Words Network on port X2 Primary Network Network on port X3 Secondary Network List of Protocol Conversion and NT 50 Device Type Supply Voltage Pin Assignment CANopen Pin Assignment CC Link Pin Assignment DeviceNet Pin Assignment PROFIBUS RS 485 Pin Assignment RS 232 Pin Assignment RS 422 Pin Assignment RS 485 Pin Assignment Ethernet RJ45 Pin Assignment RJ45 Ethernet RS 232 Pin Assignment RJ45 Ethernet RS 422 Pin Assignment RJ45 Ethernet RS 485 Pin Assignment Coupling NT 50 xx EN Devices Coupling NT 50 xx RS Devices Coupling NT 50 RS EN Devices T 50 Gateway Devices 84 86 Hilscher 2010 2015 Appendix 85 86 Table 33 NT 50 Troubleshooting 38 Table 34 LEDs EtherNet IP Scanner Master 41 Table 35 LEDs EtherNet IP Adapter Slave 42 Table 36 LEDs Open Modbus TCP 43 Table 37 LEDs PROFINET IO RT Controller 44 Table 38 LEDs PROFINET IO RT Device 45 Table 39 LEDs PROFIBUS DP Master 1 Communication LED 46 Table 40 LEDs PROFIBUS DP Slave 46 Table 41 LEDs CANopen Master 47 Table 42 LED State Definition for CANopen Master for the CAN LED 47 Table 43 LEDs CANopen Slave 48 Table 44 LED State Definition for CANopen Slave for the CAN LED 48 Table 45 LEDs DeviceNet Ma
47. evision 13 English 2015 01 Released Public Hilscher 2010 2015 Decommissioning Disposal 83 86 11 Decommissioning Disposal 11 1 Put the Device out of Operation NOTICE 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 e Disconnect the communication cables from the device e Disconnect the plug for power supply e 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 2002 96 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Append IX 12 Appendix 12 1 List of Figures Figure 1 Function NT 50 Figure 2 Device Drawings Figure 3 LEDs and Control Elements Figure 4 Range of Values for the Address Switches Figure 5 Galvanic Is
48. f the network status indicator shall be steady off LINK RJ45 LED green Number in the device A connection to the Ethernet exists OS The device has no connection to the Ethernet ACT RJ45 LED yellow n wd yellow Flashing The device sends receives Ethernet frames drawing Table 34 LEDs EtherNet IP Scanner Master netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 42 86 8 2 2 LEDs EtherNet IP Adapter Slave The subsequent table describes the meaning of the LEDs for the Real Time Ethernet device when the firmware of the EtherNet IP Adapter Slave pro tocol is loaded to the device Ep Color State Meaning 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 wi green Flashing Standby If the device has not been configured the module status indicator shall be flashing green 9e Major fault If the device has detected a non recoverable major fault the module status indicator shall be steady red Q o se gt 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 M uu Flashing Self test While the device is performing its power up testin
49. face according to ar row 2 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 netT AP 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 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Commissioning 36 86 6 Commissioning 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 Ethernet interface at the bottom of the device A PC with SYCON net soft ware is necessary for configuration For communication from SYCON net software to the netTAP NT 50 device via
50. ference potential ground of power supply M RxD TxD Receive data Transmit data positive 5 RxD TxD Receive data Transmit data negative 9 pole sub D socket male Table 25 RS 485 Pin Assignment A pull up resistor of 10 KQ is connected device internally at RxD TxD A pull down resistor of 10 KQ is connected device internally at RxD TxD Please note the wiring instructions in section RS 485 on page 81 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 28 86 4 3 3 X3 Bottom Connection 4 3 3 1 X3 for Device Type NT 50 xx EN Ethernet on RJ45 Pin Assignment meme Pin Signal Descon 1 Te Transmit data positive 12345678 EI Transmit data negative Receive data positive Connected and terminated to PE via RC Receive data negative RJ45 socket f a Connected and terminated to PE via RC combination male 8 Tem2 NENNEN 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 70 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 A NOTICE Device Damag
51. g 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 Qg green On Connected If the device has at least one established connection even to me device the Message Router the network status indicator shall be steady green rawing 6 s wd 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 wd 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 d 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 ww Flashing Self test While the device is performing its power up testing the network red green status indicator shall be flashing green red Dom Off Not powered no IP address Ifthe device does not have an IP address or is powered off the network status indicator shall be steady off LED green Amber M A connection to the Ethernet exists the device green drawing The device has no connection to the Ethernet i off The device sends receives Ethernet frame
52. guarantee regarding the correctness or accuracy of the information is assumed We reserve the right to change our products and their specification as well as related user manuals accompanying texts and documentation at all times and without advance notice without obligation to report the change Changes will be included in future manuals and do not constitute any obli gations There is no entitlement to revisions of delivered documents The manual delivered with the product applies Hilscher Gesellschaft fur Systemautomation mbH is not liable under any circumstances for direct indirect incidental or follow on damage or loss of earnings resulting from the use of the information contained in this publica tion netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 14 86 1 4 3 Exclusion of Liability The software was produced and tested with utmost care by Hilscher Ge sellschaft fur Systemautomation mbH and is made available as is No war ranty can be assumed for the performance and flawlessness of the soft ware for all usage conditions and cases and for the results produced when utilized by the user Liability for any damages that may result from the use of the hardware or software or related documents is limited to cases of in tent or grossly negligent violation of significant contractual obligations In demnity claims for the violation of significant
53. iceNet Master DTM Ol xx EN pdf tion Manual Operating Instruc Generic DTM for DeviceNet Slave devices DeviceNet Generic Slave DTM Ol 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 You need the following additional documents if you use the protocol PROFIBUS DP Master on the gateway device Manual si Contents Document name Operating Instruc DTM for PROFIBUS DP Master devices PROFIBUS DP Master DTM Ol xx EN pdf tion Manual Operating Instruc Generic DTM for PROFIBUS DP Slave de PROFIBUS DP Generic Slave DTM Ol xx EN pdf tion Manual vices Table 11 Additional Documentation for netTAP NT 50 with PROFIBUS DP Master Link netTAP NT 50 with ASCII You need the following additional documents if you use the protocol ASCII on the gateway device Manual Contents Dowmetmme ASCII Handshake Mechanism ASCII Handshake Mechanism UM xx EN pdf Table 12 Additional Documentation for netTAP NT 50 with ASCII netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 13 86 1 4 Legal Notes 1 4 1 Copyright Hilscher 2010 2015 Hilscher Gesellschaft fur Systemautomation mbH All rights reserved The images photographs and texts in the accompanying material user manual accompanying texts documentation etc are protected by
54. ices 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 78 86 10 7 RS 232 NOTICE 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 A 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 Communication Communication Partner 1 Partner 2 Cable ry 7 y a RxD TxD TxD GND ST GND PE Shield 4
55. ider Electric PROFIBUS and PROFINET are registered trademarks of PROFIBUS Inter national Karlsruhe All other mentioned trademarks are property of their respective legal own ers netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Safety 16 86 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 e NT 50 CC EN e NT 50 CC RS e NT 50 CO EN e NT 50 CO RS e NT 50 DN EN e NT 50 DN RS e NT 50 DP EN e NT 50 DP RS e 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
56. 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 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Troubleshooting 39 86 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 NT 50 CC RS 20022 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 Etherne
57. 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 Q or 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 COM Duo LED red green with wd green Flashing cyclic The device sends receive data Em with 5 Hz a The device is ready for serial communication 4 with Flashing cyclic The device is configured and is in the state stop protocol at ee X3 d red Flashing cyclic The device is not configured with 1 Hz During initialisation or missing power supply Table 49 LEDs ASCII Protocol netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 52 86 9 Technical Data 9 1 Technical Data netTAP 50 Gateway Display LED Display SYS System Status APL Application Status COM Communication Status LINK Link ACT Activity Power supply Voltage 24V 6VDC Current at 24 V typically 72 mA 150 mA with short circuit at the output of PROFIBUS Continuous short circuit may cause device damage Environmental conditions Device Dimensions L x W x H 100 x 26 x 66 mm without
58. ion or low speed physical link or no physical link the device drawing o Flashing No data exchange 5 oa le at 2 Hz INoem 0 error Quo LINK RJ45 LED o On A connection to the Ethernet exists green The device has no connection to the Ethernet RX TX RJ45 LED yellow Flashing The device sends receives Ethernet frames low Table 38 LEDs PROFINET IO RT Device netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 46 86 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 LED Color State Meaning cifX Card with 1 Communication LED current Hardware Revision wi green Flashing No configuration or stack error acyclic wi green Flashing cy Profibus is configured but bus communication is not yet released from clic the application Communication to all Slaves is established Flashing cy Communication to at least one Slave is disconnected clic 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 ED Color State 1 O o COM D
59. 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 2 s Off the communication protocol on X2 is missing 0 5son or has an error Blinking with netTAP is initialized but the configuration for 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 netTAP has detected an error during the ini tialization Missing configuration error in con figuration or internal error Figure 10 LEDs netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 41 86 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 LED Color State Meaning MS Number in all green On Device operational If the device is operating correctly the module status the device indicator shall be steady green Duo LED red green drawing j wd green Flashing Standby If the device has not been configured the module status indicator shall be flashing green aul red On Major fault If the device has detected a non recoverable major fault the module status indicator shall be steady red d red Flashing Minor fault If the device has detected a
60. les from the PC ccccecccecsseeeeeseeeeeeseeeeeeaeeeeesaees 36 6 1 2 Potential Differences for Device Types NT 50 xx RS eeeeeseeeeees 37 6 2 SAUP BOMAVION TOTO S TOT TETTE 37 T TROUBLESHOOTING an a a a EES a 38 1 1 Failure in 10 MBit s Half Duplex Mode and Workaround 39 8 LED ee tate acto E Eee 40 8 1 VS SU EDS ee E E Me ee 40 8 2 LEDs Real Time Ethernet Protocols ccccceccseccceeceeeceeeceeeceeceecseecueecueeauesaaes 41 8 2 1 LEDs EtherNet IP Scanner Master cccccssceccseceeceeseeeceeeseesceaseeesseneeeseues 41 8 2 2 LEDs EtherNet IP Adapter Slave esee 42 8 2 3 LEDS Open Modbus TG P ite diis a Rs och testo irse 43 8 2 4 LEDs PROFINET IO Contfoller ipei ana 44 8 2 5 LEDs PROFINET IO RT Device eeeeeeseeeenennnnennnn ene n nnne nnnn 45 8 3 LEDS FIEIGDUSPFOIOCOIS een tere 46 8 3 1 LED PROFIBUS DP Mastek u ae 46 8 3 2 BED sPROFIBUS DP Slave 2 222228 46 8 3 3 LED CANopen Master sess nennen nennen nenne nnns seran nnns 47 8 3 4 EIS AOD Chi SIAN i en Aare een 48 8 3 5 LED DeviceNet MaSlel 4 ie i noon otn ERI baba Iis ede ee be UbdES 49 8 3 6 LED DeviceNet Slave ccccccscccsseececsseeetaseeccsecceeeccuaeeeaseeseaseeseeeeseuseseuaeess 49 8 3 7 BED C C LInK SIAVE He tr 50 8 4 LEDS SEllal Protocols RTT 51 8 4 1 ED MOGDUS RTU ae dty tr posteo u
61. mensioned Drawings esses nennen nnns 23 4 2 Positions of LEDs and Control Elements 0 ccccccccccceeceeeeeseeeeeeeeseeeseeeeeeetaeeeaes 24 4 2 1 Range of Values for the Address Switches ccccecceeesseeeeeseeeeesseeeeeesaeeeeeeas 24 4 3 COMM CCU ONS E E E OS EL 25 4 3 1 x Recuerde 25 4 3 2 AZ FROME Connector T tat cnet a entand ale Neate ted oes 25 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 3 86 4 3 3 X3 Bottom Connections esse eek alien el 28 4 4 Schematic Diagram Galvanic Isolation 022200240002200nen nenn nenn nenn ennnnen 32 4 4 1 Galvanic Isolation of NT 50 xx EN Devices 20022200022200nnennennnnnennnnnnnennn 32 4 4 2 Galvanic Isolation of NT 50 xx RS 200222200sssnunennnnennenennennennennennennnnnenennn 33 4 4 3 Galvanic Isolation of NT 50 RS EN 200222200ssssunennenennennennennennennnnnnennn 34 o NT 50 MOUNTING AND DISMOUNTING eene mmn 35 5 1 DIN Top Hat Rail Mounting of the NT 30 u222uss2sunsnennsnnnnenennnnnnenenennnnnnenenn 35 5 2 Removing the NT 50 from the DIN Top Hat Rail eeeseeeeeeeeeeeeeeeees 35 6 COMMISSIONING dated ee 36 6 1 Load Firiware and COMMNGUIAUON ucc iro e DRE neo EE ERR cen io Eee IER DRESD EE 36 6 1 1 Download Configuration Fi
62. nections 32 86 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 Ch 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 DN 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 VIN 1 8 30Vdc X1 i Figure 5 Galvanic Isolation of NT 50 xx EN Devices Con und i ecuping againetire Functional earthing to PE o Protocol Vins Coupling potential unctional ea g to HF CD Cf 10 nF 500 V 9 Lf ae 7 lod 4v nEisOV 4 10 nF 500 V CC Link Cx2 2 3 3 nF 1000 V directly to Combicon Pina to Combicon Pin 4 directly via the metal con CANopen optically Cx2 1 MQ 15 nF 1000 V mectomerthe D Subumale connector DeviceNet optically cx2 2 2 1 MQ 15 nF 1000 V 1 MO 15 nF 1000 V Combicon Pin 3 l l directly via the metal con Profibus DP inductive Cx2 2 1 MQ 2 2 nF 1000 V nection orine D Sub female connector Ethernet inductive Cx 3 6 750 1nF 2000v Directly via the metal con X3 nection of RJ 45 sockets Table 30 Coupling NT 50 xx EN Devices
63. nfo hilscher it Support Phone 39 02 25007068 E Mail it support hilscher com netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public 86 86 Japan Hilscher Japan KK Tokyo 160 0022 Phone 81 0 3 5362 0521 E Mail info hilscher jp Support Phone 81 0 3 5362 0521 E Mail jp support hilscher com Korea Hilscher Korea Inc Seongnam Gyeonggi 463 400 Phone 82 0 31 789 3715 E Mail info hilscher kr Switzerland Hilscher Swiss GmbH 4500 Solothurn Phone 41 0 32 623 6633 E Mail info hilscher ch Support Phone 49 0 6190 9907 99 E Mail ch support hilscher com USA Hilscher North America Inc Lisle IL 60532 Phone 1 630 505 5301 E Mail info hilscher us Support Phone 1 630 505 5301 E Mail us support hilscher com Hilscher 2010 2015
64. ocol consumer SDO upload download server for configuration Emergency message producer 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 Auto baudrate detection is supported Data transport layer CAN Frames CAN Frame type for CANopen 11 Bit 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 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 61 86 9 3 3 CC Link Slave Parameter Description Parameter O oes Input data remote device station 112 bytes RY and 256 bytes RWw Output data remote device station 112 bytes RX and 256 bytes RWr Station Types Remote O station Remote device station up to 4 occupied stations Output data remote I O station 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 Table 59 Technical Data CC Link Slave Protocol
65. ocumentation for netTAP NT 50 with EtherNet IP Scanner Master Link netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 12 86 netTAP NT 50 with PROFINET IO Controller Link You need the following additional documents if you use the protocol PROFINET IO Controller on the gateway device Manual si Contents Document name Operating Instruc DTM for PROFINET IO Controller devices PROFINET IO Controller DTM Ol xx EN pdf tion Manual Operating Instruc Generic DTM for PROFINET IO Device de PROFINET IO Generic Device DTM IO xx EN pdf tion Manual vices Table 8 Additional Documentation for netTAP NT 50 with PROFINET IO Controller Link netTAP NT 50 with CANopen Master Link You need the following additional documents if you use the protocol CANopen Master on the gateway device Manual si Contents Document name Operating Instruc DTM for CANopen Master devices CANopen Master DTM Ol 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 netT AP NT 50 with DeviceNet Master Link You need the following additional documents if you use the protocol DeviceNet Master on the gateway device Manual Contents Document name Operating Instruc DTM for DeviceNet Master devices Dev
66. oil 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 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 Table 65 Technical Data Modbus RTU Protocol netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 68 86 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 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 69 86 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 b
67. olation of NT 50 xx EN Devices Figure 6 Galvanic Isolation of NT 50 xx RS Devices Figure 7 Galvanic Isolation of NT 50 RS EN Devices Figure 8 Figure 9 Mounting the netTAP NT 50 device onto the top hat rail Removing the NT 50 device from the Top Hat Rail Figure 10 LEDs Figure 11 D Sub Cable Assemblies Figure 12 PROFIBUS DP Network Figure 13 Termination CANopen Network Figure 14 DeviceNet Network Figure 15 CC Link Network Figure 16 RS 232 Null Modem Cable Connection Figure 17 RS 422 Wiring Figure 18 RS 485 Wiring 12 2 Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 netTAP N DOCO091202UM13EN Revision 13 English 2015 01 Released Public List of Tables List of Revisions Reference to Hardware Reference to Software Directory Structure of the gateway solution DVD Device Description Files for net TAP NT 50 on the DVD Basic Documentation for net T AP NT 50 Additional Documentation for net AP NT 50 with EtherNet IP Scanner Master Link Additional Documentation for net AP NT 50 with PROFINET IO Controller Link Additional Documentation for net AP NT 50 with CANopen Master Link Additional Documentation for netT AP NT 50 with DeviceNet Mast
68. on 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Commissioning 37 86 6 1 2 Potential Differences for Device Types NT 50 xx RS AN NOTICE Device Destruction Make sure that for the NT 50 xx RS device and the remote device via RS 232 RS 422 respectively RS 485 have the same potential Other wise a compensating current may cause device damage because the serial interface of the NT 50 device has no galvanic isolation to its power supply 6 2 Start up Behavior The firmware and the configuration data are loaded from the FLASH mem ory 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 sec onds appr 4 seconds depending on the size of the configuration data netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Troubleshooting 38 86 7 Troubleshooting Two methods for troublesh
69. ooting exist e The visual analysis of the LED conditions of the device e The analysis via the Ethernet port along with the configuration tool SYCON 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 24 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 re placement i ad After a power cycle the device has not found a valid firmware and remains in SYS LED flashes x bootloader mode The device has to be send back to the manufacturer for yellow green at 1 Hz repair SYS LED 1 is permanet d The device has a malfunction and needs replacement yellow SYS LED 1 flaches ua yellow The device has not found a firmware The device has to be send back to the manufacturer for repair after Power On SYS LED N is permanet d The device is well initialized Further analysis is possible with the LED 2 green APL Follow the chapter System LEDs on page 40 APL LED 2 on red flashing or red on The communication via port X2 or and port X3 is not in data exchange mode Reb nasming 9 green See chapter System LEDs on page 40 Table 33 NT 50 Troubleshooting The device is operational just in case the
70. or duplicate MAC ID or sever error in CAN network CAN bus off PARET After start of the device and during duplicate MAC ID check Table 45 LEDs DeviceNet Master 8 3 6 LED DeviceNet Slave The subsequent table describes the meaning of the LEDs for the fieldbus when the firmware of the DeviceNet Slave protocol is loaded to the device LED Color State Meaning O MNS Duo LED red green wi green On Device is online and has one or more connections in the established state Flashing Device is online and has no connection in the established state wi ail Green Red Selftest after power on green red Off Green on for 0 25 s then red on for 0 25 s then off e Critical connection failure device has detected a network error duplicate MAC ID or sever error in CAN network CAN bus off Flashing Connection timeout a After start of the device and during duplicate MAC ID check Table 46 LEDs DeviceNet Slave netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 50 86 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 ED D off Off 1 Before participating in the network Name in the 2 Unable to detect carrier device 3 Timeout drawing 4 Resetting hardware COM ail
71. ould 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 250 250 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 Resis Wire cable tance Gauge Diameter Thick 120 Ohm 39 4 pf m 22 6 Ohm km Thin 120 Ohm 39 4 pf m 91 8 Ohm km Table 72 Characteristics of DeviceNet Data Line Cable The power supply cables must match the following conditions Loop Resis Wire Gauge tance Diameter Table 73 Characteristics of DeviceNet Power Supply Cable COMBICON DeviceMet Metzteil power supply for DeviceMet DeviceNet Interface DeviceNet Interface p Versorgungsleitung 5 line FN 24V 5 rot red power lines 24V GND 1 ow schwarz black F4 1 GND l s I twisted pair cable CAN Low CAN Low COMBICON Buchse COMBICON Buchse COMBICON female connector COMBICON female connector 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 ca
72. recoverable minor fault the mod ule status indicator shall be flashing red NOTE An incorrect or inconsistent configuration would be considered a minor fault ww Flashing Self test While the device is performing its power up testing the module red green status indicator shall be flashing green red ws 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 Qg green On Connected If the device has at least one established connection even to device the Message Router the network status indicator shall be steady green rawing 6 wd 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 M Flashing Self test While the device is performing its power up testing the network red green status indicator shall be flashing green red dy off Off Not powered no IP address If the device does not have an IP address or is powered of
73. s ri LINK RJ45 ACT RJ45 LED yellow Number in the device en yellow Flashing drawing Table 35 LEDs EtherNet IP Adapter Slave netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 43 86 8 2 3 LEDs Open Modbus TCP The subsequent table describes the meaning of the LEDs for the Real Time Ethernet device when the firmware of the Open Modbus TCP protocol is loaded to the device Duo LED red green Dom Off Not Ready in the OMB task is not ready device drawing all ateen 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 o Nu fe res wi red d cyclic System error 5 On Off Ratio 25 LINK RJ E green EI Em A connection to the Ethernet exists device The device has no connection to the Ethernet drawing ACT RJ LED yellow bd wd yellow Flashing The device sends receives Ethernet frames device drawing Table 36 LEDs Open Modbus TCP netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 44 86 8 2 4 LED
74. s PROFINET IO Controller The subsequent table describes the meaning of the LEDs for the Real Time Ethernet device when the firmware of the PROFINET IO RT Controller pro tocol is loaded to the device Duo LED red green Name in the together with BF red ON device draw No valid Master license u clic at 2 Hz BF Duo LED red green Name inthe red On No Connection No Link device draw or together with SF red ON ing 9 No valid Master license d red Flashing cy Configuration fault not all configured IO Devices are connected clic at 2 Hz LINK LED green age wi On A connection to the Ethernet exists green The device has no connection to the Ethernet RX TX LED yellow RJ45 Flashing The device sends receives Ethernet frames low Table 37 LEDs PROFINET IO RT Controller netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 45 86 8 2 5 LEDs PROFINET IO RT Device The subsequent table describes the meaning of the LEDs for the Real Time Ethernet device when the firmware of the PROFINET IO RT Device proto col is loaded to the device Duo LED red green Number In red On Watchdog timeout channel generic or extended diagnosis present sys the device tem error drawing Flashing DCP signal service is initiated via the bus cyclic at 2 d for 3 sec Dene BF LED red green Number in Qe No configurat
75. sh 2015 01 Released Public Hilscher 2010 2015 Description and Requirements 20 86 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 NT 50 DP EN 1 2 3 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 pri mary network X2 Supported Communication System DP PROFIBUS DP Serial Modbus RTU or A
76. ster 49 Table 46 LEDs DeviceNet Slave 49 Table 47 LEDs CC Link Slave X2 50 Table 48 LEDs Modbus RTU Protocol 51 Table 49 LEDs ASCII Protocol 51 Table 50 Technical Data NT 50 Part 1 52 Table 51 Technical Data NT 50 Part 2 53 Table 52 Technical Data EtherNet IP Scanner Master Link Protocol 54 Table 53 Technical Data EtherNet IP Adapter Slave Protocol 55 Table 54 Technical Data Open Modbus TCP Protocol 56 Table 55 Technical Data PROFINET IO RT Controller Link Protocol 57 Table 56 Technical Data PROFINET IO RT Device Protocol 58 Table 57 Technical Data CANopen Master Link Protocol 59 Table 58 Technical Data CANopen Slave Protocol 60 Table 59 Technical Data CC Link Slave Protocol 61 Table 60 Technical Data DeviceNet Master Link Protocol 62 Table 61 Technical Data DeviceNet Slave Protocol 63 Table 62 Technical Data PROFIBUS DP Master Link Protocol 64 Table 63 Technical Data PROFIBUS DP Slave Protocol 65 Table 64 Technical Data ASCII Protocol 66 Table 65 Technical Data Modbus RTU Protocol 67 Table 66 Use of Hubs and Switches 70 Table 67 PROFIBUS Segment Length in Dependence of the Baud Rate 72 Table 68 Characteristics of PROFIBUS certified Cable 72 Table 69 Characteristics of CAN certified Cable 73 Table 70 CAN Segment Length in dependence of the Baud rate or corresponding Loop Resistance and Wire Gauge 73 Table 71 Maximum length in dependence from the Baud Rate for DeviceNet Cables 74 Table 72 Characteristics of DeviceNe
77. t Data Line Cable 74 Table 73 Characteristics of DeviceNet Power Supply Cable 74 Table 74 DeviceNet Segment Length in dependence of the Baud rate 15 Table 75 Maximum length TT Table 76 Maximum length 7 Table 77 Minimum distance between two devices TT Table 78 Electric Requirements to RS 422 Cables 80 Table 79 RS 422 Conductor Length and Transmission Rates 80 Table 80 Electric Requirements to RS 485 Cables 82 Table 81 RS 485 Cable Lengths 82 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Appendix 12 3 Contacts Headquarters Germany Hilscher Gesellschaft fur Systemautomation mbH Rheinstrasse 15 65795 Hattersheim Phone 49 0 6190 9907 0 Fax 49 0 6190 9907 50 E Mail info hilscher com Support Phone 49 0 6190 9907 99 E Mail de support hilscher com Subsidiaries China Hilscher Systemautomation Shanghai Co Ltd 200010 Shanghai Phone 86 0 21 6355 5161 E Mail info hilscher cn Support Phone 86 0 21 6355 5161 E Mail cn support hilscher com France Hilscher France S a r l 69500 Bron Phone 33 0 4 72 37 98 40 E Mail info hilscher fr Support Phone 33 0 4 72 37 98 40 E Mail fr support hilscher com India Hilscher India Pvt Ltd Pune Delhi Mumbai Phone 91 8888 750 777 E Mail info hilscher in Italy Hilscher Italia S r l 20090 Vimodrone MI Phone 39 02 25007068 E Mail i
78. t IP Adapter Slave Protocol netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 56 86 9 2 3 Open Modbus TCP Parameter Description 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 Table 54 Technical Data Open Modbus TCP Protocol netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 57 86 9 2 4 PROFINET IO RT Controller Link H Manual netX Products Modules TechnicalDataProtocols EN PROFINET IO RT Controller V2_5 man 004 PROFI NET IO RT Controller Technical Data Protocol netX50 netTAP50_en d OC Maximum number of PROFINET IO Devices 1 to one IO Device only Maximum number of cyclic input data 1024 bytes per device IOCR data length Maximum number of cyclic output data 1024 bytes per device IOCR data length 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
79. t 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 40 86 8 LEDs 8 1 System LEDs LED Color State Meaning SYS Duo LED yellow green O all green On Operating System running further diagnostic see APL LED d yel On This state may occur only briefly low If this LED stays permanently yellow then a hardware failure is possible EI Flashing Error state Boot loader active yellow yellow green green Eb coor swe meann APL Duo LED red green On The communication on X2 and X3 is in cyclic data exchange and the gateway function is executed Blinking with netTAP is initialized but the communication 2 s Off on X2 is not in cyclic data exchange 0 5 s on Blinking with netTAP is initialized but the communication 2 s off on X3
80. t 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 white orange GND white blue TxD white brown RxD brown An Ethernet connection is neces sary for configuration and diagnos tic RJ45 Socket D Sub 9 Ethernet RS232 X3 netTAP50 You can use a direct cable con X3 netTAP50 RJ45 Plug nection to the RS 232 remote RJ45 Plug device as shown on the right An Ethernet cable is required for 12345678 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 RJ45 Plug Ethernet l Diagnostics PC Remote device netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Device Drawings and Connections 30 86 RS 422 and Ethernet on RJ45 Pin Assignment Ethernet Pin Signal Description __ 12345678 6 Ethernet RX Receive data negative RS422 TxD Transmit data negative RJ45 socket fe 8 RS422 TxD Transmit data positive male PEO Metal housing on PE I Bob Smith Termination Table 28 RJ45 Ethernet RS 422 Pin Assignment ul
81. telegram length 512 bytes Data bits 7 8 bits Stop bits 1 2 bit s 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 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 Maximum number of structure elements of a send 10 telegram Maximum number of structure elements of a receive telegram Structure elements Start character s Device a 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 Table 64 Technical Data ASCII Protocol netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 67 86 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 C
82. tiation Open Modbus TCP allowed allowed 10 MBit s 100 MBit s Full or Half Duplex Auto Negotiation POWELINK forbidden PROFINET IO RT forbidden Only allowed if the switch supports Pri ority Tagging and LLDP 100 MBit s Full Duplex SERCOS lll 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 A NOTICE 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 EtherNet IP or Modbus TCP at 10 MBit s in half duplex mode otherwise failure 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 39 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 71 86 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 addi tional inductance It is not permitted to have T stubs on PROFIBUS high ba
83. ud 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 First device Last device 6 VF S m VP RxD TxD P RxD TxD P RxD TxD N am RxD TxD N 5 DGND DGND 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Wiring Instructions 72 86 The maximum length of a bus segment depends on the baudrate used see the following table 600 500 400 Table 67 PROFIBUS Segment Length in Dependence of the Baud Rate The following table contains the most important electrical dsata concerning PROFIBUS certified cable Capacity lt 30 pF m Table 68 Characteristics of PROFIBUS certified Cable netTAP NT 50 Gateway Devices DOC091202UM13EN
84. ude Elea 51 8 4 2 LED ASC zu n pem SEM MI aaa 51 9 TECHNICAL DATA sesssssessseenen emn In en en nmn nne mnn nnne nre rnni sse re nsa sensa serre nna nis 52 9 1 Technical Data netTAP 50 Gateway u uuussuuanssensnennnnennnnnnnnennnnnnnnennnenenne nennen 52 9 2 Technical Data of Real Time Ethernet Communication Protocols 54 9 2 1 EtherNet IP Scanner Master Link u00222220022000000000nn0 nennen nennen nennen 54 9 2 2 EtherNet IP Adapter Slave cccccssssccccseseeccesseecseseeecsegseecseseeessaseeessneeeneaes 55 9 2 3 Open MOGDUS TC R are ils asien 56 9 2 4 PROFINET IO RT Controllet EInk u i oc d qr ae 57 9 2 5 PISOFINETIOSRTSDOVICG ue a ee ee 58 9 3 Tecnnical Data FleldaDus P TOLIOGCOlS ii use en ui 59 9 3 1 CANopen Master Link 2 20002220002040000000Bnnnnonnnnn nennen nenne nenne nenne nnn 59 9 3 2 ANODE Slave are ie ee 60 netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Introduction 9 3 3 CGALINK SIaVOBs nitent enis ds Goss uti eric e ut 9 3 4 DeviceNet Master Link eene 9 3 5 DeviceNet Slave e iet cmd de ee ceeded ee 9 3 6 PROFIBUS DP Master Link 9 3 7 PROFIBUS DP Slave nes 2 2 9 4 Technical Data serial Protocols 9 4 1 Bolus eism De I d a MAI DR
85. uo LED red green ea RUN cyclic communication pw configuration at PROFIBUS DPside Qe Q o d cy STOP no communication connection error clic Flashing Not configured acyclic Table 40 LEDs PROFIBUS DP Slave netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 47 86 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 tp Color State Meg O O CAN Duo LED red green 3 RESET The device is executing a reset Single flash STOPPED The device is in STOPPED state all green Blinking PREOPERATIONAL The device is in the PREOPERATIONAL state 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 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 The indicator is constantly on The indicator is constantly off BEEN The indicator turns on and off with a frequency of 10 Hz on for 50 ms followed b
86. ut data 244 bytes netTAP NT 50 Gateway Devices DOC091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 65 86 9 3 7 PROFIBUS DP Slave Parameter Description Maximum number of cyclic input data 244 bytes Maximum number of cyclic output data 244 bytes 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 suppor ted SSCY1S Slave to slave communication state machine not implemented Data exchange broadcast not implemented I amp MO with fixed settings only 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 version 1 351 or higher and can be used with firmware version 1 1 or higher netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 Technical Data 66 86 9 4 Technical Data serial Protocols 9 4 1 ASCII Parameter Description and Value Range Maximum
87. y 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 netTAP NT 50 Gateway Devices DOCO091202UM13EN Revision 13 English 2015 01 Released Public Hilscher 2010 2015 LEDs 48 86 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 LED Color State Meng CAN Duo LED red green Que On OPERATIONAL The aevo sin tne OPERATIONAL sae Flickering Auto Baud Rate Detection active The Device is in the Auto Baud Rate 99 Ee Detection mode red green Q o 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 Q o Double flash Error Control Event A guard event NMT Slave or NMT master or a heartbeat event Heartbeat consumer has occurred Bus Off The CAN controller is bus off Table 43 LEDs CANopen Slave LED State Definition for CANopen Slave for the CAN LED Indicator stat

netTAP NT 50 - Gateway Devices (User manual)

Contents

Download Pdf Manuals

Related Search

Related Contents