Post by snhatton on Trace commands via Test Manager ^{CODESYS Forge talk (Post)}
One option could be to use a trigger variable to execute your trace and then toggle that variable from a step within a test case.
Last updated: 2023-12-08

Post by eschwellinger on Codesys Control Raspberry PI 4.10.0 - missing 'Update Raspberry PI' option ^{CODESYS Forge talk (Post)}
check if the RaspberryPI Package is installed (CODESYS Installer) If this is the case dd the menu command by 'tools->customize'again
Last updated: 2024-01-09

Post by nano on Library for arrays ^{CODESYS Forge talk (Post)}
habe a look at __new and __delete operators. have in mind that in this case u have a look at memory see https://help.codesys.com/api-content/2/codesys/3.5.15.0/en/_cds_operator_new/
Last updated: 2024-01-14

Post by paro on Multiple WebVisu ^{CODESYS Forge talk (Post)}
Hi, they should be independent when "Use CurrentVisu variable" is unchecked in the visu manager.. maybe you can give us more infos when its not the case.
Last updated: 2024-01-30

Post by ruben on DataSource not working ^{CODESYS Forge talk (Post)}
I had the same error. It took me a LONG way to figure it out, but in my case the problem was that I used LDATE_AND_TIME. It seems to be not supported, at least not in the Codesys version I used (3.5.16)
Last updated: 2024-02-01

Post by macros8 on Visualization using methods and cyclic ST-calls ^{CODESYS Forge talk (Post)}
Have you found the way how to call any function in case the visu is opened? Like on event when the screen is opened to initialize some variables etc.? I can´t... :/
Last updated: 2024-03-01

Post by ph0010421 on Sending Sequential Modbus TCP Packets ^{CODESYS Forge talk (Post)}
Hello You'll need to write a proper sequence to send, then wait for confirmation, and then move on to the next step. Use the CASE statement in ST. It's perfect for creating a sequence.
Last updated: 2024-03-08

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dagsupport on CAA SerialCOM - hCom Reset max value 1023 ^{CODESYS Forge talk (Post)}
Hi TimH Thanks for the information, I thought that was the case so have stepped through the code and found an error that wasn't closing the port, therefore hCom was increasing. Thanks
Last updated: 2024-03-28

Post by dgdamt on Beaglebone Black OPC-UA Server ^{CODESYS Forge talk (Post)}
Hello, In my case all was ok on the BeagleBone side (OPC server) but wrong on the client side (was OK with UA Expert who manage properly its own certificates. I finnaly removed all security settings
Last updated: 2024-04-16

Post by eschwellinger on search runtime 4.9.0.0 for pi 3 ^{CODESYS Forge talk (Post)}
sorry I missed to say how to do this just update the runtime. (extract latest debian package out of the CODESYS package) but 8n this case an update all to the latest version including CODESYS is probably the easiest option now.
Last updated: 2025-10-26

Post by gseidel on SMC_FB_WASNT_CALLED_DURING_MOTION when enable MC_MoveRelative ^{CODESYS Forge talk (Post)}
Hi ducng, please make sure to call all Motion-FBs in the EtherCAT task. In your case, the PLC_PRG should be below the EtherCAT task, not the MainTask. Best regards, Georg
Last updated: 2025-11-03

Post by eschwellinger on Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Post)}
.. try to use this projectarchive for the Stepper. In case you search for SoftMotion Examples: "c:\Program Files\CODESYS 3.5.21.X\CODESYS\CODESYS SoftMotion\Examples\Tutorial\"
Last updated: 2025-11-11

Post by manuknecht on Specify Input Configuration "OnDialogClosed" Action to only react to certain Dialogs ^{CODESYS Forge talk (Post)}
Thanks for your responses. The close listener sounds like an interesting approach, will have to see what I can do with it. I actually solved it as suggested by sturmghost by setting an enum variable to a certain state as soon as I open a dialog. This way I always know which dialog was opened last.
Last updated: 2023-10-02

Post by jeffersonhui on SP20 Visualization Element Dynamic Colors ^{CODESYS Forge talk (Post)}
I am using Codesys SP20 patch 5 and in a visualization element, the "Color variables" section does not have a section to set up dynamic color values linked to variables. In a previous version (SP18), I get the option to add variables for Normal & Alarm state colors. Does anyone know how to get the dynamic color variables to work?
Last updated: 2025-02-19

Post by jw97ke on Example_PackML.project benötigt ^{CODESYS Forge talk (Post)}
Hallo gabrielmorte, bei der Installation von dem CODESYS OMAC PackML State Machine Package aus dem CODESYS Store, wird eine Projektdatei in ein benutzerdefiniertes lokales Verzeichnis gelegt. Außerdem werden 2 zusätzliche PDF Dateien abgelegt, welche das Projekt beschreiben, so wie das Projekt auch in der Online Hilfe beschrieben wird. https://content.helpme-codesys.com/en/CODESYS%20Examples/_ex_cds_omac_state_machine.html Viele Grüße
Last updated: 2024-04-23

Post by wildcard on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, does anyone has a solution for this issue. I've the same problem. I've implemented a very simple client based on the Modbus Examples and connected the soft PLC to a Modbus Simulator. PROGRAM ModbusClient VAR initDone : BOOL := FALSE; errorID : ModbusFB.Error; client : ModbusFB.ClientTCP; timeout : UDINT := 500000; replyTimeout : UDINT := 200000; aUINT : ARRAY [0..8] OF UINT; clientRequestReadHoldingRegisters : ModbusFB.ClientRequestReadHoldingRegisters; clientRequestsCnt : UINT := 0; clientRequestsProcessCnt : UINT := 0; ipAddress : ARRAY[0..3] OF BYTE := [10,54,0,72]; END_VAR IF NOT initDone THEN initDone := TRUE; client(aIPaddr:=ipAddress, udiLogOptions:=ModbusFB.LoggingOptions.All); client(xConnect:=TRUE, ); clientRequestReadHoldingRegisters(rClient:=client, udiTimeOut:=timeout, uiUnitId:=1, uiStartItem:=0, uiQuantity:=4, pData:=ADR(aUINT[0]), udiReplyTimeout:=replyTimeout); clientRequestReadHoldingRegisters.xExecute := TRUE; clientRequestsCnt := 0; END_IF clientRequestReadHoldingRegisters(rClient:=client, udiTimeOut:=timeout, uiUnitId:=1, uiStartItem:=0, uiQuantity:=4, pData:=ADR(aUINT[0]), udiReplyTimeout:=replyTimeout, xExecute := TRUE); IF clientRequestReadHoldingRegisters.xError THEN clientRequestsCnt := clientRequestsCnt +1 ; errorID := clientRequestReadHoldingRegisters.eErrorID; END_IF clientRequestReadHoldingRegisters(rClient:=client, udiTimeOut:=timeout, uiUnitId:=1, uiStartItem:=0, uiQuantity:=4, pData:=ADR(aUINT[0]), udiReplyTimeout:=replyTimeout, xExecute := NOT clientRequestReadHoldingRegisters.xExecute); When the system is running I do get the following on the logs: 2024-05-13T10:18:07.443Z: Cmp=MODBUS lib, Class=1, Error=0, Info=0, pszInfo= Client.RequestProcessed ClientRequest,16#0164ADC561A0 unitId=1 fc=ReadHoldingRegisters id=2070 state=Error 2024-05-13T10:18:07.443Z: Cmp=MODBUS lib, Class=1, Error=0, Info=0, pszInfo= ClientRequest,16#0164ADC561A0 unitId=1 fc=ReadHoldingRegisters id=2070 change state Error -> None timestamp=63843421226 2024-05-13T10:18:08.444Z: Cmp=MODBUS lib, Class=1, Error=0, Info=0, pszInfo= ClientRequest,16#0164ADC561A0 unitId=1 fc=ReadHoldingRegisters id=2071 change state None -> Init timestamp=63844421420 2024-05-13T10:18:09.444Z: Cmp=MODBUS lib, Class=1, Error=0, Info=0, pszInfo= ClientRequest,16#0164ADC561A0 unitId=1 fc=ReadHoldingRegisters id=2071 change state Init -> Error timestamp=63845421675 But the errorID is jumping between OK and RequestNotProcessed. Any help is very appreciated which gives me a hint what I'm doing wrong. Thanks
Last updated: 2024-05-13

Post by bruceae on Ethernet/IP Scan ^{CODESYS Forge talk (Post)}
Hello, I have a robot configured as a Generic Ethernet Module under Ethernet/IP Scanner. I can not see the change of state of the outputs coming from the robot on the codesys side in real-time. (The robot has it's own internal program that would changes the values of remote outputs 0-3 off and on). Also when I send data down to the inputs of the robot it doesn't transfer over as expected. As an example I'll send to the robot's input bit 0 a value of 1. It doesn't see that value change. However, when I write that input bit 0 back to a value of 0, the robot changes state and shows a value of 1. And if I change the state of a different bit, the other bits update properly, except for the bit that I changed. Any advice would be greatly appreciated, and if anything else is needed let me know.
Last updated: 2024-09-10

Post by lsislsis on SIGABRT Error ^{CODESYS Forge talk (Post)}
Please help us. Why we take this errors. We try different versions like 4.12.0 and 4.13.0 with same results. ;*********;<loggername>codesyscontrol.log</loggername>;<logoptions>; <enable>1</enable>; <type>normal</type>; <timestamp>rtc high resolution</timestamp>; <deactivatable>0</deactivatable>; <dump>always</dump>; <filter>0x0000000f<filter>; <maxentries>100000</maxentries>; <maxfiles>1</maxfiles>; <maxfilesize>1000000</maxfilesize>;</filter></filter></logoptions>;<entries>;Timestamp, CmpId, ClassId, ErrorId, InfoId, InfoText;ClassId: LOG_INFO =1;ClassId: LOG_WARNING =2;ClassId: LOG_ERROR =4;ClassId: LOG_EXCEPTION =8;ClassId: LOG_DEBUG =16;ClassId: LOG_PRINTF =32;ClassId: LOG_COM =64;</entries>;*********2024-11-05T08:23:59.728Z, 0x0000100c, 1, 0, 0, VisuFctCheckForUnusedClients: Removing Client with IEC-ID: 1 Time delta: T#33s1ms Locks: Paintbuffer: TRUE 2024-11-05T08:23:59.728Z, 0x0000100c, 1, 0, 0, VisuFctCheckForUnusedClients: Successfully Removed Client at Address: 547195449944, IEC-ID was: 1, EXT-ID: 431000373 2024-11-05T08:28:57.913Z, 0x0000100c, 1, 0, 0, Visu_PRG: Creating Client for Extern-ID: 347055752 2024-11-05T08:28:57.926Z, 0x0000100c, 1, 0, 0, Visu_PRG: Creating Client successful for Extern-ID: 347055752 Returned IEC-ID: 1 2024-11-05T08:30:51.103Z, 0x0000100c, 1, 0, 0, Visu_PRG: Successfully Removed Client with IEC-ID: 1, Extern-ID: 347055752 2024-11-05T08:37:36.517Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state* We recommend a reboot of the controller now! 2024-11-05T08:37:36.517Z, 0x00000111, 8, 260, 3, #### Exception: HANDLED EXCPT <excpt>NonContinuable</excpt> in CH_COMM_CYCLE 2024-11-05T08:47:42.117Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T08:47:42.117Z, 0x00000111, 8, 260, 3, #### Exception: HANDLED EXCPT <excpt>NonContinuable</excpt> in CH_COMM_CYCLE 2024-11-05T09:14:41.316Z, 0x00000071, 1, 0, 13, Webserver stopped 2024-11-05T09:14:44.485Z, 0x0000013d, 1, 0, 4, Number of licensed cores for IEC-tasks: 1 from 4 2024-11-05T09:14:44.487Z, 0x0000013d, 1, 0, 4, Number of licensed cores for IEC-tasks: 4 from 4 2024-11-05T09:14:44.540Z, 0x00000002, 1, 0, 2, Application [<app>Application</app>] loaded via [Download] 2024-11-05T09:14:55.894Z, 0x00001012, 1, 0, 0, Opened alarm storage file, version: 6 2024-11-05T09:14:55.951Z, 0x0000100c, 1, 0, 0, Visuinitialization starting. 2024-11-05T09:14:55.983Z, 0x0000100c, 1, 0, 0, Visuinitialization done. 2024-11-05T09:14:55.995Z, 0x00000071, 1, 0, 12, Webserver started 2024-11-05T09:15:01.753Z, 0x0000100c, 1, 0, 0, Visu_PRG: Creating Client for Extern-ID: 2279884529 2024-11-05T09:15:01.753Z, 0x0000100c, 1, 0, 0, Visu_PRG: Creating Client successful for Extern-ID: 2279884529 Returned IEC-ID: 0 2024-11-05T09:34:44.667Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T09:34:44.667Z, 0x00000111, 8, 260, 3, #### Exception: More than 2 exceptions in CH_COMM_CYCLE: Stop logging 2024-11-05T10:13:26.867Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T10:15:21.966Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T10:19:12.167Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T10:26:02.566Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T10:31:42.866Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T11:01:54.468Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T11:09:29.868Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! 2024-11-05T11:14:44.540Z, 0x0000100d, 1, 0, 0, Demo mode expired. 2024-11-05T11:27:20.868Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state We recommend a reboot of the controller now! * Regards
Last updated: 2024-11-05

Sort by relevance or date