Post by dhumphries on No source code available ^{CODESYS Forge talk (Post)}
Try using an Ethernet/IP scanner instead of an adapter, I'm guessing the 2 devices you're trying to communicate with are adapters, you have to have a scanner somewhere and Codesys should be a scanner. I don't know why you're getting the error, you should be able to use your Ethernet port as an EthernetIP adapter (although I've never had a reason to try,) but it's probably not what you wanted to do, unless you're connecting to another PLC that is a scanner. Good luck configuring the devices you're trying to connect to, it will be a lot easier if you have an .EDS file instead of starting with a generic module, even with an .EDS it can be tricky getting the communication working.
Last updated: 2024-02-03

Post by comingback4u on Memory Address Overlap ^{CODESYS Forge talk (Post)}
Hello, We use a controller that comes with a bunch of predefined faults. These faults are considered active and historic. They are a 32 byte array but only take up 26 bytes of data. Because of this the historic faults start at address 26 instead of 31. Active faults variable take up address location 0 to 31. Historic faults variable take up address location 26 to 57. Because of this overlap I get an error that these overlap and it wont allow me to download to my controller. This isn't an issue in 3.5.5.4 but becomes an issue in newer version. Is there a way to turn this off? If I change the address location, the historic faults then become broken without doing some manipulation in the code. The software will build just fine. Thank you for your time.
Last updated: 2024-03-07

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I recognized that I have to start the two services "/etc/init.d/codemeter" and "/etc/init.d/codemeter-webadmin" in the docker container as well. If I do so, then the command "cmu -x" returns root@sensoredge-field-netfield-produktmanagment:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 7.60c of 2023-Aug-09 (Build 5625) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. So this time there is no indication any more that "Codemeter is not running". But still we are getting the error when using the license manager in CODESYS development system.
Last updated: 2024-03-21

Post by peterned on CNC - system goes to X=0 Y=0 before CNC file execution starts, how to avoid that? ^{CODESYS Forge talk (Post)}
Hi, I have a XY system and use a CNC file to move it. Everything works OK, except for the following: when CNC execution starts, the system rushes at high speed to (X=0, Y=0) point, and only then goes to the first line of the CNC file. If one of the axes is near 0, the system jumps and immediately stops with an error. In the CNC file settings (screenshot attached) I specified low default values for speed/acceleration and a start position different from 0,0 - but all that is ignored. Any idea how to avoid that move to 0,0 ? Thanks.
Last updated: 2024-04-26

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

Post by salvadegianluca on SysPlcCtrl23 and C0338: The library 'cmperrors interfaces, 3.5.5.0 (system)' is supported just in 32 bit applications ^{CODESYS Forge talk (Post)}
Good afternoon to everyone; I'm stuck with this error and I don't know how to get out from it... I tried several time googling for alternative systems to control the PLC applications and resets but without success. I would like to realize the possibility to reset the CPU and to start/stop the applications as it was possible with the SysPlcCtrl23, but this library is no longer supported in 64 bit systems and it seems due to the cmperrors interfaces sub library that was included in the above said one. Someone found a work around for this issue?
Last updated: 2024-06-14

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 dhumphries on install codesys runtime on linux ^{CODESYS Forge talk (Post)}
Adding the command worked. I was able to deploy the runtime on an ubuntu server installation. Thanks!
Last updated: 2023-11-04

Post by mos89p on Check if Codesys runtime is on 'Running' or 'Stopped' state? ^{CODESYS Forge talk (Post)}
why not put it on windows startup ? to start at each start
Last updated: 2024-07-02

Post by sukrit on TargetVisu on Raspberry? ^{CODESYS Forge talk (Post)}
thanks for this, w need to know the requirements on linux side... can you guide towards a linux installation package..
Last updated: 2024-08-28

Post by eschwellinger on Licensing info not available. ^{CODESYS Forge talk (Post)}
you need a license server on the host or on any system in your environment.
Last updated: 2024-09-23

Post by s1mon on Raspberry Pi 5 GPIO not working. ^{CODESYS Forge talk (Post)}
Is there any update on this? When will CODESYS Control support GPIOs on Raspberry Pi 5?
Last updated: 2025-03-31

Post by tk096 on Softmotion general ^{CODESYS Forge talk (Post)}
Hi, right-click on the device in the project tree on the left side and execute the command 'Enable Softmotion'.
Last updated: 2023-12-20

Post by eschwellinger on Can V3.5.19 and V2.3.9 be installed on same Windows10 PC without affecting each other? ^{CODESYS Forge talk (Post)}
Sure both could run on the same PC.
Last updated: 2023-12-28

Post by reinier-geers on Gear on is slave offline ^{CODESYS Forge talk (Post)}
When i Put Gear on, the the slave goes off.. Why ? Disable Gear_on and Reinit the drive its back
Last updated: 2024-01-14

Post by rckalex on Codesys v3.5 on WAGO 750-8202 ^{CODESYS Forge talk (Post)}
You can use C3.5 by using the 3S firmware on the 8202 https://us.store.codesys.com/codesys-control-for-pfc200-sl-1.html
Last updated: 2024-03-07

Post by rckalex on Codesys v3.5 on WAGO 750-8202 ^{CODESYS Forge talk (Post)}
You can use C3.5 by using the 3S firmware on the 8202 https://us.store.codesys.com/codesys-control-for-pfc200-sl-1.html
Last updated: 2024-03-07

Post by eschwellinger on No Visu on RasPi ^{CODESYS Forge talk (Post)}
..on 4.12.0.0 release there it will be possible to deploy RemoteTargetvisu which is what you expect now. (next week)
Last updated: 2024-06-20

Post by eschwellinger on Soft Container License issue with ARM64 Linux ^{CODESYS Forge talk (Post)}
the softcontainer should be generated on first start of the plc runtime on your system
Last updated: 2025-12-10

Post by spiessli on Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4 ^{CODESYS Forge talk (Post)}
Thanks for the suggestion, I have tried it eagerly: I have updated all packages to latest version with Codesys Installer and installed newest runtime and gateway on Raspberry Pi. Unfortunately, the error is still there. As soon as I add the SM_Drive_Servo to the device tree, I get the error below when generating the code. Reverting SM3_Basic to version 4.14 makes the error disappear. ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... Code erzeugen... [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.10.0.0 (codesys): GetStandardConfigParams [AXIS_REF_SERVO]: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet Übersetzung abgeschlossen -- 15 Fehler, 0 Warnungen : Kein Download möglich
Last updated: 2023-12-20

Sort by relevance or date