Um en Cloud Iot Gateway 108450 en 01

Startup and operation of the IoT gateway
CLOUD IOT GATEWAY

User manual
User manual
Startup and operation of the IoT gateway CLOUD IOT GATEWAY
UM EN CLOUD IOT GATEWAY, Revision 01 2018-06-20
This user manual is valid for:
Designation Version Order No.

CLOUD IOT GATEWAY 00 1031235
108450_en_01
PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany

phoenixcontact.com
Table of contents
Table of contents
1 For your safety ...........................................................................................................................6
1.1 Identification of warning notes ............................................................................... 6
1.2 Qualification of users ............................................................................................. 6
1.3 Field of application of the product.......................................................................... 7
1.3.1 Intended use .......................................................................................... 7
1.3.2 Foreseeable misuse ............................................................................... 7
1.3.3 Modifications .......................................................................................... 7
1.4 Safety notes .......................................................................................................... 7
2 From transport to unpacking ....................................................................................................10

2.1 Transport ............................................................................................................. 10
2.2 Storage................................................................................................................ 10
2.3 Checking the delivery .......................................................................................... 11
2.4 Unpacking ........................................................................................................... 11
3 Description of the IoT gateway .................................................................................................12

3.1 General description ............................................................................................. 12
3.2 Licensing information on open source software................................................... 12
3.3 Requesting source code...................................................................................... 12
3.4 Components of the IoT gateway .......................................................................... 13
3.4.1 Connection and operating elements .................................................... 13
3.4.2 Printing ................................................................................................. 14
3.5 Diagnostic and status indicators .......................................................................... 15
3.6 Reset button ........................................................................................................ 17
3.7 Parameterization memory.................................................................................... 18
3.8 Internal basic circuit diagram ............................................................................... 18
3.9 Supply plug.......................................................................................................... 19
3.10 Interfaces............................................................................................................. 20
3.10.1 Ethernet ............................................................................................... 20
3.10.2 Service interface (USB type C) ............................................................ 21
3.10.3 RS-485 interface .................................................................................. 22
3.10.4 CAN bus interface ................................................................................ 23
3.10.5 RS-232 interface .................................................................................. 24
4 Mounting hardware ..................................................................................................................25

4.1 Safety notes ........................................................................................................ 25
4.2 Mounting the IoT gateway ................................................................................... 27
4.3 Assembling the COMBICON connector .............................................................. 28
108450_en_01 PHOENIX CONTACT 3 / 108

CLOUD IOT GATEWAY
5 Connecting and wiring hardware ..............................................................................................29

5.1 Safety notes ........................................................................................................ 29
5.2 Supply voltage..................................................................................................... 30
5.2.1 Sizing of the power supply ................................................................... 30
5.2.2 Connecting the voltage supply ............................................................. 32
5.3 Connecting the Internet ....................................................................................... 33
5.4 Connecting the local Ethernet network ................................................................ 33
5.5 Connecting the RS-485, CAN bus and RS-232 participants ............................... 34
6 Web-based management (WBM) ............................................................................................36

6.1 Establishing a connection with the WBM ............................................................. 36
6.2 Login ................................................................................................................... 36
6.3 User preferences – “Users” menu........................................................................ 38
6.3.1 Showing help – “Help” menu ................................................................ 38
6.3.2 Editing access data – “Profile” menu .................................................... 39
6.4 Showing and filtering the event history –
“Journal” button ................................................................................................... 41
6.5 “Home” page ....................................................................................................... 44
6.5.1 Creating a connection .......................................................................... 46
6.5.2 Defining connection details .................................................................. 47
6.6 Advanced settings – “Settings” menu .................................................................. 59
6.6.1 System information – “Info” tab ............................................................ 59
6.6.2 Managing users – “Users” tab .............................................................. 60
6.6.3 Network settings – “Network” tab ......................................................... 64
6.6.4 Setting the realtime clock – “Time” tab ................................................. 71
6.6.5 Security settings – “Security” tab .......................................................... 72
6.6.6 Defining buffers – “Buffers” tab ............................................................ 78
6.6.7 Importing configuration file or exporting configuration –
“Import/Export” tab ............................................................................... 81
6.6.8 Updating the firmware – “Update” tab .................................................. 82
6.6.9 Deregistering the IoT gateway from the PROFICLOUD or
resetting it to factory settings – “Reset” tab .......................................... 83
6.6.10 Restarting the IoT gateway – “Restart” tab ........................................... 84
6.7 Logout ................................................................................................................. 84
7 Transmitting sensor and process data to the PROFICLOUD ...................................................85

7.1 Configuring the PROFICLOUD ............................................................................ 85
7.2 Displaying an overview of the metrics of the IoT gateway.................................... 87
7.3 Representing the metrics in Grafana graphically ................................................. 88
8 Removing hardware .................................................................................................................91

8.1 Safety notes ........................................................................................................ 91
4 / 108 PHOENIX CONTACT 108450_en_01

Table of contents
8.2 Removing cables................................................................................................. 91

8.3 Removing COMBICON connectors ..................................................................... 92
8.4 Remove the Ethernet connector .......................................................................... 92
8.5 Removing the IoT gateway .................................................................................. 92
9 After usage ..............................................................................................................................93

9.1 Maintenance and servicing.................................................................................. 93
9.2 Device replacement............................................................................................. 93
9.3 Device defect and repair...................................................................................... 93
9.4 Disposal .............................................................................................................. 94
9.5 Take-back ........................................................................................................... 94
10 Ordering data and technical data .............................................................................................95

10.1 Ordering data ...................................................................................................... 95
10.2 Technical data ..................................................................................................... 96
A Technical appendix...................................................................................................................99
A1 Troubleshooting and frequently asked questions (FAQs) .................................... 99
B Appendix for document lists....................................................................................................100

B1 List of figures ..................................................................................................... 100
B2 List of tables ...................................................................................................... 103
B3 Index.................................................................................................................. 104

CLOUD IOT GATEWAY
1 For your safety

Read this user manual carefully and keep it for future reference.
1.1 Identification of warning notes

This symbol indicates hazards that could lead to personal injury.
There are three signal words indicating the severity of a potential injury.
DANGER
Indicates a hazard with a high risk level. If this hazardous situation is not
avoided, it will result in death or serious injury.
WARNING
Indicates a hazard with a medium risk level. If this hazardous situation is not
avoided, it could result in death or serious injury.
CAUTION
Indicates a hazard with a low risk level. If this hazardous situation is not avoided,
it could result in minor or moderate injury.
This symbol together with the NOTE signal word warns the reader of actions
that might cause property damage or a malfunction.
Here you will find additional information or detailed sources of information.
1.2 Qualification of users

The use of products described in this user manual is oriented exclusively to:
– Electrically skilled persons or persons instructed by them. The users must be familiar
with the relevant safety concepts of automation technology as well as applicable
standards and other regulations.
– Qualified application programmers and software engineers. The users must be familiar
with the relevant safety concepts of automation technology as well as applicable
standards and other regulations.

For your safety
1.3 Field of application of the product
1.3.1 Intended use

The CLOUD IOT GATEWAY is an IoT gateway for connecting devices to the
PROFICLOUD. The device has an IP20 protection rating and is designed for use in closed
control cabinets or control boxes (terminal boxes) with IP54 protection or higher.
The device is designed for use in industrial environments.
1.3.2 Foreseeable misuse

To use the IoT gateway, an Internet connection is needed.
• Make sure that the IoT gateway has a connection to the Internet.
1.3.3 Modifications
Modifications to hardware and firmware of the device are not permitted.
Incorrect operation or modifications to the device can endanger your safety or damage the
device. Do not repair the device yourself. If the device is defective, please contact
Phoenix Contact.
1.4 Safety notes

Observe the country-specific installation, safety, and accident prevention regulations.
During startup and maintenance work, proceed in accordance with the five safety rules of
DIN EN 50110-1. In general, the rules should be observed in the specified order:
– Disconnect safely
– Ensure power cannot be switched on again
– Verify safe isolation from the supply
– Ground and short circuit
– Cover or safeguard adjacent live parts
Once the work is complete, perform the above steps again in reverse order.

CLOUD IOT GATEWAY
NOTE: Risk of unauthorized network access

Connecting devices to a network via Ethernet always entails the risk of unauthorized
access to the network.
Therefore, please check your application for an option for deactivating active
communication channels (for instance SNMP, FTP, BootP, DCP, HTTP, HTTPS, etc.) or
setting passwords, to prevent third parties from accessing the controller without
authorization and modifying the system.
Because of the controller's communication interfaces, we advise against using the
controller in safety-critical applications without additional security appliances.
Please take additional protective measures in accordance with the IT security
requirements and the standards applicable to your application (for instance virtual
networks (VPN) for remote maintenance access, firewalls, etc.) for protection against
unauthorized network access.
On first request, you shall release Phoenix Contact and the companies associated with
Phoenix Contact GmbH & Co. KG, Flachsmarktstraße 8, 32825 Blomberg in accordance
with §§ 15 ff. AktG or German Stock Corporation Act (hereinafter collectively referred to as
“Phoenix Contact”) from all third-party claims that are made due to improper use.
For the protection of networks for remote maintenance via VPN, Phoenix Contact offers
the mGuard product range as security appliances, which you can find described in the
latest Phoenix Contact catalog (phoenixcontact.net/products).
Additional measures for protection against unauthorized network access can be found in
the AH EN INDUSTRIAL SECURITY application note. The application note can be
downloaded at phoenixcontact.net/products.
NOTE: Electrostatic discharge!

The device contains components that can be damaged or destroyed by electrostatic
discharge. When handling the device, observe the necessary safety precautions against
electrostatic discharge (ESD) in accordance with EN 61340-5-1 and IEC 61340-5-1.
NOTE: Device damage due to polarity reversal

Polarity reversal puts a strain on the electronics and can damage the device.
• To protect the device, avoid polarity reversal of the 24 V supply.
NOTE: Electrical damage

Performing work on the IoT gateway during operation can damage the device electronics.
• Disconnect the power to the IoT gateway for all work on the device.
• Make sure that the supply voltage cannot be switched on again by unauthorized
persons.
NOTE: Device failure

The device is designed to be powered by an external 24 V DC voltage supply. The
permissible voltage range is from 18 V DC to 30 V DC (ripple included). If the voltage
exceeds or falls below the permitted voltage range, this may lead to device failure.
NOTE: Component breakage and/or short circuit

If you insert the device connectors into sockets for which they are not designated, this may
lead to components being broken and/or device short circuit.
• Insert all device connectors only in the relevant designated sockets.

For your safety

The device is designed for mounting on a horizontal DIN rail in a control cabinet. If you do
not mount the device on a horizontal DIN rail in a control cabinet, the device’s degree of
protection is not ensured. This can lead to device failure.
• Mount the device as described in Section 4.2 in order to ensure the device’s degree
of protection.
NOTE: Property damage due to impermissible load

The device has an IP20 rating (IEC 60529/EN 60529) and is thus intended for use in a
clean and dry environment. If you use device in an environment that is outside of the
specified limits, this may cause damage to the device.
• Do not subject the device to mechanical or thermal stress that exceeds the specified
thresholds.

The device is designed for a specific ambient temperature range (see Section 10.2,
“Technical data”). If you operate, store or transport the device in ambient temperatures
that are not within the specified range, this may lead to device failure.
The device is automatically grounded (FE) when it is snapped onto a grounded

DIN rail.
On the rear of the device, there are two FE springs that make contact with the DIN rail
when the device is placed on the DIN rail.
Please note:
The service interface is currently without function.
In future, the service interface (USB type C) is designated for firmware updates. The
service interface is not intended for connecting other peripheral devices.

CLOUD IOT GATEWAY
2 From transport to unpacking
2.1 Transport
The device is delivered in cardboard packaging.
• Only transport the device to its destination in its original packaging.
• On the packaging, please note the instructions regarding handling as well as moisture,
shock, tilt, and temperature indicators.
• Observe the humidity specifications and the temperature range specified for transport
(see Section 10.2, “Technical data”).
• Protect the surfaces as necessary to prevent damage.
• When transporting the equipment or storing it temporarily, make sure that the surfaces
are protected from the elements and any external influences, and that they are kept dry
and clean.
2.2 Storage
The storage location must meet the following requirements:
– Dry
– Protected from unauthorized access
– Protected from harmful environmental influences such as UV light
– Temperature range: -25°C ... +55°C
– Air pressure: 58 kPa ... 106 kPa (up to 4500 m above sea level)
– Permissible humidity: 5% ... 95% (according to DIN EN 61131-2)

From transport to unpacking
2.3 Checking the delivery

• Check the delivery for transport damage.
Damaged packaging is an indicator of potential damage to the device that may have
occurred during transportation. This could result in a malfunction.
• Submit claims for any transport damage immediately, and inform Phoenix Contact or
your supplier as well as the shipping company without delay.
• Enclose photos which clearly document the damage to the packaging/delivery together
with your claim.
• Immediately after delivery, refer to the delivery note to check if the content of the
packaging is complete.
• Keep the box and packaging material in case it is necessary to return the product.
• We strongly recommend using the original packaging to return the product.
• If the original packaging is no longer available, observe the following points:
– Observe the humidity specifications and the temperature range specified for
transport (see Section 10.2, “Technical data”).
– If necessary, use dehumidifying agents.
– Use appropriate ESD packaging to protect components that are sensitive to
electrostatic discharge.
– Make sure that the packaging you select is large enough and sufficiently thick.
– Only use plastic bubble wrap sheets as filler material.
– Attach warnings to the transport packaging so that they are clearly visible.
– Please be aware that the delivery note is to be placed inside the package in the
case of packages that are to remain within the same country. However, if the
package is being sent abroad, the delivery note must be placed inside a delivery
note pocket and attached to the outside so that it is clearly visible.
Scope of supply IoT gateway CLOUD IOT GATEWAY
2.4 Unpacking
The CLOUD IOT GATEWAY is delivered in packaging, together with a package insert that
provides installation instructions.
• Read the package insert attentively before unpacking the IoT gateway.

NOTE: Property damage due to noncompliance with ESD notes

If the ESD notes are not observed during unpacking and packaging, the device may be
damaged.
• Observe the ESD notes during unpacking and packaging.

CLOUD IOT GATEWAY
3 Description of the IoT gateway
3.1 General description

With the CLOUD IOT GATEWAY, you can connect new and existing systems to the
PROFICLOUD. The IoT gateway is equipped with various connection interfaces that can be
used for diverse communication protocols.
Sensor and process data of selected devices is sent to the CLOUD IOT GATEWAY, from
where it is transmitted to the PROFICLOUD as a metric. The transmitted sensor and
process data is collected, processed, and monitored in the PROFICLOUD.
You can use the Grafana open platform to graphically display the transferred sensor and
process data as metric.
3.2 Licensing information on open source software

The CLOUD IOT GATEWAY works with a Linux operating system.
License information for the individual Linux packages can be found in the web-based
management of the IoT gateway, see Section 6.6.1.
Notes on LGPL software All open-source software used in the product is subject to the respective license terms that
libraries are not affected by the end user license agreement (EULA) for the product. In particular, the
license holder can change the respective open-source software in accordance with the
applicable license terms. If the license holder wishes to change an LGPL software library
contained in this product, reverse engineering is permitted for debugging such
modifications.
Notes for OpenSSL This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit. (http://www.openssl.org/)
3.3 Requesting source code

The CLOUD IOT GATEWAY contains software components that have been licensed as
free software or open-source software under the GNU General Public License by the rights
holder.
You can request the source code of these software components in the form of a CD or DVD-
ROM for a processing fee of 50 euros within three years after delivery of the
CLOUD IOT GATEWAY.
Contact the After Sales Service of Phoenix Contact in writing about this at the address
PHOENIX CONTACT GmbH & Co. KG
After Sales Service
Flachsmarktstraße 8
32825 Blomberg
GERMANY
Subject: Source code CLOUD IOT GATEWAY

Description of the IoT gateway
3.4 Components of the IoT gateway
3.4.1 Connection and operating elements
1
2
3
R
PW32
2
RS N
CA
4
B
US
R
PW
L
ON
R
ER
T
AC
SF
Re
se
t
5
et
rn
Intecal
H1 Lo
ET H2 5
ET S48
R
ET
H
ET 1 Inte
H2 rn
RS Locaet
48 l
5
9 8
Figure 3-1 Connection and operating elements of the IoT gateway
1 Supply plug
2 RS-232 interface
3 CAN bus interface
4 Service interface (USB type C)
5 Diagnostic and status indicators
6 Reset button
7 Ethernet interface for connection to the Internet and the PROFICLOUD
8 Ethernet interface for local network connection
9 RS-485 interface
The CAN bus interface and service interface currently have no function.

CLOUD IOT GATEWAY
3.4.2 Printing
1 2 3 4
POWER RS232 CAN
CLOUD IOT GATEWAY

Ord.-No. 10 312 35
IP Address 192.168.10.10
Mac.: Addr. 00.A0.45.9D13.BC
Serial No. 0123456789
UUID: 12345678-9abc-def0-1234-56789abc
RS485 ETH2 Local ETH1 Internet
6 5
Figure 3-2 Printing
1 Default IP address
2 Order number and order designation
3 Serial number
4 MAC address
5 UUID
6 QR code

3.5 Diagnostic and status indicators
PWR
RS232
CAN
Ord.No. 10 31 23 5 CLOUD IOT GATEWAY

PROFICLOUD
USB
PWR
ONL
ERR
ACT
SF
RESET
ETH1 Internet
ETH2 Local
RS485
Figure 3-3 Diagnostic and status indicators
Table 3-1 Diagnostic and status indicators of the IoT gateway
Designa Color Meaning State Description

tion
Off 24-V supply voltage feed-in is not available or too low.
PWR Green Voltage supply
On 24-V supply voltage feed-in is available.
Green IoT gateway is off
Off or
PROFICLOUD service is not running.
Status of the Flashing No connection to PROFICLOUD.
ONL connection to the slowly
PROFICLOUD
Flashing Firmware update is in progress.
quickly
On Connection to the PROFICLOUD is OK.
Error in the Off No error in the service of the IoT gateway.
ERR Red service of the IoT Error in the service of the IoT gateway; IoT gateway has to be
gateway On
restarted.
Off IoT gateway: No memory access active
Memory access
ACT Yellow Flashing The IoT gateway transmits the data to the PROFICLOUD.
active
On IoT gateway: Memory access active

CLOUD IOT GATEWAY
Table 3-1 Diagnostic and status indicators of the IoT gateway

Designa Color Meaning State Description
tion
Off
SF Red Group error Flashing Currently without function
On
Off Connection not established successfully
– Green Link status Connection successfully established (link)
On
The IoT gateway can contact another network participant.
Off Data transmission not active
– Yellow Activity status Flashing/ Data transmission active (activity)
On The Ethernet interface sends or receives data.

3.6 Reset button
R
PW32
2
RS N
CA
B
US
PW
R
1
L
ON
R
ER
T
AC
SF
s et
Re
et
rn
Intecal
H1 Lo
ET H2 5
ET S48
R
108450A001
Figure 3-4 Reset button
On the device, there is a reset button that can be used to restart the IoT gateway or to reset
it to factory settings. The reset button can only be pressed with a pointed object, e.g. a pen.
Restart • During operation, press the reset button for < 2 s.

The IoT gateway restarts.
Resetting to factory • During operation, press the reset button for > 3 s.
defaults
The IoT gateway is reset to factory settings. This process can take approx. 1 minute.

CLOUD IOT GATEWAY
3.7 Parameterization memory

The IoT gateway has an internal parameterization memory in which the configuration of the
IoT gateway is stored. Received sensor and process data is buffered.
3.8 Internal basic circuit diagram
Power RS232 CAN
24V
3,3V
USB
PWR
ONL
µP ERR
ACT
SF
Reset
RS485 ETH2 ETH1

Local Internet
Figure 3-5 Internal basic circuit diagram
Key:
µP Microprocessor RS485 RS-485 interface
USB Service interface (USB type C) Transmitter
Reset button LED
RJ45 interface Voltage transformer
RS232 RS-232 interface Photocoupler
CAN CAN bus interface PWR Supply plug
The grayed fields in the basic circuit diagram represent areas that are galvanically isolated.

3.9 Supply plug
POWER
11 121314 15
R
PW32
2
RS N
CA
B
US
R
PW
L
ON
R
ER
T
AC
SF
s et
Re
et
rn
Intecal
H1 Lo
ET H2 5
ET S48
R
108450A002
Figure 3-6 Supply plug
Terminal point
assignment
Table 3-2 Terminal point assignment of the supply connector
Terminal Assignment Description

point
11 n. c. Not connected
14 GND Reference potential GND (24 V supply)
15 + +24 V DC

CLOUD IOT GATEWAY
3.10 Interfaces
The following interfaces are available on the IoT gateway:
(1) 2 x Ethernet 10/100 BASE-T(X)

For Modbus/TCP and Internet connection
(2) Service interface (USB Currently without function

type C)
(3) RS-485 interface For Modbus/RTU
(4) CAN bus interface Currently without function
(5) RS-232 interface For Modbus/RTU
3.10.1 Ethernet
The IoT gateway has two Ethernet interfaces:
ETH1 Internet: Ethernet interface for connection to the Internet and the
PROFICLOUD
ETH2 Local: Ethernet interface for local network connection
The Ethernet network is connected via RJ45 sockets.

The contact assignment of the interface is as follows:
Pin Signal Meaning
RJ45 Pin 1 1 T+ Transmit data +
Pin 2 2 T- Transmit data -
Pin 3 3 R+ Receive data +
Pin 4 4 – –
Pin 5 5 – –
Pin 6 6 R- Receive data -
Pin 7 7 – –
Pin 8 8 – –
Figure 3-7 Ethernet interface and pin assignment
The Ethernet interfaces are able to switch over the transmitter and receiver automatically
(auto crossover).

3.10.2 Service interface (USB type C)
The service interface currently has no function.
R
PW32
2
RS N
CA
1
B
US
R
PW
L
ON
R
ER
T
AC
SF
s et
Re
et
rn
Intecal
H1 Lo
ET H2 5
ET S48
R
108450A008
Figure 3-8 Service interface (USB type C)

CLOUD IOT GATEWAY
3.10.3 RS-485 interface
R
PW32
2
RS N
CA
B
US
R
PW
L
ON
R
ER
T
AC
SF
s et
Re
et
1 2 3 4 5 rn
Intecal
H1 Lo
ET H2 5
ET S48
R
RS485 108450A003
Figure 3-9 RS-485 interface
Terminal point
assignment
Table 3-3 Terminal point assignment of the RS-485 interface

point
1 B Channel B
2 R Termination resistor channel B
3 GND Reference potential of the RS-485 interface
4 R Termination resistor channel A
5 A Channel A

3.10.4 CAN bus interface
The CAN bus interface currently has no function.
CAN
1 2 3 4 5
R
PW32
2
RS N
CA
B
US
R
PW
L
ON
R
ER
C T
A
S F
s et
Re
e t
rn
Intecal
H1 Lo
ET H2 5
ET S48
R
108450A004
Figure 3-10 CAN bus interface
Terminal point
assignment
Table 3-4 Terminal point assignment of the CAN bus interface

point
2 GND Reference potential
3 H Inverted CAN signal (CAN-H)
4 SH Shielding
5 L Non-inverted CAN signal (CAN-L)

CLOUD IOT GATEWAY
3.10.5 RS-232 interface
RS-232
6 7 8 9 10
R
PW32
2
RS N
CA
B
US
R
PW
L
ON
R
ER
T
AC
SF
s et
Re
et
rn
Intecal
H1 Lo
ET H2 5
ET S48
R
108450A005
Figure 3-11 RS-232 interface
Terminal point
assignment
Table 3-5 Terminal point assignment of the RS-232 interface

point
7 GND Reference potential of the RS-232 interface
8 TX Transmit data
9 SH Shielding
10 RX Receive data

Mounting hardware
4 Mounting hardware
4.1 Safety notes


NOTE: Damage to the electronics

persons.

permitted voltage range is from 18 V DC to 30 V DC (ripple included). If the voltage
• Make sure that the voltage is not higher or lower than the permitted range.


• Install the device on a horizontal DIN rail to maintain the protection rating of the device.

CLOUD IOT GATEWAY

thresholds.


DIN rail.
On the rear of the device there are two FE springs that make contact with the DIN rail when
the device is placed on the DIN rail.
Please note:

Mounting hardware
4.2 Mounting the IoT gateway

Mounting position

• Install the device on a horizontal DIN rail to maintain the protection rating of the device.
Mounting the IoT gateway • Remove power from the unit.

• Place the device onto the DIN rail from above (A), then press it down (B).
A B
Figure 4-1 Mounting the IoT gateway

CLOUD IOT GATEWAY
4.3 Assembling the COMBICON connector

• Plug all COMBICON connectors into the corresponding sockets on the IoT gateway.
The designations of the COMBICON sockets are printed on the side of the IoT gateway.
• Pay attention to the printing on the terminal points on the COMBICON connectors:
Printing COMBICON connector for

1 ... 5 RS-485 interface
1 ... 5 CAN bus interface
6 ... 10 RS-232 interface
11 ... 15 24 V supply
NOTE: Device defect

If you do not connect the COMBICON connectors to the corresponding sockets on the IoT
gateway, there is risk of connecting the lines to the wrong terminal points. Connecting the
conductors to incorrect terminal points can lead to device defects.
• Make sure that each COMBICON connector is plugged into the correct socket at the
IoT gateway.
• When connecting the conductors, observe the terminal point assignment of the
respective COMBICON connector.

Connecting and wiring hardware
5 Connecting and wiring hardware
5.1 Safety notes



persons.

permitted voltage range is from 18 V DC to 30 V DC (ripple included). If the voltage
• Make sure that the voltage is not higher or lower than the permitted range.


thresholds.


CLOUD IOT GATEWAY

DIN rail.
On the rear of the device there are two FE springs that make contact with the DIN rail when
the device is placed on the DIN rail.
Please note:
5.2 Supply voltage
5.2.1 Sizing of the power supply

• Select an appropriate power adapter.
WARNING: Loss of electrical safety when using unsuitable power supplies

The device is intended exclusively for operation with protective extra-low voltage (PELV)
in acc. with EN 60204-1. Only PELV in accordance with the defined standard may be used
for supply purposes.
The following applies for the network compound and the I/O devices used therein:
Only use power supply units that meet EN 61204 with safe isolation and PELV in
accordance with EN 50178 or EN 61010-2-201. This prevents short circuits between
primary and secondary sides.
Proper operation of the device requires a voltage supply without fall-back

characteristic (see Figure 5-2).
When the device is switched on, there briefly is an increased inrush current. At the moment
when it is switched on, the device acts like a capacitive load.

Some electronically controlled power supplies have a fall-back characteristic curve (see
Figure 5-1). They are not suitable for operation with capacitive loads.
Overload range
Overload range
UOUT with fall-back UOUT without fall-back
characteristic curve characteristic curve
[V] [ V]
24 24
I OUT I OUT
IN [A] [ A]
1.1 x I N 2.4 x I N IN 1.5 x I N
6219C070 6219C071
Figure 5-1 Overload range with fall-back characteristic Figure 5-2 Overload range without fall-back
curve characteristic curve

CLOUD IOT GATEWAY
5.2.2 Connecting the voltage supply

• Strip 8 mm of the wire.
• Fit a ferrule to the wire, if required.
Make sure that the ferrule is crimped correctly.
Solid cable/ferrule • Insert the cable into the terminal point. The wire is clamped automatically.
Figure 5-3 Connecting a solid cable
Stranded cable • Open the spring by pressing on the spring lever with a screwdriver (A).
• Insert the cable in the terminal point (B).
• Remove the screwdriver to secure the cable.
Recommended:
Slotted screwdriver, blade width 2.5 mm (e.g. SZS 0.4x2.5 VDE, Order No. 1205037)
A
B
Figure 5-4 Connecting a stranded cable

5.3 Connecting the Internet

• Connect the Internet to the “ETH1 Internet” RJ45 socket using an Ethernet cable.
• Use an Ethernet cable that complies with at least CAT5 of IEEE 802.3.
• Observe the bending radii of the Ethernet cables used.
ET
H
ET 1 Inte
H2 rn
RS Locaet
48 l
5
108450A006
Figure 5-5 Connecting the Internet
5.4 Connecting the local Ethernet network

• Connect the local network to the “ETH2 Local” RJ45 socket using an Ethernet cable.
• Use an Ethernet cable that complies with at least CAT5 of IEEE 802.3.
• Observe the bending radii of the Ethernet cables used.
If you want to access the web-based management (WBM) of the IoT gateway with your
PC:
• Connect your PC to the “ETH2 Local” RJ45 socket using an Ethernet cable.
ET
H
ET 1 Inte
H2 rn
RS Locaet
48 l
5
108450A007
Figure 5-6 Connecting the local Ethernet network

CLOUD IOT GATEWAY
5.5 Connecting the RS-485, CAN bus and RS-232

participants
The CAN bus interface currently has no function.
• When connecting RS-485, CAN bus and RS-232 participants, pay attention to the
terminal point assignment of the respective interface, see Section 3.10.3,
Section 3.10.4 and Section 3.10.5.
• Strip 8 mm of the wire.
• Fit a ferrule to the wire, if required.
Make sure that the ferrule is crimped correctly.
Solid wire/ferrule • Insert the cable into the terminal point. The wire is clamped automatically.
Figure 5-7 Connecting a solid cable

Stranded cable • Open the spring by pressing on the spring lever with a screwdriver (A).
• Insert the cable in the terminal point (B).
• Remove the screwdriver to secure the cable.
Recommended:
Slotted screwdriver, blade width 2.5 mm (e.g. SZS 0.4x2.5 VDE, Order No. 1205037)
A
B
Figure 5-8 Connecting a stranded cable

CLOUD IOT GATEWAY
6 Web-based management (WBM)

Via the web-based management, you can configure the CLOUD IOT GATEWAY and create
metrics for the devices whose sensor and process data is to be transmitted to the
CLOUD IOT GATEWAY and the PROFICLOUD.
6.1 Establishing a connection with the WBM

• Connect your PC to the “ETH2 Local” RJ45 socket using an Ethernet cable.
• Open the web browser on your PC.
• In the address field, enter the URL “http://IP address of the IoT gateway” (default IP
address: 192.168.10.10).
The login page of the WBM opens.
6.2 Login
Figure 6-1 WBM: Login page
First access When you access the WBM for the first time, log in as the administrator with the following
default access data:
• In the “Login” input field, enter the default user name “admin”.
• In the "Password” input field, enter the default password “private".
• Click the “Sign In” button.
The “Home” page opens, see Section 6.5.
Recommended:
• Only use the default access data for the initial log in only.
• Once you have logged in successfully, change the user name and password to
prevent unauthorized access (see Section 6.3.2).

Web-based management (WBM)
Please note:
After the access data for the administrator has been changed, it is no longer possible to
log in with the default user name “admin” and the default password “private”.
You can restore the default access data by resetting the IoT gateway to the factory settings
(see Section 6.6.9).
Logging in with changed Once you have changed the default access data, use the changed user name and the
access data associated password to log in:
• Enter your user name in the “Login” input field.
• Enter your password in the “Password” input field.
Logging in as user As administrator, you can add additional users that are permitted to access the WBM of the
IoT gateway. To this end, you assign a user role with the necessary access permissions to
each user, see Section 6.6.2.
As user, you log in with the user name and the associated password:
• Enter your user name in the “Login” input field.
• Enter your password in the “Password” input field.

CLOUD IOT GATEWAY
6.3 User preferences – “Users” menu

You can open the user preferences with a click on the button (at the top right of every
page).
Figure 6-2 WBM: "Users” menu
6.3.1 Showing help – “Help” menu

• Click the button.
• Select “Help”.
The “Home/Help” page opens.
Figure 6-3 WBM: “Home/Help” page
On the “Home/Help” page, you can find an overview of the commands that you can use for
the update condition, see Section 6.5.2.4.

6.3.2 Editing access data – “Profile” menu
Editing access data With the “Profile” menu, you can change the access data with which you are currently
logged in at the WBM.
• Select “Profile”.
The “Home/Profile” page opens.
Figure 6-4 WBM: “Home/Profile” page

CLOUD IOT GATEWAY
• Enter the desired user name in the “Username” input field.

• Enter the desired new password in the “New password” input field.
Permissible characters:
– a ... z
– A ... Z
– 0 ... 9
Recommended:
• Use a combination of uppercase letters, lowercase letters, and digits for the
password.
The password should be at least 6 characters long.
• Enter the desired new password again in the “Confirm Password” input field.
• From the “Language” drop-down list, select the display language of the WBM.
After logging in, the user will see the WBM in the language selected here.
• In the “Confirm changes with your current password” input field, enter the old password
(default password of the "admin” in the factory settings: “private”).
• To apply the edited access data, click the “Update” button.
Discarding changes • To discard your changes, click the “Discard” button.

6.4 Showing and filtering the event history –

“Journal” button
• Click the button to open the event history.
The “Home/Journal” page opens.
Figure 6-5 WBM: “Home/Journal” page
Event Action/event filter

You can set a filter in order to only show certain actions or
events in the event history.
• Select the desired filter from the drop-down list (see
Table 6-1).
The filtered event history is displayed.

CLOUD IOT GATEWAY
Show X Entries Number of actions or events per page

• In the drop-down list, select how many actions or events
are to be displayed per page.
Search Search the event history

• Enter the desired search item.
The page displays all actions or events that contain the
desired search item.
First Switch between the pages of the event history

Previous
– Go to first page (First)
X
Next – Go one page back (Previous)
Last – Go to page X (X)
– Go to next page (Next)
– Go to last page (Last)
Timestamp Time of the action or event

By default, the newest entry in the event history is shown as
last entry (ascending sorting). You can alternatively sort the
entries in descending order (newest entry as first entry).
• Click on “Timestamp” to switch from ascending to
descending sorting and vice versa.
Context User name of the user who carried out a particular action.
You can order the entries in the event history by user name, in
either alphabetically ascending order (starting with A) or
alphabetically descending order (starting with Z).
• Click on “Context” to switch from ascending to
Event Action or event

You can order the entries in the event history by action or
event, in either alphabetically ascending order (starting with A)
or alphabetically descending order (starting with Z).
• Click on “Event” to switch from ascending to descending
sorting and vice versa.

Table 6-1 shows which actions or events the event history can be filtered by.
Table 6-1 Possible action/event filters of the event history

Action or event Description
None No action or event filter (default setting)
Configuration imported CLOUD IOT GATEWAY was configured
with a *.json configuration file.
Connector created A new connection has been created.
Connector deleted A connection has been deleted.
Default buffer settings updated The default buffer size of the metrics has
been changed.
Global buffer settings updated The global buffer size of the IoT gateway
has been changed.
HTTP/HTTPS method changed Connection to WBM has been changed
from HTTP to HTTPS or vice versa.
Login fail, wrong password A user entered the wrong password when
attempting to log in at the WBM.
Metric created A new metric has been created.
Metric deleted A metric has been deleted.
Network interfaces changed The settings of at least one communication
interface has been changed.
Proxy settings changed The proxy settings have been changed.
TLS certificate generated A self-signed TLS certificate has been
created for the secure HTTPS connection
to the WBM.
TLS certificate updated A TLS certificate has been renewed.
User created A user has been created.
User deleted A user has been deleted.
User login A user has logged in to the WBM.
User logout A user has logged out from the WBM.

CLOUD IOT GATEWAY
6.5 “Home” page

On the “Home” page, you can define connections for the communication between the IoT
gateway and the devices whose sensor or process data is collected, processed and
monitored in the PROFICLOUD. For each connection, you can select a communication
protocol and define connection details.
Figure 6-6 WBM: “Home” page
“Connectors” area
Show only active Filter: Only active connections
To view only connections with active communication, you can
set a corresponding filter.
• Check the box.
Now only connections with active communication are
displayed.
Show X Entries Number of connections per page

• In the drop-down list, select how many connections are to
be displayed per page.
Search Search connections

The page displays all connections that contain the desired
search item.

First Switch between the display pages

Previous
X
Add Create connection

See Section 6.5.1, “Creating a connection”

CLOUD IOT GATEWAY
6.5.1 Creating a connection

• Click the “Add” button.
The “Create connector” window opens.
Figure 6-7 WBM: “Create connector” window
• Enter a unique and meaningful name for the connection in the “Name” input field.
Select the desired communication protocol from the drop-down list.
Possible settings:
– Modbus/TCP
– Modbus/RTU
• To create the connection, click the “Add connector” button.
The created connection (in the example: “Electricity meter”) is now displayed on the “Home”
page, in the “Connectors” area.
Figure 6-8 Connections on the “Home” page
If you have created a connection, you have to define the connection details.

6.5.2 Defining connection details

• Click on the connection for which you want to define the connection details.
The “Home/Connectors” page of the selected connection opens.
Figure 6-9 WBM: “Home/Connectors” page

CLOUD IOT GATEWAY
6.5.2.1 Connection settings – “Connector settings” area
Figure 6-10 WBM: “Home/Connectors” page, “Connector settings” area of a connection

with Modbus/TCP protocol

In the “Connector settings” area, you define the following connection details:
General settings
Name Name of the connection
• If necessary, change the name that you entered when you
created the connection.
Cycle (in ms) Cycle time (in ms)

• Enter the desired cycle time within which the IoT gateway
is to call up the sensor or process data of a device
(Modbus/TCP server or Modbus/RTU slave).
Active Activate/deactivate connection

• Activate the check box if you want to use the connection.
• Deactivate the check box if you don't want to use the
connection.
Protocol-specific settings
for Modbus/TCP –
Device Address IP address of the Modbus/TCP server
“Protocol-specific
settings” area • Enter the IP address of the device (Modbus/TCP server)
whose sensor or process data is to be called up from the
IoT gateway.
Device Port Port

• Enter the port.
Slave Id Slave ID of the Modbus/TCP server

• Enter the slave ID (1 ... 247) of the device (Modbus/TCP
server) whose sensor or process data is to be called up
from the IoT gateway.
Timeout (in ms) Connection time-out in ms

• Enter the time for the connection time-out.
This value specifies the minimum time required to identify an
interruption in the communication connection.
In addition, the value specifies the time within which the
Modbus/TCP server needs to have responded to a request
In the event of connection aborts:

• Increase the time for the connection time-out to
prevent connection aborts.

CLOUD IOT GATEWAY
for Modbus/RTU –
Serial Interface Serial communication interface
“Protocol-specific
settings” area • Select the communication interface.
Possible settings:
– RS-485
– RS-232
Slave Id Slave ID of the Modbus/RTU slaves

• Enter the slave ID (1 ... 247) of the device (Modbus/RTU
slave) whose sensor or process data is to be called up
Timeout (in ms) Connection time-out in ms

• Enter the time for the connection time-out.
This value specifies the minimum time required to identify an
interruption in the communication connection.
In addition, the value specifies the time within which the
Modbus/RTU slave needs to have responded to a request
In the event of connection aborts:

• Increase the time for the connection time-out to
prevent connection aborts.
Data bits Number of data bits

• Select the number of data bits.
Stop bits Number of stop bits

• Select the number of stop bits.
Parity Parity
• Select the parity.
Baud rate Baud rate

• Select the baud rate.
Disconnecting and re- • To disconnect and reconnect the communication connection of the IoT gateway to a
establishing the device (Modbus/TCP server or Modbus/RTU slave), click “Reconnect”.
communication
connection

Applying settings • To apply the settings and reconnect the communication connection, click the “Update
and reconnect” button.
Deleting a connection • To delete the connection, click the “Delete” button.
6.5.2.2 Log messages – “Connector logs” area
Figure 6-11 WBM: “Home/Connectors” page, “Connector logs” area
In the “Connector logs” area, log messages of the connection are shown, e.g. when the
connection to a Modbus/TCP server has been established.

CLOUD IOT GATEWAY
6.5.2.3 Creating and updating metrics – “Metric list” area
Figure 6-12 WBM: “Home/Connectors” page, “Metric list” area
Add metric Create a metric

See Section „Creating a metric“
Show X Entries Number of metrics per page

• In the drop-down list, select how many metrics are to be
displayed per page.
Refresh view
• Click on the button to refresh the view.

Search Search the metrics

The page displays all metrics that contain the desired search
item.

Previous
X
Metric name Name of the metric

You can order the entries by the names of the metrics, in either
alphabetically ascending order (starting with A) or
• Click on “Metric name” to switch from ascending to
Buffer usage Size of the IoT gateway buffer that is available for this metric
You can order the entries by the buffer size of a metric, in
ascending or descending order.
• Click on “Buffer usage” to switch from ascending to
Latest value Last value that the IoT gateway received from a selected
device.
Creating a metric Sensor and process data of selected devices is sent to the CLOUD IOT GATEWAY, from
where it is transferred to the PROFICLOUD as a metric.
You have to create a metric for each sensor or process data item to be transmitted:
• Click the “Add” button.

CLOUD IOT GATEWAY
The “Create metric” window opens.
Figure 6-13 WBM: “Create metric” window
• Enter a unique and meaningful name for the metric in the “Name” input field.
• To create the metric, click the “Add metric” button.
The created metric (in the example: “Energy consumption”) is now displayed on the
“Home/Connectors” page, in the “Metric list” area.
Once you have created a metric, you assign the metric the sensor or process data item of a
selected device that is to be transmitted to the PROFICLOUD. The assignment is done by
means of Modbus register addresses, see Section 6.5.2.4.

6.5.2.4 Configuring metric settings

• On the “Home/Connectors” page, in the “Metric list” area, click the metric to be
configured.
The metric settings open.
Figure 6-14 WBM: Metric settings

CLOUD IOT GATEWAY
Metric settings –
“Metric Settings” area
Name Name of the metric
• If necessary, change the name that you entered when you
created the metric.
Buffer Size Maximum buffer size for the metric

The IoT gateway permanently checks the connection to the
PROFICLOUD and buffers the received sensor or process
data. This ensures that, if the connection to the PROFICLOUD
is interrupted, no sensor or process data is lost.
You can define the maximum buffer size for each metric:
• Enter the maximum buffer size for the metric.
The buffer size for the metric is preset with the default buffer
size that you defined on the “Buffers” tab, see Section 6.6.6.
If you do not enter a maximum buffer size for the metric, the
default buffer size is used.
Update Condition Update condition

• Enter the condition that has to be met for the IoT gateway
to send the metric to the PROFICLOUD.
For information on the permitted commands, see
Section 6.3.1.

– “Protocol-Specific
Modbus Function Modbus function code
Settings” area
• Select the Modbus function code that the IoT gateway
should use to read the sensor or process data of a device.
Possible settings:
– (0X02) Read Discrete Inputs:
Bit-by-bit reading of several digital inputs
– (0X01) Read Coils:
Bit-by-bit reading of several bits or digital outputs
– (0X04) Read Input Registers:
Word-by-word reading of several input registers
– (0X03) Read Holding Registers:
Word-by-word reading of several internal registers or
output registers
Starting Register Start address of the Modbus register

As Decimal
• Enter the start address of the Modbus register as decimal
number.
The start address is the address of the Modbus register from
which the sensor or process data is read.
Value Type Data type

• Select the data type.
Possible settings:
– float32: 4 bytes, 0 ... 4294967295
– int:
– int16 (number of Modbus registers to be read = 1):
2 bytes, -32768 ... 32767
– int32 (number of Modbus registers to be read = 2):
4 bytes, -2147483648 ... 2147483647
– unsigned int:
– uint16 (number of Modbus registers to be read = 1):
2 bytes, 0 ... 65535
– uint32 (number of Modbus registers to be read = 2):
4 bytes, 0 ... 4294967295
– float64:
8 bytes, -1.7976931348623158 E+308 ...
-2.2250738585072014 E-308
and
+2.2250738585072014 E-308 ...
+1.7976931348623158 E+308

CLOUD IOT GATEWAY
Quantity Of Number of Modbus registers to be read

Registers (Number
• Enter the number of Modbus registers to be read.
Of Words)
This entry is only required for the “int” data type.
Endianness Byte order

• Select the byte order.
Possible settings:
– Big Endian:
Most significant data word and high byte first
– Little Endian:
Least significant data word and low byte first
Applying settings • To apply the settings, click the “Update” button.
Deleting a metric • To delete the metric, click the “Delete” button.
Discarding changes • To discard your changes to the metric settings, click the “Discard” button.

6.6 Advanced settings – “Settings” menu

You can open the advanced settings with a click on the button (at the top right of every
page).
Figure 6-15 WBM: “Settings” menu
6.6.1 System information – “Info” tab

In the “Info” tab, you can find system information about the IoT gateway.
Figure 6-16 WBM: “Home/Settings” page, “Info” tab
UUID UUID of the CLOUD IOT GATEWAYs
Software version Firmware version of the ICLOUD IOT GATEWAYs
License The CLOUD IOT GATEWAY works with a Linux operating

system.
• To view the license information for the individual Linux
packages, click the link.
In the web browser, a new window with the license information
appears.
PROFICLOUD Status of the connection of the CLOUD IOT GATEWAY to the

state PROFICLOUD

CLOUD IOT GATEWAY
6.6.2 Managing users – “Users” tab

On the “Users” tab, you manage the access data of all users that are permitted to access
the WBM of the IoT gateway. To this end, you assign a user role with the necessary access
permissions to each user.
Currently, only the “Admin” user role (access permission to the WBM with administrator
rights) is available.
Figure 6-17 WBM: “Home/Settings”, “Users” tab
Add user Add user

See Section „Adding users“
Show X Entries Number of users per page

• In the drop-down list, select how many users are to be
displayed per page.
Search Search the users

The page displays all users whose user data contains the
desired search item.


Previous
X
User name User name

You can order the entries by the user names, in either
alphabetically ascending order (starting with A) or
• Click on “User name” to switch from ascending to
Last Login Last time the WBM was accessed

You can sort the entries by the time of the last access to the
WBM, in ascending order (oldest date first) or descending
order (newest date first).
• Click on “Last login” to switch from ascending to
Language Display language of the WBM

You can order the entries by the display language of the WBM,
in either alphabetically ascending order (starting with A) or
• Click on “Language” to switch from ascending to
User role User role

You can order the entries by the designations of the user roles,
in either alphabetically ascending order (starting with A) or
• Click on “User role” to switch from ascending to
Enabled User with activated/deactivated user data

You can sort the entries by users with activated or deactivated
access data.
• Click “Enabled” to switch from sorting by users with
enabled access data to users with disabled access data.

CLOUD IOT GATEWAY
Edit Edit or delete the access data of a user

• To edit the access data of a user, click .
The “Update user” window opens.
The settings in the “Update user” window are identical to those
in the “Create user” window, see Section „Adding users“.
• Click on the button to delete a user.
Confirm the subsequent safety prompt by clicking the
“Delete“ button.
Adding users • To add a user, go to the “Users” tab and click the “Add user” button.
The “Create user” window opens.
Figure 6-18 WBM: “Create user” window
• Enter the desired user name in the “Username” input field.

• Enter the desired password in the “Password” input field.
Permissible characters:
– a ... z
– A ... Z
– 0 ... 9

Recommended:
• Use a combination of uppercase letters, lowercase letters, and digits for the
password.
The password should be at least 6 characters long.
• Enter the desired new password again in the “Confirm password” input field.
• Check the ”Enabled” box to activate the access data of the created user.
Unchecking the “Enabled” box deactivates the access data of the user. If the access data
of a user has been deactivated, the user cannot access the WBM.
• From the “Language” drop-down list, select the display language of the WBM.
After logging in, the user will see the WBM in the language selected here.
• In the drop-down list, select the user role with the desired access permissions.
• Click the “Add user” button to add the new user.

CLOUD IOT GATEWAY
6.6.3 Network settings – “Network” tab

On the “Network” tab, you can configure the “ETH1 Internet” and “ETH2 Local” Ethernet
interfaces.
Figure 6-19 WBM: “Home/Settings” page, “Network” tab

6.6.3.1 Settings of the Ethernet interface “ETH1 Internet” –

“Network interface eth0” area
Figure 6-20 WBM: “Home/Settings/Network” page, “Network interface eth0“ area
DHCP/Static Type of IP address assignment

• Activate the option button for the desired type of IP
address assignment.
Possible settings:
– DHCP:
The Ethernet interface “ETH1 Internet” automatically
receives IP address settings via a DHCP server.
– Static:
You statically assign the IP address settings that you
specified in the “IPv4”, “IPv4 Mask” and “IPv4 Default
Gateway” input fields to the Ethernet interface “ETH1
Internet”.
IPv4 IP address of the Ethernet interface “ETH1 Internet”

• Enter the desired IP address.

CLOUD IOT GATEWAY
IPv4 Mask Subnet mask of the Ethernet interface “ETH1 Internet”

• Enter the desired subnet mask.
IPv4 Default Default gateway of the Ethernet interface “ETH1 Internet”

Gateway
• Enter the IP address of the default gateway.
6.6.3.2 Settings of the Ethernet interface “ETH2 Local” –

“Network interface eth1” area
Figure 6-21 WBM: “Home/Settings/Network” page, “Network interface eth1“ area

DHCP/Static Type of IP address assignment

• Activate the option button for the desired type of IP
address assignment.
Possible settings:
– DHCP:
The Ethernet interface “ETH2 Local” automatically
receives IP address settings via a DHCP server.
– Static:
You statically assign the IP address settings that you
specified in the “IPv4”, “IPv4 Mask” and “IPv4 Default
Gateway” input fields to the Ethernet interface “ETH2
Local”.
IPv4 IP address of the Ethernet interface “ETH2 Local”

• Enter the desired IP address.
IPv4 Mask Subnet mask of the Ethernet interface “ETH2 Local”

• Enter the desired subnet mask.
IPv4 Default Default gateway of the Ethernet interface “ETH2 Local”

Gateway
• Enter the IP address of the default gateway.
6.6.3.3 Nameserver settings – “Nameserver Settings” area

CLOUD IOT GATEWAY
Figure 6-22 WBM: “Home/Settings/Network” page, “Nameserver Settings” area
• Enter the IP address(es) of the desired nameserver(s).
Applying setting • To apply the setting, click the “Update” button.
Discarding change • To discard your change, click the “Discard” button.

6.6.3.4 Proxy server settings – “Proxy” area
Figure 6-23 WBM: “Home/Settings/Network” page, “Proxy” area
Active Use a proxy server

• Check the box if you are using a proxy server.
Proxy type Communication protocol for authenticating the proxy server

• In the drop-down list, select the communication protocol
for authenticating the proxy server.

CLOUD IOT GATEWAY
URL URL of the proxy server

• Enter the URL of the proxy server.
User name User name for access to the proxy server

• Enter the user name for accessing the proxy server.
Password Password for access to the proxy server

• Enter the password for accessing the proxy server.
Applying settings • To apply the settings, click the “Update” button.

6.6.4 Setting the realtime clock – “Time” tab

On the “Time” tab, set the realtime clock of the IoT gateway.
Figure 6-24 WBM: “Home/Settings” page, “Time” tab
Manually setting the • In the “Data and Time” input field, click on the displayed date.
realtime clock • In the calendar that opens, select the day.
• Below the open calendar, click on the time.
• In the dialog that opens, select the time using the arrow keys.
• To apply the settings for the realtime clock of the IoT gateway, click the “Update” button.
Synchronizing realtime • Click the “Synchronize (NTP)” button.

clock with PROFICLOUD
The realtime clock of the IoT gateway is synchronized with the date and time settings of the
NTP server
PROFICLOUD NTP server.

CLOUD IOT GATEWAY
6.6.5 Security settings – “Security” tab

On the “Security” tab, you enter a self-signed TLS certificate for secure HTTPS connection
to the WBM.
Figure 6-25 WBM: “Home/Settings” page, “Security” tab

6.6.5.1 Selecting a communication protocol – “Access method” area
Figure 6-26 WBM: “Home/Settings/Security” page, “Access method” tab
HTTPS port HTTPS port

This port is used if you have selected the HTTPS protocol in
the “Access method” drop-down list.
HTTP port HTTP port

This port is used if you have selected the HTTP protocol in the
“Access method” drop-down list.
Access method Communication protocol for the connection to the WBM

• In the drop-down list, select the communication protocol
(HTTP or HTTPS) for the connection to the WBM.
Update Applying settings

• To apply the settings, click the “Update” button.

CLOUD IOT GATEWAY
6.6.5.2 Storing key files – “Upload X.509 certificate” area
Figure 6-27 WBM: “Home/Settings/Security” page, “Upload X.509 certificate” area
An asymmetrical encryption method is used for creating a secure HTTPS connection to the
WBM.
Private key Key file that contains the private keys for the asymmetrical
Browse encryption method
• Click on the "Browse" button.
• In the file manager that opens, enter the key file that
contains the private key.
Public key Key file that contains the public key for the asymmetrical
Browse encryption method
• Click on the "Browse" button.
• In the file manager that opens, enter the key file that
contains the public key.

Update Storing key files

• To store the key files on the IoT gateway, click the
“Update” button.

CLOUD IOT GATEWAY
6.6.5.3 Generating a self-signed TLS certificate –

“Generate self-signed X.509 certificate” area
Figure 6-28 WBM: “Home/Settings/Security” page, “Generate self-signed X.509

certificate” area
For a secure HTTPS connection to the WBM, you generate a self-signed TLS certificate.
Country Country in which the company is registered

• Enter the country in which your company is registered.
State Federal state in which the company is registered

• Enter the federal state in which your country is registered.

Location City in which the company is registered

• Enter the city in which your company is registered.
Organisation Name of the company

• Enter the name of your company.
Organisational Unit Organizational unit or department

• Enter your organizational unit or department.
FQDN or Common FQDN (Fully Qualified Domain Name) or name of the IoT
Name gateway
• Enter the FQDN or the name of the IoT gateway.
E-mail E-mail address of the company

• Enter a valid company e-mail address.
Generate key Generate a self-signed TLS certificate

• To generate the self-signed TLS certificate, click the
“Generate key” button.
• Restart the IoT gateway.
The TLS certificate has now been saved in the
CLOUD IOT GATEWAYand is used for the secure HTTPS
connection to the WBM.

CLOUD IOT GATEWAY
6.6.6 Defining buffers – “Buffers” tab

On the “Buffers” tab, you can define the size of the global buffer of the IoT gateway and the
size of the default buffer for the metrics.
The IoT gateway permanently checks the connection to the PROFICLOUD and buffers the
received sensor or process data. This ensures that, if the connection to the PROFICLOUD
is interrupted, no sensor or process data is lost.
You can define the maximum buffer size for each metric, see Section 6.5.2.4, “Configuring
metric settings”. If you do not enter a maximum buffer size for a metric, the default buffer size
that you defined on the “Buffers” tab is used for the metric.
Please note:
The sum of the individual metric-specific buffer sizes many not exceed the size of the
global buffer. You can define the size of the global buffer on the “Buffers” tab.
Figure 6-29 WBM: “Home/Settings” page, “Buffers” tab

Defining the size of the

local buffer – “Global
Global buffer size Size of the global buffer
buffers” area
(in byte)
• Enter the size of the global buffer.
Please note:
The global buffer size must be smaller than the
maximum available RAM of the IoT gateway. The
maximum available RAM of the IoT gateway is
defined in the “Default buffers” area, as “System
maximum”.
Update Apply setting

• To apply the setting, click the “Update” button.
Discard Discard change

• To discard your change, click the “Discard” button.
Defining the size of the

default buffer of the
Buffering enabled Activate or deactivate the buffer
metrics – “Default buffers”
area • Check the box to save received sensor or process data in
the buffer of the IoT gateway.
• Uncheck the box if received sensor or process data
should not be saved in the buffer of the IoT gateway.
Default buffer size Size of default buffer of the metrics

(in byte)
• Enter the size of the default buffer.
In the settings for the metrics, the value defined here is used
for the size of the default buffer. You can enter the buffer size
for each individual metric, see Section 6.5.2.4, “Configuring
metric settings”.
System maximum Maximum available RAM of the IoT gateway
Currently used Buffer size already in use for other metrics

CLOUD IOT GATEWAY
Update Apply setting

• To apply the setting, click the “Update” button.
Discard Discard changes

• To discard your changes, click the “Discard” button.

6.6.7 Importing configuration file or exporting configuration –

“Import/Export” tab
On the “Import/Export” tab, you can save the IoT gateway configuration that you created via
WBM as *.json file, or import an existing *.json configuration file.
Figure 6-30 WBM: “Home/Settings” page, “Import/Export” tab
Importing a configuration • Click on the "Browse" button.

file – “Import • In the file manager that opens, enter the *.json configuration file that contains the
configuration” area configuration to be imported.
• To import the configuration, click the “Import” button.
All settings of the IoT gateway are now overwritten with the imported configuration.
Exporting a configuration • Click the “Export” button.

as configuration file –
“Export configuration”
area

CLOUD IOT GATEWAY
6.6.8 Updating the firmware – “Update” tab

On the “Update” tab, you can initiate a firmware update of the IoT gateway.
Figure 6-31 WBM: “Home/Settings” page, “Update” tab
Establishing a USB • Connect the service interface of the IoT gateway with your PC.
connection
Downloading the update • Download the *.zip update file from the address phoenixcontact.net/products on the
file page of the IoT gateway.
• Unzip the *.zip update file to a directory of your choice on your PC.
Updating firmware – • Click on the "Browse" button.

“Update” area • In the file manager that opens, select the *.rauc update file.
• To transfer the update file to the IoT gateway, click the “Upload” button.
If the update file has been transferred to the IoT gateway successfully, the firmware update
starts automatically.
While the update is in progress, the ONL LED flashes quickly.
After the firmware update, the IoT gateway is restarted automatically.

6.6.9 Deregistering the IoT gateway from the PROFICLOUD or

resetting it to factory settings – “Reset” tab
On the “Reset” tab, you can deregister the IoT gateway from the PROFICLOUD or reset the
IoT gateway to the factory settings.
Figure 6-32 WBM: “Home/Settings” page, “Reset” tab
Deregistering the IoT • Click the “Deregister” button.

gateway from the • To deregister the CLOUD IOT GATEWAY from the PROFICLOUD, confirm the safety
PROFICLOUD – prompt with “Yes”.
“Deregister from
PROFICLOUD” area If you have responded to the safety prompt by clicking “Yes”, the CLOUD IOT GATEWAY
restarts. After restarting, the device is deregistered from the PROFICLOUD and can be
registered in another account.
Resetting to factory • Click the “Reset” button.

settings – “Factory Reset” • To reset the CLOUD IOT GATEWAY to factory settings, confirm the safety prompt with
area “Yes”.
If you have responded to the safety prompt by clicking “Yes”, the CLOUD IOT GATEWAY is
reset to the factory settings.
Resetting the IoT gateway to the factory settings deletes all settings that you have
configured. Deleted settings cannot be restored.
The access data for the “admin” user is reset to the default access data (user name:
“admin”, password: “private”).

CLOUD IOT GATEWAY
6.6.10 Restarting the IoT gateway – “Restart” tab

On the “Restart” tab, you can initiate a restart of the IoT gateway.
Figure 6-33 WBM: “Home/Settings” page, “Restart” tab
Restarting the IoT • Click the “Restart” button.

gateway
The IoT gateway restarts.
6.7 Logout
To log out from the WBM, proceed as follows:
• Select “Logout”.

Transmitting sensor and process data to the PROFICLOUD
7 Transmitting sensor and process data to the

PROFICLOUD
7.1 Configuring the PROFICLOUD

Before you can transmit a metric to the PROFICLOUD, you have to register the
CLOUD IOT GATEWAY in the PROFICLOUD. To do this, proceed as follows:
Establishing a connection • Open the web browser on your PC.

to the web interface • In the address line, enter the URL “https://www.proficloud.net”.
Logging in • Enter your user name and your password.

• Click the “Sign In” button to sign into the PROFICLOUD.
Adding a To add the CLOUD IOT GATEWAY as appliance, go to the “Home/Solutions” menu and
CLOUD IOT GATEWAY select the PROFICLOUD solution “TSD Device Manager”.
Figure 7-1 PROFICLOUD solution “TSD Device Manager”
The “Appliances” page opens.

CLOUD IOT GATEWAY
Figure 7-2 “Appliances” page
Registering the • Click the “Add” button.

CLOUD IOT GATEWAY • The “Create Appliance” dialog opens.
Figure 7-3 “Create Appliance” dialog
• In the “UUID” input field, enter the UUID of the IoT gateway.
The UUID of the IoT gateway is printed on the side of the device.
• Enter a unique name for the IoT gateway in the “Appliance name” input field.
• Click on the “Add” button to save your entries.
The “IoT gateway” now appears on the “Appliances” page.

7.2 Displaying an overview of the metrics of the

IoT gateway
When the IoT gateway and the devices from which sensor and process data is read are
switched on, the respective metrics are automatically transmitted to the PROFICLOUD.
To view an overview of all metrics of the IoT gateway, proceed as follows:
• Go to the “Home/Solutions” menu and select the PROFICLOUD solution “TSD Device
Manager”.
The “Appliances” page opens.
• On the “Appliances” page, click the IoT for which you want to view the metrics.
The “Appliances / Name of the appliance” page opens.
Figure 7-4 “Appliances / Name of the appliance” page
The received metrics are shown in the “Metrics” area.

CLOUD IOT GATEWAY
7.3 Representing the metrics in Grafana graphically

The metrics can be represented graphically using the open platform Grafana.
To graphically represent a metric with Grafana, proceed as follows:
Establishing a connection • Go to the “Home/Solutions” menu and select the PROFICLOUD solution “TSD Device
with Grafana Manager”.
• Select the “Goto Analytics” entry in the menu.
The homepage of Grafana is opened.
Figure 7-5 Grafana: Homepage
Creating a new dashboard • Click on the “Home” button.

The Home page opens.
Figure 7-6 Grafana: “Home”

• Click on “New Dashboard” to create a new dashboard.

The “New Dashboard” page opens.
Figure 7-7 Grafana: “New Dashboard” page
Selecting the type of • Use the button to select a type of display (e.g. graph, etc.).
display
An example display opens for the selected graphical display (see Figure 7-8).
Selecting a metric • Click on “Panel Title” to select the metric to be displayed.

• Click on the “Edit” button.
Figure 7-8 Grafana: Example graph; Edit Panel Title
An area where you can edit the details of the selected graphical display opens below the
example display.

CLOUD IOT GATEWAY
• Switch to the “Metrics” tab.

• Select the metric to be displayed.
Figure 7-9 Grafana: Selecting the metric to be displayed
• Close the bottom area by clicking on the “X” button.

The selected metric is now displayed graphically.
Figure 7-10 Grafana: Graphical display of the selected metric

Removing hardware
8 Removing hardware
8.1 Safety notes


persons.
8.2 Removing cables

• Remove power from the unit.
• Open the spring by pressing on the spring lever with a screwdriver (A).
• Remove the cable (B).
A
B
Figure 8-1 Removing the cable

CLOUD IOT GATEWAY
8.3 Removing COMBICON connectors

• Pull the COMBICON connectors out of the sockets on the device.
8.4 Remove the Ethernet connector

• Release the RJ45 connector by pressing on the snap-in latch and remove the
connector.
8.5 Removing the IoT gateway

• Insert a tool in the base latch and pull gently upwards (A). Pull the device from the DIN
rail (B).
B
A
Figure 8-2 Removing the IoT gateway

After usage
9 After usage
9.1 Maintenance and servicing

The device is maintenance-free.
9.2 Device replacement

The IoT gateway can be replaced, if necessary.
If you want to replace an IoT in the bus configuration, proceed as described in Section 8,
“Removing hardware” and Section 4, “Mounting hardware”.
• Disconnect the power to the IoT gateway.
• Replace the IoT gateway in your bus configuration with an identical IoT gateway (same
order number).
• Once replaced, restore all the necessary connections.
• Import the configuration file of the old IoT gateway into the new IoT gateway, see
Section 6.6.7.
• Register the new IoT gateway in the PROFICLOUD, see Section 7.1.
9.3 Device defect and repair

Repairs may only be carried out by Phoenix Contact.
• Send defective devices back to Phoenix Contact for repairs or to receive a replacement
device.
• We strongly recommend using the original packaging to return the product.
• Include a note on the packaging indicating that the contents are returned goods.
• If the original packaging is no longer available, observe the following points:
– Observe the humidity specifications and the temperature range specified for transport
(see Section 10.2).
– If necessary, use dehumidifying agents.
– Use appropriate ESD packaging to protect components that are sensitive to
electrostatic discharge.
– Secure any loose parts.
– Make sure that the packaging you select is large enough and sufficiently thick.
– Only use plastic bubble wrap sheets as filler material.
– Attach warnings to the transport packaging so that they are clearly visible.
– Please be aware that the delivery note is to be placed inside the package in the case of
packages that are to remain within the same country. However, if the package is being
sent abroad, the delivery note must be placed inside a delivery note pocket and
attached to the outside so that it is clearly visible.

CLOUD IOT GATEWAY
9.4 Disposal
Disposing of the IoT • Do not dispose of the device in the household waste, but instead comply with the
gateway applicable national regulations.
Packaging disposal • Dispose of packaging materials that are no longer needed (cardboard packaging,
paper, bubble wrap sheets, etc.) with household waste in accordance with the currently
applicable national regulations.
9.5 Take-back
As an alternative, you can dispose of the device by returning it to Phoenix Contact.
• Include a note on the packaging indicating that the device should be disposed of.
Please note:
The device must not have any traces of being contaminated by oils, greases etc.

Ordering data and technical data
10 Ordering data and technical data
10.1 Ordering data
Description Type Order No. Pcs./Pkt.

Cloud IoT gateway for integrating new and existing systems without CLOUD IOT GATEWAY 1031235 1
additional engineering costs. Thanks to simple process connection using
protocols such as Modbus/TCP, sensor and process data can be
collected, processed, and monitored in the Proficloud.
Accessories Type Order No. Pcs./Pkt.

Runtime license for using devices in the PROFICLOUD, credit: 87600 units CLOUD CREDIT-10 2402986 1
Documentation Type Order No. Pcs./Pkt.

User manual, English: Startup and operation of hardware and software UM EN PROFICLOUD – –
components of the PROFICLOUD

CLOUD IOT GATEWAY
10.2 Technical data
Dimensions (nominal sizes in mm)

99 22,5
114,5
Width 22.5 mm
Height 99 mm
Depth 114.5 mm
General data
Color Gray
Weight 144.5 g (with connectors)
Mounting DIN rail mounting
Real-time clock Yes
Ambient conditions
Ambient temperature (operating) -25 °C ... 55 °C to 2000 m above mean sea level
Ambient temperature (storage/transport) -25°C ... 85°C
Permissible humidity (operation) 30% ... 95% (according to DIN EN 61131-2)
Permissible humidity (storage/transport) 5 % ... 95 %
Air pressure (operation) 70 kPa ... 106 kPa (up to 3000 m above mean sea level)
Air pressure (storage/transport) 58 kPa ... 106 kPa (up to 4500 m above mean sea level)
Degree of protection IP20
Shock 30g, 11 ms period, half-sine shock pulse,
according to IEC 60068-2-27
Shock (operation) 10g (bump endurance test according to EN 60068-2-29)
Processor
Processor ARM® Cortex®-A8 1x 600 MHz
Connection data
Designation COMBICON connector
Connection method Push-in connection
Conductor cross section (solid/stranded) 0.2 mm² ... 1.5 mm²
Conductor cross section [AWG] 24 ... 16
Stripping length 8 mm
Ethernet interface
Number of interfaces 2
Connection method RJ45

Ordering data and technical data
Ethernet interface
Transmission speed 100 Mbps
Transmission length Max. 100 m
Supported protocols Modbus/TCP, HTTPS
RS-485 interface
Connection method COMBICON connector
Number of channels 1
Physical transmission method Copper
Supported protocols Modbus/RTU
Device function Masters
Service interface
Connection method USB type C, socket
Device supply
Supply voltage 24 V DC
Supply voltage range 18 V DC ... 30 V DC
Power consumption Typ. 5 W
Real-time clock
Power reserve max. 168 h
Error messages to the higher-level control or computer system

None
Protective circuit
Protection against polarity reversal, surge protection Yes

CLOUD IOT GATEWAY
Conformance with EMC directive 2014/30/EU

Immunity test in accordance with EN 61000-6-2
Electrostatic discharge (ESD) EN 61000-4-2 / Criterion B, 6 kV contact discharge, 8 kV air discharge
IEC 61000-4-2
Electromagnetic fields EN 61000-4-3 / IEC 61000-4-3 Criterion A, field strength: 10 V/m
Fast transients (burst) EN 61000-4-4/ Criterion B, 2 kV
IEC 61000-4-4
Transient surge voltage (surge) EN 61000-4-5 / Criterion B, DC supply lines: ±0.5 kV/±0.5 kV (symmetrical/asymmetrical),
IEC 61000-4-5 fieldbus cable shield: ±1 kV
Conducted interference, EN 61000-4-6/ Criterion A, test voltage 10 V
IEC 61000-4-6
Noise emission test according to EN 61000-6-3 Class B
Approvals
You can find the current approvals at phoenixcontact.net/products.

Technical appendix
A Technical appendix
A1 Troubleshooting and frequently asked questions

(FAQs)
Information on troubleshooting and answers to frequently asked questions (FAQs) can be

found in the PLCnext community, under plcnext-community.net.

CLOUD IOT GATEWAY
B Appendix for document lists
B1 List of figures
Section 3
Figure 3-1: Connection and operating elements of the IoT gateway ..................... 13
Figure 3-2: Printing ............................................................................................... 14
Figure 3-3: Diagnostic and status indicators ......................................................... 15
Figure 3-4: Reset button ....................................................................................... 17
Figure 3-5: Internal basic circuit diagram .............................................................. 18
Figure 3-6: Supply plug ......................................................................................... 19
Figure 3-7: Ethernet interface and pin assignment ................................................ 20
Figure 3-8: Service interface (USB type C) ........................................................... 21
Figure 3-9: RS-485 interface ................................................................................. 22
Figure 3-10: CAN bus interface ............................................................................... 23
Figure 3-11: RS-232 interface ................................................................................. 24
Section 4
Figure 4-1: Mounting the IoT gateway ................................................................... 27
Section 5
Figure 5-1: Overload range with fall-back characteristic curve ............................. 31
Figure 5-2: Overload range without fall-back characteristic curve ....................... 31
Figure 5-3: Connecting a solid cable ..................................................................... 32
Figure 5-4: Connecting a stranded cable .............................................................. 32
Figure 5-5: Connecting the Internet ....................................................................... 33
Figure 5-6: Connecting the local Ethernet network ............................................... 33
Figure 5-7: Connecting a solid cable ..................................................................... 34
Figure 5-8: Connecting a stranded cable .............................................................. 35
Section 6
Figure 6-1: WBM: Login page ............................................................................... 36
Figure 6-2: WBM: "Users” menu ........................................................................... 38
Figure 6-3: WBM: “Home/Help” page ................................................................... 38
Figure 6-4: WBM: “Home/Profile” page ................................................................. 39

List of figures
Figure 6-5: WBM: “Home/Journal” page ............................................................... 41

Figure 6-6: WBM: “Home” page ............................................................................ 44
Figure 6-7: WBM: “Create connector” window ...................................................... 46
Figure 6-8: Connections on the “Home” page ....................................................... 46
Figure 6-9: WBM: “Home/Connectors” page ........................................................ 47
Figure 6-10: WBM: “Home/Connectors” page, “Connector settings” area of a
connection with Modbus/TCP protocol ............................................... 48
Figure 6-11: WBM: “Home/Connectors” page, “Connector logs” area .................... 51
Figure 6-12: WBM: “Home/Connectors” page, “Metric list” area ............................. 52
Figure 6-13: WBM: “Create metric” window ............................................................ 54
Figure 6-14: WBM: Metric settings .......................................................................... 55
Figure 6-15: WBM: “Settings” menu ........................................................................ 59
Figure 6-16: WBM: “Home/Settings” page, “Info” tab .............................................. 59
Figure 6-17: WBM: “Home/Settings”, “Users” tab ................................................... 60
Figure 6-18: WBM: “Create user” window ............................................................... 62
Figure 6-19: WBM: “Home/Settings” page, “Network” tab ....................................... 64
Figure 6-20: WBM: “Home/Settings/Network” page,
“Network interface eth0“ area ............................................................. 65
“Network interface eth1“ area ............................................................. 66
“Nameserver Settings” area ................................................................ 68
Figure 6-23: WBM: “Home/Settings/Network” page, “Proxy” area .......................... 69
Figure 6-24: WBM: “Home/Settings” page, “Time” tab ............................................ 71
Figure 6-25: WBM: “Home/Settings” page, “Security” tab ....................................... 72
Figure 6-26: WBM: “Home/Settings/Security” page, “Access method” tab ............. 73
Figure 6-27: WBM: “Home/Settings/Security” page,
“Upload X.509 certificate” area ........................................................... 74
Figure 6-28: WBM: “Home/Settings/Security” page,
“Generate self-signed X.509 certificate” area ..................................... 76
Figure 6-29: WBM: “Home/Settings” page, “Buffers” tab ........................................ 78
Figure 6-30: WBM: “Home/Settings” page, “Import/Export” tab .............................. 81
Figure 6-31: WBM: “Home/Settings” page, “Update” tab ........................................ 82
Figure 6-32: WBM: “Home/Settings” page, “Reset” tab .......................................... 83
Figure 6-33: WBM: “Home/Settings” page, “Restart” tab ........................................ 84

CLOUD IOT GATEWAY
Section 7
Figure 7-1: PROFICLOUD solution “TSD Device Manager” .................................. 85
Figure 7-2: “Appliances” page ............................................................................... 86
Figure 7-3: “Create Appliance” dialog ................................................................... 86
Figure 7-4: “Appliances / Name of the appliance” page ........................................ 87
Figure 7-5: Grafana: Homepage ........................................................................... 88
Figure 7-6: Grafana: “Home” ................................................................................. 88
Figure 7-7: Grafana: “New Dashboard” page ........................................................ 89
Figure 7-8: Grafana: Example graph; Edit Panel Title ........................................... 89
Figure 7-9: Grafana: Selecting the metric to be displayed ..................................... 90
Figure 7-10: Grafana: Graphical display of the selected metric ............................... 90
Section 8
Figure 8-1: Removing the cable ............................................................................ 91
Figure 8-2: Removing the IoT gateway ................................................................. 92

List of tables
B2 List of tables
Section 3
Table 3-1: Diagnostic and status indicators of the IoT gateway ............................ 15
Table 3-2: Terminal point assignment of the supply connector ............................. 19
Table 3-3: Terminal point assignment of the RS-485 interface ............................. 22
Table 3-4: Terminal point assignment of the CAN bus interface ........................... 23
Table 3-5: Terminal point assignment of the RS-232 interface ............................. 24
Section 6
Table 6-1: Possible action/event filters of the event history .................................. 43

CLOUD IOT GATEWAY
B3 Index
C Mounting
COMBICON connector ......................................... 28
Checking the delivery.................................................. 11
IoT gateway........................................................... 27
Components
Safety instructions ................................................. 25
Connection and operating element........................ 13
Printing .................................................................. 14
Connection O
Internet .................................................................. 33 Open source software
Local Ethernet network.......................................... 33 Licensing information ............................................ 12
Power supply......................................................... 32 Requesting source code ....................................... 12
RS-485, CAN bus and RS-232 participants........... 34 Ordering data.............................................................. 95
P
D Parameterization memory ........................................... 18
Device defect .............................................................. 93 Power supply without fall-back characteristic curve .... 30
Device replacement .................................................... 93 PROFICLOUD
Diagnostic and status indicators ................................. 15 Graphically displaying metrics in Grafana ............. 88
Disposal ...................................................................... 94 Metrics overview ................................................... 87
Registering the IoT gateway.................................. 85
E
Ethernet interface........................................................ 20 R
Removal
F COMBICON connectors........................................ 92
Ethernet connectors .............................................. 92
Fall-back characteristic curve...................................... 31
IoT gateway........................................................... 92
FAQs........................................................................... 99
Foreseeable misuse...................................................... 7
Repair ......................................................................... 93
Reset button ............................................................... 17
I
Intended use ................................................................. 7
S
Interfaces
Safety notes .................................................................. 7
CAN bus interface ................................................. 23
Storage ....................................................................... 10
Ethernet................................................................. 20
Supply plug ................................................................. 19
RS-232 interface ................................................... 24
Supply voltage
RS-485 interface ................................................... 22
Dimensioning the voltage supply........................... 30
Service interface (USB type C).............................. 21
Internal basic circuit diagram....................................... 18
T
M Take-back ................................................................... 94
Technical data ............................................................ 96
Maintenance ............................................................... 93
Transport .................................................................... 10
Modifications................................................................. 7
Troubleshooting .......................................................... 99

Index
U
Unauthorized network access ....................................... 8
Unpacking................................................................... 11
W
WBM
Advanced settings................................................. 59
Establishing a connection...................................... 36
Event history.......................................................... 41
Login ..................................................................... 36
Logout ................................................................... 84
Start page.............................................................. 44
User preferences................................................... 38

CLOUD IOT GATEWAY

Please observe the following notes
General terms and conditions of use for technical documentation
Phoenix Contact reserves the right to alter, correct, and/or improve the technical
documentation and the products described in the technical documentation at its own
discretion and without giving prior notice, insofar as this is reasonable for the user. The
same applies to any technical changes that serve the purpose of technical progress.
The receipt of technical documentation (in particular user documentation) does not
constitute any further duty on the part of Phoenix Contact to furnish information on
modifications to products and/or technical documentation. You are responsible to verify the
suitability and intended use of the products in your specific application, in particular with
regard to observing the applicable standards and regulations. All information made
available in the technical data is supplied without any accompanying guarantee, whether
expressly mentioned, implied or tacitly assumed.
In general, the provisions of the current standard Terms and Conditions of Phoenix Contact
apply exclusively, in particular as concerns any warranty liability.
This manual, including all illustrations contained herein, is copyright protected. Any
changes to the contents or the publication of extracts of this document is prohibited.
Phoenix Contact reserves the right to register its own intellectual property rights for the
product identifications of Phoenix Contact products that are used here. Registration of such
intellectual property rights by third parties is prohibited.
Other product identifications may be afforded legal protection, even where they may not be
indicated as such.
PHOENIX CONTACT 107 / 108

108
How to contact us
Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be
found on the Internet at:
phoenixcontact.com
Make sure you always use the latest documentation.
It can be downloaded at:
phoenixcontact.net/products
Subsidiaries If there are any problems that cannot be solved using the documentation, please contact
your Phoenix Contact subsidiary.
Subsidiary contact information is available at phoenixcontact.com.
Published by PHOENIX CONTACT GmbH & Co. KG
Flachsmarktstraße 8
32825 Blomberg
GERMANY
PHOENIX CONTACT Development and Manufacturing, Inc.
586 Fulling Mill Road
Middletown, PA 17057
USA
Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to:
tecdoc@phoenixcontact.com
108 / 108 PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany
phoenixcontact.com

Um en Cloud Iot Gateway 108450 en 01

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Um en Cloud Iot Gateway 108450 en 01

Cargado por

Copyright:

Formatos disponibles

Startup and operation of the IoT gateway

CLOUD IOT GATEWAY

UM EN CLOUD IOT GATEWAY, Revision 01 2018-06-20

This user manual is valid for:

Designation Version Order No.

PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany

2 From transport to unpacking ....................................................................................................10

3 Description of the IoT gateway .................................................................................................12

4 Mounting hardware ..................................................................................................................25

108450_en_01 PHOENIX CONTACT 3 / 108

5 Connecting and wiring hardware ..............................................................................................29

6 Web-based management (WBM) ............................................................................................36

7 Transmitting sensor and process data to the PROFICLOUD ...................................................85

8 Removing hardware .................................................................................................................91

4 / 108 PHOENIX CONTACT 108450_en_01

8.2 Removing cables................................................................................................. 91

9 After usage ..............................................................................................................................93

10 Ordering data and technical data .............................................................................................95

B Appendix for document lists....................................................................................................100

108450_en_01 PHOENIX CONTACT 5 / 108

1 For your safety

1.1 Identification of warning notes

Here you will find additional information or detailed sources of information.

1.2 Qualification of users

6 / 108 PHOENIX CONTACT 108450_en_01

1.3 Field of application of the product

1.3.1 Intended use

1.3.2 Foreseeable misuse

1.4 Safety notes

108450_en_01 PHOENIX CONTACT 7 / 108

NOTE: Risk of unauthorized network access

NOTE: Electrostatic discharge!

NOTE: Device damage due to polarity reversal

NOTE: Electrical damage

NOTE: Device failure

NOTE: Component breakage and/or short circuit

8 / 108 PHOENIX CONTACT 108450_en_01

NOTE: Device failure

NOTE: Property damage due to impermissible load

NOTE: Device failure

The device is automatically grounded (FE) when it is snapped onto a grounded

108450_en_01 PHOENIX CONTACT 9 / 108

2 From transport to unpacking

10 / 108 PHOENIX CONTACT 108450_en_01

2.3 Checking the delivery

Scope of supply IoT gateway CLOUD IOT GATEWAY

NOTE: Electrostatic discharge!

NOTE: Property damage due to noncompliance with ESD notes

108450_en_01 PHOENIX CONTACT 11 / 108

3 Description of the IoT gateway

3.1 General description

3.2 Licensing information on open source software

3.3 Requesting source code

12 / 108 PHOENIX CONTACT 108450_en_01

3.4 Components of the IoT gateway

3.4.1 Connection and operating elements

108450_en_01 PHOENIX CONTACT 13 / 108

POWER RS232 CAN

CLOUD IOT GATEWAY

Mac.: Addr. 00.A0.45.9D13.BC

Serial No. 0123456789

RS485 ETH2 Local ETH1 Internet

14 / 108 PHOENIX CONTACT 108450_en_01

3.5 Diagnostic and status indicators