Request a dark mode for CODESYS ^{CODESYS Forge talk (Thread)}
Request a dark mode for CODESYS
Last updated: 2026-01-21

Post by janber0206 on Adding PLC to the List view resolves in Unknown Error ^{CODESYS Forge talk (Post)}
Problem Solved The Problem was within the Usermanagment. There should be 6 files for the Usermanagment in /var/opt/codesys/ .UserMgmtDB.csv .UserMgmRightstDB.csv .GroupDatabase.csv .UserDatabase.csv_ .GroupDatabase.csv_ .UserDatabase.csv The file .UserMgmtDB.csv was missing. I moved the other files in a savefolder. Full Step by step instructions stop the runtime with sudo /etc/init.d/codesyscontrol stop rename the following files on the PI: (or save them and then delete them) in this directory: /var/opt/codesys/ .UserMgmtDB.csv .UserMgmRightstDB.csv .GroupDatabase.csv .UserDatabase.csv_ .GroupDatabase.csv_ .UserDatabase.csv then restart the Runtime: sudo /etc/init.d/codesyscontrol start now reconnect the PLC via the Automation Server - here you will be asked to create a new CODESYS user password, The user management files deleted above are then created again (in /var/opt/codesys/ on the PI).
Last updated: 2025-02-24

Post by askjong on Update variables when OPC UA Client updates. Error ID: 268468277 BadAttributeIdInvalid ^{CODESYS Forge talk (Post)}
Hi, I'm connecting to a OPC UA Server using the Data Soruce Manager OPC UA Client. This works well until the OPC UA Server updates and the OPC UA list doesn't match up when i did last clicked the "Update variables" to add variables. All the variables are still the exists and none are removed from the server, but more are added during the engineering process. The error message i get in CODESYS is "Error in OPC UA call BadAttributeIdInvalid, Error ID: 268468277". The issues is fixed when i press the "Update variables" button and just press ok without adding or removing any variables in the list. Is there a way to either automatically update the browsepath if it fails or on startup, or to trigger it by code?
Last updated: 2024-01-08

Post by fless on Warning C0564 when compiling CNC project with variables program ^{CODESYS Forge talk (Post)}
Update: We managed to avoid the warnings by changing the order of initialization by adding an attribute to the GVL with the variables. {attribute 'global_init_slot' := '49989'} The variables are initialized right before the regular GVLs (default GVL slot 49990). Note to Codesys: I see the problem, Codesys needs to initialize the CNC objects before the GVLs so they can be used in the GVL. But then you can't use variables from GVLs in CNC programs. Maybe you could disable the warning in your generated CNC objects? At least a note for a workaround would have been nice.
Last updated: 2024-04-02

Is there a way to Connect Visualization to a web that the buttons can be used using a mobile phone? ^{CODESYS Forge talk (Thread)}
Is there a way to Connect Visualization to a web that the buttons can be used using a mobile phone?
Last updated: 2021-04-22

Is possible to transform a .sqlite file generated by a Trend Recording object to a .csv file? ^{CODESYS Forge talk (Thread)}
Is possible to transform a .sqlite file generated by a Trend Recording object to a .csv file?
Last updated: 2017-12-22

Post by mikek10 on Ethernet/IP 4.6.0 causing exceptions? ^{CODESYS Forge talk (Post)}
Hi, I have a project currently in development, it has a number of Ethernet/IP devices (18 adapter devices with Codesys as scanner, another scanner device with codesys as adapter). This has been stable whilst on factory floor for several months (though prior to that I did have some Ethernet/IP issues which were resolved by adjusting RPI rates). Today I tried updating to Ethernet /IP 4.6.0 from 4.5.1, subsequent to this I had 2 exceptions in a 2 hour period, I reverted to 4.5.1 and have had no further exceptions. Note I do have a device (Zebra printer) that frequently times out and reconnects, this does not seem to cause any issues in operation and does not cause any exceptions with 4.5.1. I believe the root cause of this is on the Zebra side, however there does not seem to be any adjustment I can make to prevent the time outs. Information from device log is in screenshot attached.
Last updated: 2024-06-27

Post by pernockham on Linking to IO during runtime with hot swap? ^{CODESYS Forge talk (Post)}
I have a project where a single PLC shall control multiple nodes (up to 10 units?) with IO connected through profinet. Ideally each node should be identical however with time I see situations were different setups/configurations will be used. Codesys PLC (GVLs) |Profinet | |--PNIO-node-1--| | | AIO, | | DIO, | | CNT etc. | |--PNIO-node-2--| | | AIO, | | DIO, | | CNT etc. Ideally I think of a configuration through yaml/xml-files (the assignment/linking of the profinet nodes towards GVL-variables in the PLC as well as scaling, channel configration etc.). Would be grateful if someone could suggest library/-ies that can handle the following: - Verify what IO is connected to a device/node. - Hot-swap/assign link for IO towards GVLs, either automatically or through a HMI.
Last updated: 2024-10-11

Post by george32 on TCP Server ^{CODESYS Forge talk (Post)}
Dear people, I would like to create a TCP server in my PLC program. The TCP server needs to communicate with an external device. I have been searching the internet and found that the libraries Syssocket or CAA NetBaseSrv are two possible solutions to create a TCP server. From what I have read, CAA NetBaseSrv is more user-friendly to implement than the Syssocket variant. However, I am still struggling to actually implement this library. Foremost is my little knowledge about creating a TCP server and how to read/understand each function block, especially the outputs of some blocks and the types, e.g. server has an output CAA.Handle, but I cannot find the explanation of CAA.Handle. I tried to find a good document that can help me understand how to implement a TCP server, but I could not find it. Thank you in advance, George
Last updated: 2025-02-20

Post by thn-power on Updating OPC UA Core Nodeset on PLS ^{CODESYS Forge talk (Post)}
Hi After much trail and error I think I found the root cause to my OPC UA problem. The problem is that I cannot manage to build and download a program with a a custom OPC UA Information model. We use a Weidmueller WL2000 PLS, but the problem also exsist on the Win V3 PLC. Our custom information model is based on the latest versions of the OPC UA Core Nodeset v 1.05.03 (2023-09-20) and UA/DI nodeset 1.04.0 (2022-11-03) Those nodesets are installed in the Codesys Information Model Repository (3.5.19.6) However, when trying to build I get the following error. [ERROR] Untitled1: Communication Manager [Device: PLC Logic: Application]: The information model http://opcfoundation.org/UA/ is required by http://bos.org/ with a minimal publication date from 15.12.2023 but the device has only a model from 15.09.2021 installed. Probably the information model from 15.09.2021 is missing in the information model repository. [ERROR] Untitled1: Communication Manager [Device: PLC Logic: Application]: The information model http://opcfoundation.org/UA/DI/ is required by http://bos.org/ with a minimal publication date from 03.11.2022 but the device has only a model from 09.03.2021 installed. Probably the information model from 09.03.2021 is missing in the information model repository. Build complete -- 2 errors, 1 warnings : No download possible I think the problem is that the UA Core nodeset is implemented in the PLC firmware (at least that in Siemens S7), and that only includes the "old" nodeset from 2021-09-21 etc. So the question is, how (or if?) can I transfer the new nodeset to the PLS? I have created separate Information models under Communication manager with the newer code nodesets (UA and DI). But it seems that the compiler does not recognize them being excising, neither in the Codesys IDE or on the PLC. Would have guessed that this is a common issue, sine many manufacturers use the latest versions of the OPC UA standard, and that it would be a solution to the problem.
Last updated: 2024-09-20

Post by arundara on Variable Sync Issue In Soft Plc Redundancy ^{CODESYS Forge talk (Post)}
Hello, I was trying to create a redundancy POC for our application where we read data from few modbus tcp devices. As there is a limitaion that modbus tcp device support only for single master device, we wanted to test how the variable sync happens in redundancy mode. For that i have used the redundancy sample code added a variable "b" under a condition. What i observed was while active controller is running, if passive controller is powerup, passive controller is able to sync all the data configured for redundacny. But after that the variable data which resided under a condition is not synching from active to passive controller. I have attached the image where i have highlighter the variable. Can some help me to understand how redundacny work in codesys soft plc and if there is a solution to sync variable which are under condition, please explain the same or suggestion to achieve the same. Hardware - Raspberry Pi (2 qty) Redundancy licence used - yes in both controllers. Codesys runtime - 4.9.0.0 Codesys software version - V3.5 SP19 if i have posted this question in wrong section, please do let me know in whcih section i have to post this question.
Last updated: 2023-12-01

Post by alexgooi on Codesys KNX implementation ^{CODESYS Forge talk (Post)}
Dear forum, We are currently doing some research on the Codesys KNX implementation (https://store.codesys.com/en/codesys-knx-sl.html). We almost have it working but we are missing the last part. The setup: We have a Codesys virtual control container running on docker (4.17.0.0), the I/O is running over an Ethernet IP coupler (Weidmüller), and this is running fine. As far as I’m concerned this tells me that the ethernet device is working properly (the container has access to the outside world, including multicast). Underneath this ethernet adapter the KNX module is added (see picture). In the KNX device (Codesys) 2 input variables are added (see picture), and these are exported to ETS (ETS 5). In ETS A Codesys KNX device has been imported and the Codesys export was imported, afterwards the group addresses are attached to the variables (see picture). Afterwards this configuration is downloaded to the Codesys controller (Container) via ETS. ETS asks for the pressing of the programming button, when the virtual programming button is pressed the download starts and finishes without any errors. This tells me that ETS is communicating with the Codesys controller, and that the download process is ok (so far so good). Now the part where we are struggling with, somehow we need to convert the KNX TP to KNX IP. For this we have the following interface: Zenio KIPI SC (https://www.zennio.com/product/kipi-sc/) this is a KNX TP to IP interface. We have the following setup for this device (see picture) (an IP in the same subnet is used). We tried multiple combinations of IP addresses but the TP devices are simply not communicating to the Codesys container. Does anyone has any advice on what to try next. To make the question more explicit how can we link the TP bus to the Codesys device? Kind Regards Alex
Last updated: 2026-01-05

Post by leandroct on Creating Boot Application not working ^{CODESYS Forge talk (Post)}
I have a Control Win V3.5 SP20 (64-bit) application, and until now, I open the program (with a password) and download it. However, I need to give the client the option to install the program on the Controller, without them having to open it and access the code. So, I followed these steps: 1 – In the Online => Create Boot Application menu, I saved the generated files in a directory: Application.app Application.crc PlcLogic\visu\ directory with several files 2 – In the SysTray, I ran the PLC, and it created a directory. In the root of this directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E84889DB), I pasted Application.app and Application.crc. Since it created a \visu directory, I pasted the PlcLogic\visu\ files generated in Create Boot Application into it. 3 - In the general Codesys directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64), I edited CodesysControl.cfg, adding: [CmpLog] Application.1=Application 4 - When running the PLC, nothing happens and the TargetVisu screen does not open. What I'm doing wrong?
Last updated: 2025-09-03

Post by rabaggett on CODESYS control for Raspberry Pi 64 SL errors ^{CODESYS Forge talk (Post)}
Hi, I am trying to create a project using a raspberry pi, I have added the modules for the Pi and MCP3008. I have encountered som errors that I don't know how to track down. 1. The GPIOs give preprocessor errors, but I read that this does not prevent compiling. This seems to be true. I can build the empty project with no errors. 2. After adding a SPI master and MCP3008, the preprocessor errors double, but seem similar and the project again builds with no errors. 3. I add a DUT and GVL, with a function, and I get the following errors. They remain even if I delete these things. ------ Build started: Application: Device.Application ------- Typify code... [ERROR] crr: C0032: Cannot convert type 'Unknown type: 'ADR(GVL_Io_17160064_c083_41f8_9e53_208be7537753_HPS_7.Io_17160064_c083_41f8_9e53_208be7537753_HPS_7)'' to type 'POINTER TO IoConfigParameter' [ERROR] crr: C0077: Unknown type: 'GVL_Io_17160064_c083_41f8_9e53_208be7537753_HPS_7.Io_17160064_c083_41f8_9e53_208be7537753_HPS_7' [ERROR] crr: C0046: Identifier 'GVL_Io_17160064_c083_41f8_9e53_208be7537753_HPS_7' not defined Compile complete -- 3 errors, 0 warnings I attach the project. What am I doing wrong? Thanks!
Last updated: 2024-05-02

Post by timvh on Licensing info not available. ^{CODESYS Forge talk (Post)}
In the VPLC configuration settings there is an entry for the IP address of the license server. In this setting fill in the IP address of your device (host IP address). Then when the virtual PLC starts up, it will get the license from the license container on the host. You can do this for all VPLC's running on your device. The VPLC will always take the smallest license which fits the required license. So if you have 2 licenses for VPLC's with small and large applications, then this will work fine if you start up one VPLC which requires the small license and the other which requires the large license. PS, personally I find it much easier, especially for testing and experimenting, to activate the licenses on a CODESYS (USB) key. This is easy to activate (on your development PC) and easier to move to another device. Addtionally you don't loose the license when you need to install a completely new image on the device.
Last updated: 2025-10-02

Post by abinvest579 on TCP Client ^{CODESYS Forge talk (Post)}
Hi All, I am using codesys based plc to read and control magna power DC supply over LXI protocol using SCPI command. To connect device required socket programming for that i am using Net base service library function block TCP_Client to establish connection over TCP/IP , TCP_Write to write SCPI commands and TCP_Read to read data from Magna power DC supply. I have attached screenshot for logic developed. I am able to connect and write commands to device but i not receiving any information from device. For writing Commands i also tried various end of line character like \n,<nl>, A, D, 10, 13, 0x0A, 0x0D but not received any status from device. For testing purpose i am using simple command '*IDN?' to read data. Also if tried to check on hercules software what data actually plc read, first it read correct data after that is read wrong data as see in screen shot. 'Hello World' was correct read and after that Codesys in replaced with 'Codesysorld' that is not correct way. Same issue also appeared for send data. Any one have face same issue how i can read data directly from device correctly and send data please suggest solution on this.</nl>
Last updated: 2024-07-01

Post by eschwellinger on Device User Logon and No device is responding.. Pi4b codesys 3.5 SP19 2 + (64-bit) ^{CODESYS Forge talk (Post)}
CODESYS runtime version 4.9.0.0 for your Pi. ssh user should be pi. This is for RasperrPi Os 32 bit. If you are on RasperryPi OS 64Bit use Arm 64bit SL product as Runtime.
Last updated: 2023-09-11

Post by shabroz-gill on Unable to load boot application on ARMv7 device restart ^{CODESYS Forge talk (Post)}
The boot application already exists on the device, i can see the MPC.app file in the proper place. It is not able to load it on startup though
Last updated: 2023-12-01

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 ton on Beckhoff EK series cannot detect but BK1120 detect ^{CODESYS Forge talk (Post)}
Hi, I guess you don't have the right xml file. Download Beckhoff_EtherCAT_BKxxx_MDP.zip from https://download.beckhoff.com/download/configuration-files/io/ethercat/xml-device-description and install these in Device Repository.
Last updated: 2024-11-01

Post by eschwellinger on CodesysHMI.exe: Start Error ^{CODESYS Forge talk (Post)}
Any changes on this device? Seems that you are missing the patch protection container. Copy this file to your device and execute it "c:\Program Files\CODESYS 3.5.20.30\Temp\Patch_Protection_Only_License.WibuCmRaU"
Last updated: 2024-11-01

Post by timvh on Device diagnosis ( EtherCAT IO card ) ^{CODESYS Forge talk (Post)}
You can get the state by just using the name of your node (same name as in device tree): VAR etcState: IoDrvEthercatDriverLib.ETC_SLAVE_STATE; END_VAR etcState := EJ1100.wState; Alternatively, you can iterate through the device tree to get the status of all (Ethercat) nodes. See here an example (no guarantee it works, just give as suggestion): PROGRAM P_IO_State VAR CONSTANT uiMAX_NR_OF_TERMINALS : UINT := 100; END_VAR VAR // general device diagnosis // can only be used when the Device - PLC Settings - Advanced settings - enable diagnosis for devices is enabled // this will add the DED library coupler: DED.INode; terminal: DED.INode; aDeviceState: ARRAY[0..uiMAX_NR_OF_TERMINALS - 1] OF DED.DEVICE_STATE; uiTerminalCount : UINT; uiIndex : UINT; // for each terminal check if it implements device diagnostics xQueryResult: BOOL; itfDevice : DED.IDevice2; xDiagAvailable: BOOL; eError: DED.ERROR; xEverythingOK: BOOL; END_VAR uiTerminalCount := 0; // start at the top of the device tree with the first EtherCAT coupler coupler := EtherCAT_Master.FirstChildNode; WHILE coupler <> 0 DO // for each coupler that is found start at the first terminal terminal := coupler.FirstChildNode; WHILE terminal <> 0 AND uiTerminalCount < uiMAX_NR_OF_TERMINALS - 1 DO // for each terminal that is found get the status through the device diagnosis interface xQueryResult := __QUERYINTERFACE(terminal, itfDevice); IF xQueryResult THEN aDeviceState[uiTerminalCount] := itfDevice.GetDeviceState(xDiagnosisInfoAvailable => xDiagAvailable, eError => eError); uiTerminalCount := uiTerminalCount + 1; END_IF terminal := terminal.NextSiblingNode; END_WHILE coupler := coupler.NextSiblingNode; END_WHILE uiIndex := 0; xEverythingOK := TRUE; WHILE uiIndex < uiTerminalCount DO IF aDeviceState[uiIndex] <> DED.DEVICE_STATE.RUNNING THEN xEverythingOK := FALSE; EXIT; END_IF uiIndex := uiIndex + 1; END_WHILE
Last updated: 2025-02-06

Post by timvh on "Do you really want to perform" dialog boxes ^{CODESYS Forge talk (Post)}
Double click on the device (communication settings). At the top of this Window, go to Device -Options. Disable the option "Confirmed online mode".
Last updated: 2025-02-15

Post by timvh on Import from XML problem ^{CODESYS Forge talk (Post)}
It is not an error, but just an information message. You need to select the correct location in your device tree where you want to import the objects. E.g. select Application below your Device.
Last updated: 2025-04-30

Post by dkugler on Version management ^{CODESYS Forge talk (Post)}
If you update all to the newest versions in the project environment and update all devices in the device tree, the errors should gone! Missing the device updates is often causing this problems!
Last updated: 2025-05-28

Sort by relevance or date