![]()
Contents
Cirrus Link Resources
Cirrus Link Website![]()
Contact Us (Sales/Support)![]()
Forum![]()
Cirrus Link Modules Docs for Ignition 7.9.x![]()
Inductive Resources
Ignition User Manual![]()
Knowledge Base Articles![]()
Inductive University![]()
Forum![]()
...
| Code Block |
|---|
{
"_unmodeleddata": {
"topic": {
"namespace": "spBv1.0",
"edgeNodeDescriptor": "G1/E1",
"groupId": "G1",
"edgeNodeId": "E1",
"deviceId": "D1",
"type": "DBIRTH"
},
"payload": {
"timestamp": 1638223073192,
"metrics": [
{
"name": "T1",
"timestamp": 1638223073192,
"dataType": "Int32",
"metaData": {},
"properties": {
"Quality": {
"type": "Int32",
"value": 192
}
},
"value": 12
}
],
"seq": 1
}
},
"_eventtype": "Telemetry",
"_timestamp": "2021-11-29T21:57:54.098Z"
} |
The first message shows the 'NBIRTH' message which is an indication that the Sparkplug Edge Node has come online. The second message is a Sparkplug DBIRTH message denoting that a Sparkplug Device has come online along with its 'metrics' or tags, their metadata, and values. In this case we only had a single tag so that is all that is included in the payload.
Because Azure Injector is driven by tag change events, try writing a '10' to the T1 tag. This should result in a new DDATA message as shown below.
| Code Block |
|---|
{
"_unmodeleddata": {
"topic": {
"namespace": "spBv1.0",
"edgeNodeDescriptor": "G1/E1",
"groupId": "G1",
"edgeNodeId": "E1",
"deviceId": "D1",
"type": "DDATA"
},
"payload": {
"timestamp": 1638223663812,
"metrics": [
{
"name": "T1",
"timestamp": 1638223662800,
"dataType": "Int32",
"value": 10
}
],
"seq": 2
}
},
"_eventtype": "Telemetry",
"_timestamp": "2021-11-29T22:07:43.998Z"
} |