Post by wollvieh on Raspberry Pi Runtime 4.22.0.0 vs. 4.20.0.0 I2C Bus not running...
CODESYS Forge
talk
(Post)
... the stars needed? --> yes! [CmpCharDevice] PermittedPath.0=/dev/i2c* PermittedPath.1=/dev/spidev0.0 PermittedPath.2=/sys/class/gpio/* PermittedPath.3=/dev/gpiochip* For me it worked with this additional settings in the file /etc/codesyscontrol/CODESYSControl_User.cfg.
Last updated: 2026-10-16
Runtime 🇬🇧
CODESYS Forge
talk
(Discussion)
Related questions to SoftPLCs e.g. Raspberry Pi, Beaglebone, IoT2000 and other platforms
Last updated: 2026-10-16
Post by eschwellinger on Raspberry Pi Runtime 4.22.0.0 vs. 4.20.0.0 I2C Bus not running...
CODESYS Forge
talk
(Post)
sorry, yes stars needed
Last updated: 2026-10-16
Mismatch between coordinate monitor and actual motion using SMC_GroupJog2, MC_MoveLinearAbsolute (6DOF)
CODESYS Forge
talk
(Thread)
Mismatch between coordinate monitor and actual motion using SMC_GroupJog2, MC_MoveLinearAbsolute (6DOF)
Last updated: 2026-10-16
Raspberry Pi Runtime 4.22.0.0 vs. 4.20.0.0 I2C Bus not running...
CODESYS Forge
talk
(Thread)
Raspberry Pi Runtime 4.22.0.0 vs. 4.20.0.0 I2C Bus not running...
Last updated: 2026-10-16
Post by dmb-fan on Hilscher cards CoDeSys Control RTE
CODESYS Forge
talk
(Post)
Now it sounds not so good anymore... I don't get it. The help-site is a joke. Is there anywhere manuals or docs? Or maybe somebody show me a working CODESYSControl.cfg with CIFX50E-DP and CIFX50E-CO ? Are there 1 or 2 entry for componentnes in the gui? Is slot no. this no. in the gui or any other number? What is the Device-No. ? When I tried Win hang, or PLC hang. Log not writing or not telling me the problem. Is 2026 and for this basic things I have to do trial and error?
Last updated: 2026-10-20
Post by timvh on Block the program upload
CODESYS Forge
talk
(Post)
Don't share your username and password.
Last updated: 2026-10-21
Block the program upload
CODESYS Forge
talk
(Thread)
Block the program upload
Last updated: 2026-10-21
Post by poliautomacao on Block the program upload
CODESYS Forge
talk
(Post)
Hello, how can I block the upload of my project so that no one can download my PLC program?
Last updated: 2026-10-21
Post by dmb-fan on From target start Win OnScreenKeyboard
CODESYS Forge
talk
(Post)
Hi ! I am get crazy.... I try to start osk.exe from Visu or PLC. From Visu I can't load it, always error (It change from programm execute always to load receipe ..!?!?) From PLC always freeze of PLC, - I allowed the win service of the PLC the data exchange between desktop and service - I allowed in ..user.cfg [SysProcess] Command=AllowAll Shutdown with SysProcessExecuteCommand works, but 'osk.exe' or the complete path always crashed the system. And like always: No documentation. Just guessing. Or know somebody more and have a link for me? THANKS !
Last updated: 2026-10-27
Post by caspershes on Checking the device tree, not just the code: what else is worth a static check?
CODESYS Forge
talk
(Post)
I spend most of my time reviewing other people's CODESYS projects before commissioning, and two kinds of defects keep showing up. Both compile clean. Both read fine. One is in the code. A pause timer whose own input gets cleared inside the branch the timer is supposed to gate: rampDelay(IN := run_2); IF NOT run_2 OR rampDelay.Q THEN run_1 := TRUE; run_2 := FALSE; // the timer's own input, cleared right here ELSE run_1 := FALSE; run_2 := FALSE; END_IF Next scan IN is FALSE, the timer resets, the condition is true again, and the second pump starts immediately. A 30-second ramp delay that actually lasts one task cycle. The setpoint is on the HMI, the operator turns it, and nothing changes. The other is not in the code at all. On one site the outdoor temperature read 0.0 °C in mild weather. The ST was correct, the variable was bound to the channel — but the channel's sensor type was left at "disabled", so nothing was ever digitised. Same class: a module with Disable_module = TRUE, or an analog output bound to a variable while its mode is off. Nothing in the project reports any of this, and the code review never looks there, because the configuration lives in the device tree and not in the POUs. That second class is what pushed me to parse the .export format rather than PLCopenXML alone — the export carries the device tree and the visualization, so "nothing ever writes this alarm variable" stops being a guess and becomes a fact you can check against the screen bindings. Three things about the format that cost me time, in case they save you some: the same device parameter can appear three times (template, internal copy, actual configuration) — the last occurrence is the one in effect; the enum value of a parameter is not in the parameter itself, it is one level down in BaseType/Value; a channel counts as used when a variable is bound to SensorValueN.SensorValue — InputStatus is a bad indicator, people deliberately bind it on spare inputs. So the question. What else would you check automatically, given both the code and the device tree? I am collecting rules from sites, not from style guides, and the configuration side feels largely unexplored. For what it is worth, the checker I use for this is free and runs offline (single exe, no install, nothing uploaded anywhere): https://github.com/caspershes/plc-lint — 43 rules at the moment, reads .export and PLCopenXML. Happy to add rules people here suggest.
Last updated: 2026-10-27
Checking the device tree, not just the code: what else is worth a static check?
CODESYS Forge
talk
(Thread)
Checking the device tree, not just the code: what else is worth a static check?
Last updated: 2026-10-27
To search for an exact phrase, put it in quotes. Example: "getting started docs"
To exclude a word or phrase, put a dash in front of it. Example: docs -help
To search on specific fields, use these field names instead of a general text search. You can group with AND or OR.