Post by hermsen on Ticket #97: Allow correct publishing of Multiple Device Data discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: pending --> closed
Last updated: 2021-08-10
Post by i-campbell on Ticket #11: FB_Payload discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -22,17 +22,17 @@ [x] [x] [x] [x] Payload.metrics[].metadata.md5 [x] [x] [x] [x] Payload.metrics[].metadata.description Payload.metrics[].metadata.extensions[] //none -[x] [x] [x] [ ] Payload.metrics[].properties.keys[] -[x] [x] [x] [ ] Payload.metrics[].properties.values[].type -[x] [x] [x] [ ] Payload.metrics[].properties.values[].is_null -[x] [x] [x] [ ] Payload.metrics[].properties.values[].int_value -[x] [x] [x] [ ] Payload.metrics[].properties.values[].long_value -[x] [x] [x] [ ] Payload.metrics[].properties.values[].float_value -[x] [x] [x] [ ] Payload.metrics[].properties.values[].double_value -[x] [x] [x] [ ] Payload.metrics[].properties.values[].boolean_value -[x] [x] [x] [ ] Payload.metrics[].properties.values[].string_value -[x] [x] [x] [ ] Payload.metrics[].properties.values[].propertyset_value. //(RECURSIVE PROPERTIES) -[x] [x] [x] [ ] Payload.metrics[].properties.values[].propertysets_value.propertyset[]. //(RECURSIVE PROPERTIES) +[x] [x] [x] [x] Payload.metrics[].properties.keys[] +[x] [x] [x] [x] Payload.metrics[].properties.values[].type +[x] [x] [x] [x] Payload.metrics[].properties.values[].is_null +[x] [x] [x] [x] Payload.metrics[].properties.values[].int_value +[x] [x] [x] [x] Payload.metrics[].properties.values[].long_value +[x] [x] [x] [x] Payload.metrics[].properties.values[].float_value +[x] [x] [x] [x] Payload.metrics[].properties.values[].double_value +[x] [x] [x] [x] Payload.metrics[].properties.values[].boolean_value +[x] [x] [x] [x] Payload.metrics[].properties.values[].string_value +[x] [x] [x] [x] Payload.metrics[].properties.values[].propertyset_value. //(RECURSIVE PROPERTIES) +[x] [x] [x] [x] Payload.metrics[].properties.values[].propertysets_value.propertyset[]. //(RECURSIVE PROPERTIES) Payload.metrics[].properties.values[].extension_value //none Payload.metrics[].properties.extensions[] //none [x] [x] [x] [x] Payload.metrics[].int_value
Last updated: 2021-08-10
Post by aliazzz on Ticket #23: Architecture discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -9,4 +9,4 @@ Optional FB_Device // Represents a single Sparkplug Device. Responsible for publishing Device Metrics -// In theory the ammount of devices is unlimited and only limited by the adress namespace and maximum message // length. We will limit the number of devices default to 32 (configurable via a library parameter) +// In theory the amount of devices is unlimited and is only limited by the adress namespace and maximum message // length. We will limit the number of devices default to 32 (configurable via a library parameter)
Last updated: 2021-08-10
Post by i-campbell on Ticket #33: 50% of FB/Function will need a Unit Test discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Milestone: MVP EoN --> 1.0.0.0: EoN
Last updated: 2021-08-10
Post by aliazzz on Ticket #5: FB_EoN_Node discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -1,4 +1,6 @@ This FB should form the base for every Sparkplug B device. + +An implementation can be made after the IEC "Google Protobufs" serialisation has been written It bridges between the MQTT Broker and device(s), sensor(s) and IO(s) Milestone: 1.0 --> 2.0
Last updated: 2021-08-10
Post by aliazzz on Ticket #55: How do we Implement #PublishInterval / PublishRate? discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
This ticket will be pushed into the trunk within the next day
Last updated: 2021-08-10
Post by hermsen on Ticket #16: Implement SparkPlugB Device discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -16,4 +16,4 @@ * [x] v1.1.x.x solution implements the basis for a List of Devices * [x] V1.3.x.x solution allows for multiple devices and DDATA -* [ ] V1.7.x.x solution can receive, digest and follow up DCMD's +* [x] V1.4.x.x solution can receive, digest and follow up DCMD's // Standard DCMD's digestion has been implemented
Last updated: 2021-08-10
Post by i-campbell on Ticket #119: FB_RemoteEdge discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed assigned_to: i-campbell
Last updated: 2021-08-10
Post by hermsen on Ticket #93: Refining the state machine(s) discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: accepted --> pending
Last updated: 2021-08-10
Post by hermsen on Ticket #94: (Bd)SeqNum flow control issue's discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -2,13 +2,6 @@ The Device is allowed to send DDATA payloads (by/through command of the EoN) It seems that the DDATA payloads are tagged with a SeqNum that is too high (it needs to be N, but is tagged with N+1) -This incorrect tagging (N+1) causes/triggers the Server Node to issue a DBIRTH NCMD. -This results in a Sparkplug EoN Node that is in a continuous cycle; +This incorrect tagging (N+1) causes/triggers the Server Node to issue a DBIRTH NCMD. - NBIRTH, - NDATA, - DBIRTH, - DDATA, - NCMD-ReBirth (next step is NBIRTH again) - Improve "assigning of seqnums to payloads" by implementing a mechanism to tag payloads "just in time" with a correct seqnum. This ticket also has a certain relation with "Improve control of/over/with statemachine [#93]"
Last updated: 2021-08-10
Post by aliazzz on Ticket #32: FB_MQTT_PubSub Considerations discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> pending
Last updated: 2021-08-10
Post by aliazzz on Ticket #52: FB_MQTT: PublishMessageSize is falsely calculated around line 32 discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
labels: FB_MQTT: --> status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #70: MQTT: Subscribers outputting "Client not connected to broker" discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
labels: MQTT --> status: open --> closed
Last updated: 2021-08-10
Post by aliazzz on Ticket #52: FB_MQTT: PublishMessageSize is falsely calculated around line 32 discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
solved in v0.0.0.21
Last updated: 2021-08-10
Post by aliazzz on Ticket #1: Create Introductionpage discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Will add improved topics and payloads explanation; Here allready a little sum up of what metrics can do for us; each EoN node can share data on a broker via a set of pre-defined topic rules. The topics follow these pre defined rules while they are dynamic, when your infrastucture changes, the topics will change along. If your infrastructure grows, the topics grow accordingly, if your infrastructure shrinks, your topics shrink accordingly. Each message consists of a single Topic in the form of a hierarchy and a payload which consists of one or several metrics and its accompanying metadata. The Node decides what payload information will sent the broker (and thus shared to all other clients in the network which are subscribed) and wether this information is refreshed in a timely fashion or on change of the data. So, it is up to the EoN node device how much information and what kind of meta data of the information is shared! To provide for such flexibility, Metrics are highly flexible by nature and contain a way to expose good quality metadata and is therefore useful for many different use-cases and scenario's. For instance providing information about the pumps, are they on or off, do they have alarms. What kind of alarm, the pumpflow, the pumpcurrent, pumptorque,the VFD speed, vfd frequency etc etc etc.Evey device can have its own topic and have its own information and metadata. Since data can be shared in a timely manner or on data change we can send a report every hour or on the moment the pump sitches on or off.
Last updated: 2021-08-10
Post by aliazzz on Ticket #39: FB_SparkplugB_SimpleEncoder discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
This Ticket is sufficiently closed Any bugs will receive their own ticket
Last updated: 2021-08-10
Post by i-campbell on Ticket #11: FB_Payload discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
[r539]
Last updated: 2021-08-10
Post by i-campbell on Ticket #34: Implement basic metrics for now discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Milestone: MVP EoN --> 1.0.0.0: basic protobufs
Last updated: 2021-08-10
Post by hermsen on Ticket #106: AWS IoT Core Support discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
In v1.3.3.0, which is under development as this posted, the Mqtt client is upgraded to v1.0.2.0. This means this client will be the most recent version as shipped with IIoT SL v1.0.0.3. This Mqtt client will allow for a broader acceptance of TLS connections so it should be capable of connection with AWS without using the AWS client wrapper as part of the same IIoT library. We will release an intermediate version as a tag for easy public download very soon. Stay tuned.
Last updated: 2021-08-10
Post by i-campbell on Ticket #68: EoN: repeatedly publising NDATA discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Owner: aliazzz --> h-hermsen
Last updated: 2021-08-10
Post by aliazzz on Ticket #16: Implement SparkPlugB Device discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #93: Refining the state machine(s) discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: pending --> closed
Last updated: 2021-08-10
Post by aliazzz on Ticket #55: How do we Implement #PublishInterval / PublishRate? discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -1,13 +1,7 @@ PublishInterval / PublishRate is default set to 5000 ms. This means we cannot publish "updates" any faster then each 5000 ms. -How should we implement this? +After some debate we decided on the following mechanism: -1) For this to work we have to prevent NDATA or DDATA data to get sent immediately on-change and "buffer" all incoming changes into the encoding list until the PublishInterval expires. If the interval expires we can encode the list into a blob which contains all changes from/during the last interval period and send it. - -2) Some readily available mechanism via the MQTT Publisher? (haven't looked for it, but cannot remember its there either) - -3) Some other mechanism? - -I think 1 is the most likely candidate unless someone has a better/other idea offcourse! - +We have a timer, it sets itself as soon as we have sent data and after T#PublishInterval it resets itself. If new data is detected during timer countdown, we "buffer" it. +If the timer has expired we can send data immediately and the timer sets itself again after this action. So, the timer "blocks" sending of data during countdown.
Last updated: 2021-08-10
Post by hermsen on Ticket #89: EoN: Digest NCMD discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
labels: EoN, NCMD --> status: open --> closed
Last updated: 2021-08-10