Search Project: *:*

 
<< < 1 .. 1349 1350 1351 1352 1353 .. 3702 > >> (Page 1351 of 3702)

Post by i-campbell on Ticket #95: Versions: Downgrade to 3.5.14.0 discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Done in /branches/SP14andMQTT1020/ There are now some precompile errors (can be ignored) in the library The example also gives some precompile errors (can be ignored) Seems to run fine and connect to the broker OK. State machines updating.
Last updated: 2021-08-10

Post by aliazzz on Ticket #28: FB_Payload.ClaimNextFree* should initialize for you discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Hi, FB_Payload.InitializeStructuredPayload( ); Is at this moment difficult testable :-( Therefore I 'd suggest to see this method "disappear" i.e. become private and therefor, working by design. Maybe the FB_payload should become as 'user-friendly' as possible by reducing all burnerplate code. If the FB get instanciated and called, the underlying code could intialise itself without any exterior help?? Also, consider declaring all helper functions for FB_Payload as 'Internal' for the library so that they also disappear from view. I hope any and all initialisation can be brought back to the bare minimum as possible. Also, the interaction with this FB is event driven so it makes sense to write against methods as much as possible. I hope you'll consider this preliminary feedback, to be continued...
Last updated: 2021-08-10

Post by aliazzz on Ticket #39: FB_SparkplugB_SimpleEncoder discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Description has changed: Diff: --- old +++ new @@ -24,7 +24,7 @@ * [x] Encode( Enable ) // Start Encoding if Enable = TRUE, Stops encoding if enable = FALSE * [x] Encoded // Is encoding finished? * [x] EncoderBusy // Is the encoder busy? -* [x] EncoderError // An error occured +* [x] EncoderError( Error ) // An error occured * [x] InitEncoderBeforeAddingMetrics( Timestamp, SeqNr) // Initialize the Encoder before adding Metrics * [x] GetBDSeqNum * [x] GetSeqNum
Last updated: 2021-08-10

Post by aliazzz on Ticket #53: FB_EoN: PublishNodeBirth discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
labels: EoN, Bug --> status: open --> closed
Last updated: 2021-08-10

Post by aliazzz on Ticket #11: FB_Payload discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Description has changed: Diff: --- old +++ new @@ -0,0 +1 @@ +Implementation of FB_Payload assigned_to: i-campbell
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)
Description has changed: Diff: --- old +++ new @@ -5,6 +5,5 @@ With basic metrics is ment: basetype variables, no &#34;advanced&#34; metrics or historical things Whatever happens, the TimeStamp is mandatory and implemented. -As TimeStamp we take the current time as read from the controller. If the controller does not contain an RTC, that is just &#34;schade&#34; and we will not fix that, as it is a hardware issue. +As TimeStamp we take the current time as read from the controller. If an interested user has a controller which does not contain an RTC, we will work with that user to come up with an alternative. For now though, it is not supported. -
Last updated: 2021-08-10

Post by i-campbell on Ticket #73: EoN: Testing IIoT Host Node does not like it when it doesn't see a NDEATH discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
For MVP: user can no longer enable or disable the MQTT, it is just always on. implement "metrics":[{"name":"Node Control/Rebirth"}] to send a new birth certificate
Last updated: 2021-08-10

Post by aliazzz on Ticket #39: FB_SparkplugB_SimpleEncoder discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Description has changed: Diff: --- old +++ new @@ -5,10 +5,12 @@ Messages which are mandatory for this FB are: -* [ ] Node Death Message -* [ ] Node Birth Message -* [ ] Device Death Message -* [ ] Device Birth Message +* [x] Node Death Certificate +* [x] Node Birth Certificate +* [x] Node Data +* [x] Device Death Certificate +* [x] Device Birth Certificate +* [x] Device Data Pass a single instance of SimpleObject to the Encoder. @@ -31,7 +33,7 @@ Last but not least it should provide the end user with a way to obtain the protobuf encoded blob in order to publish it under the correct Sparkplug Topic -* [ ] GetEncodedBlobViaAdress( BlobAdr, BlobSize ) +* [x] GetEncodedBlobViaAdress( BlobAdr, BlobSize ) * [ ] GetEncodedBlobVia** ** Think of simple ways to return the blob **
Last updated: 2021-08-10

Post by hermsen on Ticket #101: Implement trigger for a DDEATH message as input FB_Device discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
assigned_to: h-hermsen --> i-campbell
Last updated: 2021-08-10

Post by hermsen on Ticket #65: EoN Example discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
status: open --> accepted
Last updated: 2021-08-10

Post by aliazzz on Ticket #3: Build a SparkplugB scada in CODESYS discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Hmmm, also a possibility! The FB_EoN_Node essentially acts as producer/consumer so it is possible. Our main goal is to debug the MQTT message contents so that the message fits the Sparkplug B protocol. This route will take less time I guess (We can always execute the original idea in a later stage of the implementation)
Last updated: 2021-08-10

Post by aliazzz on Ticket #45: FB_SimplePayloadEncoder: all unit tests all return a 37KB payload, even the small ones discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Tests silo'ed with positive outcome. Stumbled upon a side effect (re-open corresponding ticket?). EncodeMetricsList_Test encounters a 'payloadnotenoughmetrics' error while adding a list of 1024 metrics.
Last updated: 2021-08-10

Post by i-campbell on Ticket #1: Create Introductionpage 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)
Description has changed: Diff: --- old +++ new @@ -1,5 +1,5 @@ ~~~ -FB_MQTT_PubSub IMPLEMENTS CMBL.ILConC +FB_MQTT_PubSub IMPLEMENTS CBML.ILConC, CBML.IBehaviourModel FB_Init() Initialise() Connect()
Last updated: 2021-08-10

Post by i-campbell on Ticket #129: Edge: SFC itterator discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
summary: SFC itterator --> Edge: SFC itterator Description has changed: Diff: --- old +++ new @@ -1,4 +1,5 @@ It is a requirement to have things published in order -FB_Edge will receive an itterator which in a single scan, it will itterate until it finds an (Edge or Device) which wants to publish. The state machine then goes to PUBLISH and waits until the publisher is done. It then returns to the ITTERATION state to complete (does not restart) if the itteration completes without finding anyone who wants to publish, it ends the scan +FB_Edge will receive an itterator which in a single scan, it will itterate until it finds an (Edge or Device) which wants to publish. The state machine then goes to PUBLISH and waits until the publisher is done. It then returns to the ITTERATION state to complete (does not restart) if the itteration completes without finding anyone who wants to publish, it ends the state and restarts the ittetration. +The &#34;not restarting the itterator&#34; may be crucial for not favouring a particularly busy device over others. Effectively the itterator is normally a &#34;looper&#34;.
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)
Ideas: 1st measure is RAM (via Array) storage, 2nd measure is "long-term" disk storage Array (1) > Disk (2) > Send 1) Buffer every Change into an array for safe keeping. 2) If the Array is "full" we write the entire array contents to disk for sending Then we can use the emptied array again to store new changes. We could implement this feature into a separate FB and tie it in the EoN maybe using Trend Storage then we easily graph it also Trend API It automatically saves as .sqlite and can be read using VisuTrendStorageAccess https://store.codesys.com/trend-api-example.html and can be read back using you just use the trendstorageaccess lib
Last updated: 2021-08-10

Post by i-campbell on Ticket #41: Add SparkplugB.T_DateTime ALIAS for ULINT 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 i-campbell on Ticket #19: Add certificate generation to the library discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
The security screen cannot, but the security agent can (they sound so similar!) https://store.codesys.com/codesys-security-agent.html For me though, logging in to 50 controllers and remembering what all the buttons are for your particular server is too slow.
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)
summary: Every FB/Function will need a mandatory Unit Test. --> 50% of FB/Function will need a Unit Test Description has changed: Diff: --- old +++ new @@ -1,6 +1,6 @@ -Unit test will be written for each of the FB&#39;s from the library using Cfunit v10.9.95 (RC5) or better. +Unit test will be written to cover 50% of the FB&#39;s and methods from the library using Cfunit v1.1.0.0 or better. The unittest project in the trunk is to be leading. Any other tests can be written in branches to test personal developments. -As the trunk of the library gets updated, ideally the unittest project of the trunk gets updated too. +As the trunk of the library gets updated, ideally the unittest project of the trunk gets updated too. The software will be unit tested and/or integration tested, as much as possible.
Last updated: 2021-08-10

Post by i-campbell on Ticket #101: Implement trigger for a DDEATH message as input FB_Device discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
status: accepted --> closed
Last updated: 2021-08-10

Post by aliazzz on Ticket #3: Build a SparkplugB scada in CODESYS discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
summary: Set up a Sparkplug B Consumer for testing purposes --> Build a SparkplugB scada in CODESYS Description has changed: Diff: --- old +++ new @@ -1,6 +1,9 @@ -Find an **opensource** and **free** SCADA package which can consume/produce Sparkplug-B messages for testing and debug purpose. Any platform (windows, linux, and/or docker(!) hosted) will suffice. +Build an application which can consume/produce Sparkplug-B messages for testing and debug purposes. -* Find SCADA candidate, -* Install it, -* Configure it, -* Announce it. +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 Milestone: 1.0 --> 2.0
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)
status: pending --> closed
Last updated: 2021-08-10

Post by hermsen on Ticket #72: MQTT: FB_MQTT.IsConnected producing false positives discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
labels: MQTT --> status: open --> closed
Last updated: 2021-08-10

Post by hermsen on Ticket #97: Allow correct publishing of Multiple Device Data discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Version Jump! This issue has been solved in Hermsen Branch V1.3.0.0
Last updated: 2021-08-10

Post by aliazzz on Ticket #61: EoN: Maximum size NDEATH discussion co⚡e: Sparkplug™ MQTT edge and host tickets (Post)
Description has changed: Diff: --- old +++ new @@ -1,3 +1,3 @@ In the code, it asks &#34;What is the maximum size of an NDEATH&#34; -Answer: 44 Bytes. (see attachment. +Answer: 44 Bytes. (see attachment) Note that changing the size to exactly 44 requires the fix in ticket [#60]. assigned_to: h-hermsen --> aliazzz
Last updated: 2021-08-10

<< < 1 .. 1349 1350 1351 1352 1353 .. 3702 > >> (Page 1351 of 3702)

Showing results of 92541

Sort by relevance or date