EasyManua.ls Logo

Siemens MindConnect IoT2040 - Page 52

Siemens MindConnect IoT2040
126 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
The name field in body must be same as the browseName of the field which
will be collected in the OPC UA Server. It is case-sensitive.
Name for "Event Type" needs to be unique
The type field must be STRING for all data types.
The scope field should always be given as Local unless a particular reason is
required to make it "Public".
The field with name Message is the static field and it is not included to custom
event types. It is needed to be added as an extra field.
The fields Time, Severity and SourceName in the Event type are reserved fields
and should not be created as extra fields.
4.4 Overview of Modbus TCP protocol for MindConnect IoT2040
Industrial IoT supports the Modbus protocol for the MindConnect IoT2040. You can select the
protocol type Modbus TCP while adding a new data source in Asset Manager.
Modbus configuration
The Modbus configuration view is only visible after a successful onboarding of the
MindConnect IoT2040. The MindConnect IoT2040 Version must be higher than
V3.3.0.2.
The following picture shows the protocol selection in Asset Manager:
Configuring protocols
4.4 Overview of Modbus TCP protocol for MindConnect IoT2040
MindConnect IoT2040
System Manual 8/2023 52

Table of Contents

Other manuals for Siemens MindConnect IoT2040

Related product manuals