Siemens MindConnect IoT2040 - Page 36

"protocol": "Name of the protocol",
"protocolData": { },
"readCycleInSeconds": "Value"
},
"description": "",
"dataPoints": [
{
"id": "a37d9e1fee6b4",
"name": "DatapointName",
"description": "-",
"unit": "Unit",
"type": "Type",
"customData": {
"dataPointData": { }
}
}
]
}
The above key-value pairs are important for the body, if missing any key-value pair
will result in configuration failure.
Each protocol has it's unique representing its protocol specific fields and
field for representing it's unique datapoint configuration. In order to get the
successful configuration for each one of the protocol, the free formatted parts of the body needs
to be a valid json. Otherwise, the configuration will be failed.
protocolData dataP
ointData
The below given an example of how to configure a datasource with one datapoint for S7
protocol:
The below json content can be changed as required, do not depend on it strictly.
The free formatted fields "protocolData" and "dataPointData" has a specific
configuration to S7 protocol.
{
"name": "S7DS",
"customData": {
"protocol": "S7",
"protocolData": {
Configuring data in Asset Manager
3.7 Configuring MindConnect IoT2040 using API
MindConnect IoT2040
System Manual 8/2023 36