Post by damian177 on CM4S GPIO's in Codesys ^{CODESYS Forge talk (Post)}
Hi, I am running my application on device based on Compute Module 4S (Cortex-A72 (ARMv8) 64-bit ). On this device I installed RPi Runtime in 4.11.0.0 version. In my project I use device: Codesys Control for Raspberry Pi 64SL and my project works, but I actually do not have acces to all GPIO's , because GPIOs Compute Module is available only in 3.5.16.0 version and it doesn't work. Properly work GPIOs B+/Pi2 but using this device I do not have acces to all GPIO's in CM4S. Anyone of can tell me how add GPIOs Compute Module 4.11.0.0 to my project ?
Last updated: 2024-05-28

Post by kronlundo on Licensing info not available (WAGO PFC200 + Codesys V3) ^{CODESYS Forge talk (Post)}
Hi! We're using a WAGO PFC200 for several projects towards the energy sector, and recently upgraded to CODESYS V3. We have the "IEC 60870-5-104 Server" package in a test program, and it works well with the package in DEMO mode. However, when we acquired a license for the "IEC 60870-5-104 Server" package and tried to add the license on the PFC200 through the license manager, we get an error (see attached file). It seems like there is no CmContainer on the device, does anyone have an idea on how to fix this? We've also contacted WAGO on this issue a while back with no feedback yet.
Last updated: 2024-06-10

Post by mborchert on PFC100 Error "Bus not running" ^{CODESYS Forge talk (Post)}
Hello, i currently want to use a wago 750-8102 with the "codesys control for pfc100" runtime. I want to add the devices connected to the internal pfc100 bus via the "search devices" tab. This was reccommended in the following thread: https://forge.codesys.com/forge/talk/Deutsch/thread/7701332199/ But whenever i try to search for devices codesys just doesnt find anything and i cant close the "search devices" window. Has anyone got an idea what the problem might be? I already tried adding the devices connected to the pfc100 manually but the bus just doesn´t start. best regards Moritz
Last updated: 2024-06-17

Post by ron-rp on Errors with VisuUserManagement library ^{CODESYS Forge talk (Post)}
Hi all, I've played a bit with the VisuUserManagement library, and some other security option in my project, and I started getting this error when logging in - see attached pic. something to do with a specific screen in the library - VUM_Login. Also, Codesys started to ask me to log in to the library when logging in, asking to log in as user of the groups Maintainer or Owner, which I dont know either users (attached pic). when I close the login screen and try to log in to the PLC again, everything works again until I close and open Codesys. I do use user and password to login to the PLC, and this login screen is fine I know the user and pass I setup. anyone know what did I do wrong here and how to fix it?
Last updated: 2024-06-25

Post by s1mon on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
I don't know why the EtherCat fails, but what happens is: First I have only one 1WireMaster running on my Raspberry Pi and EtherCat is running fine. Then I'd like to add a 2nd 1WireMaster. Therefore I enable a 2nd GPIO Pin on the raspberry in the file "/boot/firmware/config.txt". dtoverlay=w1-gpio,gpiopin=4,pullup=0 dtoverlay=w1-gpio,gpiopin=23,pullup=0 To be able to use this 2nd 1WireMaster in Codesys Runtime I Adjust the CODESYScontrol.cfg file and add there: PlaceholderFilePath.2=/sys/devices/w1_bus_master2, $OneWire2$ After a reboot the EtherCat Master is not working any more. I didn't even add a 2nd OneWire Master in Codesys, but still if I do the EtherCat does not work. Do you have an idea why?
Last updated: 2025-10-21

Post by alimans on Unrecoverable SoftMotion state after switch to PreOp ^{CODESYS Forge talk (Post)}
For anyone still experiencing this issue, here’s how I managed to solve it: Symptoms: 1. Sometimes, on the first start of CODESYS Runtime, the modules fail to run. 2. After disconnecting and reconnecting the communication cable, the drive does not start again. 3. MC_Reset cannot clear the fault. Solution (what worked for me): 1. Check the axis communication using the SMC_CheckAxisCommunication function block (FB). 2. If CheckAxisCommunication.eComState of the axis is equal to or higher than SMC_CommunicationState.SMC_COMSTATE_BASE_COM_INITIALIZATION, then 3. Use the SMC3_ReinitDrive function block to reset the drive — and it works. For more information, refer to the official CODESYS documentation: 👉 https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/DriveInterface/AXIS_REF/SMC3_ReinitDrive.html
Last updated: 2025-10-23

Post by pruwetbe on Profinet IO-link master - IODD files ^{CODESYS Forge talk (Post)}
Hello, we have the same problem here. Our configuration in the following: Codesys V3.5 SP19 running on Exor Exware700Q Profinet network connected on Eth1 IOLink Master Turck TBEN-S2-4IOL version 3.5.9.0 IOLink sensors E+H & Sick (Pressure, T°) We installed the codesys IO link package and have the codesys IO Link SL licence activated (on a dongle) Our problem is the following: we got the IODD files from E+H & Sick we add the devices in the codesys device repository with success They appear in the devices tree under IODD branch We added the TBEN IOLink master under the Profinet IO . The IO link master are ok and display online. The IO-Link SL package datasheet indicate that there would be a way to scan the IOLink device from the network but we did not find any way to trigger this scan. (we expect to get this from a right click on each IO-Link Master module but the only possibility there is "Plug device") When clicking on Plug Device, we get a browse window with profinet IO modules. The IODD devices are not there so we cannot select them. But other devices for other brands are available and can be plugged. Our question are : 1) how do we update the Profinet IO Module catalogue in order to be able to plug the E+H & Sick Sensors that we have to work with? 2) how do we activate the Scan IOLlink device that is supposed to be included in the Codesys IO-link package? 3) where can we find the manual explaining how to use this package?
Last updated: 2024-11-12

Post by fmon on Modbus TCP client reconnection problem ^{CODESYS Forge talk (Post)}
Hello, I am using codesys Modbus TCP client (4.4.0.0) to communicate with a python modbus server (package pyModbusTCP). I first start my python server on the distant machine. After a fresh codesys compilation, a plc connection/transfer and a PLC run, the modbus connection is OK. Every time in this context the connection is created correctly. When I shut down the server, the modbus connection falls, that is normal. When I restart the python server, impossible to recreate the modbus connexion. With the client autoreconnection, I see on my server that the client tries to connect but unsuccesfully. I have the following message : DEBUG:pyModbusTCP.server:accept new connection from ClientInfo(address='192.168.1.20', port=33476) DEBUG:pyModbusTCP.server:Exception during request handling: NetworkError('recv return null') I tried to stop the codesys client and to restart it with these commands : Modbus_TCP_Client.xStop := True; // Or False Modbus_TCP_Client.Enable := True; // Or False Modbus_TCP_Server.Enable := True; // Or False I tried to confirm the error manually to force reconnection with: Modbus_TCP_Server_Motors.xConfirmError := TRUE; I tried also this command to STOP/RESET/START client and server (codesys side) but nothing happens : status_client := Modbus_TCP_Client.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.STOP); // .RESET & .START The answer of this function when executed is "status_client = NOT_SUPPORTED". Is it normal ? It seems that is a socket problem, but I do not understand if it is on the client or server side. I tried a modbus simulator called "ananas.exe" and the result is the same. Impossible to get a modbus client reconnection. What is different at the first client connection and at a reconnection attempt ? Thanks for your help
Last updated: 2025-03-17

Post by elektron785 on GPIO mit Codesys Virtual Control for Linux ARM64 SL ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich möchte an einem Entwicklungsboard auf dem der i.MX 8M Plus von NXP aufgesteckt ist die vier zur Verfügung gestellten GPIOs als Ausgänge verwenden. Ich habe mir dazu die Readme-Datei des GPIO-Beispiels von "C:\Program Files\CODESYS 3.5.20.40\CODESYS\CODESYS Control SL Extension Package\4.14.0.0\Examples\GPIO" angeschaut Die Übersicht der verfügbaren GPIOs sieht folgendermaßen aus - wobei ich das auf die reduziert habe, die für mich von Interesse sind: gpiochip0: GPIOs 0-31, parent: platform/30200000.gpio, 30200000.gpio: gpio-0 (SODIMM206 ) gpio-1 (SODIMM208 ) gpio-2 ( ) gpio-3 ( ) gpio-4 ( |sd-vsel ) out hi gpio-5 (SODIMM210 ) gpio-6 (SODIMM212 ) gpio-7 (SODIMM216 ) gpio-8 (SODIMM218 ) gpio-9 ( ) gpio-10 ( ) gpio-11 (SODIMM16 ) gpio-12 (SODIMM155 |regulator-usb1-vbus ) out lo gpio-13 (SODIMM157 ) gpio-14 (SODIMM185 |regulator-usb2-vbus ) out hi gpio-15 (SODIMM91 )** Füge ich nun das GPIO (1 Bit)-Gerät in meinem Codesys-Programm hinzu funktioniert der Bus solange bis ich die Richtung in den GPIO-Parametern von "not used" auf "Output" stelle (siehe Bild gpio_parameter). Dann funktioniert nach Download der Bus nicht mehr. Gibt es noch eine andere Möglichkeit das zu steuern oder muss ich noch Einstellungen tätigen? Für die Zeile mit dem echo (export/unexport) aus dem Beispiel fehlen mir trotz sudo die Zugriffsrechte. "The Kernel Linux has deprecated GPIO user space SysFS. However, the kernel config CONFIGGPIOSYSFS is still enabled on Toradex's BSP to support customers using it in their legacy applications. You can check the configuration by running zcat /proc/config.gz | grep CONFIGGPIOSYSFS. For GPIO access from userspace, the new char device API, also known as libgpiod, must be used." Dies steht in der Verwendung der GPIOs - eine Ausführung des zcat-Kommandos liefert ein =y zurück.
Last updated: 2025-03-17

Post by gunstr on CODESYS control on RPi starts, shortly runs, then exits ^{CODESYS Forge talk (Post)}
Thank you very much for the quick answer! The RPi hw were delivered last week so it's probably a resent version. I found an old scrapped board (2 years or so) with a broken GPIO that I tested with the same SD card image and with that board Codeys can run for the full 2h demo period without issues. Then I went back the the new board to test the 4.17.0.0 release but the installation fails... [INFORMATION] Standard output: create and install daemon [INFORMATION] Standard output: codesyscontrol started [WARNING] Unable to detect Raspberry Pi Architecture. Setting armv6l as default, you can change this through the settings panel. [INFORMATION] Standard output: codesyscontrol stopped [ERROR] Expected exit value of command failed: expected 0, received 1 [WARNING] Error setting the Raspberry Pi Architecture [ERROR] Error installing codesyscontrol Do you have any idea what could be the reason? I'm using an OS image including Python drivers for LCD and some I/O:s from last year to keep things stable, but also after upgrading with sudo apt update && sudo apt upgrade I still get the same error Reverting back to 4.15.00 works fine: [INFORMATION] Standard output: create and install daemon [INFORMATION] Standard output: codesysedge started [INFORMATION] Successfully installed codesyscontrol [INFORMATION] Successfully started CODESYS Edge Gateway for Linux [INFORMATION] Successfully started CODESYS Control for Raspberry Pi SL but as before the Codesys services stops after 30 seconds. And I noticed that the Codesys control stops and is not reachable also if I have no application loaded.
Last updated: 2025-09-02

Post by rossanoparis on After un upgrade of "CODESYS Control for Raspberry Pi MC SL" from v4.7 to v4.9 SysFileOpen function stopped working ^{CODESYS Forge talk (Post)}
For those who will step on this thread. Everything is fine, I had only to increase by 1 my place holders number. For sure the system is occupying the number 1 without being declared ... Below the modification I made to get my code working. [SysFile] PlaceholderFilePath.2=/home/pi/hpca/bin, $hpcabin$ PlaceholderFilePath.3=/home/pi/hpca/cfg, $hpcacfg$ PlaceholderFilePath.4=/home/pi/hpca/logs, $hpcalogs$ PlaceholderFilePath.5=/home/pi/hpca/resources, $hpcares$
Last updated: 2023-08-22

Post by fabian on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Hi all, Is there an update on this topic? Same problem here, I can not add more than 10 Modbus-Slave channels. Is there a workaround? Many thanks! Fabian Codesys 3.5.19 SP2, Modbus 4.3.0.0, Name: Modbus TCP Slave Hersteller: 3S - Smart Software Solutions GmbH Kategorien: Modbus TCP Slave Typ: 89 ID: 0000 0005 Version: 4.1.0.0 Bestellnummer: - Beschreibung: Ein Geraet, das als Slave für einen Modbus TCP Master konfiguriert ist. Version Konfiguration 3.5.11.0
Last updated: 2023-08-28

Post by ggarcia94 on IMAGE DISPLAY ACCORDING TO INPUT VARIABLE ^{CODESYS Forge talk (Post)}
Reopening this thread as I need to make a few images visible depending on the value of a variable. However, in the properties of the image I do not have the option to make the image visible (see attached image). I´m using Codesys V3.5 SP19. However, when I use V3.5 SP17 I have the option to make the images visible. Can someone help me achieve this with V3.5 SP19? EDIT: Fixed. Just had to uncheck Support client animations in the Visualization manger settings
Last updated: 2023-09-12

Post by ernesto881124 on ernesto881124 ^{CODESYS Forge talk (Post)}
Hello good morning everyone I would like to ask a question, is it possible to directly connect a device that only contains modbus RTU communication through an R-45 connector, directly to the PC? Or would you need an intermediate device to achieve communication? It would be of great help to me because I cannot achieve communication between the Codesys simulator plc and a Fuji Frenic mini VFD, please help me if anyone has had the same experience. Thank you so much
Last updated: 2023-09-13

Post by transmin01 on CANbus issue ^{CODESYS Forge talk (Post)}
Update: This initial issue was when using a Linux target PLC. Since then I have created a Win10 target PC and the Codesys software reported an issue associated with the device version (see attached). I am assuming this is an incompatibility with the xml file from the manufacturer and the firmware version on the module and I am chasing this up with Beckhoff. Question is, why would this not report with a Linux target?
Last updated: 2023-09-14

Post by transmin01 on PCAN serial "No CAN driver found" ^{CODESYS Forge talk (Post)}
Hi, I am using a PCAN mini CAN board which has the Windows drivers installed on the target PLC. PCAN board can be seen in device manager. However, I am getting "No CAN driver found" error. I have read the post https://forge.codesys.com/forge/talk/CODESYS-V2/thread/44aae19318/ and have uncommented the CmpPCANBasicDrv driver in the CodesysControl.cfg file in development PC and have copied it to the target PC. Current CodesysControl.cfg file attached. Is there anything else I am missing? Regards
Last updated: 2023-09-14

Post by timvh on CANbus issue ^{CODESYS Forge talk (Post)}
On a PC with the Control Win, this is probably related to the fact that the CAN drivers are not loaded. Go to the folder where your Control Win Configuration file is: - E.g. C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E1FA7ABE - Open the CODESYSControl.cfg - Remove the semi-colon in front of the CAN driver you want to use (section ComponentManager). - Set the component ID to the next number in the list (e.g. Component.8) - Save this file and restart the Control Win.
Last updated: 2023-09-14

Post by jeffgamsby on Accessing ModbusTCP addresses from python ^{CODESYS Forge talk (Post)}
Hi, I am new to modbusTCP and I am trying to access Input registers from codesys (3.5.SP13). The offset is 16#0000 and I am trying to access Channel 1[24] %IW24 to pull analog values. I am using pyModbusTCP and I need to supply a modbus address and the number of registers to read. What does 16#0000 mean in terms of the actual offset, how do I translate this number plus the channel to access this info via python? Any help would be appreciated, thank you.
Last updated: 2023-09-20

Post by jantje on Setting up the "Visual Studio Code" debugging environment (using .NET debugging) for use with the ScriptEngine API in Python. ^{CODESYS Forge talk (Post)}
Hi Till, Sadly I did not get any feedback on this and was not able to get it to work using Visual Studio Code. I believe I have used a Codesys environment to get something up, but I cant remember any specifics, its too long ago. Good luck with it! Kind regards, Jan
Last updated: 2023-10-02

Post by chris12345 on IO-Link Lizenz ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich arbeite mich momentan in das Thema IO-Link ein. Benutze einen Revolution Pi, IO-Link Master (AL1333 IFM), Sensor (OGD500 IFM) und ein IO-Link I/O Modul (AL2205 IFM). EDS-Dateien und IODD Dateien über das Geräte-Repro eingebunden. Bekomme jetzt folgenden Fehler:- Die Lizenz fehlt oder ist ungültig. Die SPS läuft im Demo-Modus. Welche Lizenz wird benötigt, um IO-Link fähigen Sensoren meinen IO-Link Master hinzuzufügen? Benutze die Codesys V3.5 SP19. Gruß Chris PS: Anbei das Bild
Last updated: 2023-10-09

Post by ofey on Symbol configuration / GVL ^{CODESYS Forge talk (Post)}
Hi! I have som variables that I communicate to a Modbus Master. These variables are declared in a "Global Variable List" where I have assigned them memory addresses. To organize this mapping I want to make a MODBUS list where I show all the variable names together with the memory address. Is there an easy way to export this list from CODESYS? Either through script or some export function maybe?
Last updated: 2023-10-11

Post by damian177 on Codesys MQTT subscribe ^{CODESYS Forge talk (Post)}
Hi, In my project I have MQTT Client like below: //mqtt client mqttClient( xEnable:=connect_to_broker, sHostname :=sHostname, uiPort:= uiPort, xUseTLS:=FALSE, wsUsername:="", wsPassword:="", xCleanSession:=TRUE, sClientId:='694d45587761676f4b6f6e74656e6572', pbWillMessage := ADR(sWillMessage), uiWillMessageSize:=DINT_TO_UINT(Stu.StrLenA(ADR(sWillMessage))), xWillRetain:=FALSE, udiTimeOut:= 10000000); And ten subscriber's , one of those is below: //subscribe a topic1 mqttSubscriber_S1(xEnable:=subscribe, eSubscribeQoS := 0, pbPayload:=ADR(sSubscribeMessage_S1), udiMaxPayloadSize :=SIZEOF(sSubscribeMessage_S1), mqttClient:=mqttClient, wsTopicFilter:=wsSubcribeTopic_S1); TerminateString(ADR(sSubscribeMessage_S1), mqttSubscriber_S1.udiPayloadSize); After connected to broker I set subscribe to TRUE in alls subscribers and my mqttclient recive error : ACKNOWLEDGE_TIMEOUT what can be wrong ?
Last updated: 2023-10-11

Post by ofey on Symbol configuration / GVL ^{CODESYS Forge talk (Post)}
Hi! I have som variables that I communicate to a Modbus Master. These variables are declared in a "Global Variable List" where I have assigned them memory addresses. To organize this mapping I want to make a MODBUS list where I show all the variable names together with the memory address. Is there an easy way to export this list from CODESYS? Either through script or some export function maybe?
Last updated: 2023-10-11

Post by sukrit on What licenses are required for runtime on raspberry pi cm4 ^{CODESYS Forge talk (Post)}
We have developed a project for 2 servo motors using raspberry pi computemodule 4 on ethercat master. we are using web visualization for display different screens. project is running well in demo. we want to implement it in production envoirment. being new still wondering which licences i need. Can We get this information in codesys devlopment software. code size is approx 5 mb, 1 instance of etharcat master and aproox 100 variables in visaualization.
Last updated: 2023-10-17

Post by eschwellinger on Persistence Manager Backup ^{CODESYS Forge talk (Post)}
you need at them moment a download once (for the configuration files generated including addresses) then stop the plc - exchange the persistence file ( without the config file) This will be improved to 3.5.18.6 and 3.5.20.0. (possible then to generate offline bootproject including full persistenmanager files) - this is if you have not 100% the same bootapplication on the devices. In case you copy the whole Application (PLCLogic) directory it should work out of the box - but only with 100% same bootprojects as mentioned above. By the CODESYS Automation Server would help solve this too.
Last updated: 2023-10-19

Sort by relevance or date