Codesys 3.0 and UML ^{CODESYS Forge talk (Thread)}
Codesys 3.0 and UML
Last updated: 2006-12-10

Visu Symbols and target visu ^{CODESYS Forge talk (Thread)}
Visu Symbols and target visu
Last updated: 2018-07-13

SMC_NCInterpreter with SMC_RoundPath and SMC_ToolRadiusCorr ^{CODESYS Forge talk (Thread)}
SMC_NCInterpreter with SMC_RoundPath and SMC_ToolRadiusCorr
Last updated: 2020-05-18

System Date and Time Function ^{CODESYS Forge talk (Thread)}
System Date and Time Function
Last updated: 2024-01-05

System libs and I/O Drivers ^{CODESYS Forge talk (Thread)}
System libs and I/O Drivers
Last updated: 2024-02-02

Socket communication with username and password ^{CODESYS Forge talk (Thread)}
Socket communication with username and password
Last updated: 2024-02-24

Raspberry and problem with runtime ^{CODESYS Forge talk (Thread)}
Raspberry and problem with runtime
Last updated: 2024-02-28

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

OPC-UA and other communication questions ^{CODESYS Forge talk (Thread)}
OPC-UA and other communication questions
Last updated: 2024-04-06

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

Data source and safety PLC ^{CODESYS Forge talk (Thread)}
Data source and safety PLC
Last updated: 2024-06-17

Get DataSources Items list and status ^{CODESYS Forge talk (Thread)}
Get DataSources Items list and status
Last updated: 2024-06-18

Wbm/runtime and visualization login ^{CODESYS Forge talk (Thread)}
Wbm/runtime and visualization login
Last updated: 2024-06-25

Unhandled exception and refactoring error ^{CODESYS Forge talk (Thread)}
Unhandled exception and refactoring error
Last updated: 2025-12-10

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

Resize and position Numpad/Keypad ^{CODESYS Forge talk (Thread)}
Resize and position Numpad/Keypad
Last updated: 2026-04-15

TCP communication and TCP Streams ^{CODESYS Forge talk (Thread)}
TCP communication and TCP Streams
Last updated: 2026-06-16

Lenze i950 Servo and WAGO PFC200 ^{CODESYS Forge talk (Thread)}
Lenze i950 Servo and WAGO PFC200
Last updated: 2026-02-13

Post by matthew on High resolution displays with 150% scaling causes CodeSys IDE to be blurry ^{CODESYS Forge talk (Post)}
I have just upgraded my laptop which has a high res display 2560x1600 and I have to have scaling switch on at 150% but everything looks blurry and not crisp, It seems CodeSys IDE is the only software on my system to look this bad, if I switch to 100% it's crisp but way to small. From a bit of research this could be due to the use of old windows forms or something? I have found a temp workaround that sort of works but not great. You have to run CodeSys in compatibility mode and adjust the DPI settings, this works ok and the editor is clear and crisp again but the actual tool bars are small like running at 100% Anyone got any tips for running CodeSys on high res displays with scaling?
Last updated: 2025-03-03

Post by talpade on WAGO PLC 200 750-8216 Ethernet connection to Codesys 3.5 ^{CODESYS Forge talk (Post)}
Hello, I have the WAGO PLC 200 750-8210. In addition I have downloaded the "WAGO Devices and Libraries 2.0.4.3" and installed the library into the Codesys v 3.5. I then create a new project on Codesys 3.5 and select the device "750-8216 PFC200 (WAGO)" (which I downloaded from the WAGO library). However when I have connected the ethernet cable from the WAGO device to my computer and on my codesys 3.5 i press "Scan Network" on codesys and it does not detect the device. How can I get it to detect the device? (I have put the ethernet cable from my WAGO to the computer, but it does not show the device).
Last updated: 2024-02-05

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 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 westcountryewe on Persistence Variables missing and DO NOT retain from Persistence Channel when using Boot Application ^{CODESYS Forge talk (Post)}
We've been experiencing an issue through SP18, SP19 and now SP20 where the Persistence Variables do not retain if we upload our program via a Boot Application. If we use the exact same program, and perform a Direct Upload via the Laptop and Ethernet connection, the Persistence Variables work exactly as expected. I have submitted 2 bug support tickets but I haven't had a response back from Codesys. Has anybody experienced the same issues and discovered a workaround? We have a requirement to utilise the Boot Application method because of logistical restrictions of being able to get out to every site, so at the moment it's a bit restriction.
Last updated: 2024-05-15

Post by cer-wa on Not able to connect multiple profinet encoder in codesys Linux ARM64 ^{CODESYS Forge talk (Post)}
Hello, currently im working with a RevPi connect 5 on a codesys project. Up until now I was having a blast because things were going really smooth but for like almost a day im kind of stuck on the integration of multiple profinet sensors into my project. This is kind of a bummer because that should be an easy thing to do. What I tried so far was to create and additional ethernet adapter where I then tried to connect my devices. in the beginning I tried to connect the devices directly which was not working because I could assign the IP-adress only to the ethernet adapter and not to the devices but the device was found in the device repository (this gets important in the second part) So what I tried next was to setup a PN-Controller and connect my devices subsequently to the Controller. Sadly now the devices wont show up in the device repository anymore. To me its not clear why this is happening. And the worst thing is: I went ahead and setup a device completely like I would want to have it in the project and when I then click on scan devices I can even find the device. But it can not be added to project for whatever reason eventhough im 100% certain that the gsdml file is the correct one. Can anyone help me with this. Like I said this seems like an easy thing to do and its taking me way longer than expected already. The only thing that came to my mind why this might not work is because I have codesys license which only allows one profinet instance. Could that be the case? The error message seems then pretty unfit but ok. I will be grateful for every advice. Thanks in advance! Best regards!
Last updated: 2025-09-25

Post by antonz on CoDeSys v3.5: creating libraries for both 32-bit and 64-bit controllers ^{CODESYS Forge talk (Post)}
Looking for thoughts on creating libraries that can be used on both 32-bit and 64-bit controllers. We are currently writing software in CoDeSys for both target types and will continu to do so for the near future. Projects are always unique, no straight forward copy/paste, yet there is enough similarity between them to use libraries for recurring logic. I do not want to create and maintain twice for both platforms if this is not absolutely necessary. I am aware of useful datatypes like __XWORD, __XINT, __UXINT. Still looking for more information and/or sample code for portable pointer arithmetic. In addition to that: how should one go about when creating and working with compiled libraries? Would I need to compile the same lib twice, once for 32-bit targets once for 64-bit targets? I would end up with two different libs with the same namespace, which does not sound elegant to me. Note: I did not intentionally make the previous paragraph bold. The forge forum software seems to do this automatically upon insertion of a word which starts with two underscores, e.g. __XWORD (yeah, here we go again :) )
Last updated: 2025-08-25

Sort by relevance or date