Post by mp9876 on Problems with simulation in Window 10 ^{CODESYS Forge talk (Post)}
Hi Automa, it seems the solution you were bringing up on 2022-04-06 could really help me as I did not remember the password I initially set. My problem though is that I am using Codesys Control Win V3.5 SP19/60 (64 bit) and I cannot locate any of the files you listed up there. I have been looking inside folder: C:\Program Files\CODESYS 3.5.19.60\CODESYS\ and they appear not to be present at all neither in the CODESYS folder or any sub-folders. Uninstalling and re-installing unfortunately does not do the trick. Any idea how I could get out of the ditch on this issue ? Anyone else maybe ? Thanks
Last updated: 2024-03-18

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 wollvieh on Problem while updating to new runtime 4.11.0.0 ^{CODESYS Forge talk (Post)}
okay, no ideas. So i made a new fresh image for the raspberry, so far,so good. Licensing the new image was no problem. And, after having trouble while read write files on the raspberry pi, i found the solution for these file operations with the Variable ForceIecFilePath in the CODESYSControl.cfg file. Some people had that issue discussed in that thread : https://forge.codesys.com/forge/talk/Deutsch/thread/d2df08e587/
Last updated: 2024-03-18

Problem while updating to new runtime 4.11.0.0 ^{CODESYS Forge talk (Thread)}
Problem while updating to new runtime 4.11.0.0
Last updated: 2024-03-18

Post by wmoon on Licensing info not available. ^{CODESYS Forge talk (Post)}
Hello, I bought some licenses from CODESYS store. I am trying to install licenses into my device(CODESYS Control for Linux ARM64 SL). But I have a trouble with it. I did it in the following order. Tool -> License Manager Selected Device and Next... Selected Soft container and Next... Select the device and Ok.. And then I always show a message "Licensing info not available. There is no dongle attached to the device." And I tried to click "Install Licenses" button. I saw the message "The value cannot be NULL. Parameter name : continerToLicenses" Could you let me know what I've missed or what I've got wrong?
Last updated: 2024-03-19

Post by cavein on PFC100 Licensing fails ^{CODESYS Forge talk (Post)}
Hi, i have a similar problem. im using pfc200 4.5.0.0. There are two softcontainer and only one with license in it. every 1-2 hrs it will auto logoff. i tried the steps above but i dont find the /var/opt/codesys/.cmact_licenses i need help please.
Last updated: 2024-03-19

Post by thewizard8 on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
Hi eschwellinger, Thanks for replying, but I'm not shure if I got it right. Do you mean that I have bad configuration on my CODESYS config file? Or in my project? Thanks in advance!
Last updated: 2024-03-19

Post by doli on Table icon ^{CODESYS Forge talk (Post)}
Hello. I have a simple table in codesys. My first column is icon and on every row I want to have an icon. How can I add it? Thank you!
Last updated: 2024-03-19

Codesys table border ^{CODESYS Forge talk (Thread)}
Codesys table border
Last updated: 2024-03-19

Post by doli on Codesys table border ^{CODESYS Forge talk (Post)}
Hello. I have a simple table in codesys. How can I remove the right border from all the cells and change just the color of border from table (not header)? Thank you!
Last updated: 2024-03-19

Table icon ^{CODESYS Forge talk (Thread)}
Table icon
Last updated: 2024-03-19

Post by timvh on Device logon problem following fresh install ^{CODESYS Forge talk (Post)}
In your project you selected the "CODESYS Control Win V3" as device, but the device you want to connect to is a "CODESYS Control Win V3 x64". Those are not the same. If you double click on the device during the network scan, you will get information that these are not the same, but that you can change the type in your project to the x64 bit type. Another option is to "right-click" on the device in the device tree of your project and select "update device" then select the x64 type.
Last updated: 2024-03-19

Post by eschwellinger on Licensing info not available. ^{CODESYS Forge talk (Post)}
check on cli on your device 'cmu -x'
Last updated: 2024-03-19

Raspberry Pi 4 als SPI Slave ^{CODESYS Forge talk (Thread)}
Raspberry Pi 4 als SPI Slave
Last updated: 2024-03-19

Post by tama00 on Raspberry Pi 4 als SPI Slave ^{CODESYS Forge talk (Post)}
Hallo zusammen, grundsätzlich sollte ja die Möglichkeit bestehen den Raspberry auch als SPI Slave zu nutzen. Leider habe ich kein entsprechendes Projekt gefunden, bei dem dies der Fall war. Kann mir jemand dabei weiter helfen, wie ich bei Codesys Control for Raspberry , die Konfigurationen für den SPI Slave machen kann? Der Master soll ein Microkontroller sein von einem anderen Gerät sein. Ich arbeite noch mit 4.10.0.0 und einem Raspberry Pi 4 Vielen Dank und liebe Grüße
Last updated: 2024-03-19

Post by eschwellinger on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
no config file is ok, the feedback is: your hardware must support this send/receive switching
Last updated: 2024-03-19

Post by squiggleypuff on RemoteTargetVisu creates Unresolved Reference ^{CODESYS Forge talk (Post)}
I have a project with a Festo CPX-E-CEC-C1-PN PLC (Run-time version 3.5.12.50) that I have been developing on just fine using Codesys V3.5 SP19 Patch 5 (64bit). I am at the stage where I wanted to use the Festo HMI screen, and have added a RemoteTargetVisu object to my application. After adding this object, I am no longer able to log in to the PLC as I get an Unresolved Reference warning for 'USERMGRUSERGETPROPERTY' towards the end of the download process. I was able to find this post (https://forge.codesys.com/forge/talk/Visualization/thread/fc686a6cb2/) where the two possible solutions are to "set the placeholder to emtpy" or update the runtime. Problem is, I don't know how to do either of these things, as I'm still very green in Codesys land. I'd be happy to update the Festo PLC runtime, as that seems like the better option, but have not had any luck in finding a tutorial for this online. If anyone could point me in the right direction I'd appreciate it.
Last updated: 2024-03-19

Post by eschwellinger on PFC100 Licensing fails ^{CODESYS Forge talk (Post)}
possible to use a newer version? maybe it is /var/opt/codesys/cmact_license in your version
Last updated: 2024-03-19

PFC100 Licensing fails ^{CODESYS Forge talk (Thread)}
PFC100 Licensing fails
Last updated: 2024-03-19

Post by umdee on Error when monitoring LAD programs ^{CODESYS Forge talk (Post)}
System Information from the computer being used: OS Name Microsoft Windows 11 Pro Version 10.0.22631 Build 22631 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Manufacturer Dell Inc. System Model Latitude 5500 System Type x64-based PC System SKU 08B9 Processor Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz, 2112 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date Dell Inc. 1.3.11, 6/11/2019 SMBIOS Version 3.2 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer Dell Inc. BaseBoard Product 0M14W7 BaseBoard Version A00 Platform Role Mobile Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "10.0.22621.2506" User Name CARDASSIA-IX\Engineer Time Zone Eastern Daylight Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 15.8 GB Available Physical Memory 4.67 GB Total Virtual Memory 18.5 GB Available Virtual Memory 2.52 GB Page File Space 2.63 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Windows Defender Application Control policy Enforced Windows Defender Application Control user mode policy Off Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes
Last updated: 2024-03-19

Device logon problem following fresh install ^{CODESYS Forge talk (Thread)}
Device logon problem following fresh install
Last updated: 2024-03-19

Device User Logon ^{CODESYS Forge talk (Thread)}
Device User Logon
Last updated: 2024-03-19

Assertion Failed ^{CODESYS Forge talk (Thread)}
Assertion Failed
Last updated: 2024-03-19

Post by mp9876 on Device logon problem following fresh install ^{CODESYS Forge talk (Post)}
Yes it had been the case I believe as I have seen that message regarding they were not the same. I had update the device though to match them and that still did not fix the problem. I gotta say I wanted to get out of that situation and attempted a lot of things and then I did two things at the same time that fixed my problem: Wiped the 64 bit version and installed the 32 bit version Installed latest SP20 I wish I knew which one of these actions fixed the problem but now I gotta catch up on this IDE learning; it's been quite a learning experience I have to say! Thank you very much for your time and advice; much appreciated!
Last updated: 2024-03-19

Post by mp9876 on Device User Logon ^{CODESYS Forge talk (Post)}
Following up on the invalid user authentication on the target Not 100% sure what the problem was but following my post I managed to create an administrator level user. Then my next issue was that I could not connect to the device. I might have flipped the device from a 64 bit version to a 32 bit version so I did UPDATE DEVICE back to the 64 bit version; still could not connect somehow. Then I did two things at the same time that fixed my problem: Wiped the Codesys Control Win 64 bit version and installed the 32 bit version Installed latest Codesys Control Win V3.5 SP20 (released today) I wish I knew which one of these actions fixed the problem but at least the problem is solved. Hoping this post may help someone one day
Last updated: 2024-03-19

Sort by relevance or date