"dataSourceId": "10d9c36c-69f7-4c33-8624-f67537e142a4",
"dataPointId": "b932b9da42f04",
"protocol": "some_protocol"
}
}
}
In the below list, there are some fields which require certain data only:
Field Name Allowed Values
to OPCUA, S7
protocol OPCUA, S7
version v1.0
type datapoint-write
key mdsp-core-commandDispatcher
The following list shows the details of the commanding functionality:
If command operation fails, then the box will set the state of the job to "FAILED" indicating
some more details in the message column of the command itself. On the other hand, the
state of the job will be "EXECUTED", if the command operation succeeded. These updated
states can be checked via Deployment Workflow’s endpoint GET /instances too.
The commanding operations are executed in a chronological order, starting first from the
oldest to the newest. The execution of those commands is synchronized with the
configuration updates to avoid inconsistencies between the device side content and cloud side
content.
In order to keep the device configuration content up to date with the backend side do
not forget to click the "Apply changes" button. Otherwise, some of your commands
will get rejected by the device side, for example a command is sent for a "READ" typed
datapoint.
Boolean type is only working strictly for ‘true’ and ‘false’ values.
To Next Page
Loading...
Need help?
General