Post by bschraud on Zielsystem stimmt nicht mit dem verbundenen Gerät überein ^{CODESYS Forge talk (Post)}
Zu der o.g. Fehlermeldung "cmperrors interfaces, 3.5.5.0 (system): C0338: Die Bibliothek 'cmperrors interfaces, 3.5.5.0 (system)' wird nur in 32-Bit-Applikationen unterstützt": Wie kann ich die Bibliothek finden, die den Fehler verursacht? Beim Doppelklick auf die Fehlermeldung würde ich einen entsprechenden Hinweis erwarten. Aber es passiert gar nichts. Wenn ich im Bibliotheksverwalter manuell den Baum durchsuche, finde ich nur Referenzen auf CmpErrors2Interfaces, die ja 64bit kompatibel sind. Leider konnte ich bisher nur eine SSD mit einem 64bit OS für den RPi zum Laufen bringen. Deswegen gehen mir langsam die Ideen aus. Vielen Dank für die Hilfe
Last updated: 2024-03-18

Post by pethun on Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Post)}
Hi We upgraded our ptoject from 3.5.19 to 3.5.20 but we get an error message in the latest version. We made our own trend function and its related to this we get error message: Trend_Menu Device: PLC Logic: Application: C0032: Cannot convert type 'RTS_SYSTIMEDATE(systimertc, 3.5.20.0 (system))' to type 'RTS_SYSTIMEDATE(systimertc, 3.5.17.0 (system))' The variables are defined as follow: start : SysTimeRtc.SYSTIMEDATE; end : SysTimeRtc.SYSTIMEDATE; The code that creates the error is the variable start and end IF xAssign THEN xAssign := FALSE; xPanEnable := FALSE; xZoomEnable := FALSE; drs.liFrom := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(start, 0 (us)); drs.liTo := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(end, 0 (us)); drs.m_itfDateRangeSelectorClient.SetCurrentRange(drs.liFrom, drs.liTo); END_IF I cant understand really what the error message means and what can be the cause of the error? It compiles fine in dthe older codesys 3.5.19. If anyone has some experience of this please help us out? We must upgrade due to the new licenses. Thanks
Last updated: 2024-04-20

Post by pethun on Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Post)}
Hi We upgraded our ptoject from 3.5.19 to 3.5.20 but we get an error message in the latest version. We made our own trend function and its related to this we get error message: Trend_Menu Device: PLC Logic: Application: C0032: Cannot convert type 'RTS_SYSTIMEDATE(systimertc, 3.5.20.0 (system))' to type 'RTS_SYSTIMEDATE(systimertc, 3.5.17.0 (system))' The variables are defined as follow: start : SysTimeRtc.SYSTIMEDATE; end : SysTimeRtc.SYSTIMEDATE; The code that creates the error is the variable start and end IF xAssign THEN xAssign := FALSE; xPanEnable := FALSE; xZoomEnable := FALSE; drs.liFrom := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(start, 0 (us)); drs.liTo := VisuTrendStorageAccess.TrendStorageConvertToTimestamp(end, 0 (us)); drs.m_itfDateRangeSelectorClient.SetCurrentRange(drs.liFrom, drs.liTo); END_IF I cant understand really what the error message means and what can be the cause of the error? It compiles fine in dthe older codesys 3.5.19. If anyone has some experience of this please help us out? We must upgrade due to the new licenses. Thanks
Last updated: 2024-04-20

Post by cdutz on Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200 ^{CODESYS Forge talk (Post)}
Hi all. I am currently struggling to get my Wago PFC200 running the Codesys Runtime in version 4.9.0.0 working. I am using Codesys V3.5SP19. I updated the PFC200 to the firmware version 04.01.10(23) after having tried the latest version (04.03.03(25) from Wago and not being able to start the runtime. After reading version 23 was needed, I changed to that and at least was able to have it start the codesys runtime. I also installed the "Codesys Control for PFC200 SL 4.9.0.0" plugin for Codesys to install the Codesys runtime in version 4.9.0.0 as well as update the Gateway on the device. While I seem to be able to connect to the gateway on the PLC (the dot is green) and when doing a scan, I do now find my PFC200, which is a huge improvement to before, where with firmware version 25 it just failed to start the runtime and I never found any device when doing a scan. Unfortunately I don't seem to be able to connect to the PLC in codesys. I logged in via SSH and changed the password and I can see that this password is correct as the stuff in the Codesys PFC200 tools tab only works if I use my changed password. And I used those credentials to update the installed Runtime version, which the log claimed to have worked fine. Now whenever I try to connect to the device found in the scan, I get a authentication pop-up with empy device name, device address: 000A. As User I use "root" and as password the password that I changed it to. As a response I just get "Ungültige Benutzerauthentifizierung auf dem Gerät" (Eng. probably something like "Invalid user authentication on the device". What could I be doing wrong? Admittedly I'm a bit lost here :-/ Chris
Last updated: 2023-08-26

Post by baldeep on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
Hi, though i am aware of the fact that Codesys doesnt not support Raspberry Pi 5 still i tried. Codesys Installation : worked Codesys Starting : worked but right after start it stopped. with Start Runtime it starts again but stops automatically after 5 seconds is Codesys planned for Raspi 5?! Regards... Singh
Last updated: 2023-12-06

Post by hermsen on Raspberry Pi 4.12.0.0 SL also stops after 15s ^{CODESYS Forge talk (Post)}
After installing this new 4.12.0.0 SL version on my RPi5 8GB and the latest bootloader, the runtime disappeared after 15secs. The bootloader my pi uses is from 2024-06-11. I was able to resolve this issue using this post: https://forge.codesys.com/forge/talk/Runtime/thread/be25c0ff66/ The workaround works for me.
Last updated: 2024-07-06

Post by ricola on codesys sp20 opcua not working ^{CODESYS Forge talk (Post)}
Hi, same pb for me ! did you find a solution ? (I'm working on 2 raspberry pi ) The same project compiled for 4.8.0.0 runtime with CodeSys 3.5SP20 is working fine on one target, and on the other one, my UAexpert receives the same "BadIdentityTokenInvalid" and none is working on 4.11.0.0 either ... anybody ?
Last updated: 2024-08-11

Post by nano on ERROR: CodeMAccess2: Used CmRuntime 2.61.2705.500 is too old ^{CODESYS Forge talk (Post)}
the codemeter deb files are part of the runtime-sl-installatonfiles. so u can download the whole raspberry pi package from store-page, unzip it with a progam like 7zip, there you'll find a folder called dependencys i thing. here should the deb files placed
Last updated: 2024-09-18

Post by egau on Hard shutdown: no code on device after power on ^{CODESYS Forge talk (Post)}
Hi, thanks for the fast response :) Yes I Have a .err file. Sorry I forgot to upload it. It is a binary file though... "Runtime goes in exception before the shutdown ?" I think it goes into exception at the same time as the power is lost...
Last updated: 2024-10-03

Post by gabor-n on PNIO Connect Parameter Error ^{CODESYS Forge talk (Post)}
It's a bit confusing, the two RPI is the same (board, OS, runtime, programing with Codesys V3.5 SP20 P2) but the one has a codesyscontrol.cfg file and the other has a codesyscontrol_user.cfg file. Shouldn't be the same? And because I over Codesys 3.5 SP 12 this would be the '_user.cfg' for both. Attached...
Last updated: 2024-10-11

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
yes i took the library from another forum: https://forge.codesys.com/forge/talk/Runtime/thread/f1400b71b6/, it is made for the ads1115 but the ads1015 is almost the same device with same adresses i only changed the divide value of the analog value, because thats the only difference between the ads1115 and ads1015.
Last updated: 2024-11-07

Post by mtnkyr on Runtime Problem connecting to Keyence IV-500MA Camera ^{CODESYS Forge talk (Post)}
I have to use Keyence IV-500MA Camera for a project. Actually I can use physical connection but I tried to connect using Ethernet protocol so I added its EDS file but I took a lot of errors. Could you help me to solve this problem?
Last updated: 2024-12-26

Post by mtnkyr on Runtime Problem connecting to Keyence IV-500MA Camera ^{CODESYS Forge talk (Post)}
I have to use Keyence IV-500MA Camera for a project. Actually I can use physical connection but I tried to connect using Ethernet protocol so I added its EDS file but I took a lot of errors. Could you help me to solve this problem?
Last updated: 2024-12-26

Post by damian177 on Serialports in EdgeBox-RPI-200 ^{CODESYS Forge talk (Post)}
Hi, Two years ago i used EdgeBox-RPI-200 with Codesys and serial ports works fine. Now I try run the same application but only new runtime but serial ports doesnt works: I have two serial: /dev/ttyACM0 - RS485 /dev/ttyACM1 - RS232 and below configuration in my sudo nano /etc/CODESYSControl_User.cfg: [SysCom] Linux.Devicefile=/dev/ttyACM But it doesnt work. what can i do ?
Last updated: 2025-05-17

Post by blitz on Latch alarm variables from the PLC runtime ^{CODESYS Forge talk (Post)}
Hi, I have a question. Does anyone know a way to change latch alarm variables from the PLC runtime? In the help there is a method described: https://content.helpme-codesys.com/en/libs/AlarmManager/Current/Interfaces/pou-IAlarm3/SetLatchVarValue.html but I don’t know how to use it correctly.
Last updated: 2025-09-23

Post by snhatton on OPC UA: How to change NodeId ?! ^{CODESYS Forge talk (Post)}
You can change the node id by adding the following to /etc/CODESYSControl.cfg: [CmpOPCUAProviderIecVarAccess] CustomNodeName=MyPLC123 Then restart the runtime and the new Node name will appear with the connection. I don't know if it's possible to remove the |var| from the name. I hope this helps!
Last updated: 2023-12-11

Post by arwie on Possibility to deactivate CmpBlkDrvUdp ^{CODESYS Forge talk (Post)}
Is it possible to completely deactivate CmpBlkDrvUdp? I managed to practically deactivate it by setting MaxRouters=1 in [CmpRouter], but in the log there are warnings: !!!! No router instance found to assign network interface <interface>ether 6</interface> [CmpRouter] MaxRouters=1 0.MainNet=BlkDrvTcp [CmpBlkDrvTcp] Name=BlkDrvTcp Codesys Runtime 4.10.0.0 Is there a setting in [CmpBlkDrvUdp] which would deactivate it?
Last updated: 2023-12-12

Post by hfelek on *SOURCEPOSITION* App = [Application] area=0, offset = 0 on default example ^{CODESYS Forge talk (Post)}
Hello, I am trying to run CmpTemplate component provided by Codesys for version 3.5.17. I call MyExternalFunction from the component but I get error as shown below. I see component is loaded successfully on runtime logs. I feel like I am missing something basically.
Last updated: 2024-01-15

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I just want to highlight, that we intend to use the codesys runtime on an embedded device that has no possibilites to connect any dongle devices to. It is an edge IO-Link master with an 1.6GHz ARM computer running inside that has an embedded linux running and a Docker container engine: https://www.hilscher.com/de/produkte/edge-gateways-mit-container-management/edge-io-link-master
Last updated: 2024-03-20

Post by idir93dz on Identifier 'IoDrvGPIO' not defined ^{CODESYS Forge talk (Post)}
Hello, After installing the pi runtime and creating a pi project, I get these errors: [ERROR] Untitled3: Application [Device: PLC Logic]: C0046: Identifier 'IoDrvGPIO' not defined [ERROR] Untitled3: Application [Device: PLC Logic]: C0080: Function block 'IoDrvGPIO' must be instantiated to be accessed [ERROR] Untitled3: Application [Device: PLC Logic]: C0004: 'IoDrvGPIO' is no component of 'IoDrvGPIO'
Last updated: 2024-04-10

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 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 cd-tt on cannot connect ot linux runtime: device does not answer the scanrequest ^{CODESYS Forge talk (Post)}
thank you eschwellinger. That one solved it for me. The password must have a length of at least 8 characters. The password must consist of at least 4 different characters. The password must contain lowercase letters. The password must contain uppercase letters. The password must contain digits. The password must contain special characters.
Last updated: 2026-06-12

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

Sort by relevance or date