netBRICK NB 100 - Gateway Devices

netBRICK NB 100 - Gateway Devices

User Manual netBRICK NB 100

Gateway Devices

Hilscher Gesellschaft für Systemautomation mbH www.hilscher.com

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public

Introduction 2/122

Table of Contents

1

INTRODUCTION.........................................................................................................6

1.1

About the User Manual ...............................................................................................6

1.1.1

Obligation to read and understand the Manual ....................................................6

1.1.2

1.1.3

List of Revisions ...................................................................................................7

Conventions in this Manual ..................................................................................8

1.2

Reference to Hardware, Software, Driver and Firmware............................................9

1.3

Contents of the Product DVD ...................................................................................10

1.3.1

1.3.2

1.3.3

Directory Structure of the DVD...........................................................................10

Device Description Files.....................................................................................11

Documentation for netBRICK .............................................................................12

1.4

Legal Notes...............................................................................................................15

1.4.1

Copyright ............................................................................................................15

1.4.2

Important Notes ..................................................................................................15

1.4.3

Exclusion of Liability ...........................................................................................16

1.4.4

1.4.5

1.4.6

Warranty .............................................................................................................16

Export Regulations .............................................................................................17

Registered Trademarks......................................................................................17

2

SAFETY ....................................................................................................................18

2.1

General Note ............................................................................................................18

2.2

Intended Use ............................................................................................................18

2.3

Personnel Qualification.............................................................................................18

2.4

References Safety ....................................................................................................18

2.5

Safety Instructions to avoid Personal Injury..............................................................19

2.5.1

Use in Hazardous Locations only in Scope of the UL Standards ......................19

2.5.2

Danger of unsafe System Operation..................................................................19

2.6

Safety Instructions to avoid Property Damage .........................................................20

2.6.1

Device Destruction by exceeding allowed Supply Voltage ................................20

2.6.2

Electrostatically sensitive Devices......................................................................20

2.6.3

Danger of unsafe System Operation..................................................................20

2.7

Labeling of Safety Messages....................................................................................21

3

DESCRIPTION AND REQUIREMENTS ...................................................................22

3.1

Device Description....................................................................................................22

3.2

Device Names ..........................................................................................................23

3.3

Protocol Conversions................................................................................................24

3.3.1

3.3.2

Protocol Conversion - Ethernet to Fieldbus .......................................................24

Protocol Conversion - Serial Protocols to Fieldbus............................................26

3.4

System Requirements ..............................................................................................27

3.5

Configuration Requirements .....................................................................................27

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 3/122

3.6

Licenses....................................................................................................................28

4

DEVICE DRAWINGS AND CONNECTIONS ............................................................29

4.1

Dimensioned Drawing...............................................................................................29

4.2

Drilling Template.......................................................................................................29

4.3

Device Label .............................................................................................................30

4.4

Positions of LEDs and Control Elements..................................................................31

4.4.1

Elements of the netBRICK NB 100-RE-xx Device .............................................31

4.4.2

Elements of the netBRICK NB 100-RS-xx Device .............................................32

4.5

Connections..............................................................................................................33

4.5.1

X1 Power Supply PWR ......................................................................................33

4.5.2

X2 Front Connection...........................................................................................34

4.5.3

4.5.4

X3 Fieldbus Connection .....................................................................................36

Diagnostic Interface............................................................................................39

4.6

Schematic Diagram - Galvanic Isolation...................................................................41

4.6.1

Galvanic Isolation NB 100-RE-DP Device .........................................................41

4.6.2

Galvanic Isolation NB 100-RE-DN/CO Device...................................................43

4.6.3

4.6.4

Galvanic Isolation NB 100-RS-DP Device .........................................................44

Galvanic Isolation NB 100-RS-DN/CO Device...................................................45

5

MOUNTING AND DISMOUNTING............................................................................46

5.1

Safety Messages on Personal Injury ........................................................................46

5.1.1

Use in Hazardous Locations only in Scope of the UL Standards ......................46

5.1.2

Danger of unsafe System Operation..................................................................46

5.2

Property Damage Messages ....................................................................................47

5.2.1

Device Destruction by exceeding allowed Supply Voltage ................................47

5.2.2

5.2.3

Electrostatically sensitive Devices......................................................................47

Danger of unsafe System Operation..................................................................47

5.3

Mounting ...................................................................................................................48

5.3.1

Use in Hazardous Locations only in Scope of the UL Standards ......................48

5.4

Dismounting..............................................................................................................49

5.4.1

Use in Hazardous Locations only in Scope of the UL Standards ......................49

6

INSTALL DRIVER .....................................................................................................50

7

COMMISSIONING ....................................................................................................51

7.1

Commissioning .........................................................................................................51

7.2

Maintainance ............................................................................................................51

7.3

Boot up Behavior ......................................................................................................52

7.3.1

Boot up Behavior on valid Firmware ..................................................................52

7.3.2

Boot up Behavior on invalid Firmware................................................................52

8

TROUBLESHOOTING ..............................................................................................61

8.1

Failure in 10 MBit/s Half Duplex Mode and Workaround..........................................62

9

LEDS.........................................................................................................................63

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 4/122

9.1

LED SYS...................................................................................................................63

9.2

LED APL ...................................................................................................................63

9.3

LEDs Real Time Ethernet Systems ..........................................................................64

9.3.1

9.3.2

9.3.3

9.3.4

LED EtherCAT Master........................................................................................64

LED EtherCAT Slave..........................................................................................65

LED EtherNet/IP Scanner (Master) ....................................................................67

LED EtherNet/IP Adapter (Slave).......................................................................68

9.3.5

9.3.6

9.3.7

9.3.8

9.3.9

9.3.10

LED Open Modbus/TCP.....................................................................................69

LED POWERLINK Controlle Node/Slave...........................................................70

LED PROFINET IO RT Controller ......................................................................72

LED PROFINET IO-RT-Device ..........................................................................73

LED sercos Master.............................................................................................74

LED sercos Slave ...............................................................................................76

9.4

LEDs Fieldbus Systems............................................................................................77

9.4.1

9.4.2

LED PROFIBUS DP Master ...............................................................................77

LED PROFIBUS DP Slave .................................................................................77

9.4.3

9.4.4

9.4.5

9.4.6

LED CANopen Master........................................................................................78

LED CANopen Slave..........................................................................................79

LED DeviceNet Master.......................................................................................80

LED DeviceNet Slave.........................................................................................80

9.5

LEDs Serial...............................................................................................................81

9.5.1

9.5.2

9.5.3

LED Modbus RTU ..............................................................................................81

LED ASCII ..........................................................................................................81

LED 3964R .........................................................................................................82

10 TECHNICAL DATA ...................................................................................................83

10.1

Technical Data netBRICK NB 100 Gateway.............................................................83

10.2

Technical Data Real-Time Ethernet Protocols..........................................................87

10.2.1

EtherCAT Master................................................................................................87

10.2.2

10.2.3

10.2.4

10.2.5

10.2.6

EtherCAT Slave..................................................................................................87

EtherNet/IP Scanner (Master) ............................................................................88

EtherNet/IP Adapter (Slave)...............................................................................89

Open Modbus/TCP.............................................................................................90

POWERLINK Controlled Node (Slave) ..............................................................90

10.2.7

10.2.8

10.2.9

PROFINET IO-RT-Controller..............................................................................91

PROFINET IO-RT-Device ..................................................................................92

sercos Master .....................................................................................................93

10.2.10

sercos Slave .......................................................................................................94

10.3

Technical Data Fieldbus Protocols ...........................................................................95

10.3.1

CANopen Master ................................................................................................95

10.3.2

10.3.3

CANopen Slave ..................................................................................................96

DeviceNet Master...............................................................................................97

10.3.4

10.3.5

10.3.6

DeviceNet Slave .................................................................................................98

PROFIBUS DP Master .......................................................................................99

PROFIBUS DP Slave .......................................................................................100

10.4

Technical Data serial Protocols ..............................................................................101

10.4.1

ASCII ................................................................................................................101

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction

10.4.2

10.4.3

5/122

Modbus RTU Master/Slave ..............................................................................102

3964R ...............................................................................................................103

11 WIRING INSTRUCTIONS .......................................................................................104

11.1

PROFIBUS .............................................................................................................104

11.2

CANopen ................................................................................................................106

11.3

DeviceNet ...............................................................................................................107

11.4

Ethernet ..................................................................................................................109

11.5

RS-232....................................................................................................................110

11.6

RS-422....................................................................................................................111

11.7

RS-485....................................................................................................................113

12 DECOMMISSIONING/DISPOSAL...........................................................................115

12.1

Decommissioning ...................................................................................................115

12.2

Disposal of Waste Electronic Equipment................................................................115

13 GLOSSARY.............................................................................................................116

14 APPENDIX ..............................................................................................................118

14.1

List of Figures .........................................................................................................118

14.2

List of Tables ..........................................................................................................119

14.3

Contacts..................................................................................................................122

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 6/122

1 Introduction

1.1 About the User Manual

This user manual describes the hardware, installation, commissioning, and operation of the netBRICK NB 100 series of gateways.

1.1.1 Obligation to read and understand the Manual

Important!

 To avoid personal injury and to avoid property damage to your system or to your device, you must read and understand all instructions in the manual and all accompanying texts to your device, before installing and operating your device.

 First read the Safety Instructions in the safety chapter.

 Obey to all Safety Messages in the manual.

 Keep the product DVD providing the product manuals. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 7/122

1.1.2 List of Revisions

Index Date Chapter Revisions

8 2012-11-07

Firmware Version 1.5.x.x

3.5 Section Configuration Requirements: Windows 2000 removed, Windows Vista

and Windows 7 added.

9.4.2 Section

updated.

9.4.4 Section

: State for baurate detection added.

10.2.3 Section EtherNet/IP Scanner (Master):

- Maximum number of total cyclic input data of 5760 reduced to 5712 bytes,

- Device Level Ring as Beacon based ‚Ring Node’ supported,

- Address Conflict Detection supported.

10.2.10 Section sercos Slave:

- Maximum number of cyclic input data and output data reduced from 200 to 128 bytes each,

- NRT channel supported: only forwarding and S/IP.

10.3.2 Section CANopen Slave:

- Event timer added,

- Auto baudrate detection is supported.

10.3.5 Section PROFIBUS DP Master:

- Maximum number of total cyclic input data extended from 3584 to 5712 bytes,

- Maximum number of total cyclic output data extended from 3584 to 5760 bytes.

10.3.6 Section PROFIBUS DP Slave: Maximum number of modules: Max. 4 input mo-

dules and max. 4 output modules, max. 24 modules when using manual setting.

9 2013-02-04 1.3.3 Section

updated.

10 2013-06-26 6

Installation program of USB driver added.

11 2014-03-11 1.3.1 Section updated.

12 2014-03-24 7.3

10.2.5

Paths to DVD updated in section Boot up Behavior.

Section Open Modbus/TCP: Information added: ‚Maximum number of connec-

tions is 16’.

11.2

Maximum cable length for 1 MBit/s is 30 m.

13 2015-01-26 10.1

UL recognized: UL 1604 and UL 508

Table 1: List of Revisions

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 8/122

1.1.3 Conventions in this Manual

Operation instructions, a result of an operation step or notes are marked as follows:

Operation Instructions:

 <instruction> or

1. <instruction>

2. <instruction>

Results:

 <result>

Notes:

Important:

<important note>

Note:

<note>

<note, where to find further information>

Safety Messages

For information about the labeling of safety messages refer to section

Labeling of Safety Messages

on page 21.

Numbering

... reference to the figure used in that section. If the numbers reference to a section outside the current section then a cross reference to that section and figure is indicated. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 9/122

1.2 Reference to Hardware, Software, Driver and Firmware

Hardware

Device Type

NB 100-RE-CO

NB 100-RE-DP

NB 100-RE-DN

NB 100-RS-CO

NB 100-RS-DP

NB 100-RS-DN

Revision

Revision 3

Revision 3

Revision 4

Revision 3

Revision 2

Revision 2

Table 2: Reference to Hardware

Port X2

Ethernet

Ethernet

Ethernet

RS interface

RS interface

RS interface

Port X3

CANopen

PROFIBUS DP

DeviceNet

CANopen

PROFIBUS DP

DeviceNet

Software

Software

SYCONnet netX setup.exe

Table 3: Reference to Software

Software Version

1.351.x.x and higher

Driver

Driver

USB Driver

Table 4: Reference to Driver

Software Version

USB Driver of Windows

®

Firmware

Firmware for the protocol conversion: see section Protocol Conversions on page 24.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 10/122

1.3 Contents of the Product DVD

The product DVD for the netBRICK NB 100 contains:

 Setup program for the configuration and diagnostic program SYCON.net

 USB Driver

 Documentation

 Firmware

 Device Description Files (GSD, GSDML, EDS, ...)

 Video-Audio Tutorials

 Presentation about netSCRIPT (relevant for netTAP NT 100 only)

1.3.1 Directory Structure of the DVD

All manuals on this DVD are delivered in the Adobe Acrobat

®

Reader format (PDF).

Directory Name

Documentation

Electronic Data Sheets (e.g.

EDS, GSD, GSDML)

Description

Documentation in the Acrobat

®

Reader Format (PDF)

Device Description File fscommand

Setups & Drivers

Supplements & Examples

Training & Podcasts

Files used during installation

Configuration and diagnostic software SYCON.net

USB Driver for netTAP NT 100 and netBRICK NB 100

Debugger software for netSCRIPT (relevant for netTAP NT

100 only)

Lua for Windows (relevant for netTAP NT 100 only)

Tool for recovery of netTAP 100 devices respectively net-

BRICK NB 100 devices

Examples for SYCON.net

Examples for netSCRIPT (relevant for netTAP NT 100 only)

Links to websites about Modbus

Videos about commissioning

Table 5: Directory Structure of the DVD

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 11/122

1.3.2 Device Description Files

The directory EDS on the DVD provides device description files for the net-

BRICK NB 100 device.

netBRICK NB 100 as File name

CANopen Slave

DeviceNet Slave

EtherCAT Slave

EtherNet/IP Adapter

POWERLINK Slave

PROFIBUS DP Slave

PROFINET IO Device sercos Slave

NB100_CO_COS.eds

NB100_DN_DNS.EDS

Hilscher NB 100-ECS-XX V2.2.xml

HILSCHER NB 100-RE EIS V1.1.EDS

00000044_NB100PLS-64O_64I.xdd

00000044_NB100PLS-512O_512I.xdd

HIL_0C9C.GSD

GSDML-V2.2-HILSCHER-NB 100-RE PNS-20120806-

143000.xml

Hilscher NB100 RE S3S FixCFG FSPIO Default.xml only for default settings.

Note

: Use the SDDML export function in SYCON.net to create a suitable SDDML file.

Table 6: Device Description Files for netBRICK NB 100 on the DVD

The device description files are for the configuration of the used master. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 12/122

1.3.3 Documentation for netBRICK

The following documentation overview gives information, for which items you can find further information in which manual.

Note:

Further information:

All manuals listed in the overview below can be found in the Documentation directory on the DVD delivered, in the Adobe Acrobat® Reader format

(PDF).

Manual

User Manual

User Manual

Operating Instruction Manual

Basic documentation for netTAP NT 100

You always need the following documents:

Contents

netBRICK NB 100

Installation, Operation and Hardware

Software Installation

Gateway Solutions

Configuration of Gateway and Proxy Devices netTAP, netBRICK and netLINK

Step by step description of the configuration of the netBRICK NB 100.

Configuration of the netBRICK NB 100 as

EtherCAT Slave,

EtherNet/IP Adapter,

Open Modbus/TCP,

POWERLINK controlled Node,

PROFINET IO Device, sercos Slave

CANopen Slave,

DeviceNet Slave respectively

PROFIBUS DP Slave

Document name

netBRICK NB 100 - Gateway Devices UM xx EN.pdf

(this manual)

Software Installation - Gateway Solutions UM xx EN.pdf

Configuration of Gateway and Proxy Devices OI xx EN.pdf

Table 7: Basic Documentation for netBRICK NB 100

Manual

Operating Instruction Manual

Operating Instruction Manual

netBRICK NB 100 with EtherCAT Master

You need the following additional documents, if you use the protocol

EtherCAT Master on the gateway device:

Contents

DTM for EtherCAT Master devices

Generic DTM for EtherCAT Slave devices

Document name

EtherCAT Master DTM OI xx EN.pdf

EtherCAT Generic Slave DTM OI xx EN.pdf

Table 8: Additional Documentation for netBRICK NB 100 with EtherCAT Master

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 13/122

Manual

Operating Instruction Manual

Operating Instruction Manual

Operating Instruction Manual

netBRICK NB 100 with EtherNet/IP Scanner/Master

You need the following additional documents, if you use the protocol

EtherNet/IP Scanner/Master on the gateway device:

Contents

DTM for EtherNet/IP Scanner devices

Document name

EtherNetIP Scanner DTM OI xx EN.pdf

Generic DTM from EDS File EtherNet/IP

Adapter Devices

EtherNetIP Generic Adapter DTM EDS OI xx EN.pdf

Generic DTM for EtherNet/IP Adapter devices EtherNetIP Generic Adapter DTM OI xx EN.pdf

Table 9: Additional Documentation for netBRICK NB 100 with EtherNet/IP Scanner/Master

Manual

Operating Instruction Manual

Operating Instruction Manual

netBRICK NB 100 with PROFINET IO Controller

You need the following additional documents, if you use the protocol

PROFINET IO Controller on the gateway device:

Contents

DTM for PROFINET IO Controller devices

Document name

PROFINET IO Controller DTM OI xx EN.pdf

Generic DTM for PROFINET IO Device devices

PROFINET IO Generic Device DTM IO xx EN.pdf

Table 10: Additional Documentation for netBRICK NB 100 with PROFINET IO Controller

Manual

Operating Instruction Manual

Operating Instruction Manual

netBRICK NB 100 with sercos Master

You need the following additional documents, if you use the protocol sercos Master on the gateway device:

Contents

DTM for sercos Master devices

Generic DTM for sercos Slave devices

Document name

sercos Master DTM OI xx EN.pdf sercos Generic Slave DTM OI xx EN.pdf

Table 11: Additional Documentation for netBRICK NB 100 with EtherCAT Master

Manual

Operating Instruction Manual

Operating Instruction Manual

netBRICK NB 100 with CANopen Master

You need the following additional documents, if you use the protocol

CANopen Master on the gateway device:

Contents

DTM for CANopen Master devices

Generic DTM for CANopen Slave devices

Document name

CANopen Master DTM OI xx EN.pdf

CANopen Generic Slave DTM OI xx EN.pdf

Table 12: Additional Documentation for netBRICK NB 100 with CANopen Master

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 14/122

Manual

Operating Instruction Manual

Operating Instruction Manual

netBRICK NB 100 with DeviceNet Master

You need the following additional documents, if you use the protocol

DeviceNet Master on the gateway device:

Contents

DTM for DeviceNet Master devices

Generic DTM for DeviceNet Slave devices

Document name

DeviceNet Master DTM OI xx EN.pdf

DeviceNet Generic Slave DTM OI xx EN.pdf

Table 13: Additional Documentation for netBRICK NB 100 with DeviceNet Master

Manual

Operating Instruction Manual

Operating Instruction Manual

netBRICK NB 100 with PROFIBUS DP Master

You need the following additional documents, if you use the protocol

PROFIBUS DP Master on the gateway device:

Contents

DTM for PROFIBUS DP Master devices

Document name

PROFIBUS DP Master DTM OI xx EN.pdf

Generic DTM for PROFIBUS DP Slave devices

PROFIBUS DP Generic Slave DTM OI xx EN.pdf

Table 14: Additional Documentation for netBRICK NB 100 with PROFIBUS DP Master

Manual

User Manual

netBRICK NB 100 with ASCII

You need the following additional documents, if you use the ASCII protocol on the gateway device:

Contents

ASCII Handshake Mechanism

Document name

ASCII – Handshake Mechanism UM xx EN.pdf

Table 15: Additional Documentation for netBRICK NB 100 with ASCII

Manual

User Manual

netBRICK NB 100 with 3964R

You need the following additional documents, if you use the 3964R protocol on the gateway device:

Contents

3964R Handshake Mechanism

Document name

3964R – Handshake Mechanism UM xx

EN.pdf

Table 16: Additional Documentation for netBRICK NB 100 with 3964R

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 15/122

1.4 Legal Notes

1.4.1 Copyright

© Hilscher, 2009-2015, Hilscher Gesellschaft für Systemautomation mbH

All rights reserved.

The images, photographs and texts in the accompanying material (user manual, accompanying texts, documentation, etc.) are protected by German and international copyright law as well as international trade and protection provisions. You are not authorized to duplicate these in whole or in part using technical or mechanical methods (printing, photocopying or other methods), to manipulate or transfer using electronic systems without prior written consent. You are not permitted to make changes to copyright notices, markings, trademarks or ownership declarations. The included diagrams do not take the patent situation into account. The company names and product descriptions included in this document may be trademarks or brands of the respective owners and may be trademarked or patented. Any form of further use requires the explicit consent of the respective rights owner.

1.4.2 Important Notes

The user manual, accompanying texts and the documentation were created for the use of the products by qualified experts, however, errors cannot be ruled out. For this reason, no guarantee can be made and neither juristic responsibility for erroneous information nor any liability can be assumed.

Descriptions, accompanying texts and documentation included in the user manual do not present a guarantee nor any information about proper use as stipulated in the contract or a warranted feature. It cannot be ruled out that the user manual, the accompanying texts and the documentation do not correspond exactly to the described features, standards or other data of the delivered product. No warranty or guarantee regarding the correctness or accuracy of the information is assumed.

We reserve the right to change our products and their specification as well as related user manuals, accompanying texts and documentation at all times and without advance notice, without obligation to report the change.

Changes will be included in future manuals and do not constitute any obligations. There is no entitlement to revisions of delivered documents. The manual delivered with the product applies.

Hilscher Gesellschaft für Systemautomation mbH is not liable under any circumstances for direct, indirect, incidental or follow-on damage or loss of earnings resulting from the use of the information contained in this publication. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 16/122

1.4.3 Exclusion of Liability

The software was produced and tested with utmost care by Hilscher Gesellschaft für Systemautomation mbH and is made available as is. No warranty can be assumed for the performance and flawlessness of the software for all usage conditions and cases and for the results produced when utilized by the user. Liability for any damages that may result from the use of the hardware or software or related documents, is limited to cases of intent or grossly negligent violation of significant contractual obligations. Indemnity claims for the violation of significant contractual obligations are limited to damages that are foreseeable and typical for this type of contract.

It is strictly prohibited to use the software in the following areas:

 for military purposes or in weapon systems;

 for the design, construction, maintenance or operation of nuclear facilities;

 in air traffic control systems, air traffic or air traffic communication systems;

 in life support systems;

 in systems in which failures in the software could lead to personal injury or injuries leading to death.

We inform you that the software was not developed for use in dangerous environments requiring fail-proof control mechanisms. Use of the software in such an environment occurs at your own risk. No liability is assumed for damages or losses due to unauthorized use.

1.4.4 Warranty

Although the hardware and software was developed with utmost care and tested intensively, Hilscher Gesellschaft für Systemautomation mbH does not guarantee its suitability for any purpose not confirmed in writing. It cannot be guaranteed that the hardware and software will meet your requirements, that the use of the software operates without interruption and that the software is free of errors. No guarantee is made regarding infringements, violations of patents, rights of ownership or the freedom from interference by third parties. No additional guarantees or assurances are made regarding marketability, freedom of defect of title, integration or usability for certain purposes unless they are required in accordance with the law and cannot be limited. Warranty claims are limited to the right to claim rectification. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Introduction 17/122

1.4.5 Export Regulations

The delivered product (including the technical data) is subject to export or import laws as well as the associated regulations of different counters, in particular those of Germany and the USA. The software may not be exported to countries where this is prohibited by the United States Export

Administration Act and its additional provisions. You are obligated to comply with the regulations at your personal responsibility. We wish to inform you that you may require permission from state authorities to export, reexport or import the product.

1.4.6 Registered Trademarks

Windows

®

XP, Windows

®

Vista and Windows

®

7 are registered trademarks of Microsoft Corporation.

Adobe-Acrobat

®

is a registered trademark of the Adobe Systems Incorporated.

CANopen

®

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

DeviceNet

® and EtherNet/IP

Vendor Association, Inc).

®

are trademarks of ODVA (Open DeviceNet

EtherCAT

®

is a registered trademark and a patented technology of Beckhoff Automation GmbH, Verl, Bundesrepublik Deutschland

, formerly Elektro

Beckhoff GmbH.

Modbus

®

is a registered trademark of Schneider Electric.

Powerlink is a registered trademark of B&R, Bernecker + Rainer Industrie-

Elektronik Ges.m.b.H, Eggelsberg, Austria

PROFIBUS and PROFINET are registered trademarks of PROFIBUS International, Karlsruhe. sercos interface

® is a registered trademark of sercos International e. V.,

Suessen, Germany.

All other mentioned trademarks are property of their respective legal owners. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Safety 18/122

2 Safety

2.1 General Note

The user manual, the accompanying texts and the documentation are written for the use of the products by educated personnel. When using the products, all safety instructions, safety messages and all valid legal regulations have to be obeyed. Technical knowledge is presumed. The user has to assure that all legal regulations are obeyed.

2.2 Intended Use

In this manual described devices: are devices for communication and connect two communication networks.

The NB 100 devices work as gateways between these two networks.

The NB 100 devices are made of a compact housing with IP 67 conformity and are designed for the mounting on a metallic underground.

2.3 Personnel Qualification

The netBRICK NB 100 Gateway must only be installed, configured and removed by qualified personnel. Job-specific technical skills for people professionally working with electricity must be present concerning the following topics:

 Safety and health at work

 Mounting and attaching of electrical equipment

 Measurement and Analysis of electrical functions and systems

 Evaluation of the safety of electrical systems and equipment

 Installing and configuring IT.

2.4 References Safety

[1] ANSI Z535.6-2006 American National Standard for Product Safety Information in

Product Manuals, Instructions, and Other Collateral Materials

[2] EN 61340-5-1 and EN 61340-5-2 as well as IEC 61340-5-1 and IEC 61340-5-2

[3] UL-Report/File E326833 (Project 10CA56304, July 22, 2011) netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Safety 19/122

2.5 Safety Instructions to avoid Personal Injury

To ensure your own personal safety and to avoid personal injury, you necessarily must read, understand and follow the following safety instructions and all safety messages in this manual about danger causing personal injury, before you install and operate your netBRICK NB 100 device.

2.5.1 Use in Hazardous Locations only in Scope of the UL Standards

Important!

Outside the scope of the UL standards you are allowed to use the netBRICK NB 100 device in non-hazardous locations only!

You are allowed to use the netBRICK NB 100 device in hazardous locations with potentially explosive atmosphere only in scope of the UL Standards and if the conditions given in the UL-Report/File E326833 (Project

10CA56304, July 22, 2011) are adhered.

According to UL Report/File E326833 the netBRICK NB 100 device is suitable for use in NEC500 Class I, Division 2, Groups A, B, C, and D OR

non-hazardous

locations only. The diagnostic interface DIAG (USB connector located in the diagnostic area) of the netBRICK NB 100 device is not suitable for the use in hazardous locations with potentially explosive atmosphere.

When using the device in hazardous locations with potentially explosive atmosphere according to UL you must observe the following safety instructions.

 Do not connect or disconnect the netBRICK NB 100 device unless power has been removed or the area is known to be non-hazardous.

 Substitution of components may impair suitability for NEC500 Class I,

Division 2, Groups A, B, C, and D.

 Do not use the diagnostic interface DIAG (USB connector) of the net-

BRICK NB 100 device in hazardous locations. Use the diagnostic interface DIAG only, if power has been removed or the area is known to be non-hazardous.

 Use only a power supply specified according to the UL standard.

2.5.2 Danger of unsafe System Operation

To prevent harm of persons, do not remove this device under runtime conditions before you can not guarantee further a safe and secure operation of the plant. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Safety 20/122

2.6 Safety Instructions to avoid Property Damage

To avoid property damage respectively device destruction of the netBRICK

NB 100 device, you necessarily must read, understand and follow the following safety instructions and all safety messages in this manual about danger causing property damage, before you install and operate your net-

BRICK NB 100 device.

2.6.1 Device Destruction by exceeding allowed Supply Voltage

Adhere for all netBRICK NB 100 device described in this manual the instruction hereafter:

The netBRICK NB 100 may only be operated with the specified supply voltage. Make sure that the limits of the allowed range for the supply voltage are not exceeded. A supply voltage above the upper limit can cause severe damage to the netBRICK NB 100! A supply voltage below the lower limit can cause malfunction in the netBRICK NB 100. The allowed range for the supply voltage is defined by the tolerances specified in this manual.

The data on the mandatory supply voltage for the netBRICK NB 100 de-

vice you find in the section System Requirements on page 27. There the

required and permitted supply voltage for the netBRICK NB 100 device is provided inclusively the permitted tolerance range.

2.6.2 Electrostatically sensitive Devices

This equipment is sensitive to electrostatic discharge, which cause internal damage and affect normal operation. Befor you open the diagnostic interface DIAG (USB connector) of the netBRICK NB 100 device follow the guidelines:

 Touch a grounded object to discharge potential static.

 Wear an approved grounding wriststrap.

 Do not touch connectors or pins on the netBRICK NB 100 device.

 If available, use a static-safe workstation.

 When not in use, store the equipment in appropriate static-safe packaging.

Reference Safety [S2]

2.6.3 Danger of unsafe System Operation

To prevent property damage, do not remove this device under runtime conditions before you can not guarantee further a safe and secure operation of the plant. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Safety 21/122

2.7 Labeling of Safety Messages

Safety Symbol

 The Section Safety Messages at the beginning of a chapter are pinpointed particularly. They are highlighted with a specific safety symbol and a signal word according to the degree of endangerment. Inside the safety message the danger is exactly named.

 The Integrated Safety Messages within a instruction description are highlighted with a signal word according to the degree of endangerment and possibly by an principle symbol. Inside the safety message the danger is exactly named.

Safety Symbol

(USA)

Sort of Warning or Principle

Warning of Personal Injury and Property Damage Message

USA:

Warning of Personal Injury

As in the scope of the ANSI Z535 Standard (for USA) instructions to a property damage message may not contain a warning triangle, this property damage messages are listed separatly for the USA.

Warning of Danger by Explosion Hazard

Warning of Damages by Electrostatic Discharge

Signal Word

Note

Table 17: Safety Symbols and Sort of Warning or Principle

Meaning

Indicates a possible hazard with medium risk, which will have as consequence death or

(grievous) bodily harm if it isn't avoided.

Indicates a minor hazard with medium risk, which could have as consequence simple battery if it isn't avoided.

Indicates a Property Damage Message.

Indicates an important note in the manual.

Table 18: Signal Words

Meaning (USA)

Indicates a Hazardous Situation Which, if not

Avoided, could Result in Death or Serious Injury.

Indicates a Hazardous Situation Which, if not

Avoided, may Result in Minor or Moderate Injury.

Indicates a Property Damage Message.

Indicates an Important Note in the Manual.

In this document all Safety Instructions and Safety Messages are designed according both to the international used safety conventions as well as to the ANSI Z535 standard, refer to reference safety [S1]. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Description and Requirements 22/122

3 Description and Requirements

3.1 Device Description

The netBRICK NB100 devices described in this manual are communication devices that are connecting two networks to each other. The NB 100 devices are operating as gateway between both networks.

The netBRICK 100 is a device with two interface ports. Its principle func-

tionality shows Figure 1. The function of the device is determined by the

loaded firmware and the loaded configuration.

Figure 1: Function netBRICK

Basically it is possible to connect either to port X2 or X3 to a host or to field devices.

The device is configured via the USB interface (behind the covering cap) by a PC and the software SYCON.net. Online diagnostics is possible via the same interface.

The installation and operation of the configuration tool SYCON.net is described in the documentation Configuration of Gateway and Proxy Devices

OI xx EN.pdf

and located in the documents folder of the DVD included in the delivery.

The firmware buffers the cyclic send and receive data of the port X2 protocol and the X3 protocol internally. The configuration tool enables the flexible mapping of the receive data of protocol X2 to send data of the protocol

X3 and vice versa.

Status information of the protocol at port X2 can be mapped into the send data of the protocol at port X3 and vice versa. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Description and Requirements 23/122

The firmware of netBRICK NB100 as gateway does not support acyclic communications or special services of the supported protocols.

The devices have a plastic housing and moulded electronics and complies to the IP67 level of protection. The device is protected against dust ingress and water in harmful quantity.

All connections are realized as M12 connectors (in accordance with

DIN EN 61076-2-101/ IEC 61076-2-101) with different codings.

3.2 Device Names

The descriptive device name of netBRICK devices consists of the following parts

1. Device type netBRICK NB100

2. Network at X2 (middle part of the device). The example shows RE for

Real-Time Ethernet.

3. Network at X3 (upper part of the device). The example shows DP for

PROFIBUS DP.

The following interfaces are currently supported at the primary network X2:

Code Interface

RE

RS

Real-Time Ethernet (2* RJ45)

Serial Interfaces: RS-232, RS-422, RS-485 (2 x M12, B coded, female connector)

Table 19: Network on Port X2 (Primary Network)

The following interfaces are currently supported at the secondary network

X3:

Code Interface

DP

CO

DN

PROFIBUS DP (M12, B coded, 1 x female connector, 1 x male connector)

CANopen (M12, A coded, 1 x female connector, 1 x male connector)

DeviceNet (M12, A coded, 1 x female connector, 1 x male connector)

Table 20: Network on Port X3 (Secondary Network)

Accordingly to the protocol at port X3 the LED

(in Figure 5: LEDs and

Control Elements

on page 31) is labeled.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Description and Requirements 24/122

3.3 Protocol Conversions

Information about the configuration of the protocol conversion of the device is in the operating instruction manual Configuration of Gateway and

Proxy Devices OI xx EN.pdf

on the DVD in the directory Documentation.

3.3.1 Protocol Conversion - Ethernet to Fieldbus

Device Name

NB 100-RE-CO

The netBRICK NB 100 connects to Ethernet on port X2 and connects to fieldbus on port X3.

The following devices support this:

Ethernet Protocol (X2) Fieldbus Protocol (X3) Firmware File Firmware

Version

1.5.x.x EtherCAT Master

EtherCAT Slave

CANopen Slave

CANopen Master

EtherCAT Slave CANopen Slave

EtherNet/IP Scanner / Master CANopen Slave

EtherNet/IP Adapter / Slave CANopen Master

EtherNet/IP Adapter / Slave

Open Modbus/TCP

Open Modbus/TCP

POWERLINK Slave

POWERLINK Slave

PROFINET IO Controller

PROFINET IO Device

PROFINET IO Device sercos Master sercos Slave sercos Slave

CANopen Slave

CANopen Master

CANopen Slave

CANopen Master

CANopen Slave

CANopen Slave

CANopen Master

CANopen Slave

CANopen Slave

CANopen Master

CANopen Slave

NBECMCOS.NXF

NBECSCOM.NXF

NBECSCOS.NXF

NBEIMCOS.NXF

NBEISCOM.NXF

NBEISCOS.NXF

NBOMBCOM.NXF

NBOMBCOS.NXF

NBPNSCOM.NXF

NBPNSCOS.NXF

NBPNMCOS.NXF

NBPNSCOM.NXF

NBPNSCOS.NXF

NBS3MCOS.NXF

NBS3SCOM.NXF

NBS3SCOS.NXF

Table 21: Protocol Conversion - Ethernet to Fieldbus (Part 1)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Description and Requirements

Device Name Ethernet Protocol (X2)

NB 100-RE-DN

NB 100-RE-DP

25/122

Fieldbus Protocol (X3) Firmware File

EtherCAT Master

EtherCAT Slave

EtherCAT Slave

DeviceNet Slave

DeviceNet Master

DeviceNet Slave

EtherNet/IP Scanner / Master DeviceNet Slave

EtherNet/IP Adapter / Slave DeviceNet Master

EtherNet/IP Adapter / Slave DeviceNet Slave

Open Modbus/TCP

Open Modbus/TCP

POWERLINK Slave

POWERLINK Slave

PROFINET IO Controller

PROFINET IO Device

DeviceNet Master

DeviceNet Slave

DeviceNet Master

DeviceNet Slave

DeviceNet Slave

DeviceNet Master

PROFINET IO Device sercos Master sercos Slave sercos Slave

EtherCAT Master

DeviceNet Slave

DeviceNet Slave

DeviceNet Master

DeviceNet Slave

PROFIBUS DP Slave

EtherCAT Slave

EtherCAT Slave

PROFIBUS DP Master

PROFIBUS DP Slave

EtherNet/IP Scanner / Master PROFIBUS DP Slave

EtherNet/IP Adapter / Slave

EtherNet/IP Adapter / Slave

Open Modbus/TCP

Open Modbus/TCP

POWERLINK Slave

POWERLINK Slave

PROFIBUS DP Master

PROFIBUS DP Slave

PROFIBUS DP Master

PROFIBUS DP Slave

PROFIBUS DP Master

PROFIBUS DP Slave

PROFINET IO Controller

PROFINET IO Device

PROFINET IO Device sercos Master sercos Slave sercos Slave

PROFIBUS DP Slave

PROFIBUS DP Master

PROFIBUS DP Slave

PROFIBUS DP Slave

PROFIBUS DP Master

PROFIBUS DP Slave

Table 22: Protocol Conversion - Ethernet to Fieldbus (Part 2)

NBECMDNS.NXF

NBECSDNM.NXF

NBECSDNS.NXF

NBEIMDNS.NXF

NBEISDNM.NXF

NBEISDNS.NXF

NBOMBDNM.NXF

NBOMBDNS.NXF

NBPNSDNM.NXF

NBPNSDNS.NXF

NBPNMDNS.NXF

NBPNSDNM.NXF

NBPNSDNS.NXF

NBS3MDNS.NXF

NBS3SDNM.NXF

NBS3SDNS.NXF

NBECMDPS.NXF

NBECSDPM.NXF

NBECSDPS.NXF

NBEIMDPS.NXF

NBEISDPM.NXF

NBEISDPS.NXF

NBOMBDPM.NXF

NBOMBDPS.NXF

NBPNSDPM.NXF

NBPNSDPS.NXF

NBPNMDPS.NXF

NBPNSDPM.NXF

NBPNSDPS.NXF

NBS3MDPS.NXF

NBS3SDPM.NXF

NBS3SDPS.NXF

Firmware

Version

1.5.x.x netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Description and Requirements 26/122

3.3.2 Protocol Conversion - Serial Protocols to Fieldbus

Device Name

The netBRICK NB 100 connects to serial interfaces (RS) on port X2 and connects to fieldbus on port X3.

The following devices support this:

Serial Protocol (X2) Fieldbus Protocol (X3) Firmware File Firmware

Version

NB 100-RS-CO

Modbus RTU Master/Slave

Modbus RTU Master/Slave

CANopen Slave

CANopen Master

NBMBRCOS.NXF

NBMBRCOM.NXF

NB 100-RS-DN

Modbus RTU Master/Slave

Modbus RTU Master/Slave

DeviceNet Slave

DeviceNet Master

NBMBRDNS.NXF

NBMBRDNM.NXF

NB 100-RS-DP ASCII

ASCII

Modbus RTU Master/Slave

Modbus RTU Master/Slave

3964R

3964R

PROFIBUS DP Slave

PROFIBUS DP Master

PROFIBUS DP Slave

PROFIBUS DP Master

PROFIBUS DP Slave

PROFIBUS DP Master

Table 23: Protocol Conversion – Serial Protocols to Fieldbus

NBASCDPS.NXF

NBASCDPM.NXF

NBMBRDPS.NXF

NBMBRDPM.NXF

NBNVRDPS.NFX

NBNVRDPM.NFX netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Description and Requirements 27/122

3.4 System Requirements

The netBRICK device has to be mounted on a flat surface. An optimal material is a metal plate (which is connected to potential equalization of the plant) where the device can be screw mounted. In case the surface is not metallic at least the two bottom screw connections have to be extensively connected to potential equalization of the installation site.

A suitable power supply is required. The voltage to be applied must be in the allowed range 24 V ± 6 V DC. The power supply must be able to deliver at least a current of 130 mA at 24 V.

Power is supplied via connector X1.

Device Destruction!

 The voltage must not exceed 30 V significantly, otherwise the device may be destroyed or damaged.

In order to avoid damage caused by overheating or freezing, it is necessary that the temperature of the device does not exceed the limits of the allowed temperature range.

The following preconditions must additionally be met in order to operate the

Gateway device successfully:

1. The Gateway device must have been loaded with the correctly suiting firmware.

2. The Gateway device must have been configured correctly using the configuration and diagnostic software SYCON.net.

3.5 Configuration Requirements

The configuration software SYCON.net must be installed on a PC to configure the netBRICK 100.

The requirements for the PC are:

 PC with 1 GHz processor or higher

 Windows

®

Windows

®

XP SP3, Windows

7 (64 bit)

®

Vista (32 bit) SP2, Windows

®

7 (32 bit) or

 Administrator rights

 Internet Explorer 5.5 or higher

 Free disk space: min. 400 MByte

 DVD ROM drive

 RAM: min. 512 MByte, recommended 1024 MByte

 Graphic resolution: min. 1024 x 768 pixel

 Keyboard and Mouse

 USB

Note:

If the project file is saved and opened again or it is used on another

PC, the system requirements need to match. Particularly the DTMs need to be installed on the used PC. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Description and Requirements 28/122

3.6 Licenses

If the netBRICK NB 100 device is used in conjunction with a firmware that has master functionality (except Modbus RTU or Open Modbus/TCP) a master license in the netBRICK device must be present.

If the device has a master license can be read out with the software

SYCON.net.

Note:

A firmware has to be loaded into the device to read out, if the device has a master license. The base firmware is not sufficient for this purpose.

How to load a firmware into the device and how to read out if the device has a master license is described in the operating instruction manual

Configuration of Gateway and Proxy Devices OI xx EN.pdf

.

The master license can be ordered later with SYCON.net and transferred with SYCON.net into the device. The master license can be ordered with at

Hilscher ‘NXLIC-MASTER’ and has part number 8211.000. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4 Device Drawings and Connections

4.1 Dimensioned Drawing

All dimensions are in mm.

29/122

Figure 2: Dimensioned Drawing

Please take care of the device’s headroom. There is enough space necessary to allow the connection of the connectors and wires since they are all tending upwards.

4.2 Drilling Template

The illustrated drilling template you can get in an actual size for printing on the delivered DVD in the folder „Documentation > netBRICK“. The TIF-File is named „drilling template.tif“.

Figure 3: Drilling Template

Please take into account that the device’s distance is depending on the used connector and cable type. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.3 Device Label

30/122

Figure 4: Device Label

No. Meaning

UL safety instructions for usage in hazardous area.

Logo.

Production month/year

Serial number

Hardware revision.

Hilscher part number.

Ambient temperatur permitted for the device.

Device name, see also section 3.2 on page 23.

Hilscher hompage.

Supply voltage and current consumption of the device. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections 31/122

4.4 Positions of LEDs and Control Elements

4.4.1 Elements of the netBRICK NB 100-RE-xx Device

No. Description

Fieldbus connector OUT (female)

User label

LINK LED / L/A LED

Ethernet connection OUT

Ethernet connector CH1 OUT

ACT LED / Rx/Tx LED

Ethernet connection OUT

COM1 LED, protocol dependent

APL LED

Covering cap for the diagnostic port. Underneath the cover you will find the USB service port and a push button used during manufacturing

Screw hole for connection to potential equalization

User label

Screw hole for connection to potential equalization

Connector PWR for power supply

SYS LED

COM0 LED, protocol dependent

ACT LED / Rx/Tx LED

Ethernet connection IN

Ethernet connector CH0 IN

LINK LED / L/A LED

Ethernet connection IN

User label

Fieldbus connector IN (male)

LED for fieldbus protocols. Labeling and function is protocol dependent

Screw hole with no connection to potential equalization

Figure 5: LEDs and Control Elements NB 100-RE-XX

The labeling of the LED is device dependent.

Label of the LED Protocol Device Type

Table 24: LED (20) – Labeling

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections 32/122

4.4.2 Elements of the netBRICK NB 100-RS-xx Device

No. Description

Fieldbus connector OUT (female)

User label

Serial RS interface, parallel with

APL LED

Covering cap for the diagnostic port. Underneath the cover you will find the USB service port and a push button used during manufacturing

Screw hole for connection to potential equalization

User label

Screw hole for connection to potential equalization

Connector PWR for power supply

SYS LED

COM LED, protocol dependent

Serial RS interface, parallel with

User label

Fieldbus connector IN (male)

LED for fieldbus protocols. Labeling and function is protocol dependent

Screw hole with no connection to potential equalization

Figure 6: LEDs and Control Elements NB 100-RS-xx

The labeling of the LED is device dependent.

Label of the LED Protocol Device Type

Table 25: LED (20) – Labeling

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections 33/122

4.5 Connections

4.5.1 X1 Power Supply PWR

The power supply of netBRICK NB 100 devices has to be connected to the connector X1 , which is of type M12 male A coded. The voltage level need to be between 18 V and 30 V DC.

Power Supply Line Pin Assignment

Power supply line

Pin Signal Description

M12 connector

A coded

1 24 V

2 -

3 0 V /

GND

4 -

5 -

PE

+24 V supply voltage

Ground of supply voltage

Metal screw connection

Table 26: X1 Power Supply Line Pin Assignment

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections 34/122

4.5.2 X2 Front Connection

4.5.2.1 X2 Ethernet Connection for NB 100-RE-xx Devices

For the Ethernet connection you have to use M12 male connectors with

AWG22 or AWG 26 cable.

Note:

The device supports auto crossover functionality, which enables twisting of RX and TX transmission lines. The following picture illustrates the M12 standard pin layout.

Connector Ethernet IN to the left hand side of the device.

Ethernet at M12 Pin Assignment

Ethernet Pin Signal

1 Ethernet Tx +

Description

Transmit data +

2

3

4

Ethernet Rx +

Ethernet Tx -

Ethernet Rx -

5 -

PE

Receive data +

Transmit data –

Receive data –

Metal screw connection

M12 female connector,

D coded

Table 27: Ethernet Pin Assignment

Connector Ethernet OUT to the right hand side of the device.

Ethernet at M12 Pin Assignment

Ethernet

M12 female connector,

D coded

Pin Signal

1 Ethernet Tx +

Description

Transmit data +

2

3

4

Ethernet Rx +

Ethernet Tx -

Ethernet Rx -

5 -

PE

Receive data +

Transmit data –

Receive data –

Metal screw connection

Table 28: Ethernet Pin Assignment

Both female connectors are angled by 90° to each other. This enables the use of angled connectors. The cable can be conducted at a relative angle of 45° compared to the device in this case.

Important:

Please note for the use of hubs and switches the wiring in-

structions in section Ethernet on page 109.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.5.2.2

35/122

X2 Serial Connection for NB 100-RS-xx Devices

Note:

The connections SERIAL A and SERIAL B are galvanically connected 1:1 in parallel.

Both connectors are angled by 90° to each other. Both connectors are B coded.

RS-232 M12 Pin Assignment

RS-232 Pin

1

Signal

CTS

Description

Clear To Send

M12 female connector, B coded

4

5

RTS Request To Send

ISO GND Data ground

PE Metal screw connection

Table 29: M12 RS-232 Pin Assignment

RS-422 M12 Pinbelegung

RS-422

M12 female connector,

B coded

4

5

Pin

1

2

3

Signal

Tx +

Rx -

Tx -

Description

Transmit data positive

Receive data negative

Transmit data negative

Rx + Receive data positive

ISO GND Isolated ground

PE Metal screw connection

Table 30: RS-422 M12 Pin Assignment

RS-485 M12 Pinbelegung

RS-485

M12 female connector,

B coded

4

5

Pin

1

2

3

Signal

TX_P

Rx/Tx -

TX_N

Description

Reserved. Do not connect!

Receive data / Transmit data negative, A-Line

Reserved. Do not connect!

Rx/Tx + Receive data / Transmit data positive, B-Line

ISO GND Data ground

PE Metal screw connection

Table 31: RS-485 M12 Pin Assignment

Please note the wiring instructions for RS-232 on page 110, for RS-422 on

page 111 and for RS-485 on page 113.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections 36/122

4.5.3 X3 Fieldbus Connection

4.5.3.1 X3 PROFIBUS Interface

The PROFIBUS interface X3 is a RS-485 interface according to PROFIBUS standard EN 50170.

Connector IN , M12 male connector, B coded.

PROFIBUS M12 RS-485 Pin Assignment

PROFIBUS

M12 connector,

B coded

Pin

1

2

3

Signal

VP

Rx/Tx -

Description

+5 V Power supply for termination max. 100 mA

Receive data / Transmit data negative, A-Line

ISO GND Data ground

4 Rx/Tx + Receive data / Transmit data positive, B-Line

5 PE Shield

PE Metal screw connection

Table 32: PROFIBUS M12 RS-485 Pin Assignment

Connector OUT , M12 male connector, B coded.

PROFIBUS M12 RS-485 Pin Assignment

PROFIBUS Pin

1

2

Signal

VP

Rx/Tx -

Description

+5 V Power supply for termination max. 100 mA

Receive data / Transmit data negative, A-Line

3

4

ISO GND

Rx/Tx +

Data ground

Receive data / Transmit data positive, B-Line

5 PE Shield

PE Metal screw connection

M12 female connector,

B coded

Table 33: PROFIBUS M12 Pin Assignment

The ports are oriented in a way that angled plugs will angle at 45 degrees away from the device and are pointing downwards.

The pins of the connector IN and OUT are connected galvanically. The power supply VP can be loaded in sum max. with 100 mA.

Please note the wiring instructions in section PROFIBUS on page 104.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.5.3.2 X3 CANopen Interface

The CANopen interface X3 is according to ISO 11898.

Connector IN

,

M12 male connector, A coded.

CANopen M12 Pin Assignment

CANopen Pin Signal Description

1 PE Shield

2 V+

+24 V CANopen-

Power supply

3

4

ISO GND CAN ground, 15 nF against PE

CAN H

M12 connector

A coded

5 CAN L

PE

Table 34: CANopen M12 Pin Assignment

CAN High-Signal

CAN Low-Signal

Metal screw connection

37/122

Connector OUT , M12 female connector, A coded.

CANopen M12 Pin Assignment

CANopen Pin Signal Description

1 PE Shield

M12 female connector

A coded

3

4

5

ISO GND

CAN H

CAN L

PE

Table 35: CANopen M12 Pin Assignment

Power supply

CAN ground, 15 nF against PE

CAN High-Signal

CAN Low-Signal

Metal screw connection

The ports are oriented in a way that angled plugs will angle at 45 degrees away from the device and are pointing downwards.

The pins of the connector IN and OUT are connected galvanically.

Please note the wiring instructions in section CANopen on page 106.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.5.3.3

38/122

X3 DeviceNet Interface

The pinning of the DeviceNet interface X3 is according to the DeviceNet standard.

Important:

According to the DeviceNet specification it is not allowed to lead the DeviceNet bus through the device! No interruption of the DeviceNet network must occur if a device is replaced! Therefore, you must

use one connection port only

(IN or OUT)!

The pins of the connector IN and OUT are connected galvanically.

Connector IN .

DeviceNet M12 Pin Assignment

DeviceNet

M12 connector

A coded

5

3

4

Pin Signal Description

1 PE Shield

2 V+ +24 V DeviceNet- supply voltage

ISO GND DeviceNet common ground, 15 nF against PE

CAN H CAN High-Signal

CAN L

PE

CAN Low-Signal

Metal screw connection

Table 36: DeviceNet M12 Pin Assignment

Connector OUT .

DeviceNet M12 Pin Assignment

DeviceNet

M12 female connector

A coded

3

4

5

Pin Signal Description

1 PE Shield

2 V+ +24 V DeviceNet- supply voltage

ISO GND DeviceNet common ground , 15 nF against PE

CAN H

CAN L

PE

Table 37: DeviceNet M12 Pin Assignment

CAN High-Signal

CAN Low-Signal

Metal screw connection

The ports are oriented in a way that angled plugs will angle at 45 degrees away from the device and are pointing downwards.

Please note the wiring instructions in section DeviceNet on page 107.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.5.4 Diagnostic Interface

4.5.4.1 Safety Messages on Personal Injury

39/122

Use in Hazardous Locations with Potentially Explosive Atmosphere only in Scope of the UL Standards

Important!

Outside the scope of the UL standards you are allowed to use the netBRICK NB 100 device in non-hazardous locations only!

When using the device in hazardous locations with potentially explosive atmosphere according to UL (UL-Report/File E326833) you must observe the following safety messages.

Explosion Hazard!

 Do not use the diagnostic interface DIAG (USB connector) of the net-

BRICK NB 100 device in hazardous locations. Use the diagnostic interface DIAG only, if power has been removed or the area is known to be non-hazardous. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.5.4.2

40/122

Diagnostic Interface

Electrostatically sensitive Devices

 To prevent damage to the netBRICK NB 100 device, make sure, that you are discharged when you open the diagnostic interface DIAG (USB connector) of the netBRICK NB 100 device.

Important:

Connect the USB cable to the device after the device was powered. Otherwise this may cause malfunction.

Under the cover of the diagnostic interface are two elements:

Figure 7: Diagnostic Interface

No Description

USB (socket) for configuration and Diagnosis

Button for manufacturing test

The USB interface is for configuration and diagnostic purpose using a

PC with SYCON.net software.

USB female connector

Pin Signal Description

1 NC Not

2 D-

3 D+ Data

4 Not to be occupied in the USB cable or the USB cable must be connected to the device after

Power On.

5 GND Ground

Shield PE Metal shell to PE

Table 38: Pin Assignment Mini-B USB Connector (5 pin)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections 41/122

4.6 Schematic Diagram - Galvanic Isolation

The following schematic diagram illustrates the internal connection between the different connectors. This gives you the possibility to properly install the device in accordance with the potential equalization concept of your plant.

Note:

The PE connection (potential equalization) of the device is done via the two bottom screw holes.

4.6.1 Galvanic Isolation NB 100-RE-DP Device

Figure 8: Galvanic Isolation NB 100 RE-DP Device

The device has three galvanically isolated areas

System area, galvanically coupled with the power supply connection

X1

Ethernet connecting area, 2 * M12 D coded. Both Ethernet ports are galvanically isolated against each other.

Fieldbus connecting area, M12 male and female connector A or B coded. The pins are connected to each other internally.

The following table shows the characteristics of the galvanic isolation of the different areas and coupling against potential equalization. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

Area

Connection

Protocol

Galvanic

Isolation

no

Coupling

X1

All devices Surge

HF

Ethernet yes

X2

X3

All devices

PROFIBUS DP yes Cx3

Cx4

Table 39: Coupling NB 100-RE-DP Device

42/122

Coupling against PE Potential

3 * 15 nF 500V

3 * RVA, voltage-dependent resistance, reversible UVA > 38V

4 * Cf = 100 nF, 2 * Lf = 100 μH each

2 * 75 Ω, 1 nF 1000 V

1 nF 2000 V

1 MΩ // 2,2 nF 1000 V netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.6.2 Galvanic Isolation NB 100-RE-DN/CO Device

43/122

Figure 9: Galvanic Isolation NB 100-RE-DN/CO Device

The device has three galvanically isolated areas

System area, galvanically coupled with the power supply connection

X1

Ethernet connecting area, 2 * M12 D coded. Both Ethernet ports are galvanically isolated against each other.

Area

Connection

Fieldbus connecting area, M12 male and female connector A or B coded. The pins are connected to each other internally.

The following table shows the characteristics of the galvanic isolation of the different areas and coupling against potential equalization.

Protocol Galvanic

Isolation

Coupling Coupling against PE Potential

All devices no Surge

X1

3 * 15 nF 500 V

3 * RVA, voltage-dependent resistance, reversible UVA > 38 V

4 * Cf = 100 nF, 2 * Lf = 100 μH

Je 2 * 75 Ω, 1 nF 1000 V

X2

Ethernet yes

HF

Cx2

X3

All devices

CANopen

DeviceNet yes Cx3 1 nF 2000 V

Cx4 + Cx5 Cx4 = (1 MΩ // 15 nF 1000 V);

Cx5 = 0 Ω

Cx4 + Cx5 each

1 MΩ // 15 nF 1000 V

Table 40: Galvanic Isolation NB 100-RE-DN/CO Device

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.6.3 Galvanic Isolation NB 100-RS-DP Device

44/122

Figure 10: Galvanic Isolation NB 100-RS-DP Device

The device has three galvanically isolated areas

System area, galvanically coupled with the power supply connection

X1

Serial connecting area, 2 * M12 B coded female connector. All pins are connected to each other internally.

Area

Connection

Fieldbus connecting area, M12 male and female connector B coded.

The pins are connected to each other internally.

The following table shows the characteristics of the galvanic isolation of the different areas and coupling against potential equalization.

Protocol galv. Isolation

Coupling Coupling against PE potential

X1

All devices no Surge

HF

3 * 15 nF 500V

3 * RVA, voltage-dependent resistance, reversible UVA > 38 V

4 * Cf = 100 nF, 2 * Lf = 100 μH

X2

X3

PROFIBUS DP yes Cx3

Cx4

1 nF 2000 V

1 MΩ // 2,2 nF 1000 V

Table 41: Galvanic Isolation NB 100-RS-DP Device

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Device Drawings and Connections

4.6.4 Galvanic Isolation NB 100-RS-DN/CO Device

45/122

Figure 11: Galvanic Isolation NB 100-RS-DN/CO Device

The device has three galvanically isolated areas

System area, galvanically coupled with the power supply connection

X1

Serial connecting area, 2 * M12 B coded female connector. All pins are connected to each other internally.

Area

Connection

Fieldbus connecting area, M12 male and female connector B coded.

The pins are connected to each other internally.

The following table shows the characteristics of the galvanic isolation of the different areas and coupling against potential equalization.

Protocol Galvanic

Isolation

Coupling Coupling against PE Potential

X1

All devices no Surge

HF

3 * 15 nF 500V

3 * RVA, voltage-dependent resistance, reversible UVA > 38 V

4 * Cf = 100 nF, 2 * Lf = 100 μH

X2

X3

All devices

CANopen

DeviceNet yes yes

Cx3

Cx4 + Cx5

1 nF 2000 V

Cx4 + Cx5 Cx4 = (1 MΩ // 15 nF 1000 V)

Cx5 = 0 Ω

Je (1 MΩ // 15 nF 1000 V)

Table 42: Galvanic Isolation NB 100-RS-DN/CO Device

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Mounting and Dismounting 46/122

5 Mounting and Dismounting

5.1 Safety Messages on Personal Injury

Obey to the following safety messages on personal injury, when mounting, dismounting or replacing the netBRICK NB 100 device.

5.1.1 Use in Hazardous Locations only in Scope of the UL Standards

The Use in Hazardous Locations with Potentially Explosive Atmosphere is only allowed in Scope of the UL Standards!

Important!

Outside the scope of the UL standards you are allowed to use the netBRICK NB 100 device in non-hazardous locations only!

When using the device in hazardous locations with potentially explosive atmosphere according to UL (UL-Report/File E326833) you must observe the following safety messages.

Explosion Hazard!

Do not connect or disconnect the netBRICK NB 100 device unless power has been removed or the area is known to be non-hazardous.

Substitution of components may impair suitability for NEC500 Class I,

Division 2, Groups A, B, C, and D.

Do not use the diagnostic interface DIAG (USB connector) of the net-

BRICK NB 100 device in hazardous locations. Use the diagnostic interface DIAG only, if power has been removed or the area is known to be non-hazardous.

 Use only a power supply specified according to the UL standard.

5.1.2 Danger of unsafe System Operation

Danger of unsafe System Operation

To prevent harm of persons, do not remove this device under runtime conditions before you can not guarantee further a safe and secure operation of the plant. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Mounting and Dismounting 47/122

5.2 Property Damage Messages

Obey to the following property damage messages, when mounting the net-

BRICK NB 100 device.

5.2.1 Device Destruction by exceeding allowed Supply Voltage

Device Destruction!

 Use only the permissible supply voltage to operate the netBRICK NB

100 device.

 Operating the netBRICK NB 100 device with a supply voltage above of the specified range leads to device destruction.

5.2.2 Electrostatically sensitive Devices

Electrostatically sensitive Devices

 To prevent damage to the netBRICK NB 100 device, make sure, that you are discharged when you open the diagnostic interface DIAG (USB connector) of the netBRICK NB 100 device.

5.2.3 Danger of unsafe System Operation

Danger of unsafe System Operation

To prevent property damage, do not remove this device under runtime conditions before you can not guarantee further a safe and secure operation of the plant. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Mounting and Dismounting 48/122

5.3 Mounting

The devices can be mounted adjacent to each other.

In case angled connectors are used, take into account that the connectors are pointing always from device in an angle of 45°. This is why you have to take care about the spacing for the cable run.

The device should be mounted on a metallic surface. At least the holes and

(Figure 5 on page 31) have to be securely connected to a metal

plate that is connected to the potential equalization. This establishes also the earthing of the M12 connectors.

For mounting of the device use screws of type M4 with an overall length of at least > 6 mm.

Information about the drilling template is in section Drilling Template on page 29.

5.3.1 Use in Hazardous Locations only in Scope of the UL Standards

The Use in Hazardous Locations with Potentially Explosive Atmosphere is only allowed in Scope of the UL Standards!

Important!

Outside the scope of the UL standards you are allowed to use the netBRICK NB 100 device in non-hazardous locations only!

When using the device in hazardous locations with potentially explosive atmosphere according to UL (UL-Report/File E326833) you must observe the following safety messages.

Explosion Hazard!

 Do not connect the netBRICK NB 100 device unless power has been removed or the area is known to be non-hazardous.

 Use only a power supply specified according to the UL standard. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Mounting and Dismounting 49/122

5.4 Dismounting

Danger of unsafe System Operation!

 To prevent harm of persons and property damage, do not remove this device under runtime conditions before you can not guarantee further a safe and secure operation of the plant.

Danger of unsafe System Operation!

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

Take care that no liquid enter into the connectors during dismounting the device.

5.4.1 Use in Hazardous Locations only in Scope of the UL Standards

When using the device in hazardous locations with potentially explosive atmosphere according to UL (UL-Report/File E326833) you must observe the following safety messages.

Explosion Hazard!

 Do not connect or disconnect the netBRICK NB 100 device unless power has been removed or the area is known to be non-hazardous.

 Substitution of components may impair suitability for NEC500 Class I,

Division 2, Groups A, B, C, and D. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Install Driver 50/122

Always use the installation program to install the USB driver. The installation program is named setup.exe and is on the Gateway Solution DVD in the folder Setups & Drivers\USB Driver.

Install the USB driver at first, before you connect the netBRICK NB 100 gateway to the USP port of your PC the first time.

Windows XP: The Found New Hardware Wizard appears under Windows

XP, when you connect the gateway to the USB port for the first time. Select the Install the software automatically option in the wizard, if the USB driver is installed on your PC. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning 51/122

7 Commissioning

7.1 Commissioning

Obey to the following property damage messages, when commissioning the netBRICK NB 100 device.

Electrostatically sensitive Devices

 To prevent damage to the netBRICK NB 100 device, make sure, that you are discharged when you open the diagnostic interface DIAG (USB connector) of the netBRICK NB 100 device.

It is necessary for commissioning that the device is loaded with relevant configuration data.

The configuration can be created and saved offline with or without real device on a standard PC with the software SYCON.net. The configuration can be downloaded into the device in two steps afterwards.

Information about the configuration of the protocol conversion of the device is in the operating instruction manual Configuration of Gateway and

Proxy Devices OI xx EN.pdf

on the DVD in the directory Documentation.

The configuration is saved in the device in a non-volatile flash memory.

Once set the data will be available after each power cycle.

The power up behavior after a power cycle is described in the chapter Boot

up Behavior

on page 52.

7.2 Maintainance

Obey to the following property damage messages, when maintaining the netBRICK NB 100 device.

Electrostatically sensitive Devices

 To prevent damage to the netBRICK NB 100 device, make sure, that you are discharged when you open the diagnostic interface DIAG (USB connector) of the netBRICK NB 100 device. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning 52/122

7.3 Boot up Behavior

7.3.1 Boot up Behavior on valid Firmware

During the power up cycle the configuration and firmware data are copied from the flash memory into the RAM of the netX 100 CPU. The firmware is then started. This procedure may take (configuration data size dependent) some seconds (usually 4 seconds).

7.3.2 Boot up Behavior on invalid Firmware

7.3.2.1

If after the power up cycle the LED SYS

known from Figure 5: LEDs and

Control Elements

on page 31 is flashing yellow / green at a rate of 1 Hz,

the firmware of the device is invalid or has been destroyed. In this case there is no further access possible with the configuration tool SYCON.net.

The device has fallen back into bootloader mode.

The device has to be recovered to the factory default settings.

Recover to Factory Default Settings

In case there is no further communication possible via and the configuration tool SYCON.net because a firmware download has failed for example, then a special recovery procedure can bring back the device back to life.

In this special state the LED SYS (No.

known from Figure 5: LEDs and

Control Elements

on page 31 is flashing yellow / green at 1 Hz.

In case a NB 100 device is connected in this very special state to the USB port of a PC, windows will ask for a new USB driver, even if you have al-

ready installed it before. Please follow the instructions in the section USB

Driver Installation in Bootloader Mode as „netX boot monitor“

on page 53 to

install the driver.

Just in the case that no driver installation is requested (cause the device has been previously connected in this state before already) please follow

the instructions in the section Load Firmware in Boot Loader Mode on page

57.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning

7.3.2.2

53/122

USB Driver Installation in Bootloader Mode as „netX boot monitor“

Note:

The following section only need to be done in case of an error, if the firmware download into the devices was not completed without error.

(Loss of power or line interruption during the firmware download).

After establishing the USB cable connection and powering the device, windows will ask you for the USB driver with the following window:

Figure 12: USB Installation in Bootloader Mode Step 1

 Insert the DVD included in the delivery into the DVD drive of your PC.

 Select . Afterwards click Next . netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning

 The following window will be opened.

54/122

Figure 13: USB Installation in Bootloader Mode Step 2

 Select in this windows the option Install from a list or specific loca-

tion

and click Next .

 The following window will appear.

Figure 14: USB Installation in Bootloader Mode Step 3

 Select and then click Next . netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning

 The following window will be opened.

55/122

Figure 15: USB Installation in Bootloader Mode Step 4

 Select the option Have Disk .

 The following window will be opened.

Figure 16: USB Installation in Bootloader Mode Step 5

 Click .

 In the opening file explorer move to the DVD folder

Setups & Drivers\USB Driver\USB netX50_51_52 and netX100 and select the file netX_usb_cdc.inf.

After returning to this window click OK . netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning

 You will return back to the following window.

56/122

Figure 17: USB Installation in Bootloader Mode Step 6

 Select netX boot monitor (even if there are other entries shown, please select this one) and confirm with Next .

 The following window will be opened.

Figure 18: USB Installation in Bootloader Mode Step 7

 Confirm

Continue Anyway

.

 Wait until the driver has been properly installed.

Continue with section Load Firmware in Boot Loader Mode on page 57.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning

7.3.2.3

57/122

Load Firmware in Boot Loader Mode

 Start directly from the DVD Supplements & Examples\Device

Recovery\netBRICK 100 Factory Settings\Recovery via

USB\comproX.exe

.

 Alternatively, copy all files from Supplements & Examples\Device

Recovery\netBRICK 100 Factory Settings\Recovery via

USB

onto your PC and then start comproX.exe.

 The following window will be opened.

Figure 19: ComProX Start

 Select the drop down menu Connection > Open .

 The following window will be opened.

Figure 20: ComProX Choice of Connection

Select and confirm with OK . netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning

 You are forwarded back to the program’s start screen.

58/122

Figure 21: ComProX Choice File Explorer

 Select now from the drop down menu Connection > File Explorer .

 The following additional windows will be opened.

Figure 22: ComProX File Explorer - NB 100 File System Structure

 In order to see the file system of the device in the window area move the dividing line slightly to the right.

Select in the window area the entry PORT_0 and do a right mouse click afterwards in the window area . netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning

 The following dialog menu will be opened.

59/122

Figure 23: ComProX File Explorer - File Menu 1

 Select from the drop down menu the entry Download .

 The standard file explorer of your windows will be opened

 Move on the DVD to folder

Supplements & Examples\Device Recovery\netBRICK 100

Factory Settings\Recovery via USB\Recovery via USB or move to the local folder and select the file NBBASEFW.NXF.

 Loading the firmware may take some seconds.

Right mouse click into the window area of the window above.

 The following dialog menu will be opened.

Figure 24: ComProX File Explorer - File Menu 2

 Select .

 In case the download was successful ComProX will show you the download firmware as shown at .

Close the window above and close the main window of ComProX.

Remove the power from your device and perform a power cycle. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Commissioning 60/122

 The device will be restarted and the firmware will be started. Now the

LED SYS (No.

known from Figure 5: LEDs and Control Elements on page 31) will be on green and the LED APL (No. known from LEDs and Control Elements on page 31) flashes red.

The reset to factory settings has successfully been executed. Now you can access to the device again with the configuration tool SYCON.net via the

USB port. From there you can now download the firmware of your choice. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Troubleshooting 61/122

8 Troubleshooting

Two methods for troubleshooting exist:

 The visual analysis of the LED conditions of the device

 The analysis via the USB port along with the configuration tool

SYCON.net.

The following overview describes the error conditions that may be detected by a visual check of the LEDs.

LED state

No LED is on

In order to find the correct position of the LEDs please follow the chapter

Positions of LEDs and

Control Elements from page 31. The numbers in the

column LED state is referencing the position number in the device drawing.

SYS LED flashes yellow/green at 1 Hz

SYS LED on yellow

Remedy

The device is not powered or the device has a malfunction and needs replacement

After a power cycle the device has not found a valid firmware and remains in bootloader mode. The device has to be recovered and set back to factory set-

ting. Follow the chapter "Recover to Factory Default Settings" on page 52.

The device has a malfunction and needs replacement.

SYS LED on green The device is well initialized. Further analysis is possible with the LED APL.

Follow the chapter “LED APL“ on page 63.

APL LED red red on or flashing

APL LED flashing green

The communication via port X2 or/and port X3 is not in data exchange mode.

See chapter “LED APL“ on page 63.

Table 43: NB 100 Troubleshooting

The device is operational just in case the described error conditions above do not met. Further protocol specific error diagnostics via the LEDs is possible by reading on the chapter “LED”.

In deep diagnostics is possible at any time via the USB diagnostic port of the device and a PC with the software SYCON.net.

In case of trouble you should make sure that you have downloaded a correct signal mapping to the device via SYCON.net

For some protocols it is necessary to synchronize data via a handshake between the gateway and the superordinated PLC. Please make sure that the handshake mechanism is kept. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Troubleshooting 62/122

8.1 Failure in 10 MBit/s Half Duplex Mode and Workaround

Only older devices are affected that have a serial number below the number listed in the following table.

Device type NB 100-RE-xx

NB 100-RE-CO

NB 100-RE-DP

NB 100-RE-DN

Affected Hardware

Serial number below

20025

20027

20020

Hardware with the communication controller netX 50, netX 100 or netX 500; netX/Internal PHYs.

When can this Failure occur?

When using standard Ethernet communication with 10 MBit/s half duplex mode, the PHY gets stuck in case of network collisions. Then no further network communication is possible. Only device power cycling allows

Ethernet communication again.

This problem can only occur with Ethernet TCP/UDP IP, EtherNet/IP or

Modbus TCP protocols when using hubs at 10 MBit/s. The issue described above is not applicable for protocols which use 100 MBit/s or full duplex mode.

Solution / Workaround:

Do not use 10 MBit/s-only hubs. Use either switches or 10/100 MBit/s Dual

Speed hubs, to make sure the netX Ethernet ports are connected with 100

MBit/s or in full duplex mode.

This erratum is fixed with all components of the ‘Y’ charge (9 digit charge number shows ‘Y’ at position 5 (nnnnYnnnn).

Reference

“Summary of 10BT problem on EthernetPHY”,

RenesasElectronics Europe, April 27, 2010 netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 63/122

9 LEDs

In order to find the correct position of the LEDs please follow the chapter

Positions of LEDs and Control Elements

from page 31. The numbers in the

column LED state is referencing the position number in the device drawing.

9.1 LED SYS

LED

SYS

Number in the device drawing

The subsequent table describes the meaning of the system LED.

Color State

Duo LED yellow/green

Meaning

(green)

On Operating System running

(yellow) static

(yellow) Flashing

Bootloader is waiting for software

This state may occur only briefly.

If this LED stays permanently yellow, then a hardware failure is possible.

The device doesn’t work. In the USB cable attached to the device has pin 4 connected with ground.

 Remove the USB cable from the device. Disconnect the power supply to the device.

Reconnect the power supply to the device. After some seconds reconnect the USB cable to the device.

 The device is working.

Boot loader active.

(yellow

/green)

Flashing yellow/green

Off

(off)

Power supply for the device is missing or hardware defect.

Table 44: System LED

9.2 LED APL

LED

APL

Number in device drawing

Color State

Duo LED green/read

(green)

On

(green)

(green)

red)

(red)

Blinking with

2 s off,

0,5 s on

Blinking with

2 s off,

0,5 s on,

0,5 s off,

0,5 s on,

Blinking with

2 s off,

0,5 s on

Blinking with

2 s off,

0,5 s on,

0,5 s off,

0,5 s on,

On

(red)

Meaning

The communication on X2 and X3 is in cyclic data exchange and the gateway function is executed netBRICK is initialized, but the communication on X2 is not in cyclic data exchange. netBRICK is initialized, but the communication on X3 is not in cyclic data exchange. netBRICK is initialized, but the configuration for the communication protocol on X2 is missing or has an error netBRICK is initialized, but the configuration for the communication protocol on X3 is missing or has an error

Table 45: LED APL

netBRICK has detected an error during the initialization: Missing configuration, error in configuration or internal error netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs

9.3 LEDs Real Time Ethernet Systems

64/122

9.3.1 LED EtherCAT Master

LED

RUN

Name in the device drawing:

COM0

ERR

Name in the device drawing:

COM1

LINK

RJ45

Ch0

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the EtherCAT Master protocol is loaded to the device.

State Meaning Color

Duo LED red/green

(off)

Off

(green)

Blinking

(green)

Flickering

(green)

Single Flash

(green)

On

Duo LED red/green

(off)

Off

(red)

On

INIT

: The device is in state INIT

PRE-OPERATIONAL

: The device is in PRE-OPERATIONAL state

BOOT

: Device is in Boot mode

SAFE-OPERATIONAL

: The device is in SAFE-OPERATIONAL state

OPERATIONAL

: The device is in OPERATIONAL state

Master has no errors

Master has detected a communication error. The error is indicated in the DPM

LED green

(green)

On A link is established

ACT

RJ45

Ch0

(off)

LED yellow

(yellow)

(off)

Flickering

Off

The device sends/receives Ethernet frames

Device has no configuration

Table 46: LEDs EtherCAT Master

LED State Definition for EtherCAT Master for the RUN and ERR

LEDs

Indicator state

On

Off

Blinking

Flickering

Single Flash

Definition

The indicator is constantly on.

The indicator is constantly off.

The indicator turns on and off with a frequency of 2,5 Hz: on for

200 ms, followed by off for 200 ms.

The indicator turns on and off with a frequency of approximately

10 Hz: on for approximately 50 ms, followed by off for 50 ms.

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

Table 47: LED State Definition for EtherCAT Master for the RUN and ERR LEDs

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 65/122

9.3.2 LED EtherCAT Slave

LED

RUN

Number in the device drawing:

COM0

ERR

Number in the device drawing:

COM1

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the EtherCAT Slave protocol is loaded to the device.

State Meaning Color

Duo LED red/green

(off)

Off

(green)

Blinking

(green)

Single Flash

(green)

On

INIT

: The device is in state INIT

PRE-OPERATIONAL

SAFE-OPERATIONAL

OPERATIONAL

: The device is in state PRE-OPERATIONAL

: The device is in state SAFE-OPERATIONAL

: The device is in state OPERATIONAL

Duo LED red/green

(off)

(red)

(red)

(red)

(red)

Off

Blinking

Single Flash

Invalid Configuration

: General Configuration Error

(Example: State change commanded by master is impossible due to register or object settings.)

Unsolicited State Change

: Slave device application has changed the

EtherCAT state autonomously: Parameter "Change" in the AL status register is set to 0x01:change/error

(Example: Synchronization Error, device enters Safe-Operational automatically.)

Double Flash

Application Watchdog Timeout

: An application watchdog timeout has occurred.

(Example: Sync Manager Watchdog timeout)

On

No error

: The EtherCAT communication of the device is in working condition

PDI Watchdog Timeout

: A PDI Watchdog timeout has occurred

(Example: Application controller is not responding any more)

L/A IN

RJ45 Ch0

L/A OUT

RJ45 Ch1

RJ45 Ch0

RJ45 Ch1

LED green

(green)

(green)

(off)

LED yellow

- -

On

Flashing

A link is established

The device sends/receives Ethernet frames

This LED is not used.

Table 48: LEDs EtherCAT Slave

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 66/122

LED State Definition for EtherCAT Slave for the LEDs RUN and

ERR LED

Indicator state

On

Off

Blinking

Single Flash

Double Flash

Definition

The indicator is constantly on.

The indicator is constantly off.

The indicator turns on and off with a frequency of 2,5 Hz: on for

200 ms, followed by off for 200 ms.

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

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 49: LED State Definition for EtherCAT Slave for the RUN and ERR LEDs

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 67/122

9.3.3 LED EtherNet/IP Scanner (Master)

LED

MS

Number in the device drawing

COM0

NS

Number in the device drawing

COM1

LINK

/RJ45

Ch0 & Ch1

&

ACT

/RJ45

Ch0 & Ch1

&

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the EtherNet/IP Scanner (Master) protocol is loaded to the device.

State Meaning Color

Duo LED red/green

(green)

(green)

(red)

On

Device operational

: If the device is operating correctly, the module status indicator shall be steady green.

Flashing

Standby

: If the device has not been configured, the module status indicator shall be flashing green.

On

Major fault

: If the device has detected a non-recoverable major fault, the module status indicator shall be steady red.

(red)

(red/green)

Flashing

Minor fault

: If the device has detected a recoverable minor fault, the module status indicator shall be flashing red. NOTE: An incorrect or inconsistent configuration would be considered a minor fault.

Flashing

Self-test

: While the device is performing its power up testing, the module status indicator shall be flashing green/red.

(off)

Off

No power

: If no power is supplied to the device, the module status indicator shall be steady off.

Duo LED red/green

(green)

(green)

(red)

(red)

(red/green)

(off)

On

Flashing

No connections

: If the device has no established connections, but has obtained an IP address, the network status indicator shall be flashing green.

On

Duplicate IP

: If the device has detected that its IP address is already in use, the network status indicator shall be steady red.

Flashing

Connection timeout

: If one or more of the connections in which this device is the target has timed out, the network status indicator shall be flashing red.

This shall be left only if all timed out connections are reestablished or if the device is reset.

Flashing

Self-test

: While the device is performing its power up testing, the network status indicator shall be flashing green/red.

Off

Connected

: If the device has at least one established connection (even to the Message Router), the network status indicator shall be steady green.

Not powered, no IP address

: If the device does not have an IP address (or is powered off), the network status indicator shall be steady off.

LED green

(green)

On A connection to the Ethernet exists

Off The device has no connection to the Ethernet

(off)

LED yellow

(yellow)

Flashing The device sends/receives Ethernet frames

Table 50: LEDs EtherNet/IP Scanner (Master)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 68/122

9.3.4 LED EtherNet/IP Adapter (Slave)

LED

MS

Number in the device drawing:

COM0

Color

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the EtherNet/IP Adapter (Slave) protocol is loaded to the device.

State

Duo LED red/green

Meaning

NS

Number in the device drawing:

COM1

LINK

/RJ45

Ch0 & Ch1

&

ACT

/RJ45

Ch0 & Ch1

&

(green)

(green)

(red)

(red)

(red/green)

(off)

Duo LED red/green

(green)

(green)

(red)

(red)

(red/green)

(off)

On

Connected

: If the device has at least one established connection (even to the Message Router), the network status indicator shall be steady green.

Flashing

No connections

: If the device has no established connections, but has obtained an IP address, the network status indicator shall be flashing green.

On

Duplicate IP

: If the device has detected that its IP address is already in use, the network status indicator shall be steady red.

Flashing

Connection timeout

: If one or more of the connections in which this device is the target has timed out, the network status indicator shall be flashing red.

This shall be left only if all timed out connections are reestablished or if the device is reset.

Flashing

Self-test

: While the device is performing its power up testing, the network status indicator shall be flashing green/red.

Off

Not powered, no IP address

: If the device does not have an IP address (or is powered off), the network status indicator shall be steady off.

LED green

On

Device operational

: If the device is operating correctly, the module status indicator shall be steady green.

Flashing

Standby

: If the device has not been configured, the module status indicator shall be flashing green.

On

Major fault

: If the device has detected a non-recoverable major fault, the module status indicator shall be steady red.

Flashing

Minor fault

: If the device has detected a recoverable minor fault, the module status indicator shall be flashing red. NOTE: An incorrect or inconsistent configuration would be considered a minor fault.

Flashing

Self-test

: While the device is performing its power up testing, the module status indicator shall be flashing green/red.

Off

No power

: If no power is supplied to the device, the module status indicator shall be steady off.

(green)

On A connection to the Ethernet exists

Off The device has no connection to the Ethernet

(off)

LED yellow

(yellow)

Flashing The device sends/receives Ethernet frames

Table 51: LEDs EtherNet/IP Adapter (Slave)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 69/122

9.3.5 LED Open Modbus/TCP

LED

RUN

Number in the device drawing:

COM0

ERR

Number in the device drawing:

COM1

LINK/

RJ45

Ch0 & Ch1

&

ACT

/RJ45

Ch0 & Ch1

&

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the Open Modbus/TCP protocol is loaded to the device.

State Meaning Color

Duo LED red/green

(off)

(green)

(green)

(green)

Off

Flashing cyclic with 1Hz

Flashing cyclic with 5Hz

On

Not Ready

OMB task is not ready

Ready, not configured yet

OMB task is ready and not configured yet

Waiting for Communication:

OMB task is configured

Connected:

OMB task has communication – at least one TCP connection is established

Duo LED red/green

(off)

Off

(red)

(red)

No communication error

Flashing cyclic with 2Hz

(On/Off Ratio =

25 %)

System error

On Communication error active

LED green

(green)

(yellow)

On

(off)

LED yellow

Off

Flashing

A connection to the Ethernet exists

The device has no connection to the Ethernet

The device sends/receives Ethernet frames

Table 52: LEDs Open Modbus/TCP

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 70/122

9.3.6 LED POWERLINK Controlle Node/Slave

LED

BS

Number in the device drawing:

COM0

Color

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the Powerlink Controlled Node/Slave protocol is loaded to the device.

State

Duo LED red/green

Meaning

BE

Number in the device drawing:

COM1

L/A

/RJ45

Ch0 & Ch1

&

RJ45

Ch0 & Ch1

&

(off)

(green)

Flickering

Single

Flash

Slave is in Basic Ethernet state

Slave is in Pre-Operational 1

Double

Flash

Slave is in Pre-Operational 2

Triple Flash Slave is in ReadyToOperate

On Slave is Operational

Blinking Slave is Stopped

Duo LED red/green

(off)

Off

(red)

On

Slave has no error

Slave has detected an error

LED green

(green)

On

(green)

Flashing

(off)

LED yellow

-

Off

-

Link

: A connection to the Ethernet exists

Activity

: The device sends/receives Ethernet frames

The device has no connection to the Ethernet

This LED is not used.

Table 53: LEDs Powerlink Controlled Node/Slave

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 71/122

LED State Definition for Powerlink Controlled Node/Slave for the

BS/BE LEDs

Indicator state

Definition

On

Off

Blinking

Flickering

Single Flash

Double Flash

Triple Flash

The indicator is constantly on.

The indicator is constantly off.

The indicator turns on and off with a frequency of approximately

2,5 Hz: on for approximately 200 ms, followed by off for 200 ms. Red and green LEDs shall be on alternately.

The indicator turns on and off with a frequency of approximately

10 Hz: on for approximately 50 ms, followed by off for 50 ms. Red and green LEDs shall be on alternately.

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

The indicator shows a sequence of two short flashes (each approximately 200 ms), separated by a short off phase (approximately 200 ms). The sequence is finished by a long off phase (approximately

1,000 ms).

The indicator shows a sequence of three short flashes (each approximately 200 ms), separated by a short off phase (approximately 200 ms). The sequence is finished by a long off phase (approximately

1,000 ms).

Table 54: LED State Definition for Powerlink Controlled Node/Slave for the BS/BE LEDs

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 72/122

9.3.7 LED PROFINET IO RT Controller

LED

SF

Name in the device drawing: COM0

Color

Duo LED red/green

(red)

On

(red)

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the PROFINET IO-RT Controller protocol is loaded to the device.

State Meaning

Flashing cyclic at 2 Hz

(together with BF „red ON“)

No valid Master license

System error

: Invalid configuration, Watchdog error or internal error

BF

Name in the device drawing: COM1

(off)

Duo LED red/green

(red)

On

No Connection:

No Link.

or (together with SF „red ON“)

No valid Master license

Configuration fault:

not all configured IO-Devices are connected.

LINK

RJ45 Ch0 &

Ch1

&

RX/TX

RJ45 Ch0 &

Ch1

&

(red)

(yellow)

Flashing cyclic at 2 Hz

(off)

LED green

(green)

On

(off)

Off

LED yellow

Flashing

A connection to the Ethernet exists

The device has no connection to the Ethernet

The device sends/receives Ethernet frames

Table 55: LEDs PROFINET IO-RT Controller

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 73/122

9.3.8 LED PROFINET IO-RT-Device

LED

SF

Number in the device drawing:

COM0

Color

Duo LED red/green

(red)

On

(red)

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the PROFINET IO-RT-Device protocol is loaded to the device.

State Meaning

Flashing cyclic at 2 Hz

(for 3 sec.)

Watchdog timeout; channel, generic or extended diagnosis present; system error

DCP signal service is initiated via the bus

BF

Number in the device drawing:

COM1

LINK

&

/RJ45

Ch0 & Ch1

RX/TX

/RJ45

Ch0 & Ch1

&

(off)

Duo LED red/green

(red)

On

(red)

Flashing cyclic at 2 Hz

No configuration; or low speed physical link; or no physical link

No data exchange

(off)

LED green

(green)

On

(off)

Off

LED yellow

(yellow)

Flashing

A connection to the Ethernet exists

The device has no connection to the Ethernet

The device sends/receives Ethernet frames

Table 56: LEDs PROFINET IO-RT-Device

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 74/122

9.3.9 LED sercos Master

LED

S3 (STA)

Name in the device drawing:

COM0

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the sercos Master protocol is loaded to the device.

State Meaning Color

Duo LED red/green

(green)

Blinking

(green)

Flickering

CP0:

Communication phase 0

Master isn't configured and is in NRT. After a status change this isn't indicated again

CP1:

Communication phase 1

CP2:

Communication phase 2

(green)

Single Flash

(green)

Double Flash

(green)

Triple Flash

(green)

On

(off)

Off

(red)

Blinking

(red)

Flickering

(red)

(red)

Single Flickering

Quadruple

Flash

Triple Flash

(red)

-

(red)

Double Flash

(red)

Single Flash

Duo LED red/green

-

CP3:

Communication phase 3

CP4:

Communication phase 4

NRT:

Non Real-time Mode

Error in the configuration database.

Boot-up was stopped due to an error.

Channel Init was executed at the Master.

No Master license present in the device

DPM Watchdog has expired.

Internal Stop of the bus cycle

Bus Sync Error Threshold

This LED is not used.

Name in the device drawing:

COM1

L/A

RJ45

Ch0 &

Ch1

&

RJ45

Ch0 &

Ch1

&

LED green

(green)

On

(green)

Flashing

(off)

LED yellow

-

Off

-

Link: A connection to the Ethernet exists

Activity: The device sends/receives Ethernet frames

The device has no connection to the Ethernet

This LED is not used.

Table 57: LEDs sercos Master

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 75/122

LED State Definition for sercos Master for the S3 (STA) and ERR

LEDs

Indicator state

Off

Blinking

Single Flickering

Flickering

Single Flash

Double Flash

Triple Flash

Quadruple Flash

Definition

The indicator is constantly off.

The indicator turns on and off with a frequency of 2,5 Hz: on for

200 ms, followed by off for 200 ms.

The indicator turns on and off with a frequency of approximately

10 Hz: on for approximately 50 ms, followed by off for 50 ms.

The indicator turns on and off once: on for approximately 50 ms, followed by off for 50 ms.

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

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).

The indicator shows a sequence of three short flashes (each

200 ms), separated by a short off phase (200 ms). The sequence is finished by a long off phase (1,000 ms).

The indicator shows a sequence of four short flashes (each

200 ms), separated by a short off phase (200 ms). The sequence is finished by a long off phase (1,000 ms).

Table 58: LED State Definition for sercos Master for the STA and ERR LEDs

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 76/122

9.3.10 LED sercos Slave

LED

S3 (STA)

Name in the device drawing:

COM 0

Name in the device drawing:

COM 1

L/A/

RJ45

Ch0 & Ch1

&

RJ45

Ch0 & Ch1

&

The subsequent table describes the meaning of the LEDs for the Real-Time

Ethernet device when the firmware of the sercos Slave protocol is loaded to the device.

State Meaning Color

Duo LED red/green/orange

(orange = red/green simultaneously)

(green)

On

CP4:

Communication phase 4,

Normal operation, no error

(green)

(red/ green)

Flashing (4 Hz)

Loopback

: The network state has changed from „fast-forward“ to

„loopback“.

Flashing (4 Hz),

The LED flashes at least for

2 seconds from red to green.

Communication Error

: Depends on IDN S-0-1003

(for details refer to sercos Slave Protocol API.pdf on the product DVD).

Shows how long the Master may in the communication phases CP3 and CP4 not received Master SYNC telegrams.

(red)

(orange)

On

On

SIII C1D

:

Error detected according to sercos third generation Cass 1 Diagnosis.

CP0 … CP3

:

Communication phase 0 to Communication phase 3

(orange)

(off)

Flashing (4 Hz)

Identification

: Bit 15 in the Slave device control that indicates remote address allocation or configuration errors between Master and Slaves

(for details refer to sercos Slave Protocol API.pdf on the product CD oder DVD).

Off No sercos Communication

Duo LED red/green

- This LED is not used.

LED green

(green)

On

(green)

Flashing

(off)

Off

LED yellow

-

Link: A connection to the Ethernet exists

Activity: The device sends/receives Ethernet frames

The device has no connection to the Ethernet

This LED is not used.

Table 59: LEDs sercos Slave

LED State Definition for sercos Slave for the S3 LED (STA LED)

Indicator state Definition

On

Off

Flashing (4 Hz)

The indicator is constantly on.

The indicator is constantly off.

The indicator turns on and off with a frequency of 4 Hz: on for appr. 125 ms, followed by off for appr. 125 ms.

Table 60: LED State Definition for sercos Slave for the S3 LED (STA LED)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 77/122

9.4 LEDs Fieldbus Systems

9.4.1 LED PROFIBUS DP Master

The subsequent table describes the meaning of the LEDs for the device when the firmware of the PROFIBUS DP Master protocol is loaded to the device.

State Meaning LED Color

Communication LED

COM

Duo LED red/green

with protocol at

X3

(green)

No configuration or stack error

(green)

(green)

(red)

(red)

Flashing acyclic

Flashing cyclic

On

Flashing cyclic

On

Profibus is configured, but bus communication is not yet released from the application

Communication to all Slaves is established

Communication to at least one Slave is disconnected

Communication to one/all Slaves is disconnected

Table 61: LEDs PROFIBUS DP Master

9.4.2 LED PROFIBUS DP Slave

LED

COM

with protocol at X3

Color

The subsequent table describes the meaning of the LEDs for the device when the firmware of the PROFIBUS DP Slave protocol is loaded to the device.

State

Duo LED red/green

Meaning

(green)

On RUN, cyclic communication.

(red)

On Wrong configuration at PROFIBUS-DPside.

(red)

(red)

Flashing cyclic

Flashing acyclic

STOP, no communication, connection error.

Not configured.

Table 62: LED PROFIBUS DP Slave

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 78/122

9.4.3 LED CANopen Master

The subsequent table describes the meaning of the LEDs for the device when the firmware of the CANopen Master protocol is loaded to the device.

State Meaning LED Color

Communication LED

CAN

with protocol at X3

Duo LED red/green

(off)

(green)

(green)

Off

Single flash

STOPPED:

The device is in STOPPED state.

Blinking

RESET:

The device is executing a reset ort he device has no configuration.

PREOPERATIONAL:

The device is in the PREOPERATIONAL state.

(green)

On

OPERATIONAL:

The device is in the OPERATIONAL state.

(red)

(red)

(red)

Single flash

Warning Limit reached:

At least one of the error counters of the CAN controller has reached or exceeded the warning level (too many error frames).

Double flash

On

Error Control Event:

Bus Off:

A guard event (NMT Slave or NMT-master) or a heartbeat event (Heartbeat consumer) has occurred.

The CAN controller is bus off.

Table 63: LED CANopen Master

LED State Definition for CANopen Master for the CAN LED with protocol at X3

Indicator state Definition

On

Off

Flickering

Blinking

Single Flash

Double Flash

The indicator is constantly on.

The indicator is constantly off.

The indicator turns on and off with a frequency of 10 Hz: on for

50 ms, followed by off for 50 ms.

The indicator turns on and off with a frequency of 2,5 Hz: on for

200 ms, followed by off for 200 ms.

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

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 64: LED State Definition for CANopen Master for the CAN LED

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 79/122

9.4.4 LED CANopen Slave

LED

CAN

with protocol at X3

The subsequent table describes the meaning of the LEDs for the device when the firmware of the CANopen Slave protocol is loaded to the device.

Meaning Color State

Duo LED red/green

(off)

Off

(green)

Single flash

(green)

Blinking

(green)

On

(red/green)

(red)

Flickering

(alternatively red / green)

Single flash

(red)

(red)

Double flash

On

RESET:

The device is executing a reset

STOPPED:

The device is in STOPPED state

PREOPERATIONAL:

The device is in the PREOPERATIONAL state

OPERATIONAL:

The device is in the OPERATIONAL state

Auto Baud Rate Detection active:

The Device is in the Auto Baud Rate

Detection mode

Warning Limit reached:

At least one of the error counters of the CAN controller has reached or exceeded the warning level (too many error frames).

Error Control Event:

A guard event (NMT Slave or NMT-master) or a heartbeat event (Heartbeat consumer) has occurred.

Bus Off:

The CAN controller is bus off

Table 65: LEDs CANopen Slave

LED State Definition for CANopen Slave for the CAN LED

Indicator state Definition

On

Off

Flickering

Blinking

Single Flash

Double Flash

The indicator is constantly on.

The indicator is constantly off.

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

The indicator turns on and off with a frequency of 2,5 Hz: on for 200 ms, followed by off for

200 ms.

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

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 66: LED State Definition for CANopen Slave for the CAN LED

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 80/122

9.4.5 LED DeviceNet Master

LED

MNS

with protocol at X3

Color

The subsequent table describes the meaning of the LEDs for the fieldbus device when the firmware of the DeviceNet Master protocol is loaded to the device.

State

Duo LED red/green

Meaning

(green)

On Device is online and has one or more connections in the established state

(green)

Flashing Device is online and has no connection in the established state

(green/red/ off)

Green/Red/

Off

Selftest after power on:

Green on for 0,25 s, then red on for 0,25 s, then off

(red)

(red)

(off)

On

Off

Critical connection failure; device has detected a network error: duplicate

MAC-ID or sever error in CAN network (CAN-bus off)

After start of the device and during duplicate MAC-ID check

Table 67: LEDs DeviceNet Master

9.4.6 LED DeviceNet Slave

LED

MNS

with protocol at X3

The subsequent table describes the meaning of the LEDs for the fieldbus device when the firmware of the DeviceNet Slave protocol is loaded to the device.

State Meaning Color

Duo LED red/green

(green)

On

(green)

(green/red/ off)

Flashing

Green/Red/

Off

Device is online and has one or more connections in the established state

Device is online and has no connection in the established state

Selftest after power on:

Green on for 0,25 s, then red on for 0,25 s, then off

(red)

On Critical connection failure; device has detected a network error: duplicate

MAC-ID or sever error in CAN network (CAN-bus off)

(red)

Off After start of the device and during duplicate MAC-ID check

(off)

Table 68: LEDs DeviceNet Slave

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 81/122

9.5 LEDs Serial

9.5.1 LED Modbus RTU

LED

COM

The subsequent table describes the meaning of the LEDs for the Modbus

RTU protocol.

State Meaning Color

Duo LED red/green

(green)

(red)

(off)

On The device has a valid configuration for Modbus RTU and is ready for

Modbus communication respectively sends/receives Modbus RTU telegrams

On Communication error:

The device works as Modbus RTU Master:

- the slave device answered with a error (Modbus Exception), e. g. functioncode not supported, access to invalid register addresses or coil addresses

- receive error detected, e. g. parity error or checksum error - timeout

(slave device does not answer)

The device works as Modbus RTU Slave:

- the Modbus RTU Master device uses an invalid functioncode

- the Modbus RTU Master device has accessed an invalid register addresses or coil addresses

- receive error detected, e. g. parity error or checksum error

- timeout (application does not answer or answers with error)

The error display is set back with the next error free Modbus telegram sequence

Off During initialisation or invalid Modbus RTU configuration or missing power supply

Table 69: LEDs Modbus RTU Protocol

9.5.2 LED ASCII

LED

COM

The subsequent table describes the meaning of the LEDs for the ASCII protocol.

Color State

Duo LED red/green

Meaning

(green)

(green)

(red)

(red)

(off)

Flashing cyclic with 5 Hz

On

Flashing cyclic with 5 Hz

Flashing cyclic with 1 Hz

Off

The device sends/receive data

The device is ready for serial communication

The device is configured and is in the state stop

The device is not configured

During initialisation or missing power supply

Table 70: LEDs ASCII Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

LEDs 82/122

9.5.3 LED 3964R

LED

COM

The subsequent table describes the meaning of the LEDs for the 3964R protocol.

Color State

Duo LED red/green

Meaning

(green)

(green)

(red)

(red)

(red)

Flashing cyclic with 10 Hz

On

On

Flashing cyclic with 5 Hz

Flashing cyclic with 1 Hz

Off

The device sends/receive data

The device is ready for serial communication

Communication error:

- receive error detected, e. g. parity error or checksum error - timeout

(remote device does not answer)

The error display is set back with the next error free 3964R telegram sequence

The device is configured and is in the state stop

The device is not configured

(off)

During initialisation or missing power supply

Table 71: LEDs 3964R Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 83/122

10 Technical Data

10.1 Technical Data netBRICK NB 100 Gateway

NB 100

Power supply

Environment

Device

Parameter

Communication controller Type

Memory RAM

Diagnostic Interface

Display

FLASH

Socket

LED Display

Value

netX 100

8 MB SDRAM

4 MB serial Flash

Mini-USB, 5-pin

SYS System Status

APL Application Status

COM Communication Status

LINK Link

ACT Activity

Voltage 24 V ± 6 V DC

Current at 24 V (typically) 130 mA

Power Consumption 3.2 W

Connector M12 male connector, A coded

Temperature range

Dimensions (L x W x H)

-20 to +70 °C

138 x 60 x 38 mm (without connectors)

CE Sign

Weight

Mounting appr. 330 g

On a flat metal surface

Protection Class IP67 according to DIN EN 60529

RoHS Yes

CE Sign

Emission

Yes

CISPR 11 class A

UL UL recognized:

UL 1604 and UL 508

Enviroment

Explosion Hazard

UL-File-Nr. E326833

Pollution Degree 2

Class I, Division 2, Groups A,

B, C and D or for non explosive areas

Configuration Software

Connections

SYCON.net

M12 according to DIN EN 61076-2-101/ IEC 61076-2-101

Table 72: Technical Data NB 100 (Part 1)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 84/122

DECLARATION OF CONFORMITY

Manufacturers Name:

Hilscher Gesellschaft für Systemautomation mbH

Address:

Rheinstraße 15, DE 65795 Hattersheim, Germany declares that the product

Product Name:

netBRICK

Trade Name:

Gateway for Harsh Enviroments

Type of Model:

NB 100-aa-bb

Confirms to 47 CFR, Part 15, Subpart B of the FCC rules

Operation is subject to the following two conditions:

(1) This device may not cause harmful interference

(2) This device must accept any interference received, including interference that may cause undesired operation netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 85/122

NB 100

Ethernet Interface for the device types:

NB 100-RE-DP,

NB 100-RE-CO,

NB 100-RE-DN

PROFIBUS Interface for the device type

NB 100-RE-DP,

NB 100-RS-DP

CANopen Interface for the device type

NB 100-RE-CO,

NB 100-RS-CO

DeviceNet Interface for the device type

NB 100-RE-DN,

NB 100-RS-DN

Parameter

Transmission rate

Interface Type

Transmission rate

Interface Type

Connector

Value

100 MBit/s

10 MBit/s (depending on loaded firmware)

100 BASE-TX, isolated

10 BASE-TX (depending on loaded firmware), isolated

Half duplex/Full duplex

Auto-Negotiation supported (at 100 MBit/s) supported (depending on loaded firmware)

Auto-Crossover supported

Connector

Transmission rate

M12 female connector D coded

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

Connector

RS 485, optically isolated

M12 B coded, male and female connector

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

ISO 11898, optically isolated

Transmission rate

Interface Type

Connector

M12 A coded, male and female connector

125 kBit/s,

250 kBit/s,

500 kBit/s

ISO 11898, optically isolated

M12 A coded, male and female connector

Table 73: Technical Data NB 100 (Part 2)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 86/122

NB 100

Serial Interfaces for the device types:

NB 100-RS-CO,

NB 100-RS-DN,

NB 100-RS-DP

Parameter Value

Interface Type RS-232, RS-422, RS-485, optically isolated

Transmission rate ASCII 300 Bit/s

600 Bit/s

1200 Bit/s

2400 Bit/s

4800 Bit/s

9600 Bit/s

19200 Bit/s

38400 Bit/s

57600 Bit/s

115200 Bit/s

Transmission rate

Modbus RTU

4800 Bit/s

9600 Bit/s

19200 Bit/s

38400 Bit/s

57600 Bit/s

115200 Bit/s

Transmission rate 3964R 300 Bit/s,

600 Bit/s,

1200 Bit/s,

2400 Bit/s,

4800 Bit/s,

9600 Bit/s,

19200 Bit/s,

38400 Bit/s,

57600 Bit/s,

115200 Bit/s

Connector M12, B coded, male or female connector

Table 74: Technical Data NB 100 (Part 3)

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.2 Technical Data Real-Time Ethernet Protocols

10.2.1 EtherCAT Master

Parameter

Maximum number of EtherCAT slaves

Maximum number of cyclic input data

Maximum number of cyclic output data

Minimum bus cycle time

Topology

Baud rate

Data transport layer

Configuration File (ethercat.xml)

Description

Maximum 200 Slaves

5760 bytes

5760 bytes

1 ms (fix)

Line

100 MBit/s

Ethernet II, IEEE 802.3

Maximum 1 MByte

87/122

Reference to stack version

The size of the bus configuration file is limited by the size of the

RAM Disk (1 Megabyte)

Only Ethernet Port 0 of the device is used for communication

All CoE Uploads, Downloads and information services must fit in one TLR-Packet. Fragmentation is not supported

Support of Distributed clocks (Slave synchronisation) is always activated

The bus cycle time is fixed to a value of 1000 µs

The watchdog time is fixed to a value of 20 ms

V2.4.x.x

Table 75: Technical Data EtherCAT Master Protocol

10.2.2 EtherCAT Slave

Parameter

Maximum number of cyclic input data

Maximum number of cyclic output data

Description

200 bytes

200 bytes

FMMUs

SYNC Manager

Baud rate

Data transport layer

Limitation

Reference to stack version

3 (netX 100/netX 500)

4 (netX 100/500)

100 MBit/s

Ethernet II, IEEE 802.3

Acyclic communication not supported

LRW is not supported

V2.5.x.x

Table 76: Technical Data EtherCAT Slave Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 88/122

10.2.3 EtherNet/IP Scanner (Master)

Parameter

Maximum number of EtherNet/IP connections

Maximum number of total cyclic input data

Maximum number of total cyclic output data

Maximum number of cyclic input data

Maximum number of cyclic output data

IO Connection type

UCMM, Class 3

Predefined standard objects

Description

64 connections for implicit

5712 bytes

5760 bytes

504 bytes per slave per telegram

504 bytes per slave per telegram

Cyclic, minimum 1 ms (depending on used number of connections and used number of input and output data)

Supported

Identity Object

Message Route Object

Assembly Object

Connection Manager

Ethernet Link Object

TCP/IP Object

Topology

DLR (Device Level Ring)

ACD (Address Conflict Detection)

Reference to stack version

Tree, Line, Ring

Beacon based ’Ring Node’

Supported

DHCP Supported

BOOTP Supported

Baud rates

Data transport layer

10 and 100 MBit/s

Ethernet II, IEEE 802.3

Integrated switch

Limitations

Supported

No acyclic user data communication

CIP Sync Services are not implemented

TAGs are not supported

V2.4.x.x

Table 77: Technical Data EtherNet/IP Scanner (Master) Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.2.4 EtherNet/IP Adapter (Slave)

Parameter

Maximum number of input data

Maximum number of output data

IO Connection (implicit)

IO Connection type

Description

504 bytes

504 bytes

1 exclusive owner, up to 2 listen only

Cyclic, minimum 1 ms

UCMM Supported

Predefined standard objects Identity Object

Message Route Object

Assembly Object

Connection Manager

Ethernet Link Object

TCP/IP Object

Topology

DLR (Device Level Ring)

ACD (Address Conflict Detection)

Reference to firmware/stack version

Tree, Line, Ring

Beacon based ’Ring Node’

Supported

DHCP Supported

BOOTP Supported

Baud rates

Data transport layer

10 and 100 MBit/s

Ethernet II, IEEE 802.3

Integrated switch

Limitations

Supported

No acyclic user data communication

CIP Sync Services are not implemented

TAGs are not supported

V2.6.x.x

Table 78: Technical Data EtherNet/IP Adapter (Slave) Protocol

89/122 netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.2.5 Open Modbus/TCP

Parameter

Maximum number of input data

Maximum number of output data

Maximum number of connections

Acyclic communication

Modbus Function Codes

Protocol Mode

Baud rates

Data transport layer

Reference to stack version

Description

2880 Registers

2880 Registers

16

Read/Write Register:

- Max. 125 Registers per Read Telegram (FC 3, 4, 23),

- Max. 121 Registers per Write Telegram (FC 23),

- Max. 123 Registers per Write Telegram (FC 16)

Read/Write Coil:

- Max. 2000 Coils per Read Telegram (FC 1, 2),

- Max. 1968 Coils per Write Telegram (FC 15)

1,

2,

3,

4,

5,

6,

7,

15,

16,

23 (Function code 23 in server mode only)

Client or Server

10 and 100 MBit/s

Ethernet II, IEEE 802.3

V2.5.x.x

Table 79: Technical Data Open Modbus/TCP Protocol

10.2.6 POWERLINK Controlled Node (Slave)

Parameter

Maximum number of cyclic input data

Maximum number of cyclic output data

Baud rate

Data transport layer

Ethernet POWERLINK version

Limitation

Reference to stack version

Description

1490 bytes

1490 bytes

100 MBit/s, half-duplex

Ethernet II, IEEE 802.3

V 2

No acyclic communication

No slave to slave communication

V2.1.x.x

Table 80: Technical Data POWERLINK Controlled Node (Slave) Protocol

90/122 netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 91/122

10.2.7 PROFINET IO-RT-Controller

Parameter

Maximum number of PROFINET IO Devices

Maximum number of total cyclic input data

Maximum number of total cyclic output data

Maximum number of cyclic input data

Maximum number of cyclic output data

Supported Protocols

Context management by CL-RPC

Minimum cycle time

Baud rate

Data transport layer

Configuration File

Limitations

Reference to stack version

Description

128

5712 bytes

5760 bytes

1024 bytes per device (= IOCR data length)

1024 bytes per device (= IOCR data length)

RTC – Real Time Cyclic Protocol, Class 1

RTA – Real Time Acyclic Protocol

DCP – Discovery and configuration Protocol

CL-RPC – Connectionless Remote Procedure Call

Supported

1 ms

Different IO-Devices can be configured with different cycle times

100 MBit/s

Full-Duplex mode

Ethernet II, IEEE 802.3

Maximum 1 MByte

Read/Write Record not supported

No Alarm processing

RT over UDP not supported

Multicast communication not supported

DHCP is not supported

Only one IOCR per IO Device

NameOfStation of IO Controller CANNOT be set using the DCP

SET NameOfStation service but only at start-up while configuring the IO Controller

SNMP not supported

LLDP not supported

The buffer for IO-Device diagnosis data will be overwritten in case of multiple diagnostic events. Only one (the last) event is stored at the same time. If a single event produces more than 200 bytes of diagnosis data, only the first 200 bytes will be taken care of.

The usable (minimum) cycle time depends on the number of used

IO Devices, the number of used input and output data. The cycletime, the number of configured IO Devices and the amount of IO data depend on each other. For example it is not possible due to performance reasons to have 128 IO Devices communication with cycle-time 1ms.

The size of the bus configuration file is limited by the size of the

RAM Disk (1 MByte)

Only one API (API = 0) is supported. Any Profile requesting a different API is currently not supported.

The IO-Device feature “FastStartUp” can not be used

WriteMultiple-Record service is not supported

V2.4.x.x

Table 81: Technical Data PROFINET IO RT Controller

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 92/122

10.2.8 PROFINET IO-RT-Device

Parameter

Maximum number of cyclic input data

Maximum number of cyclic output data

Supported protocols

Used Protocols (subset)

Topology recognition

VLAN- and priority tagging

Context Management by CL-RPC

Minimum cycle time

Baud rate

Data transport layer

Limitations

Reference to stack version

Description

1024 bytes

1024 bytes

RTC – Real Time Cyclic Protocol, Class 1 and 2 (unsynchronized)

RTA – Real Time Acyclic Protocol

DCP – Discovery and configuration Protocol

CL-RPC – Connectionless Remote Procedure Call

LLDP – Link Layer Discovery Protocol

SNMP – Simple Network Management Protocol

UDP, IP, ARP, ICMP (Ping)

LLDP, SNMP V1, MIB2, physical device yes

Supported

1 ms for RTC1 and RTC2

100 MBit/s

Ethernet II, IEEE 802.3

No acyclic user data transfer

RT over UDP not supported

Multicast communication not supported

DHCP is not supported

RT Class 2 synchronized (IRT “flex”) is not supported

RT Class 3 synchronized not supported

FastStartUp is not supported.

Media Redundancy is not supported

Access to the submodule granular status bytes (IOCS) is not supported.

The amount of configured IO-data influences the minimum cycle time that can be reached.

Supervisor-AR is not supported, Supervisor-DA-AR is supported

Only 1 Input-CR and 1 Output-CR are supported

Multiple WriteRequests are not supported

V3.4.x.x

Table 82: Technical Data PROFINET IO RT Device Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.2.9 sercos Master

Parameter

Maximum number of cyclic input data

Maximum number of cyclic output data

Maximum number of configured slave devices

Minimum cycle time

Acyclic communication

93/122

Description

5760 bytes (including Connection Control per Connection)

5760 bytes (including Connection Control per Connection)

511

250 µs

Service channel: Read/Write/Commands (for configuration only)

Communication phases

Topology

Redundancy

Baud rate

Data transport layer

Auto crossover

Supported sercos version

Limitations

Reference to stack version

NRT, CP0, CP1, CP2, CP3, CP4

Line and double ring supported

100 MBit/s, full duplex

Ethernet II, IEEE 802.3 supported

Communication Specification Version 1.1.1/1.1.2

No acyclic user data transfer

NRT channel not supported

Hot-Plug not supported

Cross Communication not supported

Ring healing (needed for redundancy) is only available if the Master has a configuration

V2.0.x.x

Table 83: Technical Data sercos Master Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 94/122

10.2.10 sercos Slave

Parameter

Maximum number of cyclic input data (Tx)

Maximum number of cyclic output data (Rx)

Maximum number of slave devices

Maximum number of applicable sercos addresses

Minimum cycle time

Topology

Communication phases

Baud rate

Data transport layer

Supported sercos version

Supported sercos Communication Profiles

Supported FSP profiles

SCP_NRTPC support

S/IP support

Identification LED feature supported

Limitations

Description

128 bytes (including Connection Control and IO Status)

128 bytes (including Connection Control and IO Control)

1

1 … 511

250 µs

Line and ring

NRT, CP0, CP1, CP2, CP3, CP4

100 MBit/s

Ethernet II, IEEE 802.3 sercos in the third generation

Communication Specification Version 1.1.2

SCP_FixCFG Version 1.1.1

SCP_VarCFG Version 1.1.1

SCP_VarCFG Version 1.1.3

FSP_IO

Yes

Yes

Yes

Max. 2 connections: 1 for consumer and 1 for producer

No acyclic user data transfer

Modifications of the Service-Channel Object Dictionary will be volatile after reset, if it resides on device

Hot plug is not supported

Cross communication not supported

NRT Channel only forwarding and S/IP

Reference to stack version V3.1.x.x

Table 84: Technical Data sercos Slave Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 95/122

10.3 Technical Data Fieldbus Protocols

10.3.1 CANopen Master

Parameter

Maximum number of CANopen nodes

Maximum number of cyclic input data

Maximum number of cyclic output data

Maximum number of receive PDOs

Maximum number of transmit PDOs

Exchange of process data

Functions

Baud rates

Data transport layer

CAN Frame type for CANopen

Limitations

Reference to stack version

Description

126

3584 bytes

3584 bytes

512

512

Via PDO transfer:

- synchronized,

- remotely requested and

- event driven (change of date)

Emergency message (consumer)

Node guarding / life guarding, heartbeat

PDO mapping

NMT Master

SYNC protocol (producer)

Simple boot-up process, reading object 1000H for identification

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 Frames

11 Bit

SDO-Upload/Download for user data transfer not supported

V2.9.x.x

Table 85: Technical Data CANopen Master Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 96/122

10.3.2 CANopen Slave

Parameter

Maximum number of cyclic input data

Maximum number of cyclic output data

Maximum number of receive PDOs

Maximum number of transmit PDOs

Exchange of process data

Functions

Baud rates

Data transport layer

CAN Frame type for CANopen

Limitations

Reference to stack version

Description

512 bytes

Objects 2200, 2201, 2202, 2203 each with up to 128 bytes

512 bytes

Objects 2000, 2001, 2002, 2003 each with up to 128 bytes

64

64

Via PDO transfer

- synchronized,

- remotely requested and

- event driven (change of date, event timer)

Node guarding / life guarding, heartbeat

PDO mapping

NMT Slave

SYNC protocol (consumer)

SDO upload/download (server, for configuration)

Emergency message (producer)

10 kBits/s,

20 kBits/s,

50 kBits/s,

100 kBits/s,

125 kBits/s,

250 kBits/s,

500 kBits/s,

800 kBits/s,

1 MBits/s

Auto baudrate detection is supported

CAN Frames

11 Bit

Timestamp (producer/consumer) not supported on application level.

V3.0.x.x

Table 86: Technical Data CANopen Slave Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.3.3 DeviceNet Master

Parameter

Maximum number of DeviceNet slaves

Maximum number of total cyclic input data

Maximum number of total cyclic output data

Maximum number of cyclic input data

Maximum number of cyclic output data

Maximum configuration data

Baud rates

Data transport layer

Description

63

3584 bytes

3584 bytes

255 bytes/connection

255 bytes/connection

1000 bytes/slave

125 kBits/s,

250 kBit/s,

500 kBit/s

Auto baudrate detection is not supported

CAN frames

Change of State

Cyclic

Poll

Explicit Peer-to-Peer Messaging

97/122

Fragmentation

Function

Explicit and I/O

Proxy for explicit messaging for user communication to all ‚group

2 only’ slaves

UCMM Supported

Objects Identity Object (Class Code 0x01)

Baud rates

Data transport layer

Message Router Object (Class Code 0x02)

DeviceNet Object (Class Code 0x03)

Connection Object (Class Code 0x05)

Acknowledge Handler Object (Class Code 0x06)

125 kBits/s,

250 kBit/s,

500 kBit/s

Auto baudrate detection is not supported

CAN frames

Limitations

Reference to stack version

User data transfer through the gateway only via IO connections

V2.3.x.x

Table 87: Technical Data DeviceNet Master Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.3.4 DeviceNet Slave

Parameter

Maximum number of cyclic input data

Description

255 bytes

Maximum number of cyclic output data 255 bytes

Connections Poll

Change-of-state

Cyclic

Fragmentation

Bit-strobe

Explicit and I/O

Baud rates

Data transport layer

Limitations

Reference to stack version

125 kBits/s,

250 kBit/s,

500 kBit/s

Auto baudrate detection is not supported

CAN frames

Access to Application Object only via IO connection

V2.3.x.x

Table 88: Technical Data DeviceNet Slave Protocol

98/122 netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.3.5 PROFIBUS DP Master

Parameter

Maximum number of PROFIBUS DP slaves

Maximum number of total cyclic input data

Maximum number of total cyclic output data

Maximum number of cyclic input data

Maximum number of cyclic output data

Configuration data

Parameterization data per slave

Baud rate

Data transport layer

Limitations

Reference to stack version

Description

125

5712 bytes

5760 bytes

244 bytes/slave

244 bytes/slave

Max. 244 bytes per slave

7 bytes/slave standard parameters

Max. 237 bytes/slave application specific parameters

9,6 kBits/s,

19,2 kBits/s,

31,25 kBits/s,

45,45 kBits/s

93,75 kBits/s,

187,5 kBits/s,

500 kBits/s,

1, 5 MBits/s,

3 MBits/s,

6 MBits/s,

12 MBit/s

Auto baud rate detection is not supported

PROFIBUS FDL

DP V1 services class 1 and 2 are not supported

DP V2 services are not supported

V2.5.x.x

Table 89: Technical Data PROFIBUS DP Master Protocol

99/122 netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 100/122

10.3.6 PROFIBUS DP Slave

Parameter

Maximum number of cyclic input data

Maximum number of cyclic output data

Maximum number of modules

Baud rate

Data transport layer

Limitations

Reference to firmware/stack version

Description

244 bytes

244 bytes

Max. 4 input modules and max. 4 output modules, max. 24 modules when using manual setting

9,6 kBits/s,

19,2 kBits/s,

31,25 kBits/s,

45,45 kBits/s

93,75 kBits/s,

187,5 kBits/s,

500 kBits/s,

1, 5 MBits/s,

3 MBits/s,

6 MBits/s,

12 MBit/s

Auto baudrate detection is supported

PROFIBUS FDL

DP V1 services class 1 and 2 to transfer user data are not supported

SSCY1S – Slave to slave communication state machine not implemented

Data exchange broadcast not implemented

I&M0 with fixed settings only

V2.4.x.x

Table 90: Technical Data PROFIBUS DP Slave Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 101/122

10.4 Technical Data serial Protocols

10.4.1 ASCII

Parameter

Maximum telegram length

Data bits

Reference to stack version

Description and Value Range

1024 bytes

7, 8 bits

Stop bits

Parity

Baud rate

1, 2 bit(s)

None, even, odd

300 bit/s,

600 bit/s,

1200 bit/s,

2400 bit/s,

4800 bit/s,

9600 bit/s,

19200 bit/s,

38400 bit/s,

57600 bit/s,

115200 bit/s

Duplex Half-duplex

Flow control None

Indicator for end of received telegram

Timing parameter

Number of send buffers

Number of receive buffers

Number of transmission retries

Maximum number of structure elements of a send telegram

Maximum number of structure elements of a receive telegram

Structure elements

On receipt of a fixed number of characters

On receipt of termination character(s)

Elapse of character delay time

Response timeout

Receive watchdog time

Send cycle time

1

1

Character delay time

1

10

10

Start character(s),

Device address,

Object index or start address,

Command identifier,

Data area with length information,

Data area with termination character(s),

End character(s),

Checksum,

Character(s) without meaning (fix length)

Checksum methods CRC8,

CRC16,

CRC32,

Exor

V1.0.x.x

Table 91: Technical Data ASCII Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data

10.4.2 Modbus RTU Master/Slave

Parameter

Maximum number of input data

Maximum number of output data

Acyclic communication

Function Codes Modbus Master

Function Codes Modbus Slave

Mode

Modbus Address

Baud rates

Data bits

Stop bits

Parity

Limitations

Reference to stack version

Description and Value Range

2880 Registers

2880 Registers

Read/Write Register,

Maximum 125 Registers per Read Telegram (FC 3, 4),

Maximum 123 Registers per Write Telegram (FC 16),

Maximum 118 Registers per Write Telegram (FC 23),

Maximum 118 Registers per Read Telegram (FC 23)

Read/Write Coil,

Maximum 2000 Coils per Read Telegram (FC 1, 2),

Maximum 1968 Coils per Write Telegram (FC 15)

1, 2, 3, 4, 5, 6, 15, 16

1, 2, 3, 4, 5, 6, 7, 8, 15, 16, 23

Modbus Master or Modbus Slave

1 ... 247

1200 bit/s,

2400 bit/s,

4800 bit/s,

9600 bit/s,

19200 bit/s,

38400 bit/s,

57600 bit/s,

115200 bit/s

8 bits

1, 2 bit(s)

None, even, odd

Broadcast not supported

V1.3.x.x

Table 92: Technical Data Modbus RTU Protocol

102/122 netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Technical Data 103/122

10.4.3 3964R

Parameter

Maximum Telegram Length

Data Bits

Stop Bits

Parity

Baud Rate

Description and Value Range

5736 bytes

7, 8 bits

1, 2 bit(s)

None, even, odd

300 bit/s,

600 bit/s,

1200 bit/s,

2400 bit/s,

4800 bit/s,

9600 bit/s,

19200 bit/s,

38400 bit/s,

57600 bit/s,

115200 bit/s

Duplex Half-duplex

Priority Adjustable: High or low Priority

Timing Parameter Acknowledge Timeout

Character Delay Time

Number of Send Buffers

Number of Receive Buffers

Number of Transmission Retries

1

Ring Buffer with 30 buffers (FIFO)

Adjustable

Checksum Method

Reference to stack version

BCC

V0.9.x.x

Table 93: Technical Data 3964R Protocol

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 104/122

11 Wiring Instructions

Please note the wiring instructions for the corresponding protocol specifications, otherwise a perfect function of the device is not guaranteed.

11.1 PROFIBUS

Please ensure that termination resistors are available at both ends of the cable. If special PROFIBUS connectors are being used, these resistors are often found inside the connector and must be switched on. For baud rates above 1.5 MBaud use only special connectors, which also include additional inductance.

It is not permitted to have T-stubs on PROFIBUS high baud rates. Use only a special cable which is approved for PROFIBUS-DP. Make a solid connection from the cable shield to ground at every device and make sure that there is no potential difference between the grounds at the devices.

If the Hilscher device is linked with only one other device on the bus, they must be at the ends of the bus line. The reason is that these devices must deliver the power supply for the termination resistors. Otherwise the Master can be connected at any desired position.

Figure 25: PROFIBUS-DP Network M12 Pinning

The figure shows the pinning for M12 connectors. Please note that the pinning differs from the figure above for other connector types.

Up to 32 PROFIBUS devices can be connected to one bus segment. If several bus segments are linked to each other with repeaters, there can be up to 127 devices on the network.

Only PROFIBUS certified cable, preferably the cable type A, should be used.

The maximum length of a bus segment depends on the baud rate used,

see Table 94: PROFIBUS Segment Length in Dependence of the Baud

Rate

on page 105.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 105/122

Baud rate in kBit/s Max. distance in m

9,6 1.200

19,2 1.200

93,75 1.200

187,5 1.000

500 400

1.500 200

3.000 100

6.000 100

12.000 100

Table 94: PROFIBUS Segment Length in Dependence of the Baud Rate

The following table contains the most important electrical dsata concerning

PROFIBUS certified cable:

Parameter Value

Capacity

Loop resistance

Wire gauge

< 30 pF/m

110 Ω/km

0,64 mm

Table 95: Characteristics of PROFIBUS certified Cable

For the pinout for PROFIBUS see section X3 PROFIBUS Interface on page

36.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 106/122

11.2 CANopen

Please use only CAN certified cable with the following characteristics:

Parameter Value

Capacity < 50 pF/m

Table 96: Characteristics of CAN certified Cable

Figure 26: Termination CANopen Network

The pin numbers inthe figure above refer to M12 connectors. If you use devices in the network with other types of connectors, take care that the pin numbers of those devices can be different from the figure above.

At the ends of the network there must be two resistors of 120 Ω to terminate the cable. It is allowed to use repeaters to increase the number of nodes, which may be connected, or to increase the maximum cable length.

The CAN segment length in dependence of the Baud rate or corresponding

Loop Resistance and Wire Gauge is given in the following table:

Baud rate in kBit/s s

Max. distance Loop Resistance Wire Gauge

1.000 30

Table 97: CAN Segment Length in dependence of the Baud rate or corresponding Loop Resistance and Wire Gauge

For the pinout for CANopen see section X3 CANopen Interface on page 37.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 107/122

11.3 DeviceNet

Up to 64 DeviceNet devices can be linked together over the bus. The maximum length of the bus cable depends on the used baud rate and the used cable type. Only special proved DeviceNet cable should be used.

The maximum length of the DeviceNet cable depends from the baud rate and from the chosen cable type. In the following table, these are listed in the following table:

Baudrate in kbit/s Maximum length of cable (thick cable)

Maximum length of cable (thick cable)

125

250

500

500 m

250 m

100 m

100 m

100 m

100 m

Table 98: Maximum length in dependence from the Baud Rate for DeviceNet Cables

The data line cables must match the following conditions:

Data line cable

Impedance

Thick 120 Ohm

Thin 120 Ohm

Capacity

<39,4 pf/m

<39,4 pf/m

Loop Resistance

Wire

Gauge

(Diameter)

<22,6 Ohm/km 2 * 1.1 mm

<91,8 Ohm/km 2 * 0,6 mm

Table 99 Characteristics of DeviceNet Data Line Cable

The power supply cables must match the following conditions:

Power supply cable

Loop Resistance

Wire Gauge

(Diameter)

Thick <11,8 Ohm/km 2 * 1.4 mm

Thin <57,4 Ohm/km 2 * 0,7 mm

Table 100: Characteristics of DeviceNet Power Supply Cable

Figure 27: DeviceNet Network with M12 Connectors

Please ensure that termination resistors with 120 Ohm are available at both ends of the cable.

Further devices can be connected via T-stubs to the bus cable. The maximum length of all T-stubs is 6 m. The whole length of the bus cable and all

T-stubs does not exceed the maximum length listed in the following table. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 108/122

There are two different types of cables. If both cables types are used within the same network, the maximum length is:

Max. distance Baud rate in kBits/s

L thick

+ 5 x L thin

<= 500 m

L thick

+ 2,5 x L thin

<= 250 m

L thick

+ L thin

<= 100 m at 125 kBaud at 250 kBaud at 500 kBaud

Table 101: DeviceNet Segment Length in dependence of the Baud rate

The DeviceNet cable contains the data line cables and the power supply cables.

For the pinout for DeviceNet see section X3 DeviceNet Interface on page

38.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 109/122

11.4 Ethernet

For the pinout for Ethernet see section X2 Ethernet Connection on page 34.

Use of Hubs and Switches

For the corresponding communication systems, the use of hubs and/or switches is either forbidden or allowed. The following table shows the acceptable use of hubs and switches by each communication system:

Communication System Hub Switch

EtherCAT

EtherNet/IP

Open Modbus/TCP

POWELINK

PROFINET IO RT sercos

forbidden allowed allowed only allowed between EtherCAT Master and first EtherCAT Slave

(100 MBit/s, Full Duplex) allowed

(10 MBit/s/100 MBit/s,

Full or Half Duplex, Auto-Negotiation) allowed

(10 MBit/s/100 MBit/s,

Full or Half Duplex, Auto-Negotiation) allowed forbidden forbidden Only allowed, if the switch supports ‚Priority Tagging’ and LLDP

(100 MBit/s, Full Duplex) forbidden forbidden

Table 102: Use of Hubs and Switches

Failure of the Network Communication

 Do not operate hardware with the communication controllers netX 50, netX100 or netX 500 with the protocols Ethernet TCP/UDP/IP, Ether-

Net/IP or Modbus TCP at 10 MBit/s in half-duplex mode, otherwise failure of the network communication can occure.

 Use only switches or 10/100 MBit/s dual-speed hubs and ensure that the network operates at 100 MBit/s and in full-duplex mode.

For further information refer to section Failure in 10 MBit/s Half Duplex

Mode and Workaround

on page 62.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions

11.5 RS-232

110/122

The RS232 interface (EIA-232) is a point-to-point connection of two communication devices. Only shielded cables have to be used. No termination resistors are required.

Take care of the pin assignment at the communication partner. This decides, whether you need a so called null modem cable with crossed pin assignments.

Figure 28: RS-232 Null-Modem Cable Connection

* Pinout for the communication partner: See device description of the used device.

Take into consideration the setting for RTS Control in the parameters of the used protocol (Modbus RTU, ASCII and 3964R).

Parameter RTS Control

RTS Control Off

Cable / Remote Device (Communication Partner)

No wires for CTS and RTS are needed in the cable.

RTS Control On Wires for CTS and RTS are needed in the cable.

Conductor length and transmission rates

In the EIA-232 norm a maximum cable capacitance of 2500 pF is allowed for a RS232 connection.

max. baud rate max. Length

19.200 15

Cables of such capacitance may have the following lengths depending on the baud rate

57.600 5

115.200 <2

Higher length can be achieved with cables of extraordinarily low capacitance.

For the pinout for the serial interface see section X2 Serial Connection on page 35.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions

11.6 RS-422

111/122

The lines of this industry bus interface are operated in push-pull action, four lines are required which can be controlled in half duplex or full duplex mode. This interface has been designed for one master and at maximum

10 slaves. Using repeaters, using even more slaves is possible.

Cable lengths of up to 1.2 km (at low baud rates) and data transmission rates of up to 10 MBit/s (at maximally 12 m length of line) are possible. The maximum useable transmission rate depends on the technical data of the used devices.

The following illustration shows wiring for RS-422:

Figure 29: RS-422 Wiring

Bus Requirements:

The bus cable must be a shielded 4.wire twisted pair cable. Each pair of wires has to be used for exactly one data transmission direction. The shield should be connected at both ends to the potential equalization system.

On each end, the bus requires a termination resistor (LT) of 90 Ω to 150 Ω between the lines. This value depends on the characteristic wave impedance of the cable.

The pull-up and pull-down resistors should have a resistance of 390 Ω up to

650 Ω. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 112/122

Cable Requirements:

The workmanship of bus cabling is an important factor of the reliable operation and also for the electromagnetic compatibility and emission. It is mandatory to use shielded twisted-pair cables. The shield of the cable must consist of a copper wire mesh.

Parameter Value

150 Ω ± 15 Ω Characteristic wave impedance

Capacitance

Loop resistance

Wire gauge

< 30 pF/m

110 Ω/km

0,64 mm

Table 103: Electric Requirements to RS-422 Cables

The following lengths of lines can be achieved:

Max. overall length of line

Max. Baud rate

Max. length of a single branch line

120 m

600 m

1200 m

1 MBit/s

500 kBit/s

100 kBit/s

0,3 m

0,6 m

1,5 m

Table 104: RS-422 Conductor Length and Transmission Rates

For the pinout for the serial interface see section X2 Serial Connection on page 35.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions

11.7 RS-485

113/122

The lines of this industry bus interface are operated in push-pull action, only two lines are required which can be controlled in half duplex or full duplex mode. The advantage of the 2-wire technology mainly consists in the multimaster capability. In principle, each participant is able to exchange data with any other participant. However, synchronous send attempts of two or more participants must be prevented by the applied protocol. The RS-485 interface allows the connection of up to 32 transmitters and receivers using a protocol. (With repeaters even more participants are possible.)

Nowadays, RS-485 supports cable lengths of up to 1.2 km (see Table 106:

RS-485 Cable

Lengths on page 114) and data transmission rates of up to 1

MBit/s. The maximum useable transmission rate depends on the technical data of the used devices.

The following illustration shows wiring for RS-485:

Figure 30: RS-485 Wiring

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Wiring Instructions 114/122

Bus requirements:

The bus cable must be a shielded twisted pair cable where the shield should be connected at both ends with large contact areas to the potential equalization system.

On each end, the bus requires a termination resistor (LT) between the lines

D1 und D0 of approximately the amount of the characteristic wave impedance of the cable, which usually amounts to a value between 120 Ω and

220 Ω.

The pull-up and pull-down resistors should have a value of 390 Ω up to

650 Ω.

Cable requirements:

The workmanship of bus cabling is an important factor of the reliable operation and also for the electromagnetic compatibility and emission. It is mandatory to use shielded twisted-pair cables. The shield of the cable must consist of a copper wire mesh.

Parameter Value

150 Ω ± 15 Ω Characteristic wave impedance

Capacitance

Loop resistance

Wire gauge

< 30 pF/m

110 Ω/km

0,64 mm

Table 105: Electric Requirements to RS-485 Cables

The following lengths of lines can be achieved:

Max. overall length of line

Max. Baud rate Max. length of a single branch line

120 m

600 m

1200 m

1 MBit/s

500 kBit/s

100 kBit/s

0,3 m

0,6 m

1,5 m

Table 106: RS-485 Cable Lengths

For the pinout for the serial interface see section X2 Serial Connection on page 35.

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Decommissioning/Disposal 115/122

12 Decommissioning/Disposal

12.1 Decommissioning

Obey to the following safety messages, when decommissioning the net-

BRICK NB 100 device.

Danger of unsafe System Operation!

 To prevent harm of persons and property damage, do not remove this device under runtime conditions before you can not guarantee further a safe and secure operation of the plant.

Danger of unsafe System Operation!

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

Refer also to the notes in the section„Dismounting“ on page 49.

12.2 Disposal of Waste Electronic Equipment

According to the European Directive 2002/96/EG “Waste Electrical and

Electronic Equipment (WEEE)”, waste electronic equipment may not be disposed of as household waste. As a consumer, you are legally obliged to dispose of all waste electronic equipment according to national and local regulations.

Waste Electronic Equipment

 This product must not be treated as household waste.

This product must be disposed of at a designated waste electronic equipment collecting point. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Glossary 116/122

13 Glossary

Auto-Crossover

Auto-Crossover is a feature of an interface: An interface with Auto-

Crossover capability will automatically detect and correct if the data lines have been exchanged vice versa.

Baud rate

Data transmission speed of a communication channel or interface.

Boot loader

Program loading the firmware into the memory of a device in order to be executed.

Division 2

HAZARD Division 2: The presence of explosive gas os less than 10 hours per year.

EtherCAT

A communication system for industrial Ethernet designed and developed by

Beckhoff Automation GmbH.

EtherNet/IP

A communication system for industrial Ethernet designed and developed by

Rockwell. It partly uses the CIP (Common Industrial Protocol).

Ethernet Powerlink

A communication system for industrial Ethernet designed and developed by

B&R. It partly uses CANopen technologies.

Gateway

A device interfacing between two different communication standards.

GND

Reference potential

Groups

Groups A, B, C, D denotes classes of substances with different hazard potential.

Hazard Class I

Class I is hazardous area

ISO GND

Isolated reference potential, isolated from other device areas.

PE

Potential equalization line, Potential equalization line of the process plant. netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Glossary

Pollution Degree 2

117/122

Usually only electrically non-conductive pollution occur. Occasionally, temporarily electrical conductivity caused by condensation must be reckoned.

PROFINET

A communication system for Industrial Ethernet designed and developed by

PROFIBUS International. It uses some mechanisms similar to those of the

PROFIBUS field bus.

Real-Time Ethernet

Real-Time Ethernet (also denominated as Industrial Ethernet) is an extension of the Ethernet networking technology for industrial purposes with very good Real-Time features and performance. There is a variety of different

Real-Time Ethernet systems on the market which are incompatible with each other. The most important systems of these are

 EtherCAT

 EtherNet/IP

 Ethernet Powerlink

 PROFINET

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Appendix

14 Appendix

14.1 List of Figures

Figure 1: Function netBRICK

Figure 2: Dimensioned Drawing

Figure 3: Drilling Template

Figure 4: Device Label

Figure 5: LEDs and Control Elements NB 100-RE-XX

Figure 6: LEDs and Control Elements NB 100-RS-xx

Figure 7: Diagnostic Interface

Figure 8: Galvanic Isolation NB 100 RE-DP Device

Figure 9: Galvanic Isolation NB 100-RE-DN/CO Device

Figure 10: Galvanic Isolation NB 100-RS-DP Device

Figure 11: Galvanic Isolation NB 100-RS-DN/CO Device

Figure 12: USB Installation in Bootloader Mode Step 1

Figure 13: USB Installation in Bootloader Mode Step 2

Figure 14: USB Installation in Bootloader Mode Step 3

Figure 15: USB Installation in Bootloader Mode Step 4

Figure 16: USB Installation in Bootloader Mode Step 5

Figure 17: USB Installation in Bootloader Mode Step 6

Figure 18: USB Installation in Bootloader Mode Step 7

Figure 19: ComProX Start

Figure 20: ComProX Choice of Connection

Figure 21: ComProX Choice File Explorer

Figure 22: ComProX File Explorer - NB 100 File System Structure

Figure 23: ComProX File Explorer - File Menu 1

Figure 24: ComProX File Explorer - File Menu 2

Figure 25: PROFIBUS-DP Network M12 Pinning

Figure 26: Termination CANopen Network

Figure 27: DeviceNet Network with M12 Connectors

Figure 28: RS-232 Null-Modem Cable Connection

Figure 29: RS-422 Wiring

Figure 30: RS-485 Wiring

118/122

104

106

107

110

111

113

58

58

59

59

56

56

57

57

54

54

55

55

43

44

45

53

31

32

40

41

22

29

29

30

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Appendix 119/122

14.2 List of Tables

Table 1: List of Revisions

Table 2: Reference to Hardware

Table 3: Reference to Software

Table 4: Reference to Driver

Table 5: Directory Structure of the DVD

Table 6: Device Description Files for netBRICK NB 100 on the DVD

Table 7: Basic Documentation for netBRICK NB 100

Table 8: Additional Documentation for netBRICK NB 100 with EtherCAT Master

Table 9: Additional Documentation for netBRICK NB 100 with EtherNet/IP Scanner/Master

Table 10: Additional Documentation for netBRICK NB 100 with PROFINET IO Controller

Table 11: Additional Documentation for netBRICK NB 100 with EtherCAT Master

Table 12: Additional Documentation for netBRICK NB 100 with CANopen Master

Table 13: Additional Documentation for netBRICK NB 100 with DeviceNet Master

Table 14: Additional Documentation for netBRICK NB 100 with PROFIBUS DP Master

Table 15: Additional Documentation for netBRICK NB 100 with ASCII

Table 16: Additional Documentation for netBRICK NB 100 with 3964R

Table 17: Safety Symbols and Sort of Warning or Principle

Table 18: Signal Words

Table 19: Network on Port X2 (Primary Network)

Table 20: Network on Port X3 (Secondary Network)

Table 21: Protocol Conversion - Ethernet to Fieldbus (Part 1)

Table 22: Protocol Conversion - Ethernet to Fieldbus (Part 2)

Table 23: Protocol Conversion – Serial Protocols to Fieldbus

Table 24: LED (20) – Labeling

Table 25: LED (20) – Labeling

Table 26: X1 Power Supply Line Pin Assignment

Table 27: Ethernet Pin Assignment

Table 28: Ethernet Pin Assignment

Table 29: M12 RS-232 Pin Assignment

Table 30: RS-422 M12 Pin Assignment

Table 31: RS-485 M12 Pin Assignment

Table 32: PROFIBUS M12 RS-485 Pin Assignment

Table 33: PROFIBUS M12 Pin Assignment

Table 34: CANopen M12 Pin Assignment

Table 35: CANopen M12 Pin Assignment

Table 36: DeviceNet M12 Pin Assignment

Table 37: DeviceNet M12 Pin Assignment

Table 38: Pin Assignment Mini-B USB Connector (5 pin)

Table 39: Coupling NB 100-RE-DP Device

Table 40: Galvanic Isolation NB 100-RE-DN/CO Device

Table 41: Galvanic Isolation NB 100-RS-DP Device

Table 42: Galvanic Isolation NB 100-RS-DN/CO Device

Table 43: NB 100 Troubleshooting

Table 44: System LED

Table 45: LED APL

Table 46: LEDs EtherCAT Master

Table 47: LED State Definition for EtherCAT Master for the RUN and ERR LEDs

Table 48: LEDs EtherCAT Slave

Table 49: LED State Definition for EtherCAT Slave for the RUN and ERR LEDs

Table 50: LEDs EtherNet/IP Scanner (Master)

Table 51: LEDs EtherNet/IP Adapter (Slave) netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

35

35

35

36

32

33

34

34

24

25

26

31

21

21

23

23

14

14

14

14

13

13

13

13

10

11

12

12

7

9

9

9

63

64

64

65

44

45

61

63

38

40

42

43

36

37

37

38

66

67

68

Appendix 120/122

Table 52: LEDs Open Modbus/TCP

Table 53: LEDs Powerlink Controlled Node/Slave

Table 54: LED State Definition for Powerlink Controlled Node/Slave for the BS/BE LEDs

Table 55: LEDs PROFINET IO-RT Controller

Table 56: LEDs PROFINET IO-RT-Device

Table 57: LEDs sercos Master

Table 58: LED State Definition for sercos Master for the STA and ERR LEDs

Table 59: LEDs sercos Slave

Table 60: LED State Definition for sercos Slave for the S3 LED (STA LED)

Table 61: LEDs PROFIBUS DP Master

Table 62: LED PROFIBUS DP Slave

Table 63: LED CANopen Master

Table 64: LED State Definition for CANopen Master for the CAN LED

Table 65: LEDs CANopen Slave

Table 66: LED State Definition for CANopen Slave for the CAN LED

Table 67: LEDs DeviceNet Master

Table 68: LEDs DeviceNet Slave

Table 69: LEDs Modbus RTU Protocol

Table 70: LEDs ASCII Protocol

Table 71: LEDs 3964R Protocol

Table 72: Technical Data NB 100 (Part 1)

Table 73: Technical Data NB 100 (Part 2)

Table 74: Technical Data NB 100 (Part 3)

Table 75: Technical Data EtherCAT Master Protocol

Table 76: Technical Data EtherCAT Slave Protocol

Table 77: Technical Data EtherNet/IP Scanner (Master) Protocol

Table 78: Technical Data EtherNet/IP Adapter (Slave) Protocol

Table 79: Technical Data Open Modbus/TCP Protocol

Table 80: Technical Data POWERLINK Controlled Node (Slave) Protocol

Table 81: Technical Data PROFINET IO RT Controller

Table 82: Technical Data PROFINET IO RT Device Protocol

Table 83: Technical Data sercos Master Protocol

Table 84: Technical Data sercos Slave Protocol

Table 85: Technical Data CANopen Master Protocol

Table 86: Technical Data CANopen Slave Protocol

Table 87: Technical Data DeviceNet Master Protocol

Table 88: Technical Data DeviceNet Slave Protocol

Table 89: Technical Data PROFIBUS DP Master Protocol

Table 90: Technical Data PROFIBUS DP Slave Protocol

Table 91: Technical Data ASCII Protocol

Table 92: Technical Data Modbus RTU Protocol

Table 93: Technical Data 3964R Protocol

Table 94: PROFIBUS Segment Length in Dependence of the Baud Rate

Table 95: Characteristics of PROFIBUS certified Cable

Table 96: Characteristics of CAN certified Cable

105

105

106

Table 97: CAN Segment Length in dependence of the Baud rate or corresponding Loop Resistance and Wire

Gauge

106

Table 98: Maximum length in dependence from the Baud Rate for DeviceNet Cables

Table 99 Characteristics of DeviceNet Data Line Cable

Table 100: Characteristics of DeviceNet Power Supply Cable

107

107

107

108

Table 101: DeviceNet Segment Length in dependence of the Baud rate

Table 102: Use of Hubs and Switches

Table 103: Electric Requirements to RS-422 Cables

109

112

100

101

102

103

96

97

98

99

92

93

94

95

89

90

90

91

86

87

87

88

81

82

83

85

79

80

80

81

77

78

78

79

75

76

76

77

69

70

71

72

73

74

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Appendix

Table 104: RS-422 Conductor Length and Transmission Rates

Table 105: Electric Requirements to RS-485 Cables

Table 106: RS-485 Cable Lengths

121/122

112

114

114

netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Appendix

14.3 Contacts

Headquarters

Germany

Hilscher Gesellschaft für

Systemautomation mbH

Rheinstrasse 15

65795 Hattersheim

Phone: +49 (0) 6190 9907-0

Fax: +49 (0) 6190 9907-50

E-Mail: [email protected]

Support

Phone: +49 (0) 6190 9907-99

E-Mail: [email protected]

Subsidiaries

China

Hilscher Systemautomation (Shanghai) Co. Ltd.

200010 Shanghai

Phone: +86 (0) 21-6355-5161

E-Mail: [email protected]

Support

Phone: +86 (0) 21-6355-5161

E-Mail: [email protected]

France

Hilscher France S.a.r.l.

69500 Bron

Phone: +33 (0) 4 72 37 98 40

E-Mail: [email protected]

Support

Phone: +33 (0) 4 72 37 98 40

E-Mail: [email protected]

India

Hilscher India Pvt. Ltd.

Pune, Delhi, Mumbai

Phone: +91 8888 750 777

E-Mail: [email protected]

Italy

Hilscher Italia S.r.l.

20090 Vimodrone (MI)

Phone: +39 02 25007068

E-Mail: [email protected]

Support

Phone: +39 02 25007068

E-Mail: [email protected]

Japan

Hilscher Japan KK

Tokyo, 160-0022

Phone: +81 (0) 3-5362-0521

E-Mail: [email protected]

Support

Phone: +81 (0) 3-5362-0521

E-Mail: [email protected]

Korea

Hilscher Korea Inc.

Seongnam, Gyeonggi, 463-400

Phone: +82 (0) 31-789-3715

E-Mail: [email protected]

Switzerland

Hilscher Swiss GmbH

4500 Solothurn

Phone: +41 (0) 32 623 6633

E-Mail: [email protected]

Support

Phone: +49 (0) 6190 9907-99

E-Mail: [email protected]

USA

Hilscher North America, Inc.

Lisle, IL 60532

Phone: +1 630-505-5301

E-Mail: [email protected]

Support

Phone: +1 630-505-5301

E-Mail: [email protected]

122/122 netBRICK NB 100 | Gateway Devices

DOC091111UM13EN | Revision 13 | English | 2015-01 | Released | Public © Hilscher, 2009-2015

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents