Post by fred on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
Hi, I have Proxmox running on a Rasperry 4 and have debian 12 ARM installed here. I wanted to install Codesys Control for Raspberry on it. According to the messages, the runtime environment and the gateway were installed successfully, but I can't find a device to downplay a program. The sudo service codesys start command fails. (see image) Does somebody has any idea? Thank you for your help! Greetings Fred
Last updated: 2023-11-22

Post by vincentger on using ADS1115 ^{CODESYS Forge talk (Post)}
Any reason the ADS1115 wouldnt work with SP20.1 and Runtime 10.0.0.0 on the Raspberry Pi . Using Bullseye or Buster i run into the same issue: Libary and integration works in general as described above BUT i am seeing "bleeding" between the analog inputs . Specifically consecutive ones: So sometimes the raw from AI1 shows on AI2, AI2 on AI3, .. AI4 on AI1. Even with filtering i cant smoothen that out properly and i feel like something is wrong. Almost like the bus is stumbling over itself, or the request from Codesys to the device.
Last updated: 2024-10-28

Post by aliazzz on Raspberry Pi 3: Linux/ARMHFv7 unknown container technology ^{CODESYS Forge talk (Post)}
Hi CODESYS team! It seems Podman for Raspberry Pi 3 is not detected correctly in the latest "Deploy Control SL 4.14.0.0" : Linux/ARMHFv7 unknown container technology. 1) The Communication Tab, device information section shows podman technology as DETECTED. 2) The Runtime Deployment menu message says: "unknown container architecture" 3) The pulldown window under the deployment tab doesn't show the options for ARMHF Virtual Edge SL and ARMHF Virtual Control SL. I hope you can fix this soon and keep up the great work!
Last updated: 2024-12-15

Post by fschuler on No connection to Raspberry at runtime installation ^{CODESYS Forge talk (Post)}
Hi, I try to install the Codesys realtime in a Raspberry PI 3B+. When I click on the installation button I get always the message No connection to device: An established connection was aborted by the server. Raspberry 3B+ with newest raspberry PI OS. Codesys 3.5.15 Patch 1 Codesys Runtime Package 3.5.16.20 SSH is activated. I can login with Putty Ping is possible IP address search is possible Just the installation is not started.
Last updated: 2025-07-23

Post by eschwellinger on Licensing info not available. ^{CODESYS Forge talk (Post)}
yes and no ... if you run the license server on the host (to serve licenses to the docker instances / vplcs then there is no runtime which could check the licenses on the host. Therefore you need the CODESYS WBM to activate or check the licenes or you could use in CODESYS IDE the licensemanager ( not the one for the device licenses) but you have the the IP of the license server that he know where to search for the licenses ..tool options i guess to add it, will add a screenshot later.
Last updated: 2025-10-01

Post by miodusy on CODESYS Control Standard S and Beaglebone ^{CODESYS Forge talk (Post)}
Hi, CODESYS Control Standard S + CODESYS Visualization L, CODESYS Control for Beaglebone 4.11.0.0, CODESYS V3.5 SP20 + (64-bit) I have problem that license manager say that this device is not supported when i try active whole license. When I select only runtime and communication it is go next step, but then I no have license on in Visualistion section, all of rest of software metric licese is ok(IO, Istances of com et, code size etc.). Thanks!
Last updated: 2024-05-11

Post by jonasz on Deploy LicenseServer for Linux SL ^{CODESYS Forge talk (Post)}
Hello, I'm asking for help with installing the license server for Linux SL 4.18.0.0. When I try to install it, I get a message that the WIBUCodeMeter package is missing. I checked the package manager tab to see if the package is installed, and it is - Codemeter 8.40.7120.501. I've checked the CodeMeter Runtime on the target machine, and everything seems to be working fine. One thing caught my eye: the Device Architecture tab says "None" Please help me solve this problem.
Last updated: 2025-11-14

Post by pernockham on Images not shown in webvisu ^{CODESYS Forge talk (Post)}
Two issues. Ive been struggling to get the user management the way I want it. I want to protect the device from unauthorized upload/download, but I do not want login requirement on webvisu. The combination that seems to work is to use "runtime device user management" while keeping the visu user management in "legacy mode"? Initially this seemed to work, but now images are not loaded when using direct access, while they are still shown if I access the webpage via Automation server. Im guessing its connected to the authorization changes? Anyone able to help out? Thanks Also, I read that legacy mode should be avoided, is it possible to use "runtime based visu user management" while keeping direct access to the webpage without login. System is a "Control for linux SL, version 4.20.0.0" Per
Last updated: 2026-04-10

Post by yannickasselin on Question about Demo License limitations for Modbus TCP communication and Fieldbus Instances ^{CODESYS Forge talk (Post)}
As far as I know, there is no other limitations than the 2 hours limit. The demo mode should be plenty enough for testing purposes. Regarding instances. In the device tree, 1 master = 1 instance, no matter how many slaves the master is communicating with. But it is also possible that your Codesys runtime act as a slave. In this case, each slave in the device tree is one instance. You can also use the license metric tool in the IDE. This will tell you exactly how many instances you have in your project. https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_edt_device_licensed_software_metrics.html
Last updated: 2026-02-28

Post by pernockham on Pointer/reference to Codesys trend recording object? ^{CODESYS Forge talk (Post)}
I have a Hmi that acts as an interface for many (mostly identical) units. This is managed by a sort of "mux" where you select which unit that should be presented on the HMI. Backbone is solved by a HMI-gvl defined as reference/pointer to "unit-data", which then can be set to the individual units. While this works for most data I still have not sorted how to solve this for the trend recordings. One solution would be to have already "mux:ed" data values as source for the/one trend. However then the trend would contain data from different units/sources which could/will cause confusion. If its possible to "clear" this can be mitigated. Possibly let the trend have its own "mux-selector" (ie, the hmi are focusing on unit#3 however trend data is locked on unit#5), that could also work.. Or, let each unit have its own trend recording, which is focused if the unit is "selected". Can I reach the trend recording objects programmatically (those defined in the device tree)? Ie, can I use a "reference/pointer to these trend recording objects"? There is a field "data source" in the trend properties dialog which seems to resemble what Im looking for? But Im not sure if I can use it in some way, I cannot change anything in this field it only says <local application="">. </local>
Last updated: 2025-09-16

Post by siscu on Raspberry i2c master device ^{CODESYS Forge talk (Post)}
I want to implement an extended I2C master for Raspberry Pi Control. I was hoping for it to be as easy as creating a library with a FB that extends i2cMaster and associating it with a device following the forge drivers documentation, but I haven't managed to make it work as the driver behaves only as an i2c slave. I'm thinking this is because the forge forum only talks about extending i2c, and the master portion is omitted since most users won't want to add a custom one. I'd like to know if I'm doing something wrong. Is it really possible to make an I2C master extension device? If so, are there public examples we can check out? Any info on this topic will be appreciated.
Last updated: 2024-10-16

Post by davidbo on All the things needed for anonymous login to OPC UA ^{CODESYS Forge talk (Post)}
I thought I knew what I am doing, but something is missing what? From Device-Communication Settings select from drop down menu "Device" Select entry "Change Runtime Security Policy" Check the "Allow anonymous login" Select "Symbol Configuration" in your application In settings check "Support for OPC UA features" Check some of the values you want in your set Press the build button in the "Symbol Configuration" Press the button "Configure Symbol Rights" Make sure that Anonymous_OPCUAServer has access right to your "default set" From Device-Communication Settings select "Access Rights" in RemoteConnections-OPCUAServer Anonymous_OPCUAServer should be given modify and view rights I suppose. I can connect with UaExpert but I cannot see my Application or browse my values. What is missing?
Last updated: 2025-09-10

Post by thierry-b on CODESYS device discovery performance in large networks (/16) ^{CODESYS Forge talk (Post)}
Hello, We are using CODESYS 3.5 SP19.70 in an educational environment with several WAGO PFC200 controllers (CODESYS Runtime). Our campus network is currently configured as a /16, which creates a very large broadcast domain. We observe slow device discovery and long scan times when opening the network view. Before restructuring our architecture, we would like to know the recommended network practices for CODESYS: Recommended broadcast domain size for device discovery Possible impact of large networks (/16) on scan performance Usual recommendations (VLANs, /24 segmentation, etc.) Known limitations or points of attention in extended networks Any guidance or official recommendations would be very helpful. Thank you.
Last updated: 2026-03-29

Post by fless on No source code available for profinet library ^{CODESYS Forge talk (Post)}
looks like you are running in a bug in the newest version 4.4.0 of the profinet library or the new library triggers a bug in your code. did you update your profinet device too? you could try to downgrade to an older version of the library. via library manager - placeholders, double click Profinet 4.4.0 in the library column and choose an older version.
Last updated: 2023-08-23

Post by spareparts on SPI Master not running/MCP3008 Missing driver. ^{CODESYS Forge talk (Post)}
I believe I have installed the correct device descriptions and library, in an attempt to use the MCP3008 in conjunction with RPI; when project runs the MCP3008 is unable to find the correct driver. Is there anything I'm missing? Very new to this so any help is apprecated!
Last updated: 2023-09-12

Post by eschwellinger on Correct CAN Driver for EL6751 ^{CODESYS Forge talk (Post)}
Hi, for Control Win : add CmpEL6751CanDrv in the c:\ProgramData\CODESYS\CODESYSControlWinV3x64\E1FA7ABE\CODESYSControl.cfg [ComponentManager] Component.1=CmpTargetVisuStub Component.2=CmpWebServer Component.3=CmpWebServerHandlerV3 Component.4=SysCpuMultiCore Component.5=SysReadWriteLock Component.6=SysCpuBreakpoints Component.7=SysPipeWindows Component.8=CmpEL6751CanDrv for Linux SL or Pi or any ARM device - I think it is already static loaded as component - see plclogger on startup
Last updated: 2023-09-20

Post by exkrim19 on Unable to connect to this device ^{CODESYS Forge talk (Post)}
What worked for me with this error was to go to Tools -> Update Raspberry Pi, select Install, and from the popup screen, there are options to change your installation (I changed it to single core, instead of multicore), and I was then able to connect to my Rpi 4.
Last updated: 2024-06-28

Post by flappyman on licenses question ^{CODESYS Forge talk (Post)}
I hope this tread will be able to help me. I got your new licenses and it was working perfectly fine. Unfortunately, my PLC got severely damaged and it can not run anymore. Is it possible to somehow release the license so I could use it again. I have all information for the device and can provide it.
Last updated: 2024-08-05

Post by wbj0t on tool 'update raspberry pi' unavailable ^{CODESYS Forge talk (Post)}
Hi all. Codesys 3.5.19, patch 3. After installing raspberry 4.10 package I can see raspberry device, but can't see update raspberry pi tool. In custimsation->tools I found: Unknown command (8ec1a...) [plugin unavailable] Unknown command (7216f...) [plugin unavailable] Codesys installed in default directory. I reinstalled Codesys, thats not help.
Last updated: 2024-09-26

Post by winki on Scan Network on gateway created with Control Sl ^{CODESYS Forge talk (Post)}
Hello, I am new on CODESYS environement. I am used to BECKHOFF env. I would like to use codesys on debian distribution. I followed this tutorial : https://www.youtube.com/watch?v=TVF0LV279_4 But I am stuck on selected the device. I do not understand, everything is running correctly Someone have an idea ? Loic
Last updated: 2024-10-16

Post by eschwellinger on RS485 CAN HAT to Cosesys ^{CODESYS Forge talk (Post)}
Hi if you add in (ttyAMA0 should fit to your HAT's device [SysCom] Linux.Devicefile.1=/dev/ttyAMA0 to /etc/CODESYSControl_Usr.cfg since 4.12.0.0 version /etc/codesyscontrol/CODESYSControl_Usr.cfg then access in CODESYS with Com1 should do it. Keep in mind that only adapters work (for RS485) which do determine the send/receive direction in hardware
Last updated: 2024-10-28

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Okay i will try. I tried already the different settings. The CodeSys version i use, is CodeSys 3.5 SP20 Patch 3. The device which i use is CodeSys Control For Raspberry PI 64 SL version 4.13.0.0. The wiring should be okay because i'm using the Edatec ED-CM4IND-1432-4C(EU).
Last updated: 2024-11-07

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
I don't have a multiplexer so it very weird that it connects with that multiplexer. If i do a I2C scan on the PI terminal, i only get the device addresses 0x48 and 0x51. One for the ADC and one for RTC. I will try again with your libraries
Last updated: 2024-11-12

Post by teichhei on The selected container ... does not fit your ticket ^{CODESYS Forge talk (Post)}
After correspondence with Mr Schwellinger from Codesys the resolution for this was to uninstall the SL 4.14 and install SL 4.13 on the device. Once this was done the licensing worked as expected. I noted that the container then showed a Version 3.00 and not 0.00.
Last updated: 2025-01-11

Post by atone on Change IO-Link Device Interface connected to a Profinet-Slave at Runtime ^{CODESYS Forge talk (Post)}
OK, I figured out that I can simply define all the sensors as 16 bytes IN/OUT, even if they are not all used. EDIT: The negative effect is that each bit is taken into account as an I/O for the license, even if not used.
Last updated: 2025-04-28

Sort by relevance or date