Scan devices hangs CODESYS ^{CODESYS Forge talk (Thread)}
Scan devices hangs CODESYS
Last updated: 2025-12-13

Estun servo with codesys ^{CODESYS Forge talk (Thread)}
Estun servo with codesys
Last updated: 2025-12-23

Monitor active Codesys connection ^{CODESYS Forge talk (Thread)}
Monitor active Codesys connection
Last updated: 2026-03-29

Codesys MODBUS RTU devices ^{CODESYS Forge talk (Thread)}
Codesys MODBUS RTU devices
Last updated: 2026-07-14

Codesys Installation problem ^{CODESYS Forge talk (Thread)}
Codesys Installation problem
Last updated: 2026-08-10

Redundancy Codesys Runtime, Synchronization ^{CODESYS Forge talk (Thread)}
Redundancy Codesys Runtime, Synchronization
Last updated: 2026-01-30

CODESYS and Github Copilot ^{CODESYS Forge talk (Thread)}
CODESYS and Github Copilot
Last updated: 2026-02-13

Codesys KNX implementation ^{CODESYS Forge talk (Thread)}
Codesys KNX implementation
Last updated: 2026-03-04

Codesys V2.3 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Forum about V2.3
Last updated: 2026-08-26

Post by simotion on Codesys Softmotion Win V3 x64 ^{CODESYS Forge talk (Post)}
I have a project in Codesys v3.5 sp19 patch2 that contains softmotion virtual axes. I want to simulation the code (softmotion) on the simulated plc on the pc. The controller in the project is a Codesys Softmotion Win V3 x64. I have started up the Codesys Softmotion Win 64 on the pc. However it seems a 3.5 sp14 controller. When trying to download the project, I get a message that target system is different from connected system (3.5.19 vs 3.5.14). How do I set the connected system to 3.5.20 (there seems no way to set the target system to 3.5.14
Last updated: 2023-10-04

Post by idalu on Profinet PN_Controller Issue, Network Adapter ^{CODESYS Forge talk (Post)}
i have a problem with Profinet on my project. I'm using Codesys RTE 3.5.19.50. When i download program to controller the ethernet is ok, PN_Controller is ok but every device i'm trying to connect is red with error "DCP no RealStationName". When i'm trying to Scan for Devices on PN_Controller there are no devices found. I have installed Codesys driver CmpEt1000Drv to my network adapter (i'm sure it is right intel pro 1000 model). I have noticed that when i installed codesys driver i'm no longer able to ping this network adapter (i can ping it when intel driver is installed). On my previous projects with runetimes i can ping it even with codesys driver installed. I have also tried to do downgrade of everything to version 3.5.19.20 and it not helped.
Last updated: 2024-01-17

Post by drbuzz on Communication Error (#0) for IFM controller ^{CODESYS Forge talk (Post)}
Hi Folks, Every time I use an IFM controller I always seem to run into a problem connecting to it. I get the Communications Error (#0). So I thought I would share some tips and tricks. Once the CANfox Cable (EC2112) cable driver is installed, you can use the yellow app in the sys tray to blink the lights on the cable. Confirm the cable works in the IFM maintenance software by connecting to the controller and reading the information on it. Make sure to download an OS into the controller (the light will go from a fast blink to solid green). In Codesys V2.3, the communication settings for the CR0401 is 250kBaud by default and Node ID 127. What got me, was I needed to reboot the computer after the cable driver install. Also if your application has canbus settings in it which are changed from default, after the controller is power cycled, the new Node ID and Baud will be in effect. I made a handy guide because too much time has been wasted on this. Programming IFM CR0401 Serial/Can Programming Cable • Connect IFM EC2112 CanFox programming cable with connector adapter. • Make sure cable is linked to VM (if using VM). • Install drivers for cable if not installed. o Download from IFM EC2112 site. https://www.ifm.com/ca/en/product/EC2112 • Once Installed, reboot computer. • In system tray, there should be a yellow icon that you can open and check on programming cable. Select the cable in the list and flash the lights to confirm it is working. Maintenance Software • Install IFM Maintenance Tool Software. o Download from IFM Site. https://www.ifm.com/ca/en/download/eco100_MaintenanceTool • Open IFM Maintenance software • Select Basic System • Select CAN cable • It will tell you if you don’t have a cable connected. • Use Wizard if needed. • Read Channel Parameter on the Settings page, or get Identity in the System Information > Identity. • Default Node is 127 on a new unit. Baud is 250kBaud (bits/sec) • Controller information should populate. • Controller green light should be blinking at 5hz (meaning OK but no OS, just bootloader). • Click Software > Load. • Open the OS file. Should match Codesys version selection (for CR0401 this is version 3). o Download OS file from IFM Website. https://www.ifm.com/ca/en/product/CR0401 o It is located at the top of the download under “software for CR0401”. o Select the file and load it… this will take a minute. • Once completed the unit should now have a solid green light o Solid green means the controller has an OS but no application is running. Codesys V2.3 Application • Codesys needs to be downloaded and installed from the IFM website as it has the IFM libraries and license to use the software. o Download from the IFM CR0401 page. o https://www.ifm.com/ca/en/product/CR0401 • Create new application with the correct IFM controller or Open Codesys application. • Keep in mind that the PLC Configuration on the Resources tab can be changed for the CAN communication interface… so changes to node and baud will take effect after the first download and reboot of the controller. • Go to “Online” in the top menu and change “Communication Parameters” o The Local dropdown shows the last configuration used. All other interfaces will show below it and need to be updated when changed or used. o Confirm Node ID is 127 for the first download.  The NodeID will change to whatever the program has after (in my case 125).  Node Send Offset should be default at 1536  Node Recv Offset should be default at 1408  Can bus Baudrate should be 250 kbaud.  Yes to Motorola Byte Order  Block Transfer should be false and note used (60 is default setting).  Can Card Driver should match the systray item which is Sie_USB. • If the system populated the other one, just update and relay the communication parameters. The software will usually bring up the available cable and driver. • Go to “Online” and Login to download. o Press Yes to Download Application. I hope this helps!
Last updated: 2025-03-21

Post by artplc on 3.5 P20 hangs - no response ^{CODESYS Forge talk (Post)}
Subject: Solution: CODESYS Freezes Linked to Large Symbol Configuration (OPC UA) Hello everyone, I was experiencing the same problem as many here: CODESYS (v3.5 SP20+) freezing during compilation and download, especially on projects that use OPC UA for SCADA. The only workaround was to run Build > Clean all before every download. I believe I have found the root cause and a permanent solution. The Problem: The issue is directly related to a large Symbol Configuration. In my project, I only need about 700 tags for OPC UA, but the Symbol Configuration list was showing over 250,000 tags. This is because it automatically includes all variables from Global Variable Lists (GVLs) and other memory areas. When any static variable is changed, the IDE tries to rebuild this enormous list, causing it to freeze for several minutes. The Solution: Instead of letting CODESYS export every variable by default, you can use a pragma to tell it which variables or GVLs to exclude from the symbol export process. Place the following pragma at the top of any GVL or data structure that you do not want to be part of the symbol configuration: 1 {attribute 'symbol' := 'none'} 2 VAR_GLOBAL 3 // All variables in this GVL will now be excluded from the 4 // Symbol Configuration by default. 5 InternalVariable1 : INT; 6 InternalVariable2 : BOOL; 7 END_VAR After adding this pragma to all the GVLs that were not needed for OPC UA, the number of tags in my Symbol Configuration dropped to the correct amount. The compilation and download process is now fast again, with no freezing. This method is much more efficient than manually managing the symbol list in the editor. I hope this helps others who are facing this frustrating issue. Best regards.
Last updated: 2025-08-10

Codesys - Como Resetar a senha do Codesys ControlWin ^{CODESYS Forge talk (Thread)}
Codesys - Como Resetar a senha do Codesys ControlWin
Last updated: 2023-08-21

Codesys Control for Linux & Codesys Control for Linux ARM ^{CODESYS Forge talk (Thread)}
Codesys Control for Linux & Codesys Control for Linux ARM
Last updated: 2021-08-03

Codesys <-> Logo OBA7 Kommunikation | C++, Java oder Codesys ^{CODESYS Forge talk (Thread)}
Codesys <-> Logo OBA7 Kommunikation | C++, Java oder Codesys
Last updated: 2016-12-22

Read codesys version in the codesys application ^{CODESYS Forge talk (Thread)}
Read codesys version in the codesys application
Last updated: 2025-01-20

CODESYS Security Key vs CODESYS Runtime Key ^{CODESYS Forge talk (Thread)}
CODESYS Security Key vs CODESYS Runtime Key
Last updated: 2016-09-13

Conversion from CoDeSys 2 to CoDeSys 3 ^{CODESYS Forge talk (Thread)}
Conversion from CoDeSys 2 to CoDeSys 3
Last updated: 2013-10-17

etablish communication between codesys 2 and codesys 3 ^{CODESYS Forge talk (Thread)}
etablish communication between codesys 2 and codesys 3
Last updated: 2017-08-18

Licensing Codesys control for raspi without using codesys software ^{CODESYS Forge talk (Thread)}
Licensing Codesys control for raspi without using codesys software
Last updated: 2023-04-12

Copy a program IL from codesys 2 to codesys 3 ^{CODESYS Forge talk (Thread)}
Copy a program IL from codesys 2 to codesys 3
Last updated: 2017-02-27

How to open a Codesys V2.3 project in Codesys V3.5 ^{CODESYS Forge talk (Thread)}
How to open a Codesys V2.3 project in Codesys V3.5
Last updated: 2018-03-23

share data between codesys and non-codesys application ^{CODESYS Forge talk (Thread)}
share data between codesys and non-codesys application
Last updated: 2016-03-03

Sort by relevance or date