Milestone
- 3.0.0.0: SparkplugB Peer-2-peer Edge Node
- 9.9.9.9: Backlog
- 2.0.0.0: Example
- 2.0.0.0: Device
- 2.0.0.0: TLS
- 2.0.0.0: Protobufs full
- 3.0.0.0 Full Feature Product (FFP)
- 2.0.0.0 Standard Feature Product (SFP)
- 3.0.0.0: High Availability
- 2.0.0.0: Edge
- 3.0.0.0 Historical Values
Searches
Help
#91 Protobufs: support communicating to buggy implementations
Due to a bug in eclipse Tahu, most current Sparkplug Implementations cannot parse correctly formed Uint32 Metrics, Uint32 Parameters, Uint32 PropertyValues nor Uint32 DataSetValues.
It is not possible to communicate to devices with the buggy implementation at the same time as communicating according to the specification. As such we need a toggle to "conform to spec" or "work around Uint32 bugs in certain Sparkplug implementations".
Ignition MQTT Engine currently exhibits this bug (MQTT Engine 4.0.5 (b2020062917))
As workaround, don't use Uint32, use Uint64.
Perhaps a warning can be given in the log if any Uint32s are detected.
Implemented in r597.
GVL_sparkplugB.IWantBuggyUInt32s : BOOL; controls the behaviour
The encoding for Parameters, PropertyValues, DataSetValues is not yet complete, so leaving this issue open until it is complete.
Parameters and Property values are done.
Dataset values are more complex, as the data type is not stored with the data value.
I am not even sure if the data type is mandatory.
The other idea is for the bugginess to be handled at the point of adding the data type.
Is this still valid or has eclipse solved this?