Post by edvard-munch on How I can get "Done flag" for "Modbus Slave Channel"? ^{CODESYS Forge talk (Post)}
This is from 10 years ago, I know. But I have been using (SLAVE_DEVICE.iChannelIndex = CHANNEL_NUMBER) AND (SLAVE_DEVICE.xDone) I suppose that it shows xDone for the channel that shows up in the iChannelIndex at the same cycle? It seems to be working properly for two devices that I have been using it before But now I have another device and using two write channels, for one register each. One channel works properly and returns DONE flag When another channel is triggered, I see that it shows up in iChannelIndex, but flag DONE not received, but no Error for the channel. Also, when i check the register in the device it's evident that data has been transferred. Is this could happen sometimes with CODESYS, so DONE flag not received? Or this is a problem with a given device? With this certain register
Last updated: 2024-12-19

Post by wpawago on Message view - Column "Action" ^{CODESYS Forge talk (Post)}
Hello everyone, I am with Codesys SP21 Patch5, there is an "Action" column in the Messages view, located between "Description" and "Project". Does anyone know how this column is supposed to work? I could not find any information about it in the CODESYS documentation: https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_cmd_messages.html I tried using it with Static Analysis Light, for example with the unused variables check, but the Action field remains empty. I initially thought it might provide a quick fix, such as automatically deleting the unused variable, but that does not seem to be the case. I am also developing some IronPython scripts and was wondering whether it is possible to populate this column with a custom action, allowing users to trigger a predefined command directly from the Messages view. Has anyone worked with this feature before or knows if it is exposed through the scripting API?
Last updated: 2026-08-26

Post by lukasz on Unresolved reference when trying to upload to Codesys Runtime V3 ^{CODESYS Forge talk (Post)}
Hello! I'm working with Codesys SP21 Patch 4. The project builds without any errors. When trying to upload my project to Codesys Runtime V3 x64 I get a lot of Unresolved Reference errors, all with FU- at the start and then -CLOSELAYER2, -GETBUSINFO, -GETFRAME etc. I also get a error pop-up that I should 'update device' in the project but it's not specified to which version or anything useful really.There's also not much to choose from. When I check Runtime version in the systray I get 3.5.21.40 and it's the same as I have set up in the project as the device. All information I get is that it should be clear from the errors but no useful information is provided in the errors. Do I need to install some library? I checked other posts and for different reference error and this was the answer. Thanks in advance!
Last updated: 2026-03-25

Post by lzml on HTML5 visualization controls disabled on CODESYS Control for Linux SL - overlay not supported? ^{CODESYS Forge talk (Post)}
Hello, I'm developing a custom HTML5 visualization control (via the HTML5 Control Editor / Tools > Visualization Element Repository) and I'm running into what looks like a target-device limitation when trying to deploy it to CODESYS Control for Linux SL. I'd like to understand whether this is a known/expected limitation or something in my setup. Environment - CODESYS Development System: V3.5.22.0 - Target runtime: CODESYS Control for Linux SL, package version 4.15.0.0 (installed together with CODESYS Edge Gateway for Linux 4.15.0.0) - Visu system libraries (VisuElems, VisuElemsAlarm, VisuInputs, VisuNativeControl, etc.): version 4.7.0.0 - Host OS: Debian RT (minimal/base installation) - We only use WebVisu, not TargetVisu. What I did 1. Built a custom HTML5 control following the official HTML5-API-Examples pattern (.html5control.xml manifest + ElementWrapper.js + CSS), installed it successfully via the HTML5 Control Editor ("Save and Install") into the Visualization Element Repository. 2. In the Visualization Manager, enabled "Support client animations and overlay of native elements" (documented as required for HTML5 controls to work at all). 3. With the project's Device set to CODESYS Control for Linux SL, compiling/downloading fails with: "Overlay is not supported for your target visualization device." (Visualization Manager) Build stops with 1 error, download not possible. Isolating the cause - The Visualization Element Repository confirms the control is correctly installed. - With the project Device set to a Windows-based device, the HTML5 control appears and is enabled in the Toolbox as expected. - With the project Device set to CODESYS Control for Linux SL, the HTML5 control is disabled/missing from the Toolbox entirely, even though it's installed in the repository. This points to the Linux SL device description simply not declaring overlay/HTML5 support, rather than a missing package or Debian-side dependency (WebVisu itself already works fine for standard/native visualization elements on this same target). Questions 1. Does CODESYS Control for Linux SL currently support WebVisu overlay (and therefore custom HTML5 controls)? I found documentation stating overlay support for target visualizations (Windows and Linux) was added starting with CODESYS Development System V3.5.17.0, but that seems to refer to TargetVisu, and our case is WebVisu-only on a Linux runtime. 2. If not currently supported, is this on a roadmap, or is there a different Linux runtime package/edition that does support WebVisu overlay for HTML5 controls? 3. Is there any Linux-side configuration or package needed to enable this (given the check appears to happen against a static device capability declaration rather than a live server check), or is this purely a matter of the device description bundled with the current Control for Linux SL package? Thanks in advance for any pointers.
Last updated: 2026-08-05

Post by bertus on Can't get SMC_SmoothPath to work ^{CODESYS Forge talk (Post)}
Hello all, I am trying to run a XY trajectory from a static G-Code file. Everything works except the smoothing/blending of the corners. My setup: Codesys v3.5sp18 Raspberry Pi 4 CODESYS Control for Raspberry Pi SL, using demo license. Zero axes (only using the interpolator). The order of processing for my decoding is: SMC_NCDecoder (ok) SMC_SmoothMerge (ok) SMC_SmoothPath (not ok) SMC_LimitDynamics SMC_CheckVelocities I created following instances and buffers: fbNCDecoder: SMC_NCDecoder; fbSmoothMerge: SMC_SmoothMerge; fbSmoothPath: SMC_SmoothPath; fbLimitDynamics: SMC_LimitDynamics; fbCheckVelocities: SMC_CheckVelocities; aNCDecoderBuffer: ARRAY[0..49] OF SMC_GeoInfo; // buffer stage 1 (fbNCDecoder) aSmoothMergeBuffer: ARRAY[0..19] OF SMC_GeoInfo; // buffer stage 2 (fbSmoothMerge) aSmoothPathBuffer: ARRAY[0..99] OF SMC_GeoInfo; // buffer stage 3 (fbSmoothPath) aLimitDynamicsBuffer: ARRAY[0..39] OF SMC_GeoInfo; // buffer stage 4 (fbLimitDynamics) My original G-Code file has a lot of short G1 elements but this example, I reduced it to a simple square: N000 G51 D10 N010 G38 O1 N020 G00 X0 Y0 F50 E1000 E-1000 N030 G01 X0 Y-37.5 N040 G01 X-75 Y-37.5 N050 G01 X-75 Y37.5 N060 G01 X0 Y37.5 N070 G01 X0 Y0 N080 G50 N090 G39 O1 In the Codesys CNC settings, I have these instances activated: SMC_SmoothMerge SMC_SmoothPath SMC_LimitDynamics SMC_CheckVelocities And with those settings (and the path-preprocessing button actived), the G-Code viewer shows the square with nicely blended corners (see attached picture). However, when running it on the PLC, it doesn't blend the corners at all. Below the relevant part of my code. The process is started with bDecode. // stage 1: decoding G-code fbNCDecoder( ncprog := square, bExecute:= bDecode, bAbort:= NOT bDecode, nSizeOutQueue := SIZEOF(aNCDecoderBuffer), pbyBufferOutQueue := ADR(aNCDecoderBuffer) ); // stage 2: merge short linear segments fbSmoothMerge( bExecute := bDecode, poqDataIn := fbNCDecoder.poqDataOut, nSizeOutQueue := SIZEOF(aSmoothMergeBuffer), pbyBufferOutQueue := ADR(aSmoothMergeBuffer), piMaxDifference := PI_MAX_DIFFERENCE, usiMaxDegree := 5, wFeatureFlag := 1, wAdditionalParamNumber := 0, dMinimumCurvatureRadius := D_MIN_CURVATURE_RADIUS ); // stage 3: smooth corners fbSmoothPath( bExecute := bDecode, bAbort := NOT bDecode, poqDataIn := fbSmoothMerge.poqDataOut, eMode := SMC_SMOOTHPATHMODE.SP_SPLINE5_MIN_CURVATURE, eAddAxMode := SMC_SMOOTHPATHADDAXMODE.SPAA_NONE, nSizeOutQueue := SIZEOF(aSmoothPathBuffer), pbyBufferOutQueue := ADR(aSmoothPathBuffer), dAngleTol := D_ANGLE_TOL, bSymmetricalDistances := TRUE, bImprovedSymmetricCuts := TRUE ); // stage 4: keep acc/dec and velocity within limits fbLimitDynamics( bExecute := bDecode, bAbort := NOT bDecode, poqDataIn := fbSmoothPath.poqDataOut, wAxis := 16#07, nSizeOutQueue := SIZEOF(aLimitDynamicsBuffer), pbyBufferOutQueue := ADR(aLimitDynamicsBuffer), bIncludePathSettings := TRUE, dMaxVel := 2500, dMaxAccDec := 10000 ); // stage 5: check the path speed fbCheckVelocities( bExecute := bDecode, bAbort := NOT bDecode, poqDataIn := fbLimitDynamics.poqDataOut, dAngleTol := D_ANGLE_TOL); pathQueue := fbCheckVelocities.poqDataOut; // repeat until MaxDuration ... Any idea what I'm doing wrong? Is smooth path supposed to work at all when using a demo license? Thanks.
Last updated: 2025-12-17

Post by bossjosh21 on Codesys Modbus RTU (Modbus_Slave_Com_Port Not Running) ^{CODESYS Forge talk (Post)}
Can someone help me about my problem of my Modbus_Slave_Com_Port Not Running. I am using RevPiConnect 4 and I connected my actuator to the RS485 of my RevPI.
Last updated: 2023-12-05

Post by mubeta on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Maybe the example posted it's not so clear, but this is not the problem. The execution of every motion methods is well triggered.
Last updated: 2024-07-18

OPC-UA Server, Symbol Set: Raise an error: Object reference not set to an instance of an object. ^{CODESYS Forge talk (Thread)}
OPC-UA Server, Symbol Set: Raise an error: Object reference not set to an instance of an object.
Last updated: 2024-08-08

Post by malie on Visuutils FbOpenDialog(Extended) not open Dialog from POUs ^{CODESYS Forge talk (Post)}
Hello, how can i open a dialog from POUs and not from Devices via FbOpenDialog. In an project would it work when i place it in the application, but in a library? Example attached. Thanks in advance Max Update: - append a screenshot
Last updated: 2024-08-20

Post by pietrobalint on Persistent variables are not read after initialization ^{CODESYS Forge talk (Post)}
Hi, I have Raspberry Pi 5 and I would like to use persistence manager too. But Codesys support said that Application Composer not compatibile with my runtime. Could you recommend a solution?
Last updated: 2024-09-01

Post by trycyclepower on EtherCAT drive going into fault mode require power cycle everytime ^{CODESYS Forge talk (Post)}
I have EtherCAT servo drive lost communication with PLC everytime it gets faulted, it does not not communicate until I power cycle everything again, how to solve this issue?
Last updated: 2024-09-11

Post by prakashkoladiya on CODESYS Gateway is not running ^{CODESYS Forge talk (Post)}
Suddenly CODESYS gateway has been stopped running as below picture so I’m not able to scan network PLC. I also tried to start CODESYS gateway service manually but its giving error as below. Have you faced this kind of problem before ??
Last updated: 2024-10-08

Post by reinier-geers on Ethercat not running. ^{CODESYS Forge talk (Post)}
I change a running programm but now ethercat is not running. all users are there. Why is it always problems with codesys/ Diadesigner. i see also a Crist ? Why ther is only one master
Last updated: 2024-10-16

Post by lsislsis on Alarm Table rows font size not change ^{CODESYS Forge talk (Post)}
When we try to change the font size of alarm table headers change as excpected but timestamps and messages not change and keep one small size from the begining. Is there any solution for that? Regards
Last updated: 2024-10-23

Post by pernockham on Persistence Manager: Config File not found? ^{CODESYS Forge talk (Post)}
Also. Every third (or so) attempt to login/compile is unsuccessful with the error prompt "one or more errors occurred", however there is no information available on what this error might be. If I remove the PersistenceManager-module, these problems are not present.
Last updated: 2024-11-01

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
I tested your project but with same results i am still not seeing analog values. I also included the library list, the mainprogram.
Last updated: 2024-11-08

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
your driver is not running. All libraries must be present first! Then you can try the following. Delete the ADS1115 and the I2C_maseter from the device tree. Create everything again.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
I also installed your codesys version with the codesys for raspberry pi package version 4.7.0. but with no succes, only the TCA multiplexer has a constant green turning circle, the ADS1115 still changing from running to not running.
Last updated: 2024-11-11

Sort by relevance or date