Home

netTAP NT 50

1. RS232 GND Data reference potential ground of power supply 6 Ethernet RX Receive data negative RS232 TxD Transmit data RJ45 socket fe RS232 RxD male 8 RS232 RxD Receive data data PE MetalcaseonPE Pf Bob Smith Termination Table 21 RJ45 Ethernet RS232 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 Ethernet signal lines Make sure that there is no interrup tion of the shield connection when preparing the cable Make sure that the TxD signal of one device is connected to the RxD signal of the other device for a RS 232 connection white orange GMD 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 12345678 An Ethernet cable is required for 12343678 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Publi
2. Table 32 LEDs PROFIBUS DP Master 1 Communication LED 8 3 2 LED PROFIBUS DP Slave The subsequent table describes the meaning of the LEDs for the fieldbus when the firmware of the PROFIBUS DP Slave protocol is loaded to the device Ub coor swe mean O netTAP NT 50 current Hardware Revision COM Duo LED red green all On RUN cyclic communication green wd Flashing cy STOP no communication connection error red clic wi Flashing not configured red acyclic Table 33 LEDs PROFIBUS DP Slave 1 Communication LED netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 46 85 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 Up Guo State man oS CAN Duo LED red green Jof The device is executing a reset wi Single flash STOPPED The Device is in STOPPED state green wd Blinking PREOPERATIONAL The Device is in the PREOPERA green TIONAL state On OPERATIONAL The Device is in the OPERATIONAL state green w Single flash Warning Limit reached At least one of the error counters red of the CAN controller has reached or exceeded the warning level too many error frames Double flash Error Control Event A guard event NMT Slave or NMT 9 master or a heartbeat event Heartbeat c
3. 1000 V connectomoribe D Sub male connector DeviceNet optisch Cx2 2 1 MQ 15 nF 1000 V 1 MQ 15 nF 1000 V Combicon Pin 3 directly via the metal Profibus DP inductive Cx2 2 1 MQ 2 2 nF 1000 V connectiomof the D Sub female connector Ethernet inductive cx3 6 750 1nF 2000v Directly via the metal X3 EPUM of RJ 45 so ckets Table 24 Coupling NT 50 xx EN Devices netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 33 85 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 X11 O Figure 5 Galvanic Isolation of NT 50 xx RS Devices pd galv Iso i Coupling against PE Functional earthing to onnec Protocol lation Coupling potential PE tion ur O Cf 10 nF 500 V no Lf 47 uH no cx1 D 4 10 nF 500V CC Link Cx2 2 3 3 nF 1000 V directly CANopen optisch Cx2 2 1 MO 15 nF 1000 V directly via the metal connection of the D Sub male connector DeviceNet optisch 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 3 Ethernet indu
4. Open Modbus TCP EtherNet IP Adapter Slave PROFINET IO Device PROFINET IO Controller 1 Open Modbus TCP EtherNet IP Scanner Master 1 NSMBREIL NXF N5DPSASC NXF N5DPSMBR NXF N5ASCEIS NXF N5ASCEIL NXF N5ASCPNS NXF N5ASCPNL NXF N5ASCOMB NXF N5MBREIS NXF NSMBRPNS NXF NSMBRPNL NXF NSMBROMB NXF Table 11 List of Protocol Conversion and NT 50 Device Type netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Description and Requirements 19 85 3 3 System Requirements A NOTICE A The netTAP NT 50 device must be mounted on a DIN rail according to DIN EN 60715 A suitable power supply is required The voltage to be applied must be in the allowed range 24 V 6 V DC The power supply must be able to deliver at least a current of 100 mA at 24 V Power supply is possible via pins 1 GND and 2 24V of the netTAP NT 50 power supply connector located on the upper side of the device Device Destruction The voltage must not exceed 30 V significantly otherwise the device may be destroyed or damaged 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 preconditi
5. oe hilscher COMPETENCE IN COMMUNICATION User Manual netTAP NT 50 Gateway Devices Hilscher Gesellschaft fur Systemautomation mbH www hilscher com DOC091202UM02EN Revision 2 English 2010 09 Released Public Introduction 2 85 Table of Contents 1 INTRODUCTION ETE 5 1 1 ADOULING USEFIManUal eu 2 25 essen 5 1 1 1 Ne Ric D UU IN 5 1 2 o A E E E T ATE 6 1 2 1 COPIE eek leiten 6 1 2 2 IMDBOFanNE NOIES io 6 1 2 3 zeiten mro ae Bei 7 1 2 4 WV IRAN erging 7 1 2 5 EXPOM RE QUIALIONS aaa ee 8 1 2 6 Registered lradeMarks curia 8 1 3 Conventions In TIS Mahal nee a ae 9 1 4 Reference to Hardware Software and Firmware eese 10 1 3 Contents orthe Product DVD a nina 11 1 5 1 Directory Structure of the DVD c oocccncnccccnccocnococnoconnonanconanononnnnnnonannonannonanonos 11 1 5 2 Device Description Als nat Em 11 1 5 3 Documentation for net AP NT 50 u2zuu220sssennnnnnennnnnnennnnnnennn nennen nennen 12 2 SAFE I see E 13 2 1 General N Ole a TEER E AE T E SE A TE EE SA EEEE E EE ee 13 2 2 Mended Use circle 13 2 3 Personnel QUANG N acid i 13 2 4 Commitment to read and understand the Manual eene 14 2 5 ReteroncesS Sale nannten er Aarau 14 2 6 Labeling of Safety Instructions sellers 19 3 DESCRIPTION AND REQUIREMEN TS 5 tere u 16 3 1 DES CHIP OD MT E I UEM E 16 3 2 Device Versions and Pr
6. 6 MBits s 12 MBit s Auto baudrate detection is not supported Data transport layer PROFIBUS FDL Limitations DP V1 services class 1 and 2 are not supported DP V2 services are not implemented Table 54 Technical Data PROFIBUS DP Master Link Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 64 85 9 3 7 PROFIBUS DP Slave 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 are not supported SSCY1S Slave to slave communication state machine not im plemented Data exchange broadcast not implemented I MO with fixed settings only Table 55 Technical Data PROFIBUS DP Slave Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 65 85 9 4 Technische Daten serielle Protokolle 9 4 1 ASCII 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
7. Decommissioning 6 1 Load Firmware and Configuration The device delivered without loaded firmware and configuration It is necessary that a firmware and configuration is loaded into the device for commissioning The device can be configured before or after mounting via the RJ45 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 Ethernet it is necessary to assign an IP address to the net AP NT 50 device This is done with the Ethernet Device Setup Software which is in stalled together with SYCON net software Information about this is in the manual netGateway on the product DVD in the directory Documentation 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 6 1 1 Download Configuration Files from the PC 1 The configuration can be created and saved offline with or without real device on a standard PC with the software SYCON net The configura tion can be downloaded into the device in two steps afterwards 2 The selected firmware and configuration has to be transferred in two steps via an Ethernet connection into the device The configuration is stored in the device in a non volatile flash memory Once set the data will be available after each power cycle These steps are described in t
8. Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 49 85 The device has a valid configuration for Modbus RTU and is ready for Modbus communication respectively sends receives Modbus RTU telegrams Communication error The device works as Modbus RTU Master the slave device answered with a error Modbus Excep tion e g functioncode 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 function code the Modbus RTU Master device has accessed an invalid register addresses 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 Mod bus telegram sequence LEDs 90 85 8 4 2 LED ASCII The subsequent table describes the meaning of the LEDs for the ASCII protocol COM Duo LED red green with al Flashing cyclic The device sends receive data protokocol green with 1 Hz at X2 gt On The device is ready for serial communication green 4 with d Flashing cyclic The device is configured and is in the state stop protocol at red with 5 Hz Flashing cyclic The device is not configured re
9. Max Baud rate Max length of a single line branch line Table 71 RS422 Conductor Length and Transmission Rates netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 10 1 9 RS485 IN NOTICE A 80 85 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 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 RS485 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 and data trans mission rates of up to 1 MBit s Concerning this topic see Table 73 RS 485 Cable Lengths
10. RxD soo Figure 15 RS 232 Null Modem Cable Connection The pin assignment are for a DSub connector The signals RTS and CTS are not present on all devices Conductor length and transmission rates In the ElA 232 norm a maximum cable ca pacitance of 2500 pF is allowed for a RS232 Cables of such capacitance may have the 97 600 following lengths depending on the baud rate Higher length can be achieved with cables of extraordinarily low capaci tance netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 10 1 3 RS 422 A NOTICE A 78 85 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 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 maximal
11. netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 30 85 RS485 and Ethernet on RJ45 pin assignment Ethernet pm Siona Bedeutumg 12345678 6 Ethernet RX Receive data negative Hoo AI Ru45 socket fe 9 notused 0000 De PE metal housing on PE _ 7 Bob Smith Abschluss Table 23 RJ45 Ethernet RS422 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 for a RS 485 connection Ethernet white blue white orange blue RxD TxD 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 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 interf
12. 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 Suwon 443 810 Phone 82 31 204 6190 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
13. 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table 48 Table 49 Table 50 Table 51 Table 52 Table 53 Table 54 Table 55 Network on port X3 Secondary Network List of Protocol Conversion and NT 50 Device Type Power supply line 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 RS232 pin assignment RJ45 Ethernet RS422 pin assignment RJ45 Ethernet RS422 pin assignment Coupling NT 50 xx EN Devices Coupling NT 50 xx RS Devices Coupling NT 50 RS EN Devices NT 50 Troubleshooting LEDs EtherNet IP Scanner Master LEDs EtherNet IP Adapter Slave LEDs Open Modbus TCP LEDs PROFINET IO RT Device LEDs PROFIBUS DP Master 1 Communication LED LEDs PROFIBUS DP Slave 1 Communication LED LEDs CANopen Master LED State Definition for CANopen Master for the CAN LED LEDs CANopen Slave LED State Definition for CANopen Slave for the CAN LED LEDs DeviceNet Master LEDs DeviceNet Slave LED Modbus RTU Protocol LED ASCII Protocol Technical Data NT 50 Part 1 Technical Data NT 50 Part 2 Technical Data EtherNet IP Scanner Master Link P
14. D Sub Connectors eese nennen nnne nennen 68 10 1 2 A PE 69 10 1 3 PRO PIB WS M H 70 10 1 4 CANO Dead 72 10 1 5 IO VIC i e e ee nenne 73 10 1 6 G0 A pP E 75 10 1 7 A 77 10 1 8 PRO AD ee ee ee en ee ee ee 78 10 1 9 ROIO RE NENNE NER EEE SI NENNEN do M en eee ree 80 TE USES 82 11 1 LISLOFFIGgUrES zn ee ee 82 11 2 LISEOFTADIOS ee ee ee 83 QU CONTACTS ILLUM 85 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 5 85 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 List of Revisions Index Date Chapter Revisions O 1 2010 05 25 al Created o O 2010 08 19 Device name corrected to NT 50 RS EN RJ45 graphic LEDs chanced Text for future use removed COM LED position NT 50 RS EN COM LED position NT 50 RS EN LED description for EtherNet IP Adapter Slave added Wiring Instructions for RS 422 Bus Requirements changed Wiring Instructions for RS 485 Bus Requirements changed Table 1 List of Revisions netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 6 85 1 2 Legal Notes 1 2 1 Copyright 2008 2010 Hilscher Gesellschaft f r Systemautoma
15. Receive watchdog time Send cycle time Character delay time Number of send buffers Number of receive buffers Number of transmission retries Maximum number of structure elements of a send telegram Maximum number of structure elements of a receive telegram Structure elements Start character s Device address Object index or start address Command identifier Data area with length information Data area with termination character s End character s Checksum Character s without meaning fix length Checksum methods Table 56 Technical Data ASCII Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 66 85 9 4 2 Modbus RTU Master Slave Maximum number of input data 2880 Registers Maximum number of output data 2880 Registers Acyclic communication Read Write Register Maximum 125 Registers per Read Telegram FC 3 4 Maximum 123 Registers per Write Telegram FC 16 Maximum 118 Registers per Write Telegram FC 23 Maximum 118 Registers per Read Telegram FC 23 Read Write Coil Maximum 2000 Coils per Read Telegram FC 1 2 Maximum 1968 Coils per Write Telegram FC 15 Function Codes Modbus Master 1 2 3 4 5 6 15 16 Function Codes Modbus Slave 1 2 3 4 5 6 7 8 15 16 23 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 57 Technic
16. an IP Address for the netTAP NT 50 Operating Instruc SYCON net SYCONnet_netFrame_en pdf tion Manual Frame Application Operating Instruc netDevice and netProject SYCONnet_netDevice_en pdf tion Manual FDT Container Operating Instruc netGateway DTM for netTAP netBRICK and netGateway_DTM_en pdf tion Manual netLINK Configuration of Gateway and Proxy Devices 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 Operating Instruc DTM for EtherNet IP Scanner devices EtherNetIP_Scanner_DTM_en pdf tion Manual Operating Instruc Generic DTM for EtherNet IP Adapter devices EtherNetlP_GenericAdapter_DTM_en pdf tion Manual Operating Instruc DTM for PROFINET IO Controller devices PROFINET IO Controller DTM en pdf tion Manual Operating Instruc Generic DTM for PROFINET IO Device devi PROFINET IO GenericDevice DTM en pdf tion Manual ces Operating Instruc DTM for CANopen Master devices CANopen Master netX DTM en pdf tion Manual Operating Instruc Generic DTM for CANopen Slave devices CANopen Generic Slave DTM en pdf tion Manual Operating Instruc DTM for DeviceNet Master devices DeviceNet Master netX DTM en pdf tion Manual Operating Instruc Generic DTM for DeviceNet Slave devices DeviceNet Generic Slave DTM en pdf tion Manual Operating Instruc DTM fo
17. and all T stubs does not exceed the maximum length listed in the following table netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 74 85 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 Linin lt 500 m at 125 kBaud Linick 2 5 X Lthin lt 250 m at 250 kBaud Linick Linn lt 100 m at 500 kBaud Table 66 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 75 85 10 1 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 O respectively The following illustration displays the basic network structure First device Last device DA DA 100 al LA e 100 110 130 DB G DG E SLD m La A sAllios H DB anre Termin
18. counters of red the CAN controller has reached or exceeded the warning level too many error frames Double Error Control Event A guard event NMT Slave or NMT 9 flash master or a heartbeat event Heartbeat consumer has oc curred e Bus Off The CAN controller is bus off red Table 36 LEDs CANopen Slave LED State Definition for CANopen Slave for the CAN LED Indicator state Definition The indicator is constantly on The indicator is constantly off 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 37 LED State Definition for CANopen Slave for the CAN LED netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 48 85 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 tb Color swe Men SSS MNS Duo LED red green 3 M On Device is online and has one or more connections in the 9 established state Flashing Device is online and has no connection in the establis
19. module status indicator shall be steady off Duo LED red green Flashing red green 3 Q NS Number in Connected If the device has at least one established con nection even to the Message Router the network status indicator shall be steady green 2 the device green drawing No connections If the device has no established connec tions but has obtained an IP address the network status indicator shall be flashing green Flashing green Duplicate IP If the device has detected that its IP address is already in use the network status indicator shall be steady red Connection timeout If one or more of the connections in which this device is the target has timed out the network status indicator shall be flashing red This shall be left only if all timed out connections are reestablished or if the device is reset Flashing Self test While the device is performing its power up testing the network status indicator shall be flashing green red Flashing D d Bd 2 red green Off Not powered no IP address If the device does not have an IP address or is powered off the network status indicator shall be steady off LINK RJ4 LED green Z ET ud On A connection to the Ethernet exists in the de green vice draw o Les The device has no connection to the Ethernet ACT RJ45 LED yellow Numberin Flashing The device sends recei
20. supported ring topology Table 44 Technical Data EtherNet IP Scanner Master Link Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 54 85 9 2 2 EtherNet IP Adapter Slave 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 45 Technical Data EtherNet IP Adapter Slave Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 55 85 9 2 3 Open Modbus TCP Maximum number of input data 2880 Registers Maximum number of output data 2880 Registers Acyclic communication Read Write Register Max 125 Registers per Read Telegram FC 3 4 23 Max 121 Registers per Write Telegram FC 23 Max 123 Registers per Write Telegram FC 16 Read Write Coil Max 2000 Coils per Read Telegram FC 1 2 Max 1968 Coils per Write Telegram FC 15 Modbus Function Codes 1 2 3 4 5 6 7 1 16 23 Function code 23 in server mode only Table 46 Technical Data Open Modbus TCP Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 E
21. 0 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 43 85 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 LED Color State 3 Meaing RUN Duo LED red green Number Off Not Ready in the OMB task is not ready device l l drawing Flashing cyclic Ready not configured yet O green with 1Hz OMB task is ready and not configured yet Flashing cyclic Waiting for Communication green with 5Hz OMB task is configured On Connected green OMB task has communication at least one TCP connec tion is established ERR Duo LED red green Number Off No communication error in the device drawing Flashing cyclic with 2Hz On Off Ratio LINK RJ Number in the device drawing The device has no connection to the Ethernet ACT RJ LED yellow Number 3 in the device drawing O Flashing The device sends receives Ethernet frames yellow Table 30 LEDs Open Modbus TCP netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 44 85 8 2 4 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
22. 1 9 1 Technical Data net AP 50 Gateway ccocccoccccccoccccnconoconnonoconnnnonanonnocannnnocanonnonanenes 51 9 2 Technical Data of Real Time Ethernet Communication Protocols o9 9 2 1 EtherNet IP Scanner Master Link eese o3 9 2 2 EtherNet IP Adapter Slave les ana ve da o4 9 2 3 Open Modbus TCP MTM LE 55 9 2 4 PROFINET IO RT Controller Link ooccoocccocccocncccccoccnocccocncconocnononononanononos 56 9 2 5 PISOFINET IO ITZDOVIGG cuidara aa 57 9 3 Technische Daten Feldbus Protokolle coccoccocccnoccocconconccnoccccconconcnncanos 58 9 3 1 CANOpen Master LINK qc Tt 58 9 3 2 CANOPEN Slave a a O DO 59 9 3 3 A T UU 60 9 3 4 DeviceNet Master Link esee sti ea redo sense 61 9 3 5 DEVICENELSIAVE D TTL 62 9 3 6 PROFIBUS DP Master EINK isse stessa ste een 63 9 3 7 PIEISOFIBUSSDPISIAVBU nsu diti tee odes ute a EN paa secs drav gres dfoe ota eo oet dera Et Dot 64 9 4 Technische Daten serielle Protokolle oococconconconccnocconionionccnonnonconon 65 9 4 1 ASCII arias 65 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 4 85 9 4 2 Modbus RTU Master Slave ooocccoccccoccnccccccocnconcncnncnonacnnnononnnnnoncncnncnonannnnnnnnos 66 10 APPENDIX C 67 10 1 WiN TUC UON Sr utres no eset iode aaa ee 67 10 1 1 Assembly of
23. 1 Connector for Power Supply Front view 26 mm X1 with D Sub male connector Bottom View Js with RJ45 Socket NT 50 CO EN NT 50 CO RS NT 50 RS EN X2 and X3 Communication interfaces 21 85 with D Sub female connector E with RJ45 Socket NT 50 DP EN NT 50 DP RS Dimensions of the power supply plug X1 in mm netTAP NT 50 Gateway Devices DOC091202UMO2EN Revision 2 English 2010 09 Released Public O Hilscher 2010 Device Drawings and Connections 22 85 4 2 LEDs and Control Elements Meaning of the elements Connector X1 for power supply SYS LED APL LED 3 COM LED 4 LED depends on protocol at X2 G LED depends on protocol at X2 6 Rotary address switch factor 10 7 Rotary address switch factor 1 LED green LINK at X3 9 LED yellow ACT activity at X3 Figure 3 LEDs and Control Elements The rotary address switch and O are not supported from any firmware at this time netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 23 85 4 3 Connections 4 3 1 4 3 2 4 3 2 1 4 3 2 2 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 tween 18 V me 30 V DC The plug is included in delivery Power su line pin assignment Power supply Desc
24. Device Damage Make sure that the NT 50 device and the remote device via RS 232 RS 422 respectively RS 485 have the same potential Otherwise a compensating current may cause device damage because the serial in terface of the NT 50 device has no galvanic isolation to its power sup ply Device Damage Make sure that only a 4 wire Ethernet cable is used with pin 1 2 3 and 6 if no Y cable for separation of the Ethernet and serial interface is used On pin 4 5 7 and 8 on the NT 50 device are the signals for the serial interface If you transfer these signal via an Ethernet cable to the connected device e g to a switch this may cause a device damage of the used devices 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 lf 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 NOTICE netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 28 85 RS232 and Ethernet on RJ45 pin assignment meme Pin Signal Description 12345678 4 RS232 3 3 V Data potential High not usable as power i supply Ri appr 300 Q
25. Released Public Hilscher 2010 Appendix 72 85 10 1 4 CANopen Please use only CAN certified cable with the following characteristics Parameter Value Capacity lt 50 pF m Table 61 Characteristics of CAN certified Cable First device Last device CAN Hm CAN_H 120 i CAN L mmt CAN L AN GND ma CAN GND Figure 12 Termination CAN Network At the ends of the network there must be two resistors of 120 Q 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 CANopen cables are listed in the following table Baud rate Max distance Loop Resistance Wire Gauge in kBit s s 1000 m lt 26 Q km 0 75 0 80 mm2 4000 m lt 26 Q km 0 75 0 80 mm2 1000 m 26 Q km 0 75 0 80 mm2 Table 62 CAN Segment Length in dependence of the Baud rate or corresponding Loop Re sistance and Wire Gauge netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 73 85 10 1 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 should be used The maximum length of the DeviceNet cable depend
26. XF CANopen Slave ASCII N5COSASC NXF Modbus RTU Master Slave N5COSMBR NXF DeviceNet Master for one slave EtherNet IP Adapter Slave PROFINET IO Device Open Modbus TCP EtherNet IP Adapter Slave N5CCSPNS NXF N5CCSPNL NXF N5CCSOMB NXF N5COLEIS NXF N5COLPNS NXF N5COLOMB NXF N5COSEIS NXF N5COSPNS NXF N5COSPNL NXF N5COSOMB NXF NSDNLEIS NXF NSDNLPNS NXF N5DNLOMB NXF NSDNSEIS NXF EtherNet IP Scanner Master 1 NSDNSEIL NXF PROFINET IO Device PROFINET IO Controller 1 Open Modbus TCP N5DNSPNS NXF N5DNSPNL NXF N5DNSOMB NXF NT 50 DN RS DeviceNet Master for one slave ASCII N5DNLASC NXF Modbus RTU Master Slave N5DNLMBR NXF NT 50 DP EN slave PROFIBUS DP Slave EtherNet IP Adapter Slave PROFINET IO Device Open Modbus TCP EtherNet IP Adapter Slave DeviceNet Slave ASCII N5DNSASC NXF Modbus RTU Master Slave N5DNSMBR NXF PROFIBUS DP Master for one N5DPLEIS NXF NSDPLPNS NXF N5DPLOMB NXF N5DPSEIS NXF EtherNet IP Scanner Master 1 NSDPSEIL NXF PROFINET IO Device PROFINET IO Controller 1 Open Modbus TCP N5DPSPNS NXF N5DPSPNL NXF N5DPSOMB NXF NT 50 DP RS PROFIBUS DP Master for one ASCII N5DPLASC NXF slave Modbus RTU Master Slave N5DPLMBR NXF NT 50 RS EN PROFIBUS DP Slave ASCII Modbus RTU Master Slave ASCII Modbus RTU Master Slave EtherNet IP Adapter Slave Ethernet IP Scanner Master 1 PROFINET IO Device PROFINET IO Controller 1
27. ace is used with the cable shown at the right RJ45 Plug Ethernet RS485 Diagnostics PC Remote device netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 31 85 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 GB Note The PE connection potential equalization of the device is done via the DIN rail netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 32 85 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 18 30Vdc H mrm m OE Figure 4 Galvanic Isolation of NT 50 xx EN Devices Pla galv Isola l Coupling against PE Functional earthing to Sabes Protocol tion Coupling potential PE HE Cf 10 nF 500 V ng Lf 47 uH cx CO 4 10 nF 500 V CC Link Cx2 2 3 3 nF 1000 V directly to Combicon Pin 4 directly via the metal CANopen optisch Cx2 2 1 MO 15 nF
28. al Data Modbus RTU Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 67 85 10 Appendix 10 1 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 68 85 10 1 1 Assembly of D Sub Connectors The design of the bus cabling is an essential factor for the proper function of communication Therefore special attention should be paid to the cable connections with its connectors Particularly ensure good shield connec tion The shield must be connected as follows 1 2 3 4 r 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 pl
29. ating 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 NL 51N DPL device after return of the power supply and subsequently the firmware is started This process can take several seconds appr 4 seconds depending on the size of the configuration data 6 3 Put the Device out of Operation In order to avoid personal and material damage do not remove this device from a production line without having ensured a secure operation of the production line during and after the removal of the device NOTICE A NOTICE In order to avoid personal and material damage do not remove this device from a production line without having ensured a secure operation of the production line during and after the removal of the device 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 from the DIN rail netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Troubleshooting 38 85 7 Troubleshooting Two methods for troubleshooting exist e The visual analysis of the LED conditions of the device e The analysis via the Ethernet port along with
30. ation resistor depends on the used cable type see CC Link Cable Wiring Manual Figure 14 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 76 85 Only trunk line without branches Baud rate max Length ca max Length ca max length high ble V1 00 ble V1 10 and flexible V1 10 cable V1 00 with Type 50 high capacity 156 kbps 1200 m 1200 m Table 67 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 line max length of all branch 200 m lines Table 68 Maximum length Further devices can be connected via T branches to the bus cable only at the baud rates 156 kbps and 625 kbps The maximum length of all T stubs is l
31. bus Protokolle 9 3 1 CANopen Master Link 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 49 Technical Data CANopen Master Link Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 59 85 9 3 2 CANopen Slave Exchange of process data Via PDO transfer synchronized remotely requested and event driven change of date Functions Node guarding life guarding heartbeat PDO mapping NMT Slave SYNC protocol consumer Baud rates 10 kBits s 20 kBits s 50 kBits s 100 kBits s 125 kBits s 250 kBits s 500 kBits s 800 kBits s 1 MBits s Data transport layer CAN Frames CAN Frame type 11 Bit Limitations SDO Upload Download for user data transfer not supported Emergency message producer not supported Table 50 Technical Data CANopen Slave Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 60 85 9 3 3 CC Link Slave Firmware works a
32. c Hilscher 2010 Device Drawings and Connections 29 85 RS422 and Ethernet on RJ45 pin assignment Ethernet Pin Signal Description 12345678 Receive data positive ui 6 Ethernet RX Receive data negative Transmit data negative male PE metalhousingonPE _ Bob Smith Termination Table 22 RJ45 Ethernet RS422 pin assignment X3 netTAP50 The figure on the right shows a Y RJ45 Plug cable adapter for the separation of 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 tion wihte brown RxD white blue TxD RJ45 Socket Ethernet X3 netTAP50 You can use a direct cable con X3 netTAP50 RJ45 Plug nection to the RS 422 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 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 _ J __ Shield _____Y RJ45 Plug Ethernet RS422 Diagnostics PC Remote device
33. ccording to CC Link Version 2 0 Input data remote device station 112 bytes RY and 256 bytes RWw Output data remote device station 112 bytes RX and 256 bytes RWr Extension cycles 1 2 4 8 Baud rates 156 kBit s 625 kBit s 2500 kBit s 5 MBit s 10 MBit s Limitation Intelligent Device Station not supported Firmware works according to CC Link Version 1 11 Station Types Remote I O station Remote device station up to 4 occupied stations 48 bytes 48 bytes Input data remote I O station 4 bytes RY Output data remote l O station 4 bytes RX 4 bytes RY and 8 bytes RWw per occupied station Maximum input data Maximum output data Input data remote device station Output data remote device station 4 bytes RX Baud rates 156 kBit s 625 kBit s 2500 kBit s 5 MBit s 10 MBit s e and 8 bytes RWr per occupied station Input data remote device station 4 bytes RY and 8 bytes RWw per occupied station Firmware Reference to firmware stack version Table 51 Technical Data CC Link Slave Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 61 85 9 3 4 DeviceNet Master Link 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 Co
34. ce Type NT 50 xx EN e Important When using Ethernet TCP UDP IP EtherNet IP or Modbus TCP at 10 MBit s 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 Refer to section Failure in 10 MBit s Half Duplex Mode and Workaround on page 39 Ethernet on RJ45 pin assignment Ethernet Pin Signal Descripti n Transmit data positive 12345678 Transmit data negative Receive data positive Connected and terminated to PE via RC Receive data negative Connected and terminated to PE via RC RJ45 socket fe combination male Bob Smith Termination Table 20 Ethernet RJ45 pin assignment netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 27 85 4 3 3 2 X3 for Device Type NT 50 xx RS For this device type the Ethernet interface is required for the configuration of the device It may be necessary for diagnostic purpose to use a Y cable which separates the serial interface RS and the Ethernet interface Device Damage Make sure that the NT 50 device and the remote device via RS 232 NOTICE 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 AN
35. ctive Cx3 O 2 750 1nF 2000 V connectomermddb X3 Teil 4 nn diag sockets O Directly via the metal connection of RJ 45 X3 Teil sockets Table 25 Coupling NT 50 xx RS Devices netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 34 85 4 4 3 Galvanic Isolation of NT 50 RS EN The device type NT 50 RS EN has three galvanically isolated areas The coupling to PE is shown in the following figure and in the following table X2 VIN 18 30Vde Hf ae E gt RJ45 O E Figure 6 Galvanic Isolation of NT 50 RS EN Devices galv Isola i Coupling against PE Functional earthing to Protocol tion Coupling potential PE mE HF D cre 10 nF 500 V Directly via the metal Lf 47 uH ca OD 4 10 nF 500 V Ethernet inductive Cx3 6 75Q 10 nF 2000 V connection of RJ 45 sockets Lf 47 uH connection of the D Sub female connector c1 D 4 10 nF 500 V A HF O Cf 10 nF directly via the metal no Table 26 Coupling NT 50 RS EN Devices netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 NT 50 Mounting and Dismounting 39 85 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 de
36. ctly named Instructions to a property damage message do not con tain a warning triangle Symbol Symbol Sort of Warning or Principle USA NX Warning of Personal Injury Warning of danger by electrical current Warning of damages by electrostatic discharge Principle Mandatory read Manual Table 7 Safety Symbols and Sort of Warning or Principle Signal Word Meaning Signal Word USA Meaning USA Indicates a direct hazard with high A DANGER Indicates a Hazardous risk which will have as conse a DANGER Situation Which if not quence death or grievous bodily Avoided will Result in harm if it isn t avoided Death or Serious Injury WARNING Indicates a possible hazard with Indicates a Hazardous medium risk which will have as consequence death or grievous bodily harm if it isn t avoided Situation Which if not Avoided could Result in Death or Serious Injury CAUTION Indicates a minor hazard with Indicates a Hazardous medium risk which could have as Situation Which if not consequence simple battery if it Avoided may Result in isn t avoided Minor or Moderate Injury NOTICE Indicates a Property Damage NOTICE Indicates a Property Message Damage Message Indicates an important note in the Note Indicates an Important manual Note in the Manual Table 8 Signal Words In this document the safety instructions and property damage messages are designed according both to the international used safety conventions a
37. cuments is limited to cases of in tent or grossly negligent violation of significant contractual obligations In demnity claims for the violation of significant 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 2 4 Warranty Although the hardware and software was developed with utmost care and tested intensively Hilscher Gesellschaft fur 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 ownershi
38. d with 1 Hz C ot During initialisation or missing power supply Table 41 LED ASCII Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 51 85 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 z6VDC 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 con nector Table 42 Technical Data NT 50 Part 1 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 92 85 Ethernet Interface Transmission rate 100 MBit s for the device types 10 MBit s depending on loaded NT 50 DP EN firmware NT 50 CO EN NT 50 DN EN NT 50 RS EN 100 BASE TX isolated 10 BASE TX depending on loaded firmware isolated Half duplex Full duplex supported at 100 MBit s Auto Negotiation supported depending on loaded firmware Transmission rate 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 MBit s 6 MBit s 12 MBit s RS 485 optically isolated SubD female 9 pin CANopen I
39. de 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 Limitations Acyclic communication Explicit Messaging for user data transfer not supported Table 52 Technical Data DeviceNet Master Link Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 62 85 9 3 5 DeviceNet Slave Maximum number of cyclic input data 255 bytes Maximum number of cyclic output data 255 bytes Connections Poll Change of state 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 Limitations Acyclic communication Explicit Messaging for user data transfer not supported Table 53 Technical Data DeviceNet Slave Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 63 85 9 3 6 PROFIBUS DP Master Link Parameterization data 7 bytes standard parameters Max 237 bytes application specific parameters Baud rate 9 6 kBits s 19 2 kBits s 31 25 kBits s 45 45 kBits s 93 75 kBits s 187 5 kBits s 500 kBits s 1 5 MBits s 3 MBits s
40. 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Troubleshooting 39 85 7 1 Failure in 10 MBit s Half Duplex Mode and Workaround Affected Hardware Hardware with the communications controller netX 50 netX 100 or netX 500 netX Internal PHYs When can this Failure occur When using standard Ethernet communication with 10 MBit s half duplex mode the PHY gets stuck in case of network collisions Then no further network communication is possible Only device power cycling allows Ethernet communication again This problem can only occur with Ethernet TCP UDP IP EtherNet IP or Modbus TCP protocols when using hubs at 10 MBit s The issue described above is not applicable for protocols which use 100 MBit s or full duplex mode Solution Workaround Do not use 10 MBit s only hubs Use either switches or 10 100 MBit s Dual Speed hubs to make sure the netX Ethernet ports are connected with 100 MBit s or in full duplex mode This erratum is fixed with all com
41. e 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 VP 2 VP RxD TxD P RxD TxD P RxD TxD N ma RxD TxD N 5 DGND DGND Figure 11 PROFIBUS DP Network Up to 32 PROFIBUS devices can be connected to one bus segment If several bus seg ments are linked to each other with repeaters there can be up to 127 devices on the net Work Only PROFIBUS certified cable preferably the cable type A should be used netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 71 85 The maximum length of a bus segment depends on the baudrate used see the following table ms h 500 400 Table 59 PROFIBUS Segment Length in Dependence of the Baud Rate The following table contains the most important electrical dsata concerning PROFIBUS certified cable Capacity 30 pF m Table 60 Characteristics of PROFIBUS certified Cable netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09
42. eleased Public Hilscher 2010 Lists 82 85 11 Lists 11 1 List of Figures Figure 1 Function NT 50 16 Figure 2 Device Drawings 21 Figure 3 LEDs and Control Elements 22 Figure 4 Galvanic Isolation of NT 50 xx EN Devices 32 Figure 5 Galvanic Isolation of NT 50 xx RS Devices 33 Figure 6 Galvanic Isolation of NT 50 RS EN Devices 34 Figure 7 Mounting the netTAP NT 100 device onto the DIN top hat rail 35 Figure 8 Removing the NT 50 device from the DIN Top Hat Rail 35 Figure 9 LEDs 40 Figure 10 D Sub Cable Assemblies 68 Figure 11 PROFIBUS DP Network 70 Figure 12 Termination CAN Network 12 Figure 13 DeviceNet Network 73 Figure 14 CC Link Network 15 Figure 15 RS 232 Null Modem Cable Connection 17 Figure 16 RS422 Wiring 78 Figure 17 RS 485 Wiring 80 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Lists 11 2 List of Tables Table 1 List of Revisions Table 2 Reference to Hardware Table 3 Reference to Software Table 4 Directory Structure of the DVD Table 5 Device Description Files for netT AP NT 50 on the DVD Table 6 Documentation for netT AP NT 50 Table 7 Safety Symbols and Sort of Warning or Principle Table 8 Signal Words Table 9 Network on port X2 Primary Network 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
43. 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 Table 47 Technical Data PROFINET IO RT Controller netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 57 85 9 2 5 PROFINET IO RT Device Maximum subslot address 100 Physical device PDev submodules are allowed at slot 0 subslot addresses 0x8000 0x8064 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 LLDP Link Layer Discovery Protocol SNMP Simple Network Management Protocol LLDP SNMP V1 MIB2 physical device Minimum cycle time 1ms IO Device can be configured with different cycle times Data transport layer Ethernet Il IEEE 802 3 Limitations Acyclic communication not supported RT over UDP not supported IRT not supported Multicast communication not supported Only one device instance is supported DHCP is not supported Reference to firmware stack version V2 1 40 x Table 48 Technical Data PROFINET IO RT Device Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 58 85 9 3 Technische Daten Feld
44. he operating instruction manual netGate Way o0 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 netGateway on the product DVD in the directory Documentation Important Do not interrupt the communication during the download of the firmware into the netT AP NT 50 device lf 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Commissioning Decommissioning 37 85 6 1 2 Potential Differences for Device Types NT 50 xx RS Device Destruction Make sure that for the NT 50 xx RS device and the remote device via NOTICE 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 A 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 compens
45. hed en state Critical connection failure device has detected a network 9 error duplicate MAC ID or sever error in CAN network CAN bus off LAB s Connection timeout mo Communication faulted e pot After start of the device and during duplicate MAC ID check Table 38 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 Device is online and has one or more connections in the Gen established state Flashing Device is online and has no connection in the established en state Critical connection failure device has detected a network 9 error duplicate MAC ID or sever error in CAN network CAN bus off Flashing Connection timeout Flashing Communication faulted 9 l 0f After start of the device and during duplicate MAC ID check Table 39 LEDs DeviceNet Slave netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 8 4 LEDs Seriell 8 4 1 LED Modbus RTU The subsequent table describes the meaning of the LEDs for the Modbus COM 3 with protocol at X2 with protocol at X3 RTU protocol Duo LED red green all On green d On red Off During initialisation or invalid Modbus RTU configuration or missing power supply Table 40 LED Modbus HTU Protocol netTAP NT 50
46. ills for people pro fessionally working with electricity must be present concerning the following topics 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 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Safety 14 85 2 4 Commitment to read and understand the Manual Important Read and understand all instructions in this manual before installation or use of your device to avoid injury 2 5 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 GermanEdition 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Safety 15 85 2 6 Labeling of Safety Instructions The safety instructions are pinpointed particularly The instructions are highlighted with a specific safety symbol a warning triangle and a signal word according to the degree of endangerment Inside the note the danger is exa
47. imited 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 69 Minimum distance between two devices netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 10 1 7 RS 232 A NOTICE A 77 89 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 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 The RS232 interface ElA 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 Signal
48. l netGateway on the product DVD in the directory Documentation netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Description and Requirements 17 85 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 netT AP 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 sla ve can be connected Thus for example for protocols with master function ality the designation PROFIBUS DP Master Link means that one PRO FIBUS DP Slave can be connected 3 2 Device Versions 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 c
49. ly 12 m length of line are possible The following illustration shows wiring for RS422 T Master ER MA l Pull Up ja CONNU IZ a mussen Pull Down 5W GND Pull Up 8M sema m rsen ae Pull Down r AV r 1 I GND pas V LYN NY I jose Steven Figure 16 RS422 Wiring Bus Requirements The bus cable must be a shielded 4 wire twisted pair cable Each pair of wires has to be used for exactly one data transmission direction The shield should be connected at both ends to the potential equalization system On each end the bus requires a termination resistor LT of 90 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 O netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 79 85 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 Table 70 Electric Requirements to RS 422 Cables The following lengths of lines can be achieved Max overall length of
50. n 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 9 LEDs netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 41 85 8 2 LEDs Real Time Ethernet Systems 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 Ub Color State Meaning SSS DwlEDmdgmen O Oo MS Duo LED red green Numberin Qg On Device operational Ifthe device is operating correctly the pla device green module status indicator shall be steady green rawing O Flashing Standby If the device has not been configured the module green status indicator shall be flashing green w On Major fault If the device has detected a non recoverable red major fault the module status indicator shall be steady red Flashing Minor fault If the device has detected a recoverable minor fault the module status indicator shall be flashing red NOTE An incorrect or inconsistent configuration would be consid ered a minor fault Self test While the device is performing its power up testing the module status indicator shall be flashing green red Off No power If no power is supplied to the device the
51. n the Adobe Acrobat Reader for mat PDF Video Audio Video Tutorial in AVI Format Tutorials Table 4 Directory Structure of the DVD 1 5 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 NT50 CC CCS 2 csp NT50 CC CCS 3 csp NT50 CC CCS 4 csp NT50 CC CCS IO csp CANopen Slave NT50 CO COS EDS EtherNet IP Adapter HILSCHER NT 50 EN EIS V1 1 EDS PROFIBUS DP Slave HIL 0C99 GSD PROFINET IO Device GSDML V2 1 HILSCHER NT 50 EN PNS 20100226 xml Table 5 Device Description Files for net AP NT 50 on the DVD DeviceNet Slave NT50 DN DNS EDS The device description files are for the configuration of the used master netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 12 85 1 5 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 User Manual netTAP NT 50 Gateway Devices UM xx Installation Operation and Hardware EN pdf this manual Gateway Solutions xx EN pdf User Manual Ethernet Device Configuration Ethernet Device Configuration Ol xx EN pdf Assignment of
52. ncnnnnoo 35 6 COMMISSIONING DECOMMISSIONING erm 36 6 1 Load Firmware and Configuration cccccccsscceccseeceecceeceeccueceeecueseecueseeeseesaeenaes 36 6 1 1 Download Configuration Files from the PC oocccccnccccncccccnnccncccnnnncnconcncnnconnnnnnos 36 6 1 2 Potential Differences for Device Types NT 50 xx RS coococcccoccccoccccccnccncncnncnnnnnnnos 37 6 2 Starts SAVIO saeua ee edge LE caused 37 6 3 F tthe Device out or Opera sisi 37 T TROUBLESHOOTING reren 38 1 1 Failure in 10 MBit s Half Duplex Mode and Workaround 39 8 EZB an cos dl 40 8 1 System LEEDS nenne 40 8 2 LEDs Real Time Ethernet Systems 022202402200200000 0000 nen nnn nenne san nme nn enennnn 41 8 2 1 LEDs EtherNet IP Scanner Master us 440044440RRennn nenne nenne nenne nennen 41 8 2 2 LEDs EtherNet IP Adapter Slave 2 u0222002000020000Rnn0 nenne nenne enn 42 8 2 3 LEDS Open Modpus EGP issue 43 8 2 4 LEDS PROFINET IO RT DEV CE aia di 44 8 3 LEDS Feldbus Systeme A A 45 8 3 1 LED PROFIBUS DP Master rosaa ee eisen 45 8 3 2 LED PROFIBUS DP SIAVE neu nee 45 8 3 3 LED ANOPen Master ut IT 46 8 3 4 LED CANOPER SIaVe zen een 47 8 3 9 LEED DeviceNet Master szene ee eles ee Gee ee 48 8 3 6 LED DeviceNet ola VE as 48 8 4 CEDS Sene laca seines 49 8 4 1 EID VIGO DUS IES Un nee 49 8 4 2 PAS Cll an ee daa 50 9 TECGRAHNICAE DATA sonont a en ios 5
53. nglish 2010 09 Released Public Hilscher 2010 Technical Data 96 85 9 2 4 PROFINET IO RT Controller Link Supported Protocols RTC Real Time Cyclic Protocol Class 1 RTA Real Time Acyclic Protocol DCP Discovery and configuration Protocol CL RPC Connectionless Remote Procedure Call Context management by CL RPC Supported Minimum cycle time 1 ms Different IO Devices can be configured with different cycle times Baud rate 100 MBit s Full Duplex mode Data transport layer Ethernet Il IEEE 802 3 Configuration File Maximum 1 MByte Limitations Reference to firmware stack version 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 lO Device NameOfStation of IO Controller CANNOT be set using the DCP SET NameOfStation service but only at start up while configuring the IO Controller SNMP not supported LLDP not supported 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
54. nimum distance between two devices Electric Requirements to RS 422 Cables RS422 Conductor Length and Transmission Rates Electric Requirements to RS 485 Cables RS 485 Cable Lengths netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public 12 73 73 73 74 76 76 76 79 79 81 81 O Hilscher 2010 Contacts 12 Contacts Headquarters Germany Hilscher Gesellschaft f r 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 New Delhi 110 025 Phone 91 11 40515640 E Mail info hilscher in Italy Hilscher Italia srl 20090 Vimodrone MI Phone 39 02 25007068 E Mail info hilscher it Support Phone 39 02 25007068 E Mail it support hilscher com netTAP NT 50 Gateway Devices DOC091202UMO2EN Revision 2 English 2010 09 Released Public 85 85 Japan Hilscher Japan KK Tokyo 160
55. nterface Transmission rate 10 kBit s for the device type 20 kBit s NT 50 CO XX 50 kBit s 100 kBit s 125 kBit s 250 kBit s 500 kBit s 800 kBit s 1 MBit s Interface Type ISO 11898 optically isolated Connector SubD male 9 pin DeviceNet Interface Transmission rate 125 kBit s for the device type 250 kBit s NT 50 DN EN 500 kBit s Interface Type ISO 11898 optically isolated Connector COMBICON 5 pin Interface Type RS 232 RS 422 RS 485 RJ45 Interface Type PROFIBUS Interface for the device types NT 50 DP EN Connector Interface Type Serial Interface for the device type Connector NT 50 xx RS Ethernet and serial interface to gether in one connector Table 43 Technical Data NT 50 Part 2 netTAP NT 50 Gateway Devices DOC091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Technical Data 53 85 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 ACD Address Conflict Detection not supported DLR not
56. ommunication systems are currently supported at the pri mary network X2 Supported Communication System DP PROFIBUS DP Serial Modbus RTU or ASCII Table 9 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 10 Network on port X3 Secondary Network netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Description and Requirements 18 85 3 2 2 Protocol Conversions The following table lists the protocol conversion and the necessary netT AP NT 50 device type Device Name Protocol at X2 Protocol at X3 Firmware File Firmware Version o NT 50 CO EN NT 50 DN EN CANopen Master for one slave CANopen Slave DeviceNet Slave EtherNet IP Adapter Slave N5CCSEIS NXF 1 0 x x EtherNet IP Scanner Master 1 NSCCSEIL NXF PROFINET IO Device PROFINET IO Controller 1 Open Modbus TCP NT 50 CC RS CC Link Slave ASCII N5CCSASC NXF Modbus RTU Master Slave N5CCSMBR NXF EtherNet IP Adapter Slave PROFINET IO Device Open Modbus TCP EtherNet IP Adapter Slave EtherNet IP Scanner Master 1 NSCOSEIL NXF PROFINET IO Device PROFINET IO Controller 1 Open Modbus TCP NT 50 CO RS CANopen Master for one slave ASCII N5COLASC NXF Modbus RTU Master Slave N5COLMBR N
57. on page 81 The following illustration shows wiring for RS 485 l Master M N ra Pul Up toV u D1 _ DO I Pull Down GND Figure 17 RS 485 Wiring Bus requirements The bus cable must be a shielded twisted pair cable where the shield should be connected at both ends with large contact areas to the potential equalization system On each end the bus requires a termination resistor LT between the lines D1 und DO of approximately the amount of the characteristic wave imped ance of the cable which usually amounts to a value between 120 O and 220 Q netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 81 85 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 lt 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 impedance Loop resistance Table 72 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 73 RS 485 Cable Lengths netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 R
58. ons 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 system configurator netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Description and Requirements 20 85 3 4 Configuration Requirements The configuration software SYCON net must be installed on a PC The re quirements for the PC are PC with 1 GHz processor or higher Windows 2000 and Windows XP Internet Explorer 5 5 or higher Free disk space min 400 MByte DVD ROM drive RAM min 512 MByte recommended 1024 MByte Graphic resolution min 1024 x 768 pixel Keyboard and Mouse 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 4 Device Drawings and Connections 4 1 Device and Dimensioned Drawings Side view 60 mm 4 mm 5 5 mm Device type with Combicon con nector with RJ45 Socket NT 50 CC EN NT 50 CC RS NT 50 DN EN NT 50 DN RS Figure 2 Device Drawings In the drawing above X
59. onsumer has oc curred e Bus Off The CAN controller is bus off red Table 34 LEDs CANopen Master LED State Definition for CANopen Master for the CAN LED The indicator is constantly on Of The indicator is constantly off 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 se quence is finished by a long off phase 1 000 ms Table 35 LED State Definition for CANopen Master for the CAN LED netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 47 85 8 3 4 LED CANopen Slave The subsequent table describes the meaning of the LEDs for the fieldbus device when the firmware of the CANopen Slave protocol is loaded to the device ib eoor State Meaning SSS CAN Duo LED red green of The device is executing a reset wd Single flash STOPPED The Device is in STOPPED state green wi Blinking PREOPERATIONAL The Device is in the PREOPERA green TIONAL state On OPERATIONAL The Device is in the OPERATIONAL state green Of No Error The Device is in working condition Single flash Warning Limit reached At least one of the error
60. otocol Conversions eeeseesee nnn 17 3 2 1 Device NAMES usted CN Dur ea aola to ipea ee 17 3 2 2 FTOLIOCOLCOnVSrSIOTIS sustenta recoRbuD en o 18 3 9 System Iedulrermehls esse nba 19 3 4 Configuration Requirements 2 a oues 20 4 DEVICE DRAWINGS AND CONNECTIONS eene 21 4 1 Device and Dimensioned Drawing cccccceecseceeeseeceeceeceeeeeeeeeseeseeseeseeseeeaeees 21 4 2 LEEDS and ContollEle mentes cba 22 4 3 CONNECCION ERE DUET UT TRIN tet 23 4 3 1 AL MOD OMe GOlis ates EE ee reed alate een 23 4 3 2 AZ FFONLGCONNECLON rn een en 23 4 3 3 X3 BOOM CONNECCION i TTE TU TT 26 4 4 Schematic Diagram Galvanic Isolati0N ooccocccoccccncoccocnconccnncanconncanonononnnos 31 4 4 1 Galvanic Isolation of NT 50 xx EN Devices ooccooccoccoccooccocoooncncconncononanonnonanonnons 32 4 4 2 Galvanic Isolation of NT 50 xx RS 2222202200nnennnnnnnnnnnnennnnnnennn nennen nennen nenn 33 4 4 3 Galvanic Isolation of NT 50 RS EN sssseseee men nmn nnne nen 34 5 NT 50 MOUNTING AND DISMOUNTING uu2202u2s0 nu RH mmn 35 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 3 85 5 1 DIN Top Hat Rail Mounting of the NT 50 22u22s0ssuessensnenenenennenenennenenennnnen 35 5 2 Removing the NT 50 from the DIN Top Hat Rall o ooccocccoccocncoccccnccc
61. p or the freedom from inter ference by third parties No additional guarantees or assurances are made regarding marketability freedom of defect of title integration 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 8 85 1 2 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 2 6 Registered Trademarks Windowse 2000 Windowse XP are registered trademarks of Microsoft Corporation Adobe Acrobate is a registered trademark of the Adobe Systems Incorpo rated netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 9 85 1 3 Conventions in this Manual Operation instructions a result of an o
62. peration step or notes are marked as follows Operation Instructions gt instruction Or 1 lt instruction gt 2 lt instruction gt Results Y result Notes db Important lt important note gt gt Note lt note gt lt note were to find further information gt Numbering o Er n 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 10 85 1 4 Reference to Hardware Software and Firmware Hardware NT 50 RS EN 2 Serial Table 2 Reference to Hardware Software Software Version SYCONnet netX setup exe 1 300 xxx Table 3 Reference to Software Firmware Firmware for the protocol conversion see section Protocol Conversions on page 18 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 11 85 1 5 Contents of the Product DVD The product DVD for the netT AP NT 50 contains e Setup program for the configuration and diagnostic program SYCON net and for Ethernet Device Setup program e Documentation e Firmware e Device Description Files GSD GSDML EDS 1 5 1 Directory Structure of the DVD All manuals on this DVD are delivered i
63. ponents of the Y charge 9 digit charge number shows Y at position 5 nnnnYnnnn Reference Summary of 10BT problemon EthernetPHY RenesasElectronics Europe April 27 2010 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 40 85 8 LEDs 8 1 System LEDs LED Color site Meaning Duo LED yellow green D green On Operating System running further diagnostic see APL LED This state may occur only briefly If this LED stays permanently yellow then a hardware failure is possible o Flashing Error state Boot loader active yellow green Off Power supply for the device is missing or hardware failure UD Color Sms Meaning APL Duo LED red green 2 d On The communication on X2 and X3 is in cyclic green data exchange and the gateway function is executed yellow green Blinking with netTAP is initialized but the communication green 2 s off on X2 is not in cyclic data exchange 0 5 son Blinking with netTAP is initialized but the communication green 2 s off on X3 is not in cyclic data exchange 0 5 s on 0 5 s off 0 5 s on Blinking with netTAP is initialized but the configuration for 2 s off the communication protocol on X2 is missing 0 5 son 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 o
64. pull down resistor of 100 kQ is connected device internally at Rx Tx netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 25 85 4 3 2 5 X2 for Device Type NT 50 RS EN RS 232 pin assignment RS 232 Pin Signal Description FP ee eden around oponer sus Reference potential ground of power supply 3 data 9 pole sub D socket male Table 17 RS 232 pin assignment RS 422 pin assignment men m smi Tome 0000 Hb recio data poste o 6 nor Tamsmt wapste O TxD Transmit data negative 9 pole sub D socket male Table 18 RS 422 pin assignment A pull up resistor of 10 KQ is connected device internally at RxD A pull down resistor of 10 KQ is connected device internally at RxD RS 485 pin assignment n 1 GND Reference potential ground of power supply 4 RxD TxD Receive data Transmit data positive 5 RxD TxD Receive data Transmit data negative 9 pole sub D socket male Table 19 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 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 26 85 43 3 X3 Bottom Connection 4 3 3 1 X3 for Devi
65. r PROFIBUS DP Master devices PROFIBUS Master netX DTM en pdf tion Manual Operating Instruc Generic DTM for PROFIBUS DP Slave devi PROFIBUS Generic Slave DTM en pdf tion Manual ces ASCII Handshake Mechanism ASCII Handshake Mechanism UM xx EN pdf Table 6 Documentation for netTAP NT 50 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Safety 13 85 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 sk
66. ription ie 0V Ground of power supply GND Table 12 Power supply line pin assignment X2 Front Connection X2 for Device Type NT 50 CO xx CANopen pin assignment CANopen Pm Signal Beso NR 2 emnt cwwstsine s socND CAN ground SS 9 pole sub D male Table 13 CANopen pin assignment X2 for Device Type NT 50 CC xx CC Link pin assignment DA Data ee Data ground DN RN Shield internally connected to common ground Field ground internally connected to common ground Socket female Table 14 CC Link pin assignment netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Device Drawings and Connections 24 85 4 3 2 3 X2 for Device Type NT 50 DN xx DeviceNet pin assignment DeviceNet Pin Signal Description 1 ISO GND Common ground 9 DeviceNet power supply CAN L CAN Low signal 85 CANH CAN High signal COMBICON 5 V 24 V DeviceNet power supply Socket female Table 15 DeviceNet pin assignment 4 3 2 4 X2 for Device Type NT 50 DP xx RS 485 Profibus pin assiqnment sonus Pin sme mein _ _ ___ Lions Control seal for pester rec conto 6 VP Power supply positive w Rx Tx Receive Transmit data negative 9 pole sub D socket female Table 16 PROFIBUS RS 485 pin assignment A pull up resistor of 100 kQ is connected device internally at Rx Tx A
67. rotocol Technical Data EtherNet IP Adapter Slave Protocol Technical Data Open Modbus TCP Protocol Technical Data PROFINET IO RT Controller Technical Data PROFINET IO RT Device Protocol Technical Data CANopen Master Link Protocol Technical Data CANopen Slave Protocol Technical Data CC Link Slave Protocol Technical Data DeviceNet Master Link Protocol Technical Data DeviceNet Slave Protocol Technical Data PROFIBUS DP Master Link Protocol Technical Data PROFIBUS DP Slave Protocol netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public 83 85 Hilscher 2010 Lists Table 56 Table 57 Table 58 Table 59 Table 60 Table 63 Technical Data ASCII Protocol Technical Data Modbus RT U Protocol Use of Hubs and Switches PROFIBUS Segment Length in Dependence of the Baud Rate Characteristics of PROFIBUS certified Cable Table 61 Table 62 Characteristics of CAN certified Cable 84 85 65 66 69 71 71 12 CAN Segment Length in dependence of the Baud rate or corresponding Loop Resistance and Wire Gauge Maximum length in dependence from the baud rate for DeviceNet cables Table 64 Characteristics of DeviceNet Data Line Cable Table 65 Table 66 Characteristics of DeviceNet Power Supply Cable DeviceNet Segment Length in dependence of the Baud rate Table 67 Table 68 Table 69 Table 70 Table 71 Table 72 Table 73 Maximum length Maximum length Mi
68. s well as to the ANSI standard refer to reference safety 1 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Description and Requirements 16 85 3 Description and Requirements 3 1 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 I O Data Mapping Device Figure 1 Function NT 50 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 netTAP 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 Information about the configuration of the device with SYCON net soft ware is in the manua
69. s 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 Table 63 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 lt 39 4 pf m lt 22 6 Ohm km Thin 120 Ohm 39 4 pf m 91 8 Ohm km Table 64 Characteristics of DeviceNet Data Line Cable The power supply cables must match the following conditions Loop Resis Wire Gauge tance Diameter Table 65 Characteristics of DeviceNet Power Supply Cable COMBICON DeviceNet Netzteil power supply for DeviceNet DeviceNet Interface DeviceNet Interface Versorgungsleitung AN ower lines EN 5 24V 5 rot red power Ii i 24V I j GND 1 schwarz black 1 GND l twisted pair cable r CAN High 4 wei white verdrillte Leitung 4 CAN High CAN_Low CAN_Low COMBICON Buchse COMBICON Buchse COMBICON female connector COMBICON female connector Figure 13 DeviceNet Network Please ensure that termination resistors with 120 Ohm are available at both ends of the cable Further devices can be connected via T stubs to the bus cable The maxi mum length of all T stubs is 6 m The whole length of the bus cable
70. ted If the device has at least one established con nection even to the Message Router the network status indicator shall be steady green 2 Number in the device n drawing No connections If the device has no established connec tions but has obtained an IP address the network status indicator shall be flashing green Flashing green Duplicate IP If the device has detected that its IP address is already in use the network status indicator shall be steady red Connection timeout If one or more of the connections in which this device is the target has timed out the network status indicator shall be flashing red This shall be left only if all timed out connections are reestablished or if the device is reset Flashing D a gt Self test While the device is performing its power up testing the network status indicator shall be flashing green red Flashing D gd dd 2 red green Off Not powered no IP address If the device does not have an IP address or is powered off the network status indicator shall be steady off LINK RJ4 LED green Number On A connection to the Ethernet exists in the de l green vice draw Off The device has no connection to the Ethernet ing ACT RJ45 Number in the device LED yellow Flashing The device sends receives Ethernet frames drawing YELLOW Table 29 LEDs EtherNet IP Adapter Slave netTAP NT 5
71. th the communication controllers netX 50 NOTICE netX100 or netX 500 with the protocols Ethernet TCP UDP IP Ether Net IP or Modbus TCP at 10 MBit s in half duplex mode otherwise fail ure of the network communication can occure Use only switches or 10 100 MBit s dual speed hubs and ensure that the network operates at 100 MBit s and in full duplex mode 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 Ether Net IP or Modbus TCP at 10 MBit s in half duplex mode otherwise fail ure of the network communication can occure Use only switches or 10 100 MBit s dual speed hubs and ensure that the network operates at 100 MBit s and in full duplex mode A For further information refer to section Failure in 10 MBit s Half Duplex Mode and Workaround on page 39 netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Appendix 70 85 10 13 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 baud rates Use only a special cabl
72. the configuration tool SYCON net The following overview describes the error conditions that may be detected by a visual check ofthe LEDs In order to find the correct position of the LEDs please follow the chapter LEDs and Control Elements from page 22 The numbers in the column LED state is referencing the position number in the device drawing No LED is on The device is not powered or the device has a malfunction and needs re placement 3 a After a power cycle the device has not found a valid firmware and remains in SYS LED flashes bootloader mode The device has to be send back to the manufacturer for repair SYS LED 1 is permanet d The device has a malfunction and needs replacement yellow SYS LED 1 aches d 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 O is permanet ai 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 rea flashing or red on The communication via port X2 or and port X3 is not in data exchange mode AFELE Hashing d green See chapter System LEDs on page 40 Table 27 NT 50 Troubleshooting yellow green at 1 Hz The device is operational just in case the illustrated error conditions do not met Further protocol specific error diagnostics via the LEDs is possible by reading on the chapter LEDs In deep
73. the device gt LED eee aon In Watchdog timeout channel generic or extended diagnosis the device S present system error drawing Flashing DCP signal service is initiated via the bus cyclic at 2 k for 3 sec BF Duo LED T Number in d On No configuration or low speed physical link or no physical the device red link drawing d Flashing No data exchange red cyclic at 2 Hz for jWem LINK RJ45 LED M A connection to the Ethernet exists 0 The device has no connection to the Ethernet RX TX RJ45 LED yellow wd Flashing The device sends receives Ethernet frames yellow Table 31 LEDs PROFINET IO RT Device netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 45 85 8 3 LEDs Feldbus Systeme 8 3 1 LED PROFIBUS DP Master The subsequent table describes the meaning of the LEDs for the fieldbus when the firmware of the PROFIBUS DP Master protocol is loaded to the device Eb coor state Meng SSS netTAP NT 50 current Hardware Revision COM Duo LED red green Flashing No configuration or stack error green acyclic Flashing cy Profibus is configured but bus communication is not yet green clic released from the application wi On Communication to all Slaves is established green Flashing cy Communication to at least one Slave is disconnected red clic On Communication to one all Slaves is disconnected red
74. tion mbH All rights reserved The images photographs and texts in the accompanying material user manual accompanying texts documentation etc are protected by 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 2 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 man
75. ual 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 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 f r 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Introduction 7 85 1 2 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 do
76. ug to the bare braided shield under the strain relief Fix the strain relief with screws The cable connection should look like shown below Figure 10 D Sub Cable Assemblies O OJO 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 DOCO091202UMO2EN Revision 2 English 2010 09 Released Public O Hilscher 2010 Appendix 69 85 10 1 2 Ethernet 10 1 2 1 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 Negotiation 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 58 Use of Hubs and Switches Failure of the Network Communication Do not operate hardware wi
77. ves Ethernet frames the device yellow drawing Table 28 LEDs EtherNet IP Scanner Master netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 LEDs 42 85 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 ib Color ss Men SS Duo teDredigeen SS MS Duo LED red green Number in Qg On Device operational If the device is operating correctly the me device green module status indicator shall be steady green rawing 4 d Flashing Standby If the device has not been configured the module green status indicator shall be flashing green On Major fault If the device has detected a non recoverable red major fault the module status indicator shall be steady red Flashing Minor fault If the device has detected a recoverable minor fault the module status indicator shall be flashing red NOTE An incorrect or inconsistent configuration would be consid ered a minor fault Self test While the device is performing its power up testing the module status indicator shall be flashing green red Off No power If no power is supplied to the device the module status indicator shall be steady off Duo LED red green wl Flashing red green D a gt NS Connec
78. vice 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 as illustrated at the left onto the top hat rail from above 1 Then press the device against the mounting surface according to ar row 2 Figure 7 Mounting the netTAP NT 100 device onto the DIN 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 DIN top hat rail 5 2 Removing the NT 50 from the DIN Top Hat Rail In order to remove the netTAP from the DIN Top Hat Rail first remove the power supply cable and all data cables from the device To release the device from the DIN Top Hat Rail use a screw driver which you put at the clip 1 in the center of the device By pressing the screw driver in direction of arrow the lock at the DIN top hat rail is released You can then easily pull the device off the DIN top hat rail in direction of arrow 3 Figure 8 Removing the NT 50 device from the DIN Top Hat Rail netTAP NT 50 Gateway Devices DOCO091202UMO2EN Revision 2 English 2010 09 Released Public Hilscher 2010 Commissioning Decommissioning 36 85 6 Commissioning

netTAP NT 50

Contents

Download Pdf Manuals

Related Search

Related Contents