Post by aliazzz on Ticket #4: Create session state management for EoN Node discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Last updated: 2021-08-10
Post by aliazzz on Ticket #5: FB_EoN_Node discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
This ticket is sufficiently closed Any bugs will get a separate ticket.
Last updated: 2021-08-10
Post by hermsen on Ticket #91: Protobufs: support communicating to buggy implementations discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Is this still valid or has eclipse solved this?
Last updated: 2021-08-10
Post by hermsen on Ticket #115: Every type of Node will have it's seperate log (bonus kudos) discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #100: EoN state machine should return to offline when an MQTT error occurs discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Is implemented in trunk v1.3.3.5
Last updated: 2021-08-10
Post by hermsen on Ticket #15: Example project for a SCADA discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #81: Comment the Example Project discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #115: Every type of Node will have it's seperate log (bonus kudos) discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
labels: Log, Component, Node, Separate --> status: open --> closed
Last updated: 2021-08-10
Post by i-campbell on Ticket #128: new implementation of FB_EdgeMQTT client discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by aliazzz on Ticket #27: Visibility Control of Objects discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
👍
Last updated: 2021-08-10
Post by i-campbell on Ticket #32: FB_MQTT_PubSub Considerations discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
You can use the wildcards defined my MQTT, but I don't see anyway to add a list of topics. So '#' is multilevel topic subscription. '+' is single level topic subscription.
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)
status: accepted --> pending Milestone: MVP: EoN --> 1.0.0.0: basic protobufs
Last updated: 2021-08-10
Post by hermsen on Ticket #124: Replace Payload.ClaimNextFree*() with FB_Factory.Create*() discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
I think this ticket has been implemented by Ian. I'll close it. Re-open if not satisfactory
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)
Description has changed: Diff: --- old +++ new @@ -1,8 +1,8 @@ -PubSub can inform us a message has been received via pubsub.IsMessageReceived(). -PubSub can then be called to obtain the message via pubsub.getmessage(). +PubSub can inform us that a message has been received via .IsMessageReceived(). +PubSub can then be called to obtain the message via .getmessage(). The blob data which is received should be consumed by FB_Payload. -thinking aloud: +Thinking aloud: Passing a pointer/length of the blob is far superior (as no data is physically copied around) Binding a dynamic buffer is also under my consideration as an option if needed/wanted or has some unforseen advantage. Offcourse the simplest idea is the best and should be chosen. @@ -22,8 +22,6 @@ END_IF; ~~~ - -=> pubsub.IsMessageReceived() should be called continuously and is asynchronous by design as I wrote it in a non blocking style on purpose. Therefore the penalty is that it should be called continuously to detect the edge and react on it as that is the only chance to grab the data. If this can be designed in **simpeler AND safer** way, please share your thoughts..
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)
Status: open --> accepted
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 @@ -12,10 +12,6 @@ - Implements the same dynamic arrays of Sparkplug values as EoN, - The EoN can iterate through the connected FB_Devices via a list and sends all relevant Data to Primary SCADA - -v1.1.0.0 implements the basis for a List of Devices -From this version onwards we can expand The EoN and the Device to accommodate the appropriate code - -Projected versioning; -V1.3.0.0: EoN sends all Device Data too -V1.5.0.0: EoN can receive commands and distinguishes them for itself or a child Device +[x] v1.1.x.x solution implements the basis for a List of Devices +[ ] V1.4.x.x solution sends all Device Data too +[ ] V1.7.x.x solution can receive, digest and follow up DCMD's
Last updated: 2021-08-10
Post by i-campbell on Ticket #3: Build a SparkplugB scada in CODESYS discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -3,7 +3,3 @@ This application should demonstrate the usage and power of the sparkplug. This Ticket should be implemented after the FB_EoN_Node is done. - -The application needs a broker, so a suggestion would be to use an open to public broker in order to easily test the application hassle free. Local brokers or brokers with encryption can be setup in a later stage because they are not mandatory to debug the code. - -Any and all suggestions are welcome
Last updated: 2021-08-10
Post by hermsen on Ticket #111: FB_PrimaryHost: Construct "Dynamic" Structure of Edge Nodes discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
How should it be built on the fly => Could you share your thoughts on paper?
Last updated: 2021-08-10
Post by i-campbell on Ticket #29: MIT Licence discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by i-campbell on Ticket #117: FB_GroupID discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -1 +1 @@ -FB_GroupID scans and allocates a group of Nodes (edges, devices, other nodes) +FB_GroupID is allocated through NBIRTHs and holds a list of Birthed Edge Nodes status: open --> closed assigned_to: i-campbell
Last updated: 2021-08-10
Post by hermsen on Ticket #128: new implementation of FB_EdgeMQTT client discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -1 +1 @@ -FB_DeviceMQTTClient will be phased out and integrated into a single FB_EdgeMQTTClient +FB_DeviceMQTTClient publisher code will be phased out and integrated into a single FB_EdgeMQTTClient. Subscriber code will stay intact
Last updated: 2021-08-10
Post by hermsen on Ticket #125: PrimaryHost: proces & publish messages discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Last updated: 2021-08-10
Post by i-campbell on Ticket #39: FB_SparkplugB_SimpleEncoder 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 hermsen on Ticket #123: PrimaryHost: Investigate suitability of FBFactory for dynamic structure discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
The factory pattern has found it's way in our library 👍
Last updated: 2021-08-10
Post by aliazzz on Ticket #51: EoN: EON.PublishBirth() calls publish() twice discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
solved in v0.0.0.21
Last updated: 2021-08-10