...
MQTT Transmission Store and Forward Not Enabled
...
- Transmission connects and publishes its BIRTH
...
- The timestamp for Tag1 set at the Edge to 'now' per the Edge's system clock.
...
- Tag change events occur naturally at the Edge
...
- During this time the timestamp is always set using the tag change event time at the Edge. This results in Tag1's timestamp at Engine matching that of the Edge.
...
- Transmission loses connection.
- At this point, Engine 'stales' the tag by setting the quality to BAD_STALE and sets the timestamp of Tag1 to 'now' per the Central Gateway's system clock.
...
- The tag may or may not be changing at the Edge - Engine won't know in real time this is happening
...
- so it sets the quality of
...
- Tag1 to BAD_STALE.
...
- Transmission reconnects and publishes its BIRTH
...
- The timestamp for
...
- Tag1 set at the Edge to 'now' per the Edge's system clock.
- Assuming the quality of
...
- Tag1 at the Edge is GOOD - it will be set to GOOD at Engine.
- If the tag value had never changed at the Edge
...
- , then you would see three events with the same value, three different timestamps, and the quality go from GOOD -> BAD_STALE -> GOOD.
{"serverDuration": 115, "requestCorrelationId": "95faadbe36a3d7a8"}