https://forge.codesys.com/lib/cobolt/tickets/You searched for assigned_to:"hermsen"enSat, 17 May 2025 00:36:24 -0000https://forge.codesys.com/lib/cobolt/tickets/170/I'm trying to run the example project with Ignition bu I got this error from the Ignition log Invalid payload missing sequence number: spBv1.0/co5e112/NBIRTH/Edge2 and I'm not able to see anything in the ignition designer I'm using Codesys 3.5.20 Any hint to make this run? William BlandonSat, 17 May 2025 00:36:24 -0000https://forge.codesys.com/lib/cobolt/tickets/170/https://forge.codesys.com/lib/cobolt/tickets/165/*This task has been split off from ticket [#160] since this task will take significant time to implement If the user disables the edge it shall disconnect and a NDEATH will be published. For more information see: https://github.com/eclipse/sparkplug/blob/develop/specification/src/main/asciidoc/chapters/Sparkplug_5_Operational_Behavior.adoc#edge-node-session-terminationhermsenSat, 05 Nov 2022 21:20:03 -0000https://forge.codesys.com/lib/cobolt/tickets/165/https://forge.codesys.com/lib/cobolt/tickets/160/FB_Edge has a local variable Connect. 1. [x] Move it to VAR_INPUT 2. [x] rename Connect to Enable 3. [x] document its behaviour 4. Implement the functionality a. [x] Edge shall not start until enabled. b. [#165] Edge shall disconnect and a NDEATH will be published. *Implementation of NDEATH has been splitted of and moved to [#165]i-campbellSun, 17 Jul 2022 16:43:47 -0000https://forge.codesys.com/lib/cobolt/tickets/160/https://forge.codesys.com/lib/cobolt/tickets/158/We intend eventually to use some SP18 compiler features, namely UTF8 strings, which will bring processing performance enhancements as well as application memory usage improvements. Also, we want to use SP18 development environment. This would mean though that for end users to use the latest version of co⚡e, they will need to use SP18 development environment and SP18 compiler, even if with their older runtimes. The only problem here would be, those with devices from manufacturers which both: a) only work with their own customized version of the CODESYS development environment and b) are not yet at SP18 with that development environment (eg. has released SP17 a month ago) So we have two options moving forward. Option 1 - We create a release of the current state, and for anyone not using the SP18 development environment yet, they have to use this version. All versions from now will require SP18. Option 2 - We try to continue development in such a way that allows for the old compiler also. Option 2 is more work than Option 1, but we understand some people might take time to move to SP18. We opt for Option 1, as this will let us realize the new performance improvements faster. Tasks for old version: * :point_right: CODESYS git *ONLY* supports SP17 and later:exclamation: * [x] Create a commit in the binaries git, which stores the libraries and projects which can be opened using SP16 Patch 1 development environment. The libraries should compile and be installed in the repository, the unit test should run, the project should run and send data to/from Edge and Host. * [x] Host * [x] Stack * [x] Edge * [x] Example * [x] Unittest * [x] Create a git tag of that SP16.10 commit. * [x] Create instructions for how to access that for users who want to use an older version in the FAQ. Tasks for SP18 version: * [x] Use SP18 to checkout, close project, open project, and commit the SP18 changes with a commit message containing this Ticket number and title * [x] Up the compiler version to SP18 * [x] Set the "Project Settings > Library Development > Pointer size to use" to "32bit or 64 bit" * [x] Commit and push to main * [x] Host v1.4.0.0 * [x] Stack v1.5.0.0 * [x] Edge * [x] Example * [x] Unittesti-campbellSat, 05 Nov 2022 21:20:03 -0000https://forge.codesys.com/lib/cobolt/tickets/158/https://forge.codesys.com/lib/cobolt/tickets/157/* [x] Refactor FB_SparkplugBSimple to FB_SparkplugBxCoderHandler from Stack * [x] Repair references in Edge * [x] and Host LibrarieshermsenFri, 08 Apr 2022 20:41:05 -0000https://forge.codesys.com/lib/cobolt/tickets/157/https://forge.codesys.com/lib/cobolt/tickets/152/Add a yml file to auto build various artefacts; * [x] binaries * [x] project * [x] unittest * [ ] co⚡e-edge.library * [ ] co⚡e-host.library * [ ] co⚡e-stack.library Suggestion: only add a .yml pipeline to binaries git in order to build and package tags.hermsenSun, 17 Apr 2022 22:09:17 -0000https://forge.codesys.com/lib/cobolt/tickets/152/https://forge.codesys.com/lib/cobolt/tickets/150/d:Project archive is too big to be downloaded from a git repository. Maybe this needs to be SVN, or some other file storage (which allows 50Mb downloads)i-campbellThu, 25 Nov 2021 19:28:39 -0000https://forge.codesys.com/lib/cobolt/tickets/150/https://forge.codesys.com/lib/cobolt/tickets/149/We should publish lots of hardware and software info obtained from the platform which the Edge runs on. All the info is aggregated and then published in the metric "ABOUT" with access "read-only * [x] https://faq.codesys.com/display/CDSFAQ/Reading+the+Manufacturer+Information+of+the+Controller * [x] https://faq.codesys.com/display/CDSFAQ/Reading+the+IP+and+MAC+Addresses+from+AdapterInfo * [x] https://faq.codesys.com/display/CDSFAQ/Reading+the+Compiler+and+Runtime+Version * [x] https://faq.codesys.com/pages/viewpage.action?pageId=21135402 * [x] https://faq.codesys.com/display/CDSFAQ/Identifying+the+Hardware+and+Operating+System added Opt-Out IWantExtendedEdgeInformation : BOOL := TRUE; https://forge.codesys.com/lib/cobolt/cobolt-edge/ci/71221096fbe2cabd8304e28b874874f9c67fe13a/hermsenFri, 03 Dec 2021 13:55:48 -0000https://forge.codesys.com/lib/cobolt/tickets/149/https://forge.codesys.com/lib/cobolt/tickets/148/MQTT Client SL 1.5.0.0 introduces WebSockets. This should be supported. test.mosquitto.org has some websocket listeners * [x] HTTPS WebSockets support, * [x] Proxy Settings support( unverified), * [x] TLS Support (wss://... implemented but unverified), * [x] Edge / Device ( ws://... verified), * [ ] Host i-campbellSun, 17 Jul 2022 16:49:01 -0000https://forge.codesys.com/lib/cobolt/tickets/148/https://forge.codesys.com/lib/cobolt/tickets/147/This ticket serves as aplaceholder to creat a set of commit scripts which will solve several re-occuring tasks automatically for us. we can call these scripts in various ways, among them is on a git commit hook: tasks we must persue are; Auto-test the solution, STweep the solution source, When the commit will be tagged, it needs to committed to binaries git. A script (through codesys git api interface) needs to be developed to orchestrate these tasks. Any such task should be considered for ci/cd so we can concentrate on development itself instead. hermsenSat, 06 Nov 2021 10:03:58 -0000https://forge.codesys.com/lib/cobolt/tickets/147/https://forge.codesys.com/lib/cobolt/tickets/144/Suggestions 1) Fix is to set a buffersize i.e. ~~~ _workWSTRING : WSTRING(4096); ~~~ 2) Replace functions from Standard64 with the functions from StringUtils hermsenSat, 30 Oct 2021 17:36:05 -0000https://forge.codesys.com/lib/cobolt/tickets/144/https://forge.codesys.com/lib/cobolt/tickets/142/mqttsparkplugb is a generic name, and it disagrees with the project naming guidelines of the eclipse foundation. As such the project should be migrated from: https://forge.codesys.com/prj/mqttsparkplugb/ to https://forge.codesys.com/lib/cobolt/i-campbellThu, 12 Aug 2021 00:58:57 -0000https://forge.codesys.com/lib/cobolt/tickets/142/https://forge.codesys.com/lib/cobolt/tickets/141/Migrate the project to git. * [x] One git repository for each library/project. Use name co⚡e.library if possible, if not cobolt-library * [x] For convenient download of the binary library/project files, we will continue to publish these to the SVN repository. At a later date, the binaries will be migrated to their own git repository, prefereably conserving the SVN history (of the binaries) wii-campbellSat, 23 Oct 2021 23:03:20 -0000https://forge.codesys.com/lib/cobolt/tickets/141/https://forge.codesys.com/lib/cobolt/tickets/140/Remove FB_Payload_OLD from libraryi-campbellSun, 11 Jul 2021 17:42:43 -0000https://forge.codesys.com/lib/cobolt/tickets/140/https://forge.codesys.com/lib/cobolt/tickets/137/If set to a publish rate of 2000 (ms) the edge publishes NDATA faster than one every 2 seconds. NDATA should be limited to the publish rate.i-campbellMon, 10 May 2021 20:46:14 -0000https://forge.codesys.com/lib/cobolt/tickets/137/https://forge.codesys.com/lib/cobolt/tickets/136/The edge publishes somehow publishes payloads that are valid but empty i.e; Payloads contain timestamp and a valid seqnum, but the metrics section is empty; NDATA ~~~ {"timestamp":1619874081095,"metrics":[],"seq":218} ~~~ Replication: Set GenerateDataTimer to e.g. T#60s whilst keeping publishPeriod to e.g. 500 1) Find root cause of this unwanted and unnecessary sending of empty payloads, 2) Suggest and implement a suitable fix.hermsenMon, 10 May 2021 20:45:55 -0000https://forge.codesys.com/lib/cobolt/tickets/136/https://forge.codesys.com/lib/cobolt/tickets/135/Proof and Update the following to match latest library: [x] [Add to existing](https://forge.codesys.com/prj/mqttsparkplugb/home/Add%20SparkplugB%20to%20existing%20CODESYS%20project/) [x] [Set up Test Server](https://forge.codesys.com/prj/mqttsparkplugb/home/Set%20up%20test%20system/) - rename to setup a test system with Ignition Primary Host Add the following guides: [x] setting up a test environment with a co⚡e primary hosti-campbellSat, 15 May 2021 22:48:45 -0000https://forge.codesys.com/lib/cobolt/tickets/135/https://forge.codesys.com/lib/cobolt/tickets/128/FB_DeviceMQTTClient publisher code will be phased out and integrated into a single FB_EdgeMQTTClient. Subscriber code will stay intact hermsenFri, 30 Apr 2021 13:34:43 -0000https://forge.codesys.com/lib/cobolt/tickets/128/https://forge.codesys.com/lib/cobolt/tickets/116/Any detected group add/remove will trigger a log message will display: the detected group name, the number available in pool, the added/removed count Same goes for added/removed edges, devices and metrics The cmpHost component will log thesehermsenSat, 05 Nov 2022 21:20:03 -0000https://forge.codesys.com/lib/cobolt/tickets/116/https://forge.codesys.com/lib/cobolt/tickets/115/Every "node" in the library will have it's own log. This will make logging in general and debugging easier as a log only will contains messages from that certain component. How this should be realised is yet to be seen. If the effort is too high this ticket will be backlogged.hermsenSat, 13 Mar 2021 19:25:53 -0000https://forge.codesys.com/lib/cobolt/tickets/115/https://forge.codesys.com/lib/cobolt/tickets/110/Create an FB_PrimaryHost. It should connect (with last will state). It should disconnect. It should subscribe to: namespace/+/NBIRTH/+ namespace/+/NDEATH/+ namespace/+/DBIRTH/# namespace/+/DDEATH/# namespace/+/NDATA/+ namespace/+/DDATA/# namespace/+/NCMD/+ namespace/+/DCMD/# STATE/+ it should provide the following methods, which will be used to handle the payloads: onNBIRTH() onNDEATH() onDBIRTH() onDDEATH() onNDATA() onDDATA() onNCMD() onDCMD() onSTATE() it should publish STATE.i-campbellSat, 05 Nov 2022 21:20:03 -0000https://forge.codesys.com/lib/cobolt/tickets/110/https://forge.codesys.com/lib/cobolt/tickets/109/The title says it all, moving DCMD to FB_DevicehermsenSun, 27 Dec 2020 00:42:45 -0000https://forge.codesys.com/lib/cobolt/tickets/109/https://forge.codesys.com/lib/cobolt/tickets/108/With the 1.0.2.0 MQTT SL library, it is now possible to verify the server certificate. This should be added, so that the certificate can be verified.i-campbellSun, 27 Dec 2020 20:44:14 -0000https://forge.codesys.com/lib/cobolt/tickets/108/https://forge.codesys.com/lib/cobolt/tickets/103/cause: pointer will turn to zero while still dereferencing this pointer hermsenSat, 19 Dec 2020 15:24:24 -0000https://forge.codesys.com/lib/cobolt/tickets/103/https://forge.codesys.com/lib/cobolt/tickets/100/as there is no way to error out of the two publish states, there is no way to reconnect to an MQTT Server once a connection is lost. => Yes, I have seen this effect during testing too, thanks for reminding me to make this ticket😀 A solution had already been thought off but the current seqnums issue has higher priority.😔 Suggested solution; After loss of connection, make sure the EoN can return to the offline step. The trigger to detect this is programmed outside the StateMachine. It is then forwarded into the state machine in form of an input command to let the EoN StateMachine go-to The offline state. The above mechanism will also trigger devices to go to plugged but offline as they monitor the EoN continuously. Whenever the connection restores the EoN will reconnect and the devices will automatically follow after the connection is restored with no programming required (by design)hermsenSat, 02 Jan 2021 13:03:35 -0000https://forge.codesys.com/lib/cobolt/tickets/100/