Home
Objective
Establish a Serial Communication platform / toolkit
* Consisting of documented interfaces and base implementations
* For "consumers": end user applications and libraries
* For "providers": device and library developers
Ideally... 😉
Background
I had a lot of work in CODESYS application development for a diversity of industrial and commercial facilities, and as such ended up with a huge amount of "wanted to be reusable" tools, libraries. Some very simple and basics, but also some very deep and valuable: (task-sequnce oriented modbus toolkit, a Genibus master-slave stack, vfd controlers wit pump physics). And I have to keep these libraries maintained and updated, as most of my application code relies on them.
For the serial communication they originally rely on the beloved standard CoDeSys SysCom library, however as the years passed I had to continously upgrade and rewrite them, to add specific support for serial interfaces on different remote I/O modules, gateways, transceivers. So my libraries got "dirty", containing multiple versions of multiple specific implementations...
This time, I decided to do the "big rewrite" in a different way, remove all the serial device specific code from the libraries, and separate the communication layer into a hierarchy of libraries, under the umbrela of a common set of interfaces.
So, I'M DOING THIS ANYWAY - and I'm pretty sure to do it good enough for my own use.
However, during the past days of the development, I've realized, that it might not be impossible to make it public and reusable; and as a "side product" it could bring up and hopefully clarify many poorly documented topics. That's why I decided to open this project on CODESYS Forge, use some limited time for presentation and communication, and let's see...
BTW, I have some foggy memory, that I already started this once... But it was a different era: CODESYS V3 was still very fresh, V2 was a must... A lot changed since...
Project Members:
- Strucc.c (admin)
Discussion
Anonymous