Post by necatibilgin on Communication betwee 2 codesys devices with PROFINET ^{CODESYS Forge talk (Post)}
Hi everybody, Is there any sample project that communicates 2 devices with profinet using Codesys platform on the devices? BR, Necati.
Last updated: 2023-11-03

Post by baldeep on Codesys Raspberry Runtime 4.10.0.0 and RSM Utility 3.5.19.0 ^{CODESYS Forge talk (Post)}
I had been using Codesys Raspberry 4.9.0.0 Runtime for a Project with CAA File 3.5.19.0. But now with Update 4.10.0.0 and Raspberry pi 64 Bit.....i cannot compile my code as RSM Utility 3.5.19.0 is not recognised. Any help? Regards
Last updated: 2023-11-20

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
I tested your project but with same results i am still not seeing analog values. I also included the library list, the mainprogram.
Last updated: 2024-11-08

Post by s1ack on Undertanding Application Based Licenses ^{CODESYS Forge talk (Post)}
Can anyone confirm my thinking here that this project will require Control Standard M because of the I/O channel count under the fieldbus?
Last updated: 2024-11-08

Post by simone on Collapse all ^{CODESYS Forge talk (Post)}
Thank you so much r-niedermayer, it really helps me. Sorry for the late response but I have worked on a different project rather than the codesys one
Last updated: 2024-12-03

Post by rmaas on TCP Server ^{CODESYS Forge talk (Post)}
Hi George, I am no expert but recently tried and got it working using this example project: https://forge.codesys.com/prj/codesys-example/nbs/home/Home/#example-for-tcp-server-tcp-client BR, Rinie
Last updated: 2025-02-20

Post by fil on Using Latch Variable in Alarm as input from text list ^{CODESYS Forge talk (Post)}
Good morning, I am currently working on a project where this would be of enormous value. Any input would be very welcome - thanks in advance. Best regards Fil
Last updated: 2025-03-06

Post by bernardchen on Modbustcp.lib missing codesys v2.3 ^{CODESYS Forge talk (Post)}
a codesys project V2.3.9 opened with error of libuary missing. Modbustcp.lib and Modbustcpsrv.lib where can I download these two libs . I am a beginner of codesys. this codesys v2.3 is running in virtualbox XP system without internet access.
Last updated: 2025-03-12

Post by programmer on 3.5 P20 hangs - no response ^{CODESYS Forge talk (Post)}
Hi, Is there a solution found for the problem described in first post? Any version above Codesys 3.5 P19 hangs during start up. It makes no difference whether I simply start Codesys or open a project directly. I'm using Windows 10 Home edition. Thanks!
Last updated: 2025-06-23

Post by gseidel on MC_MoveAbsolute: C0138: No matching 'FB_Init' method found for instantiation of SMC_MoveAbsRelPerformerImpl [ERROR] ^{CODESYS Forge talk (Post)}
Hi Imdat, can you please provide the exact version of CODESYS and the compiler version in the project settings? Thanks, Georg
Last updated: 2025-09-08

Post by pernockham on PHOENIX CONTACT Axioline PLCnext project in CodeSys SodftPLC ^{CODESYS Forge talk (Post)}
The structure should be the same independent of which runtime version. Im using Codesys control for linux SL. Ie, add an ethernet device, then profinet controler then phoenix PN bus coupler.
Last updated: 2025-09-09

Post by ranadheer on PHOENIX CONTACT Axioline PLCnext project in CodeSys SodftPLC ^{CODESYS Forge talk (Post)}
Thankyou TimvH ,while searching in every device about the component it is same like above screenshot,and i crosscheck with the device repository but devices are available here.
Last updated: 2025-09-09

Post by pernockham on PHOENIX CONTACT Axioline PLCnext project in CodeSys SodftPLC ^{CODESYS Forge talk (Post)}
You should use PLCnext if your device-hw is a PLCnext-un it. As I understand it you are using "CODESYS Control Win V3 x64".
Last updated: 2025-09-09

Post by liai on can not new a cam table in codesys V3.5 SP20 ^{CODESYS Forge talk (Post)}
I am using a new project, with nothing, but when add a simple cam table, and compile, there will be errors. It seems some add-on or library was missing, but there is not any hint. Could you help, please.
Last updated: 2025-09-18

Post by lipton on Safety Cross-communication with network variables ^{CODESYS Forge talk (Post)}
I am currently engaged in research for a Codesys project that involves the establishment of communication between two or more Codesys safety controllers using safe communication protocols, would it be possibole ? /Best Regards
Last updated: 2023-12-29

Post by yann2021 on SysProcessExecuteCommand ^{CODESYS Forge talk (Post)}
Hello, I have this code who worked fine in an other project with a previous SP. Why do I have now errors when I generate this code...? Who can help me pls? Many thanks for your help.
Last updated: 2024-02-04

Post by thewizard8 on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
Hi eschwellinger, Thanks for replying, but I'm not shure if I got it right. Do you mean that I have bad configuration on my CODESYS config file? Or in my project? Thanks in advance!
Last updated: 2024-03-19

Post by vincentger on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Any resolution on this? I have currently 75 channels in my project that i brought up from SP18, which means i am 65 Channels above the new limitation?
Last updated: 2024-04-09

Post by gseidel on CNC / G01 Speed is very slow (or go-stop motion) in Continuous short segment . ^{CODESYS Forge talk (Post)}
Hi k2saki, 1.SMC_ReadNCFile2 2.SMC_Interpreter 3.SMC_SmoothMerge 4.SMC_SmoothPath 5.SMC_CheckVelocities I attached a simple example project. Best regards, Georg
Last updated: 2024-04-30

Post by gseidel on Warning C0564 when compiling CNC project with variables program ^{CODESYS Forge talk (Post)}
Hi Fless, thanks for your report! We created an issue in our bug tracker (SM-5109) and will have a look at this issue. Best regards, Georg
Last updated: 2024-04-30

Post by rabaggett on CODESYS control for Raspberry Pi 64 SL errors ^{CODESYS Forge talk (Post)}
It is either my installation is bad, or there is a bug. I re-created the project in 3.5 SP19 and there are no errors or warnings. Compiles with no errors or warnings. The original was done in 3.5 SP20. Thoughts?
Last updated: 2024-05-03

Post by ton on Code erzeugen mit kryptischer Fehlermeldung mit GVL_Io_dd05d808 ^{CODESYS Forge talk (Post)}
Ich habe das gleiche problem. Losch mal die '.precompile cache’ datei und öffne dass project. Ich habe dan keine fehler meldung und kann ohne probleme online.
Last updated: 2024-05-22

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

Post by fmon on Modbus TCP client reconnection problem ^{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". Is it normal ? 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 client reconnection. What is different at the first client connection and at a reconnection attempt ? Thanks for your help
Last updated: 2025-03-17

Post by testlogic on Sending Sequential Modbus TCP Packets ^{CODESYS Forge talk (Post)}
I have a Modbus TCP slave device where I need to do sequential writes to the same register. The register I'm writing to is kind of like a command line, each packet is a command word encoded in Hexadecimal. I am having difficulty implementing this system in CoDeSys 3.5 SP19. I feel like the structure of the program should be something along the lines of (Pseudocode): ModbusTCPSend(Command Register, Command1) ModbusTCPSend(Command Register, Command2) ModbusTCPSend(Command Register, Command3) I have tried to implement this with a rising edge trigger wMot1OPCode := 16#E1; //Stop Motor & Kill Program xMot1SendOP := TRUE; //Send OP on rising edge xMot1SendOP := FALSE; //Reset wMot1OPCode := 16#9E; //Disable Motor xMot1SendOP :=TRUE; //Send OP on rising edge xMot1SendOP := FALSE; //Reset Where "wMot1OPCode" is the IO map for writing to the command register, and "xMot1SendOP" is the rising edge trigger for that modbus channel. However, this doesn't work. The device never responds to the modbus commands. It seems like the trigger variable is switched too quickly for modbus to send the packet. I know the modbus register is working, because I can set the channel to cyclic and the device will respond. However, I can't use this reliably because I need each command to be sent once, in order. Cyclic keeps re-sending the commands and seems like it could miss a command as well if one was sent in-between cycle time. I have also trying using the Application trigger as described by https://faq.codesys.com/pages/viewpage.action?pageId=24510480, but this is also not working for me. See attached picture for my FBD code. This seems like a simple function, I can't tell what I'm doing wrong here. Thanks for the help.
Last updated: 2024-03-06

Sort by relevance or date