Related Manuals for hilscher netTAP NT 151-RE-RE
Summary of Contents for hilscher netTAP NT 151-RE-RE
- Page 1 User manual netTAP NT 151RERE RealTime Ethernet gateway Hilscher Gesellschaft für Systemautomation mbH www.hilscher.com DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public...
-
Page 2: Table Of Contents
Safety instructions to avoid property damage .............. 17 2.6.1 Device destruction by exceeding allowed supply voltage........ 17 2.6.2 Danger of unsafe system operation.............. 18 2.6.3 Device destruction due to overheating ............ 18 Labeling of safety messages .................. 19 Description .......................... 20 Functionality ........................ 20 Protocol conversions ...................... 22 Interfaces........................ 22 Requirements.......................... 23 Device drawings and connectors .................. 24 Dimensioned drawings .................... 24 Positions of the interfaces and LEDs ................ 25 Device label ........................ 26 Protocol logo and LED label sticker ................ 27 Power supply connector .................... 28 Ethernet connectors ....................... 28 USB interface (MiniB USB) ................... 29 Galvanic isolation ...................... 30 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... - Page 3 12 Technical data......................... 68 12.1 Technical data netTAP NT 151RERE ................ 68 12.2 Technical data of the protocols .................. 70 12.2.1 PROFINET IO Controller ................. 70 12.2.2 PROFINET IO Device.................. 71 12.2.3 EtherNet/IP Scanner.................. 73 12.2.4 EtherNet/IP Adapter .................. 74 12.2.5 EtherCAT Master..................... 74 12.2.6 EtherCAT Slave.................... 75 12.2.7 Sercos Master .................... 75 12.2.8 Sercos Slave .................... 76 13 Decommissioning/Disposal.................... 77 13.1 Putting the device out of operation................. 77 13.2 Disposal of waste electronic equipment ................. 77 Contacts .......................... 81 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public...
-
Page 4: Introduction
Introduction 4/81 1 Introduction About this document 1.1.1 Description of the contents This user manual describes hardware, technical data, installation and commissioning of the Hilscher netTAP gateway device NT 151RERE for RealTime Ethernet networks. This document also features stepbystep instructions on how to reset the netTAP device to its “factory settings” (a.k.a. “firmware recovery”) and how to use an SD memory card to copy configuration data from one device to another (a.k.a. “cloning” of a spare device). Technical data of the supported RealTime Ethernet protocols can also be found in this document. Note that the configuration of the NT 151RERE device is not subject of this document. Configuration and firmware download are described in the operating instruction manual Configuration of Gateway and Proxy Devices, DOC081201OIxxEN. Instructions on how to install the necessary configuration software can be found in the user manual Software Installation, DOC100315UMxxEN. 1.1.2 Obligation to read the manual Important: Ø To avoid personal injury or property damage to your system or to your device, you must read and understand all instructions in this manual and in the documents accompanying your device before installing and operating your device. Ø First read the Safety Instructions in the chapter Safety [} page 16]. Ø Observe all Safety Messages in this manual. Ø Keep the product DVD providing the product manuals. 1.1.3 List of revisions Index Date... -
Page 5: Conventions In This Document
Introduction 5/81 1.1.4 Conventions in this document Notes, operation instructions and results of operation steps are marked as follows: Notes Important: <important note> Note: <simple note> <note, where to find further information> Operation instructions 1. <operational step> Ø <instruction> Ø <instruction> 2. <operational step> Ø <instruction> Ø <instruction> Results <intermediate result> <final result> For a description of the labeling of Safety Messages, see section Labeling of safety messages [} page 19]. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 6: Reference To Hardware, Firmware, Software And Drivers
1722.122/S3S/S3M T120J0I0.NXF 1.x.x EtherNet/IP Adapter 1722.122/S3S/EIS T120J0H0.NXF 1.x.x EtherNet/IP Scanner 1722.122/S3S/EIM T120J0G0.NXF 1.x.x EtherNet/IP Adapter PROFINET IO Device 1722.122/EIS/PNS T120H0D0.NX 1.x.x PROFINET IO Controller 1722.122/EIS/PNM T120H0C0.NX 1.x.x EtherCAT Master 1722.122/EIS/ECM T120H0E0.NX 1.x.x Sercos Master 1722.122/EIS/S3M T120H0I0.NXF 1.x.x EtherNet/IP Adapter 1722.122/EIS/EIS T120H0H0.NX 1.x.x EtherNet/IP Scanner 1722.122/EIS/EIM T120H0G0.NX 1.x.x Table 2: Reference to firmware netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 7: Table 3: Reference To Software
Software This document relates to the following software versions: Software Version File name Path on Gateway Solutions DVD SYCON.net 1.400.x.x SYCONnet netX setup.exe Setups & Drivers\SYCON.net Table 3: Reference to software 1.1.5.3 Device description files This document relates to the following device description files: If used as Devices File name Path on Gateway Solutions DVD PROFINET IO Device 1722.122/PNS/PNS GSDMLV2.31HILSCHERNT 151 Electronic Data Sheets (e.g. 1722.122/PNS/PNM RERE PNS201510211.xml EDS,GSD,GSDML)\PROFINET 1722.122/PNS/ECM 1722.122/PNS/S3M 1722.122/PNS/EIM 1722.122/ECS/PNS 1722.122/S3S/PNS 1722.122/EIS/PNS EtherCAT Slave 1722.122/ECS/PNS Hilscher NT 151ECSXX Vx.x.xml Electronic Data Sheets (e.g. 1722.122/ECS/PNM EDS,GSD,GSDML)\EtherCAT 1722.122/ECS/ECS 1722.122/ECS/ECM 1722.122/ECS/S3M 1722.122/ECS/EIS... -
Page 8: Contents Of The Product Dvd
· Tools · Directory of the DVD: Folder Contents Documentation 1. Software Operating instruction manuals for device configuration (PDF) Ethernet Device Setup Utility SYCON.net Configuration Software 2. Hardware User manuals of the gateway devices (PDF) netBRICK 100, Model NB 100xxyy netLINK PROXY, Model NL 51NDPL netTAP 50, Model NT 50xxyy netTAP 100, Model NT 100xxyy netTAP 151, Model NT 151RERE 3. For Programmers Documentation for developers (PDF) Error Codes Compilation IO Data Flow Control of 3964R protocol IO Data Flow Control of ASCII protocol Modbus RTU Specification Modbus TCP Specification netSCRIPT Scripting Language 4.PLC Application Notes Controllogix PLCs EthernetIP Integration SIMATIC PLCs Consistent Data PROFIBUS,PROFINET SIMATIC PLCs Migration from PROFIBUS to PROFINET Simple TCPIP connectivity through Modbus TCP 5.Installation Instructions Wiring and software installation instructions for standard users (PDF) netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 9: Table 6: Directory Of Gateway Solutions Dvd
Files needed for displaying the installation menu of the Gateway Solutions DVD Setups & Drivers Lua for Windows netSCRIPT_Debugger Setup Installation wizard for software components SYCON.net Configuration and diagnosis software USB Driver Supplements & Examples Device Factory Reset netBRICK 100 Factory Settings netTAP 100 Factory Settings netTAP 151 Factory Settings Modbus RTU,TCP Technical Resources Source Code from www.freemodbus.org (Freeware) Test Tools from www.modbustools.com (Shareware) netSCRIPT Source Codes RSLogix5000 Projects Siemens STEP7 Projects Example project acyclic communication PROFINET IO Device to Ethernet IP Scanner SYCON.net Projects SYCON.net example projects Training & Podcasts Podcasts Flash video presentations Powerpoints PowerPoint presentations Table 6: Directory of Gateway Solutions DVD netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 10: Documentation Overview
Software Installation Gateway Solutions UM xx Gateway Solutions configuration EN.pdf software Table 7: Basic documentation for NT 151RERE NT 151RERE as PROFINET IO Controller You also need the following documents if you are using the device as PROFINET IO Controller: Title Contents Document ID Path on the Gateway Solutions DVD Operating Description of the DOC060302OIxxEN Documentation\english\1.Software\SYCON.net Instruction Manual device type manager Configuration Software\Master Configuration DTM for Hilscher for PROFINET IO \PROFINET IO Controller\PROFINET IO Controller PROFINET IO Controller devices DTM OI xx EN.pdf Controller Devices Operating Description of the DOC060305OIxxEN Documentation\english\1.Software\SYCON.net Instruction Manual device type manager Configuration Software\Master Configuration Generic DTM for for generic \PROFINET IO Controller \IO Device Configuration PROFINET IO PROFINET IO \PROFINET IO Generic Device DTM OI xx EN.pdf... -
Page 11: Table 9: Additional Documentation For Nt 151Rere As Profinet Io Device
PROFINET IO PROFINET IO \PROFINET IO Generic Device DTM OI xx EN.pdf Devices devices Table 9: Additional documentation for NT 151RERE as PROFINET IO Device NT 151RERE as EtherCAT Master You also need the following documents if you are using the device as EtherCAT Master: Title Contents Document ID Path on the Gateway Solutions DVD Operating Description of the DOC080404OIxxEN Documentation\english\1.Software\SYCON.net Instruction Manual device type manager Configuration Software\Master Configuration DTM for Hilscher for EtherCAT Master \EtherCAT Master\EtherCAT Master DTM OI xx EtherCAT Master devices EN.pdf Device Operating Description of the DOC071202OIxxEN Documentation\english\1.Software\SYCON.net Instruction Manual device type manager Configuration Software\Master Configuration Generic Slave DTM for generic EtherCAT \EtherCAT Master\Slave Configuration\EtherCAT for EtherCAT Slave slave devices Generic Slave DTM OI xx EN.pdf Devices User Manual ... -
Page 12: Table 12: Additional Documentation For Nt 151Rere As Ethernet/Ip Scanner
DTM for modular devices EtherNet/IP Adapter Devices Table 12: Additional documentation for NT 151RERE as EtherNet/IP Scanner NT 151RERE as Sercos Master You also need the following documents if you are using the device as Sercos Master: Title Contents Document ID Path on the Gateway Solutions DVD Operating Description of the DOC090301OIxxEN Documentation\english\1.Software\SYCON.net Instruction Manual device type manager Configuration Software\Master Configuration\sercos DTM for Hilscher for sercos master Master\sercos Master DTM OI xx EN.pdf sercos Master devices Devices Operating Description of the DOC090302UMxxEN Documentation\english\1.Software\SYCON.net Instruction Manual device type manager Configuration Software\Master Configuration\sercos Generic Slave DTM for generic sercos Master\Slave Configuration\sercos Generic Slave for sercos Slave slave devices DTM OI xx EN.pdf Devices Table 13: Additional documentation for NT 151RERE as Sercos Master netTAP NT 151RERE | RealTime Ethernet gateway... -
Page 13: Legal Notes
Introduction 13/81 Legal notes 1.4.1 Copyright © Hilscher 2016, Hilscher Gesellschaft für Systemautomation mbH All rights reserved. The images, photographs and texts in the accompanying material (user manual, accompanying texts, documentation, etc.) are protected by German and international copyright law as well as international trade and protection 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 notices, markings, trademarks or ownership declarations. The included diagrams do not take the patent situation into account. The company names and product descriptions included in this document may be trademarks or brands of the respective owners and may be trademarked or patented. Any form of further use requires the explicit consent of the respective rights owner. 1.4.2 Important notes The user manual, accompanying texts and the documentation were created for the use of the products by qualified experts, however, errors cannot be ruled out. For this reason, no guarantee can be made and neither juristic responsibility for erroneous information nor any liability can be assumed. Descriptions, accompanying texts and documentation included in the user manual do not present a guarantee nor any information about proper use as stipulated in the contract or a warranted feature. It cannot be ruled out that the user manual, the accompanying texts and the documentation do not correspond exactly to the described features, standards or other data of the delivered product. No warranty or 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 obligations. 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 followon damage or loss of... -
Page 14: Exclusion Of Liability
Introduction 14/81 1.4.3 Exclusion of liability The software was produced and tested with utmost care by Hilscher Gesellschaft für Systemautomation mbH and is made available as is. No warranty can be assumed for the performance and flawlessness of the software for all usage conditions and cases and for the results produced when utilized by the user. Liability for any damages that may result from the use of the hardware or software or related documents, is limited to cases of intent or grossly negligent violation of significant contractual obligations. Indemnity claims for the violation of significant contractual obligations are limited to damages that are foreseeable and typical for this type of contract. It is strictly prohibited to use the software in the following areas: for military purposes or in weapon systems; · for the design, construction, maintenance or operation of nuclear · facilities; in air traffic control systems, air traffic or air traffic communication · systems; · in life support systems; · 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 failproof control mechanisms. Use of the software in such an environment occurs at your own risk. No liability is assumed for damages or losses due to unauthorized use. 1.4.4 Warranty Although the hardware and software was developed with utmost care and tested intensively, Hilscher Gesellschaft für Systemautomation mbH does not guarantee its suitability for any purpose not confirmed in writing. It cannot be guaranteed that the hardware and software will meet your requirements, that the use of the software operates without interruption and that the software is free of errors. No guarantee is made regarding infringements, violations of patents, rights of ownership or the freedom from interference by third parties. No additional guarantees or assurances are... -
Page 15: Export Regulations
1.4.6 Registered trademarks ® Adobe Reader is a registered trademark of the Adobe Systems Incorporated. EtherNet/IP™ is a trademark of ODVA (Open DeviceNet Vendor Association, Inc). ® EtherCAT is a registered trademark and a patented technology of Beckhoff Automation GmbH, Verl, Federal Republic of Germany, formerly Elektro Beckhoff GmbH. ® PROFINET is a registered trademark of PROFIBUS & PROFINET International (PI), Karlsruhe. ® ® Sercos and Sercos interface are registered trademarks of Sercos international e. ® ® ® ® Windows XP, Windows Vista, Windows 7 and Windows 8 are registered trademarks of Microsoft Corporation. All other mentioned trademarks are property of their respective legal owners. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 16: Safety
General note The user manual, the accompanying texts and the documentation are written 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. Intended use The netTAP NT 151RERE device described in this manual is a communication device connecting two separate RealTime Ethernet networks with each other. The device thus serves as a “gateway” between the two networks. The netTAP NT 151RERE device is equipped with a compact housing and is intended for DIN rail mounting according to DIN EN 60715. Personnel qualification The netTAP NT 151RERE must be installed, configured and removed only by qualified personnel. Jobspecific technical skills for people professionally working with electricity must be present concerning the following topics: Safety and health at work · Mounting and connecting of electrical equipment · Measurement and Analysis of electrical functions and systems · · Evaluation of the safety of electrical systems and equipment · Installing and Configuring IT systems References safety [S1] ANSI Z535.62006 American National Standard for Product Safety Information in Product Manuals, Instructions, and Other Collateral Materials [S2] IEC 609501, Information technology equipment Safety Part 1: General requirements, (IEC 609501:2005, modified); German Edition EN 609501:2006 [S3] EN 6134051 and EN 6134052 as well as IEC 6134051 and IEC 6134052 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 17: Safety Instructions To Avoid Personal Injury
Safety 17/81 Safety instructions to avoid personal injury To ensure your own personal safety and to avoid personal injury, you must read, understand and follow the safety instructions and all safety messages in this manual about danger that might cause personal injury, before you install and operate your netTAP NT 151RERE device. 2.5.1 Danger of unsafe system operation To prevent personal injury, make sure that the removal of the netTAP NT 151RERE device from your plant during operation will not affect the safe operation of the plant. Safety instructions to avoid property damage To avoid property damage to your system or to the netTAP NT 151RERE device, you must read, understand and follow the safety instructions and all safety messages in this manual about danger that might cause property damage, before you install and operate your device. 2.6.1 Device destruction by exceeding allowed supply voltage Observe the following notes concerning the supply voltage: The netTAP NT 151RERE device may only be operated with the · specified supply voltage. Make sure that the limits of the allowed range for the supply voltage are not exceeded. A supply voltage above the upper limit can cause severe damage to the · device! A supply voltage below the lower limit can cause malfunction of the · device. The allowed range for the supply voltage of the netTAP NT 151RERE device is specified in section Technical data netTAP NT 151RERE [} page 68]. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 18: Danger Of Unsafe System Operation
Safety 18/81 2.6.2 Danger of unsafe system operation To prevent property damage, make sure that the removal of the netTAP NT 151RERE device from your plant during operation will not affect safe operation of the plant. 2.6.3 Device destruction due to overheating The air ventilation slots of the netTAP device must not be covered by any objects, otherwise the device might overheat! Maximum environmental temperature is +60 °C. If the environmental temperature exceeds +50 °C, you must allow for a minimum of 17.5 mm distance between the netTAP and neighboring devices. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 19: Labeling Of Safety Messages
The Section Safety Messages at the beginning of a chapter are · pinpointed particularly and highlighted by a signal word according to the degree of endangerment. The kind of danger is specified exactly by the safety message text and optionally by a specific safety sign. · The Integrated Safety Messages embedded in operating instructions are highlighted by a signal word according to the degree of endangerment. In the safety message, the nature of the hazard is indicated. Signal words and safety signs in safety messages on personal injury Signal word Meaning Indicates a direct hazard with high risk, which will have as consequence death or grievous bodily harm if it is not avoided. Indicates a possible hazard with medium risk, which will have as consequence death or (grievous) bodily harm if it is not avoided. Indicates a minor hazard with medium risk, which could have as consequence personal injury if it is not avoided. Table 14: Signal words in safety messages on personal injury Safety sign Sort of warning or principle Warning of lethal electrical shock Principle: Disconnect the power plug Table 15: Safety signs in messages on personal injury Signal words and safety signs in safety messages on property damage Signal word Meaning Indicates a property damage message Table 16: Signal words in safety messages on property damage Safety sign Sort of warning or principle Warning of property damage by electrostatic discharge Table 17: Safety signs in safety messages on property damage netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 20: Description
Description 20/81 3 Description Functionality The netTAP NT 151RERE device is a communication gateway connecting two separate RealTime Ethernet networks. The two networks can be either using the same (e. g. PROFINET IO to PROFINET IO) or two different RTE network systems protocols (e. g. EtherNet/IP to PROFINET IO). The NT 151RERE always acts as slave device in the primary network (which is connected at gateway interface X2); in the secondary network however (which is connected at gateway interface X3), it can act either as slave or as master device. For processing the communication, each of the device’s two network interfaces has its own netX controller: the primary network interface (X2) is controlled by the netX 51, the secondary network interface (X3) by the more powerful netX 100. Figure 1: Data flow netTAP NT 151RERE netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... - Page 21 Description 21/81 The protocol conversion (e. g. PROFINET IO Device to EtherNet/IP Scanner) is determined by the firmware installed in the device. The communication parameters are to be configured by the user himself by means of the SYCON.net configuration and diagnosis software, which is included in the scope of delivery. The netTAP NT 151RERE device is equipped with a compact housing and is suitable for DIN rail mounting according to DIN EN 60715. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public...
-
Page 22: Protocol Conversions
T120J0J0.NXF Master 1722.122/PNS/S3M 1722.122/ECS/S3M 1722.122/S3S/S3M 1722.122/EIS/S3M T120D0I0.NXF T120F0I0.NXF T120J0I0.NXF T120H0I0.NXF EtherNet/IP Adapter 1722.122/ECS/EIS 1722.122/S3S/EIS 1722.122/EIS/EIS T120F0H0.NXF T120J0H0.NXF T120H0H0.NXF Scanner 1722.122/PNS/EIM 1722.122/ECS/EIM 1722.122/S3S/EIM 1722.122/EIS/EIM T120D0G0.NXF T120F0G0.NXF T120J0G0.NXF T120H0G0.NXF Table 18: Available protocol conversions with article numbers and firmware names Interfaces The Ethernet interface for the primary network (X2), consisting of two RJ45 jacks, is located on the upper side of the NT 151RERE device, the Ethernet interface for the secondary network (X3), also consisting of two RJ45 jacks, is located on the bottom side of the device. The configuration interfaces (Mini USB socket and SD memory card slot) are easily accessible at the front of the device. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 23: Requirements
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. For the allowed temperature, see section Technical data netTAP NT 151RERE [} page 68]. Requirements for using the SYCON.net configuration software For installing and operating the SYCON.net configuration software on your PC, you need the following: PC with 1 GHz processor or higher · ® ® ® Windows 7 (32 bit) SP1, Windows 7 (64 bit) SP1, Windows 8 (32 bit) · ® or Windows 8 (64 bit) Administrator privilege required for installation · 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 USB interface · netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 24: Device Drawings And Connectors
Device drawings and connectors 24/81 5 Device drawings and connectors Dimensioned drawings Outer dimensions of the netTAP NT 151RERE: Figure 2: Outer dimensions of NT 151RERE Dimensions of the power supply plug: Figure 3: Dimensions of Mini COMBICON power supply plug Important: When planning the installation of the netTAP device, reserve sufficient room above and below the device to allow for convenient plugging or unplugging of the network and power supply cables. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 25: Positions Of The Interfaces And Leds
RealTime Ethernet interface channel 2 (X2, RJ45 socket) (10) LINK LED for RealTime Ethernet interface channel 2 (11) ACT LED for RealTime Ethernet interface channel 2 (activity) (12) RealTime Ethernet interface channel 3 (X2, RJ45 socket) (13) LINK LED for RealTime Ethernet interface channel 3 NT 151RERE front view (14) ACT LED for RealTime Ethernet interface channel 3 (activity) (15) RealTime Ethernet interface channel 0 (X3, RJ45 socket) (16) LINK LED for RealTime Ethernet interface channel 0 (17) ACT LED for RealTime Ethernet interface channel 0 (activity) (18) RealTime Ethernet interface channel 1 (X3, RJ45 socket) (19) LINK LED for RealTime Ethernet interface channel 1 (20) ACT LED for RealTime Ethernet interface channel 1 (activity) (21) Connector for supply voltage (X1) Top view (X2) Bottom view (X3) Table 19: LEDs and interfaces NT 151RERE netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 26: Device Label
Device label Each netTAP NT 151RERE carries a device type label providing the following information: Communication channels of primary network at X2 MAC address at X2 Abbreviation of primary network protocol at X2 Device type ID Article number Serial number of device Hardware revision number Matrix label Abbreviation of secondary network protocol at X3 (10) MAC address at X3 (11) Communication channels of secondary network at X3 (12) Voltage supply interface (X1) Protocol abbreviations: PNM PROFINET IO Controller PNS PROFINET IO Device ECM EtherCAT Master ECS EtherCAT Slave S3M Sercos Master Sercos Slave EtherNet/IP Scanner EtherNet/IP Adapter POWERLINK Controlled Node netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 27: Protocol Logo And Led Label Sticker
Device drawings and connectors 27/81 Protocol logo and LED label sticker Each netTAP with preloaded firmware is delivered with the appropriate protocol logos and LED labels already attached to the device. Devices without preloaded firmware (for which the appropriate firmware has to be loaded into the device by the customer) are shipped with a separate sheet of sticker labels for all supported protocols. The customer can attach the stickers to the device in order to mark the network interfaces and their protocolspecific LEDs. Figure 4: Protocol stickers netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 28: Power Supply Connector
ISO_IN Isolated input (reserved for future use) ISO_OUT Isolated output (reserved for future use) 0 V / GND Ground of supply voltage +24 V +24 V supply voltage Table 20: Pin assignment of 5pole power supply socket Use a fivepole MINI COMBICON plug (included in the delivery) for connecting the voltage supply: Supply voltage Signal Description Reserved for future use Reserved for future use Reserved for future use 0 V / GND Ground of supply voltage 24 V +24 V supply voltage Mini Combicon Table 21: Pin assignment Mini Combicon plug 5pole Ethernet connectors The RealTime Ethernet interfaces are equipped with RJ45 sockets (see positions (9), (12), (15) and (18) in section Positions of the interfaces and LEDs [} page 25]). Use twisted pair cables of category 5 (CAT5) or higher, consisting of four twisted pairs. The maximum baud rate is 100 MBit/s (CAT5). Note: The device supports Auto Crossover function. Due to this fact, RX and TX can be switched. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 29: Usb Interface (Minib Usb)
RX– Receive data – Connected to FE via RC combination* RJ45 Buchse Shield Capacitive to FE * Bob Smith Termination Table 22: Ethernet RJ45 pin assignment If you are using the netTAP with EtherCAT, please observe also the user manual Wiring Instructions EtherCAT, DOC121104UMxxEN, stored on the Gateway Solutions DVD in the Documentation\english\5.Installation Instructions directory. USB interface (MiniB USB) The USB interface (see position (6) in section Positions of the interfaces and LEDs [} page 25]) is used for configuring the netTAP NT 151RERE with SYCON.net (see operating instruction manual Configuration of Gateway and Proxy Devices, DOC081201OIxxEN) and for recovering the firmware (see section Using USB to recover firmware [} page 39]). USB socket Signal Description D Data Data + Ground Shield Capacitive to GND Table 23: Pin assignment MiniB USB connector (5pin) netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 30: Galvanic Isolation
Device drawings and connectors 30/81 Galvanic isolation Figure 5: Galvanic isolation of NT 151RERE Note: The isolated area is the gray area in the picture above. Functional earth is connected via back plane bus of the DIN top hat rail. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 31: Mounting Of Device
Mounting of device 31/81 6 Mounting of device Safety messages Please observe the following safety messages: Device destruction due to compensating currents ! Please pay attention to the grounding and shielding concept of your plant. The concept should prevent the flowing of compensating currents via signal and power supply lines between the used devices. Otherwise device destruction of the netTAP is possible. Device destruction due to overheating ! The air ventilation slots of the netTAP device must not be covered by any objects. Otherwise the device might overheat. Maximum allowed environmental temperature is + 60 °C. If the environmental temperature exceeds + 50 °C, you must allow a minimum distance of 17.5 mm between the netTAP and neighboring devices. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 32: Mounting Device Onto Top Hat Rail
Mounting of device 32/81 Mounting device onto Top Hat Rail Ø The netTAP device is to be mounted onto a horizontally attached top hat rail according to DIN EN 60715. Ø The rail has to be connected with the potential equalization conductor (FE). Figure 6: Mounting the netTAP device onto Top Hat Rail Ø Push the device onto the top hat rail from above (1). Ø Then press the device against the rail until the bolt of the lower hook engages (2). Ø After mounting, connect the 24 V supply voltage to the device. Device Destruction by Exceeding the Allowed Supply Voltage! The supply voltage must not exceed 30 V, otherwise the netTAP device will be damaged. Note: Grounding is done via a grounding contact located at the backside of the device, connecting it electrically to the DIN top hat rail. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 33: Removing Device From Top Hat Rail
Mounting of device 33/81 Removing device from Top Hat Rail Ø Before dismounting the netTAP from the top hat rail, first remove the power supply cable and all data cables from the device. Figure 7: Removing the netTAP device from Top Hat Rail Ø Put a screw driver into the slot of the latch at the bottom of the device. Ø To disengage the lock of the hook, pull down the latch with the screw driver. Ø Take the device off the top hat rail. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 34: Commissioning
DOC081201OIxxEN. Configuration The netTAP needs to be configured with the Windows configuration software SYCON.net via the USB interface of the device (see position (6) in section Positions of the interfaces and LEDs [} page 25]). SYCON.net allows you to create a configuration “offline”, without an actual connection to the target device (i. e. the netTAP). Only for the subsequent download of the configuration into the device, you need a physical USB connection. The device stores this data remanently, i. e. the data is being kept after power off or device reset. Detailed information about configuration with SYCON.net can be found in the operating instruction manual Configuration of Gateway and Proxy Devices, DOC081201OIxxEN on the Gateway Solutions DVD in the Documentation\english\1.Software \SYCON.net Configuration Software\Configuration of Gateway and Proxy Devices OI xx DE.pdf directory. Startingup with inserted SD memory card In case an SD memory card containing a valid configuration is inserted into the netTAP NT 151RERE while a poweron cycle is being performed, all data stored on the card will be copied to the internal load memory of the device. (For the position of the memory card slot, see (5) in section Positions of the interfaces and LEDs [} page 25].) This data can be: firmware · configuration files · Any old data stored in the load memory will be erased by this. With this procedure, you can reset the device to its factory settings or load a desired configuration without having to establish a USB connection to the SYCON.net configuration software. SYCON.net offers the function to copy the data of the internal load memory of an already configured netTAP onto an inserted empty SD memory card. Thus, you can easily “clone” a configuration and transfer it into another device, e. g. into a spare device in case of a defective primary device. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... - Page 35 Commissioning 35/81 Note that the SD card must be FAT formatted, otherwise it will not be recognized by the device. Detailed instructions on how to transfer configuration data into another netTAP device by SD memory card can be found in chapter Using SD memory card to copy configuration data into spare netTAP devices [} page 47]. Resetting the netTAP to its factory settings by using an SD memory card (e. g. in case of a defective firmware) is described in the subsequent chapter. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public...
-
Page 36: Firmware Recovery
8 Firmware recovery Overview If after poweron the SYS LED (see position (3) in section Positions of the interfaces and LEDs [} page 25]) is flashing yellow and green at a rate of 1 Hz, the device is in boot mode. The firmware file of the netTAP NT 151RE RE is missing or defective. In this state the device cannot be operated and the firmware needs to be recovered either by SD memory card or via USB. Using SD memory card to reset the device to its factory settings When using the SD memory card, the file system inside the device will be reformatted and all existing firmware, configuration or IP address files will automatically be deleted. The device will thus be reset to its “factory settings”. Note that by this method, only a socalled “base firmware” is copied from the SD memory card to the device, enabling the subsequent downloading of the “regular” full firmware by SYCON.net via USB connection. This means that after using the SD card, you will have to establish a USB connection between the netTAP and your configuration PC in order to download the regular firmware and a new configuration to the device with SYCON.net. Using USB and ComProX2 to reset the device to its factory settings/ recover the firmware On the other hand, if you are using the Hilscher ComProX2 tool via USB, you can directly access the file system of the netTAP and overwrite the old defective firmware file with a fresh firmware file. Here, you can directly download the “regular” firmware to the netTAP without first having to use the “base firmware” – as it is the case when using the SD card. Since ComProX2 allows you to format the whole file system or to erase or download only individual files, you can decide for yourself whether you want to reset the device to its factory settings (erase all files and then download firmware) or whether you want to preserve old configuration files inside the device and only erase the old defective firmware file by downloading new firmware file, thus performing only a “firmware recovery” instead of a “factory reset”. Note, however, that a defective firmware most likely causes corruption also of the file system, thus making a reformatting of the file system strongly advisable before downloading the new firmware file. Therefore it is recommended to completely reset the device to its factory settings instead of just exchanging/recovering the firmware. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 37: Using An Sd Memory Card To Reset The Nettap To Its "Factory Settings
Firmware recovery 37/81 Using an SD memory card to reset the netTAP to its “factory settings” The netTAP NT 151RERE can be reset to its factory settings by using the load memory image on an SD memory card. You will find the load memory image on the Gateway Solutions DVD in the Supplements & Examples \Device Factory Reset\netTAP 151 Factory Settings \Recovery via Memory Card directory. From there, you can copy the image to the SD memory card, and then use the card to copy it to the netTAP device. All existing old data (including the configuration) in the internal load memory of the netTAP will thereby be deleted and a “base firmware” will be loaded to the device. After recovery by SD card, you therefore must download the full “regular” firmware and a new configuration to the device with SYCON.net. Note: The SD memory card is not included in the delivery of the NT 151 RERE device, but can be obtained from Hilscher. The part number of the card is 1719.003. Prerequisites Empty SD memory card (FAT formatted) · PC with SD card reader device · Gateway Solutions DVD · The netTAP device is supplied with voltage · Stepbystep instructions 1. Copy load memory image from DVD to SD card. Ø If applicable: remove write protection on your SD memory card. Ø Insert the empty SD memory card into the SD card reader device of your PC. Ø On the Gateway Solutions DVD, open Supplements & Examples \Device Factory Reset\netTAP 151 Factory Settings \Recovery via Memory Card directory. -
Page 38: Figure 8: Insert Sd Card
Firmware recovery 38/81 2. Copy load memory image to netTAP device. Ø Disconnect the voltage supply from your netTAP device. Ø Insert the SD card into the card slot of the netTAP device until it engages (metal contacts of the card must be facing left). Figure 8: Insert SD card Ø Reconnect the voltage supply of your netTAP device. Ê The device then loads the memory image. While loading the image, the SYS LED quickly alternates between green and yellow for approximately eight seconds, then shows steady yellow for approximately ten seconds, then is switched off for a short while before it finally shows steady green light. The device automatically starts the loaded firmware. Ø Remove the SD memory card from device. ð The netTAP device has been reset to its factory settings. The device now needs a firmware download and a new configuration with SYCON.net via USB connection. Instructions for this can be found in the operating instruction manual Configuration of Gateway and Proxy Devices, DOC081201OIxxEN. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 39: Using Usb To Recover Firmware
Firmware recovery 39/81 Using USB to recover firmware Via USB, you can reset the netTAP device to its factory settings by re formatting its file system and downloading a new firmware file to the device. For this, you need a USB cable with a Mini USB connector and the Hilscher ComProX2 tool, which is stored on the Gateway Solutions DVD in the Supplements & Examples\Device Factory Reset\netTAP 151 Factory Settings\Recovery via USB directory. ComProX2 can be executed directly from DVD, it does not need to be installed on your configuration PC. Note that for recovery via USB, you need to install the USB driver for the Hilscher netTAP on your configuration PC. This driver allows you to communicate with the netTAP via USB, even if the old firmware within the device is defective or missing altogether. It is recommended to install the USB driver before you connect the netTAP device via USB cable. Use the setup.exe driver installation program for this, which is stored on the Gateway Solutions DVD in the Setups & Drivers\USB Driver directory. The installation of the USB driver is described in the user manual Software Installation Gateway Solutions, DOC100315UMxxEN, which is stored on the Gateway Solutions DVD in the Documentation\english\5.Installation Instructions directory. Note: As an alternative, you can just perform a socalled “firmware recovery” by downloading a new firmware file to the device without having reformatted the file system beforehand, thus preserving all existing configuration files within the device. Note, however, that a defective firmware most likely causes corruption also of the file system, therefore you are strongly advised to reformat the file system before downloading a new firmware file. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 40: Figure 9: Comprox Start Window
Firmware recovery 40/81 Prerequisites The USB driver for Hilscher netTAP has been installed on the · configuration PC (the driver is included in the USB driver installation program stored on the Gateway Solutions DVD). The configuration PC has been connected to the netTAP device via · USB cable. You have access to the Gateway Solutions DVD. · The netTAP device is supplied with voltage. · · Disconnect all other Hilscher devices (apart from the NT 151RERE) that may happen to be also connected to the configuration PC via USB. · If applicable, close SYCON.net on your configuration PC. Stepbystep instructions 1. Open ComProX2. Ø On the Gateway Solutions DVD, open Supplements & Examples \Device Factory Reset\netTAP 151 Factory Settings \Recovery via USB directory. Ø Doubleclick comproX2.exe file. Ê The ComProX2 tool opens: Figure 9: ComProX start window netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 41: Figure 10: Activate Auto Refresh Function
Firmware recovery 41/81 2. Activate AutoRefresh function. Ø Open Connection menu and make sure that the File Explorer auto refresh option is checked. Figure 10: Activate auto refresh function 3. Connect to netTAP device. Ø In the menu, choose Connection > Open. Ê After the Windows USB/COM ports on the configuration PC have been scanned, the Open USB Port dialog window opens. The netTAP is displayed in the dropdown list as 2nd Stage Loader (netX100/500) behind the connecting USB COM of the PC (in this example COM18): Figure 11: ComProX Open USB Port dialog window Note: The socalled “Second Stage Bootloader” (2nd Stage Loader) is a software module inside the netTAP complementing the regular firmware. If the firmware is defective or missing, the Second Stage Bootloader takes over, enabling communication between the device and ComProX2 via USB. A netTAP device running with proper functional firmware connected via USB would answer at the COM port with a netTAP 151 entry, followed by the abbreviation of the protocol conversion implemented in the firmware (e. g. PNS/PNS). Ø Click OK button. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 42: Figure 12: Contents Of The Nettap Ports Displayed In Comprox
Firmware recovery 42/81 Ê The Open USB Port dialog window closes. The File Explorer (left window) shows the files currently stored in the various ports of the netTAP. (The ports within the netTAP are not to be confused with the USB COM ports of the configuration PC.) Figure 12: Contents of the netTAP ports displayed in ComProX 4. Reformat file system (delete old files in flash memory of netTAP). Ø Before you proceed to reformat the file system, thus deleting all existing files, you should note or writedown the exact name of the firmware file stored in PORT_0. You can recognize the firmware file by its NXF file extension. In this example, it is the T120D0D0.NXF file (protocol conversion PROFINET IO Device to PROFINET IO Device). Noting the file name makes it easier for you to identify the file later on the Gateway Solutions DVD for download. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 43: Figure 13: Format Flash Memory
Firmware recovery 43/81 Ø In the menu, choose Connection > Format Flash Disk > Quick Format. Figure 13: Format flash memory Ø In the Information window, click OK button. Figure 14: Acknowledge formatting dialog Ê The file system is being formatted and all files in the ports are deleted. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 44: Figure 15: Formatting Finished Message
Firmware recovery 44/81 Ø Acknowledge the Quick Format is finished message by clicking the OK button. Figure 15: Formatting finished message 5. Download firmware file. Ø In the File Explorer (left window) select PORT_0 entry. Ø Use the right mouse button to open the context menu and select Download. Figure 16: Download menu netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 45: Figure 17: Open File Dialog
Firmware recovery 45/81 Ê The Open file to download dialog window opens: Figure 17: Open File Dialog Ø On the Gateway Solutions DVD, open Firmware\netTAP 151 folder. Search the list for the name of the firmware file which you had noted/written down before you formatted the file system/flash disk. In this example, it is the T120D0D0.NXF file (protocol conversion PROFINET IO Device to PROFINET IO Device). Note: You can also consult the table in the Hardware and firmware [} page 6] section in order to find out the name of the right firmware file for your protocol conversion. Ø Select the firmware file you want to download, then click Open button. Ê The file is being downloaded: Figure 18: Download status netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 46: Figure 19: Download Finished Message
Firmware recovery 46/81 Ø Acknowledge the File successfully downloaded message by clicking the OK button. Figure 19: Download finished message Ê The downloaded firmware file should now be displayed under PORT_0: Figure 20: Firmware in PORT_0 Ø In the menu, choose Connection > Close to close the connection to the netTAP, then choose File > Exit to close ComProX. 6. Restart netTAP device. Ø Disconnect the voltage supply from the device, then reconnect it. Ê After restart, the SYS LED shows steady green light (indicating firmware is running) and the APL LED shows steady red light (indicating missing configuration). ð You have reset the netTAP device to its factory settings. The device now needs a new configuration with SYCON.net via USB connection. Instructions for this can be found in the operating instruction manual Configuration of Gateway and Proxy Devices, DOC081201OIxxEN. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 47: Using Sd Memory Card To Copy Configuration Data Into Spare Nettap Devices
Using SD memory card to copy configuration data into spare netTAP devices 47/81 9 Using SD memory card to copy configuration data into spare netTAP devices Overview With the Memory Card Management function of the netTAP DTM in SYCON.net, you can copy an already downloaded configuration together with the firmware and the IP address from the internal load memory of the netTAP device onto an SD memory card, which has been inserted into the device. Thus, you can “backup” this data to an external storage medium. Afterwards, you can remove the SD memory card from the netTAP device, insert it into other devices and thus copy the data into their internal load memory. By this method, you can easily bring several devices to an identical state of configuration (i. e. “clone” a primary device) without having each time to establish an online connection between the configuration PC (respectively SYCON.net) and the individual devices. This can be useful, e. g., if you want to prepare an identical “spare” device. Prerequisites · SD memory card, FAT formatted. Note: The SD memory card is not included in the delivery of the NT 151 RERE device, but can be obtained from Hilscher, part number 1719.003. · A configuration has been downloaded to the netTAP device. · The Windows PC/Notebook with SYCON.net and the netTAP device are connected via USB. · The netTAP is connected to a voltage supply. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 48: Stepbystep Instructions
Using SD memory card to copy configuration data into spare netTAP devices 48/81 Stepbystep instructions 1. Start SYCON.net configuration software. Ø In the Windows Start menu, select All Programs > SYCON.net System Configurator > SYCON.net. Ê A login dialog appears: Figure 21: Login SYCON.net Ø Enter your password, then click OK. Ê SYCON.net opens with a new empty project: Figure 22: Empty project in SYCON.net netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 49: Figure 23: Sycon.net_Sd_Karte1
Using SD memory card to copy configuration data into spare netTAP devices 49/81 2. Open existing netTAP project or create a new project. Note: You can use your already existing configuration project to establish a USB connection between SYCON.net and the netTAP device, and to open the Memory Card Management dialog. If you don’t have access to the old configuration project file, you can create a provisional new project, consisting only of the netTAP symbol, and use this makeshift project to establish the USB connection. Ø In the menu, choose File > Open…to open an existing netTAP project. Ø In the Vendor tab of the Device Catalog (right window), open folder Hilscher GmbH > Gateway StandAlone Slave. Then select NT 151 RERE device and drag & drop it onto the bus configuration line in the middle window. Figure 23: SYCON.net_SD_Karte1 3. Open the netTAP configuration window (i. e. the netTAP DTM). Ø Doubleclick the netTAP symbol in the bus configuration line, or select the netTAP symbol and choose Configuration > Gateway from the context menu (to open context menu, rightclick on the netTAP symbol). netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 50: Figure 24: Device Assignment 1
Using SD memory card to copy configuration data into spare netTAP devices 50/81 Ê If you are using an existing netTAP project, for which the configuration of the driver and the device assignment had already taken place, the netTAP DTM now opens with the Settings dialog window. In this case, you can directly proceed with step 5. If you have just now created a new project, the netTAP DTM opens with the Device Assignment dialog window and immediately starts scanning for connected devices. Figure 24: Device assignment 1 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 51: Figure 25: Device Assignment 2
Using SD memory card to copy configuration data into spare netTAP devices 51/81 Ø Wait a moment until the connected device has been found: Figure 25: Device assignment 2 4. Assign netTAP device. Ø Select the found NT 151RERE by checking the field in front of the device entry. Figure 26: Device assignment 3 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 52: Figure 27: Memory Card Management Of The Nettap Dtm
Using SD memory card to copy configuration data into spare netTAP devices 52/81 Ø Click Apply button. 5. Copy configuration data from netTAP device to SD memory card. Ø In the Navigation Area, select Configuration > Memory Card Management. Ê The Memory Card Management dialog window opens. The Folder field in the Directory area of the dialog window displays the file system of the internal load memory of the netTAP device: Figure 27: Memory Card Management of the netTAP DTM Ø Remove the write protection of your SD memory card and insert it into the netTAP device until it engages (metal contacts of card must be facing left). Figure 28: Insert SD card netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 53: Figure 29: Memory Card Management After Inserting Sd Memory Card
Using SD memory card to copy configuration data into spare netTAP devices 53/81 Ø In order to refresh the display: close the Memory Card Management dialog window (e. g. by clicking on Signal Mapping entry in the Navigation area), then open it again. Ê In the Folder field of the Directory area, the file system of the SD memory card is now displayed below the directory of the internal load memory of the netTAP device (scroll down in the Folder field). Furthermore, the Backup button is now active and can be used: Figure 29: Memory Card Management after inserting SD memory card Ø Click Backup to copy the data stored in the internal load memory of the netTAP to the SD memory card. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 54: Figure 30: Memory Card Management After Backup To Sd Memory Card
Using SD memory card to copy configuration data into spare netTAP devices 54/81 Ê The data is copied to the SD memory card. This can take a short while (observe the clock symbol in the footer of the dialog window). After copying has been finished, the data is displayed below SDMMC: \Backup in the Folder field: Figure 30: Memory Card Management after backup to SD memory card Ø Click OK to close the netTAP DTM. Ø Exit SYCON.net 6. Copy data from SD memory card into spare netTAP device. Ø Remove the SD memory card from the original netTAP device. Ø Insert the SD memory card into the spare device. Ø Connect spare device to voltage supply or briefly disconnect voltage supply (in case the device had already been connected to voltage supply). ð The spare netTAP device then loads the data from the SD memory card into its own internal load memory. While loading, the SYS LED quickly alternates between green and yellow for approximately eight seconds, then shows steady yellow for approximately ten seconds, then is switched off for a short while before it finally shows steady green light. The device automatically starts the loaded firmware and the configuration. Ø Remove the SD memory card from the netTAP device. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 55: Leds
State Meaning Duo LED yellow/green Operating System running. For further diagnosis, see APL LED. Position in the device (green) drawing: (3) The hardware of the device is defective and needs replacement. (yellow) The device could not be initialized. No boot loader was found in (yellow) the load memory. The load memory of the device might be Flashing defective or a USB cable, which has pin 4 connected with ground, might be attached to the device. This prevents the device from starting. Flashing Error state! Boot loader active. yellow/green (yellow/ Firmware file is missing or defective. The device needs to be green) 1 Hz recovered by SD memory card or via USB. See chapter Firmware recovery [} page 36]. Flashing Data is being copied from the SD memory card into the internal yellow/green load memory. (yellow/ green) 16 Hz Power supply for the device is missing or hardware is defective. (off) Table 24: System LED netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 56: Apl Led
Blinking with netTAP is initialized, but the communication on X2 is not in cyclic data (green) 2 s off, exchange. 0.5 s on Blinking with netTAP is initialized, but the communication on X3 is not in cyclic data (green) 2 s off, exchange. 0.5 s on, 0.5 s off, 0.5 s on Blinking with netTAP is initialized, but the configuration for the communication (red) 2 s off, protocol on X2 is missing or has an error. 0.5 s on Blinking with netTAP is initialized, but the configuration for the communication (red) 2 s off, protocol on X3 is missing or has an error. 0.5 s on, 0.5 s off, 0.5 s on netTAP has detected an error during the initialization: (red) · Missing configuration · Error in configuration · Internal error Table 25: APL LED netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 57: Leds Of The Realtime Ethernet Systems
OFF") LINK LED green (green) On The device is linked to the Ethernet. CH0: (16), CH1: (19) The device has no link to the Ethernet. (off) RX/TX LED yellow Flickering (load The device sends/receives Ethernet frames. CH0: (17), CH1: (20) dependent) (yellow) The device does not send/receive Ethernet frames. (off) Table 26: LED states for the PROFINET IOController protocol LED state Definition The indicator is constantly on. The indicator is constantly off. Flashing The indicator turns on and off for 3 seconds with a frequency of 1 Hz: (1 Hz, 3 s) “on” for 500 ms, followed by “off” for 500 ms. Flashing The indicator turns on and off with a frequency of 2 Hz: (2 Hz) “on” for 250 ms, followed by “off” for 250 ms. Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependent) activity: "on" for approximately 50 ms, followed by "off" for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity. Table 27: LED state definitions for the PROFINET IOController protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 58: Leds Profinet Io Device
LED green (green) On The device is linked to the Ethernet. CH0: (16), CH1: (19) CH2: (10), CH3: (13) The device has no link to the Ethernet. (off) RX/TX LED yellow Flickering (load The device sends/receives Ethernet frames. CH0: (17), CH1: (20) dependent) (yellow) CH2: (11), CH3: (14) The device does not send/receive Ethernet frames. (off) Table 28: LED states for the PROFINET IODevice protocol LED state Definition The indicator is constantly on. The indicator is constantly off. Flashing The indicator turns on and off for 3 seconds with a frequency of 1 Hz: (1 Hz, 3 s) “on” for 500 ms, followed by “off” for 500 ms. Flashing The indicator turns on and off with a frequency of 2 Hz: (2 Hz) “on” for 250 ms, followed by “off” for 250 ms. Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependent) activity: "on" for approximately 50 ms, followed by "off" for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity. Table 29: LED state definitions for the PROFINET IODevice protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 59: Leds Ethercat Master
LINK LED green (green) On The device is linked to the Ethernet. CH0: (16) The device has no link to the Ethernet. (off) LED yellow Flickering (load The device sends/receives Ethernet frames. CH0: (17) dependent) (yellow) The device does not send/receive Ethernet frames. (off) Table 30: LED states for the EtherCAT Master(V3) protocol LED 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: (2.5 Hz) “on” for 200 ms, followed by “off” for 200 ms. Flickering (10 Hz) The indicator turns on and off with a frequency of 10 Hz: “on” for 50 ms, followed by “off” for 50 ms. Single flash The indicator shows one short flash (200 ms) followed by a long “off“ phase (1,000 ms). Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependant) activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity. Table 31: LED state definitions for the EtherCAT Master(V3) protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 60: Leds Ethercat Slave
LED green (green) On Link: The device is linked to the Ethernet, but does not send/ CH0: (16), CH1: (19) receive Ethernet frames. CH2: (10), CH3: (13) (green) Flickering (load Activity: The device is linked to the Ethernet and sends/receives dependant) Ethernet frames. The device has no link to the Ethernet. (off) LED yellow This LED is not used. (off) Table 32: LED states for the EtherCAT Slave protocol LED 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: (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). Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependent) activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity. Table 33: LED state definitions for the EtherCAT Slave protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 61: Leds Ethernet/Ip Scanner
Duplicate IP: The device has detected that its IP address is (red) already in use. Not powered, no IP address: The device does not have an IP (off) address (or is powered off). LINK LED green (green) On The device is linked to the Ethernet. CH0: (16), CH1: (19) The device has no link to the Ethernet. (off) LED yellow Flickering (load The device sends/receives Ethernet frames. CH0: (17), CH1: (20) dependant) (yellow) The device does not send/receive Ethernet frames. (off) Table 34: LED states for the EtherNet/IP Scanner protocol LED state Definition The indicator is constantly on. The indicator is constantly off. Flashing The indicator turns on and off with a frequency of 1 Hz: (1 Hz) “on” for 500 ms, followed by “off” for 500 ms. Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependant) activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity. Table 35: LED state definitions for the EtherNet/IP Scanner protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 62: Leds Ethernet/Ip Adapter
(Off) Not powered, no IP address: The device does not have an IP (off) address (or is powered off). LINK LED green (green) On The device is linked to the Ethernet. CH0: (16), CH1: (19) CH2: (10), CH3: (13) The device has no link to the Ethernet. (off) LED yellow Flickering (load The device sends/receives Ethernet frames. CH0: (17), CH1: (20) dependent) CH2: (11), CH3: (14) (yellow) The device does not send/receive Ethernet frames. (off) Table 36: LED states for the EtherNet/IP Adapter protocol LED state Definition The indicator is constantly on. The indicator is constantly off. Flashing (1 Hz) The indicator turns on and off with a frequency of 1 Hz: “on” for 500 ms, followed by “off” for 500 ms. Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependant) activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity Table 37: LED state definitions for the EtherNet/IP Adapter protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 63: Leds Sercos Master
Blinking (2.5 Hz) Error in the configuration database. (red) Single Flickering Channel Init was executed at the Master. (red) Double Slave is missing. (red) Flickering Unconfigured Slave No matching mandatory slave list No bus connected Duplicate Sercos address Invalid Sercos address Flickering Bootup was stopped due to an error. (red) (10 Hz) No error (off) LED green (green) On Link: The device is linked to the Ethernet, but does not send/ CH0: (16), CH1: (19) receive Ethernet frames. (green) Flickering (load Activity: The device is linked to the Ethernet and sends/receives dependent) Ethernet frames. The device has no link to the Ethernet. (off) LED yellow This LED is not used. (off) Table 38: LED states for the Sercos Master protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 64: Table 39: Led State Definitions For The Sercos Master Protocol
LEDs 64/81 LED state Definition The indicator is constantly on. The indicator is constantly off. 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). Triple Flash The indicator shows a sequence of three 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). Quadruple Flash The indicator shows a sequence of four 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). Blinking (2.5 Hz) The indicator turns on and off with a frequency of 2.5 Hz: “on” for 200 ms, followed by “off” for 200 ms. Single Flickering The indicator is switched on and off once: 'on' for 50 ms, followed by 'off' for 500 ms. Double Flickering The indicator is switched on and off and on once: 'on' / 'off' / 'on' each for approximately 50 ms, followed by 'off' for 500 ms. Flickering (10 Hz) The indicator turns on and off with a frequency of 10 Hz: 'on' for 50 ms, followed by 'off' for 50 ms. Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependent) activity: 'on' for approximately 50 ms, followed by 'off' for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity. Table 39: LED state definitions for the Sercos Master protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 65: Led Sercos Slave
(2 Hz) error, (see Sercos Slave V3 Protocol API Manual). (red/ orange) Flashing Watchdog error: Application is not running (not yet implemented) (red) (2 Hz) Communication Error (C1D): Error detected according to Sercos (red) third generation Class 1 Diagnosis, see SCP Status codes class error (see Sercos Slave V3 Protocol API Manual). NRTMode: (Non RealTime Mode) No Sercos Communication (off) Duo LED red/green This LED is not used. (off) LED green (green) On Link: The device is linked to the Ethernet, but does not send/ CH0: (16), CH1: (19) receive Ethernet frames. CH2: (10), CH3: (13) (green) Flickering (load Activity: The device is linked to the Ethernet and sends/receives dependent) Ethernet frames. The device has no link to the Ethernet. (off) LED yellow This LED is not used. (off) Table 40: LED states for the Sercos Slave protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 66: Table 41: Led State Definitions For The Sercos Slave Protocol
LEDs 66/81 LED state Definition The indicator is constantly on. The indicator is constantly off. Flashing The indicator turns on and off with a frequency of 2 Hz: (2 Hz) one color: On for appr. 250 ms, followed by off for appr. 250 ms. two colors: First color for appr. 250 ms, followed by the second color for appr. 250 ms. Flashing (1 x green/3s) Flashing green for 250 ms, then orange on for 2 second and 750 ms. (2 x green/3s) Flashing green / orange / green, each for 250 ms, then orange on for 2 seconds and 250 ms. (3 x green/3s) Flashing green / orange / green / orange / green, each for 250 ms, then orange on for 1 second and 750 ms. (1 x orange/3s) Flashing orange for 250 ms, then green on for 2 second an 750 ms. (2 x orange/3s) Flashing orange / green / orange, each for 250 ms, then green on for 2 seconds and 250 ms. Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet dependent) activity: "on" for approximately 50 ms, followed by "off" for 50 ms. The indicator turns on and off in irregular intervals to indicate low Ethernet activity. Table 41: LED state definitions for the Sercos Slave protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 67: Troubleshooting
SYS The hardware of the device is defective and needs SYS LED shows static yellow Position in device replacement. drawing: (3) SYS The device is well initialized. Further diagnosis is SYS LED shows static green Position in device possible with the APL LED. See section APL LED [ } page 56]. drawing: (3) APL LED flashes red or shows static APL Position in device red. drawing: (4) APL The communication at port X2 or/and port X3 is not APL LED flashes green. Position in device in data exchange mode. See also section APL LED drawing: (4) [} page 56]. Table 42: netTAP NT 151RERE troubleshooting by LED For protocolspecific error diagnostics by LED, see section LEDs of the RealTime Ethernet systems [} page 57]. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 68: Technical Data
(DIN EN 611312) ESD contact discharge 6 kV (criterion A) (DIN EN 611312) Burst 2.2 kV (criterion B) (DIN EN 611312) Surge 1 kV (criterion A) (DIN EN 611312) Immunity: radiated, HF 10 V/m (criterion A) field (DIN EN 6100043) 80 MHz ... 3 GHz Immunity: conducted (DIN 10 V/m (criterion A) EN 6100046) 150 kHz ... 80 MHz Radio interference 30 ... 2000 MHz (criterion A) emission (DIN EN 5501623) Radio interference 0.01 ... 30 MHz (criterion A) voltage (DIN EN 5501621) Environmental conditions Ambient temperature If distance to neighboring devices is minimum 17.5 mm: range for operation 20 … + 60 °C If housing has contact to neighboring device (and if surface temperature of neighboring device does not exceed + 70 °C): 20 … + 50 °C Humidity 10 ... 95 % netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 69: Table 43: Technical Data Nettap Nt 151Rere
Technical data 69/81 Category Parameter Value Device Dimensions (L x W x H) 113.6 x 22.6 x 99 mm (without connector) Weight 121 g Mounting Top hat rail (DIN rail EN 60715) Protection class IP 20 RoHS CE Sign CE Sign Configuration Software SYCON.net Ethernet Interfaces Transmission rate 100 MBit/s 10 MBit/s Interface type 100 BASETX, isolated Half duplex/Full duplex supported (at 100 MBit/s) AutoNegotiation supported AutoCrossover supported Connector X2 (primary network): 2 x RJ45 X3 (secondary network): 2 x RJ45 Table 43: Technical data netTAP NT 151RERE netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 70: Technical Data Of The Protocols
Minimum cycle time 1 ms Different IO Devices can be configured with different cycle times Functions Fast Startup of PROFINET IO Devices supported Baud rate 100 MBit/s FullDuplex mode Data transport layer Ethernet II, IEEE 802.3 Configuration file Maximum 1 MByte Limitations Read/Write Record not supported No Alarm processing RT over UDP not supported Multicast communication not supported DHCP is not supported Only one IOCR per IO Device NameOfStation of IO Controller CANNOT be set using the DCP SET NameOfStation service but only at startup while configuring the IO Controller The buffer for IODevice 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 cycletime, the number of configured IO Devices and the amount of IO data depend on each other. For example it is not possible due to performance reasons to have 128 IO Devices communication with cycletime 1ms. The size of the bus configuration file is limited by the size of the RAM Disk (1 MByte) Only one API (API = 0) is supported WriteMultipleRecord service is not supported Reference to stack version PROFINET IO Controller 2.7.x.x Table 44: Technical data PROFINET IO Controller protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 71: Profinet Io Device
1440 Bytes Maximum number of cyclic output data 1440 Bytes Maximum number of submodules 255 submodules per Application Relation at the same time, 1000 submodules can be configured Multiple Application Relations (AR) The Stack can handle up to 2 IOARs, one Supervisor AR and one SupervisorDA AR at the same time. Supported protocols RTC – Real Time Cyclic Protocol, Class 1 (unsynchronized), Class 3 (synchronized) RTA – Real Time Acyclic Protocol DCP – Discovery and configuration Protocol CLRPC – Connectionless Remote Procedure Call LLDP – Link Layer Discovery Protocol SNMP – Simple Network Management Protocol MRP – MRP Client Topology recognition LLDP, SNMP V1, MIB2, physical device Identification & Maintenance Read and write of I&M14 Minimum cycle time 1 ms for RT_CLASS_1 IRT Support RT_CLASS_3 Media redundancy MRP client is supported Additional features DCP, VLAN and prioritytagging, Shared Device Baud rate 100 MBit/s Data transport layer Ethernet II, IEEE 802.3 PROFINET IO specification V2.2 (legacy startup) and V2.3 (but advanced startup only for RT) are supported. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 72: Table 45: Technical Data Profinet Io Rt Irt Device Protocol
Technical data 72/81 Parameter Description Limitations No acyclic user data transfer. RT over UDP not supported. Multicast communication not supported. DHCP is not supported. FastStartUp is not supported. The amount of configured IOdata influences the minimum cycle time that can be reached. Only 1 InputCR and 1 OutputCR are supported. Media Redundancy is not supported. System Redundancy (SRAR) and ConfigurationinRun (CiR) are not supported. Max. 255 submodules can be used simultaneously within one specific Application Relation. RT Class 2 synchronized (IRT “flex”) is not supported. Access to the submodule granular status bytes (IOCS) is not supported. SharedInput is not supported. MRPD is not supported. DFP and other HighPerformanceprofile related features are not supported. PDEV functionality is only supported for submodules located in slot 0. Submodules cannot be configured or used by an AR in subslot 0. DAP and PDEV submodules only supported in slot 0. NT 151RERE can be used in a PROFINET IRT network, however cannot be used with IRT communication due to the internal gateway structure and internal cycle times of the device. Reference to stack version V3.9 Table 45: Technical data PROFINET IO RT IRT Device Protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 73: Ethernet/Ip Scanner
UCMM, Class 3 Supported Quick connect Supported Predefined standard objects Identity Object Message Route Object Assembly Object Connection Manager Ethernet Link Object TCP/IP Object DLR Object QoS Object Topology Tree, Line, Ring DLR (Device Level Ring) Beacon based ’Ring Node’ ACD (Address Conflict Detection) Supported DHCP Supported BOOTP Supported Baud rate 10 and 100 MBit/s Data transport layer Ethernet II, IEEE 802.3 Switch function Integrated Limitations No acyclic user data transfer. CIP Sync Services are not implemented TAGs are not supported Reference to stack version V2.8 Table 46: Technical data EtherNet/IP Scanner (Master) protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 74: Ethernet/Ip Adapter
12.2.5 EtherCAT Master Parameter Description Maximum number of EtherCAT slaves Maximum 200 Slaves. The number of usable slaves depends on the available memory for the configuration file. See ‘configuration file’ below. Maximum number of cyclic input data 4600 bytes Maximum number of cyclic output data 4600 bytes Minimum bus cycle time 205 µs, depending on the used number of slaves and the used number of cyclic input data and output data. Recommended is a cycle time of 1 ms and higher. Bus Scan Supported Redundancy Not supported Distributed Clocks Supported Topology Line Baud rate 100 MBit/s Data transport layer Ethernet II, IEEE 802.3 Configuration File (ethercat.xml or config.nxd) Maximum 1 MByte Limitations No acyclic user data transfer The size of the bus configuration file is limited by the size of the FLASH disk (1 Mbyte). Reference to stack version V4.2.x.x Table 48: Technical data EtherCAT Master protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 75: Ethercat Slave
Maximum number of cyclic input data 5760 bytes (including Connection Control per Connection) Maximum number of cyclic output data 5760 bytes (including Connection Control per Connection) Maximum number of configured slave devices Minimum cycle time 250 µs Acyclic communication Service channel: Read/Write/Commands Functions Bus Scan Communication phases NRT, CP0, CP1, CP2, CP3, CP4 Topology Line and double ring Redundancy Supported NRT channel Supported Baud rate 100 MBit/s, full duplex Data transport layer Ethernet II, IEEE 802.3 Auto crossover Supported Supported Sercos version Communication Specification Version 1.3 TCP/IP Stack Integrated Limitations No acyclic user data transfer. NRT channel not used HotPlug not supported Cross Communication not supported Reference to stack version V2.1 Table 50: Technical daten sercos master protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 76: Sercos Slave
120 bytes (including Connection Control and IO Control) Maximum number of slave devices Maximum number of applicable sercos addresses 1 … 511 Minimum cycle time 250 µs Topology Line and ring Communication phases NRT, CP0, CP1, CP2, CP3, CP4 Baud rate 100 MBit/s Data transport layer Ethernet II, IEEE 802.3 Supported Sercos version Sercos in the third generation Communication Specification Version 1.3.0 Supported Sercos Communication Profiles SCP_FixCFG Version 1.1.1 SCP_VarCFG Version 1.1.1 SCP_VarCFG Version 1.1.3 Supported FSP profiles FSP_IO SCP_NRTPC support S/IP support Identification LED feature supported Limitations Max. 2 connections: 1 for consumer and 1 for producer No acyclic user data transfer Modifications of the ServiceChannel Object Dictionary will be volatile after reset, if it resides on device Hot plug is not supported Cross communication not supported NRT Channel only forwarding and S/IP Reference to stack version V3.3.x.x Table 51: Technical data Sercos slave protocol netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... -
Page 77: Decommissioning/Disposal
Decommissioning/Disposal 77/81 13 Decommissioning/Disposal 13.1 Putting the device out of operation Danger of Unsafe System Operation ! To prevent personal injury or property damage, make sure that the removal of the device from your plant during operation will not affect the safe operation of the plant. Ø Disconnect all communication cables from the device. Ø Disconnect the power supply plug. Ø Remove the device from the DIN rail as described in section Removing device from Top Hat Rail [} page 33]. 13.2 Disposal of waste electronic equipment Important notes from the European Directive 2012/19/EU “Waste Electrical and Electronic Equipment (WEEE)” Waste electronic equipment This product must not be treated as household waste. This product must be disposed of at a designated waste electronic equipment collecting point. Waste electronic equipment may not be disposed of as household waste. As a consumer, you are legally obliged to dispose of all waste electronic equipment according to national and local regulations. netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public... - Page 78 Login SYCON.net ....................48 Figure 22: Empty project in SYCON.net ................48 Figure 23: SYCON.net_SD_Karte1 ..................49 Figure 24: Device assignment 1 .................... 50 Figure 25: Device assignment 2 .................... 51 Figure 26: Device assignment 3 .................... 51 Figure 27: Memory Card Management of the netTAP DTM ..........52 Figure 28: Insert SD card....................... 52 Figure 29: Memory Card Management after inserting SD memory card ....... 53 Figure 30: Memory Card Management after backup to SD memory card ......54 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public...
- Page 79 LED states for the EtherCAT Master(V3) protocol ..........59 Table 31: LED state definitions for the EtherCAT Master(V3) protocol........59 Table 32: LED states for the EtherCAT Slave protocol ............60 Table 33: LED state definitions for the EtherCAT Slave protocol..........60 Table 34: LED states for the EtherNet/IP Scanner protocol............ 61 Table 35: LED state definitions for the EtherNet/IP Scanner protocol ........61 Table 36: LED states for the EtherNet/IP Adapter protocol............. 62 Table 37: LED state definitions for the EtherNet/IP Adapter protocol ........62 Table 38: LED states for the Sercos Master protocol.............. 63 Table 39: LED state definitions for the Sercos Master protocol ..........64 Table 40: LED states for the Sercos Slave protocol..............65 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public...
- Page 80 LED state definitions for the Sercos Slave protocol ..........66 Table 42: netTAP NT 151RERE troubleshooting by LED............. 67 Table 43: Technical data netTAP NT 151RERE..............68 Table 44: Technical data PROFINET IO Controller protocol........... 70 Table 45: Technical data PROFINET IO RT IRT Device Protocol .......... 71 Table 46: Technical data EtherNet/IP Scanner (Master) protocol........... 73 Table 47: Technical data EtherNet/IP Adapter (slave) protocol ..........74 Table 48: Technical data EtherCAT Master protocol .............. 74 Table 49: Technical data EtherCAT slave protocol ..............75 Table 50: Technical daten sercos master protocol..............75 Table 51: Technical data Sercos slave protocol..............76 netTAP NT 151RERE | RealTime Ethernet gateway © Hilscher 2016 DOC150802UM01EN | Revision 1 | English | 201607 | Released | Public...
-
Page 81: Contacts
Contacts 81/81 Contacts HEADQUARTERS Germany Hilscher Gesellschaft für Systemautomation mbH Rheinstrasse 15 D65795 Hattersheim Phone: +49 (0) 6190 99070 Fax: +49 (0) 6190 990750 EMail: info@hilscher.com Support Phone: +49 (0) 6190 990799 EMail: de.support@hilscher.com SUBSIDIARIES China Japan Hilscher Systemautomation (Shanghai) Co. Ltd. Hilscher Japan KK 200010 Shanghai Tokyo, 1600022 Phone: +86 (0) 2163555161 Phone: +81 (0) 353620521 EMail: info@hilscher.cn EMail: info@hilscher.jp Support Support Phone: +86 (0) 2163555161 Phone: +81 (0) 353620521 EMail: cn.support@hilscher.com EMail: jp.support@hilscher.com France Korea Hilscher France S.a.r.l. Hilscher Korea Inc. 69500 Bron Seongnam, Gyeonggi, 463400 Phone: +33 (0) 4 72 37 98 40 Phone: +82 (0) 317893715 EMail: info@hilscher.fr...