Post by osande on Trend/trace data ^{CODESYS Forge talk (Post)}
Anyone have problems with trend in lastest release - SP21 Patch5? Does not record data, stores only zeros to the sqlite database and flatliners at zero in trend/trace views. Worked in P4.
Last updated: 2026-03-12

Post by mjam04 on AM243 LaunchPad as PROFINET Device with CODESYS – RPC Aborted error when scanning devices ^{CODESYS Forge talk (Post)}
Hello, I am currently trying to use the AM243 LaunchPad as a PROFINET device and connect to it using CODESYS. In my setup I am also using a Raspberry Pi running the CODESYS PROFINET Runtime, which acts as the PROFINET controller. The setup of the Profinet controller is correct, so all devices are in the same subnet. However, I encounter an issue when scanning for PROFINET devices in CODESYS. The AM243 LaunchPad appears in the scan results, but the following error is reported: RPC Aborted: 0x16C9A049 Additionally, CODESYS shows the message that the identification data is not available and the IP address should be checked. Because of this error, the controller cannot establish a connection to the device. Another observation is that I cannot ping the AM243 LaunchPad from my PC, even though I configured what should be the correct IP address. Setup: PROFINET Device: AM243 LaunchPad PROFINET Stack: Industrial Communication SDK example PROFINET Controller: Raspberry Pi running CODESYS with PROFINET Runtime Engineering PC: CODESYS IDE Network: Ethernet connection between PC, Raspberry Pi, and AM243 In the attachments there is a screenshot of the corresponding error. Did anybody had the same error? Any hints or debugging suggestions would be greatly appreciated. Thank you!
Last updated: 2026-03-13

Post by osande on Trend/trace data ^{CODESYS Forge talk (Post)}
Trend ....
Last updated: 2026-03-13

Trend/trace data ^{CODESYS Forge talk (Thread)}
Trend/trace data
Last updated: 2026-03-13

Post by osande on Trend/trace data ^{CODESYS Forge talk (Post)}
Ok, the problem is that the trend/trace system can't read function block instance data. The variables has to be stored directly under the program calling the FBs. Thus, FB variables to be trended/traced must be connected to variables declared in the program. Seems like a bug to me!
Last updated: 2026-03-13

Post by osande on Trend/trace data ^{CODESYS Forge talk (Post)}
The standard Trace works...
Last updated: 2026-03-13

UC20-M4000 Redundancy – Application is not automatically synchronized and redundancy breaks after online change ^{CODESYS Forge talk (Thread)}
UC20-M4000 Redundancy – Application is not automatically synchronized and redundancy breaks after online change
Last updated: 2026-03-16

Post by mrkm-dic on UC20-M4000 Redundancy – Application is not automatically synchronized and redundancy breaks after online change ^{CODESYS Forge talk (Post)}
Hello, I am currently testing redundancy using two UC20-M4000 controllers with CODESYS Control SL. The basic redundancy functionality (Active/Passive switching and failover) works, but I am experiencing problems when updating the application. Environment Controller: Weidmüller UC20-M4000 OS: u-OS Runtime: CODESYS Control SL 4.12.1.0-1 Redundancy link: dedicated Ethernet connection between the two controllers Time synchronization: NTP configured, time difference between controllers is about 1–2 seconds Current behavior Application synchronization When I download a modified application to PLC1 (Active controller), the application is not automatically copied to PLC2 (Passive controller). However, when I perform a path swap, the application download to PLC2 starts automatically. My expectation was that the Passive controller would automatically receive the updated application after downloading to the Active controller. Online change When performing an online change, redundancy is lost and the controllers switch to Standalone mode. Typical log messages include: RedundancySynchronize called Redundancy failover itself works correctly. The application boot project exists on both controllers (Application.app and Application.crc). Network interfaces are up and correctly configured. Question Is this behavior expected when updating the application in a redundant UC20-M4000 setup? Should the Passive PLC automatically receive the updated application, or is manual synchronization required? Any advice or recommended configuration for stable redundancy during online change and application download would be greatly appreciated. Thank you.
Last updated: 2026-03-16

Post by bdschnapp on OPC-UA ApplicationUri / ProductUri ^{CODESYS Forge talk (Post)}
Were you able to figure out if it is possible to change the Application/Product URI of your server? I am having the same problem.
Last updated: 2026-03-16

Post by bdschnapp on OPC-UA ApplicationUri / ProductUri ^{CODESYS Forge talk (Post)}
From Codesys support: The format of the URN is always the same. It's always urn:<vendor>:<product>:OPCUA:Server. What I think you can influence the vendor and product (DeviceName) through settings in the runtime cfg file:</product></vendor> [SysTarget] VendorNameUnicode="T\00E\00S\00T\00" DeviceNameUnicode="t\00e\00s\00t\00" Note that these are 16-bit strings, thus the ASCII padded with nulls
Last updated: 2026-03-17

OPC-UA ApplicationUri / ProductUri ^{CODESYS Forge talk (Thread)}
OPC-UA ApplicationUri / ProductUri
Last updated: 2026-03-17

Transparent wireless serial bridge for Modbus RTU – experience with LoRa/WiFi RS-485 link to CODESYS runtime ^{CODESYS Forge talk (Thread)}
Transparent wireless serial bridge for Modbus RTU – experience with LoRa/WiFi RS-485 link to CODESYS runtime
Last updated: 2026-03-18

Post by dafalin-codesys on Transparent wireless serial bridge for Modbus RTU – experience with LoRa/WiFi RS-485 link to CODESYS runtime ^{CODESYS Forge talk (Post)}
Last updated: 2026-03-18

EThercat Dynamic configuration ^{CODESYS Forge talk (Thread)}
EThercat Dynamic configuration
Last updated: 2026-03-18

WebClient result empty ^{CODESYS Forge talk (Thread)}
WebClient result empty
Last updated: 2026-03-20

Post by hannibal on Codesys Trend - setting Y axis minimum and maximum as variables - error ^{CODESYS Forge talk (Post)}
Hi, It was my fault. I was using a REAL variable instead of INTEGER. Sorry for posting this.
Last updated: 2026-03-22

Error IPR Buffer too small ^{CODESYS Forge talk (Thread)}
Error IPR Buffer too small
Last updated: 2026-03-23

Wann kann Git Rebase ^{CODESYS Forge talk (Thread)}
Wann kann Git Rebase
Last updated: 2026-03-23

Post by mae-rex on Wann kann Git Rebase ^{CODESYS Forge talk (Post)}
Hallo, ab wann ist das notwendige Feature einen Branch zu rebasen verfügbar? Gruß MAE
Last updated: 2026-03-23

Alarm Table Issues ^{CODESYS Forge talk (Thread)}
Alarm Table Issues
Last updated: 2026-03-23

AI + Programming ^{CODESYS Forge talk (Thread)}
AI + Programming
Last updated: 2026-03-23

Post by vietnam-coder on Ethernet/IP EDS file ^{CODESYS Forge talk (Post)}
excuse me , can you help me to raise up to 255 input and output please ,
Last updated: 2026-03-24

Ethernet/IP EDS file ^{CODESYS Forge talk (Thread)}
Ethernet/IP EDS file
Last updated: 2026-03-24

WebVisu Activity Tracking (no user logged in) ^{CODESYS Forge talk (Thread)}
WebVisu Activity Tracking (no user logged in)
Last updated: 2026-03-24

Unresolved reference when trying to upload to Codesys Runtime V3 ^{CODESYS Forge talk (Thread)}
Unresolved reference when trying to upload to Codesys Runtime V3
Last updated: 2026-03-25

Sort by relevance or date