Post by shivsrikakolum on Getting SMC_ERROR 34 SMC_AXIS_NOT_READY_FOR_MOTION, while the axis should be ready for motion ^{CODESYS Forge talk (Post)}
how did you manage to get rid of the error. i have set the cycle time to 2000 microsecond but my softaxis is still amber warning
Last updated: 2026-07-07

Post by arj3090 on Beckhoff CX9240 : Using Internal EtherCAT Bus ^{CODESYS Forge talk (Post)}
I installed Linux ARM SL and it recognizes the RJ45 ethernet ports, but I cannot get it to recognize the internal port for the IO cards.
Last updated: 2026-07-10

Post by charly29160 on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
Hi, after updating CODESYS Control for Raspberry Pi SL from patch level 18 to 21 (currently 4.21.0.0), the IoDrvGPIO driver ("GPIOs B+/Pi2") can no longer open any GPIO chip on a Raspberry Pi 5. Log output on login: Could not open GPIOChip0. Access to path /dev/gpiochip0 not allowed. Add /dev/gpiochip0 to permitted paths in configuration file if required Could not open GPIOChip4. Trying to open GPIOChip0 Access to path /dev/gpiochip4 not allowed. Add /dev/gpiochip4 to permitted paths in configuration file if required Could not open any GPIOChip. System details: Raspberry Pi 5, 32-bit Raspberry Pi OS (armv7l), kernel 6.12.47+rpt-rpi gpiodetect correctly shows gpiochip0 [pinctrl-rp1] (54 lines) as the RP1 GPIO controller Runtime: CODESYS Control for Raspberry Pi SL 4.21.0.0, Runtime Toolkit SP21+ This worked without issues before the update to SP21. I've tried adding the following to CODESYSControl_User.cfg without success: ini[CmpCharDevice] Linux.DevicePath.1=/dev/gpiochip0 Linux.DevicePath.2=/dev/gpiochip4 Could you tell me the correct section/key to whitelist /dev/gpiochip0 (and /dev/gpiochip4) for CmpCharDevice? I suspect this is part of the general security hardening introduced around SP21 (similar to ForceIecFilePath for SysFile, or the new Gateway "accept local clients only" default), but I couldn't find it documented anywhere. Thanks in advance!
Last updated: 2026-07-19

Post by eschwellinger on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
see here: https://www.codesys.com/eco-system/up-to-date/release-lifecycle/release-plan-roadmap/ 18.8
Last updated: 2026-08-11

Post by mariussandu on OPC-UA ^{CODESYS Forge talk (Post)}
I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30. Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.
Last updated: 2026-09-07

Post by mariussandu on OPC-UA ^{CODESYS Forge talk (Post)}
I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30. Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.
Last updated: 2026-09-07

Post by caualima on AI + Programming ^{CODESYS Forge talk (Post)}
What do you think about having an AI Agent specialized in ST programming in Codesys? I see this saving hours and hours of work for those who program on a daily basis.
Last updated: 2026-01-24

Post by arpat on Error, visualisation property handling, VISU_USEPROPERTYINFO ^{CODESYS Forge talk (Post)}
For me going to Project -> Project Settings -> Visualisation -> check "Visible" and then check both "Activate property handling ..." and "Activate implicit checks ..." solved the problem.
Last updated: 2026-02-03

Post by altin on No source code available for this object ^{CODESYS Forge talk (Post)}
Hello, I get same error message but pointing at different library. The error appears when im trying to scroll an AlarmTable on a thouch screen (ifm CR1204). Anyone knows what causing this and how to procceed? Many thanks in advance,
Last updated: 2026-02-16

Post by eschwellinger on Unable to deploy "Control for Linux SL 4.18.0.0" ^{CODESYS Forge talk (Post)}
Hi could you check if this really exists in 4.19.0.0 deploy tool? In your case architecture is missing- see my configuration
Last updated: 2026-02-17

Post by eschwellinger on Unable to deploy "Control for Linux SL 4.18.0.0" ^{CODESYS Forge talk (Post)}
can you please check this: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_toubleshooting_deploytool2.html#UUID-b83dc01e-8cff-c574-7efe-8615b95a51ed_section-idm234790234401598
Last updated: 2026-02-19

Post by timvh on Unit testing support / libraries for EcoStruxure Machine Expert (CODESYS) ^{CODESYS Forge talk (Post)}
If the Professsional Developer Edition (which includes the Test Manager) is not supported by Schneider, then an option is to use the Open Source Unit test framework. See: https://forge.codesys.com/lib/counit/home/Home/
Last updated: 2026-02-20

Post by alexgooi on Codesys KNX implementation ^{CODESYS Forge talk (Post)}
Dear Forum, For anyone interested we have solved this problem. Before we were using a KNX TP/IP interface, now we are using a KNX TP/IP router, and it works like a charm now.
Last updated: 2026-03-04

Post by fpawlak on How to register own component - CMAddComponent() or CMAddComponent2() ^{CODESYS Forge talk (Post)}
Hi, so really oneone has no idea which way is correct one? Or maybe both are okey if they work for me?
Last updated: 2026-03-13

Post by nulltrace on How change Unity-ID in TCP Modbus Slave ^{CODESYS Forge talk (Post)}
Hey Husarz, thanks for your Message, now i understand your Problem, also able to reproduce that. Pls. give me a Short Time to Check some stuff on this, i'll come back to this Topic with news ASAP. Greetings
Last updated: 2026-04-03

Post by nulltrace on How change Unity-ID in TCP Modbus Slave ^{CODESYS Forge talk (Post)}
Hey, I also waiting for feedback from Mr. Schwellinger @eschwellinger, please send me an answer, i would appreciate it. The clue is, i know the solution, but have to check if it's allowed to share.
Last updated: 2026-04-14

Post by tvm on Generic Variables and FDB ^{CODESYS Forge talk (Post)}
I also ran into this, try using Coil<1> as the type in the FBD box. From what I understand, with VAR_GENERIC CONSTANT, the compiler creates separate data types for each different function block declaration.
Last updated: 2026-07-22

Post by somlioy on Beckhoff ESI import german text ^{CODESYS Forge talk (Post)}
Solved. Had to explicitly select English inside CODESYS as language instead of system default, which for my case is norwegian... Open Tools → Options → International Settings Set the development-system language to English Restart codesys
Last updated: 2026-07-28

Post by axberry on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
when is the releaseof the 4.2.0.0
Last updated: 2026-08-10

Post by eschwellinger on CAN TX regression in Control for Raspberry Pi 4.21.0.0 with CAN API library (RX works, TX silently fails) ^{CODESYS Forge talk (Post)}
seems to be an accident but there is a workaround in the Configfile: [CmpSocketCanDrv] AsyncSend=1 and will be solved with 4.22.0.0 Release
Last updated: 2026-08-17

Post by reinier-geers on Read own network device name ^{CODESYS Forge talk (Post)}
Hi. When i scan for devices on the network i get names of the devices. Is there a command to get device name in my programm ? i found : DED.GetDeviceNameString( DED.GetRoot() ); but then i get his name in the programm. not his name in the network.
Last updated: 2026-09-17

Post by wollvieh on Raspberry Pi Runtime 4.22.0.0 vs. 4.20.0.0 I2C Bus not running... ^{CODESYS Forge talk (Post)}
... the stars needed? --> yes! [CmpCharDevice] PermittedPath.0=/dev/i2c* PermittedPath.1=/dev/spidev0.0 PermittedPath.2=/sys/class/gpio/* PermittedPath.3=/dev/gpiochip* For me it worked with this additional settings in the file /etc/codesyscontrol/CODESYSControl_User.cfg.
Last updated: 2026-10-16

Post by alex-at-xana on EThercat Dynamic configuration ^{CODESYS Forge talk (Post)}
Hi Everyone, For a fast monitoring system I am using Ethercat oversampling and timestamping inputs. As the customers has a lot of different configurations out in the field, we went for a dynamic Ethercat configuration. Already got the whole detection chain working but now I am stuck since two days in debugging the configuration. Here are my quesitons: I extended the dynamic config example for the EL3632 16#0E303052: //EL3632 pSlave^.SetDCSettings(TRUE,TRUE,80,80,TRUE,4000,0,0); pSlave^.AddSyncManager(16#1000,128,16#26,TRUE,3); pSlave^.AddSyncManager(16#1080,128,16#22,TRUE,2); pSlave^.AddSyncManager(16#1100,0,16#4,TRUE,1); pSlave^.AddSyncManager(16#1110,214,16#20,TRUE,0); pSlave^.AddFMMU(0,214,0,7,16#1110,0,1,1); pSlave^.AddFMMU(0,1,0,0,16#80D,0,1,1); xKnown := TRUE; This leads to a PLL Error for these devices. I double and triple checked the configuraton, but cannot find the issue. There seems to be one difference: the config dialog creates a startup parameter: 16#10F3:16#05, Name: Command_0, Value:0. Bitlen: 16, Stop on fault: false, jumpt at fault: false: next line: 0 a) I do not find information on how to set this in my code. Can you help me there? b) Without trying to set the value, I get a PLL error for these devices in the master log. Is the config wrong? c) Do I need to set the Master to Autoconfigure or Manual? I used autoconfigure for my tests. The stack creates input data addresses for the slaves input data range (pSlaves[i].InputData) which are different from those created when I use the Engineering tools dialogs to configure Ethercat. Specifically, the addresses seem to be aligned at 16 byte boundaries when they are created using the engineering tool, but may appear at uneven addresses when I use the script in dynamic config. I did not try to access ULINT at uneven addresses yet, but I am suspecting this may be a problem. Do I need to manually align the addresses ? Any help is appreciated...
Last updated: 2024-09-10

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 mubeta on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Thank you for your interest. Your answers are in line with what I knew, so at least it comforts me that I did not misinterpret the situation. However, I don't have an exact match as, for this project over the past few days I have: 1) I have gone back to leaving the various FBs of the motion always called, all of them, and in the state machine I use a boolean to activate the various useful Execute. (But in the future I want to go back and try the programming technique with which I wanted to develop this project); 2) For the occasional error: SMC_FB_WASNT_CALLED_DURING_MOTION perhaps it was due to the fact that I had set the Ethercat bus synchronism only at the CAN master level, but not at the level of individual drives. I have now also activated it for the individual drives and it does indeed seem to have been resolved, but having also adopted the programming technique mentioned in point 1), I cannot say whether this was the solution to the problem, or instead the previous point. Is there an error ‘regulator or start not set’ in the device log before the error ‘motion generating FB wasn't called for at least one cycle’? I can't answer that right now. By now the machine is running and I am no longer there, at this one. Also, I seem to remember that the 'fbeFBerror' drive structure (5-element array), does not cycle, BUT ONCE THE 5 EVENTS AFTER SWITCHING ON, IT DOES NOT UPDATE ANYMORE (but that's another issue), so diagnostics were not easy.
Last updated: 2024-07-24

Sort by relevance or date