Import OPC UA model to Codesys ^{CODESYS Forge talk (Thread)}
Import OPC UA model to Codesys
Last updated: 2024-03-12

CODESYS Installer CLI - commands syntax description ^{CODESYS Forge talk (Thread)}
CODESYS Installer CLI - commands syntax description
Last updated: 2024-03-20

Codesys v3.5 SP11 and Python scripts ^{CODESYS Forge talk (Thread)}
Codesys v3.5 SP11 and Python scripts
Last updated: 2024-04-05

Codesys 3.5.12 Module not Found ^{CODESYS Forge talk (Thread)}
Codesys 3.5.12 Module not Found
Last updated: 2024-04-17

Launch a *.exe file from codesys ^{CODESYS Forge talk (Thread)}
Launch a *.exe file from codesys
Last updated: 2024-04-19

Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Thread)}
Upgrade from codesys 3.5.19 to 3.5.20
Last updated: 2024-04-20

Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Thread)}
Upgrade from codesys 3.5.19 to 3.5.20
Last updated: 2024-04-23

Trouble installing codesys 64 3.5.19.0 ^{CODESYS Forge talk (Thread)}
Trouble installing codesys 64 3.5.19.0
Last updated: 2024-04-23

Raspberry Pi Codesys SPI Master ^{CODESYS Forge talk (Thread)}
Raspberry Pi Codesys SPI Master
Last updated: 2024-04-23

Codesys v3.5 Sint to byte ^{CODESYS Forge talk (Thread)}
Codesys v3.5 Sint to byte
Last updated: 2024-04-24

AG Abzug bei Codesys 3 ^{CODESYS Forge talk (Thread)}
AG Abzug bei Codesys 3
Last updated: 2024-05-08

CODESYS Control Standard S and Beaglebone ^{CODESYS Forge talk (Thread)}
CODESYS Control Standard S and Beaglebone
Last updated: 2024-05-11

Trouble installing codesys 64 3.5.19.0 ^{CODESYS Forge talk (Thread)}
Trouble installing codesys 64 3.5.19.0
Last updated: 2024-06-19

Toradex and CODESYS and licensing ^{CODESYS Forge talk (Thread)}
Toradex and CODESYS and licensing
Last updated: 2025-10-21

CODESYS HMI and 2 monitors ^{CODESYS Forge talk (Thread)}
CODESYS HMI and 2 monitors
Last updated: 2026-01-13

Codesys complains about matching versions ^{CODESYS Forge talk (Thread)}
Codesys complains about matching versions
Last updated: 2025-12-16

Safe Editor in codesys v3.5sp21p30 ^{CODESYS Forge talk (Thread)}
Safe Editor in codesys v3.5sp21p30
Last updated: 2026-03-12

Pilz PBRT Robot with CoDeSys ^{CODESYS Forge talk (Thread)}
Pilz PBRT Robot with CoDeSys
Last updated: 2026-05-10

Forge 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Discussions about CODESYS Forge projects and features of the CODESYS Forge website
Last updated: 2026-06-15

Request a dark mode for CODESYS ^{CODESYS Forge talk (Thread)}
Request a dark mode for CODESYS
Last updated: 2026-01-21

Codesys ControlWinV3x64 with EtherCat Slave ^{CODESYS Forge talk (Thread)}
Codesys ControlWinV3x64 with EtherCat Slave
Last updated: 2026-02-27

Engineering 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Discussions about the CODESYS Development System, IEC programming, CODESYS Professional Developer Edition
Last updated: 2 hours ago

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

Post by dekelec on Codesys 2.3 & Peak PCAN ^{CODESYS Forge talk (Post)}
I use Peak USB adapter daily to download from CoDeSys 2.3 and 3.5 to IFM, EPEC and other controllers. The process: - First you need to install the appropriate driver. Link: https://www.peak-system.com/Drivers.523.0.html?&L=1 - Restart the computer - Start the CoDeSys application - Change the name of the adapter in Communication parameters, as mentioned in previous comment. Write the name exactly as written "Peak_USB", as it could also be case sensitive (defines which .dll file to use). If this doesn't work I would contact the vendor of the controller to find out the procedure. In the attachment I've added a FAQ document from IFM regarding using PCAN USB. P.S. I've noticed in your picture of communication parameters a channel via TCP/IP is mentioned. In this case a USB to CAN connection is not being used. First you should change the channel/gateway to connect via CANbus or connect using an Ethernet cable.
Last updated: 2024-07-09

Post by timvh on License problem gateway ^{CODESYS Forge talk (Post)}
What we are trying to explain is that, yes CODESYS creates the software, but Epis decides how they implement it on their hardware, which runtime version they use and they decide which functionality they support. So it is always a combination of the two. What CODESYS provides is a runtime with options for e.g. visualization or softmotion. Epis could add this softmotion license as default to their controller, but if they don't then CODESYS provides another option with a single license in a "Wibu CodeMeter" container. Eventhough the feature exists, Epis has to add this "CodeMeter" software on their controller to be able to access the licenses in the container. We don't know if they did this. Then finally it depends on what type of runtime is on this controller and which license Epis is using. So if they have an OEM license (not an application based license), then most likely you will need the Softmotion license (not a number of axis). See https://store.codesys.com/en/codesys-softmotion-sl-bundle.html. But to be sure if this is supported by the Epis controller, you must ask Epis.
Last updated: 2024-04-30

Sort by relevance or date