Post by janber0206 on RPI is license server down ^{CODESYS Forge talk (Post)}
I had the same problem. Problem solved: all licences purchased before October 2022 must be updated by Codesys. To do so, simply contact the support in the Codesys Store.
Last updated: 2023-10-30

Post by eschwellinger on OPCUA Ctrl-Node fehlt ^{CODESYS Forge talk (Post)}
..dann mal im WBM alles deaktivieren, da der OPC UA Server ja direkt im PFC200 SL RUntime integriert ist und nicht über die WBM Oberfläche zu konfigurieren ist.
Last updated: 2023-12-05

Post by hwopereis on How to use Application Trigger in Modbus TCP Server ^{CODESYS Forge talk (Post)}
I'm now circumventing the problem by creating a separate TCP client for all Write actions. Upon registering a changed variable, I enable this client, until the change is processed.
Last updated: 2024-07-01

Post by shabroz-gill on Data Sources Manager causing exception due to float or double type in OPC server ^{CODESYS Forge talk (Post)}
Was this ever resolved? I see the same issue with the version 3.5.19.5
Last updated: 2024-07-01

Post by elayaraj on Codesys Soft PLC OPC UA server ^{CODESYS Forge talk (Post)}
Hi, You may refer to this below video link to get some idea.. hopefully it works https://www.youtube.com/watch?v=RBMff-IlPA4
Last updated: 2024-08-30

Post by reinier-geers on Syssockping hang up V3.5.9.2 ^{CODESYS Forge talk (Post)}
For data logging on a server i check the connection with Syssockping. When i do that it seems to hang uo the system once a while for 13 seconds. Why ??
Last updated: 2024-09-02

Post by arfoto on Gateway ^{CODESYS Forge talk (Post)}
Merhaba Gateway config moda almak istediğimde BU hatayı alıyorum. maalesef bu sorunu çözemiyorum amacım softplc yi Automation Server a Bağlamak Ama maalesef config moda giremiyorum dosya yolumda C:\ProgramData\CODESYS\CODESYSGatewayV3 bu şekilde. Teşekkür ediyorum.
Last updated: 2024-09-17

Post by fmbrew-rob on Licensing info not available. ^{CODESYS Forge talk (Post)}
I do have a license server installed. Can you point to a document or ANYTHING that shows how to configure this virtual control to properly do licensing?
Last updated: 2024-09-24

Post by astrum on OPC UA Client Zertifikate in "Vertrauenswürdige Zertifikate" verschieben ^{CODESYS Forge talk (Post)}
Hallo zusammen, gebe es eine Möglichkeit die Client Zertifikate aus dem Quarantäne Bereich zu den Vertrauenswürdige Zertifikaten zu verschieben, und das ohne die Codesys-Umgebung ? Der OPC UA Server läuft über eine Delta Steuerung die über Codesys eingerichtet wurde.
Last updated: 2024-10-10

Post by mainak on OPC UA C# client connecting to OPC UA CODESYS server ^{CODESYS Forge talk (Post)}
it could be due to security settings. In codesys IDE, go to device-> change run-time security policy, and click the checkbox that says "Allow anonymous login". try if this works.
Last updated: 2024-10-19

Post by banialuk on Modbus TCP Server ^{CODESYS Forge talk (Post)}
Hello, I have poroblem with define input in function block modbusFB.serverTCP 'dataModel', in my aplication I need starting Input Registers from 3000, and I must define this in 'data Model' but I dont now how exacly to do it. Anybody now somethin about this?
Last updated: 2024-10-19

Post by tmo21 on Automation server - trends stop recording - need to manually reconnect ^{CODESYS Forge talk (Post)}
Hi Edwin, Thanks for your message. Edge controller Version: 4.4.0.0 based on 3.5.17.30 PLC version: Device Identification Name CODESYS Control for Raspberry Pi MC SL Vendor 3S - Smart Software Solutions GmbH Device type Softmotion3S Firmware version 4.4.0.0
Last updated: 2024-10-23

Post by dogulas on OPC UA C# client connecting to OPC UA CODESYS server ^{CODESYS Forge talk (Post)}
mainak, sorry, just saw your post. I have done that and I still get the same exception. the innerResult says "BadSecureChannelClosed 'Remote side closed connection'". Any other tips? Pointers are welcome.
Last updated: 2024-11-12

Post by askic on Howto disable OPC-UA service in BeagleBone Runtime ^{CODESYS Forge talk (Post)}
Hello I need this same information, but it is not available online anymore and the link is down. I'm not able to find this information in the online help. Does anybody know how to disable OPCUA server if not needed?
Last updated: 2025-01-10

Post by mandeepahujaifm on Exception when OPCUA datasource disconnects from Server ^{CODESYS Forge talk (Post)}
@eschwellinger - We are experiencing the exact same issue. RunTime 3.5.19.70 and IDE V3.5 SP21. It's 100% reproducible. All you have to do is disconnect the network cable for about 10 minutes. OPC UA Crashes and requires a reboot to fix.
Last updated: 2025-03-28

Post by dat422 on OPC UA Method - How to wait for result? ^{CODESYS Forge talk (Post)}
Hi, I am also interested to know on how to use the Codesys OPCUA Client to call methods from e.g. a python opcua server.
Last updated: 2025-03-28

Post by benemenn on OPC server in "Communication manager" ^{CODESYS Forge talk (Post)}
Same Issue here. If I understood correctly codesys plans to discontinue the classic SymbolConfigurations. But somehow, the CommunicationManager doesnt seem to support structures or arrays.
Last updated: 2025-03-31

Post by vincerex on SFTP access ^{CODESYS Forge talk (Post)}
hello everyone, is there a library or a way to access to SFTP server using Codesys? SysSocket library is only suitable for FTP it seems. I didn't find any other suggestion on the web Thanks for your help VinceReX
Last updated: 2025-04-01

Post by gurkan on OPCUA array max length? ^{CODESYS Forge talk (Post)}
2000 works. When testing with UA Expert there is a timeout from the OPCUA Server when trying to subscribe to the variable CPU do not seems to be to affected. The memory(RAM) however is building up
Last updated: 2024-02-19

Post by eschwellinger on OPC Da Server Code Meter Issues after Enabling License ^{CODESYS Forge talk (Post)}
it is mandatory to activate the OPC DA license into the 32-xxxxxx legacy container (not UFC) you need a remove ticket -> contact CODESYS store - my question to move the license
Last updated: 2024-05-03

Post by bryandimino on OPC Da Server Code Meter Issues after Enabling License ^{CODESYS Forge talk (Post)}
Additionally the license is loaded on the soft storage for my device but it shows up as invalid. I just activated it today.
Last updated: 2024-05-02

Post by timvh on Modbus TCP Server connection is ESTABLISHED but all holding registers are value 0? ^{CODESYS Forge talk (Post)}
Are you sure you need to read holding registers? Have you tried reading input registers?
Last updated: 2026-01-07

Post by fleaplc on Modbus TCP Server connection is ESTABLISHED but all holding registers are value 0? ^{CODESYS Forge talk (Post)}
Did you check the communication with a sniffer ? (ex. Wireshark) to check if the holding get to zero by a wrong writing (client initialization?) o something else?
Last updated: 2026-01-27

Post by danp1406 on Question about Demo License limitations for Modbus TCP communication and Fieldbus Instances ^{CODESYS Forge talk (Post)}
Hello everyone, I am currently working with CODESYS Virtual Control for Linux running in Docker on a Debian virtual machine. I am deploying my application using Deploy Control SL, and in my project I am using the ModbusFB library to implement Modbus TCP communication. My setup is the following: I am trying to establish a Modbus TCP connection between a virtual PLC (CODESYS acting as Modbus TCP Client/Master) and a Siemens S7-1200 PLC acting as a Modbus TCP Server. From the Debian VM, I can successfully ping the S7-1200 and verify that port 502 is open using tools like nc. Network-wise, everything appears to be correct. However, when running the application in CODESYS, I receive messages such as “Demo mode for Modbus/TCP Master started. Will expire and stop!” and socket errors like “ClientSocket.UpdateStatus socket error 111 disconnecting.” The ClientTCP block from the ModbusFB library attempts to connect, but the connection does not remain stable. My main question is whether the CODESYS demo license explicitly limits or interrupts Modbus TCP Master communication. Is it expected that in demo mode the runtime will automatically close sockets after some time or prevent stable Modbus TCP connections? I would like to confirm whether this behavior is normal when using ModbusFB in demo mode, or if I should continue troubleshooting the configuration. Additionally, I would like clarification regarding the “fieldbus instances” mentioned in CODESYS licensing options (for example, 2, 4, or 16 instances). What exactly is considered one fieldbus instance? Does one Modbus TCP Client block count as one instance? Does each active connection to a different device count separately? Do Modbus TCP Master and Server count independently toward the total number of instances? Finally, I would appreciate clarification on any other practical limitations of demo mode when using industrial communication libraries such as ModbusFB. Are there limits on the number of connections, number of requests, or communication duration? I am trying to determine whether demo mode is sufficient for testing a virtual PLC communicating with a Siemens S7-1200 over Modbus TCP, or whether a full license is required even for this kind of validation scenario. Thank you in advance for any guidance.
Last updated: 2026-02-25

Post by paulg on RasPi CAA Serial example - unexpected behavior during debug ^{CODESYS Forge talk (Post)}
I've trimmed down the CAA Serial Codesys example to only listen on one port but, when stepping through the Case structure in debug mode, it jumps out of the structure during a specific point in every scan (I'll point it out below after describing the setup and listing the code). I'm using a Pi 4 Model B, and I have an Arduino Nano Every plugged in via USB which is streaming the following serial message at 1 Hz: Time since opening connection: 1 s Time since opening connection: 2 s ...and so on. The Pi shows the Nano at /dev/ttyACM0 so I edited CODESYSControl_User.cfg to read: Linux.Devicefile=/dev/ttyACM The code in my PLC_PRG is (ignore some of the comments, I hadn't deleted them out from the original example): PROGRAM PLC_PRG VAR xStartTest : BOOL:= TRUE; iState : INT; xTestDone : BOOL;(* True, when the test was done succesfully *) (* Settings to communicate with the COM Port *) aCom1Params : ARRAY [1..7] OF COM.PARAMETER; como1 : COM.Open; comc1 : COM.Close; comw1 : COM.Write; comr1 : COM.Read; //sWrite : STRING := 'Test String!'; sRead : STRING(25); szRead : CAA.SIZE; xCom1OpenError : BOOL; xCom1CloseError : BOOL; xCom1WriteError : BOOL; xCom1ReadError : BOOL; END_VAR //This example shows the communication of two COM Ports with each other. //The first one writes a string of characters, which is read by the second one. //After successful execution, the two COM Ports are closed and the test is done. IF xStartTest THEN CASE iState OF 0: //The parameters are set for the COM Port aCom1Params[1].udiParameterId := COM.CAA_Parameter_Constants.udiPort; aCom1Params[1].udiValue := 1; // the correct Port should be adapted aCom1Params[2].udiParameterId := COM.CAA_Parameter_Constants.udiBaudrate; aCom1Params[2].udiValue := 115200; aCom1Params[3].udiParameterId := COM.CAA_Parameter_Constants.udiParity; aCom1Params[3].udiValue := INT_TO_UDINT(COM.PARITY.NONE); aCom1Params[4].udiParameterId := COM.CAA_Parameter_Constants.udiStopBits; aCom1Params[4].udiValue := INT_TO_UDINT(COM.STOPBIT.ONESTOPBIT); aCom1Params[5].udiParameterId := COM.CAA_Parameter_Constants.udiTimeout; aCom1Params[5].udiValue := 0; aCom1Params[6].udiParameterId := COM.CAA_Parameter_Constants.udiByteSize; aCom1Params[6].udiValue := 8; aCom1Params[7].udiParameterId := COM.CAA_Parameter_Constants.udiBinary; aCom1Params[7].udiValue := 0; //The first Port is opened with the given parameters como1(xExecute := TRUE, usiListLength:=SIZEOF(aCom1Params)/SIZEOF(COM.PARAMETER),pParameterList:= ADR(aCom1Params)); IF como1.xError THEN xCom1OpenError := TRUE; iState := 1000; END_IF //After a successful opening, the next state is reached IF como1.xDone THEN iState := 15; END_IF 15: // the reading process is started comr1(xExecute := TRUE,hCom:= como1.hCom, pBuffer:= ADR(sRead), szBuffer:= SIZEOF(sRead)); IF comr1.xError THEN xCom1ReadError := TRUE; END_IF //After completion the size of the written bytes are saved IF comr1.xDone OR comr1.xError THEN szRead := comr1.szSize; iState := 20; END_IF 20: // If everything was successful the ports are closed and the handles are released comc1(xExecute := TRUE,hCom:= como1.hCom); IF comc1.xError THEN xCom1CloseError := TRUE; END_IF IF comc1.xDone OR comc1.xError THEN iState := 25; END_IF 25: // The first port is closed and the used handle released xTestDone := TRUE; xStartTest := FALSE; iState := 0; como1(xExecute := FALSE); comw1(xExecute := FALSE); comc1(xExecute := FALSE); ELSE iState := 0; END_CASE END_IF I realize as I write this that the .udiPort should be 0 and not 1, but that shouldn't be causing the issue I'm seeing. I'm forcing xStartTest:=TRUE every scan so that I can step into each line and observe what's happening. What I see is that the port parameters are set and the port is opened with no errors, but the code jumps out of the case structure to the last line every time it reaches (and I step into) the iState:=15 line (at the end of the iState:=0 block). So every scan cycle it goes through the block for iState=0 and jumps out at the same spot. I'm a little new to PLC programming so I may be misunderstanding the flow, but shouldn't this case structure keep moving down in the same scan? If it only handles one case per scan, why doesn't the value of iState persist? Thanks! Update: I restarted the Codesys control today and I was then able to see an error for como1.eError of "WRONG_PARAMETER". I tried doing some digging and another post made me think I should add another line to CODESYSControl_User.cfg, so I now have: [SysCom] Linux.Devicefile=/dev/ttyACM portnum := COM.SysCom.SYS_COMPORT1 So now when I set .udiPort to 1, I get "NO_ERROR" but I also don't read anything from the port (i.e. szRead = 0 always). If I try setting the port to 0 (which I'm confused about, because I added a COMPORT1 line but the device shows on the Pi as ACM0), I get the "WRONG_PARAMETER" error again. Is there an easier way to troubleshoot the Pi and view what ports the Codesys runtime is actually able to see while the Pi is running?
Last updated: 2024-06-06

Sort by relevance or date