Post by fless on FB having single input but initialized with Array ^{CODESYS Forge talk (Post)}
Why will it retain the sum value from the last call? This is how PLC work. Usually variables only get initialized after a download or a reset (i.e. power loss). RETAIN variables are saved in a special kind of RAM and keep their value after a power loss. To initialize variables on every call of your FB use the VAR TEMP block. VAR_TEMP sum : INT; END_VAR
Last updated: 2024-05-07

Post by ofey on Codesys Soft PLC OPC UA server ^{CODESYS Forge talk (Post)}
Hi! I'm sorry if this has been asked before. I have tried looking up previous topics regaring this, but even though I'm following tutorials and other posts I cant seem to get this to work consistently. I actually got the connection established on a test project after some trial and error. I only got it to work with the "Anonymous login". But after i deleted the test project and tried to get the same thing to work on another project I cant get it to work anymore. What I'm trying to do: Set up and OPC UA Server using CODESYS with the free soft PLC. I then try to connect to the OPC UA Server with the program "UaExpert". What happens: I get the error Error "'BadUserAccessDenied' was returned during ActivateSession". What I have done in CODESYS: - Added the object "Symbol configuration" and checked some test variables - Checked "Support OPC UA features - In "Communication settings -> device -> Change runtime security policy" I have checked "Allow anonymous login" What I have done in UAExpert: - Found the OPC UA server under "local". (It is showing two servers though, I do not know why. It showed the same when it worked yesterday). Se attachment - Checked "Anonymous" under "Authentication settings in the OPC UA server. I'm new to CODESYS, so it could be something elementary wrong in my settings. Maybe something in the user settings in CODESYS regarding user rights or something?
Last updated: 2023-09-14

Post by timvh on Toradex and CODESYS and licensing ^{CODESYS Forge talk (Post)}
For the Virtual Control you need to use a "Network license". The Virtual Control has parameters of which one is the reference to the license server. This can be the device itself, but you need to activate the license on the host system (not in the container). For this, CODESYS has a Network License server with WBM (web based management). See for the Network License configuration: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_license_controller_linux.html If it is only for evaluation, I would advise to use a CODESYS (USB) key and activate the license on the key. Then you still have to install the CODESYS Network License server on the host, but you don't have to activate the license as soft license on the device. The benefit is that you can easily move your license to another device when needed. Off course your device must have a free USB port available to be able to do this.
Last updated: 2025-10-20

Post by rer-code on Codesys 3.5.18.60 – Application Loss and Persistent Data Corruption ^{CODESYS Forge talk (Post)}
Hi, I’m currently managing over 50 PLCs running Codesys version 3.5.18.60. At seemingly random intervals, some of these devices experience a failure where: All persistent variables are lost. Attempting to log in results in the message: “The application does not exist on device. Do you want to create it and proceed with download?” The log shows: “Loading retain-data/bootproject failed.” From what I’ve gathered, this may be due to a corrupted persistent data file, but I’m not entirely sure how to confirm or resolve this issue. If anyone has encountered something similar or has suggestions for troubleshooting or preventing this, I would greatly appreciate your input. Best regards
Last updated: 2025-08-19

Post by mani-i4point0 on Issue with WebVisu on Raspberry PI ^{CODESYS Forge talk (Post)}
Hi, I am running Codesys Runtime by purchasing 'Codesys control for raspberry pi MC SL', I am trying to use the Variables from my GVL's. Few of the variables used as a Pushbutton form the Visualization. These 'BOOL' Variable getting unlatched automatically even though there is no write function in the Overall project. All of them are 'Read' functions, at the same time few other BOOL variable behaviors are seems to be fine. I have tried, clean all and download, serval time restarted the hardware. Happy to share any any information. Your input to resolve this issue would be highly appriciated. Version Details: codesyscontrol 4.8.0.0, armhf codesyscontrol based on SDK 3.5.19.0
Last updated: 2024-03-20

Post by winki on ModbusFB ClientRequest: never recovers after a single ReplyTimeout (requires full download) ^{CODESYS Forge talk (Post)}
Library: ModbusFB (CODESYS Modbus package) IDE / Runtime: CODESYS V3.5 SP___ / Control runtime ___ Target: ___ (e.g. gateway, Linux ARM64 / Debian) Slave: Modbus TCP inverter Summary I poll a Modbus TCP slave with a permanent connection: one ClientTCP (kept connected, xConnect:=TRUE) and one ClientRequestReadHoldingRegisters, triggered cyclically. Everything works fine after a fresh application download. But as soon as one single ReplyTimeout occurs (slave temporarily not answering), the request never recovers. It stays stuck and no further messages are sent, even though the TCP connection is still reported as alive. Only a full application download brings it back — an online change or a runtime reset is not enough / not what I want in production. State observed when stuck So the connection is alive, the request finished in ReplyTimeout, the FB is back to _state = None, but udiNumMsgSent no longer increases — as if a new rising edge on xExecute is no longer accepted / no longer produces a new message. My trigger logic (simplified) Each PLC cycle, in this order: If the request is fully at rest (NOT xExecute AND NOT xBusy AND NOT xDone AND NOT xError) and a read is pending, I set xExecute := TRUE. I call clientTcp() then clientRequest(rClient := clientTcp) once each, per cycle. On xDone or xError, I set xExecute := FALSE. I made sure to insert at least one full cycle with xExecute = FALSE (seen by the FB call) before re-triggering, so the falling edge is processed. Questions After a ReplyTimeout (xError = TRUE), what is the exact, correct sequence to re-trigger the same ClientRequest so a new message is actually sent again? Is a full cycle with xExecute = FALSE between two executions mandatory? Is there a known condition where, after ReplyTimeout, the ClientTCP keeps xConnected = TRUE but silently stops sending new requests (e.g. an internal request queue / _udiRequestId that gets out of sync)? udiNumMsgSent freezing at 23 while the FB shows _state = None is what puzzles me. Is the recommended pattern to drop the connection (ClientTCP.xConnect := FALSE for one cycle, then TRUE) on a request error, rather than keeping it alive? The docs state a request error does not close the connection, so I kept it open — but maybe that is the issue here. Could the large uiStartItem (50514) be relevant? It works right after download, so addressing seems correct, but I want to rule it out. Any guidance on the canonical recovery pattern after a request timeout would be greatly appreciated. Thanks!
Last updated: 2026-06-19

Post by rossanoparis on How to configure CODESYSControl_User.cfg in order to use a specific network card for OPCUA Server ^{CODESYS Forge talk (Post)}
Hello at all I'd like to know how to configure CODESYSControl_User.cfg in order to use a specific network card for OPCUA Server. In the past, I tried to ask in "Forge" about this topic, but I could find neither help nor document informations about it. Reading the file "codesyscontrol.log" I see these logs OPC UA Server Started: Hostname: NTLRPICTRL01, Port: 4840 URL: opc.tcp://NTLRPICTRL01:4840 Loopbackadapter activated. **All available networkadapters are used.** Multithreading activated. 3 workers used. My controller, which is a Linux PC, has got two network cards eth0 and eth1 I whant to use the card with name "eth0" as a server for OPCUA and keep the "eth1" free for other stuffs. Is it possible ? Best regards Rossano
Last updated: 2023-08-25

Post by mubeta on parker servo and position ^{CODESYS Forge talk (Post)}
Reading between the lines of what you did not specify, it therefore seems to appear that in the programme, at the end of the movement order, there is an order to remove power and switch off the pulse modulation. if this is the case, it is obvious that the motor then remains free. If the position is to be maintained at the end of the movement, the motor current modulator, which on the PLC side is controlled via the MC_Power method, must not be interrupted. Another possibility is that in the motor drive settings, the standstill torque current is set very low or zero and without position monitoring. You have to check this via the servo motor drive.
Last updated: 2024-08-05

CoDeSys libraries for BECKHOFF EL7332/EL7342 ^{CODESYS Forge talk (Thread)}
CoDeSys libraries for BECKHOFF EL7332/EL7342
Last updated: 2023-08-25

Import RsLogix 5000 project to Codesys ^{CODESYS Forge talk (Thread)}
Import RsLogix 5000 project to Codesys
Last updated: 2023-09-07

Codesys Control RTE V3. Remote Control ^{CODESYS Forge talk (Thread)}
Codesys Control RTE V3. Remote Control
Last updated: 2023-09-22

Recommended Specification for running CodeSys ^{CODESYS Forge talk (Thread)}
Recommended Specification for running CodeSys
Last updated: 2013-11-14

Kommunikationsunterbrechung zwischen CODESYS und RPi 3 ^{CODESYS Forge talk (Thread)}
Kommunikationsunterbrechung zwischen CODESYS und RPi 3
Last updated: 2017-02-20

CODESYS Development System V3.5.18.30 Installation Error ^{CODESYS Forge talk (Thread)}
CODESYS Development System V3.5.18.30 Installation Error
Last updated: 2022-12-07

CoDeSys OPC server with SIMULATION3 interface ^{CODESYS Forge talk (Thread)}
CoDeSys OPC server with SIMULATION3 interface
Last updated: 2016-02-24

Neues Forum zur CoDeSys OPC Anbindung ^{CODESYS Forge talk (Thread)}
Neues Forum zur CoDeSys OPC Anbindung
Last updated: 2011-04-14

Modbus übertragung von CodeSys nach Excel ^{CODESYS Forge talk (Thread)}
Modbus übertragung von CodeSys nach Excel
Last updated: 2010-08-01

CoDeSys V3 mit Raspberry Pi Kamera ^{CODESYS Forge talk (Thread)}
CoDeSys V3 mit Raspberry Pi Kamera
Last updated: 2016-05-05

Codesys Projekt läst sich nicht öffnen ^{CODESYS Forge talk (Thread)}
Codesys Projekt läst sich nicht öffnen
Last updated: 2017-12-10

CODESYS on RPI - tcpip socket ^{CODESYS Forge talk (Thread)}
CODESYS on RPI - tcpip socket
Last updated: 2022-07-14

Codesys V3 and Enron Modbus ^{CODESYS Forge talk (Thread)}
Codesys V3 and Enron Modbus
Last updated: 2022-11-09

PY Script aus CoDeSys Programm ausführen ^{CODESYS Forge talk (Thread)}
PY Script aus CoDeSys Programm ausführen
Last updated: 2017-01-25

CoDeSys 3 auf dem STM32 ^{CODESYS Forge talk (Thread)}
CoDeSys 3 auf dem STM32
Last updated: 2009-03-03

CODESYS + Funktionale Sicherheit SIL3/PLe ^{CODESYS Forge talk (Thread)}
CODESYS + Funktionale Sicherheit SIL3/PLe
Last updated: 2020-05-28

Sort by relevance or date