Fuzzy Logic PID Controller
CODESYS Forge
talk
(Thread)
Fuzzy Logic PID Controller
Last updated: 2025-11-18
JSON_Utilities_SL JSONFileWriter error NULL_POINTER
CODESYS Forge
talk
(Thread)
JSON_Utilities_SL JSONFileWriter error NULL_POINTER
Last updated: 2026-04-09
Movesuperimposed Command Aborted Error
CODESYS Forge
talk
(Thread)
Movesuperimposed Command Aborted Error
Last updated: 2026-04-13
Sysfile Konfiguration
CODESYS Forge
talk
(Thread)
Sysfile Konfiguration
Last updated: 2026-04-13
internal error
CODESYS Forge
talk
(Thread)
internal error
Last updated: 2026-04-20
Alarmmanagement – Dynamic Alarm List
CODESYS Forge
talk
(Thread)
Alarmmanagement – Dynamic Alarm List
Last updated: 2026-04-25
library inside library
CODESYS Forge
talk
(Thread)
library inside library
Last updated: 2026-04-25
Engineering IDE from linux?
CODESYS Forge
talk
(Thread)
Engineering IDE from linux?
Last updated: 2026-04-27
Network variable stops sending
CODESYS Forge
talk
(Thread)
Network variable stops sending
Last updated: 2026-05-07
V3.5 SP22 Patch1
CODESYS Forge
talk
(Thread)
V3.5 SP22 Patch1
Last updated: 2026-05-08
ReadWriteEEprom FB question
CODESYS Forge
talk
(Thread)
ReadWriteEEprom FB question
Last updated: 2026-05-18
TextList name error (fake)
CODESYS Forge
talk
(Thread)
TextList name error (fake)
Last updated: 2026-06-05
Version management
CODESYS Forge
talk
(Thread)
Version management
Last updated: 2026-06-24
Generic Variables and FDB
CODESYS Forge
talk
(Thread)
Generic Variables and FDB
Last updated: 2026-07-22
Static Analysis Error SA0026
CODESYS Forge
talk
(Thread)
Static Analysis Error SA0026
Last updated: 2026-07-27
Post by eschwellinger on How to reset forgotten User Management / Administrator password on CODESYS Control Win V3 (V3.5 SP22 Patch 2)?
CODESYS Forge
talk
(Post)
since 3.5.20.10 version you should find it here: C:\Windows\system32\config\systemprofile\AppData\Roaming\CODESYS\xxxxxxxx (64Bit) C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\CODESYS\xxxxxxxx (32Bit) you need to have admin rights.
Last updated: 2026-08-26
Enum mit Textliste
CODESYS Forge
talk
(Thread)
Enum mit Textliste
Last updated: 2026-09-17
Post by gseidel on Test
CODESYS Forge
talk
(Post)
Test topic
Last updated: 2026-09-22
Read a webclient value
CODESYS Forge
talk
(Thread)
Read a webclient value
Last updated: 2026-10-08
Block the program upload
CODESYS Forge
talk
(Thread)
Block the program upload
Last updated: 2026-10-21
Post by eoahe on Problem Reading Registers via Modbus from non Codesys device
CODESYS Forge
talk
(Post)
Hey Guys :) I have the following Problem using Modbus via Codesys: I'm trying to implement a Modbus Device into my codesys project. The device is a Router from Teltonika (RUT956) and it can communicate via Modbus. Currently I'm trying to implement it into my codesys prject as a slave and I'm using my windows computer as master. As it is not a codesys device (the codesys application is not uploaded to device as it has its own software) I'm having problems requesting and reading registers from the router. I've set up my windows computer as Master and implemented the router as slave. When I go online on my master device it sais that it has established a connection to the slave (router)(So I'm thinking this could work as there is a connection?). The goal is to read the GPS (latitude and longitude) data and on the homepage of teltonika you can find the register address and number of registers (adress 143 for latitude and 145 for longitude; both have a number of two registers). I've found tutorials how to read specific registers via their register address with other modbus programs (like modbus-cli), but as my entire project is established in codesys I was hoping to read these specific registers via codesys so that I can show the GPS data on my dashboard. I've tried establishing slave channels but that hasn't been working. I tried read input register channels of the length 4 but it's not possible to define specific register addresses to read via codesys so that didn't work (I jsut get a slaves device failure) and I've also tried establishing 516 (total number of registers the router sends I think?) read inputregister channels but that has the samle failure... So i guess the problem I'm having is establishing slave channels to read these specific registers. Does anyone know how to tackle this problem and has maybe had the same problem? Or maybe someone knows a workaround? I'm quite new to codesys so maybe I'm also lacking expertise...
Last updated: 2025-03-01
Post by kurtk on SysProcess Execute Command unable to run commands with special characters
CODESYS Forge
talk
(Post)
Thank you for this additional information. Could you please provide the references to the official documentation where you found this information ? I got as far as: Then insert this: [SysProcess] BasePriority=Realtime Command=AllowAll devoid of references of where the CodesysContol.cfg file was located or of the need to run codesys as root I incrementally located bits of information with perplexity searches but remained mired at error 25 ERR_NO_ACCESS I am curious whether root access is MANDATORY to run SysProcessExecuteCommand (- and/or any other SysProcess functions) or if a more access-constrained User=quasiroot could suffice without the security concerns ? Apparently codesys runs fine without User=root for almost everything... That raises the question: What IS the default codesys user ? I notice in the prototypes: VAR sCommand : STRING := '/usr/bin/whoami'; sOutput : STRING(255); refCommand : REFERENCE TO STRING; refOutput : REFERENCE TO STRING; resultCmd : UDINT; END_VAR whenever I attempt to build this Codesys v3.5 SP2 whines that "cannot convert type REFERENCE TO STRING to STRING" don't remember the exact message... Apparently this happens whenever a fixed-length string is involved. if I get rid of (255) and just set the string := ' '; that is sufficient to make the compiler happy. Is this a recently enforced constraint ? Why does this compile for you and not for me ? There are references to functions / utilities which are used/needed to massage the string references - but I see no specific details... I also notice you specify: Make sure the lib SysProcessImplementation, SysTypes, and CmpErrors is on the project. I don't comprehend why all of the dependent libraries are not automatically referenced, added ? I don't recall seeing anywhere but here that SysProcessImplementation must be included... It just seems odd that the default is to exclude essential libraries, or require alchemical conjuring to assemble all the ingredients for gnat soup ;-) Thanks a lot... I'm still a codesys newby getting my wheels on - or sometimes just partially on
Last updated: 2025-09-12
Post by danp1406 on Question about Demo License limitations for Modbus TCP communication and Fieldbus Instances
CODESYS Forge
talk
(Post)
Hello everyone, I am currently working with CODESYS Virtual Control for Linux running in Docker on a Debian virtual machine. I am deploying my application using Deploy Control SL, and in my project I am using the ModbusFB library to implement Modbus TCP communication. My setup is the following: I am trying to establish a Modbus TCP connection between a virtual PLC (CODESYS acting as Modbus TCP Client/Master) and a Siemens S7-1200 PLC acting as a Modbus TCP Server. From the Debian VM, I can successfully ping the S7-1200 and verify that port 502 is open using tools like nc. Network-wise, everything appears to be correct. However, when running the application in CODESYS, I receive messages such as “Demo mode for Modbus/TCP Master started. Will expire and stop!” and socket errors like “ClientSocket.UpdateStatus socket error 111 disconnecting.” The ClientTCP block from the ModbusFB library attempts to connect, but the connection does not remain stable. My main question is whether the CODESYS demo license explicitly limits or interrupts Modbus TCP Master communication. Is it expected that in demo mode the runtime will automatically close sockets after some time or prevent stable Modbus TCP connections? I would like to confirm whether this behavior is normal when using ModbusFB in demo mode, or if I should continue troubleshooting the configuration. Additionally, I would like clarification regarding the “fieldbus instances” mentioned in CODESYS licensing options (for example, 2, 4, or 16 instances). What exactly is considered one fieldbus instance? Does one Modbus TCP Client block count as one instance? Does each active connection to a different device count separately? Do Modbus TCP Master and Server count independently toward the total number of instances? Finally, I would appreciate clarification on any other practical limitations of demo mode when using industrial communication libraries such as ModbusFB. Are there limits on the number of connections, number of requests, or communication duration? I am trying to determine whether demo mode is sufficient for testing a virtual PLC communicating with a Siemens S7-1200 over Modbus TCP, or whether a full license is required even for this kind of validation scenario. Thank you in advance for any guidance.
Last updated: 2026-02-25
Post by trusty-squire on Codesys for raspberry pi 5 not working exactly
CODESYS Forge
talk
(Post)
Not sure if you've resolved this yet, but the Codesys runtime user/password is different than the Linux user/password. You'll need the Linux user credentials when you log in over SSH (for example, to install the Codesys runtime). When you first log in to Codesys on the RaspPi you'll set up a Codesys user and password. If you lost those credentials, you could try uninstalling and then re-installing the Codesys runtime on the RaspPi so you can setup a new user/password.
Last updated: 2025-03-16
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.