hilscher NIOT-E-TIB100-GB-RE, NIOT-E-TPI51-EN-RE User Manual

User manual

netIOT Edge Gateway

NIOT-E-TIB100-GB-RE (Remote)

V1.1.2

Hilscher Gesellschaft für Systemautomation mbH

www.hilscher.com

Table of contents 2/263

Table of contents

1 Introduction .............................................................................................................................. 6

1.1 About the user manual .....................................................................................................6

1.2 List of revisions ................................................................................................................6

2 Brief description ...................................................................................................................... 7

3 Device drawings....................................................................................................................... 8

3.1 Positions of the interfaces ................................................................................................8

3.2 Dimensions ....................................................................................................................10

4 Connectors and mounting .................................................................................................... 11

4.1 Mounting ........................................................................................................................11

4.2 LED sticker.....................................................................................................................11

4.3 Power supply..................................................................................................................11

4.4 LAN connectors..............................................................................................................12

4.5 Real-Time Ethernet connectors .....................................................................................12

4.6 USB connectors .............................................................................................................12

4.7 Serial Interface ...............................................................................................................13

4.7.1 RS-232............................................................................................................13

4.7.2 RS-485............................................................................................................13

4.8 Wi-Fi...............................................................................................................................14

5 LEDs........................................................................................................................................15

5.1 Positions of the LEDs on the gateway ...........................................................................15

5.2 Gateway status LEDs.....................................................................................................16

5.3 LEDs of the LAN interface..............................................................................................16

5.4 LEDs of the PROFINET IO Device interface..................................................................17

5.5 LEDs of the EtherNet/IP Adapter interface ....................................................................18

6 Commissioning the Edge Gateway ...................................................................................... 20

6.1 Establishing the IP address communication ..................................................................20

6.2 Using the web browser to establish a connection with the Edge Gateway ....................22

6.2.1 Using the host name ....................................................................................... 22

6.2.2 Access to the Edge Gateway in the Windows network environment .............. 23

6.2.3 Using the IP address....................................................................................... 23

7 Edge Gateway Manager......................................................................................................... 24

7.1 Calling the Edge Gateway Manager ..............................................................................24

7.2 Edge Gateway Manager web page................................................................................25

8 Control Panel.......................................................................................................................... 27

8.1 Opening the control panel ..............................................................................................27

8.1.1 First login ........................................................................................................ 28

8.1.2 Secure connection .......................................................................................... 29

8.2 Overview and main menu ..............................................................................................33

8.3 System information and system time ............................................................................. 35

8.3.1 Displaying system information ........................................................................ 35

Table of contents 3/263

8.3.2 License Manager ............................................................................................ 36

8.3.3 Displaying the system log files........................................................................ 40

8.3.4 Setting the system time................................................................................... 44

8.3.5 Backup and restore......................................................................................... 47

8.3.6 Rebooting the system ..................................................................................... 54

8.3.7 System shutdown............................................................................................ 55

8.4 Packet management ......................................................................................................56

8.4.1 Managing packets........................................................................................... 56

8.5 Network ..........................................................................................................................57

8.5.1 Configuring Ethernet communication (LAN) ................................................... 57

8.5.2 Configuring wireless communication (WiFi).................................................... 60

8.5.3 Field ................................................................................................................ 66

8.5.4 Hostname........................................................................................................ 67

8.6 Services .........................................................................................................................68

8.6.1 Starting, stopping and configuring services .................................................... 68

8.7 User management..........................................................................................................72

8.7.1 Managing user roles ....................................................................................... 72

8.7.2 Managing user accounts................................................................................. 74

8.8 Security ..........................................................................................................................75

8.8.1 Public Key Infrastructure................................................................................. 75

8.9 Help................................................................................................................................78

8.10 Session ..........................................................................................................................78

8.10.1 User profile...................................................................................................... 78

8.10.2 Logout ............................................................................................................. 79

9 Node-RED - The wiring editor ............................................................................................... 80

9.1 Modelling IoT flows with nodes ......................................................................................81

9.2 Opening Node-RED .......................................................................................................82

9.3 Graphical user interface .................................................................................................84

9.4 Working with Node-RED ................................................................................................ 86

9.4.1 Using Git hub repository to store flows (projects) ........................................... 88

9.4.2 Menu Deploy................................................................................................... 89

9.4.3 Dashboard ...................................................................................................... 91

9.5 List of nodes.................................................................................................................101

9.6 MQTT input node .........................................................................................................104

9.7 MQTT output node .......................................................................................................109

9.8 OPC UA input node......................................................................................................111

9.9 OPC UA output node ...................................................................................................117

10 Examples for Node-RED...................................................................................................... 119

10.1 Example 1: Inject and debug node...............................................................................119

10.2 Example 2: MQTT input node ......................................................................................121

10.3 Example 3: MQTT output node ....................................................................................125

10.4 Example 4: OPC UA input node...................................................................................129

10.5 Example 5: OPC UA output node ................................................................................135

10.6 Example 6: Fieldbus input node...................................................................................142

10.7 Example 7: Fieldbus output node.................................................................................150

11 Configuring and using the fieldbus node.......................................................................... 158

Table of contents 4/263

11.1 Overview ......................................................................................................................158

11.2 Configuring the fieldbus and defining the signals.........................................................160

11.2.1 Creating a new fieldbus configuration........................................................... 160

11.2.2 Changing the existing fieldbus configuration ................................................ 167

11.2.3 Loading firmware and configuration.............................................................. 173

12 Configuring PROFINET and defining signals.................................................................... 175

12.1 User interface...............................................................................................................175

12.2 Menu commands..........................................................................................................175

12.2.1 Project - Save ............................................................................................... 176

12.2.2 GSDML Download ........................................................................................ 176

12.2.3 Printing the configuration .............................................................................. 176

12.2.4 Help - Contents ............................................................................................. 177

12.2.5 Help - Information ......................................................................................... 177

12.3 Configuration tree.........................................................................................................178

12.3.1 PROFINET configuration .............................................................................. 178

12.3.2 IO and signal configuration ........................................................................... 179

12.3.3 Signal definitions overview............................................................................ 188

12.3.4 Download of the GSDML file......................................................................... 189

12.3.5 Help............................................................................................................... 189

13 Configuring EtherNet/IP and defining signals .................................................................. 190

13.1 User interface...............................................................................................................190

13.2 Menu commands..........................................................................................................190

13.2.1 Project - Save ............................................................................................... 191

13.2.2 EDS Download.............................................................................................. 191

13.2.3 Printing the configuration .............................................................................. 192

13.2.4 Help - Contents ............................................................................................. 192

13.2.5 Help - Information ......................................................................................... 192

13.3 Configuration tree.........................................................................................................193

13.3.1 EtherNet/IP configuration.............................................................................. 193

13.3.2 IO and signal configuration ........................................................................... 194

13.3.3 Signal definitions overview............................................................................ 203

13.3.4 Download of the EDS file .............................................................................. 204

13.3.5 Help............................................................................................................... 204

14 Edge Server .......................................................................................................................... 205

14.1 Function principle .........................................................................................................205

14.1.1 Communication with IT-network and mobile devices.................................... 205

14.1.2 Communication with the OT-network............................................................ 207

14.1.3 Access rights to the REST API ..................................................................... 207

14.1.4 Functions of the Edge Server ....................................................................... 208

14.1.5 Internal structure of the Edge Server ............................................................ 209

14.2 Edge Server Control Center.........................................................................................210

14.2.1 Starting the Edge Server Control Center ...................................................... 210

14.2.2 Functions ...................................................................................................... 210

14.2.3 Service list..................................................................................................... 211

14.3 Configuration of the Edge Server.................................................................................213

14.3.1 The configuration of IP address area............................................................ 213

14.3.2 Selecting the protocols to scan for field devices ........................................... 216

15 Isolated application execution with Docker ...................................................................... 217

15.1 Docker, image, and container ......................................................................................217

Table of contents 5/263

15.2 Working with Docker via the web GUI..........................................................................220

15.2.1 The portainer.io interface .............................................................................. 220

15.2.2 Example: Executing the web server NGINX as a container.......................... 222

16 Public Key Infrastructure .................................................................................................... 224

16.1 Asymmetric encryption.................................................................................................224

16.2 Certificates and keys....................................................................................................226

16.2.1 Structure of a certificate according to X.509 ................................................. 226

16.2.2 Hierarchy of trust........................................................................................... 227

16.2.3 File formats for certificate and key files......................................................... 228

16.3 Use cases ....................................................................................................................228

16.3.1 Use case 1: Verification of the authenticity of the communication partner

(Server) ......................................................................................................... 228

16.3.2 Use case 2: Server certificates for Edge Gateway services ......................... 230

16.3.3 Use case 3: Client certificates for specific servers........................................ 232

16.4 Working with root certificates ....................................................................................... 234

16.4.1 Display the list of trustworthy root certificates............................................... 234

16.4.2 Upload a trustworthy certificate into the Edge Gateway ............................... 234

16.4.3 Download of certificates from the Edge Gateway into a file.......................... 235

16.4.4 Removing root certificates/CAs that are no longer considered as trustworthy ....

235

16.4.5 Adding a new trustworthy certificate to the trusted certification authority store of

the Edge Gateway ........................................................................................ 235

16.5 Working with server certificates for inbound connections ............................................ 236

16.5.1 Working with certificates for HTTP and OPC UA Server .............................. 236

16.5.2 Working with key files for HTTP and OPC UA Server .................................. 239

16.6 Working with client authentication certificates for outbound connections .................... 241

16.6.1 Working with certificates for client authentication ......................................... 241

16.6.2 Working with key files for client authentication ............................................. 244

17 Technical data ...................................................................................................................... 248

17.1 Technical Data NIOT-E-TIB100-GB-RE.......................................................................248

17.2 Technical data PROFINET IO Device..........................................................................250

17.3 Technical data EtherNet/IP Adapter.............................................................................251

18 Decommissioning, dismounting and disposal ................................................................. 252

18.1 Putting the device out of operation...............................................................................252

18.2 Removing device from top hat rail................................................................................252

18.3 Disposal of waste electronic equipment.......................................................................252

19 Appendix............................................................................................................................... 253

19.1 Legal notes...................................................................................................................253

List of figures ....................................................................................................................... 257

List of tables......................................................................................................................... 261

Contacts................................................................................................................................ 263

Introduction 6/263

1 Introduction

1.1 About the user manual

This user manual describes the installation, configuration and functionality of the device NIOT-E-TIB100-GB-RE .

1.2 List of revisions

Revision Date Author Change

1 2018-03-13 HHe, RGö All sections created.

2 2018-05-24 HHe

Section Node-RED service [}page68]: All flows are deleted.

Section Using Git hub repository to store flows (projects) [}page88] added.

Section Isolated application execution with Docker [}page217] added.

3 2018-06-11 HHe, RGö

Section OPC UA Server for Edge [}page69] added.

4 2018-08-13 RGö, HHe

Section Displaying the system log files [}page40] added. Section Security [}page75] added. Section Public Key Infrastructure [}page224] added.

Table1: List of revisions

Brief description 7/263

2 Brief description

Hilscher's netIOT Edge Gateway NIOT-E-TIB100-GB-RE securely connects Real-Time Ethernet automation networks with a „Cloud“ or any IoT-directed application. As a field device, it is performing a cyclic I/O data exchange with the PLC and communicates with further IoT-capable field devices within the automation network. These key field data exchanged in real-time form the basis for intelligent higher-level IoT applications for cyber-physical processes and M2M solutions.

The gateway is designed for continuous operation in environments with permanent intranet or Internet connection. Security mechanisms such as the physical separation of automation and IT network, a secure operating system, the execution of signed firmware and packets, as well as encryption techniques of the latest standards secure the data integrity and offer protection against data theft.

The gateway base function forms the web-based Thing Wiring editor NodeRED, which serves to model the flows in the devices. Data apps and data profiles are created within minutes with predefined function blocks of the editor. OPC UA and MQTT functions address objects in IoT-capable field devices or in the cloud via standardized IoT protocols.

The Hilscher netIOT Service offers additional software packets to extend the Edge Gateway base functions by further applications or accesses to specific clouds.

Figure1: Edge Gateway communication structure

Device drawings 8/263

3 Device drawings

3.1 Positions of the interfaces

Fieldbus

SYS

APL SEC POW

GPO1 WWAN WLAN BAT

COM

8 7

Figure2: Positions of the interfaces of NIOT-E-TIB100-GB-RE

Device drawings 9/263

Pos. Interface For details see

(1) Gateway state LEDs (8 x) Gateway status LEDs

(2) Antenna (1 x Wi-Fi), optional: Available at device variant

NIOT-E-TIB100-GB-RE/WF only.

Wi-Fi [}page14]

(3) LED communication state of Real-Time Ethernet.

Name und function depends on used RTE protocol: PROFINET IO Device = SF (System failure) EtherNet/IP Adapter = MS (module status)

LEDs of the PROFINET IO Device interface [}page17]

LEDs of the EtherNet/IP Adapter interface [}page18]

(4) Real-Time Ethernet connector (RJ45 jacket) channel 0

Real-Time Ethernet connectors [}page12]

(5) Real-Time Ethernet connector (RJ45 jacket) channel 1

(6) LED communication state of Real-Time Ethernet.

Name und function depends on used RTE protocol: PROFINET IO Device = BF (Bus failure) EtherNet/IP Adapter = NS (network status)

LEDs of the PROFINET IO Device interface [}page17]

LEDs of the EtherNet/IP Adapter interface [}page18]

(7) USB connector (1x USB 3.0)

USB connectors [}page12]

(8) USB connector (1x USB 2.0)

USB connectors [}page12]

(9) LAN connector (RJ45 jacket) port 2 / Eth1

LAN connectors [}page12]

(10) LAN connector (RJ45 jacket) port 1 / Eth0

LAN connectors [}page12]

(11) Serial interface connector COM (RS-232/485, can be

configured)

Serial Interface [}page13]

Table2: Positions of the interfaces of NIOT-E-TIB100-GB-RE

Device drawings 10/263

3.2 Dimensions

Fieldbus

SYS APL SEC POW

GPO1 WWAN WLAN BAT

COM

120 mm

63 mm

106 mm 106 mm

106 mm

100 mm

Figure3: Dimensions

Connectors and mounting 11/263

4 Connectors and mounting

4.1 Mounting

Mount the Edge Gateway on a DIN rail onto the wall of the cabinet.

4.2 LED sticker

Each fieldbus system uses its own names for the LED displays. Therefore, an LED sticker with the names of the respective fieldbus system is included within the delivery of the Edge Gateway. Stick the sticker of the fieldbus system to be used to the I/O shield of the fieldbus interface of the Edge Gateway.

Figure4: LED label

4.3 Power supply

DC 24V Pin Signal Description

+ +24 V DC +24 V DC

- GND Ground (Reference potential)

FE Functional earth

Table3: Power supply connector

Connectors and mounting 12/263

4.4 LAN connectors

The Edge Gateway has two LAN connectors for connecting it to the cloud network, positions (10) and (9) (see section Positions of the interfaces [}page8]).

The MAC addresses of the LAN interfaces are printed on the device label.

Section Configuring Ethernet communication (LAN) [}page57] describes, how you can set the IP address parameters of the LAN interfaces.

4.5 Real-Time Ethernet connectors

The Edge Gateway has 2 RJ45-connectors to connect the fieldbus to a Real-Time Ethernet network (OT network), positions (4) and (5) (see section Positions of the interfaces [}page8]).

For data exchange at the fieldbus, use the fieldbus input and output in node Node-RED. Sections Example 6: Fieldbus input node [}page142] and Example 7: Fieldbus output node [}page150] describe how to access the cyclic I/O data of the fieldbus in Node-RED.

4.6 USB connectors

The Edge Gateway has 2 USB connectors (1), positions (7) and (8) (see section Positions of the interfaces [}page8]).

You do not need the USB connectors for operation of the Edge Gateway. You need the USB connector if you connect a keyboard in order to change settings in the BIOS or if you do a firmware recovery with a USB stick.

Connectors and mounting 13/263

4.7 Serial Interface

The Edge Gateway has one configurable serial interface (position (11)). You can use the serial interface as RS-232 or RS-485 interface.

Prerequisites

You have to set the interface type in the BIOS. For this, you need a keyboard with USB connector, and a serial cable.

BIOS settings

In the BIOS, select Advanced > IT8786 Super IO Configuration > Serial Port 1 Configuration for COM1 or Serial Port 2 Configuration for COM2.

Serial Port Configuration Parameter

Serial Port Enabled

Disabled

Device Settings Display only

Serial Port (COM): IO=248h; IRQ=5

Onboard Serial Port Mode RS232

RS485 (do not use this setting) RS485 Auto (use this setting for RS-485 only, because RTS control is active)

Table4: Parameters of the serial interface

4.7.1 RS-232

RS-232 Pin Signal Description

1 DCD Data Carrier Detect

2 RXD Receive signal

3 TXD Send signal

4 DTR Data Terminal Ready

5 ISO_GND Ground (reference potential)

6 DSR Data Set Ready

7 RTS Request to Send

8 CTS Clear to Send

9 RI Ring Indicator

Table5: RS-232 D-Sub

4.7.2 RS-485

RS-485 Pin Signal Description

1 Rx/Tx‑ Send/receive signal negative

2 Rx/Tx+ Send/receive signal positive

3 n.c. -

4 n.c. -

5 ISO_GND Ground (reference potential)

6 n.c. -

7 n.c. -

8 n.c. -

9 n.c. -

Table6: RS-485 D-Sub

Connectors and mounting 14/263

4.8 Wi-Fi

You can use the Edge Gateway for wireless network communication. The Edge Gateway supports 2 Wi-Fi operating modes: Access Point and Client. Operating mode Access Point allows the Edge Gateway to connect to other Wi-Fi devices in order to configure the Edge Gateway from a mobile device for example. Operating mode Client allows the Edge Gateway to be connected to any Wi-Fi Access Point.

Section Configuring wireless communication (WiFi) [}page60] describes how you activate the antennas and how to set the Wi-Fi operating mode.

LEDs 15/263

5 LEDs

5.1 Positions of the LEDs on the gateway

Fieldbus

SYS

APL SEC POW

GPO1 WWAN WLAN BAT

COM

Figure5: NIOT-E-TIB100-GB-RE LED positions

LEDs 16/263

5.2 Gateway status LEDs

LEDs indicating system status, application status, voltage supply, battery state, as well as activity of the serial interface COM, and GPIOs. The position of the LEDs is indicated by position (1), see in section Positions of the LEDs on the gateway [}page15].

LED Color Meaning

SYS

yellow/

green

System status

APL

yellow/

green

Application status

SEC

blau

Security status

POW

yellow

Power supply OK

GPO1

yellow/

green

GPIO1 (programmable, currently not used)

WWAN

yellow

WWAN status

WLAN

yellow

Wireless LAN status

BAT

yellow

Battery state

Table7: Description of gateway status LEDs

5.3 LEDs of the LAN interface

LEDs indicating state of the LAN communication. For the positions of the LAN LEDs, see section Positions of the LEDs on the gateway [}page15].

LED Color State Meaning

LINK

See positions (2) and

(4)

Duo LED green/orange

(green)

On 1 GBit network connection

(orange)

On 100 MBit network connection

(off)

Off 10 MBit or no network connection

RX/TX

See positions (3) and

(5)

LED yellow

(yellow)

On The device does not send/receive frames.

(yellow)

Flickering (load dependent)

The device sends/receives frames.

(off)

Off The device does not send/receive Ethernet frames.

Table8: LEDs LAN interface

LEDs 17/263

5.4 LEDs of the PROFINET IO Device interface

LED Color State Meaning

SF (System Failure)

Position in the device drawing: (2)

Duo LED red/green

(off)

(Off) No error

(red)

Flashing (1 Hz, 3 s)

DCP signal service is initiated via the bus.

(red)

On Watchdog timeout; channel, generic or extended diagnosis

present; system error

BF (Bus Failure)

Position in the device drawing: (7)

Duo LED red/green

(off)

Off No error

(red)

Flashing (2 Hz)

No data exchange

(red)

On No configuration;

or low speed physical link; or no physical link

LINK

CH0 (3) , CH1 (5)

LED green

(green)

On The device is linked to the Ethernet.

(off)

Off The device has no link to the Ethernet.

RX/TX

CH0 (4) , CH1 (6)

LED yellow

(yellow)

Flickering (load dependent)

The device sends/receives Ethernet frames.

(off)

Off The device does not send/receive Ethernet frames.

Table9: LED states for the PROFINET IO-Device protocol

LED state Definition

Flashing (1 Hz, 3 s)

The indicator turns on and off for 3 seconds with a frequency of 1 Hz: “on” for 500 ms, followed by “off” for 500 ms.

Flashing (2 Hz)

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

Flickering (load dependent)

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

Table10: LED state definitions for the PROFINET IO-Device protocol

LEDs 18/263

5.5 LEDs of the EtherNet/IP Adapter interface

LED Color State Meaning

(module status)

Position in the device drawing: (2)

Duo LED red/green

(green)

On Device operational: The device is operating correctly.

(green)

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

(green/red/ green)

Flashing green/red/ green

Self-test: The device is performing its power-up testing. The module status indicator test sequence occurs before the network status indicator test sequence, according to the following sequence:

· Network status LED off.

· Module status LED turns green for approximately 250 ms,

turns red for approximately 250 ms, and again turns green (and holds that state until the power-up test has completed).

· Network status LED turns green for approximately 250 ms, turns red for approximately 250 ms, and then turns off (and holds that state until the power-up test has completed).

(red)

Flashing (1 Hz) Major recoverable fault: The device has detected a major

recoverable fault. E.g., an incorrect or inconsistent configuration can be considered a major recoverable fault.

(red)

On Major unrecoverable fault: The device has detected a major

unrecoverable fault.

(off)

Off No power: The device is powered off.

NS (Network status)

Position in the device drawing: (7)

Duo LED red/green

(green)

On Connected: An IP address is configured, at least one CIP

connection (any transport class) is established, and an Exclusive Owner connection has not timed out.

(green)

Flashing (1 Hz) No connections: An IP address is configured, but no CIP

connections are established, and an Exclusive Owner connection has not timed out.

(green/red/off)

Flashing green/red/off

Self-test: The device is performing its power-up testing. Refer to description for module status LED self-test.

(red)

Flashing (1 Hz) Connection timeout: An IP address is configured, and an

Exclusive Owner connection for which this device is the target has timed out.

The network status indicator returns to steady green only when all timed out Exclusive Owner connections are reestablished.

(red)

On Duplicate IP: The device has detected that its IP address is

already in use.

(off)

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

IP address (or is powered off).

LINK

CH0 (3), CH1 (5)

LED green

(green)

On The device is linked to the Ethernet.

(off)

Off The device has no link to the Ethernet.

ACT

CH0 (4), CH1 (6)

LED yellow

(yellow)

Flickering (load dependent)

The device sends/receives Ethernet frames.

(off)

Off The device does not send/receive Ethernet frames.

Table11: LED states for the EtherNet/IP Adapter protocol

LEDs 19/263

LED state Definition

Flashing (1 Hz)

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

Flashing green/red/ green

The MS LED indicator turns on green on for 250 ms, then red on for 250 ms, then green on (until the test is completed).

Flashing green/red/off

The NS LED indicator turns on green on for 250 ms, then red on for 250 ms, then off (until the test is completed).

Flickering (load dependant)

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

Table12: LED state definitions for the EtherNet/IP Adapter protocol

Commissioning the Edge Gateway 20/263

6 Commissioning the Edge Gateway

6.1 Establishing the IP address communication

An IP address is required to address the Edge Gateway in the LAN network.

The following figure shows the factory setting of the LAN interfaces and the assignment of the connections.

Figure6: Default settings of the Ethernet network connectors

You have two possibilities of establishing a connection with the Edge Gateway (factory setting):

NetNetwork connection - alternative 1: DHCP server available

If a DHCP server is available in the network: Ø Use an Ethernet cable to connect the LAN connection port 1 (eth0)

(see position (7) in section Positions of the interfaces [}page8]) with a network in which a DHCP server is available.

ð The Edge Gateway obtains an IP address from the DHCP server.

Access to the Edge Gateway is possible now.

Note:

The Edge Gateway sends a request to a DHCP server once after switching on the device or after each connection of the Ethernet cable, i.e. when the Edge Gateway detects a link signal. If you want to activate a request of the Edge Gateway to the DHCP server manually, pull off the Ethernet cable from the Edge Gateway and reconnect it to the Edge Gateway.

Read section Using the web browser to establish a connection with the Edge Gateway [}page22] to find out how to access the Edge Gateway.

Commissioning the Edge Gateway 21/263

Network connection - alternative 2: Direct connection and adaptation of the IP address of the PC or notebook used for commissioning

The IP address of the Edge Gateway (factory setting) is 192.168.253.1 and the subnet mask is 255.255.255.0 at LAN connection port 2 (eth1, see position (5) in section Positions of the interfaces [}page8]).

If no DHCP server is available, you can set an IP address on your PC or notebook, which suits the same subnet:

Ø Use an Ethernet cable to connect the LAN connection port 2 (eth1)

directly with your PC or notebook.

Ø Open the Control panel. Ø Click on Network and Sharing Center. Ø Click on Change adapter settings. Ø Double click the name of the network connection: Local Area

Connection. (The name of the network connection may be different on your PC.)

Ø Click on Properties. Ø Double click on Internet Protocol Version 4 (TCP/IPv4). Ø Set the following IP address, e.g. 192.168.253.2 and subnet mask

255.255.255.0.

Ø Click on Ok and then click on Close. ð Now you can access the Edge Gateway from your PC or notebook.

Read section Using the IP address [}page23] to find out how to access the Edge Gateway.

Commissioning the Edge Gateway 22/263

6.2 Using the web browser to establish a connection with the Edge Gateway

You have three possibilities to access the Edge Gateway:

1. by means of the host name (see section Using the host name [}page22])

2. by access via the Windows network (see section Access to the Edge Gateway in the Windows network environment [}page23]),

3. by using the IP address (see section Using the IP address [}page23]).

6.2.1 Using the host name

The Edge Gateway has a host name you can use to access the device.

Where do you find the host name on the device?

The device is delivered (factory setting) with a label printed at its bottom. In the figure below the host name has a red frame.

Figure7: Device label: Hostname

Establishing a connection with the host name

Ø Enter the following address in the address line of your browser:

https://<hostname> Example: For the device with the host name NTB827EB1D9D94 enter https:// NTB827EB1D9D94

ð The Edge Gateway Manager opens.

You can now use the Edge Gateway manager to configure the device. For this purpose, read section Edge Gateway Manager web page [}page25].

Commissioning the Edge Gateway 23/263

6.2.2 Access to the Edge Gateway in the Windows network environment

To be located easily in the network, the Edge Gateway uses the UPnP technology (Universal Plug and Play). This technology will display the Edge Gateway in the Windows network environment.

Ø To display all devices in the network, click on Network in the Windows

Explorer.

Ê You will find the Edge Gateway under Other Devices:

Figure8: netIOT Edge Gateway in the Windows network

Ø Open the context menu of this entry and select Properties. Ê The menu provides information on the Edge Gateway, e.g. serial

number, MAC address, host name or die IP address.

Ø Click on the link under Device web page. ð The Edge Gateway manager opens. Ø To open the Edge Gateway manager, you can also double-click on the

device icon.

ð The Edge Gateway manager opens.

You can now use the Edge Gateway manager to configure the device. For this purpose, read section Edge Gateway Manager web page [}page25].

6.2.3 Using the IP address

If you know the IP address of one of the LAN connections of the Edge Gateway and if you are physically connected to your operating device, you can use your web browser to establish a connection with the Edge Gateway by entering this IP address directly. Should your operating device be configured with an IP address only, but without a subnet mask, your operating device has to be located in the same subnet as the Edge Gateway to be able establish a connection.

Ø Enter the IP address in the address line of the web browser as follows:

https://<IP address> Example: https://10.11.5.61

ð The Edge Gateway manager opens.

You can now use the Edge Gateway manager to configure the device. For this purpose, read section Edge Gateway Manager web page [}page25].

Edge Gateway Manager 24/263

7 Edge Gateway Manager

7.1 Calling the Edge Gateway Manager

The Edge Gateway manager is a web page with tiles that allow rapid access to the applications integrated in the device or to external web pages.

The Edge Gateway uses the secured HTTPS protocol to access web pages stored in the Edge Gateway.

Ø To open the Edge Gateway manager, enter the following information in

the address line of your browser: https://<Host name of the Edge Gateway> or

https://<IP address of the Edge Gateway>

ð Your browser displays the Edge Gateway manager.

Figure9: Edge Gateway Manager

Note:

Remember that the secured HTTPS protocol is used here, not the widely spread HTTP protocol.

Edge Gateway Manager 25/263

7.2 Edge Gateway Manager web page

The Edge Gateway Manager displays tiles that allow rapid access to the applications integrated in the device or external web pages.

Icon Function

Opens the control panel of the Edge Gateway.

The control panel configures the Edge Gateway and displays information on the system. Section Control Panel [}page27] describes the possibilities of configuration as well as the displayed information on the system.

Opens the wiring editor Node-RED.

Section Node-RED - The wiring editor [}page80]describes how to create applications for the Edge Gateway.

Opens the Node-RED Dashboard (graphical user interface).

Opens the Edge Server Control Center.

See section Edge Server [}page205].

Opens the Docker management.

See section Isolated application execution with Docker [}page217].

Opens the Edge Gateway documentation stored in the device.

Opens the homepage of the Device Information Portal in the Internet.

Requires a connection to the Internet.

Edge Gateway Manager 26/263

Icon Function

Opens the homepage of the netIOT platform in the Internet.

Requires a connection to the Internet.

Opens the Hilscher homepage in the Internet.

Requires a connection to the Internet.

Opens legal information concerning the Edge Gateway.

Requires a connection to the Internet.

Table13: Starting applications with the Edge Gateway Manager

Control Panel 27/263

8 Control Panel

8.1 Opening the control panel

With the control panel you can configure the Edge Gateway and display device-specific information.

Ø Click the tile Control Panel.

Ø The login screen for the Control Panel is displayed.

Ø Enter your user name and your password. Ø Click at Login. ð The Control Panel will be displayed.

Control Panel 28/263

8.1.1 First login

Setting the administrator password when the control panel is called for the first time

The dialog box Set Administrator Password is displayed when the control panel is called for the first time.

Figure10: Edge Gateway Manager - Setting the administrator password

To set a new administrator password, proceed as follows: Ø Enter the preset password under Current Password. With the first

commissioning, the password is:

admin

Ø Enter the new administrator password. It must have at least 7

characters. For reasons of safety, Hilscher recommends using significantly more characters. A strong password consists of upper and lower case letters, digits and special characters. A quality indicator in the dialog box evaluates the password.

Weak password Mediocre password Strong password

Control Panel 29/263

Ø Click Change Password only after the entered password has been

evaluated as strong.

ð The administrator password for the user account Admin has thus been

changed.

ð As an administrator you can now use the control panel, create further

users in the user management, and assign access rights.

8.1.2 Secure connection

Edge Gateways support web connections secured by SSH/TSL via https:// accesses only.

By definition, a secure connection can provide an efficient protection only if a certificate proves that the server is secure. Only then can running transactions of the initiating browser and the server be considered as protected against interception and data theft.

This is why the browser at first inquires a certificate of verification from the server (Gateway). This certificate proves that the issuer has verified the security of the server. Each browser provides a preinstalled list of known authorized issuers of certificates.

Each time the certificate of the server arrives at the browser, the browser compares the issuer of the certificate with the issuers stored in the list of known authorized issuers of certificates.

If the issuer of the certificate is not listed, the browser will signal a certificate error and request the user's confirmation to continue because it assumes that the connection is insecure.

As standard, Edge Gateways contain a certificate issued by Hilscher that is not on the list of the known authorized issuers of certificates. Due to that, the browser signals an insecure connection and requests the confirmation to continue. When this confirmation has been given once, any future connections will be established without further requests.

Note:

In the control panel you can replace this certificate any time by the certificate of a known authorized issuer of certificates, see section Uploading and installing own security certificates).

Control Panel 30/263

8.1.2.1 Connection without certificate with Microsoft Internet Explorer

Microsoft Internet Explorer: Edge Gateway Manager will not be displayed

If you use the Microsoft Internet Explorer and the following page is displayed, click the option Continue to this web site (not recommended).

Figure11: Security error message of the Internet Explorer

8.1.2.2 Connection without certificate with Firefox

If you use Firefox as a browser, a self-signed certificate will cause the following error message:

Figure12: Security error message of the Firefox browser (1)

To avoid this message caused by a self-signed certificate, proceed as follows:

Ø To display the complete message, click Advanced.

Figure13: Security error message of the Firefox browser (2)

Ø To define an exceptional rule that enables the display of the user

interface without repeated error messages, click Add Exception.

+ 233 hidden pages

hilscher NIOT-E-TIB100-GB-RE, NIOT-E-TPI51-EN-RE User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual