Post by timvh on JSON ^{CODESYS Forge talk (Post)}
I don't know the details of jsonArrayWriter, but the common behaviour for an xExecute input is that the FB starts on the trigger that it gets TRUE. In your case xExecute is never FALSE, so it is never triggered again to start the jsonArrayWriter. So change the condition from TRUE to a variable which you set to TRUE with the "xFirst". Then when the jsonArrayWriter is done (xDone), or has an error (xError), then set this variable to FALSE.
Last updated: 2024-05-01

Post by sajid on NMEA Serial data read in Control win v3 x64 ^{CODESYS Forge talk (Post)}
I am using the SerialCom example program from the CODESYS website to read NMEA strings in CODESYS Control Win V3 x64 through a serial-to-USB converter. However, I occasionally receive only partial data or encounter errors in the received string. A screenshot of expected NMEA string attached for reference. Could you please advise on how to ensure the full NMEA string is received consistently? Error in strRead variable is <value of="" the="" expression="" cannot="" be="" retrieved=""></value>
Last updated: 2025-10-16

Post by sajid on NMEA Serial data read in Control win v3 x64 ^{CODESYS Forge talk (Post)}
I am using the SerialCom example program from the CODESYS website to read NMEA strings in CODESYS Control Win V3 x64 through a serial-to-USB converter. However, I occasionally receive only partial data or encounter errors in the received string. A screenshot of expected NMEA string attached for reference. Could you please advise on how to ensure the full NMEA string is received consistently? Error in strRead variable is <value of="" the="" expression="" cannot="" be="" retrieved=""></value>
Last updated: 2025-10-16

Post by imdatatas on SMC_ERROR.SMC_AXIS_NOT_READY_FOR_MOTION when using Drive Virtual ^{CODESYS Forge talk (Post)}
@ducng, Another possible situation could be that normally there are 3 inputs for MC_Power. In your above images, I can't see the "bDriveStart" input activated. As Mr. @gseidel mentioned, you need to make sure MC_Power.Status output should be TRUE. Issuing any movement command without activating the axis would naturally result in an error. For MC_Power; You can set the Enable and bDriveStart inputs to TRUE and try turning the axis activation on and off using only the bRegulatorOn input. Regards, Imdat
Last updated: 2025-11-28

Post by gseidel on Scara3 kinematic robot error ^{CODESYS Forge talk (Post)}
Hi aniket-b, the maximum cycle time of the EtherCAT_Task is very high, ca. 35 ms. Could you please check if this is just the first cycle after starting the application or if it happens during motion? (You can reset the times in the task configuration by right-clicking in the "monitoring" tab.) Another thing to try: put the SoftMotion_Planning task on a different core. Best regards, Georg
Last updated: 2026-01-07

Post by nz-dave on *exception* [processorloadwatchdog] occurred in: app=[all], task=[all] ^{CODESYS Forge talk (Post)}
Can anyone shed some light on this issue im having. at random, sometimes days, sometimes weeks or months. i get this error and have to reset the plc. Im using a Weintek HMI with ethernet/ip remote io and vsd. i have tried increasing my task times and watchdogs. and when i view my PLCload in the shell its normally around 3-4%, highest ive ever seen is 7%. Nothing i do seems to help the issue. Could the HMI's Codesys CPU be getting to hot do to high ambient temp?
Last updated: 2026-02-01

Post by winki on Error in licence activation ^{CODESYS Forge talk (Post)}
Hello, Despite receiving an activation message after entering the license number, I don’t have any license installed on my gateway. I went to check in /var/opt/codesys/ and there is no License file. I searched the entire gateway for a .lic file and found no license. I’m really stuck—how can I fix this, please? When I am using the licence tools I got this picture: But nothing that have been activated. Loic,
Last updated: 2026-02-03

Post by winki on Error in licence activation ^{CODESYS Forge talk (Post)}
Hello, Despite receiving an activation message after entering the license number, I don’t have any license installed on my gateway. I went to check in /var/opt/codesys/ and there is no License file. I searched the entire gateway for a .lic file and found no license. I’m really stuck—how can I fix this, please? When I am using the licence tools I got this picture: But nothing that have been activated. Loic,
Last updated: 2026-02-03

Post by ryandmg on Web Client (HMI) Disconnects from Webvisu (Weidmuller u-OS) ^{CODESYS Forge talk (Post)}
Hey Everyone, I'm having a bit of a struggle finding settings that will reliably maintain a connection between the webvisu and a touchscreen client. Every so often the HMI disconnects and will perpetually display the red spinning arrow with the "Error Happened, Will resume automatically" text. Power cycling the HMI to force a reconnect will re-establish comms. It seems to happen during periods of inactivity if that's a clue. From what I've gathered so far this seems to have something to do with the webvisu update rate, buffer size as well as the visu task scan rate. We first tried the default settings as follows: Webvisu Update Rate: 200 ms Webvisu Buffer Size: 50,000 Visu Task Scan Rate: 100 ms Priority 31 Other Tasks for Reference: Main Task Scan Rate: 100 ms Priority 1 Alarm Manager Scan Rate: 50 ms Priority 31 Ethercat Task: 4 ms Priority 1 This would disconnect some what regularly. We then made the following changes to try and stabilize: Webvisu Update Rate: 150 ms Webvisu Buffer Size: 75,000 Visu Task Scan Rate: 75 ms Kept other tasks the same. This seems to disconnect even more frequently. Also for reference the network is very small and only consists of the PLC, a small switch and the HMI. We're also not controlling frames from outside the visu program itself. The frame changes are all done natively. Any suggestions to get this to stop disconnecting? Oh and whatever the issue is the log does not record it. Figured I would ask here before opening a ticket. Thanks in advance for your help!
Last updated: 2023-09-06

Post by sean-barton on Ambiguous namespace in library dependencies ^{CODESYS Forge talk (Post)}
I am trying to install the MQTT Client SL in an existing project I have been working on for years. After adding the library to the project, and without adding any other code, upon building I get a C0180: Ambiguous namespace 'MBM' error between the memory block manager (MBM) in the NetBaseSrv dependency of the MQTT Client SL library and the memory block manager (MBM) in the CAA CanL2 dependency of the 3S CANopen stack library. I have tried: * setting "Only allow qualified access to all identifiers." in the properties for both the parent libraries. * deleting the 3S CANopen stack library. Upon (re)building the error simply points to another conflicting library - there are many. * deleting the Library Manager and rebuilding it. * adding the memory block manager library (used in the NetBaseSrv) manually and changing its namespace to MBM3S. None of the above allow me to access the MQTT library through its namespace (MQTT). Adding the memory block manager manually removes the C0180 error, but the MQTT library is not accessible - i.e. mqttClient : MQTT.MQTTClient; highlights the mqttClient as "Identifier 'MQTT.MQTTClient' not defined". Is there anything else I can try?
Last updated: 2025-01-09

Post by imdatatas on MC_MoveAbsolute: C0138: No matching 'FB_Init' method found for instantiation of SMC_MoveAbsRelPerformerImpl [ERROR] ^{CODESYS Forge talk (Post)}
Dear @gseidel, Thank you for your reply. The exact version of Codesys and its compiler was 3.5.21.20. The compiler version was fixed and could not be changed in project settings. Since I couldn't continue due to this compilation error, I temporarily overcame this issue as follows. -- I completely uninstalled Codesys 3.5.21.20 and completely deleted the Codesys folder in the C:\ProgramData folder. -- I restarted my computer and installed Codesys 3.5.19.70. -- I updated the Codesys Installer and all its add-ons to the latest versions. -- The project that was giving me the compilation error I mentioned before is now open with Codesys 3.5.19.70, compiled it, and successfully downloaded it on the device. -- I haven't encountered the same problem anymore. I think this issue is related to SP21 and its compiler. Frankly, I'd expect a project created with an older version to compile without errors after opening it with the latest Codesys version and updating all libraries. Regards, imdatatas
Last updated: 2025-09-26

Post by tomast on Codesys and Siemens SINAMICS 20 modbus RTU "Response CRC Fail" ^{CODESYS Forge talk (Post)}
Hi everyone, I'm currently working on a project involving the control of 5 VFDs via Modbus RTU, this time using the WAGO 750-8212 CPU. So far, I've managed to make progress, but I've encountered an issue. While I can successfully read and write to all the registers I need, I consistently encounter a "Response CRC Fail" error when attempting to write the value 1151 to the STW register at address 40100. I'm able to set the frequency via register 40101 and adjust all other parameters using different registers. Setting STW to 1150 results in the drive ready boolean from the ZSW-bit being received instantly. However, the moment I attempt to send 1151 to register 40100, I immediately receive the "Response CRC Fail" error for all channels. I've also attempted to use combined control, employing Modbus for frequency control and starting from a digital input. Everything seems to function properly until I send the start command to the VFD. Interestingly, I consistently encounter the same error the moment I send the start command, regardless of whether I use register 40006 (high) or 40100 (1151). Could someone please assist me in resolving this issue?
Last updated: 2024-03-21

Post by rk-gaw on Unhandled exception and refactoring error ^{CODESYS Forge talk (Post)}
Hello everyone. I hope this is the right place to ask for help, this error is causing me a great amount of time loss and I really would like to end this nightmare. I don't know why but at times if I try to Browse -> Display Cross Reference on a variable Codesys just crashes. I'll attach the file with the complete crash report hoping someone can figure why it happend. I think that the unhandled exception comes from the PersisranceManager Module and is connected with the other big problem I'm facing: I cannot refactor in my project, if I'll try to refactor a POU name the whole POU will become "frozen", it's like its desynchronizing from the project and the project cannot find the pointer to the POU once I refactor it. And when I open the project a warning pop-up will show up with the frozen POUs name, but I cannot figure out what the warning is telling me. I'll attach every warning and error pop up the project is showing me, and thanks in advance to anyone who can figure something out.
Last updated: 2025-12-10

Post by pppn on Issue with Forward Open Connections in Ethernet/IP Protocol Stack in Codesys ^{CODESYS Forge talk (Post)}
Hello, I am facing an issue with my Ethernet-based project in Codesys. My product was functioning well until I modified the protocol stack and uploaded it to my device. Here are the details of my problem: Project Setup: I am working on an Ethernet-based project to test my product. The project was running without issues before modifying the protocol stack. Issue: After modifying the protocol stack and uploading it to my device, I am encountering an error in Codesys related to the forward open connections. Error status: connection failure, extended: connection in use or duplicate forward open. According to the Ethernet/IP protocol in codesys, there are three forward open connections that need to be established. The first two connections are opening without any issues. The third connection, which is an input-only connection, is causing problems. The error message indicates that the connection is already open. Debugging Attempts: I have extensively debugged the protocol stack and found no issues. The product works well when tested with EIP tools but not with Codesys. Exclusive owner connections are working correctly, and only the input-only connection is problematic. Wireshark Traces: Wireshark traces show that the third connection attempts to open but reports that it is already open. Steps to Reproduce: Modify the protocol stack and upload it to the device. Attempt to establish three forward open connections in Codesys. Observe the error on the third connection (input-only). Request: I would appreciate any suggestions or guidance on how to resolve this issue. If there are specific settings or configurations in Codesys that I need to check, please let me know. Additionally, if there are known issues or workarounds related to this problem, I would be grateful for the information. Attachments: Wireshark traces showing the connection attempts and errors Screenshots of the error messages in Codesys codesys version: CODESYS V3.5 SP16 Patch 3 + 64 bit
Last updated: 2024-06-25

Post by pppn on Issue with Forward Open Connections in Ethernet/IP Protocol Stack in Codesys ^{CODESYS Forge talk (Post)}
Hello, I am facing an issue with my Ethernet-based project in Codesys. My product was functioning well until I modified the protocol stack and uploaded it to my device. Here are the details of my problem: Project Setup: I am working on an Ethernet-based project to test my product. The project was running without issues before modifying the protocol stack. Issue: After modifying the protocol stack and uploading it to my device, I am encountering an error in Codesys related to the forward open connections. Error status: connection failure, extended: connection in use or duplicate forward open. According to the Ethernet/IP protocol, there are three forward open connections that need to be established. The first two connections are opening without any issues. The third connection, which is an input-only connection, is causing problems. The error message indicates that the connection is already open. Debugging Attempts: I have extensively debugged the protocol stack and found no issues. The product works well when tested with EIP tools but not with Codesys. Exclusive owner connections are working correctly, and only the input-only connection is problematic. Wireshark Traces: Wireshark traces show that the third connection attempts to open but reports that it is already open. Steps to Reproduce: Modify the protocol stack and upload it to the device. Attempt to establish three forward open connections in Codesys. Observe the error on the third connection (input-only). Request: I would appreciate any suggestions or guidance on how to resolve this issue. If there are specific settings or configurations in Codesys that I need to check, please let me know. Additionally, if there are known issues or workarounds related to this problem, I would be grateful for the information. Attachments: Wireshark traces showing the connection attempts and errors Screenshots of the error messages in Codesys codesys version: CODESYS V3.5 SP16 Patch 3 + 64 bit
Last updated: 2024-06-25

web visu on IFM ^{CODESYS Forge talk (Thread)}
web visu on IFM
Last updated: 2023-08-18

WebVisu on mobile devices ^{CODESYS Forge talk (Thread)}
WebVisu on mobile devices
Last updated: 2023-09-13

Operation on Alarm History ^{CODESYS Forge talk (Thread)}
Operation on Alarm History
Last updated: 2018-05-09

ProfiNET on WAGO PFC200 ^{CODESYS Forge talk (Thread)}
ProfiNET on WAGO PFC200
Last updated: 2017-01-24

LTIME variable on visualisation ^{CODESYS Forge talk (Thread)}
LTIME variable on visualisation
Last updated: 2014-02-20

Semaphores on Linux target ^{CODESYS Forge talk (Thread)}
Semaphores on Linux target
Last updated: 2012-09-18

Codesys 3.5.17.20 on Wine. ^{CODESYS Forge talk (Thread)}
Codesys 3.5.17.20 on Wine.
Last updated: 2022-01-18

Jitter problems on imx8 ^{CODESYS Forge talk (Thread)}
Jitter problems on imx8
Last updated: 2023-10-19

creationg on dynamic widgets ^{CODESYS Forge talk (Thread)}
creationg on dynamic widgets
Last updated: 2023-10-20

Save Recipe on Paspberry ^{CODESYS Forge talk (Thread)}
Save Recipe on Paspberry
Last updated: 2024-08-06

Sort by relevance or date