Post by hermsen on Ticket #96: Versions: Upgrade MQTT Client SL to the one that installs with IIoT Libraries SL 1.3.0.0 discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Implemented in v1.3.3.0 in branch
Last updated: 2021-08-10
Post by hermsen on Ticket #105: Lowering Device CPU consumption discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Implementation of FB_EoNTopicProvider Implementation of FB_DeviceTopicProvider Which helps to significantly lower the WCONCAT function usage count as string manipulation is known to be CPU consumption prone.
Last updated: 2021-08-10
Post by i-campbell on Ticket #78: EoN: Uses non-unique ClientID discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
labels: EoN --> status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #14: Example project for a Node discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #77: TLS hCert needs to be SysTypes.RTS_INVALID_HANDLE, if there is no client certificate discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
implemented in v0.9.1.2
Last updated: 2021-08-10
Post by aliazzz on Ticket #9: Initial Testing MQTT Broker discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -5,4 +5,10 @@ TCP Port: 1883 No authentication or certificate verification possible -http://www.mqtt-dashboard.com/ +See http://www.mqtt-dashboard.com/ +for their current traffic. + +For a good MQTT explorer; +http://mqtt-explorer.com/ +Opensource, free and available for any OS by Thomas Nordquist +
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)
Incorrect SeqNum tagging is solved in V1.1.0.10 in my branch.
Last updated: 2021-08-10
Post by hermsen on Ticket #135: Project Homepage: Update guides discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Reopen 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 @@ -15,8 +15,28 @@ //// +Part2 Also at this moment, I have code which publishes arbitrary messages. The initialisation of sending a new message takes 2 cycles, as the first cycle resets the state machine (xDone = false, xBusy = false, Xerror = false, internal client state is dormant) then a rising edge on exectue sends a new message. I guess there is no "shorter" way to handshake the process, as the stats output need to be digested after a send. When Execute is set to False, the statemachine is reset and dormant. + +EDIT => part2 Solved + +~~~ +// publish +xPublishBusy := MQTT_PubSub.PublisherBusy(); +xPublishDone := MQTT_PubSub.PublisherDone(); +xPublishError := MQTT_PubSub.PublisherError( eError => ePublishError ); + +MQTT_PubSub.Publish( Execute := xPublish, + PubTopic:= PublishTopic, + PubMessage:= PublishMessage, + PubQos:= PublishQos, + PubRetain:= PublishRetain ); + +xPublish := xPublishBusy AND NOT(xPublishDone OR xPublishError); +~~ + +
Last updated: 2021-08-10
Post by hermsen on Ticket #76: FB_PayLoadMetric "hangs" if it receives an invalid message discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: open --> closed
Last updated: 2021-08-10
Post by hermsen on Ticket #30: Define User Story for setting up sparkplug with CODESYS discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
labels: User Story --> status: open --> closed
Last updated: 2021-08-10
Post by i-campbell on Ticket #10: Secure testing MQTT broker discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Milestone: SFP: TLS --> 2.0.0.0: TLS
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 @@ -1,4 +1,3 @@ - FB_EoN_Node encapsulates status: open --> accepted assigned_to: aliazzz
Last updated: 2021-08-10
Post by i-campbell on Ticket #19: Add certificate generation to the library discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
https://store.codesys.com/crypto-example.html
Last updated: 2021-08-10
Post by i-campbell on Ticket #18: SVN: use 'standard' cforge folder structure discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
assigned_to: aliazzz
Last updated: 2021-08-10
Post by i-campbell on Ticket #48: Cforge tool integration discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Tool is not yet suitable for large SVN repositories, and if we just wait, CODESYS Git will be available.
Last updated: 2021-08-10
Post by aliazzz on Ticket #9: Initial Testing MQTT Broker discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
The broker works as expected, I used mqtt explorer for it. It "sees" all unencrypted topics/traffic (many of which codesys ;-) ). I will incorporate a pre configured send and receive MQTT framework into our project/library.
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)
Milestone: 2.0 --> 3.0
Last updated: 2021-08-10
Post by aliazzz on Ticket #31: Define how Store & Forward should be implemented (historical data) discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Description has changed: Diff: --- old +++ new @@ -1,4 +1,6 @@ Purpose of store & Forward: + +Determine a way in which we can store and forward hystorical information to bridge any trendgaps / database gaps on SCADA side of the architecture. When a EoN Node has lost its connection to a broker, any updated value which had to be published now gets stored in the local storage of the EoN node. Whenever the EoN node gets online again (after a succesful restored connection) the EON now will publish it's local hystorical data to the broker. @@ -9,5 +11,3 @@ I should read up in the spec on what it statesbon this point, but without having done so, I can think of these suggestions on how to achive the usecase. Some suggestions from my side; a file, filled with hystorical metrics can forwarded after reconnect by the EoN node. The SCADA server can issue a command to ask for such a file from the EoN,which then replies with said anwser(s). The anwser can be a file of hystoric metrics or a payload with metrics marked as hystorical data. Maybe tere are even other possibilities on achieving this within the constraints of the sparkplug spec? -Anyway => determine a way in which we can store and forward hystorical information to bridge any trendgaps / database gaps on SCADA side of the architecture. -
Last updated: 2021-08-10
Post by aliazzz on Ticket #6: How to implement “Google Protobufs” serialization/deserialization ? discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
summary: implement an IEC “Google Protobufs” encoder/parser --> How to implement “Google Protobufs” serialization/deserialization ? Description has changed: Diff: --- old +++ new @@ -1,7 +1,18 @@ The core component of the SparkplugB Library will be the IEC “Google Protobufs” encoder/parser. +How do we solve this issue? + +* Should we include an external C library? + * Personally I have no experience with that but I am willing to learn it ;-) +* Can we think of another way of implementing this? Ideas are welcome! + + This ticket is therefore a placeholder for Milestone 1.0. It is neccesary for the following; + + +----- + Sparkplug™ B MQTT Payload Definition
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)
Splitted connect into; 1. PublishNCMD, 2. PublishDCMD. so it's now; 1. PublishNCMD, 2. PublishDCMD, 3. Publish NBirth, 4. Publish DBirth.
Last updated: 2021-08-10
Post by aliazzz on Ticket #23: Architecture discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
status: accepted --> closed
Last updated: 2021-08-10
Post by aliazzz on Ticket #24: FB_MQTT_PubSub discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
The CBML LConC state machine is implemented, now integrating the MQTT Client/Publisher code.
Last updated: 2021-08-10
Post by aliazzz on Ticket #29: MIT Licence discussion
co⚡e: Sparkplug™ MQTT edge and host
tickets
(Post)
Done!
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)
summary: AWS compatable --> AWS IoT Core Support status: open --> accepted
Last updated: 2021-08-10