Motion 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Realizing single or multi axis motion control, CAM, CNC and Robotic applications
Last updated: 2026-10-16

Runtime 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Related questions to SoftPLCs e.g. Raspberry Pi, Beaglebone, IoT2000 and other platforms
Last updated: 2026-10-16

Post by john-robinson on Limiting Memory Access of an Array to Within its Bounds ^{CODESYS Forge talk (Post)}
Recently we had an issue regarding some simple code to calculate a rolling average. The code indexes from zero to 199 to properly store the current input into a circular buffer which then allows us to calculate a rolling average: VAR input_5s : REAL; outs_arr : ARRAY[0..199] OF REAL; i : USINT := 0; END_VAR ___ //this code runs every five seconds, calculating a rolling average outs_arr[i] := input_5s; i := i + 1; output := OSCAT_BASIC.ARRAY_AVG(ADR(outs_arr), SIZEOF(outs_arr)); IF i >= SIZEOF(outs_arr) THEN i := 0; END_IF There is a simple bug in this code where the index will be set to 0 when it has surpassed the length of the array in bytes (800 in this case) rather than larger than the number of reals in the array (200). The solution here is simple, replacing i >= SIZEOF(outs_arr) with i >= SIZEOF(outs_arr)/SIZEOF(outs_arr[0]). In this example when the index increased to 201 and the line outs_arr[201] := input_5s was called, codesys arbitrarily wrote to the address in memory that is where outs_arr[201] would be if the array was that long. I would like to find a way to wrap the codesys array inside of a wrapper class that checks if an input is within the bounds of an array before writing to that value. I know how I would implement that for a specific array, I could create a method or class that takes an input of an array of variable length, ie. ARRAY[*] OF REAL, but I don't know how to make this for any data type. I am wondering if anyone has ever done anything similar to this, or has any better suggestions to ensure that none of the programmers on this application accidentally create code that can arbitrarily write to other locations in memory.
Last updated: 2024-03-05

Post by leandroct on Error reading files after runtime update from 4.0.0.0 to 4.8.0.0 ^{CODESYS Forge talk (Post)}
Since version 19 they changed how file access is handle. There are two solutions: 1. You change where the file is stored (need to go to: /PlcLogic/) 2. You can, if you don´t want to store at PlcLogic, add the following line in the CODESYSControl.cfg under [SysFile]: ForceIecFilePath=0 The CodesysControl.cfg is at C:\ProgramData\CODESYS\CODESYSControlWinV3x64\xxPROJECT_NUMBERxx\ Here the email they sent me: "with the 3.5.19 Version we changed how files are handled. See following issue: CDS-81506 - CODESYS Control SysFile system file access vulnerability. There are two solutions: 1. You change where the file is stored (need to go to: /PlcLogic/) 2. You can, if you don´t want to store at PlcLogic, add the following line in the CODESYSControl.cfg under [SysFile]: ForceIecFilePath=0 Here is the official release-note: [[COMPATIBILITY_INFORMATION]] With the activation of ForceIecFilePath the file access from IEC is now restricted to the configured paths only (file sandbox)! [SysFile] ForceIecFilePath=1 (new default) The standard path is the current directory, the PlcLogic subfolder or a configured path. Every file access outside of this path is configured via PlaceholderFilePath, for example access to temporary files or removable media: [SysFile] PlaceholderFilePath.1=/tmp, $TMP$ PlaceholderFilePath.2=/media/usb, $USB$ PlaceholderFilePath.2.Volatile=1 For more information see our tutorial FilePath & Placeholders. To restore the old behavior ForceIecFilePath may be configured as follows: [SysFile] ForceIecFilePath=0 BUT WE HIGHLY RECOMMEND TO LEAVE THIS SETTING AT ITS NEW DEFAULT VALUE! "
Last updated: 2024-05-07

Post by nativemode on V3.5 SP19 C-Code-Module nicht auffindbar ^{CODESYS Forge talk (Post)}
Nachtrag: vom CODESYS-Support habe ich jetzt die Antwort erhalten, dass es nicht mehr möglich ist, C-Dateien direkt zu integrieren. Man kann aber immer noch mit vorkompilierten C-Bibliotheken arbeiten: https://content.helpme-codesys.com/de/CODESYS%20Development%20System/_cds_integrating_c_code.html
Last updated: 2023-08-23

Post by jinil on Import RsLogix 5000 project to Codesys ^{CODESYS Forge talk (Post)}
Hello, I am trying to do the same thing. I want my Rslogix 5000 project into Codesys. Was wondering if you have found a way to do it. Thank you.
Last updated: 2023-09-07

Post by jinil on Import RsLogix 5000 project to Codesys ^{CODESYS Forge talk (Post)}
Hello, I am trying to do the same thing. I want my Rslogix 5000 project into Codesys. Was wondering if you have found a way to do it. Thank you.
Last updated: 2023-09-07

Post by nyee on Project compiling error in Simulation mode ^{CODESYS Forge talk (Post)}
Hi, I have a similar issue - we have been using codesys V3.5.16.20 Do you have any suggestions or confirmation that this will work with a different version of codesys and Pi extension
Last updated: 2023-09-07

Upgrading CODESYS runtime from v4.7 to v4.9 using a bash script leads to lose the licences stored in the soft container ^{CODESYS Forge talk (Thread)}
Upgrading CODESYS runtime from v4.7 to v4.9 using a bash script leads to lose the licences stored in the soft container
Last updated: 2023-09-19

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 janber0206 on Lizenz lässt sich nicht aktivieren für Revolution Pi ^{CODESYS Forge talk (Post)}
Problem gelöst: alle Lizenzen die vor Oktober 2022 gekauft wurden, müssen von Codesys aktualisiert werden. Dafür einfach den Support anschreiben im Codesys Store.
Last updated: 2023-10-30

How to use more 4 instances of CANopen/Profibus/Modbus with The application-based license CODESYS Control ^{CODESYS Forge talk (Thread)}
How to use more 4 instances of CANopen/Profibus/Modbus with The application-based license CODESYS Control
Last updated: 2023-11-02

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 totorovic on Codesys Softmotion Win V3 x64 ^{CODESYS Forge talk (Post)}
You have to update the device in your IDE to 3.5.14 or you can contact your Codesys runtime supplier to know how to set the connected system to 3.5.19
Last updated: 2023-11-09

Post by mybackingtracks on Codesys Control Raspberry PI 4.10.0 - missing 'Update Raspberry PI' option ^{CODESYS Forge talk (Post)}
I have updated Codesys Control Raspberry PI form 4.8.0 to 4.10.0. After I did it, 'Update Raspberry PI' disappeared from the 'Tools' menu How to solve it?
Last updated: 2023-12-06

Post by i-campbell on Codesys 3.5 Library Download Failed ^{CODESYS Forge talk (Post)}
You use very old codesys, maybe SP13? the newer sp17 libraries are in a format not compatible with your version. I suggest upgrading everything to at least SP17, but may as well go to SP20 Patch 2.
Last updated: 2024-08-21

Post by petrus on Redundancy Codesys Runtime, Synchronization ^{CODESYS Forge talk (Post)}
Hello, Has anyone figured out the Standalone issue after a network break? I have the similar behavior with two 750-8212 WAGO controllers. Using firmware 27 and CODESYS 3.5.19.70.
Last updated: 2024-08-22

Sort by relevance or date