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: 18 hours ago

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

Post by anonymous on Hi, I try to send and receive data using a UDP connection via SysSocket 3.5.17.0. While sending data works fine, I have problems with the receiving part. I am able to capture the received data of client side in wireshark But unable to capture it on the codesys ^{CODESYS Forge talk (Post)}
Hi, I try to send and receive data using a UDP connection via SysSocket 3.5.17.0. While sending data works fine, I have problems with the receiving part.I am able to capture the data of client side in wireshark but i am unable to capture it in the codesys. Heres the below part of code of client side. PROGRAM POU_udpclient_program VAR istep : INT := 1;//step variable for state machine xStart: BOOL;// Flag to start the UDP protocol iecSocketId: syssocket_interfaces.RTS_IEC_HANDLE;//socket handle for receiving iecCreateResult: syssocket_interfaces.RTS_IEC_RESULT; ipAddr: syssocket.SOCKADDRESS;//Socket address structure for receiving sIpAddress : STRING := '192.168.0.2'; wPort: WORD:= 12346; iecConnectResult : syssocket_interfaces.RTS_IEC_RESULT;//connect paramters sDataRec : STRING[255];//Buffer for received data xiRecBytes : __XINT;//number of bytes received iecRecResult : syssocket_interfaces.RTS_IEC_RESULT;//receive data parameters iecCloseResult : syssocket_interfaces.RTS_IEC_RESULT; END_VAR syssocket.SysSockInetAddr(sIpAddress,ADR(ipAddr.sin_addr)); ipAddr.sin_family := syssocket.SOCKET_AF_INET; ipAddr.sin_port := syssocket.SysSockHtons(wPort); CASE istep OF 1: //create socket IF xStart THEN iecSocketId:= syssocket.SysSockCreate(syssocket.SOCKET_AF_INET,syssocket.SOCKET_DGRAM,syssocket.SOCKET_IPPROTO_IP,ADR(iecCreateResult)); IF iecSocketId = syssocket_interfaces.RTS_INVALID_HANDLE THEN xStart := FALSE; istep := 1; ELSE istep := 2; END_IF END_IF 2: //connect to socket server using setoption iecConnectResult := syssocket.SysSockSetOption(iecSocketId,syssocket.SOCKET_SOL,syssocket.SOCKET_SO_REUSEADDR,ADR(ipAddr),SIZEOF(ipAddr)); istep := 3; 3: //receive data xiRecBytes := syssocket.SysSockRecvFrom(iecSocketId,ADR(sDataRec),SIZEOF(sDataRec),0,ADR(ipAddr),SIZEOF(ipAddr),ADR(iecRecResult)); istep := 4; 4: //close socket iecCloseResult:= syssocket.SysSockClose(iecSocketId); xStart := FALSE; istep := 1; END_CASE
Last updated: 2024-06-03

Post by viksym on How to get the motor scaling value from code ^{CODESYS Forge talk (Post)}
If anybody finds this in the future, I managed to do it like this: scalingValue := EncoderPulseCountPerRev / ABS(AxisName.fScaleFactor); No need to use MC_ReadParameter as I am able to read this value directly from the axis object. Using an absolute value of the fScaleFactor is there in case the axis is set as inverted, in which case it would be a negative value. I was not able to figure out how to get EncoderPulseCountPerRev programatically, but since all my servos use an encoder with pulse count per revolution of 16#800000, the final equation looks like this: scalingValue := 16#800000 / ABS(AxisName.fScaleFactor);
Last updated: 2025-08-19

Post by jmfernandes on OpenDir always in error ^{CODESYS Forge talk (Post)}
Hello just to give more feedback the error I get is "ERROR_UNKNOWN :represents raw value of 5110" in File.DirOpen. The xDone never gets true, and I never get the listing of files (csv files in this case). In the hDir i get the value of 0 for a DWord!?
Last updated: 2024-07-31

Post by dkugler on User management ^{CODESYS Forge talk (Post)}
If the PLC is equieped with a USB socket it's possible to copy the user management file via IEC code to a USB stick and restore it at the new plc. The file is located there: /PlcLogic/visu/app_visuusermgmtdb.csv I use this to reset the user management to default in case of the customer has changed passwords and lost it.
Last updated: 2024-09-04

Post by bjarne-pagaard on Unable to add alarm configuration object to project ^{CODESYS Forge talk (Post)}
I believe it should be available. It may be the case, that your device does not support the alarm configuration. Some smaller PLCs sometimes do not support it. You can try changing to a different device, like a Codesys Control Win, in your project, and see if then allows you to add the alarm configuration.
Last updated: 2024-09-27

Post by timvh on Library ENUM text representation in visualization ^{CODESYS Forge talk (Post)}
Probably the enum from the library doesn't have text support. In that case you need to add your own TextList to the application. In the rectangle you should use the property "dynamic text" to link this object to the textlist which you have created yourself and then link the text index to your enum variable.
Last updated: 2025-01-09

Post by antonz on CoDeSys v3.5: creating libraries for both 32-bit and 64-bit controllers ^{CODESYS Forge talk (Post)}
Thanks Tim. I would think it somehow is relevant when creating a compiled library, but that may very well not be the case. If I understand you correctly, then the same compiled library created from my source code would work for both 32 bit as well as 64 bit controllers.
Last updated: 2025-09-01

Post by toby on Codesys Control Raspberry PI 4.10.0 - missing 'Update Raspberry PI' option ^{CODESYS Forge talk (Post)}
Hi, Mine is the same, both using v3.5 SP17 patch 6, and v3.5 SP19 patch 5 when using anything newer than v4.8.0 the same issue as above occurs. Checked the 'Customize' window in case it was hidden/disabled in there but couldn't find it. Thanks for the help on this. Toby
Last updated: 2024-01-09

Sort by relevance or date