Do you have a question about the sensorEDGE FIELD and is the answer not in the manual?
Questions and answers
Summary of Contents for hilscher sensorEDGE FIELD
Page 1
User manual sensorEDGE FIELD Hilscher Gesellschaft für Systemautomation mbH www.hilscher.com DOC211002UM01EN | Revision 1 | English | 2022-01 | Released | Public...
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 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.
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.
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.
14/172 2 Safety 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.
FIELD device if you want to run your application containers in the Standard Docker of the device (i.e. if you do not want to connect your sensorEDGE FIELD to the Internet for managing it from the netFIELD Cloud).
4.1.2 netFIELD Cloud user The following table shows the steps that you must perform in order to commission your sensorEDGE FIELD device if you are a netFIELD Cloud user/subscriber and want to manage your device from the netFIELD Cloud (https://www.netfield.io).
Note that you need to connect your sensorEDGE FIELD device temporarily to the Internet in order to allow it to “pull” the container images from the Docker Hub. If you are a netFIELD Cloud user, you can deploy these containers alternatively in the device’s IoT Edge Docker via the netFIELD Portal.
Onboard device in netFIELD Cloud 4.5.1.1 Overview If you connect the sensorEDGE FIELD device via Internet to the netFIELD Cloud (https://www.netfield.io), you can install containers and manage your sensorEDGE 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.
Ø In the API Endpoint field, enter the URL of the REST-API interface of the portal. For the Hilscher netFIELD Portal, this is: api.netfield.io If you are using a different instance of the portal, ask your portal’s system administrator for the URL.
Commissioning and first steps 52/172 Step-by-step instructions Ø Login to the netFIELD Portal. Ø Select your sensorEDGE FIELD device in the Device Manager of the netFIELD Portal. Ø In the DEVICE NAVIGATION panel select Containers and open the Available Containers tab.
In the navigation panel on the left of the screen, you can select the available “standard” management and configuration pages. Many Hilscher netFIELD application containers like the netFIELD App IO-Link Configurator or the netFIELD App Platform Connector provide their own configuration GUI (if deployed on your device), which can be selected here.
Networking Services The Networking Services page allows you to configure Wi-Fi settings of devices that support wireless communication. Since the sensorEDGE FIELD device does not support Wi-Fi, this page is currently disabled. Onboarding (and offboarding) The Onboarding page allows you to “register” your device in the netFIELD Cloud (respectively netFIELD Portal).
*.pem format to the netFIELD OS. Figure 63: Web Server Certificate page Note: The netFIELD OS contains a certificate issued by Hilscher. Note that the automatically created certificate is valid for one year. You can upload your own certificate to the netFIELD OS here. The corresponding root certificate should be rolled out on each of your PC/devices that you use for connecting to the netFIELD OS.
OS. These settings are stored in a JSON configuration file in the netFIELD OS (/etc/gateway/mqtt-config.json). By default, all Hilscher netFIELD Apps use this configuration file. Other containers (i.e. non-Hilscher application containers) that do not require their own customized MQTT client settings, can also use these settings here if the configuration file is referenced accordingly in the container image (e.g.
The “Remote Control” functions of the Portal allow you to access IP services (like e.g. HTTP(S), SSH, VNC, RDP or other TCP-based services) running on the netFIELD OS of your sensorEDGE FIELD device (or on other devices connected to a network that is accessible by the sensorEDGE FIELD device/netFIELD OS) from a remote PC via a HTTPS tunnel.
To update the operating system, proceed as follows: 1. Contact Hilscher support for instructions on how to download the *.swu update file to your local PC. 2. Upload the *.swu update file from your local PC to the device.
Figure 75: netX 90 Firmware update page To update the netX 90 firmware, proceed as follows: 1. Download the netX 90 firmware ZIP archive file from Hilscher (contact Hilscher support for instructions). 2. Upload the ZIP archive file from your local PC to the device.
Ethernet LAN interface (eth0) in the Local Device Manager. If you require a recovery of your sensorEDGE device, contact Hilscher support via email at support@hilscher.com or via contact form on https://www.hilscher.com/support/contact/.
Status of the IO-Link port (Note: Yellow is produced by switching red and green duo LED on at the same time) 8 x B (red/green/yellow) Not used Table 32: Technical data sensorEDGE FIELD IO-Link ports Category Parameter Value IO-Link Master (Class A) Specification V1.1.2...
Page 164
Liability disclaimer The hardware and/or software was created and tested by Hilscher Gesellschaft für Systemautomation mbH with utmost care and is made available as is. No warranty can be assumed for the performance or...
Page 165
Warranty Hilscher Gesellschaft für Systemautomation mbH hereby guarantees that the software shall run without errors in accordance with the requirements listed in the specifications and that there were no defects on the date of acceptance.
Page 166
The customer hereby expressly acknowledges that this document contains trade secrets, information protected by copyright and other patent and ownership privileges as well as any related rights of Hilscher Gesellschaft für Systemautomation mbH. The customer agrees to treat as confidential all of the information made available to customer by Hilscher Gesellschaft für...
Page 171
Table 30: Elements in Configuration tab of port ..............127 Table 31: Elements on Attachments page................131 Table 32: Technical data sensorEDGE FIELD ............... 152 Table 33: Technical data IO-Link ports................... 154 Table 34: OPC UA Server ...................... 155 Table 35: IO-Link Master Event Codes...................
Need help?
Do you have a question about the sensorEDGE FIELD and is the answer not in the manual?
Questions and answers