Hilscher Sensoredge field User manual

User manual

sensorEDGE FIELD

Hilscher Gesellschaft für Systemautomation mbH

www.hilscher.com

Table of contents 2/172

Table of contents

1 Introduction .............................................................................................................................. 5

1.1 About this document ........................................................................................................5

1.1.1 Description of the contents ...............................................................................5

1.1.2 List of revisions ................................................................................................. 5

1.1.3 Conventions in this document........................................................................... 6

1.2 Terms and abbreviations..................................................................................................7

1.3 Brief description ...............................................................................................................8

1.3.1 Overview ........................................................................................................... 8

1.3.2 Key features hardware...................................................................................... 8

1.3.3 Key features software ....................................................................................... 9

1.3.4 Limitations....................................................................................................... 10

1.4 netFIELD OS: Industrial IoT Operating System .............................................................11

2 Safety ...................................................................................................................................... 14

2.1 Intended use ..................................................................................................................14

2.2 General note ..................................................................................................................14

2.3 Personnel qualification...................................................................................................14

2.4 Modification reserved.....................................................................................................14

2.5 Safety instructions to avoid personal injury....................................................................15

2.6 Safety instructions to avoid device damage...................................................................15

2.7 Labeling of safety messages..........................................................................................16

3 Hardware description ............................................................................................................ 17

3.1 Device overview.............................................................................................................17

3.2 Interfaces .......................................................................................................................19

3.2.1 Supply voltage ................................................................................................19

3.2.2 Ethernet connector.......................................................................................... 20

3.2.3 IO-Link Master ................................................................................................21

3.3 LEDs ..............................................................................................................................22

3.3.1 SYS (System) LED .........................................................................................22

3.3.2 CLD (Cloud) LED ............................................................................................ 22

3.3.3 EDG (Edge) LED ............................................................................................24

3.3.4 Power supply LEDs......................................................................................... 26

3.3.5 Ethernet LEDs................................................................................................. 26

3.3.6 IO-Link Port Status LEDs................................................................................ 27

3.4 Block diagram ................................................................................................................28

4 Commissioning and first steps ............................................................................................ 29

4.1 Overview ........................................................................................................................29

4.1.1 Standard Docker user ..................................................................................... 29

4.1.2 netFIELD Cloud user ......................................................................................30

4.2 Hardware installation......................................................................................................31

4.2.1 Before you begin............................................................................................. 31

4.2.2 Mounting ......................................................................................................... 31

4.2.3 Power supply requirements ............................................................................33

4.2.4 Connecting cables ..........................................................................................34

4.3 Login to Local Device Manager......................................................................................36

4.4 Deploy basic containers.................................................................................................40

sensorEDGE FIELD | User manual

Table of contents 3/172

4.5 netFIELD Cloud user......................................................................................................41

4.5.1 Onboard device in netFIELD Cloud ................................................................ 41

4.5.2 Deploy containers via netFIELD Portal ........................................................... 51

4.6 IO-Link configuration......................................................................................................55

5 Local Device Manager ........................................................................................................... 58

5.1 Overview ........................................................................................................................58

5.2 System ...........................................................................................................................60

5.3 Networking .....................................................................................................................63

5.3.1 Overview ......................................................................................................... 63

5.3.2 Firewall............................................................................................................ 68

5.3.3 Network Proxy settings ................................................................................... 77

5.4 Networking Services ......................................................................................................83

5.5 Onboarding (and offboarding)........................................................................................83

5.6 Standard Docker ............................................................................................................86

5.7 IoT Edge Docker ............................................................................................................93

5.8 Accounts ........................................................................................................................98

5.9 Certificate.....................................................................................................................101

5.10 General Settings ..........................................................................................................102

5.10.1 Overview ....................................................................................................... 102

5.10.2 Web Server (Port) Settings ........................................................................... 102

5.10.3 Default MQTT Client Settings ....................................................................... 104

5.10.4 Docker Network Settings ..............................................................................106

5.10.5 Remote Access............................................................................................. 110

5.11 Terminal .......................................................................................................................112

5.12 System Update.............................................................................................................113

5.12.1 Operating System ......................................................................................... 113

5.12.2 netX 90 Firmware.......................................................................................... 116

5.13 Logs .............................................................................................................................117

5.14 IO-Link Configurator.....................................................................................................118

5.14.1 Overview ....................................................................................................... 118

5.14.2 IO-Link Configurator Dashboard ................................................................... 119

5.14.3 Connected Device......................................................................................... 123

5.14.4 Attachments .................................................................................................. 130

6 Embedded OPC UA Server ................................................................................................. 135

6.1 Overview ......................................................................................................................135

6.2 OPC UA information model..........................................................................................136

6.3 Accessing OPC UA Server via external client (for testing) ..........................................140

6.3.1 Overview ....................................................................................................... 140

6.3.2 Configure port forwarding on Firewall page .................................................. 141

6.3.3 Configure port forwarding in Linux Terminal ................................................. 145

6.3.4 Connect to server and browse nodes ........................................................... 146

6.3.5 Example of acyclic call via ReadISDU .......................................................... 149

7 Device recovery ................................................................................................................... 151

8 Technical data ...................................................................................................................... 152

9 Decommissioning, dismounting and disposal ................................................................. 156

sensorEDGE FIELD | User manual

Table of contents 4/172

10 Appendix............................................................................................................................... 157

10.1 IO-Link event codes .....................................................................................................157

10.1.1 IO-Link Master Event Codes......................................................................... 157

10.1.2 IO-Link Device Event Codes (common)........................................................ 158

10.2 Useful CLI commands and parameters in Terminal.....................................................160

10.2.1 Network Manager.......................................................................................... 160

10.2.2 Show interface status.................................................................................... 160

10.2.3 Activate interface ..........................................................................................160

10.2.4 Manage Standard Docker ............................................................................. 160

10.2.5 Docker Compose support for Standard Docker environment ....................... 160

10.2.6 Manage IoT Edge Docker ............................................................................. 160

10.2.7 External storage support using iSCSI ........................................................... 161

10.2.8 Enable/disable SSH Daemon (release port 22) ............................................ 161

10.2.9 Follow the system log via terminal CLI .........................................................161

10.3 Registered Trademarks................................................................................................162

10.4 Legal notes...................................................................................................................163

List of figures ....................................................................................................................... 168

List of tables......................................................................................................................... 171

Contacts................................................................................................................................ 172

sensorEDGE FIELD | User manual

Introduction 5/172

1 Introduction

1.1 About this document

1.1.1 Description of the contents

This user manual describes the sensorEDGE FIELD device (NFS-M8-QM-

D2-N16/NFLD) from Hilscher (for better readability also just named

“sensorEDGE” in the following chapters). It contains a description of the

device hardware, its technical data and a description of its web-based

configuration GUI (Local Device Manager).

It also provides instructions on how to commission the device “in the field”

and how to “onboard” it in the netFIELD Cloud for remote management

(optional use case for users/subscribers of the netFIELD Cloud).

1.1.2 List of revisions

Index Date Author Revision

1 01-20-2022 MKE Document created

Table1: List of revisions

sensorEDGE FIELD | User manual

Introduction 6/172

1.1.3 Conventions in this document

Notes, instructions and results of operating steps are marked as follows:

Notes

Important:

Note:

Instructions

1. Operational step

ØInstruction

2. Operational step

ØInstruction

Results

Intermediate result

Final result

sensorEDGE FIELD | User manual

Introduction 7/172

1.2 Terms and abbreviations

Term Description

Container Executable software package including all components

needed to run an application on a Docker engine.

Docker Software for isolating applications using container

virtualization. Docker enables the creation and operation of

Linux containers. netFIELD OS provides two Docker runtime

environments: IoT Edge Docker and Standard Docker. The

IoT Edge Docker environment is managed remotely from the

netFIELD Platform.

IIoT Industrial Internet of Things.

IT network Information technology network.

Microsoft Azure IoT Edge Features a deployable Docker-based runtime along with a

public cloud-hosted backend logic for remote device servicing.

It is the basic framework of the evolved netFIELD device-to-

cloud communication infrastructure.

netFIELD App netFIELD application Docker container from Hilscher. Runs in

the IoT Edge Docker or Standard Docker of the netFIELD OS

on the netFIELD Edge.

netFIELD Cloud Internet-hosted platform providing APIs for cloud-to-cloud and

cloud-to-edge communication. Based on Microsoft Azure IoT

Edge. Consists of the netFIELD Platform (backend) and the

netFIELD Portal (web-based user interface/frontend). The

netFIELD Cloud is also referred to as netFIELD.io

netFIELD Edge Devices or systems running the netFIELD OS, providing

connectivity to the netFIELD Cloud. Cloud connectivity is

based on Microsoft Azure IoT Edge.

netFIELD.io Internet-hosted platform providing APIs for cloud-to-cloud and

cloud-to-edge communication. Based on Microsoft Azure IoT

Edge. Consists of the netFIELD Platform (backend) and the

netFIELD Portal (web-based user interface/frontend).

netFIELD.io is also referred to as netFIELD Cloud.

netFIELD OS Cross-platform capable operating system providing

connectivity to the netFIELD Cloud. Cloud connectivity is

based on Microsoft Azure IoT Edge.

netFIELD Platform Backend of the netFIELD Cloud, providing APIs for cloud-to-

cloud and cloud-to-edge communication.

netFIELD Portal Web-based user interface (frontend) of the netFIELD Cloud.

netX 90 SoC SoC (System on a Chip) for OT networks with additional

support for IO-Link. Handles the IO-Link protocol in the

sensorEDGE device along with two netIOL transceiver chips.

Also contains an OPC UA server providing an information

model of the IO-Link data.

OT network Operational technology network.

Table2: Terms and abbreviations

sensorEDGE FIELD | User manual

Introduction 8/172

1.3 Brief description

1.3.1 Overview

sensorEDGE FIELD is an IP67-rated IO-Link Master (“sensor block”) with

edge computing power. It turns IO-Link sensor data into MQTT tags and

publishes them to an MQTT broker that can run either inside the device

(default) or hosted on a remote system. In turn, applications can subscribe

to this MQTT broker in order to receive the data.

Optionally you can connect your sensorEDGE FIELD device over the

Internet to the netFIELD Cloud (https://www.netfield.io), which allows you

to manage your sensorEDGE via remote control functions from the

netFIELD Portal (which is the web-based user interface of the netFIELD

Cloud).

You can also stream MQTT messages from your sensorEDGE to 3rd party

applications via the RESTful API of the netFIELD Platform (which is the

backend of the netFIELD Cloud).

Note:

Note that connecting the sensorEDGE FIELD device to the

netFIELD Cloud requires an account/subscription for the netFIELD

Cloud services (https://www.netfield.io).

Contact your local Hilscher sales representative for information on

terms and conditions.

1.3.2 Key features hardware

·Eight IO-Link ports (Class A) for multi-sensor applications.

·IP 67 Class protected: The sensorEDGE housing block is suited for

cabinet-free installations in the field in harsh environments close to

machines.

·Ethernet connector to connect the sensorEDGE to your IT network

and/or to uplink it to the Internet (e.g. to the netFIELD Cloud).

·LED Indicators for rapid on-site visual diagnostics of the states of the

sensorEDGE and of the connected IO-Link sensors.

·24 V DC power supply

·Compact housing dimensions: 200 mm x 60 mm x 30 mm

(L x W x H)

·Drilling holes in housing for secure wall mounting for maximum

protection against vibration and shock.

sensorEDGE FIELD | User manual

Introduction 9/172

1.3.3 Key features software

·Preinstalled and non-removable netFIELD OS (netFIELD Operating

System) with Local Device Manager (web GUI) for local configuration

and administration of the sensorEDGE.

For more information on the netFIELD OS, see section netFIELD OS:

Industrial IoT Operating System [}page11].

·Deployable applications for sensor configuration, data acquisition,

processing, analytics and connectivity (to on-site enterprise systems or

to the cloud) do not run natively under the netFIELD OS, but as

containers in a Docker runtime under netFIELD OS.

netFIELD OS provides two Docker runtimes that can run simultaneously

on the device:

–IoT Edge Docker for remote and automatic deployment and

maintenance of containers. These containers are deployed (“pulled”)

and managed over the netFIELD Cloud. This requires your device to

be onboarded in the netFIELD Cloud. Note that you need an

account/subscription for the netFIELD Cloud

(https://www.netfield.io) for this.

–Standard Docker for manual and local deployment and

maintenance of containers.

These containers can be pulled from official registries like Docker

Hub (https://hub.docker.com) or from any locally hosted Docker

registry. In case you do not have an account/subscription for the

netFIELD Cloud, the standard Docker is the only way to pull and run

container applications on your device.

·Basic application containers (apps):

–IO-Link Configurator: Due to its auto-discovery and provisioning

service using the sensors’ IODD device description files, the

netFIELD App IO-Link Configurator allows you to quickly

commission connected IO-Link sensors. If the sensorEDGE is

connected to the Internet, the app automatically loads the IODD files

from the central Internet database https://ioddfinder.io-link.com

(if the IODD files are available in the database).

Else, the web interface of the IO-Link Configurator also allows you to

manually commission and configure highly sophisticated sensors.

–OPC UA IO-Link Adapter: Converts the IO-Link sensor data/

information available on the netX 90 OPC UA server into MQTT tags

and publishes them to an MQTT broker.

sensorEDGE FIELD | User manual

Introduction 10/172

·Options for users/subscribers of the netFIELD Cloud

(https://www.netfield.io):

–Remote device management and container deployment via

netFIELD Portal.

For a detailed description of the netFIELD Portal, see operating

instruction manual netFIELD Portal, DOC190701OIxxEN.

– The WebSocket interface of the netFIELD Platform allows you to

stream aggregated data for monitoring, long-term analytics or

diagnostics with your own applications via REST API

(see https://api.netfield.io/v1/documentation).

You can easily create your own and personal API key needed for

authorization with different levels of permission in the API Key

Manager of the netFIELD Portal.

–Software updates for the sensorEDGE (application containers and

netFIELD OS) can be conveniently initialized and managed via the

netFIELD Portal.

1.3.4 Limitations

IO-Link and digital I/Os

The sensorEDGE does not support:

·IO-Link actuators

·IO-Link Class B devices

·Digital input/outputs

Note:

IO-Link Class A sensors featuring additional digital inputs/outputs

(channel B at pin 2) can be connected for IO-Link communication;

however, the digital I/Os are neither evaluated nor supported by the

sensorEDGE.

Data storage life expectancy due to used NAND flash technology

The internal eMMC flash of the sensorEDGE supports approximately 25

TBW (Terabytes Written). Be aware of this limitation regarding the amount

of data and the frequency of write cycles if you plan to run applications that

need to store data on the media.

We recommend you not to run applications requiring high frequencies of

write cycles (like e.g. database applications) on the device.

sensorEDGE FIELD | User manual

Introduction 11/172

1.4 netFIELD OS: Industrial IoT Operating System

The netFIELD OS, as a part of our technology portfolio, supports scalable

field device hardware depending on the customer's use case. In order to

achieve this, applications do not run directly on the host system but instead

as containers in a Docker runtime. Our OS is very lean and only supports

the essential services required by the customer's network infrastructure.

Features

·Run containers: Containers are revolutionizing connected IoT devices,

and netFIELD OS is the perfect match to run them.

·Manage device: Manage your device locally with a web-based

interface. It is easy to administer storage, configure networks, and

more.

·Build to last: Build to survive in harsh environments like unexpected

shutdowns with security in mind.

·Easy to port: Based on a Yocto project (https://www.yoctoproject.org)

maintained Linux for easy porting to most capable device types across

various CPU architectures.

Architecture

Hilscher netFIELD OS is a secure operating system that makes it easy to

program, deploy, connect and manage Edge Devices. Hilscher netFIELD

OS extends the Linux kernel, with software libraries to securely connect

operation technology like PLC, MES, Historians, Files or other on-premise

systems with IT services like the netFIELD Portal. Our OS lets you innovate

faster embracing container technologies managed by the netFIELD Portal

from a central point or locally at the edge.

Figure1: netFIELD OS architecture

sensorEDGE FIELD | User manual

Introduction 12/172

Core services

The netFIELD OS core services include the support of hardware interfaces,

the network environment, secure communication and system logging. In

order to support the customer in setting up the gateway configuration, the

Local Device Manager is coming along with the core services. With the

open plug-in mechanism, the functionality of the Local Device Manager can

be easily extended with the help of containerized applications.

Container management

Application containers can run in the IoT Edge Docker or Standard Docker

environment and do contain business logic such as for data acquisition,

analytics, processing or connectivity to cloud or enterprise systems.

The container management provides the functionality to pull and run

containers on the device itself. Before a container can be run, its image

needs to be pulled from a certain container registry. After that the container

is created, the application can be then controlled by using the start / stop

commands or by enabling the autostart option. Also, the deletion of

containers and images is a part of container management. In order to

enable the field devices for off- and online scenarios, netFIELD OS

provides two Docker runtime environments at the same time.

The IoT Edge Docker environment is managed by the netFIELD.io platform

remotely. That is why there is no need to have direct access to the

netFIELD Device, as long as the device can hold its connection to

netFIELD.io. Administrators can be anywhere and have full management

access to the device with the stored images and have the ability to control

the application containers remotely. Otherwise, the Standard Docker can

be used locally if the netFIELD device is not connected to netFIELD.io. In

this case, the Standard Docker runtime environment can be managed by

the Local Device Manager, by the netFIELD OS command line interface or

by a web application like portainer.io, which can be deployed as container.

Figure2: netFIELD OS container management

sensorEDGE FIELD | User manual

Introduction 13/172

Inter-container communication

Application containers usually focus on the dedicated business logic in

order to avoid the development of unmaintainable software monoliths. In

this scenario, multiple containers need to work together to realize customer

use cases. Our powerful message and container-oriented architecture

provide the highest level of flexibility and reusability when implementing

customer solutions with individual requirements. This reduces IoT solution

cost in development and operation.

Figure3: netFIELD OS inter-container communication

Services supported by netFIELD OS

·Network interface configuration

·Firewall configuration (NAT, TCP/IP port management)

·HTTP(S) Proxy Server configuration

·Network storage (NFS, iSCSI) support

·Resources monitoring

·Access to netFIELD OS and Docker services via a web-terminal or over

SSH

·Standard Docker instance for locally managed containers, including

Docker Compose support

·netFIELD OS update (local/remote) support

·System and container logging

·Onboarding in netFIELD Cloud

·Secure communication to the netFIELD Cloud services

·Remote device control/access via netFIELD Cloud, protected by “four-

eyes principle”: Must be enabled in Local Device Manager

·IoT Edge Docker instance for application container managed via

netFIELD Cloud

·Selection of upstream (device-to-cloud) protocol to the netFIELD Cloud:

AMQP, AMQPWS, MQTT or MQTTWS. Note that the protocols use

different ports, which is relevant to your firewall configuration.

sensorEDGE FIELD | User manual

Safety 14/172

2 Safety

2.1 Intended use

In the first instance, sensorEDGE FIELD is an edge device for publishing

data from local IO-Link sensors to a local or remote MQTT Broker and/or to

an Internet cloud presence.

Secondly, it operates as an edge computing platform that allows to move

custom software, workloads, logic and intelligence on the device.

The sensorEDGE FIELD device complies with protection class IP 67 and is

suitable for indoor and outdoor use, e.g. in industrial automation plants.

Any use other than specified here is not permitted.

2.2 General note

To avoid personal injury or property damage to your system or to this

product, you must read and understand all instructions in this manual

before using the product.

This manual was written for the use of the product by educated personnel.

When using the product, all safety instructions and all valid legal

regulations must be obeyed. Technical knowledge is presumed.

Keep this manual for future reference.

2.3 Personnel qualification

The device may only be installed, configured, operated and removed by

qualified personnel. Job-specific technical skills for people professionally

working with electricity must be present concerning the following topics:

·Safety and health at work

·Mounting and attaching of electrical equipment

·Measurement and analysis of electrical functions and systems

·Evaluation of the safety of electrical systems and equipment

·Installing and configuring IT

2.4 Modification reserved

Changes or modifications to hardware or software of the device by the user

are not permitted.

The device does not contain any parts that are serviceable by the user.

Do not open or damage the housing.

sensorEDGE FIELD | User manual

Safety 15/172

2.5 Safety instructions to avoid personal injury

Danger of electric shock

Use only 24 V DC SELV (Safety Extra Low Voltage) or PELV (Protective

Extra Low Voltage) systems for the voltage supply of your device!

2.6 Safety instructions to avoid device damage

Risk of device destruction by exceeding allowed current

The current draw of the device’s power supply must not exceed 16 A !

Always protect the power supply with a circuit breaker or fuse. For this

purpose, use a 24 V DC / max. 16 A fuse or circuit breaker with type B trip

characteristics.

Risk of device destruction by exceeding the allowed supply voltage

The device may only be operated with the specified supply voltage of 24 V

DC (± 6 V DC). Make sure that the limits of the allowed range for the supply

voltage are not exceeded.

A supply voltage

·above the upper limit can cause severe device damage

·below the lower limit can cause malfunction of the device

·below appr. 10 V can cause a device reset

sensorEDGE FIELD | User manual

Safety 16/172

2.7 Labeling of safety messages

All safety instructions and safety messages in this document are designed

in accordance with the international safety requirements and the ANSI

Z535.6 requirements.

·The Section Safety Messages at the beginning of a chapter are

pinpointed particularly and are highlighted by a signal word according to

the degree of endangerment. The kind of danger is specified exactly by

the safety message text and optionally by a specific safety sign.

·The Integrated Safety Messages embedded in operating instructions

are highlighted by a signal word according to the degree of

endangerment. The nature of the hazard is indicated in the safety

message.

Signal words and safety signs in safety messages on personal injury

Signal word Meaning

Indicates a direct hazard with high risk, which will have as consequence

death or grievous bodily harm if it is not avoided.

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

consequence death or (grievous) bodily harm if it is not avoided.

Indicates a minor hazard with medium risk, which could have as

consequence personal injury if it is not avoided.

Table3: Signal words in safety messages on personal injury

Safety sign Sort of warning or principle

Warning of lethal electrical shock

Principle: Disconnect the power plug

Table4: Safety signs in messages on personal injury

Signal words and safety signs in safety messages on property

damage

Signal word Meaning

Indicates a property damage message

Table5: Signal words in safety messages on property damage

Safety sign Sort of warning or principle

Warning of property damage by electrostatic discharge

Table6: Safety signs in safety messages on property damage

sensorEDGE FIELD | User manual

Hardware description 17/172

3 Hardware description

3.1 Device overview

Figure4: Device overview with interfaces

sensorEDGE FIELD | User manual

Hardware description 18/172

Pos. Label/name Description For details see section

(1)  Wi-Fi/Bluetooth LED. Currently without function

(reserved for future use).

–

(2) SYS LED indicating the state of the IO-Link communication

controller

SYS (System) LED [}page22]

(3) CLD Cloud LED, by default auto-controlled by the netFIELD

OS, indicating the state of the cIoud connection.

Auto-control can be deactivated, allowing the LED to

be programmed by the user.

CLD (Cloud) LED [}page22]

(4) EDG Edge LED, by default without function. Can be

programmed by the user.

Note: If you onboard your device in the netFIELD

Cloud and deploy the netFIELD App Platform

Connector, the EDG LED will be auto-controlled by the

Platform Connector, indicating the state of the IO-Link

functionality of the device.

EDG (Edge) LED [}page24]

(5) – Mounting hole (M4 screw) for attaching the device to its

carrier. Also connection to Functional Earth (FE).

–

(6) ERR ERR LED. Currently without function (reserved for

future use)

–

(7) RUN RUN LED. Currently without function (reserved for

future use).

–

(8) X33 Ethernet LAN port (M12 connector, D-coded, female) Ethernet connector [}page20]

(9) LINK LINK LED of X33 Ethernet LAN port Ethernet LEDs [}page26]

(10) ACT Activity LED of X33 Ethernet LAN port

(11) – Removable label plate (for customized marking of

interfaces)

–

(12) X1 … X8 IO-Link port (M12 connector, A-coded, female) IO-Link Master [}page21]

(13) A Status LED of IO-Link port IO-Link Port Status LEDs [}page27]

(14) B Status LED of digital I/O channel B (not supported by

the sensorEDGE device)

(15) – Mounting hole (M4 screw) for attaching the device to its

carrier

–

(16) 2L LED indicating that auxiliary supply voltage (U2L) is

connected.

Note: The sensorEDGE does not need or use auxiliary

supply voltage (U2L).

Power supply LEDs [}page26]

(17) X21 Supply voltage connector (+24V, M12 connector, L-

coded, male)

Supply voltage [}page19]

(18) 1L LED indicating the state of the standard supply voltage

(U1L)

Power supply LEDs [}page26]

(19) – QR code for scanning the sensorEDGE ID (optional) –

(20) ID Unique ID of the sensorEDGE device

(21) Model sensorEDGE model name –

Table7: Positions on sensorEDGE FIELD

sensorEDGE FIELD | User manual

Hardware description 19/172

3.2 Interfaces

3.2.1 Supply voltage

X21 (see position (17) in section Device overview [}page17]) is the

connector for the +24 V DC standard supply voltage (U1L) load circuit 1L.

U1L / 1L supplies the power for the device itself (logic) and for the connected

IO-Link devices.

Note:

The sensorEDGE does not need or use auxiliary supply voltage

(U2L), even though the pins for the 2L auxiliary load circuit are

implemented on the device. The 1L and 2L load circuits are

galvanically isolated from each other.

Supply voltage Pin Signal Description

M12, L-coded,

male

5-pin (4 + FE)

1 1L+ +24 V DC power supply for system and sensors (U1L)

2 2L- Not used (device does not use U2L)

3 1L- Ground for U1L

4 2L+ Not used (device does not use U2L)

FE FE Functional earth

Table8: Supply voltage

For a description of the LEDs belonging to this interface, see section Power

supply LEDs [}page26].

Accessories

Use cables featuring an M12 L-coded female connector for mating; e.g. one

of the following products (other brands are also available).

Cable assemblies:

·https://shop.murrelektronik.com/en/Connection-Technology/With-

open-ended-wires/Power/M12-Power-L-coded-5pol-female-0-with-

cable-7000-P4221-9660150.html

·https://www.ifm.com/de/en/product/E12641

·https://www.phoenixcontact.com/online/portal/pi/?uri=pxc-oc-

itemdetail:pid=1414772

Connector only:

·https://b2b.harting.com/ebusiness/en/M12-Power-IDC-female-L-code-

d/21032962505

·https://b2b.harting.com/ebusiness/de/M12-Power-IDC-female-L-coded-

w-o-FE/21032962506

·https://catalog.belden.com/index.cfm?event=pd&p=PF_RKCCS5L

sensorEDGE FIELD | User manual

Hardware description 20/172

3.2.2 Ethernet connector

X33 (see position (8) in section Device overview [}page17]) is the

Ethernet port for connecting the sensorEDGE to the IT network,

respectively to the Internet.

The MAC address of the Ethernet port is imprinted on the left side of the

device housing.

Note that in the device’s state of delivery, receiving an IP address for the

Ethernet interface is set to DHCP mode and hence requires a DHCP server

running in the connected Ethernet LAN network, providing and assigning an

IP address to the device automatically.

You can configure the network settings of this port on the Networking page

of the Local Device Manager (see section Networking [}page63]).

Ethernet Pin Signal Description

M12, D-coded,

female, 4-pin

1 TX+ Transmit data, positive

2 RX+ Receive data, positive

3 TX– Transmit data, negative

4 RX– Receive data, negative

Shield FE Connected to functional earth via metal socket

(Shield)

Table9: Ethernet

For a description of the LEDs belonging to this interface, see section

Ethernet LEDs [}page26].

Accessories

Use cables featuring an M12 D-coded male connector for mating; e.g. one

of the following products (other brands are also available).

Cable assemblies:

·https://shop.murrelektronik.com/en/Connection-Technology/

Connection-cables/Data/M12-male-0-RJ45-male-0-shielded-

Ethernet-7000-44711-6590030.html

·https://b2b.harting.com/ebusiness/de/RJ45-M12-d-code-ang-

AWG22-7-PUR-0-5m/09486883018005

·https://b2b.harting.com/ebusiness/de/RJ45-M12-d-code-str-AWG22-7-

PUR-0-5m/09486896018005

·https://www.metz-connect.com/home/products/pcabling/cables-and-

wires/connection-cables-m12~e3.en.html?id=142M1D10010

·https://www.metz-connect.com/home/products/pcabling/cables-and-

wires/connection-cables-m12~e3.en.html?id=142M4D15010

Connectors only:

·https://shop.murrelektronik.com/en/Connection-Technology/Field-

wireable/Data/MOSA-M12-MALE-0-FIELD-WIREABLE-

IDC-7000-14521-0000000.html

·https://www.te.com/deu-de/product-T4111502031-000.html

·https://www.sick.com/de/en/ste-1204-g/p/p314574

sensorEDGE FIELD | User manual

This manual suits for next models

Table of contents

Popular I/O System manuals by other brands

National Instruments

National Instruments PXIe-7820 Getting started guide

Mitsubishi

Mitsubishi FX2N-4AD-TC user guide

WAGO

WAGO 750-341 manual

Ursalink

Ursalink UC1152 quick start guide

Symetrix

Symetrix SymNet Series quick start guide

Moxa Technologies

Moxa Technologies ioLogik E1500 Series Quick installation guide

National Instruments

National Instruments NI 9225 Operating instructions and specification

Smartgen

Smartgen DIN16A user manual

DMP Electronics

DMP Electronics 1154 installation guide

ABB

ABB Remote I/O RIO600 Installation and commissioning manual

Drip Drop

Drip Drop ADA-2000-E installation manual

Nav TV

Nav TV AV1LEX quick start guide

Leroy-Somer

Leroy-Somer Nidec MDX-I/O LITE Installation and commissioning manual

MicroControl

MicroControl uCAN.8.dio-BOX manual

YASKAWA

YASKAWA VIPA IM 053EC manual

GSS

GSS PHIS 1000 Assembly instruction

Beckhoff

Beckhoff EP1518-0001 Documentation

Omron

Omron GI-SMD1624 Safety precautions

hilscher sensorEDGE FIELD User manual

Popular I/O System manuals by other brands