Post by mehmetembedded on Linux ARM64 SL, GPIO Access ^{CODESYS Forge talk (Post)}
Hello. I am using TI AM64x evaluation board TMDS64EVM. It has 8 leds connected via I2C to SoC.I wanna control them via codesys GPIO device. Is that possible? If so how I can do it. I had no problem installing codesys runtime, and running program on device. But when it comes to GPIO access, It couldn’t make it.
Last updated: 2024-05-08

Post by mehmetembedded on Linux ARM64 SL, GPIO Access ^{CODESYS Forge talk (Post)}
Hello. I am using TI AM64x evaluation board TMDS64EVM. It has 8 leds connected via I2C to SoC.I wanna control them via codesys GPIO device. Is that possible? If so how I can do it. I had no problem installing codesys runtime, and running program on device. But when it comes to GPIO access, It couldn’t make it.
Last updated: 2024-05-08

Post by k2saki on Automatic TOOL Length Measurement like Typical CNC Machine. ^{CODESYS Forge talk (Post)}
I'd like to measure tool length using SW. How do I set variable from the accurate drive position when switch turn ON/OFF? Hopefully, I'd like to measure Z-Pos with M-Function in G-Code automatically, And I'd like to set it to G43 as tool length correction.
Last updated: 2024-05-09

Post by eschwellinger on connect IDE to plc that uses modem ppp ^{CODESYS Forge talk (Post)}
Which plc type is it? Easy connection is to install a Gateway on remote side - this is available for Windows and Linux devices Then just add a new Gateway in CODESYS (with the IP Adress of the remote device) -> then scan the plc via this new added Gateway
Last updated: 2024-05-21

Post by eschwellinger on Runtime on Raspberry pi5 stops after 15 seconds ^{CODESYS Forge talk (Post)}
Think this is bootloader related: Workaround: Use previous bootloader version cp /lib/firmware/raspberrypi/bootloader-2712/stable/pieeprom-2024-01-15.bin ./pieeprom.bin rpi-eeprom-config pieeprom.bin > bootconf.txt rpi-eeprom-config --out pieeprom-new.bin --config bootconf.txt pieeprom.bin sudo rpi-eeprom-update -d -f ./pieeprom-new.bin sudo reboot
Last updated: 2024-06-10

Post by vitorp on Visualization Toolbox in German ^{CODESYS Forge talk (Post)}
Hello, I am new to Codesys. I installed it on my computer and set the language to English. Most of the localized text appears in the correct language, but the Visualization Toolbox and the element properties are in German. I haven't found a way to change them to English. Can someone help me with this?
Last updated: 2024-06-17

Post by koppit on SysComRead Timeout Parameter ^{CODESYS Forge talk (Post)}
Im using SysCom ver. 3.5.17.0 and seem to have the same issue on a Raspberry Pi. It's not waiting for the requested number of bytes, no matter if "ulTimeout := SYS_INFINITE" or any other value. The only solution I have found is to stall the program to allow the serial port to recieve the data.
Last updated: 2024-06-26

Post by denizerm on Deploy Control SL cant find Podman ^{CODESYS Forge talk (Post)}
I found something that might be the main cause for this: /etc/os-release features the ID=debian entry on my reference system; When i temporarily override my DUTs os-release to feature ID=debian or similar its able to detect Podman. Is there a way to fix this behaviour?
Last updated: 2025-10-24

Post by salmawis on Advice on OOP hardware I/O code structure ^{CODESYS Forge talk (Post)}
Call 10 FB instances. Connect Motor_1_Fault to the i_xHW_FaultDetected pin of FB 1, Motor_2_Fault to FB 2... By doing this, your FB will be flexible. The programming will be smooth like a perfect Drift Boss, instead of "hitting the wall" because it can't be reused!
Last updated: 2025-10-31

Post by kalmeyer on Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Post)}
I AM VERY GRATEFUL FOR YOUR HELP. I HAVE INSTALLED: CODESYS SOFTMOTION VER. 4.19.0.0 AS SEEN IN THE ATTACHED FILE. BUT IT DOESN'T CHANGE THE FACT THAT I GET 6 ERRORS WHEN I HAVE INSTALLED SM_Drive_RaspiStepper_Direct DO YOU HAVE ANY SUGGESTIONS ON WHAT I CAN DO NOW? /KLAUS
Last updated: 2025-11-10

Post by seler on Custom button with output status ^{CODESYS Forge talk (Post)}
Hi, Im struggle with making custom button. The idea is simple grey light bulb after touch (input var) it changes to yellow but shows output var status not switch status. So if light is physically on, switched by physical switch, bulb is also yellow. How to do it?
Last updated: 2025-11-18

Post by eschwellinger on Deploy LicenseServer for Linux SL ^{CODESYS Forge talk (Post)}
As I see from your logs I think the Timeprovider is not accurate enough in your case. Things to check - at the moment you run it on the same device? (for tesing purpose ok) I would set 127.0.0.0 as IP and set it not really to Core 0 ( many other stuff is there)
Last updated: 2025-11-20

Post by blitz on Can't get SMC_SmoothPath to work ^{CODESYS Forge talk (Post)}
Hi @bertus I have a similar situation: just like in your case I can see that rounding works correctly only for the first element, additionally in my case on a path made of lines where I am testing this every second line is skipped. The interpolator jumps to every second iActObjectSourceNo.
Last updated: 2026-01-07

Post by eschwellinger on Deploy LicenseServer for Linux SL ^{CODESYS Forge talk (Post)}
for the package you net to install 32bit support(to have the native timprovider availble to deploy) sudo apt-get install libc6:i386 Then native Safeplc and native Safetimeprovider should be available to install. Raspi yes - but there is no official package available till now and you need have a rt_preemt patched kernel on the Pi, then it works like charm
Last updated: 2025-11-18

Post by gatto on warning C0195 ^{CODESYS Forge talk (Post)}
Good morning dear codesys users. I'm using 3.5.20.40 and I get this warning C0195 when I assign an initial value to xyz. However, if I do it on a single byte (abc), it doesn't display any warning. Why? VAR_GLOBAL abc : BYTE := 100 ; xyz : ARRAY [1..10] OF BYTE := [10(100)] ; END_VAR
Last updated: 2025-11-20

Post by eschwellinger on NO SIGNAL ON POWER_ON FOR STEPPER MOTOR ^{CODESYS Forge talk (Post)}
Hi, how should that work? You need to download the example project and you need that structure of the project and one of the additional hardware sets https://forge.codesys.com/drv/sm3raspistepper/home/Home/ L298N or A4988, DRV8880. Important to have no GPIO in the project and have this additional tasks.
Last updated: 2025-11-24

Post by kambel on IO Drive on C manual ^{CODESYS Forge talk (Post)}
Hello, pls help!!! Is there a more detailed manual (for dummies) for writing your own IO drive device in C? Another question: how can I add diagnostics to the IEC IO Drive device so that a red triangle lights up in the project tree in the event of a malfunction?
Last updated: 2026-01-29

Post by yr00 on OPC UA datasource low read frequency ^{CODESYS Forge talk (Post)}
Hello everyone, I am trying to test the OPC UA client feature in Codesys. My setup is the following; I have a Codesys simulation/ visualization running on Control Win V3. My OPC UA server is hosted on a Siemens 1518 PLC using PLCSim Advanced. The setup is completely virtual so there are no really PLCs. Everything is on my laptop. Writing data from the Codesys simualtion to the server is very quick. I have a PLC program running on another 1500 PLC which reads data from simulation via the server, and changes in the simulation (e.g. button pressed) appear within hundreds of miliseconds if not tens of miliseconds in my PLC program. However, when it comes to reading data from the OPC UA Server by Codesys, it taks around 1-2s. I connected a UAExpert client and it gets update very quickly so I am fairly sure the problem is with Codesys. I have tried changing the update rate in datasource -> General and Diagnosis, but it doesn't seem to have an effect. Do you guys have any suggestion on what I can do?
Last updated: 2023-08-29

Post by rcaponi on Codesys Control RTE V3. Remote Control ^{CODESYS Forge talk (Post)}
Hello, I would like to have, if possible, some clarification on this function. That is, I would like to understand if it is useful for managing, fom my development PC, the RTE runtime executed on a remote control. This is what the help says: Remote PLC: Opens the Remote Configuration dialog. By enabling or disabling the Control remote PC, not local option, you determine whether a PLC is used that is on a remote or local PC. Accordingly, the menu commands Start PLC, Stop PLC, and PLC Configuration refer to the local PC or a PC reached on the network. For the remote PC, specify the Target PC address, Port number, and a Timeout value (in ms) for the connection (Remote Timeout [ms]). But does this mean that I also need to install the RTE runtime on my development PC? Is it possible to have some more information? Best regards Roberto Caponi
Last updated: 2023-09-22

Post by naps on cant install runetime on 750-8202 ^{CODESYS Forge talk (Post)}
Hello, im trying to install the 3.5 Runtime on a a fresh image on my 750-8202. Product Description: WAGO 750-8202 PFC200 CS 2ETH RS Firmware Revision: 03.10.08(22) ~~~ df -h Filesystem Size Used Available Use% Mounted on ubi0:rootfs.1 82.5M 66.5M 11.8M 85% / devtmpfs 117.8M 16.0K 117.8M 0% /dev none 118.3M 12.0K 118.3M 0% /tmp none 118.3M 0 118.3M 0% /media none 4.0M 136.0K 3.9M 3% /var/log none 118.3M 112.0K 118.2M 0% /var/run none 118.3M 0 118.3M 0% /var/lock none 118.3M 0 118.3M 0% /var/tmp none 118.3M 0 118.3M 0% /sys/fs/cgroup tmpfs 118.3M 48.0K 118.2M 0% /run /dev/ubi0_1 58.6M 3.4M 52.2M 6% /home /dev/ubi0_1 58.6M 3.4M 52.2M 6% /settings /dev/ubi0_1 58.6M 3.4M 52.2M 6% /log ~ After installation and reboot i have still the wago webinterface. No runtime on Information Tab and the Runtime button from the configuration tab is lost. iv try it with firmware 22 and 21. Same problem. What can i do?
Last updated: 2024-09-29

Post by kbazzett on "Sequent Microsystems" industrial automation hat raspberry pi ^{CODESYS Forge talk (Post)}
Here is a complete list of the Sequent Microsystems Pi hats that work in Codesys. https://github.com/SequentMicrosystems/SM_CODESYS/tree/main/ "For easy install download the .package file and open it on your computer, Codesys installer will know what to do with it." <- This. The Multi I/O Hat fit my needs because of the Analog I/O 4-20ma and RTD. I used a Raspberry Pi 5 and 64b install. The example project is also worth the download. With the sample project open, right click on the Raspberry Pi device and update to whatever you are using (SL, MC, 64b). Enable I2C on the PI. You can jumper the hats Analog Outputs to Inputs and see it function on the Web Visualization. Very Cool! I spent quite a bit of time trying to find this solution so hopefully this update helps others. Here is the video link on how to setup a Raspberry PI as a Codesys PLC https://youtu.be/RPoPscbo3Kc?si=Th4-n-mQ6g5fdHj8
Last updated: 2024-12-05

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 fontrap on cmDongle Raspberry Pi issue ^{CODESYS Forge talk (Post)}
Hello mates, I'm working with CODESYS V3.5 SP20 on a Raspberry Pi and I use "Raspberry Pi MC SL" as device on the project. I've installed the Control Standard L (multicore) license on a Wibu System usb-Dongle (cmStick/4.50) that already had another license from another vendor. I follow the online activation procedure from CODESYS documentation. Raspberry Pi has already CodeMeter installed for the other license. When I plugin the dongle on Raspberry and start the Runtime from Raspberry Pi Update in CODESYS I receive the message that I'm on Demo mode because the license is missing. I double checked that the license is activated in the dongle, through the WebAdmin of CodeMeter and the second license runs properly without any issue. I have already try to change the dongle from HID to MSD device and backward but the the Runtime cannot recognize the Dongle. I have also try to stop and start the Runtime through CODESYS without success. Is there anything else I can do to fix this issue?
Last updated: 2024-04-22

Post by jv-certhon on Io driver Scan functionality ^{CODESYS Forge talk (Post)}
Hello, Codesys IDE is 3.5.21.30 IoDrvBase is: 3.5.17.8 I am working on implementing Codesys on our I/O product line, using the IO driver examples, and the Linux UDS socket approach. I have sucessfully created an implemetation where I have a Device with mutiple slots, on which I can plug modules. These modules represent our IO modules, and communication is successful. (For this question the assumtion can be made that Codesys commucates with 1 'master' device, which handles further communcation with the IO modules. For the next part of the question it can be assumed that the Master device has a list of which modules are attached/available) I'm now trying to implement the 'Scan for Devices...' feature, but I'm completetly lost on what to do once the IoDrvScanModules method is called in my IoDrvFB. I'm guessing that the ppConnectorList has to be filled with the found devices, but I have no idea if that is the correct approach. And Codesys is not triggering my breakpoints in the method, which makes things more difficult. I hope someone could provide some examples or guidance on what steps I should take to implement the scan feature. Thanks in advance.
Last updated: 2025-11-26

Post by scoob on ModbusFB - Slow Response Time ^{CODESYS Forge talk (Post)}
Hello, I have been trying to use the ModbusFB functions so I can put some code into libraries, but it seems to be very slow for me. I have a Modbus device with 100ms registers. I previously setup 10 channels in the 'traditional' Modbus Slave with channels and mappings - and set a cyclic trigger at 100ms - this worked fine. I then tried the ModbusFB example, and setup reading the same 10 blocks of modbus addresses, copying the example and putting all of the requests into an array and triggering the requests sequentially. I timed how long the requests are taking to get round to each one, and it is around 1s 450ms. How do I speed this up to match the cyclic time? IF NOT(init) THEN init := TRUE; // Set the required IP address: ipAddress[0] := 192; ipAddress[1] := 168; ipAddress[2] := 1; ipAddress[3] := 10; // Pass the required IP address to the clinet FB: client_NetworkSwitch.aIPaddr := ipAddress; client_NetworkSwitch.udiLogOptions := (ModbusFB.LoggingOptions.ClientConnectDisconnect OR ModbusFB.LoggingOptions.ClientReceivedValidReplies); // Try to connect the client client_NetworkSwitch(xConnect:=TRUE); // Configure all the channels to read connecting them to the client: portStatus_Request(rClient := client_NetworkSwitch, uiStartItem := 4096, uiQuantity := 32, pData := ADR(portStatus), udiReplyTimeout := udiReplyTimeout); portSpeed_Request(rClient := client_NetworkSwitch, uiStartItem := 4352, uiQuantity := 32, pData := ADR(portSpeed)); flowControl_Request(rClient := client_NetworkSwitch, uiStartItem := 4608, uiQuantity := 32, pData := ADR(flowControl)); linkUpCounter_Request(rClient := client_NetworkSwitch, uiStartItem := 5888, uiQuantity := 32, pData := ADR(linkUpCounter)); txPacketCounter1_Request(rClient := client_NetworkSwitch, uiStartItem := 8192, uiQuantity := 100, pData := ADR(txPacketCounter1)); txPacketCounter2_Request(rClient := client_NetworkSwitch, uiStartItem := 8292, uiQuantity := 28, pData := ADR(txPacketCounter2)); rxPacketCounter1_Request(rClient := client_NetworkSwitch, uiStartItem := 8448, uiQuantity := 100, pData := ADR(rxPacketCounter1)); rxPacketCounter2_Request(rClient := client_NetworkSwitch, uiStartItem := 8548, uiQuantity := 28, pData := ADR(rxPacketCounter2)); txErrors_Request(rClient := client_NetworkSwitch, uiStartItem := 8704, uiQuantity := 64, pData := ADR(txErrors)); rxErrors_Request(rClient := client_NetworkSwitch, uiStartItem := 8960, uiQuantity := 64, pData := ADR(rxErrors)); // Trigger all client requests initially FOR clientRequestsCnt := 0 TO (SIZEOF(clientRequests)/SIZEOF(clientRequests[0]))-1 DO pClientRequest := clientRequests[clientRequestsCnt]; pClientRequest^.xExecute := TRUE; END_FOR // Prepare sequential trigger / control of client requests. clientRequestsCnt := 0; pClientRequest := clientRequests[clientRequestsCnt]; END_IF // Call the client to do request processing: client_NetworkSwitch(); // Now we trigger client request sequentially ... IF NOT pClientRequest^.xExecute AND NOT pClientRequest^.xDone AND run AND client_NetworkSwitch.xConnected THEN pClientRequest^.xExecute := TRUE; END_IF // .. and check result/error IF pClientRequest^.xExecute AND run AND client_NetworkSwitch.xConnected THEN IF pClientRequest^.xDone THEN // Prepare next trigger of client request (a rising edge of xExecute) pClientRequest^.xExecute := FALSE; IF clientRequestsCnt < SIZEOF(clientRequests)/SIZEOF(clientRequests[0])-1 THEN // next client request clientRequestsCnt := clientRequestsCnt + 1; ELSE clientRequestsIterationCounter := clientRequestsIterationCounter + 1; clientRequestsCnt := 0; END_IF pClientRequest := clientRequests[clientRequestsCnt]; END_IF END_IF I did try a semi-coded way using the IoDrvModbusTCP library, and setting the slave com settings, then 10 commands and 10 requests, then using a TP on xDone as a pause, before triggering another request - this is time the delay is around 120ms - so the device is fine with the speed, just something I am doing wrong in the ModbusFB method I am sure.
Last updated: 2024-04-26

Sort by relevance or date