Inheritence of struct,
CODESYS Forge
talk
(Thread)
Inheritence of struct,
Last updated: 2025-03-14
Home
(Sys)Com-Wrapper
home
(WikiPage)
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)
Last updated: 2025-03-14
Post by egau on Enable and Disable Project IO programmatically
CODESYS Forge
talk
(Post)
Hi @eschwellinger, I tried this with Modbus COM slaves. I was able to disable them (slave becomes greyed out in the device tree), but the DED.Reconfigure "eError" output shows "NOT_SUPPORTED". After this, when I tried to re-enable the slave, it did not work (device stayed greyed out in the device tree), and the DED.Reconfigure "eError" output also showed "NOT_SUPPORTED". Is there something to do about this, or the device just doesn't support reconfiguration? P.S: I tried this running locally on my computer (not in simulation mode). So of course I was not physically connected to the devices. I have two similar projects, but one of them doesn't have the Modbus_COM devices. I know I can "Exclude from build" the devices for that project, but I would really prefer not to do this if possible. I would prefer to dynamically toggle a configuration variable that would enable or disable the slaves.
Last updated: 2025-03-14
Enable and Disable Project IO programmatically
CODESYS Forge
talk
(Thread)
Enable and Disable Project IO programmatically
Last updated: 2025-03-14
wiki Discussion
fmon
wiki
(Discussion)
Forum for wiki comments
Last updated: 2025-03-14
blog Discussion
fmon
blog
(Discussion)
Forum for blog comments
Last updated: 2025-03-14
(no subject)
fmon
wiki
(Thread)
Last updated: 2025-03-14
Post by fmon on Modbus : dis- / re-connect cable: modbus does not re-start
CODESYS Forge
talk
(Post)
Hello, I am using codesys Modbus TCP client (4.4.0.0) to communicate with a python modbus server (package pyModbusTCP). I first start my python server on the distant machine. After a fresh codesys compilation, a plc connection/transfer and a PLC run, the modbus connection is OK. Every time in this context the connection is created correctly. When I shut down the server, the modbus connection falls, that is normal. When I restart the python server, impossible to recreate the modbus connexion. With the client autoreconnection, I see on my server that the client tries to connect but unsuccesfully. I have the following message : DEBUG:pyModbusTCP.server:accept new connection from ClientInfo(address='192.168.1.20', port=33476) DEBUG:pyModbusTCP.server:Exception during request handling: NetworkError('recv return null') I tried to stop the codesys client and to restart it with these commands : Modbus_TCP_Client.xStop := True; // Or False Modbus_TCP_Client.Enable := True; // Or False Modbus_TCP_Server.Enable := True; // Or False I tried to confirm the error manually to force reconnection with: Modbus_TCP_Server_Motors.xConfirmError := TRUE; I tried also this command to STOP/RESET/START client and server (codesys side) but nothing happens : status_client := Modbus_TCP_Client.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.STOP); // .RESET & .START The answer of this function when executed is "status_client = NOT_SUPPORTED" It seems that is a socket problem, but I do not understand if it is on the client or server side. I tried a modbus simulator called "ananas.exe" and the result is the same. Impossible to get a modbus reconnection. What is different at the first connection and at a reconnection attempt ? Thanks for your help
Last updated: 2025-03-14
Home (version 1) discussion
brubingh
wiki
(Thread)
Home (version 1) discussion
Last updated: 2025-03-14
Home
fmon
wiki
(WikiPage)
Project Members: fmon (admin)
Last updated: 2025-03-14
ExportPLCopenXML is failing
CODESYS Forge
talk
(Thread)
ExportPLCopenXML is failing
Last updated: 2025-03-15
Home (version 1) discussion
fmon
wiki
(Thread)
Home (version 1) discussion
Last updated: 2025-03-14
Post by alberto on ExportPLCopenXML is failing
CODESYS Forge
talk
(Post)
I'm trying to export my whole project through the option ExportPLCopenXML. It seems working, but when I'm trying to import the xml I have the following error during the importation process: Object reference not set to an instance of an object. It seems a usual issue with this process that affects to the pointer to user classes inside a procedure. I receive this error for two general functions that have this pointer declarations in the VAR_INPUT section. It seems a bug into the export/import process of CodeSYS and I couldn't skip it so far. Anyone could help me? Thanks in advance.
Last updated: 2025-03-15
wiki Discussion
libichj
wiki
(Discussion)
Forum for wiki comments
Last updated: 2025-03-15
blog Discussion
libichj
blog
(Discussion)
Forum for blog comments
Last updated: 2025-03-15
(no subject)
libichj
wiki
(Thread)
Last updated: 2025-03-15
Home
libichj
wiki
(WikiPage)
Project Members: libichj (admin)
Last updated: 2025-03-15
Post by libichj on Raspberry Pi: List of available drivers / libraries
CODESYS Forge
talk
(Post)
Is it possible to renew the urls in your post? Especially fo "Arduino UNO IO Device Description and Library"? Thank you for reply.
Last updated: 2025-03-15