netHOST NHST-T100 - LAN controlled master devices UM 04 EN · T100EN/PNM/ECM/EIM devices, but firmware has to be loaded into the device by the customer) This document also features

User Manual

netHOST NHSTT100LAN controlled master devices for Fieldbus and Real

Time Ethernet Systems

Hilscher Gesellschaft für Systemautomation mbHwww.hilscher.com

DOC130401UM04EN | Revision 4 | English | 201507 | Released | Public

Table of contents 2/72

Table of contents1 Introduction............................................................................................................................... 51.1 About this document......................................................................................................... 5

1.1.1 Description of the contents ................................................................................ 51.1.2 Obligation to read the manual ........................................................................... 61.1.3 List of revisions ................................................................................................. 61.1.4 Conventions in this document ........................................................................... 71.1.5 Reference to hardware, firmware, software and drivers.................................... 8

1.2 Contents of the product DVD ......................................................................................... 101.3 Documentation overview ................................................................................................ 121.4 Legal notes..................................................................................................................... 16

1.4.1 Copyright ......................................................................................................... 161.4.2 Important notes................................................................................................ 161.4.3 Exclusion of liability ......................................................................................... 171.4.4 Warranty .......................................................................................................... 171.4.5 Export regulations............................................................................................ 181.4.6 Registered Trademarks ................................................................................... 18

2 Safety....................................................................................................................................... 192.1 General note................................................................................................................... 192.2 Intended use................................................................................................................... 192.3 Personnel qualification ................................................................................................... 192.4 References safety .......................................................................................................... 192.5 Safety instructions to avoid personal injury .................................................................... 20

2.5.1 Danger of unsafe system operation................................................................. 202.6 Safety instructions to avoid property damage ................................................................ 20

2.6.1 Device destruction by exceeding allowed supply voltage................................ 202.6.2 Danger of unsafe system operation................................................................. 20

2.7 Labeling of safety messages.......................................................................................... 21

3 Description.............................................................................................................................. 223.1 Functionality ................................................................................................................... 223.2 Device types................................................................................................................... 243.3 Interfaces........................................................................................................................ 25

4 Requirements.......................................................................................................................... 27

5 Device drawings and connectors ......................................................................................... 295.1 Dimensioned drawings ................................................................................................... 295.2 Positions of the LEDs, connectors and control elements ............................................... 30

5.2.1 netHOST for Fieldbus systems........................................................................ 305.2.2 netHOST for RealTime Ethernet systems ...................................................... 31

5.3 Protocol logo and LED label sticker ............................................................................... 325.4 Device label .................................................................................................................... 325.5 Power supply connector (X1) ......................................................................................... 325.6 Ethernet connectors ....................................................................................................... 335.7 Fieldbus interfaces (X3) ................................................................................................. 34

5.7.1 PROFIBUS DP interface (NHSTT100DP/DPM)............................................ 34

netHOST NHSTT100 | LAN controlled master devicesDOC130401UM04EN | Revision 4 | English | 201507 | Released | Public

© Hilscher 2013 – 2015


5.7.2 CANopen interface (NHSTT100CO/COM).................................................... 345.7.3 DeviceNet interface (NHSTT100DN/DNM) ................................................... 35

5.8 USB interface (MiniB USB) ........................................................................................... 355.9 Schematic diagram of Galvanic isolation ....................................................................... 35

5.9.1 netHOST for Fieldbus systems........................................................................ 365.9.2 netHOST for RTE systems .............................................................................. 37

6 Mounting and dismounting of netHOST device................................................................... 386.1 Safety messages............................................................................................................ 386.2 Mounting netHOST device onto Top Hat Rail ................................................................ 396.3 Removing netHOST device from the Top Hat Rail......................................................... 40

7 Commissioning....................................................................................................................... 417.1 Firmware ........................................................................................................................ 417.2 Configuring the netHOST ............................................................................................... 417.3 Startup behavior ............................................................................................................ 43

7.3.1 Startup without SD memory card ................................................................... 437.3.2 Startup with inserted SD memory card........................................................... 43

8 Firmware recovery.................................................................................................................. 448.1 Overview ........................................................................................................................ 448.2 Using an SD memory card to reset the netHOST to its “factory settings” ...................... 448.3 Using USB to recover firmware ...................................................................................... 46

9 Troubleshooting ..................................................................................................................... 50

10 LEDs ........................................................................................................................................ 5110.1 SYS LED ........................................................................................................................ 5110.2 APL LED......................................................................................................................... 5210.3 LEDs of the Fieldbus and RealTime Ethernet systems................................................. 53

10.3.1 LED PROFIBUS DP Master (NHSTT100DP/DPM) ...................................... 5310.3.2 LED CANopen Master (NHSTT100CO/COM) .............................................. 5410.3.3 LED DeviceNet Master (NHSTT100DN/DNM).............................................. 5510.3.4 LEDs PROFINET IO Controller ...................................................................... 5610.3.5 LEDs EtherCAT Master ................................................................................... 5710.3.6 LEDs EtherNet/IP Scanner.............................................................................. 58

11 Technical data......................................................................................................................... 5911.1 Technical data of the netHOST devices......................................................................... 59

11.1.1 netHOST for Fieldbus systems........................................................................ 5911.1.2 netHOST for RealTime Ethernet systems ...................................................... 61

11.2 Technical data of the protocols ...................................................................................... 6211.2.1 PROFIBUS DP Master (NHSTT100DP/DPM) .............................................. 6211.2.2 CANopen Master (NHSTT100CO/COM) ...................................................... 6311.2.3 DeviceNet Master (NHSTT100DN/DNM)...................................................... 6411.2.4 PROFINET IO Controller ................................................................................. 6511.2.5 EtherCAT Master............................................................................................. 6611.2.6 EtherNet/IP Scanner........................................................................................ 67

12 Decommissioning/Disposal................................................................................................... 6812.1 Putting the device out of operation................................................................................. 6812.2 Disposal of waste electronic equipment ......................................................................... 68


© Hilscher 2013 – 2015


List of figures.......................................................................................................................... 69

List of tables ........................................................................................................................... 70

Contacts .................................................................................................................................. 72


© Hilscher 2013 – 2015

Introduction 5/72

1 Introduction

1.1 About this document

1.1.1 Description of the contentsThis user manual describes hardware, installation and commissioning ofthe LAN controlled Hilscher netHOST master devices for fieldbus and RealTime Ethernet networks:

NHSTT100DP/DPM for PROFIBUS DP (order no.: 1890.410/DPM)

NHSTT100CO/COM for CANopen (order no.: 1890.500/COM)

NHSTT100DN/DNM for DeviceNet (order no.: 1890.510/DNM)

NHSTT100EN/PNM for PROFINET IO (order no.: 1890.840/PNM)

NHSTT100EN/ECM for EtherCAT (order no.: 1890.110/ECM)

NHSTT100EN/EIM for EtherNet/IP (order no.: 1890.820/EIM)

NHSTT100EN for PROFINET IO, EtherCAT or EtherNet/IP (order no.: 1890.800, hardware and performance are identical to the NHSTT100EN/PNM/ECM/EIM devices, but firmware has to be loaded into thedevice by the customer)

This document also features the technical data of the devices and of thesupported network protocols. Instructions for resetting a netHOST device toits “factory settings” (firmware recovery) are also provided here. The installation of the configuration software and the configuration of thenetHOST devices are not subject of this document.The installation of the software is described in the user manual SoftwareInstallation netHOST Devices. Instructions on how to configure, diagnoseor test a netHOST device, or how update its firmware are provided in theoperating instruction manual Configuration of LAN controlled masterdevices – netHOST.All devices are delivered with their firmware already installed, except for theNHSTT100EN netHOST device. If you are using the NHSTT100EN, youwill find instructions on how to install the firmware in the operatinginstruction manual Configuration of LAN controlled master devices –netHOST.

See also section Documentation overview [ page 12].


© Hilscher 2013 – 2015

Introduction 6/72

1.1.2 Obligation to read the manual

Important:Ø To avoid personal injury or property damage to your system orto your device, you must read and understand all instructions inthis manual and in the documents accompanying your devicebefore installing and operating your device.

Ø First read the Safety Instructions in the chapter Safety [ page 19].

Ø Observe all Safety Messages in this manual.Ø Keep the product DVD providing the product manuals.

1.1.3 List of revisionsIndex Date Revision1 20130805 Created2 20141205 Devices for RealTime Ethernet added, document completely revised.

Subtitle of document changed from “Remote Fieldbus Device for FieldInstallation“ to „LAN controlled master devices for Fieldbus and RealTime Ethernet networks“.

3 20150710 Device NHSTT100EN for loadable firmware added.4 20150722 Firmware version in section Hardware and firmware [ page 8]

updated to version ≥ 1.7Section LEDs of the Fieldbus and RealTime Ethernet systems [ page 53] updated.Layout of document updated.Layout of safety messages updated.

Table 1: List of revisions


© Hilscher 2013 – 2015

Introduction 7/72

1.1.4 Conventions in this documentNotes, operation instructions and results of operation steps are marked asfollows:

Notes

Note:<important note>

Note:<simple note>

<note, where to find further information>

Operation instructions

1. <operational step>Ø <instruction>

2. <operational step>Ø <instruction>

Results

<intermediate result>

<final result>

For a description of the labeling of Safety Messages, see section Labelingof safety messages [ page 21].


© Hilscher 2013 – 2015

Introduction 8/72

1.1.5 Reference to hardware, firmware, software and drivers

1.1.5.1 Hardware and firmware

This document relates to the following versions of hardware and firmware:

Devices with preloaded firmwarenetHOST devicepreloaded withfirmware

Order no. Hardwarerevision

Protocol Firmware file Firmware(startingfrom thisversion andhigher)

NHSTT100DP/DPM 1890.410/DPM 4 PROFIBUS DP Master FT20V010.NXF 1.7.x.xNHSTT100CO/COM 1890.500/COM 4 CANopen Master FT20V040.NXF 1.7.x.xNHSTT100DN/DNM 1890.510/DNM 4 DeviceNet Master FT20V060.NXF 1.7.x.xNHSTT100EN/PNM 1890.840/PNM 2 PROFINET IO Controller FT20C0V0.NXF 1.7.x.xNHSTT100EN/ECM 1890.110/ECM 2 EtherCAT Master FT20E0V0.NXF 1.7.x.xNHSTT100EN/EIM 1890.820/EIM 2 EtherNet/IP Scanner FT20G0V0.NXF 1.7.x.x

Table 2: Reference to devices with preloaded firmware

Device for loadable firmware

(Firmware not loaded in state of delivery of device):netHOST device forloadable firmware

Order no. Hardwarerevision

Supported protocols Loadablefirmware file

Firmware(startingfrom thisversion andhigher)

NHSTT100EN 1890.800 2 PROFINET IO Controller FT20C0V0.NXF 1.7.x.xEtherCAT Master FT20E0V0.NXF 1.7.x.xEtherNet/IP Scanner FT20G0V0.NXF 1.7.x.x

Table 3: Reference to devices for loadable firmware

Note:For acting as master device, the NHSTT100EN requires theNXLICMaster license (order no.: 8211.000). Make sure to orderthe NHSTT100EN device together with the master license, so thatit can be delivered with the license already loaded. If necessary, a master license can also be ordered and installedbelatedly; instructions for this are provided in the operatinginstruction manual Configuration of LAN controlled master devices –netHOST.


© Hilscher 2013 – 2015

Introduction 9/72

1.1.5.2 Software

This document relates to the following software versions:Software Version File name Path on netHOST Solutions DVDSYCON.net 1.380.x.x SYCONnet netX setup.exe Setups & Drivers\SYCON.netEthernet DeviceConfiguration Tool

1.501.x.x EnDevConfigTool.msi Setups & Drivers\Ethernet Device Setup Utility

netHOST DeviceTest Application

1.0.x.x netHOST.exe Setups & Drivers\netHOST Test

ComProX 0.9.x.x comproX.exe Supplements & Examples\netHOST DeviceRecovery\Recovery via USB

Table 4: Reference to software

1.1.5.3 Drivers

This document relates to the following driver versions:Driver Version File name Path on netHOST Solutions DVDInstallation program forWindows USB drivers, contains:

setup.exe Setups & Drivers\USB Driver

· Windows Driver Packagehilusbser

6.0.x.x

· Windows Driver Packagehilusbser

6.0.x.x

Table 5: Reference to drivers


© Hilscher 2013 – 2015

Introduction 10/72

1.2 Contents of the product DVDThe netHOST Solutions product DVD contains:· PDF documentation for users and developers· SYCON.net configuration and diagnostic program for Windows· Ethernet Device Configuration Tool for Windows· netHOST Device Test Application for Windows· Communication DLLs for immediate usage in customerengineeredWindows applications

· source code of the DLLs· XML templates and examples for configuring the netHOST devicewithout SYCON.net

· Converter DLL for converting XML text files into netHOSTreadableNXD binary files

· CToolkit (source code for developers of NonWindows target platformsand embedded systems)

· USB drivers for Windows (only needed for resetting the device to itsfactory settings)

· Firmware:If you are using devices with preloaded firmware, these firmware filesare needed only for resetting the device to its factory settings or forfirmware recovery in case of a device defect.If you are using an NHSTT100EN device (netHOST for loadablefirmware), you have to load the corresponding firmware file of thedesired protocol into the device during commissioning with SYCON.net.

· Software for resetting the device to its factory settings and for loadingfirmware

· Videoaudio tutorials


© Hilscher 2013 – 2015

Introduction 11/72

Directory of the DVD:Folder ContentsDocumentation1. Software Software documentation for standard users (PDF)

Ethernet Device Setup UtilitySYCON.net

2. Hardware User Manual of the netHOST NHSTT100 device (PDF)3. For Programmers

0.Understanding the Remote AccessPrinciple

Documentation for developers (PDF)

1.Communication Interface DLL API2.CToolkit Programming ReferenceGuide3.Shared Memory Interface4.Communication Protocol specificAPIs5.Configuration without SYCON.net,XML file based

Documentation for developers (PDF) and XML files

6.Ethernet Device Scanning UDPProtocol

Documentation for developers (PDF)

7.Error Codes4. Installation Instructions Wiring and software installation instructions for standard users (PDF)

Firmware Loadable device firmwareNote: If you are using devices with preloaded firmware, these firmwarefiles are needed only for resetting the device to its factory settings orfor firmware recovery in case of a device defect.If you are using an NHSTT100EN device (netHOST for loadablefirmware), you have to load the corresponding firmware file of thedesired protocol into the device during commissioning withSYCON.net.

fscommand Files needed for displaying the installation menu of the netHOSTSolutions DVD

Programming & DevelopmentConfiguration without SYCON.net, XML filebased

XML files

Generic XML Configuration SchemaProtocol Specific XML TemplatesXML2NXD Converter DLL

Developing own remote accessingApplications

Header Files Header files for compilationnetXTransport Protocol CToolkit C source code of the netHOST transport protocol for target platform

adaptationnetXTransport Protocol DLL C++ source codes of the DLLs and the netHOST Device Test

Application for usage under Windows and precompiled Windows DLLsWireshark netXTransport ProtocolInterpreterDLL

DLL files for Wireshark

Setups & Drivers Installation programs for the SYCON.net configuration and diagnosticsoftware, for the netHOST Device Test Application, for the EthernetDevice Configuration Tool (Ethernet Device Setup Utility) and for theUSB drivers

Supplements & ExamplesnetHOST Device Recovery

Recovery via Memory Card Images for recovering the factory settings of the device by memorycard


© Hilscher 2013 – 2015

Introduction 12/72

Folder ContentsRecovery via USB Software for recovering the factory settings of the device via USB

netXTransport Protocol CToolkit Linux,Win32 Test Applications with SourceCode

netXTransport Protocol CToolkit Test Applications.sfx.exe

netXTransport Protocol DLL Win32 TestApplication with Source Code

netHOST test application for Windows

SYCON.net Sample Projects SYCON.net example projectsXML2NXD Converter Test Application(WPF) with Source Code

XML2NXD Converter Test Application.sfx.exe

Training & Podcasts Video presentations in avi formatTable 6: Directory of netHOST Solutions DVD

1.3 Documentation overviewThis section lists documents that are relevant to the user of the netHOSTdevice.

Basic documentsTitle Contents Document ID Path on the netHOST Solutions DVDUser ManualnetHOST NHSTT100 – LANcontrolled masterdevices for Fieldbusand RealTimeEthernet Systems(this document)

Installation,commissioning andhardware descriptionof the netHOSTdevices and othertechnical data

DOC130401UMxxEN Documentation\english\2.Hardware\netHOST,Model NHSTT100xx\netHOST NHSTT100 – LANcontrolled master devices UM xx EN.pdf

OperatingInstruction ManualConfiguration ofLAN controlledmaster devices –netHOST

Configuring, testing,diagnosing andupdating firmware ofthe netHOSTdevices

DOC130402OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Configuration of netHOSTDevices OI xx EN.pdf

User ManualSoftware InstallationnetHOST Devices

Instructions forinstalling thenetHOST software

DOC130501UMxxEN Documentation\english\4.Installation Instructions\netHOST Software Installation UM XX EN.pdf

OperatingInstruction ManualEthernet DeviceConfiguration

Instructions on howto assign an IPaddress to Hilscherdevices

DOC050402OIxxEN Documentation\english\1.Software\Ethernet DeviceSetup Utility \Ethernet Device Configuration OI XXEN.pdf

User Manual Wiring Instructions

Wiring instructions(cablecharacteristics) forfieldbus networks

DOC120208UMxxEN Documentation\english\4.Installation Instructions\Wiring Instructions UM XX EN.pdf

Table 7: Basic documentation for netHOST


© Hilscher 2013 – 2015

Introduction 13/72

netHOST as PROFIBUS DP Master

You also need the following documents if you are using an NHSTT100DP/DPM netHOST device:

Title Contents Document ID Path on the netHOST Solutions DVDOperatingInstruction ManualDTM for HilscherPROFIBUS DPMaster Devices

Description of thedevice type managerfor PROFIBUS DPmaster devices

DOC070401OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\PROFIBUS DP Master\PROFIBUS DP MasterDTM OI xx EN.pdf

OperatingInstruction ManualGeneric Slave DTMfor PROFIBUS DPSlave Devices

Description of thedevice type managerfor genericPROFIBUS DP slavedevices

DOC031001OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\PROFIBUS DP Master\Slave Configuration\PROFIBUS DP Generic Slave DTM OI xx EN.pdf

Table 8: Additional documentation for netHOST as PROFIBUS DP Master

netHOST as CANopen Master

You also need the following documents if you are using an NHSTT100CO/COM netHOST device:

Title Contents Document ID Path on the netHOST Solutions DVDOperatingInstruction ManualDTM for HilscherCANopen MasterDevices

Description of thedevice type managerfor CANopen masterdevices

DOC070402OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\CANopen Master\CANopen Master DTM OI xxEN.pdf

OperatingInstruction ManualGeneric Slave DTMfor CANopen SlaveDevices

Description of thedevice type managerfor generic CANopenslave devices

DOC060203OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\CANopen Master\Slave Configuration\CANopenGeneric Slave DTM OI xx EN.pdf

Table 9: Additional documentation for netHOST as CANopen Master

netHOST as DeviceNet Master

You also need the following documents, if you are using an NHSTT100DN/DNM netHOST device:

Title Contents Document ID Path on the netHOST Solutions DVDOperatingInstruction ManualDTM for HilscherDeviceNet MasterDevices

Description of thedevice type managerfor DeviceNet masterdevices

DOC070403OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\DeviceNet Master\DeviceNet Master DTM OI xxEN.pdf

OperatingInstruction ManualGeneric Slave DTMfor DeviceNet SlaveDevices

Description of thedevice type managerfor genericDeviceNet slavedevices

DOC041201OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\DeviceNet Master\Slave Configuration\DeviceNetGeneric Slave DTM OI xx EN.pdf

Table 10: Additional documentation for netHOST as DeviceNet Master


© Hilscher 2013 – 2015

Introduction 14/72

netHOST as PROFINET IO Controller

You also need the following documents if you are using an NHSTT100EN/PNM, respectively NHSTT100EN device with loaded PROFINET IOController firmware:

Title Contents Document ID Path on the netHOST Solutions DVDOperatingInstruction ManualDTM for HilscherPROFINET IOController Devices

Description of thedevice type managerfor PROFINET IOController devices

DOC060302OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\PROFINET IO Controller\PROFINET IO ControllerDTM OI xx EN.pdf

OperatingInstruction ManualGeneric DTM forPROFINET IODevices

Description of thedevice type managerfor genericPROFINET IOdevices

DOC060305OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\PROFINET IO Controller \IO Device Configuration\PROFINET IO Generic Device DTM OI xx EN.pdf

Table 11: Additional documentation for netHOST as PROFINET IO Controller

netHOST as EtherCAT Master

You also need the following documents if you are using an NHSTT100EN/ECM, respectively NHSTT100EN device with loaded EtherCAT Masterfirmware:

Title Contents Document ID Path on the netHOST Solutions DVDOperatingInstruction ManualDTM for HilscherEtherCAT MasterDevice

Description of thedevice type managerfor EtherCAT Masterdevices

DOC080404OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\EtherCAT Master\EtherCAT Master DTM OI xxEN.pdf

OperatingInstruction ManualGeneric Slave DTMfor EtherCAT SlaveDevices

Description of thedevice type managerfor generic EtherCATslave devices

DOC071202OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\EtherCAT Master\Slave Configuration\EtherCATGeneric Slave DTM OI xx EN.pdf

User Manual Wiring InstructionsEtherCAT

Wiring instructionsfor EtherCATnetworks

DOC121104UMxxEN Documentation\english\4.Installation Instructions\Wiring Instructions UM xx EN.pdf

Table 12: Additional documentation for netHOST as EtherCAT Master


© Hilscher 2013 – 2015

Introduction 15/72

netHOST as EtherNet/IP Scanner

You also need the following documents if you are using an NHSTT100EN/EIM, respectively NHSTT100EN device with loaded EtherNet/IP Scannerfirmware:

Title Contents Document ID Path on the netHOST Solutions DVDOperatingInstruction ManualDTM for EtherNet/IPScanner Devices

Description of thedevice type managerfor EtherNet/IPScanner devices

DOC061201OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\EtherNetIP Scanner\EtherNetIP Scanner DTM OIxx EN.pdf

OperatingInstruction ManualGeneric, ModularGeneric DTM fromEDS File for nonmodular andmodular EtherNet/IPAdapter Devices

Description of thegeneric, modulargeneric device typemanager from EDSfile for nonmodularEtherNet/IP Adapterdevices and modularEtherNet/IP Adapterdevices

DOC100221OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\EtherNetIP Scanner\Adapter Configuration\EtherNetIP Generic Adapter DTM EDS OI xxEN.pdf

OperatingInstruction ManualGeneric DTM forEtherNet/IP AdapterDevices andModular GenericDTM for modularEtherNet/IP AdapterDevices

Description of thegeneric device typemanager forEtherNet/IP Adapterdevices and modularEtherNet/IP Adapterdevices

DOC070203OIxxEN Documentation\english\1.Software\SYCON.netConfiguration Software\Master Configuration\EtherNetIP Scanner\Adapter Configuration\EtherNetIP Generic Adapter DTM OI xx EN.pdf

Table 13: Additional documentation for netHOST as EtherNet/IP Scanner


© Hilscher 2013 – 2015

Introduction 16/72

1.4 Legal notes

1.4.1 Copyright© Hilscher 2013 – 2015, Hilscher Gesellschaft für Systemautomation mbH

All rights reserved.

The images, photographs and texts in the accompanying material (usermanual, accompanying texts, documentation, etc.) are protected byGerman and international copyright law as well as international trade andprotection provisions. You are not authorized to duplicate these in whole orin part using technical or mechanical methods (printing, photocopying orother methods), to manipulate or transfer using electronic systems withoutprior written consent. You are not permitted to make changes to copyrightnotices, markings, trademarks or ownership declarations. The includeddiagrams do not take the patent situation into account. The companynames and product descriptions included in this document may betrademarks or brands of the respective owners and may be trademarked orpatented. Any form of further use requires the explicit consent of therespective rights owner.

1.4.2 Important notesThe user manual, accompanying texts and the documentation were createdfor the use of the products by qualified experts, however, errors cannot beruled out. For this reason, no guarantee can be made and neither juristicresponsibility for erroneous information nor any liability can be assumed.Descriptions, accompanying texts and documentation included in the usermanual do not present a guarantee nor any information about proper useas stipulated in the contract or a warranted feature. It cannot be ruled outthat the user manual, the accompanying texts and the documentation donot correspond exactly to the described features, standards or other data ofthe delivered product. No warranty or guarantee regarding the correctnessor accuracy of the information is assumed.

We reserve the right to change our products and their specification as wellas related user manuals, accompanying texts and documentation at alltimes and without advance notice, without obligation to report the change.Changes will be included in future manuals and do not constitute anyobligations. 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 anycircumstances for direct, indirect, incidental or followon damage or loss ofearnings resulting from the use of the information contained in thispublication.


© Hilscher 2013 – 2015

Introduction 17/72

1.4.3 Exclusion of liabilityThe software was produced and tested with utmost care by HilscherGesellschaft für Systemautomation mbH and is made available as is. Nowarranty can be assumed for the performance and flawlessness of thesoftware for all usage conditions and cases and for the results producedwhen utilized by the user. Liability for any damages that may result from theuse of the hardware or software or related documents, is limited to cases ofintent or grossly negligent violation of significant contractual obligations.Indemnity claims for the violation of significant contractual obligations arelimited 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 nuclearfacilities;

· in air traffic control systems, air traffic or air traffic communicationsystems;

· in life support systems;· in systems in which failures in the software could lead to personal injuryor injuries leading to death.

We inform you that the software was not developed for use in dangerousenvironments requiring failproof control mechanisms. Use of the softwarein such an environment occurs at your own risk. No liability is assumed fordamages or losses due to unauthorized use.

1.4.4 WarrantyAlthough the hardware and software was developed with utmost care andtested intensively, Hilscher Gesellschaft für Systemautomation mbH doesnot guarantee its suitability for any purpose not confirmed in writing. Itcannot be guaranteed that the hardware and software will meet yourrequirements, that the use of the software operates without interruption andthat the software is free of errors. No guarantee is made regardinginfringements, violations of patents, rights of ownership or the freedom frominterference by third parties. No additional guarantees or assurances aremade regarding marketability, freedom of defect of title, integration orusability for certain purposes unless they are required in accordance withthe law and cannot be limited. Warranty claims are limited to the right toclaim rectification.


© Hilscher 2013 – 2015

Introduction 18/72

1.4.5 Export regulationsThe delivered product (including the technical data) is subject to export orimport laws as well as the associated regulations of different counters, inparticular those of Germany and the USA. The software may not beexported to countries where this is prohibited by the United States ExportAdministration Act and its additional provisions. You are obligated tocomply with the regulations at your personal responsibility. We wish toinform you that you may require permission from state authorities to export,reexport or import the product.

1.4.6 Registered TrademarksAdobe Reader® is a registered trademark of the Adobe SystemsIncorporated.

CANopen® is a registered trademark of CAN in AUTOMATION International Users and Manufacturers Group e.V (CiA), Nürnberg.

DeviceNet™ and EtherNet/IP™ are trademarks of ODVA (Open DeviceNetVendor Association, Inc).

EtherCAT® is a registered trademark and a patented technology ofBeckhoff Automation GmbH, Verl, Federal Republic of Germany, formerlyElektro Beckhoff GmbH.

PROFIBUS® and PROFINET® are registered trademarks of PROFIBUS &PROFINET International (PI), Karlsruhe.

Windows® XP, Windows® Vista, Windows® 7 and Windows® 8 areregistered trademarks of Microsoft Corporation.

All other mentioned trademarks are property of their respective legalowners.


© Hilscher 2013 – 2015

Safety 19/72

2 Safety

2.1 General noteThe user manual, the accompanying texts and the documentation arewritten for the use of the products by educated personnel. When using theproducts, all safety instructions and all valid legal regulations have to beobeyed. Technical knowledge is presumed. The user has to assure that alllegal regulations are obeyed.

2.2 Intended useThe netHOST devices described in this manual are communication deviceswhich connect a TCP/IP network to a fieldbus or RealTime Ethernetnetwork. The netHOST devices thus serve as “gateways” between the twonetworks.

The netHOST devices are in a compact housing and suitable for DIN railmounting according to DIN EN 60715.

2.3 Personnel qualificationThe netHOST devices must only be installed, configured and removed byqualified personnel. Jobspecific technical skills for people professionallyworking with electricity must be present concerning the following topics:· Safety and health at work· Mounting and attaching of electrical equipment· Measurement and analysis of electrical functions and systems· Evaluation of the safety of electrical systems and equipment· Installing and configuring IT

2.4 References safety[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


© Hilscher 2013 – 2015

Safety 20/72

2.5 Safety instructions to avoid personal injuryTo ensure your own personal safety and to avoid personal injury, you mustread, understand and follow the safety instructions and all safety messagesin this manual about danger that might cause personal injury, before youinstall and operate your netHOST device.

2.5.1 Danger of unsafe system operationTo prevent personal injury, make sure that the removal of the device fromyour plant during operation will not affect the safe operation of the plant.

2.6 Safety instructions to avoid property damageTo avoid property damage to your system or to the netHOST device, youmust read, understand and follow the safety instructions and all safetymessages in this manual about danger that might cause property damage,before you install and operate your netHOST device.

2.6.1 Device destruction by exceeding allowed supply voltageObserve the following notes concerning the supply voltage:· The netHOST may only be operated with the specified supply voltage.Make sure that the limits of the allowed range for the supply voltage arenot exceeded.

· A supply voltage above the upper limit can cause severe damage to thenetHOST!

· A supply voltage below the lower limit can cause malfunction of thenetHOST.

The allowed range for the supply voltage is specified in the sectionTechnical data of the netHOST devices [ page 59].

2.6.2 Danger of unsafe system operationTo prevent property damage, make sure that the removal of the devicefrom your plant during operation will not affect safe operation of the plant.


© Hilscher 2013 – 2015

Safety 21/72

2.7 Labeling of safety messagesIn this document the safety instructions and property damage messagesare designed according both to the internationally used safety conventionsas well as to the ANSI Z535 standard.· The Section Safety Messages at the beginning of a chapter arepinpointed particularly and highlighted by a signal word according to thedegree of endangerment. The kind of danger is specified exactly by thesafety message text and optionally by a specific safety sign.

· The Integrated Safety Messages embedded in operating instructionsare highlighted by a signal word according to the degree ofendangerment. In the safety message, the nature of the hazard isindicated.

Signal words and safety signs in safety messages on personal injury

Signal word MeaningIndicates a direct hazard with high risk, which will have as consequencedeath or grievous bodily harm if it is not avoided.Indicates a possible hazard with medium risk, which will have asconsequence death or (grievous) bodily harm if it is not avoided.Indicates a minor hazard with medium risk, which could have asconsequence personal injury if it is not avoided.

Table 14: Signal words in safety messages on personal injury

Safety sign Sort of warning or principleWarning 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 propertydamage

Signal word MeaningIndicates a property damage message

Table 16: Signal words in safety messages on property damage

Safety sign Sort of warning or principleWarning of property damage by electrostatic discharge

Table 17: Safety signs in safety messages on property damage


© Hilscher 2013 – 2015

Description 22/72

3 Description

3.1 FunctionalityThe Hilscher netHOST is a communication device that connects a TCP/IPnetwork to a fieldbus or RealTime Ethernet (RTE) network. The netHOSTdevice has a compact housing and is suited for DIN rail mounting accordingto DIN EN 60715.

The netHOST device allows you to access data of a fieldbus or RealTimeEthernet network from your PC, terminal or other host system via TCP/IP.Thus, the device serves as a gateway, respectively programming interfacebetween your PC/terminal/host system and the fieldbus or RTE network.Once configured, the netHOST device controls the secondary network onits own.An appropriate application program establishes the TCP/IP connection tothe device and accesses the data of the fieldbus/RTE network. Access to the netHOST device takes place according to the “EthernetMarshalling” procedures, by which locally generated service requests of aninitiator (i. e. the host application) are being transmitted to a receiver (i. e.the netHOST device) by an appropriate method (i. e. coded/decoded inEthernet telegrams). The service requests are then called and executed“remotely” on the netHOST device.

The host system can be based on a Windows operating system, but is,however, not restricted to Windows only. For Windows developers, thenetHOST Solutions DVD provides the code with the Ethernet Marshallingfunction both as C++ source code and as Windows DLL(netXTransport.dll). For developers of embedded systems, the DVDprovides a C source code which is independent from any specific type ofoperating system.

Important:The Ethernet LAN connection to the netHOST device is notprotected by password or encryption. Protection againstunauthorized access by external networks has to be ensured byusing adequate measures !


© Hilscher 2013 – 2015

Description 23/72

The following figure illustrates the data flow of “Ethernet Marshalling” withthe netHOST:

Figure 1: Data flow of LAN controlled netHOST device


© Hilscher 2013 – 2015

Description 24/72

3.2 Device types

Devices with preloaded firmware

LAN controlled netHOSTs are currently available as master devices forthe following protocols:· PROFIBUS DP (NHSTT100DP/DPM),· CANopen (NHSTT100CO/COM),· DeviceNet (NHSTT100DN/DNM),· PROFINET IO (NHSTT100EN/PNM),· EtherCAT (NHSTT100EN/ECM),· EtherNet/IP (NHSTT100EN/EIM)

netHOSTs acting as slave devices in the secondary network are not yetavailable. All devices listed above are delivered with their firmware and masterlicense already loaded.

Device for loadable firmware

To allow users of RealTime Ethernet system more flexibility, Hilscher alsooffers the device· NHSTT100EN

which has the same hardware and performance as the other netHOSTdevices for RealTime Ethernet listed above (NHSTT100EN/PNM/ECMEIM), but it is not delivered with preloaded firmware. For this device,the product DVD provides firmware files for the· PROFINET IO Controller,· EtherCAT Master and· EtherNet/IP Scanner

protocols, which can be chosen and downloaded to the NHSTT100EN bythe user himself, the device supporting each of these three protocols. Toact as a master, the NHSTT100EN also needs the NXLICMaster license.If you order the NHSTT100EN together with the NXLICMaster license(order no. 8211.000), the device will be delivered with an already installedand activated master license – you will thus only have to download thechosen firmware file.

A belated ordering and downloading of a master license after devicedelivery is also possible, information on this can be found in the operatinginstruction manual Configuration of LAN controlled master devices –netHOST.


© Hilscher 2013 – 2015

Description 25/72

3.3 InterfacesAll interfaces are easily accessible at the front of the netHOST device. Inaddition to the necessary network interfaces, every device is also equippedwith a USB interface (protected by a cover) and an SD memory card slot.The USB and SD memory card interfaces can be used to perform afirmware recovery or to reset the device to its “factory settings” (see chapterFirmwareRecovery [ page 44]).

netHOST for Fieldbus systems

The netHOST devices NHSTT100DP/DPM, NHSTT100CO/COM andNHSTT100DN/DNM are equipped with two RJ45 sockets on the left side (X2), in order to connect the device to the LAN network by which thenetHOST is controlled/marshalled. The interface for the Fieldbus (i. e. thesecondary network), which is to be controlled by the netHOST, is locatedon the right side of the device (X3) and consists of a PROFIBUS DP,CANopen or DeviceNet interface and the appropriate fieldbus connectorhardware (according to the device type).

The following figure shows the NHSTT100DP/DPM netHOST device:

Figure 2: netHOST for Fieldbus: NHSTT100DP/DPM (example)


© Hilscher 2013 – 2015

Description 26/72

netHOST for RealTime Ethernet systems

The netHOST devices NHSTT100EN, NHSTT100EN/PNM, NHSTT100EN/ECM and NHSTT100EN/EIM are equipped with three RJ45sockets. The two RJ45 sockets for the RealTime Ethernet system, which isto be controlled by the netHOST, are located on the left side of the device (X2). A single RJ45 socket for the LAN network, by which the netHOST iscontrolled/marshalled, is located on the right side of the device (X3).

Figure 3: netHOST for RTE systems


© Hilscher 2013 – 2015

Requirements 27/72

4 RequirementsTechnical requirements· The netHOST device is to be mounted on a DIN rail according to DINEN 60715.

· A suitable external 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 130 mA at24 V.

· Power supply is to be connected at the X1 connector located on theupper side of the device (see section Positions of the LEDs, connectorsand control elements [ page 30]).

Device Destruction by Exceeding Allowed Supply Voltage!The voltage must not exceed 30 V, otherwise the device may be destroyedor damaged.

In order to avoid damage caused by overheating or freezing, it is necessarythat the temperature of the device does not exceed the limits of the allowedtemperature range. For the allowed temperature, see section Technicaldata of the netHOST devices [ page 59].

General requirements

Additionally, the following preconditions must be met in order to operate thenetHOST device successfully:· If you are using an NHSTT100EN netHOST device (order no.1890.800) you must download the firmware to the device beforecommissioning/configuring the netHOST.

· An IP address must be assigned to the netHOST device (by default/factory setting, the IP address of the netHOST is 0.0.0.0).

· The netHOST device must be properly configured with the SYCON.netconfiguration software. The configuration needs to be downloaded tothe device. As an alternative, the netHOST can also be configured bythe accessing host system.

For detailed information on how download firmware to the NHSTT100EN device and how to configure all netHOST devices withSYCON.net, see Operating Instruction Manual Configuration of LANcontrolled master devices – netHOST, DOC130402OIxxEN, storedon the netHOST Solutions DVD in the Documentation\english\1.Software\SYCON.net directory.


© Hilscher 2013 – 2015

Requirements 28/72

Requirements for using the SYCON.net configuration software

For installing and operating the SYCON.net configuration software, youneed the following:· PC with 1 GHz processor or higher· Windows® XP SP3, Windows® Vista (32 bit) SP2, Windows® 7 (32 bit)SP1, Windows® 7 (64 bit) SP1, Windows® 8 (32 bit) or Windows® 8 (64bit)

· 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· Ethernet interface

Note:If the project file is saved and opened again or it is used on anotherPC, the system requirements need to match. Particularly the DTMsneed to be installed on the used PC.

Restrictions

Touch screen is not supported.


© Hilscher 2013 – 2015

Device drawings and connectors 29/72

5 Device drawings and connectors

5.1 Dimensioned drawingsThe outer dimensions are identical for all types of netHOST devices.

Side view: Front view::

Power supply plug:

Table 18: Dimensioned drawing, example NHSTT100DP

Important:When planning the installation of the netHOST device, take intoaccount that there must be enough head room above the device toallow for convenient plugging and unplugging of the power supply.


© Hilscher 2013 – 2015


5.2 Positions of the LEDs, connectors and control elements

5.2.1 netHOST for Fieldbus systemsThe following figure depicts LEDs, connectors and control elements of thenetHOST for Fieldbus systems. The left part of each netHOST is identicalfor all device types, the right part differs according to fieldbus type.

NHSTT100DP

(1) Connector for supply voltage (X1)(2) Slot for SD memory card

(part number 1719.003)

(3) Address switch (factor 10), can be monitored inthe system information block.

(4) Address switch (factor 1), can be monitored inthe system information block.

(5) SYS LED (system status)

(6) APL LED (application status)

(7) Mini USB service interface (protected by a cover)

(8) LINK LED for LAN channel 0

(9) LAN interface channel 0 (X2, RJ45 socket)

(10) ACT LED for LAN channel 0 (activity)

(11) LINK LED for LAN channel 1

(12) LAN interface channel 1 (X2, RJ45 socket)

(13) ACT LED for LAN channel 1 (activity)

(14) LED communication status of fieldbusPROFIBUS DP Master (NHSTT100DP): COMCANopen Master (NHSTT100CO): CANDeviceNet Master (NHSTT100DN): MNS

(15) Fieldbus interface (X3)PROFIBUS DP Master (NHSTT100DP): Dsub 9pole femaleCANopen Master (NHSTT100CO): Dsub 9pole maleDeviceNet Master (NHSTT100DN): COMBICON 5pole

Table 19: LEDs, connectors and operating elements of netHOST for Fieldbus systems


© Hilscher 2013 – 2015


5.2.2 netHOST for RealTime Ethernet systemsThe following figure depicts LEDs, connectors and control elements of thenetHOST for RealTime Ethernet systems.

NHSTT100EN

(1) Connector for supply voltage (X1)(2) Slot for SD memory card

(part number 1719.003)(3) Push button without function(4) SYS LED (system status)(5) APL LED (application status)(6) Mini USB service interface

(protected by a cover)(7) Protocol specific LED

for PROFINET IO Controller: SFfor EtherCAT Master: RUNfor EtherNet/IP Scanner: MS

(8) Protocol specific LEDfor PROFINET IO Controller: BFfor EtherCAT Master: ERRfor EtherNet/IP Scanner: NS

(9) LINK LED for RealTime Ethernet channel 0

(10) RealTime Ethernet interface channel 0 (X2, RJ45 socket)

(11) ACT LED for RealTime Ethernet channel 0 (activity)

(12) LINK LED for RealTime Ethernet channel 1

(13) RealTime Ethernet interface channel 1 (X2, RJ45 socket)

(14) ACT LED for RealTime Ethernet channel 1 (activity)

(15) LINK LED for LAN interface(16) LAN interface (X3, RJ45 socket)(17) ACT LED for LAN interface (activity)

Table 20: LEDs, connectors and operating elements of netHOST for RTE systems


© Hilscher 2013 – 2015


5.3 Protocol logo and LED label stickerEach netHOST with preloaded firmware is delivered with the appropriateprotocol logo and LED labels already attached to the device. In case of theNHSTT100EN device (for which the appropriate firmware has to beloaded into the device by the customer) label stickers for the supportedmaster protocols for PROFINET IO, EtherCAT and EtherNet/IP areincluded in the delivery package, and can be attached to the device by thecustomer:

PROFINET IO EtherCAT EtherNet/IP

Table 21: Sticker for NHSTT100EN

5.4 Device label(1) Technical data(2) Device type name

(3) Part number

(4) Hardware revision number

(5) Serial number

Table 22: Device label (NHSTT100DP example)

5.5 Power supply connector (X1)For identification, see position (1) in section Positions of the LEDs,connectors and control elements [ page 30].

The power supply of the netHOST has to be connected to connector X1.The power supply voltage must be in the range between 18 V and 30 V DC.Supply voltage Pin Signal Description

Mini Combicon

1 0 V / GND Ground of supply voltage2 24 V +24 V supply voltage

Table 23: Pin assignment Mini Combicon socket 2pole

Note:The power supply plug is included in the delivery. If needed as aspare part, the plug can be obtained from RIA CONNECT GmbH inBlumberg, Germany, part number: 31369102001792.


© Hilscher 2013 – 2015


5.6 Ethernet connectorsThis section describes the technical details of the LAN and RealTimeEthernet connectors of the netHOST devices. The details are valid for theLAN interface featured by all netHOST types and for the RTE interfacefeatured only by the netHOST devices for RealTime Ethernet systems.

For identification of the LAN connector of the netHOST for Fieldbussystems, see positions (9) and (12) in section netHOST for Fieldbussystems [ page 30].

For identification of the LAN connector of the netHOST for RealTimeEthernet systems, see position (16), for identification of the RTEconnectors, see positions (10) and (13) in section netHOST for RealTimeEthernet systems [ page 31].

The Ethernet interfaces (LAN and RTE) use RJ45 sockets, with twisted paircables of category 5 (CAT5) or higher, consisting of four twisted pairs. Themaximum baud rate is 100 MBit/s (CAT5).

Note:The device supports Auto Crossover function. Due to this fact, RXand TX can be switched. The following figure shows the RJ45standard pinning.

Ethernet Pin Signal Description1 TX+ Transmit data positive2 TX– Transmit data negative3 RX+ Receive data positive4 Term 1 Connected and terminated to PE via RC

combination*5 Term 16 RX– Receive data negative7 Term 2 Connected and terminated to PE via RC

combination*8 Term 2* Bob Smith Termination

Table 24: Ethernet RJ45 pin assignment

If you are using the NHSTT100EN/ECM for EtherCAT, pleasenote also the user manual Wiring Instructions EtherCAT,DOC121104UMxxEN, stored on the netHOST Solutions DVD in theDocumentation\english\4.Installation Instructionsdirectory.


© Hilscher 2013 – 2015


5.7 Fieldbus interfaces (X3)For identification, see position (15) in section netHOST for Fieldbussystems [ page 30].

Information on fieldbus cabling can be found in the user manualWiring Instructions, DOC120208UMxxEN, stored on the netHOSTSolutions DVD in the Documentation\english\4.InstallationInstructions directory.

5.7.1 PROFIBUS DP interface (NHSTT100DP/DPM)The PROFIBUS DP interface at X3 is a RS485 interface according toPROFIBUS standard EN 50170.PROFIBUS Pin Signal Description

9pole subDsocket, female

3 Rx/Tx + Receive / Transmit data positive4 CNTRP Control signal for repeater (direction control)

5 ISO GND Data ground

6 VP Power supply positive 5V for terminatingresistor. Maximum current 100 mA.

8 Rx/Tx Receive / Transmit data negative

Shield PE Metal shell on PE

Table 25: PROFIBUS RS485 pin assignment

A pull up resistor of 100 kΩ is connected inside the device at “Rx / Tx +“.

A pull down resistor of 100 kΩ is connected inside the device at “Rx / Tx “.

5.7.2 CANopen interface (NHSTT100CO/COM)The CANopen interface at X3 is an ISO 11898 interface according to theCANopen CiA DS 102 standard.CANopen Pin Signal Description

9polesubD male

2 CAN L CAN Low bus line3 ISO GND CAN ground

7 CAN H CAN High bus line

1, 4, 5,6, 8, 9

Important note and strongly recommended:Leave these pins unconnected! Otherwise thereis a high risk of a device damage.

Shield PE Metal shell on PE

Table 26: CANopen pin assignment


© Hilscher 2013 – 2015


5.7.3 DeviceNet interface (NHSTT100DN/DNM)The pin assignment of the DeviceNet interface at X3 complies with theDeviceNet standard.DeviceNet Pin Signal Description

COMBICONsocket, female

1 ISO GND Common groundDeviceNetpower supply.

2 CAN L CAN Low signal

3 Drain Shield

4 CAN H CAN High signal

5 V+ +24 V DeviceNetpower supply

Table 27: DeviceNet pin assignment

5.8 USB interface (MiniB USB)For identification, see section Positions of the LEDs, connectors and controlelements [ page 30].

The USB interface can be used to perform a firmware download/firmwarerecovery to the netHOST device to its “factory settings” (see section UsingUSB to recover firmware [ page 46]).USB Buchse Pin Signal Description

1 USB_EXT Power supply USB Bus (+5 V, from externally)2 D Data 3 D+ Data +4 ID5 GND GroundShield PE Metal shell to PE

Table 28: Pin assignment MiniB USB connector (5pin)

5.9 Schematic diagram of Galvanic isolationThe following schematic diagram illustrates the internal connectionsbetween the different connectors X1, X2 and X3 of the netHOST device.This gives you the chance to properly install the device in accordance withthe “potential equalization concept” of your plant.

Note:The PE connection (potential equalization) of the device is done viathe DIN rail.


© Hilscher 2013 – 2015


5.9.1 netHOST for Fieldbus systemsGalvanic isolation of the netHOST devices NHSTT100DP/DPM, NHSTT100CO/COM and NHSTT100DN/DNM.

Figure 4: Galvanic isolation of netHOST for Fieldbus systems

The device has three galvanically isolated areas. The isolation to thenetwork connections is indicated by the red arrow (A).(1) System area, galvanically coupled with the power supply connection at X1.(2) LAN connecting area, 2 * RJ45.

(The figure above shows only one RJ45 socket. The second RJ45 socket is built upidentically and connected to the logic at netX X2.)

(3) Fieldbus connecting area with DSub male / female or Combiconconnector.

The following table shows the characteristics of the galvanic isolation of thedifferent areas and coupling against potential equalization:

AreaConnection

Interface galv.Isolation

Coupling Coupling against PEpotential

Functional earthing to PE

(1)X1

no

Cx1 (1) 4 * 10 nF 500VHF (1) Cf = 10 nF, Lf = 47 μH

(2)X2

Ethernet inductive Cx2 (2) 4 * 75 Ω, 1 nF 2000 V Directly via the metalconnection of RJ 45 sockets

(3)X3

CANopen(NHSTT100CO)

optically Cx3 (3) 1 MΩ // 15 nF 1000V directly

PROFIBUS(NHSTT100DP) inductive

Cx3 (3) 1 MΩ // 2.2 nF 1000 V directly

DeviceNet(NHSTT100DN)

optically Cx3 (3) 1 MΩ // 15 nF 1000V 1 MΩ // 15 nF 1000V

Table 29: Coupling of netHOST for Fieldbus systems


© Hilscher 2013 – 2015


5.9.2 netHOST for RTE systemsGalvanic isolation of the netHOST devices NHSTT100EN, NHSTT100EN/PNM, NHSTT100EN/ECM and NHSTT100EN/EIM.

Figure 5: Galvanic isolation of netHOST for RTE systems

The device has three galvanically isolated areas. The isolation to thenetwork connections is indicated by the red arrow (A).(1) System area, galvanically coupled with the power supply connection at X1.(2) LAN connection area, 2 * RJ45.

(The figure above shows only one RJ45 socket. The second RJ45 socket is built upidentically and connected to the logic at netX X2.)

(3) LAN connection area 1 * RJ45

The following table shows the characteristics of the galvanic isolation of thedifferent areas and coupling against potential equalization:

AreaConnection

Interface galv.Isolation

Coupling Coupling against PEpotential

Functional earthing to PE

(1)X1

no

Cx1 (1) 4 * 10 nF 500VHF (1) Cf = 10 nF, Lf = 47 μH

(2)X2

RealTimeEthernet

inductive Cx2 (2) 4 * 75 Ω, 1 nF 2000 V Directly via the metalconnection of RJ 45 sockets

(3)X3

Ethernet inductive Cx3 (3) 4 * 75 Ω, 1 nF 2000 V Directly via the metalconnection of RJ 45 socket

Table 30: Coupling of netHOST for RTE systems


© Hilscher 2013 – 2015

Mounting and dismounting of netHOST device 38/72

6 Mounting and dismounting of netHOST device

6.1 Safety messagesPlease 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 signaland power supply lines between the used devices. Otherwise devicedestruction of the netHOST is possible.

Device Destruction Due to Overheating !The air ventilation slots of the netHOST device must not be covered by anyobjects. Otherwise the device might overheat.

Important:On the top side, the devices should have a minimum distance of 20mm to the next device.


© Hilscher 2013 – 2015


6.2 Mounting netHOST device onto Top Hat RailØ The netHOST device is to be mounted onto a horizontally attached tophat rail according to DIN EN 60715.

Ø The rail has to be connected with the potential equalization conductor(PE).

Ø The devices can be mounted onto the top hat rail sidebyside withoutany gap.

(1)(2)

Ø Push the device onto the top hat rail from above.Ø Then press the device against the mounting surface.

Table 31: Mounting the netHOST device onto Top Hat Rail

Ø 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 netHOST devicewill be damaged.

Note:Grounding is done via a grounding contact located at the backsideof the device, connecting it electrically to the DIN top hat rail.


© Hilscher 2013 – 2015


6.3 Removing netHOST device from the Top Hat RailIn order to remove the netHOST from the top hat rail, first remove thepower supply cable and all data cables from the device.

(1)

(2)

(3)

Ø To release the device from the top hat rail, put a screw driverto the clip located on the bottom in the middle of the device.

Ø To disengage the lock from the top hat rail, press the screwdriver upwards.

Ø You can then easily pull the device off the top hat rail.

Table 32: Removing the netHOST device from Top Hat Rail


© Hilscher 2013 – 2015

Commissioning 41/72

7 Commissioning

7.1 FirmwareWith the exception of the NHSTT100EN device (order no.: 1890.800), allnetHOST devices are delivered with their firmware already loaded. Thus,you can instantly install, configure and commission the netHOST afterdelivery. You will find a short summarizing description about configurationin the following section, for detailed instructions and examples see theoperating instruction manual Configuration of LAN controlled masterdevices – netHOST.

If you are using the NHSTT100EN device, you first have to download thefirmware featuring the RealTime Ethernet master protocol (PROFINET IO,EtherCAT or EtherNet/IP) to the device with the SYCON.net configurationsoftware. Detailed instructions on this can be found in the operatinginstruction manual Configuration of LAN controlled master devices –netHOST. Once you have downloaded the firmware to the NHSTT100ENdevice, all following configurational steps are same as for the devices withpreloaded firmware as described in the operating instruction manual.

7.2 Configuring the netHOST

Assigning IP address with Ethernet Device Configuration Tool

A netHOST device is delivered without its Fieldbus or RealTime Ethernetconfiguration and answers at its LAN interface with the default IP address0.0.0.0.

Before the netHOST device can be configured (in case of the NHSTT100EN, before the firmware can be downloaded to the device), a valid IPaddress has to be assigned to the netHOST. Use the Ethernet DeviceConfiguration Tool for this. The IP address of the device must be in thesame sub net as the IP address of the configuration PC, so that it can laterbe reached for configuration.Note, that the IP address assigned by the Ethernet Device ConfigurationTool is kept by the netHOST device only until next poweron cycle ordevice reset, respectively until a permanent IP address has beenconfigured and downloaded to the device with SYCON.net.


© Hilscher 2013 – 2015

Commissioning 42/72

Configuration with SYCON.net

The netHOST device is configured with the Windows configuration softwareSYCON.net. The configuration is transferred to the netHOST device viaLAN connection and TCP/IP protocol (primary network, in case of netHOSTdevices for Fieldbus systems connected to the X2 interface, in case ofnetHOST devices for RTE systems to the X3 interface).

SYCON.net allows you to create a configuration “offline”, without anyimmediate connection to the target device (i. e. the netHOST). Only for thesubsequent download of the configuration into the device, you need aphysical LAN connection.

The SYCON.net configuration consists of the IP address and the fieldbus orRealTime Ethernet configuration. The device stores this data remanently, i.e. the data is being kept after power off or device reset.

After updating the firmware of the netHOST device with SYCON.net, thedevice loses its configuration and its IP address. The device then answerswith its default IP address 0.0.0.0 again.

Detailed information about configuration, diagnosis, testing andfirmware update can be found in the operating instruction manualConfiguration of LAN controlled master devices – netHOST,DOC130402OIxxEN, stored on the netHOST Solutions DVD in theDocumentation\english\1.Software\SYCON.net directory.


© Hilscher 2013 – 2015

Commissioning 43/72

7.3 Startup behaviorAfter a return of power or device reset, the startup behavior of thenetHOST device depends on whether at the time of power return an SDmemory card is inserted in the device or not.

7.3.1 Startup without SD memory cardIf no card is inserted at the time of power return or reset, the firmware andconfiguration data (if available) stored remanently in the internal loadmemory is loaded and started. This can take approximately four seconds,depending on the size of the configuration data.

7.3.2 Startup with inserted SD memory cardIf an SD memory card containing a valid configuration is inserted in thenetHOST device at the time of power on, all data stored on the card iscopied to the internal load memory of the device. This data can be:· firmware· configuration files· IP address

All 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 loadthe desired configuration without having to establish a LAN connection tothe SYCON.net configuration software. With the SD card, you can easily“clone” a configuration and transfer it into another device, e. g. into a sparedevice in case of a defective primary device.

With the SYCON.net configuration software, the data of the internal loadmemory of the netHOST device can be copied to an empty SD memorycard. Note that the SD card must be FAT16 formatted, otherwise it will notbe recognized by the device.

Detailed instructions on how to transfer configuration data intoanother netHOST device by SD memory card can be found inchapter Using SD Memory Card to Copy Configuration Data toSpare netHOST Devices in the operating instruction manualConfiguration of LAN controlled master devices – netHOST,DOC130402OIxxEN.

Resetting the netHOST device to its factory settings by using an SDmemory card (e. g. in case of a defective firmware) is described in thesubsequent chapter.


© Hilscher 2013 – 2015

Firmware recovery 44/72

8 Firmware recovery

8.1 OverviewIf after poweron the SYS LED (for the position of the SYS LED see sectionPositions of the LEDs, connectors and control elements [ page 30]) isflashing yellow and green at a rate of 1 Hz, the device is in boot mode. Thefirmware file of the netHOST device is missing or defective. In this state thedevice cannot be operated and a new firmware file needs to be loaded intothe device either via SD memory card or via USB. When using the SDmemory card, all existing configuration or IP address files inside the devicewill be deleted. The device will thus be reset to its “factory settings”. On theother hand, when using the firmware download function via USB, you canoverwrite only the old defective firmware file and keep the configurationfiles inside the device, thus performing only a “firmware recovery” instead ofa “factory reset”. When using USB, you can decide for yourself, whetheryou also want to delete the configuration files in order to perform a full“factory reset”.

8.2 Using an SD memory card to reset the netHOST to its “factorysettings”

The netHOST device can be reset to its factory settings by using the loadmemory image on an SD memory card. You will find the load memoryimage on the netHOST Solutions DVD in the Supplements & Examples\netHOST Device Recovery\Recovery via Memory Carddirectory in the folder of your device type (e. g. NHSTT100DP_DPM folderfor the NHSTT100DP/DPM device). From there, you can copy the imageto the SD memory card, and then use the card to copy it to the netHOSTdevice.All existing old data (including configuration and IP address) in the internalload memory of the device will thereby be deleted. After recovery by SDcard, the device therefore needs a new IP address and a newconfiguration.

Note:The SD memory card is not included in the delivery of the netHOSTdevice, but can be obtained from Hilscher. The part number of thecard is 1719.003.

Prerequisites· Empty SD memory card (FAT16 formatted)· PC with SD card reader device· netHOST Solutions DVD· the netHOST device is supplied with voltage


© Hilscher 2013 – 2015


Stepbystep instructions1. Copy load memory image from DVD to SD card.Ø Insert an empty SD memory card into the SD card reader device of yourPC.

Ø On the netHOST Solutions DVD, open Supplements & Examples\netHOST Device Recovery\Recovery via Memory Carddirectory.

Ø In the directory, open the folder for your type of device, e. g. NHSTT100DP_DPM, then copy the STARTUP.INI file and the BACKUP folder(with all its subfolders) to the root directory of the SD memory card.

Ø Remove the SD memory card from the SD card reader device.

2. Copy load memory image to netHOST device.Ø Disconnect the voltage supply from your netHOST device.Ø Insert the SD card into the card slot of the netHOST device until itengages (see position (2) in section Positions of the LEDs, connectorsand control elements [ page 30]).

Ø Reconnect the voltage supply of your netHOST device.Ê The device then loads the memory image. While loading the image, theSYS LED quickly alternates between green and yellow forapproximately eight seconds, then shows steady yellow forapproximately ten seconds, then is switched off for a short while beforeit finally shows steady green light. The device automatically starts theloaded firmware.

Ø Remove the SD memory card from device.ð The netHOST device has been reset to its factory settings. The device now needs an IP address and a configuration.


© Hilscher 2013 – 2015


8.3 Using USB to recover firmwareVia USB, you can reset the netHOST device to its factory settings or, as analternative, perform a socalled “firmware recovery”, by downloading a newfirmware file to the device without thereby deleting any existingconfiguration files within the device. For this, you need a USB cable with a Mini USB connector and the HilscherComProX tool, which is stored on the netHOST Solutions DVD in theSupplements & Examples\netHOST Device Recovery\Recoveryvia USB directory. ComProX can be executed directly from DVD, it doesnot need to be installed on your configuration PC. Note that for recovery via USB, you need to install the USB driver for theHilscher netHOST on your configuration PC. This driver allows you tocommunicate with the netHOST via USB, even if the old firmware within thedevice is defective or missing altogether. It is recommended to install the USB driver before you connect thenetHOST device via USB cable. Use the setup.exe driver installationprogram for this, which is stored on the netHOST Solutions DVD in theSetups & Drivers\USB Driver directory.

The installation of the USB driver is described in the user manualSoftware Installation netHOST Devices, DOC130501UMxxEN,which is stored on the netHOST Solutions DVD in theDocumentation\english\4.Installation Instructionsdirectory.

Note the following concerning recovery via USB: Although any old firmware file that may have existed in the netHOST devicewill be overwritten by downloading the new firmware file (recognizable bythe .NXF file name extension), all other files stored in the internal loadmemory of the device remain untouched. This means that any existingconfiguration (CONFIG.NXD) or IP address (NWID.NXD) file in the devicecan be preserved for further use, if needed. However, if you want acomplete reset of your device via USB (a complete reset to “factory setting”means that only “fresh” firmware is present in the device), you can deletethe configuration and the address files separately in the Explorer of theComProX tool.

Prerequisites· The USB driver for Hilscher netHOST has been installed on theconfiguration PC (the driver is included in the USB driver installationprogram stored on the netHOST Solutions DVD).

· The configuration PC has been connected to the netHOST device viaUSB cable.

· You have access to the netHOST Solutions DVD.· The netHOST device is supplied with voltage.


© Hilscher 2013 – 2015


Stepbystep instructions1. Open ComProX.Ø On the netHOST Solutions DVD, open Supplements & Examples\netHOST Device Recovery\Recovery via USB directory.

Ø Doubleclick comproX.exe file.Ê The ComProX tool opens:

Figure 6: ComProX start screen

2. Connect to netHOST device.Ø In the menu, choose Connection > Open.Ê After the Windows USB/COM ports have been scanned, the connectionselection dialog opens:

Figure 7: ComProX Connection dialog

Ø Select Hilscher netHOST entry, then click OK.Ê The connection dialog closes and you are back in start screen ofComProX.

3. Download firmware file.Ø In the menu, choose Connection > File Explorer.


© Hilscher 2013 – 2015


Ê The Explorer window opens:

Figure 8: ComProX File Explorer

Ø Under Filesystem, select PORT_0.Ê The content of PORT_0 is displayed. This, most likely, will be the oldfirmware file, which you want to overwrite. If you have alreadydownloaded a configuration to the netHOST, the IP addressconfiguration file (NWID.NXD) is also displayed here.

Ø In the right part of the Explorer window, rightclick to open the contextmenu, then choose Download.

Figure 9: ComProX Download

Ê The Choose a file dialog opens:

Figure 10: Choose a file dialog in ComProX


© Hilscher 2013 – 2015


Ø Open the folder for your device and select the firmware file you want todownload to your device (firmware files can be recognized by the filename extension .NXF).

Ø Click Open.Ê The firmware file is being downloaded to the netHOST device. The oldfirmware file is being overwritten. This can take a few seconds.

4. Check download.Ø In the right part of the Explorer window, rightclick to open the contextmenu, then choose Refresh.

Ø Wait for a few seconds.Ê If the download has been successful, the downloaded firmware file isdisplayed in Port 0:

Figure 11: Downloaded firmware in Explorer

Note:If there is an IP address file (NWID.NXD) present in Port_0 andconfiguration files (CONFIG.NXD) in Port_1, and you do not want touse these configuration files any longer, you can delete them inorder to completely reset the device to its “factory settings”. For this,select the configuration file in the Explorer, then choose Deletecommand from the context menu.

5. Exit ComProX.Ø Close the Explorer window.Ø In the menu of ComProX, choose Connection > Close to close theconnection to the device.

Ø Close ComProX.6. Restart netHOST device.Ø Disconnect the voltage supply from the netHOST device, thenreconnect it.

ð After restart, the SYS LED shows steady green light.The state of the APL LED depends on whether a valid configuration isstill present in the device. If this is not the case, the APL LED is blinkingred.


© Hilscher 2013 – 2015

Troubleshooting 50/72

9 TroubleshootingThere are two steps of error diagnosis:· the initial approximate diagnosis by checking the LEDs of the device,· the comprehensive diagnosis with the SYCON.net configuration anddiagnosis software via LAN connection.

The following overview describes the error conditions that may be detectedby checking the LEDs (for identification of the LEDs, please refer to sectionPositions of the LEDs, connectors and control elements [ page 30]).

For information on how to diagnose the netHOST device withSYCON.net, see Operating Instruction Manual Configuration of LANcontrolled master devices – netHOST, DOC130402OIxxEN, storedon the netHOST Solutions DVD in the Documentation\english\1.Software\SYCON.net directory.

LED LED state Cause/remedyAll No LED is on The device is not powered or the device is

defective and needs replacement.SYS RTE devices: position (4)Fieldbus devices: position (5)

SYS LED flashes yellow/green at 1 Hz

After a power cycle the device has not found avalid firmware and remains in boot loader mode.The firmware of the device has to be “recovered”.See chapter FirmwareRecovery [ page 44].If recovery fails, the load memory of the devicemight be defective.

SYS RTE devices: position (4)Fieldbus devices: position (5)

SYS LED flashes yellow The device could not be initialized. No boot loaderwas found in the load memory. The load memory ofthe device might be defective or a USB cable,which has pin 4 connected with ground, might beattached to the device. This prevents the devicefrom starting.

SYS RTE devices: position (4)Fieldbus devices: position (5)

SYS LED shows static yellow

The hardware of the device is defective and needsreplacement.

SYS RTE devices: position (4)Fieldbus devices: position (5)APL RTE devices: position (5)Fieldbus devices: position (6)

SYS LED shows static greenandAPL LED flashes red orshows static red.

The device is well initialized. Further diagnosis ispossible with the APL LED. See section LED APL [ page 52].

APL RTE devices: position (5)Fieldbus devices: position (6)

APL LED flashes green. The communication at port X2 or/and port X3 is notin data exchange mode. See also section LED APL[ page 52].

Table 33: netHOST troubleshooting by LED

For protocolspecific error diagnostics by LED, see section LEDs of theFieldbus and RealTime Ethernet systems [ page 53].


© Hilscher 2013 – 2015

LEDs 51/72

10 LEDsThis chapter describes the meaning of the LEDs of the netHOST device.For identification of the LEDs on the device, please refer to sectionPositions of the LEDs, connectors and control elements [ page 30].

10.1 SYS LEDThis LED indicates basic operating states which are independent of theconfiguration of the device.

LED Color State MeaningSYSRTE devices: position (4)Fieldbus devices: position (5)

Duo LED yellow/green

(green) On Operating System running. For further diagnosis, see APL LED.

(yellow) On The hardware of the device is defective and needs replacement.

(yellow)Flashing

The device could not be initialized. No boot loader was found inthe load memory. The load memory of the device might bedefective or a USB cable, which has pin 4 connected with ground,might be attached to the device. This prevents the device fromstarting.

(yellow/green)

Flashingyellow/green1 Hz

Error state! Boot loader active.Firmware file is missing or defective. The device needs to berecovered by SD memory card or via USB. See chapter Firmwarerecovery [ page 44].

(yellow/green)

Flashingyellow/green16 Hz

Data is being copied from the SD memory card into the internalload memory.

(off) Off Power supply for the device is missing or hardware is defective.

Table 34: System LED


© Hilscher 2013 – 2015

LEDs 52/72

10.2 APL LEDThis LED indicates the communication state of the primary network(Ethernet LAN) and the secondary network (Fieldbus or RealTimeEthernet), as well as the state of the configuration of the netHOST device.

LED Color State MeaningAPLRTE devices: position (5)Fieldbus devices: position (6)

Duo LED red/green

(green) On The Ethernet cable of the primary network is plugged in at the LANinterface. The netHOST device communicates via secondary network(Fieldbus or RealTime Ethernet) and exchanges payload data. ThenetHOST function is executed without error.Note: This does not indicate a connection to a host application.

(green) Blinking with2 s off, 0.5 s on

netHOST is initialized, a valid configuration is present in the device.The netHOST communicates via secondary network, but the LANinterface at the primary network shows no activity.The Ethernet cable has been removed from the LAN interface.Reconnect the cable.

(green) Blinking with2 s off, 0.5 s on, 0.5 s off, 0.5 s on

netHOST is initialized, a valid configuration is present in the device.Communication at the secondary network (Fieldbus or RealTimeEthernet) is not in payload data exchange.

· In the netHOST configuration, the starting mode for communicationat the interface of the secondary network is set to “controlled by thehost application”, which is the default setting. Please check thissetting in the configuration software. Check also, whether or not thestart command from the host application has already been issued.

· netHOST as Fieldbus or RealTime Ethernet master after startcommand: The netHOST has no payload data connection to any ofthe configured slaves. The configuration of the netHOST might not match the configurationof the slaves or the fieldbus or RTE cable is not connected. Use theSYCON.net configuration software for diagnosis.

(red) Blinking with2 s off, 0.5 s on

netHOST is initialized, but the configuration of the primary network(LAN) does not allow communication.

· DHCP mode was configured for the LAN network, but the device hasnot yet received an IP address from the DHCP server.Check the DHCP server and your configuration.

· An IP address has been configured, but it conflicts with another IPaddress already used in the LAN network.

· Configuration is missing in the netHOST device. Use the SYCON.net configuration software to download theconfiguration.

· LAN configuration has an error.


© Hilscher 2013 – 2015

LEDs 53/72

LED Color State MeaningAPLRTE devices: position (5)Fieldbus devices: position (6)

(red) Blinking with2 s off, 0.5 s on, 0.5 s off, 0.5 s on

netHOST is initialized, but the configuration of the secondary networkprotocol (Fieldbus or RealTime Ethernet) does not allowcommunication. Use the SYCON.net configuration software todownload the configuration again.

· A watchdog timeout error has occurred while the watchdog for hostapplication was active. The Fieldbus or RTE network has been set tooperating mode “stop”. Check the LAN connection to the hostapplication. The connection to the host application has to be reestablished.

· The configuration of the Fieldbus/RTE network has an error.

· The configuration of the Fieldbus/RTE network is not complete.

· The configuration of the Fieldbus/RTE network is missing.

(red) On netHOST has detected one of the following errors during theinitialization:

· Missing configuration

· Error in configuration

· Internal sequence errorTable 35: APL LED

10.3 LEDs of the Fieldbus and RealTime Ethernet systems

10.3.1 LED PROFIBUS DP Master (NHSTT100DP/DPM)The subsequent table describes the meaning of the COM LED of theNHSTT100DP/DPM netHOST device.

LED Color State MeaningCOMPosition inthe devicedrawing: (14)

Duo LED red/green

(green) On Communication to all Slaves is established.

(green) Blinking (5 Hz) PROFIBUS is configured, but the bus communication is not yet releasedfrom the application.

(green) Flashing, acyclic No configuration or faulty configuration

(red) Blinking (5 Hz) Communication to at least one Slave is disconnected.

(red) On Communication to all Slaves is disconnected or another serious errorhas occurred.Redundant Mode: The active Master was not found.

(off) Off Device is not switched on or network power is missing.

Table 36: LED states for the PROFIBUS DP Master protocol

LED state DefinitionOn The indicator is constantly on.Off The indicator is constantly off.Blinking (5 Hz) The indicator turns on and off with a frequency of 5 Hz:

“on” for 100 ms, followed by “off” for 100 ms.Flashing, acyclic The indicator turns on and off in irregular intervals.

Table 37: LED state definitions for the PROFIBUS DP Master protocol


© Hilscher 2013 – 2015

LEDs 54/72

10.3.2 LED CANopen Master (NHSTT100CO/COM)The subsequent table describes the meaning of the CAN LED of the NHSTT100CO/COM netHOST device:

LED Color State MeaningCANPosition inthe devicedrawing: (14)

Duo LED red/green

(green) On OPERATIONAL: The device is in the OPERATIONAL state.

(green) Blinking (2,5 Hz)PREOPERATIONAL: The device is in the PREOPERATIONAL state.

(green) Single flash STOPPED: The device is in STOPPED state.

(red) Single flash Warning limit reached: At least one of the error counters of the CANcontroller has reached or exceeded the warning level (too many errorframes).

(red) Double flash Error control event: A guard event (NMT Slave or NMT Master) or aheartbeat event (Heartbeat consumer) has occurred.

(red) On Bus off: The CAN controller is in bus OFF state.

(off) Off RESET: The device is executing a reset or the device has noconfiguration.

Table 38: LED states for the CANopen Master protocol

LED state DefinitionOn The indicator is constantly on.Off The indicator is constantly off.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 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 39: LED state definitions for the CANopen Master protocol


© Hilscher 2013 – 2015

LEDs 55/72

10.3.3 LED DeviceNet Master (NHSTT100DN/DNM)The subsequent table describes the meaning of the MNS LED of theNHSTT100DN/DNM netHOST device:

LED Color State MeaningMNSPosition inthe devicedrawing: (14)

Duo LED red/green

(green) On Device operational AND online, connected Device is online and has established all connections with all Slaves.

(green) Flashing (1 Hz) Device operational AND online Device is online and has established no connection in the establishedstate. Configuration missing, incomplete or incorrect.

(green/red/off)

Flashing (2 Hz)Green/Red/Off

Selftest after power on

(red) Flashing (1 Hz) Minor fault and/or connection timeout Device is online and has established one or more connections in theestablished state. It has data exchange with at least one of theconfigured Slaves. Minor or recoverable fault: No data exchange withone of the configured Slaves. One or more Slaves are not connected.Connection timeoutMinor or recoverable fault: No data exchange with one of the configuredSlaves. One or more Slaves are not connected.Connection timeout.No network power present.

(red) On Critical fault or critical link failure Critical connection failure; device has detected a network error: duplicateMACID or severe error in CAN network (CANbus off).

(off) Off Device is not powered The device may not be powered. Device is not online and/or no network power The device has not yet completed the Dup_MAC_ID test. The device is powered, but the network power is missing.

Table 40: LED states for the DeviceNet Master protocol

LED state DefinitionOn The indicator is constantly on.Off The indicator is constantly off.Flashing (1 Hz) The indicator turns on and off with a frequency of appr. 1 Hz:

“on” for appr. 500 ms, followed by “off” for appr. 500 ms.Flashing (2 Hz) green/red/off

The indicator turns on green on for 250 ms, then red on for 250 ms, then off.

Table 41: LED state definitions for the DeviceNet Master protocol


© Hilscher 2013 – 2015

LEDs 56/72

10.3.4 LEDs PROFINET IO ControllerThe subsequent table describes the meaning of the PROFINET IOController LEDs of the NHSTT100EN/PNM, respectively of the NHSTT100EN with loaded PROFINET IO Controller firmware.

LED Color State MeaningSF (SystemError)Position inthe devicedrawing: (7)

Duo LED red/green

(off) Off No error

(red) Flashing (1 Hz, 3s)

DCP signal service is initiated via the bus.

(red) Flashing (2 Hz) System error: Invalid configuration, Watchdog error or internal error

(red) On (together withSF „red ON)

No valid Master license

BF (Bus Failure)Position inthe devicedrawing: (8)

Duo LED red/green

(off) Off No error

(red) Flashing (2 Hz) Configuration fault: Not all configured IODevices are connected.

(red) On (together withSF „red ON")

No valid Master license

(red) On (together withSF „red OFF“)

No Connection: No Link.

LINKCh0 (9)Ch1 (12)

LED green

(green) On The device is linked to the Ethernet.

(off) Off The device has no link to the Ethernet.

RX/TXCh0 (11)Ch1 (14)

LED yellow

(yellow)Flickering (loaddependent)

The device sends/receives Ethernet frames.

(off) Off The device does not send/receive Ethernet frames.

Table 42: LED states for the PROFINET IOController protocol

LED state DefinitionOn The indicator is constantly on.Off The indicator is constantly off.Flashing (1 Hz, 3 s) The indicator turns on and off for 3 seconds with a frequency of 1 Hz: “on” for 500 ms, followed by

“off” for 500 ms.Flashing (2 Hz) The indicator turns on and off with a frequency of 2 Hz:

“on” for 250 ms, followed by “off” for 250 ms.Flickering (loaddependent)

The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernetactivity: "on" for approximately 50 ms, followed by "off" for 50 ms. The indicator turns on and off inirregular intervals to indicate low Ethernet activity.

Table 43: LED state definitions for the PROFINET IOController protocol


© Hilscher 2013 – 2015

LEDs 57/72

10.3.5 LEDs EtherCAT MasterThe subsequent table describes the meaning of the EtherCAT Master LEDsof the NHSTT100EN/ECM, respectively of the NHSTT100EN withloaded EtherCAT Master firmware.

LED Color State MeaningRUNPosition inthe devicedrawing: (7)

Duo LED red/green

(off) Off INIT: The device is in INIT state.

(green) Blinking (2,5 Hz) PREOPERATIONAL: The device is in PREOPERATIONAL state.

(green) Flickering (10 Hz) BOOT: Device is in Boot mode.

(green) Single flash SAFEOPERATIONAL: The device is in SAFEOPERATIONAL state.

(green) On OPERATIONAL: The device is in the OPERATIONAL state.

ERRPosition inthe devicedrawing: (8)

DuoLED red/green

(off) Off Master has no errors

(red) On Master has detected a communication error. The error is indicated in theDPM.

LINKCh0 (9)

LED green



ACTCh0 (11)

LED yellow

(yellow)Flickering (loaddependent)



Table 44: LED states for the EtherCAT Master protocol

LED state DefinitionOn The indicator is constantly on.Off The indicator is constantly off.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.

Flickering (10 Hz)

The indicator turns on and off with a frequency of 10 Hz: “on” for 50 ms, followed by “off” for 50ms.

Single flash The indicator shows one short flash (200 ms) followed by a long “off“ phase (1,000 ms).Flickering (loaddependant)

The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernetactivity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off inirregular intervals to indicate low Ethernet activity.

Table 45: LED state definitions for the EtherCAT Master protocol


© Hilscher 2013 – 2015

LEDs 58/72

10.3.6 LEDs EtherNet/IP ScannerThe subsequent table describes the meaning of the EtherNet/IP ScannerLEDs of the NHSTT100EN/EIM, respectively of the NHSTT100EN withloaded EtherNet/IP Scanner firmware.

LED Color State MeaningMS (modulestatus)Position inthe devicedrawing: (7)

Duo LED red/green

(green) On Device operational: The device is operating correctly.

(green) Flashing (1 Hz) Standby: The device has not been configured.

(red/green)

Flashing (1 Hz) Selftest: The device is performing its power up testing.

(red) Flashing (1 Hz) Minor fault: The device has detected a recoverable minor fault. E. g. anincorrect or inconsistent configuration can be considered as a minorfault.

(red) On Major fault: The device has detected a nonrecoverable major fault.

(off) (Off) No power: The power supply to the device is missing.

NS (networkstatus)Position inthe devicedrawing: (8)

Duo LED red/green

(green) On Connected: The device has at least one established connection (evento the Message Router).

(green) Flashing (1 Hz) No connections: The device has no established connections, but hasobtained an IP address.

(red/green)

Flashing (1 Hz) Selftest: The device is performing its power up testing.

(red) Flashing (1 Hz) Connection timeout: One or more of the connections in which thisdevice is the target have timed out. This status will be finished only if alltimed out connections are reestablished or if the device is reset.

(red) On Duplicate IP: The device has detected that its IP address is already inuse.

(off) Off Not powered, no IP address: The device does not have an IP address(or is powered off).

LINKCh0 (9)Ch1 (12)

LED green



ACTCh0 (11)Ch1 (14)

LED yellow

(yellow)Flickering (loaddependant)



Table 46: LED states for the EtherNet/IP Adapter protocol

LED state DefinitionOn The indicator is constantly on.Off 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 (loaddependant)

The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernetactivity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off inirregular intervals to indicate low Ethernet activity.

Table 47: LED state definitions for the EtherNet/IP Scanner protocol


© Hilscher 2013 – 2015

Technical data 59/72

11 Technical data

11.1 Technical data of the netHOST devices

11.1.1 netHOST for Fieldbus systemsNHSTT100DP/CO/DN Parameter ValueCommunication controller Type netX 100Memory RAM 8 MB SDRAM

FLASH 4 MB serial FlashSD memory card (optional) max. 2 GByte

Do not use SDHC or SDXC card typesUSB Interface USB Socket MiniUSB, 5pinDisplay LEDs SYS system status netHOST

APL application status netHOSTLINK Link (LAN interface)ACT Activity (LAN interface)Fieldbus communication status:NHSTT100DP/DPM: COMNHSTT100CO/COM: CANNHSTT100DN/DNM: MNS

Power supply Voltage 24 V ± 6 V DC with reverse voltage protection

Current at 24 V (typically) 130 mAPower consumption 3.2 WConnector MiniCOMBICON, 2pinPower supply For UL compliant usage:

Device shall be supplied by an isolated voltage source.Environmental conditions Temperature range 0 … + 60 °C

Humidity No condensation permittedEnvironment For UL compliant usage:

Device must be used in a pollution degree 2 environment.Device Dimensions (L x W x H) 100 x 52 x 70 mm (without connector)

Weight appr. 150 gMounting on DIN rail EN 60715Protection class IP 20RoHS Yes

CE Sign CE Sign YesEmission CISPR 11 Class AImmunity EN 611312:2003

Configuration Software SYCON.net Ethernet Device Configuration Tool

Table 48: Technical data netHOST for Fieldbus systems (Part 1)


© Hilscher 2013 – 2015


NHSTT100DP/CO/DN Parameter ValueEthernet Interface (X2) Transmission rate 100 MBit/s

10 MBit/sInterface type 100 BASETX, isolatedHalf duplex/Full duplex supported (at 100 MBit/s)AutoNegotiation supportedAutoCrossover supportedConnector 2 * RJ45

PROFIBUS DP Interface(X3) NHSTT100DP

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

Interface type RS 485, optically isolatedConnector SubD female, 9pin

CANopen Interface (X3)NHSTT100CO

Transmission rate 10 kBit/s,20 kBit/s,50 kBit/s,100 kBit/s,125 kBit/s,250 kBit/s,500 kBit/s,800 kBit/s,1 MBit/s

Interface type ISO 11898, optically isolatedConnector SubD male, 9pin

DeviceNet Interface (X3)NHSTT100DN

Transmission rate 125 kBit/s, 250 kBit/s, 500 kBit/s

Interface type ISO 11898, optically isolatedConnector COMBICON, 5pin

Table 49: Technical data netHOST for Fieldbus systems (Part 2)


© Hilscher 2013 – 2015


11.1.2 netHOST for RealTime Ethernet systemsNHSTT100EN/PNM/ECM/EIM Parameter ValueCommunication controller Type netX 100Memory RAM 8 MB SDRAM

FLASH 4 MB serial FlashSD memory card(optional)

max. 2 GByteDo not use SDHC or SDXC card types

USB Interface USB Socket MiniUSB, 5pinDisplay LEDs SYS system status netHOST

APL application status netHOSTLINK Link (LAN and RTE interface) ACT Activity (LAN and RTE interface)Protocol specific LEDs:PROFINET IO Controller: SF, BFEtherCAT Master: RUN, ERREthernet/IP Scanner: MS, NS

Power supply Voltage 24 V ± 6 V DC with reverse voltage protection

Current at 24 V (typically) 130 mAPower consumption 3.2 WConnector MiniCOMBICON, 2pinPower supply For UL compliant usage:

Device shall be supplied by an isolated voltage source.Environmental conditions Temperature range 0 … + 60 °C

Humidity No condensation permittedEnvironment For UL compliant usage:

Device must be used in a pollution degree 2environment.

Device Dimensions (L x W x H) 100 x 52 x 70 mm (without connector)Weight appr. 150 gMounting on DIN rail EN 60715Protection class IP 20RoHS Yes

CE Sign CE Sign YesEmission CISPR 11 Class AImmunity EN 611312:2003

Configuration Software SYCON.netEthernet Device Configuration Tool

Ethernet Interfaces (RTE at X2 and LAN at X3)

Transmission rate 100 MBit/s10 MBit/s

Interface type 100 BASETX, isolatedHalf duplex/Full duplex supported (at 100 MBit/s)AutoNegotiation supportedAutoCrossover supportedConnector X2 (RTE interface): 2 x RJ45

X3 (LAN interface): 1 x RJ45Table 50: Technical data netHOST for RealTime Ethernet systems


© Hilscher 2013 – 2015


11.2 Technical data of the protocols

11.2.1 PROFIBUS DP Master (NHSTT100DP/DPM)Parameter DescriptionMaximum number of PROFIBUS DP slaves 125 (DPV0/DPV1)Maximum number of total cyclic input data 5712 bytesMaximum number of total cyclic output data 5760 bytesMaximum number of cyclic input data 244 bytes per slaveMaximum number of cyclic output data 244 bytes per slaveConfiguration data Max. 244 bytes per slaveParameterization data per slave 7 bytes standard parameter per slave

Max. 237 bytes application specific parameters per slaveAcyclic communication DPV1 class 1 read, write

DPV1 class 1 alarmDPV1 class 2 initiate, read, write, data transport, abort

Maximum number of acyclic read/write 240 bytes per slave and telegramFunctions Configuration in Run (CiR), requires host application program support

Timestamp (Master functionality)Redundancy Supported, requires host application program supportBaud rate 9,6 kBits/s,

19,2 kBits/s, 31,25 kBits/s, 45,45 kBits/s93,75 kBits/s, 187,5 kBits/s, 500 kBits/s, 1, 5 MBits/s, 3 MBits/s, 6 MBits/s, 12 MBit/sAuto baud rate detection is not supported

Data transport layer PROFIBUS FDLLimitations DPV2 isochronous mode and slave slave communication are not

supported.The redundancy function cannot be used, if the master is configured bythe host application program by packets.

Reference to firmware/stack version 2.6.x.xTable 51: Technical data PROFIBUS DP Master protocol


© Hilscher 2013 – 2015


11.2.2 CANopen Master (NHSTT100CO/COM)Parameter DescriptionMaximum number of CANopen nodes 126Maximum number of cyclic input data 3584 bytesMaximum number of cyclic output data 3584 bytesMaximum number of receive PDOs 512Maximum number of transmit PDOs 512Exchange of process data Via PDO transfer:

synchronized, remotely requested and event driven (change of date)

Acyclic communication SDO Upload/Download, max. 512 bytes per requestFunctions Emergency message (consumer and producer)

Node guarding / life guarding, heartbeatPDO mappingNMT MasterSYNC protocol (producer)Simple bootup 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

CAN layer 2 access Send/receive via API supported (11 bit/29 bit)Data transport layer CAN FramesCAN Frame type for CANopen 11 BitReference to version V2.11.x.x

Table 52: Technical data CANopen Master protocol


© Hilscher 2013 – 2015


11.2.3 DeviceNet Master (NHSTT100DN/DNM)Parameter DescriptionMaximum number of DeviceNet slaves 63Maximum number of total cyclic input data 3584 bytesMaximum number of total cyclic output data 3584 bytesMaximum number of cyclic input data 255 bytes/connectionMaximum number of cyclic output data 255 bytes/connectionMaximum Configuration data 1000 bytes/slaveAcyclic communication Explicit connection

All service codes are supportedConnections Bit Strobe

Change of StateCyclicPollExplicit PeertoPeer Messaging

Function Quick ConnectFragmentation Explicit and I/OUCMM SupportedObjects Identity Object (Class Code 0x01)

Message Router Object (Class Code 0x02)DeviceNet Object (Class Code 0x03)Connection Object (Class Code 0x05)Acknowledge Handler Object (Class Code 0x06)

Baud rates 125 kBits/s, 250 kBit/s, 500 kBit/sAuto baudrate detection is not supported

Data transport layer CAN framesReference to firmware/stack version V2.3.x.x

Table 53: Technical data DeviceNet Master protocol


© Hilscher 2013 – 2015


11.2.4 PROFINET IO ControllerParameter DescriptionMaximum number of PROFINET IODevices

128

Maximum number of total cyclic inputdata

5712 bytes (including IOxS status bytes)

Maximum number of total cyclic outputdata

5760 bytes (including IOxS status bytes)

Maximum number of cyclic input data 1440 bytes per device (= IOCR data length including IOxS status bytes)Maximum number of cyclic output data 1440 bytes per device (= IOCR data length including IOxS status bytes)Acyclic communication Read/Write Record

Limited to 1392 bytes per telegramLimited to 4096 bytes per request

Alarm processing yes, but requires handling in host application programDiagnostic data One 200 byte buffer per IO deviceDCP functions via API Name Assignment IODevices (DCP SET NameOfStation)

Set IODevices IP (DCP SET IP)Signal IODevice (DCP SET SIGNAL)Reset IODevice to factory settings (DCP Reset FactorySettings)Bus scan (DCP IDENTIFY ALL)

Supported Protocols RTC – Real Time Cyclic Protocol, Class 1RTA – Real Time Acyclic ProtocolDCP – Discovery and configuration ProtocolCLRPC – Connectionless Remote Procedure Call

Context management by CLRPC SupportedMinimum cycle time 1 ms

Different IODevices can be configured with different cycle timesFunctions Fast Startup of PROFINET IO Devices supportedBaud rate 100 MBit/s

FullDuplex modeData transport layer Ethernet II, IEEE 802.3Configuration file Maximum 1 MByteLimitations RT over UDP not supported

Multicast communication not supportedDHCP is not supported (neither for PROFINET IOController nor for the IODevices)Only one IOCR per IO DeviceNameOfStation of IO Controller CANNOT be set using the DCP SETNameOfStation service but only at startup while configuring the IO ControllerThe buffer for IODevice diagnosis data will be overwritten in case of multiplediagnostic events. Only one (the last) event is stored at the same time. If asingle event produces more than 200 bytes of diagnosis data, only the first 200bytes 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 ofconfigured IO Devices and the amount of IO data depend on each other. Forexample it is not possible due to performance reasons to have 128 IO Devicescommunication with cycletime 1ms.The size of the bus configuration file is limited by the size of the RAM Disk (1MByte)WriteMultipleRecord service is not supported

Reference to firmware/stack version V2.6.x.xTable 54: Technical data PROFINET IO RT Controller


© Hilscher 2013 – 2015


11.2.5 EtherCAT MasterParameter DescriptionMaximum 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 5760 bytesMaximum number of cyclic output data 5760 bytesMinimum 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 acycle time of 1 ms and higher.

Acyclic communication CoE (CANopen over EtherCAT)CoEUpload, CoEDownloadMaximum 1500 bytes

Functions Get OD ListGet object descriptionGet entry descriptionEmergencySlave diagnostics

Bus Scan SupportedRedundancy Supported, but not at the same time with Distributed ClocksDistributed Clocks Supported, but not at the same time with RedundancyTopology Line or ringBaud rate 100 MBit/sData transport layer Ethernet II, IEEE 802.3Configuration File (ethercat.xml or config.nxd) NHSTT100EN: Maximum 2 MByteLimitations The size of the bus configuration file is limited by the size of the

FLASH disk (2 Mbyte).All CoE Uploads, Downloads and information services must fit inone TLRPacket. Fragmentation is not supportedDistributed Clock and Redundancy cannot be used at the sametime.

Reference to firmware/stack version V3.0.x.xTable 55: Technical data EtherCAT Master protocol


© Hilscher 2013 – 2015


11.2.6 EtherNet/IP ScannerParameter DescriptionMaximum number of EtherNet/IPconnections

64 connections for implicit and explicit

Maximum number of total cyclic input data 5712 bytesMaximum number of total cyclic output data 5760 bytesMaximum number of cyclic input data 504 bytes per slave per telegramMaximum number of cyclic output data 504 bytes per slave per telegramIO Connection type Cyclic, minimum 1 ms (depending on used number of connections and

used number of input and output data)Maximum number of unscheduled data 1400 bytes per telegramUCMM, Class 3 SupportedExplicit Messages, Client and ServerServices

Get_Attribute_Single/AllSet_Attribute_Single/All

Quick connect SupportedPredefined standard objects Identity Object

Message Route ObjectAssembly ObjectConnection ManagerEthernet Link ObjectTCP/IP ObjectDLR ObjectQoS Object

Maximal number of user specific objects 20Topology Tree, Line, RingDLR (Device Level Ring) Beacon based ’Ring Node’ACD (Address Conflict Detection) SupportedDHCP SupportedBOOTP SupportedBaud rates 10 and 100 MBit/sData transport layer Ethernet II, IEEE 802.3Switch function IntegratedLimitations CIP Sync Services are not implemented

TAGs are not supportedReference to firmware/stack version V2.6.x.x

Table 56: Technical data EtherNet/IP Scanner (master) protocol


© Hilscher 2013 – 2015

Decommissioning/Disposal 68/72

12 Decommissioning/Disposal

12.1 Putting the device out of operation

Danger of Unsafe System Operation !To prevent personal injury or property damage, make sure that the removalof the device from your plant during operation will not affect the safeoperation 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 RemovingnetHOST device from the Top Hat Rail [ page 40].

12.2 Disposal of waste electronic equipmentAccording to the European Directive 2002/96/EG “Waste Electrical andElectronic Equipment (WEEE)”, waste electronic equipment may not bedisposed of as household waste. As a consumer, you are legally obliged todispose of all waste electronic equipment according to national and localregulations.

Waste electronic equipmentWaste Electronic EquipmentThis product must not be treated as household waste.This product must be disposed of at a designated waste electronicequipment collecting point.


© Hilscher 2013 – 2015

List of figures 69/72

List of figuresFigure 1: Data flow of LAN controlled netHOST device....................................................... 23Figure 2: netHOST for Fieldbus: NHSTT100DP/DPM (example) ..................................... 25Figure 3: netHOST for RTE systems ................................................................................... 26Figure 4: Galvanic isolation of netHOST for Fieldbus systems ........................................... 36Figure 5: Galvanic isolation of netHOST for RTE systems.................................................. 37Figure 6: ComProX start screen .......................................................................................... 47Figure 7: ComProX Connection dialog ................................................................................ 47Figure 8: ComProX File Explorer......................................................................................... 48Figure 9: ComProX Download ............................................................................................. 48Figure 10: Choose a file dialog in ComProX.......................................................................... 48Figure 11: Downloaded firmware in Explorer......................................................................... 49


© Hilscher 2013 – 2015

List of tables 70/72

List of tablesTable 1: List of revisions........................................................................................................ 6Table 2: Reference to devices with preloaded firmware ....................................................... 8Table 3: Reference to devices for loadable firmware ............................................................ 8Table 4: Reference to software ............................................................................................. 9Table 5: Reference to drivers ................................................................................................ 9Table 6: Directory of netHOST Solutions DVD...................................................................... 11Table 7: Basic documentation for netHOST.......................................................................... 12Table 8: Additional documentation for netHOST as PROFIBUS DP Master......................... 13Table 9: Additional documentation for netHOST as CANopen Master ................................. 13Table 10: Additional documentation for netHOST as DeviceNet Master ................................ 13Table 11: Additional documentation for netHOST as PROFINET IO Controller ..................... 14Table 12: Additional documentation for netHOST as EtherCAT Master ................................. 14Table 13: Additional documentation for netHOST as EtherNet/IP Scanner ............................ 15Table 14: Signal words in safety messages on personal injury............................................... 21Table 15: Safety signs in messages on personal injury .......................................................... 21Table 16: Signal words in safety messages on property damage........................................... 21Table 17: Safety signs in safety messages on property damage............................................ 21Table 18: Dimensioned drawing, example NHSTT100DP.................................................... 29Table 19: LEDs, connectors and operating elements of netHOST for Fieldbus systems ....... 30Table 20: LEDs, connectors and operating elements of netHOST for RTE systems.............. 31Table 21: Sticker for NHSTT100EN...................................................................................... 32Table 22: Device label (NHSTT100DP example) ................................................................. 32Table 23: Pin assignment Mini Combicon socket 2pole......................................................... 32Table 24: Ethernet RJ45 pin assignment ................................................................................ 33Table 25: PROFIBUS RS485 pin assignment........................................................................ 34Table 26: CANopen pin assignment........................................................................................ 34Table 27: DeviceNet pin assignment....................................................................................... 35Table 28: Pin assignment MiniB USB connector (5pin) ........................................................ 35Table 29: Coupling of netHOST for Fieldbus systems ............................................................ 36Table 30: Coupling of netHOST for RTE systems................................................................... 37Table 31: Mounting the netHOST device onto Top Hat Rail ................................................... 39Table 32: Removing the netHOST device from Top Hat Rail.................................................. 40Table 33: netHOST troubleshooting by LED ........................................................................... 50Table 34: System LED ............................................................................................................ 51Table 35: APL LED.................................................................................................................. 52Table 36: LED states for the PROFIBUS DP Master protocol ................................................ 53Table 37: LED state definitions for the PROFIBUS DP Master protocol ................................. 53Table 38: LED states for the CANopen Master protocol ......................................................... 54Table 39: LED state definitions for the CANopen Master protocol.......................................... 54Table 40: LED states for the DeviceNet Master protocol ........................................................ 55


© Hilscher 2013 – 2015

List of tables 71/72

Table 41: LED state definitions for the DeviceNet Master protocol......................................... 55Table 42: LED states for the PROFINET IOController protocol ............................................. 56Table 43: LED state definitions for the PROFINET IOController protocol.............................. 56Table 44: LED states for the EtherCAT Master protocol ......................................................... 57Table 45: LED state definitions for the EtherCAT Master protocol.......................................... 57Table 46: LED states for the EtherNet/IP Adapter protocol..................................................... 58Table 47: LED state definitions for the EtherNet/IP Scanner protocol .................................... 58Table 48: Technical data netHOST for Fieldbus systems (Part 1) .......................................... 59Table 49: Technical data netHOST for Fieldbus systems (Part 2) .......................................... 60Table 50: Technical data netHOST for RealTime Ethernet systems ..................................... 61Table 51: Technical data PROFIBUS DP Master protocol...................................................... 62Table 52: Technical data CANopen Master protocol............................................................... 63Table 53: Technical data DeviceNet Master protocol.............................................................. 64Table 54: Technical data PROFINET IO RT Controller........................................................... 65Table 55: Technical data EtherCAT Master protocol .............................................................. 66Table 56: Technical data EtherNet/IP Scanner (master) protocol........................................... 67


© Hilscher 2013 – 2015

Contacts 72/72

Contacts

HEADQUARTERS

GermanyHilscher Gesellschaft für Systemautomation mbHRheinstrasse 15D65795 HattersheimPhone: +49 (0) 6190 99070Fax: +49 (0) 6190 990750EMail: [email protected]: +49 (0) 6190 990799EMail: [email protected]

SUBSIDIARIES

ChinaHilscher Systemautomation (Shanghai) Co. Ltd.200010 ShanghaiPhone: +86 (0) 2163555161EMail: [email protected]: +86 (0) 2163555161EMail: [email protected]

FranceHilscher France S.a.r.l.69500 BronPhone: +33 (0) 4 72 37 98 40EMail: [email protected]: +33 (0) 4 72 37 98 40 EMail: [email protected]

IndiaHilscher India Pvt. Ltd.Pune, Delhi, MumbaiPhone: +91 8888 750 777EMail: [email protected]

ItalyHilscher Italia S.r.l.20090 Vimodrone (MI)Phone: +39 02 25007068EMail: [email protected]: +39 02 25007068EMail: [email protected]

JapanHilscher Japan KKTokyo, 1600022Phone: +81 (0) 353620521EMail: [email protected]: +81 (0) 353620521EMail: [email protected]

KoreaHilscher Korea Inc.Seongnam, Gyeonggi, 463400Phone: +82 (0) 317893715EMail: [email protected]

SwitzerlandHilscher Swiss GmbH 4500 SolothurnPhone: +41 (0) 32 623 6633EMail: [email protected]: +49 (0) 6190 990799EMail: [email protected]

USAHilscher North America, Inc. Lisle, IL 60532Phone: +1 6305055301EMail: [email protected]: +1 6305055301EMail: [email protected]


© Hilscher 2013 – 2015

mailto:[email protected]
















netHOST NHST-T100 - LAN controlled master devices UM 04 EN · T100EN/PNM/ECM/EIM devices, but firmware has to be loaded into the device by the customer) This document also features

Documents