Querying sensorEDGE data via netFIELD Cloud WebSocket API services
72/166
No.
Element
Description
(1)
"topic"
MQTT topic (UTF-8 coded)
(2)
"PublisherId" ID of the instance in the sensorEDGE device (i.e. the netFIELD App
OPC-UA IO-Link Adapter) that published the data to the MQTT
message bus.
(3)
"Messages"
Array of messages containing the IDs and values retrieved from the
connected sensor(s). Depends on how many sensors are connected
and enabled for publishing and how many values/data points they
provide.
Note that individual sensors and their values/data points can be
enabled/disabled for publishing in the
IO-Link Configurator
of the
Local Device Manager
.
(4)
“Timestamp”
Timestamp taken in the sensorEDGE device at the time the value was
read from the sensor.
(5)
"POI"
“Point of interest”: Unique string that specifies the sensor from which
the values are retrieved (URL-encoded).
(6)
"Payload"
Payload section containing the actual sensor values.
Table 19: Important elements in Data message
The path for accessing a certain sensor value – in this example
distance
measured by the
ifm
sensor connected to port X1 of the sensorEDGE –
thus would be:
payload.data.Messages[1].Payload.Distance
netFIELD sensorEDGE | User manual
DOC200601UM01EN | Revision 1 | English | 2021-09 | Released | Public
© Hilscher 2021
