Post by fontrap on cmDongle Raspberry Pi issue ^{CODESYS Forge talk (Post)}
Good morning @eschwellinger, After some research I found out that the problem is the preinstalled CodeMeter on Raspberry Pi. As I mentioned the CodeMeter was installed on the Raspberry because I use a license from other vendor that needs the CodeMeter to be installed. The problem is that when I uninstall the CodeMeter from Raspberry I am able to detect the dongle from CODESYS and everything works as it should be but now the other product can not detect its own license. When I reinstall the CodeMeter I am back to the initial problem. Is there a way to overcome this conflict through CODESYS?
Last updated: 2024-04-24

Post by bjarne-pagaard on Codesys v3.5 Sint to byte ^{CODESYS Forge talk (Post)}
Hi A SINT is a short (signed) integer. It is already only 1 byte - so you should have no problem casting it to a byte like so: bMyByte := TO_BYTE(sintMyShortInt); If you have a regular INT you want to put in 2 bytes - there are a lot of ways you can do this. A Union is certainly one of them. You could have a union with 2 memebers: An array of 2 bytes as one member, and an integer value as another member. Another way would be to look at MEMCPY to put the value into your CAN-message. .. or create a function to take your input value as input, and giving you 2 individual bytes as output. This could be handy if you need to change the byte-order. Integer data types: https://help.codesys.com/webapp/_cds_datatype_integer;product=codesys;version=3.5.17.0 -Bjarne
Last updated: 2024-04-24

Post by esave on Softmotion Light Problem: The license is missing or invalid ^{CODESYS Forge talk (Post)}
Hello everybody I want to controll a stepper driver from Leadshine (EM3E-556E). The EtherCat slave is CiA 402 compatible. Because of this I bought the Softmotion Light Package from Codesys and implemented it in my project. I rightclicked the EtherCat slave and added the Softmotion Light axis. But now the error message shows: "The license is missing or invalid. The PLC runs in demo mode." What have i done wrong? I use Codesys 3.5.17. Is it possible that the stepper driver is not compatible with the Softmotion license? Thanks for all your help
Last updated: 2024-05-02

Post by westcountryewe on Persistence Variables missing and DO NOT retain from Persistence Channel when using Boot Application ^{CODESYS Forge talk (Post)}
We've been experiencing an issue through SP18, SP19 and now SP20 where the Persistence Variables do not retain if we upload our program via a Boot Application. If we use the exact same program, and perform a Direct Upload via the Laptop and Ethernet connection, the Persistence Variables work exactly as expected. I have submitted 2 bug support tickets but I haven't had a response back from Codesys. Has anybody experienced the same issues and discovered a workaround? We have a requirement to utilise the Boot Application method because of logistical restrictions of being able to get out to every site, so at the moment it's a bit restriction.
Last updated: 2024-05-15

Post by wbj0t on connect IDE to plc that uses modem ppp ^{CODESYS Forge talk (Post)}
Hello everyone! I have an PLC device that uses modem ppp connection to the internet with white IP. Device PPP connection with modem operator established, so I can connect to this device via SSH also within Codesys IDE (check version, info, etc...) BUT, I cant establish connection to this device in the device gateway options for application upload and debugging. How can I do this? Im trying set my device remote IP and port 11740, but, as I understand, it is wrong decision, because the next logic in this connection: local W10 service (Codesys Gateway) listen on 1217, then (some how) this service scanning local networks for seeking any local IP which listening on port 11740, and then connects and writes there. OR IM WRONG?:) W10 tool 'Test-NetConnection' with parameters 'ip -Port 11740' succeeded with True. Need some help, please :)
Last updated: 2024-05-21

Post by fpawlak on KNX SL on stock PFC200 firmware ^{CODESYS Forge talk (Post)}
Hi All. Is it possible to use CODESYS KNX SL on stock Wago firmware (Codesys version, not e!Cockpit). I have Wago 750-8212 with firmware 0.4.04.03(26). When I tried to run 'KNX SL' or even 'Device Reader', I have got [FATAL ERROR] Unresolved reference: 'CODEMGETCONTENTBYFIRMCODE3' [FATAL ERROR] Unresolved reference: 'CODEMGETCONTENTBYFIRMCODE2' [FATAL ERROR] Unresolved reference: 'CODEMGETCONTENTBYFIRMCODE2' What probbalby means that there is no running CodeMeter component on PLC. I have checked /etc/codesys3.d/CODESYSControl.cfg [CmpWebServer] WebServerPortNr=58080 [CmpSecureChannel] CertificateHash=86ccf31839a098ee32067179e26600f1bd6b36f8 [CmpUserMgr] AsymmetricAuthKey=a9d38381e75bbf1bbfc8749e97f536f68238a2ce So the question is if I can somehow add Codemeter to stock firmware? Or should I switched to CODDESYS Control for PFC200 SL or application-base runtime licence?
Last updated: 2024-05-23

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 daanyouknow on Using a raspberry pi and NVLs to log variables outside of Codesys ^{CODESYS Forge talk (Post)}
Hi, My PLC/controller doesn't support OPC UA, so my current plan to create a ringbuffer/circular logger is to connect a raspberry pi to it, use the Network Variable List receiver and sender and raspberry pi codesys runtime to get the variables to the raspberry pi, after which I will use the pi which DOES support OPC UA to get the variables to a python program which logs the desired variables for a certain amount of time for me, would this work? I don't want to spend 50+ euros + licencing fees for a solution that might not work.
Last updated: 2025-11-14

Post by imdatatas on Error: C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr ^{CODESYS Forge talk (Post)}
Unfortunately, the "C0138: No matching 'FB_Init" method found" error is a nightmare for CODESYS V3.5 SP21. I'm not sure if anything has been done about this or if anything will be fixed. I've encountered the same issue many times, and it was only resolved by completely uninstalling SP21, deleting all related files and folders from my computer, and then installing SP19. So, I've given up on using SP21 and switched back to SP19patch7. Here are some previous posts regarding the "C0138: No matching 'FB_Init" on SP21 of Codesys. https://forge.codesys.com/forge/talk/Visualization/thread/0763d6ca8e/ https://forge.codesys.com/forge/talk/Motion/thread/9074005bf4/
Last updated: 2025-11-28

Post by kporter on Codesys EtherCAT Driver (CmpEt1000MPD) can't set MAC address ^{CODESYS Forge talk (Post)}
EtherCAT is a point-to-point protocol so it doesn't need a unique MAC address. It would be very useful to set the MAC address to 020000000000, the standard address for this kind of application. (The important bit is the 02 at the start of the address, which means locally-administered MAC.) The stock Windows driver can do this for my i210 card. But the CODESYS CmpEt1000MPD driver cannot. The image shows the setting with the Windows driver. If I set all my customers' cards to this address, then I don't need to deal with this when deploying my application. A simple PowerShell script can be used to set the MAC address once when the NIC is installed and the driver is changed.
Last updated: 2026-02-09

Post by pernockham on Unable to deploy "Control for Linux SL 4.18.0.0" ^{CODESYS Forge talk (Post)}
And the strange thing for me is that if i connect with an older IDE version (where I only have 4.17.0.0 installed) I can see both "CODESYS Control for Linux SL" and "CODESYS Edge Gateway for linux". And that I loose (both presence and possibility to update) the first option (Control SL) if i let the updater install "Control for linux SL" vers. 4.18.0.0 or later. (Note that runtime 4.17.0.0 is installed and it is running and I can login to that system, but no apparent option available to update it to 4.19.0.0). Attached print screen where I connected the "deploy sl tool" to the same system, where the upper (IDE) one has 4.19.0.0 installed, while the lower one has 4.17.0.0 installed..
Last updated: 2026-02-17

Post by yannickasselin on Question about Demo License limitations for Modbus TCP communication and Fieldbus Instances ^{CODESYS Forge talk (Post)}
As far as I know, there is no other limitations than the 2 hours limit. The demo mode should be plenty enough for testing purposes. Regarding instances. In the device tree, 1 master = 1 instance, no matter how many slaves the master is communicating with. But it is also possible that your Codesys runtime act as a slave. In this case, each slave in the device tree is one instance. You can also use the license metric tool in the IDE. This will tell you exactly how many instances you have in your project. https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_edt_device_licensed_software_metrics.html
Last updated: 2026-02-28

Post by gseidel on Absolute movement controlled by an external encoder. ^{CODESYS Forge talk (Post)}
Hi polyautomacao, basically, there are two ways to approach this. My first choice would be to check whether your servo drives supports an external encoder, connect the encoder to the servo and configure the servo accordingly. In this case, you would not need to change anything in the CODESYS application. If that is not an option, you could use SM_DrivePosControl, a drive that closes the position loop in the PLC, and feed it with the external encoder positions. See (0). You can switch your servo drive to velocity control mode (SMC_SetControllerMode) and use SMC_FollowVelocity to apply the fSetVelocity of the SM_DrivePosControl to your servo. The MC_MoveAbsolute can then be performed on the SC_DrivePosControl Hope that helps. (0) https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_example_poscontrol.html Best regards, Georg
Last updated: 2026-03-04

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 superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I updated the docker container runtime to version 4.11.0.0. and build the container with this "Dockerfile" FROM arm64v8/debian:11.6 RUN apt-get update RUN apt-get install -y wget sudo unzip libusb-1.0-0-dev procps ENV CDS_VERSION "4.11.0.0" ENV EDGE_VERSION "4.11.0.0" ENV URL "https://store-archive.codesys.com/ftp_download/3S/LinuxARM64/2302000039/$CDS_VERSION/CODESYS%20Control%20for%20Linux%20ARM64%20SL%20$CDS_VERSION.package" ENV EDGE_URL "https://store-archive.codesys.com/ftp_download/3S/EdgeGatewayLinux/000120/$EDGE_VERSION/CODESYS%20Edge%20Gateway%20for%20Linux%20$EDGE_VERSION.package" RUN wget --output-document=/tmp/codesys.package $URL && \ unzip -p /tmp/codesys.package '*codemeter*.deb' > /tmp/codemeter.deb && dpkg -i /tmp/codemeter.deb && \ unzip -p /tmp/codesys.package '*codesyscontrol*.deb' > /tmp/codesys.deb && dpkg -i /tmp/codesys.deb RUN wget --output-document=/tmp/edge.package $EDGE_URL && \ unzip -p /tmp/edge.package '*arm64.deb' > /tmp/edge.deb && dpkg -i /tmp/edge.deb EXPOSE 11740 1217 11743 ENTRYPOINT ["/bin/sh", "-c" , "/etc/init.d/codemeter start && /etc/init.d/codemeter-webadmin start && /etc/init.d/codesyscontrol start && /etc/init.d/codesysedge start && tail -f /dev/null"] Now cmu -x" returns root@sensoredge-field-netfield-produktmanagment:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 8.00 of 2023-Nov-28 (Build 5967) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. But still CODESYS development system reports that it needs a dongle and when I click install that "value cannot be null. Parameter name: containerToLicenses" It seems that Codemeter is forced to look for a dongle instead of a CMsoftcontainer. Can you confirm that CODESYS licensing works also when CODESYS is installed in a Docker container?
Last updated: 2024-03-21

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

Sort by relevance or date