Post by dandyk on Dynamic Images ^{CODESYS Forge talk (Post)}
Hello, I have very similar problem, but it seems that your solution does not work for me. I am using TwinCAT XAE Shell v3.1.4024.55 and TwinCAT Runtime. Sorry for writing here on codesys forge, but since I found the only relevant topic here and since TwinCAT is almost the same with CODESYS in many applications, I chose to write here. I simply need to dynamically update image in visualization based on camera trigger (I am doing a machine vision application). Camera triggers an image, my program processes it (applies thresholding, draws contours etc...) and saves the processed image in the runtime location (the same one you were mentioning). This was done successfully. I need to make it work at runtime, while the program is executing and I need to refresh the image in the visualization each time camera triggers a new image and program processes it. When I create image element in the visualization and define the bitmap ID variable as STRING which contains the image ID defined in the image pool, then it displays the image in the image pool, but does not work at runtime, while the program is executing. I also used the Bitmap Version. I declared it in Global variable list as integer with initial value of 0 and wrote the variable in the bitmap version in the image element in visualization. Each time new image is saved to the runtime location, I wrote a program to increment Bitmap Version by 1. It increments and the image does not update in the visualization, unfortunately. I think that bitmap version is working correctly and deletes the cached image as it is supposed to, but the Image Pool does not update the image ID with the new image... the path to the image is always the same... only the actual image changes with the same file name. Image Pool is not dynamic and cannot refresh the image in the path to the actual one at runtime. How can I refresh the image ID in the image pool at runtime? Bitmap version only deletes cached image and reloads the image from the image ID, but the image ID has the same image, because image pool won't update at runtime. Do you know any solution to this problem?
Last updated: 2024-04-06

Post by jeffg on License issue with visu tags ^{CODESYS Forge talk (Post)}
I seem to be having a problem with the license on ver 3.5.19 patch 5 The runtime keeps going into demo mode but it wont tell me the reason I looked at the license software metrics and the visu doesn't appear to be working I attached screen shots of the metrics screen and the license dongle that is plugged in to the windows PC Anyone have any ideas on how to fix this
Last updated: 2024-06-28

Post by andre-luis on Check if Codesys runtime is on 'Running' or 'Stopped' state? ^{CODESYS Forge talk (Post)}
Just to share, for those who as me are seeking for this and had found no information anywhere in this World: Every time I stop/start the PLC runtime ( turning into 'Stopped' or 'Running' state ) the 'CODESYSControlService' appears at the Taskmanager list, which could suggest a straight correlation. I was expecting a clever solution, but this one solves for while.
Last updated: 2024-07-02

Post by bfunk on Codesys 3.5 auf Wago 750-8101 ^{CODESYS Forge talk (Post)}
Moin, hat hier noch jemand das Problem, das die Codesysruntime (PFC100, Ver.4.11, projektiert mit Codesys 3.5.20sp1), auf der Steuerung nach kurzer Zeit mit einem AUSNAHMEFEHLER in STOP geht? Ich hatte das ganze schon am laufen, sollte dann ein Firmwareupdate durchfuehren (auf die neuste moegliche). Das Firmwareupdate konnte ich auf 03.10.08(22) ist sauber durchgelaufen, die Firmware laeuft auch noch wenn die runtime aufgegeben hat. bekomme die runtime nur dann wieder zum laufen, wenn ich den ganzen controller reboote.
Last updated: 2024-07-03

Post by nano on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
in the codesyscontrol.cfg or codesyscontrol_user.cfg you have to declare whoch comport-ports from runtime are used. please tell us how the comport is called in linux an post the codesyscontrol.cfg files also write down here, which parameters are used in the python-script and what is parameteized in the modbus-master-comport of your codesys-application. mostly the errors occurs in ine of these areas
Last updated: 2024-07-11

Post by aliazzz on Unable to deploy Virtual Control SL on ARM64 (Raspberry Pi5) ^{CODESYS Forge talk (Post)}
An interesting remark for CODESYS Support. I found this after looking through the Runtime Deploy Tool messages when I connect to an AMD64 architecture Successfully Connected to Target ( {MyIP} - AMD64 ) when I connect to an ARM64 architecture (Raspberry Pi5) Successfully Connected to Target ( {MyIP} - ) As clearly seen in the attached .png, the AMD64 target is detected, while the ARM64 target architecture is not detected (displayed). I assume that this is the reason why the pulldown menu isn't populated correctly.
Last updated: 2024-07-28

Post by garmusd on Raspberry Pi 5 GPIO not working. ^{CODESYS Forge talk (Post)}
I paid money for the RPi runtime because the Product Description says that GPIO is supported. It is also written in the Versions that since 4.11 RPi5 is supported. And I use 4.13. Nowhere is it mentioned that GPIO is still not supported... It's a pity that the Codesys developers still can't find a way to fix it. Are there plans for when it will be fixed or are the developers too weak? Just wondering, is there anyone with a working GPIO? Can you share the details of your system?
Last updated: 2024-09-27

Post by aliazzz on Runtime licenses not detected => DEMO Mode 2hour ^{CODESYS Forge talk (Post)}
Hi! After upgrading all my licensed runtimes to V4.14.0.0 (= RaspberryPi SL, LinuxSL and ControlWin x64 SL) I found out via the logfiles they all defaulted back into DEMO mode while all runtimes have a USB dongle inserted. So, my main question is how I can get the Dongle license detected? I use License Server 4.14.0.0 and Edge Gateway 4.14.0.0 on all platforms Any suggestions are welcome.
Last updated: 2024-12-15

Post by atone on Set DeviceID of an IO-Link Sensor at Runtime ^{CODESYS Forge talk (Post)}
I need to be able to change (set) the DeviceID of an IO-Link sensor (see DeviceID.png) at runtime. I tried with both ProfinetCommon.PN_PortConfiguration and ProfinetCommon.IOL_PortConfiguration, but I get an error for both when I try to read the port configuration (see PN_PortConfiguration.png). Does one of those FBs is the right one for my purpose? Do I possibly make a mistake when assigning the parameter IOLD_ID/IOLM_ID?
Last updated: 2025-03-19

Post by alexgooi on OPC-UA and other communication questions ^{CODESYS Forge talk (Post)}
Dear forum, I currently have a big question mark above my head, and maybe this forum can shine some light on the situation. I recently updated to Codesys 3.15 SP19 Patch 6. And now I’m trying to setup the OPC-UA server, besides that I’m trying to connect to the controller with the Codesys V3 (Ethernet) protocol. OPC-UA I have installed the correct licenses on my controller (Runtime and communication). I’m able to connect to the controller with an OPC-UA client, and I’m able to browse the tags, so far so good. Therefore I’m assuming that the OPC-UA server is running on the controller. But now the strange part, in the device security settings I have set the communication Policy to BASCI256SHA256 ( I also have tried the other ones) and the communication mode is set to secure if possible (I also have tried all the other ones) (see picture). With these settings I would assume that I would only be able to login with a Basic256SHA256 policy with a client. But the opposite is true, I am able to login using the no policy mode and when I set it to Basic256SHA256 the client (UA-Expert) notes that this policy is not available on the server. I then check the certificates and I noted that there is no certificate for the OPC-UA server, I tried to generate one but it gave the error that the certificate has not been created by the device (See picture). To summarize I have no clue what is going on, and the controller does the opposite of what I would expect. Codesys Ethernet V3 driver I have a HMI connected to the same controller using the Ethernet V3 driver. But this will not connect. I tried all the Protocols (see picture), with and without the username and password enabled. But it will not connect, when I scan the available servers I can see the controller with the port number that I am expecting, so I’m assuming that the Codesys V3 ethernet driver is up on the controller. Does anyone can give me some direction, because the stuff that I tried doesn’t make sense to me. Thank you in advance
Last updated: 2024-04-02

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 eschwellinger on Stop raspberry from executing a plc program ^{CODESYS Forge talk (Post)}
/var/opt/codesys/PLCLogic as soon you have dowloaded the project to the Pi it will run the bootapplication no connection to the pc is needed anymore
Last updated: 2023-08-24

Post by patrik on CODESYS Control for Raspberry Pi SL on Raspberry Pi 4b ^{CODESYS Forge talk (Post)}
Hi! I'm 99% sure I'm running CoDeSys on a raspberry pi 4b. just be aware that there is a separate license for running it on multiple cores. https://store.codesys.com/en/codesys-control-for-raspberry-pi-mc-sl.html
Last updated: 2023-09-05

Post by kumareasu on Code Size ^{CODESYS Forge talk (Post)}
Hello, How to find the following for for my application when I want to switch over to "Application Based Licence"... Code Size. IO size When I use Analog IO. IO size when I use AC inverter(Drive for AC induction motor). For example we read/write few EtherCAT registers.
Last updated: 2023-09-07

Post by danwoodlock on RPI Zero w - Edge gateway cant install ^{CODESYS Forge talk (Post)}
I believe the reason that I eventually lose my ability connect is because of exceeding the time limit for demo mode. Still unsure why I cannot update the edge gateway though.
Last updated: 2023-09-13

Post by danwoodlock on RPI Zero w - Edge gateway cant install ^{CODESYS Forge talk (Post)}
Thanks very much for the explanation. I am basically new to the rpi world, but somewhat familiar with the indraworks/CtrlX versions of codesys. Appreciate your help.
Last updated: 2023-09-13

Post by transmin01 on PCAN serial "No CAN driver found" ^{CODESYS Forge talk (Post)}
Second question is, how do I determine the correct network ID for my Canbus config in Codesys? I have 2 CANbus ports on the target PC. Regards Trevor
Last updated: 2023-09-14

Post by transmin01 on Correct CAN Driver for EL6751 ^{CODESYS Forge talk (Post)}
Hi, does anyone know what is the correct driver name that needs to go into the CodesysControl.cfg file for a Beckhoff EL6751? TIA Trevor.
Last updated: 2023-09-19

Post by eschwellinger on PCAN serial "No CAN driver found" ^{CODESYS Forge talk (Post)}
which system are you using on the target system? If this is Linux this is different - in compare to use it on Control Win
Last updated: 2023-09-20

Post by conny-nm on onewire bus master stop working after 4.8.0.0 upgrade ^{CODESYS Forge talk (Post)}
Habe ein ähniches Problem Ethercat läuft nur mit RT 4.8.0.0 nicht aber Onewire. Füge ich ForceFile läuft Onewire, nicht Ethercat. Bei IecFilePath.3 läuft Ethercat nicht aber Onewire
Last updated: 2023-09-20

Post by eschwellinger on onewire bus master stop working after 4.8.0.0 upgrade ^{CODESYS Forge talk (Post)}
du musst Onewire in einer eigenen Task aufrufen, das sind blockierende Aufrufe das geht nur in eigener Task, hab hier mal im Forum ein Beispiel gepostet
Last updated: 2023-09-20

Post by augmue on onewire bus master stop working after 4.8.0.0 upgrade ^{CODESYS Forge talk (Post)}
ich lese alle 4 Sekunden einen Sensor DS18B20 aus Datei im Verzeichniss /mnt/1wire mit USB-Adapter und owfs [SysFile] IecFilePath.3=/mnt/1wire
Last updated: 2023-09-20

Post by derpaul on PFC200 Update to 4.9.0.0 - No Connection ^{CODESYS Forge talk (Post)}
This is: 02.04.22(06) As I do see now, minimal Version is 17, but why did my Controller work with Runtime 4.8.0.0 (Which was the last installed When I remember correctly)
Last updated: 2023-09-28

Post by martinlithlith on CODESYS Control for Raspberry Pi SL on Raspberry Pi 4b ^{CODESYS Forge talk (Post)}
Feedback: I have a raspberry pi 4 (not + as in original question). It works fine to run the CODESYS Control for Raspberry Pi SL license on a pi 4.
Last updated: 2023-10-17

Post by janber0206 on RPI is license server down ^{CODESYS Forge talk (Post)}
I had the same problem. Problem solved: all licences purchased before October 2022 must be updated by Codesys. To do so, simply contact the support in the Codesys Store.
Last updated: 2023-10-30

Sort by relevance or date