Post by eschwellinger on How to Connect / Go Online without re-downloading the project ^{CODESYS Forge talk (Post)}
Which plc type is it: Either use Automationserver to do this or save the project archives instead of projects or use the source dowload function and reopen the application from plc. So you need to chose one of them.
Last updated: 2024-04-13

Post by vtec35 on search runtime 4.9.0.0 for pi 3 ^{CODESYS Forge talk (Post)}
yes but impossible to upload runtime 4.9.0.0 now we have put an image on the sd card with 4.13.0.0, i have 27 error message to this type, and if i test some output not work, et some work ------ Processus de compilation entamé : application : Device.HiddenOnlineConfigModeApp ------- Affecter un type à un code... [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0032: Le type 'Type inconnu : 'ADR(GVL_Io_73f6cbf3_7be8_4500_8421_47e565d899a0_HPS_1.Io_73f6cbf3_7be8_4500_8421_47e565d899a0_HPS_1)'' ne peut pas être converti en type 'POINTER TO IoConfigParameter' [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0077: Type inconnu : 'GVL_Io_73f6cbf3_7be8_4500_8421_47e565d899a0_HPS_1.Io_73f6cbf3_7be8_4500_8421_47e565d899a0_HPS_1' [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0046: Identificateur 'GVL_Io_73f6cbf3_7be8_4500_8421_47e565d899a0_HPS_1' non défini [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0032: Le type 'Type inconnu : 'ADR(GVL_Io_1b6dcc3b_ae11_4288_b9a9_86f9323448d1_HPS_1.Io_1b6dcc3b_ae11_4288_b9a9_86f9323448d1_HPS_1)'' ne peut pas être converti en type 'POINTER TO IoConfigParameter' [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0077: Type inconnu : 'GVL_Io_1b6dcc3b_ae11_4288_b9a9_86f9323448d1_HPS_1.Io_1b6dcc3b_ae11_4288_b9a9_86f9323448d1_HPS_1' [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0046: Identificateur 'GVL_Io_1b6dcc3b_ae11_4288_b9a9_86f9323448d1_HPS_1' non défini [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0032: Le type 'Type inconnu : 'ADR(GVL_Io_5ae6fa5a_c197_4038_9581_03e1650806a0_HPS_4.Io_5ae6fa5a_c197_4038_9581_03e1650806a0_HPS_4)'' ne peut pas être converti en type 'POINTER TO IoConfigParameter' [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0077: Type inconnu : 'GVL_Io_5ae6fa5a_c197_4038_9581_03e1650806a0_HPS_4.Io_5ae6fa5a_c197_4038_9581_03e1650806a0_HPS_4' [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj 241025: C0046: Identificateur 'GVL_Io_5ae6fa5a_c197_4038_9581_03e1650806a0_HPS_4' non défini [ERREUR] conditionneuse_camphre-ssa-05-02-24-V3 maj
Last updated: 2025-10-26

Post by fefefede on Get the numer of day ^{CODESYS Forge talk (Post)}
Hello i tro to create a program to turn on or off the air condition in relationship temperature and numer of day. I can't get the number of day. I try this after installing SysTime library but this not work and have this error on debug ------ Build started: Application: Device.Sim.Device.Application ------- Typify code... Generate code... [ERROR] giorno_accensione_aria: PLC_PRG Device: PLC Logic: Application: C0032: Cannot convert type 'Unknown type: 'SysTimeCore(TRUE)'' to type 'TIME' [ERROR] giorno_accensione_aria: PLC_PRG Device: PLC Logic: Application: C0035: Program name, function or function block instance expected instead of 'SysTimeCore' [ERROR] giorno_accensione_aria: PLC_PRG Device: PLC Logic: Application: C0032: Cannot convert type 'Unknown type: 'DayOfWeek(CurrentTime)'' to type 'INT' [ERROR] giorno_accensione_aria: PLC_PRG Device: PLC Logic: Application: C0035: Program name, function or function block instance expected instead of 'DayOfWeek' [INFORMATION] giorno_accensione_aria: PLC_PRG Device: PLC Logic: Application: C0181: Related position Build complete -- 4 errors, 0 warnings : No download possible PROGRAM PLC_PRG VAR Temperatura: UDINT; AriaCondizionata: BOOL := FALSE; CurrentDayOfWeek: INT; //Variabile Giorno CurrentTime: TIME; GiornoDellaSettimana: INT; DayOfWeek: INT; END_VAR CurrentTime := SysTimeCore(TRUE); // Ottieni l'ora corrente CurrentDayOfWeek := DayOfWeek(CurrentTime); CASE GiornoDellaSettimana OF 1: // Azioni per Lunedì 2: // Martedì se più 10° accend altrimenti spegni IF Temperatura >= 10 THEN AriaCondizionata := TRUE; ELSE AriaCondizionata := FALSE; END_IF 3: // Mercoledì se più di 50° accendi altrimenti spegni IF Temperatura >=50 THEN AriaCondizionata := TRUE; ELSE AriaCondizionata := FALSE; END_IF 4: // Giovedì se più di 40° accendi altrimenti spegni IF Temperatura >=40 THEN AriaCondizionata := TRUE; ELSE AriaCondizionata := FALSE; END_IF 5: // Venerdì se più di 50° accendi altrimenti spegni IF Temperatura >=50 THEN AriaCondizionata := TRUE; ELSE AriaCondizionata := FALSE; END_IF 6: // Sabato se più di 25° accendi altrimenti spegni IF Temperatura >=25 THEN AriaCondizionata := TRUE; ELSE AriaCondizionata := FALSE; END_IF 7: // Domenica sempre spenta AriaCondizionata := FALSE; END_CASE
Last updated: 2023-09-14

Post by otbeka on CmpCrypto CryptoGenerateHash Not Outputting ^{CODESYS Forge talk (Post)}
Unfortunately I noticed that, and tried: * using CryptoGeteAlgorithmByID within the function call * inputting the raw byte pointer as a testByte * instantiating the _hHash handle within the function body * using a different cryptoID or the raw DINT values from the RtsCryptoID DUT ... to no avail. The pReturn value is also set to 0, which would indicate that it is OK, right? This is odd given that the function is the same within the CryptoDemo example project here, just with a newer version. Is it possible that there is something wrong with the way my bytestring is being set up? I use the following DUTs here: TYPE MESSAGE : STRING(255); END_TYPE TYPE HASH_CODE : ARRAY[0..19] OF BYTE; END_TYPE
Last updated: 2024-09-06

Post by alexgooi on Function Blocks and arrays of function blocks ^{CODESYS Forge talk (Post)}
Hi Jack, I think you have to look at a FB in a different way. A Function block (Class) can contain its own data. In other words don't define loose data in your GVL, but define a instance of a FB (Object) in your GVL: Example: Function_Block Basic_Class VAR_INPUT Open_Command: BOOL; END_VAR VAR_OUTPUT Opened: BOOL; END_VAR if Open_Command then Opened := TRUE; ELSE Opened := FALSE; END_IF Global Variables Objects: ARRAY[1..100] OF Basic_Class; //Here you ar defining you objects END_VAR In your code you can directly acces the data and couple it to the IO: GVL.Objects[1].Open_Command := %IX0.0; %QX0.0 := GVL.Objects[1].Opened; //To call the code itself use: GVL.Objects[1](); If you want to take this a step further you are also able to add methods and properties to the FB/Class end thereby creating a OOIP program
Last updated: 2024-02-15

Post by mjk97 on CFC Toggle Function ^{CODESYS Forge talk (Post)}
Last updated: 2024-05-03

Post by shabroz-gill on Data Sources Manager causing exception due to float or double type in OPC server ^{CODESYS Forge talk (Post)}
Was this ever resolved? I see the same issue with the version 3.5.19.5
Last updated: 2024-07-01

Post by lostcontrol on Remote Ethernet/ip Adapter communication with scanner running on codesys ^{CODESYS Forge talk (Post)}
is the bus running.? what type of values/IO is the adaptor providing? do you have a map of the data layout? are you actually looking at the right offset?
Last updated: 2023-12-16

Post by kevinm on Data source and safety PLC ^{CODESYS Forge talk (Post)}
I am having the same trouble. However, if I change the Login Configuration settings to 'Type: Login using the credentials determined at runtime' then the Connection information continues as 'Connection state: Connecting' and 'Error information: OK'. There is no User Management on the source PLC.
Last updated: 2024-05-16

Problem of assigning physical addresses to variables of type ARRAY OF ARRAY as MW and QW ^{CODESYS Forge talk (Thread)}
Problem of assigning physical addresses to variables of type ARRAY OF ARRAY as MW and QW
Last updated: 2025-03-31

How do I fix ";Internal Error (x86-64): Invalid type size" error? ^{CODESYS Forge talk (Thread)}
How do I fix ";Internal Error (x86-64): Invalid type size" error?
Last updated: 2025-04-16

Why is no more possible use REFERECE OF in return method type? ^{CODESYS Forge talk (Thread)}
Why is no more possible use REFERECE OF in return method type?
Last updated: 2021-12-10

addressin an array of byte containing bits of type bool ^{CODESYS Forge talk (Thread)}
addressin an array of byte containing bits of type bool
Last updated: 2018-11-14

Modify the 0x1600 access type of CAN Local Device in Codesys ^{CODESYS Forge talk (Thread)}
Modify the 0x1600 access type of CAN Local Device in Codesys
Last updated: 2018-11-23

Maximizing Struct type Variable in offline mode and adding comments to each element ^{CODESYS Forge talk (Thread)}
Maximizing Struct type Variable in offline mode and adding comments to each element
Last updated: 2021-04-28

ENI server: Object type registry not found in the database ^{CODESYS Forge talk (Thread)}
ENI server: Object type registry not found in the database
Last updated: 2010-02-19

changing the type of an existing POU from FB to PRG ^{CODESYS Forge talk (Thread)}
changing the type of an existing POU from FB to PRG
Last updated: 2012-12-14

CmpIecVarAccess to get name of a type, not of a variable (instance) ^{CODESYS Forge talk (Thread)}
CmpIecVarAccess to get name of a type, not of a variable (instance)
Last updated: 2016-06-08

How to use Jerk input and Velocity ramp type in MC_MoveAbsolute ^{CODESYS Forge talk (Thread)}
How to use Jerk input and Velocity ramp type in MC_MoveAbsolute
Last updated: 2018-07-09

Problem configuring the 750-638 Counter for Hall-type sensor ^{CODESYS Forge talk (Thread)}
Problem configuring the 750-638 Counter for Hall-type sensor
Last updated: 2012-10-29

Post by brandonje on [Error] IoDrvEtherNetIP Library with Weintek ^{CODESYS Forge talk (Post)}
I'm using weintek and Codesys V3.5 SP22 when I try to charge an ethernetIP device show me this error: ------ Build started: Application: Device.Application ------- Typify code... [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0231: Expression of type 'BOOL' expected in this place [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0077: Unknown type: '(_pPhysicalLink^._xLinkState <> CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up)' [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0077: Unknown type: 'CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up' [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0062: 'CmpSysEthernet.OperStatus' is no structured variable [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0063: 'CMPSYSETHERNET, 3.4.3.0 (3S - SMART SOFTWARE SOLUTIONS GMBH)' contains no definition for 'OperStatus' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: 'ADR(ethFrame.ethData)'' to type 'POINTER TO StructEthernetframe' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'ethFrame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: 'ethFrame.udFrameLen'' to type 'ANY' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '((driverInstance * 2) + 1)'' to type 'ANY' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0077: Unknown type: '(driverInstance * 2)' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0077: Unknown type: 'driverInstance' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0046: Identifier 'driverInstance' not defined [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0231: Expression of type 'BOOL' expected in this place [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SIZEOF(ethFrame.ethData)' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'ethFrame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0018: 'ethFrame.udFrameLen' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: 'ADR(ethFrame.ethData)'' to type 'POINTER TO BYTE' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'ethFrame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0201: Type 'SysEthernetFrame' is not equal to type 'SysEthernetFrame' of VAR_IN_OUT respectively REFERENCE 'ethFrame' [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier 'ethClose' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: 'ethClose' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: '_diAdapterNumber' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_stName' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: '_stName' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_stDescription' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: '_stDescription' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0231: Expression of type 'BOOL' expected in this place [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0077: Unknown type: '(_pPhysicalLink^._xLinkState = CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up)' [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0077: Unknown type: 'CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up' [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0062: 'CmpSysEthernet.OperStatus' is no structured variable [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0063: 'CMPSYSETHERNET, 3.4.3.0 (3S - SMART SOFTWARE SOLUTIONS GMBH)' contains no definition for 'OperStatus' [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] memory block manager, 3.5.21.30 (codesys): ObjectRetain [Disposable]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] memory block manager, 3.5.21.30 (codesys): ObjectRelease [Disposable]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [LLDP_Management]: C0201: Type 'SysEthernetFrame' is not equal to type 'SysEthernetFrame' of VAR_IN_OUT respectively REFERENCE 'frame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [LLDP_Management]: C0201: Type 'SysEthernetFrame' is not equal to type 'SysEthernetFrame' of VAR_IN_OUT respectively REFERENCE 'ethFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0032: Cannot convert type 'Unknown type: 'ADR(frame.ethData[0])'' to type 'POINTER TO BYTE' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'frame.ethData[0]' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0032: Cannot convert type 'Unknown type: 'SIZEOF(frame.ethData)'' to type 'UDINT' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'frame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0018: 'frame.udFrameLen' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Receive [UcmmReceiver]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Send [UcmmReceiver]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Enqueue [UcmmQueue]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Enqueue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Enqueue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Dequeue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Dequeue [UcmmQueue]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Dequeue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] asynchronous job manager, 5.0.0.0 (codesys): ExtendAsync [FactoryBase]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. Compile complete -- 71 errors, 0 warnings Build complete -- 71 errors, 0 warnings : No download possible
Last updated: 2026-08-20

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 otbeka on CAA File Handling: "Read only" error ^{CODESYS Forge talk (Post)}
Hi, On CODESYS V3.5.19.50 I am using the latest 3S File Access library (CAA File & CAA Types) to save and retrieve configuration data from the User Data section of an SD card, via file called config.txt. The application reads the file to memory once upon initialisation, and then the only other operation is overwriting the file with the updated configuration whenever the user changes the settings. An issue is ocurring, seemingly randomly, where the config.txt file, and all surrounding directories, cannot be written to by the unit, returning a READ_ONLY_CAA error upon file open. This sometimes does not clear even after power-cycling the PLC several times, yet checking the file permissions with ls -l shows normal read, write, and execute access. I am wondering if this is caused by the PLC itself or by an issue in my application. I have included my CAA File handler function block (SD_Card_Bin(FB).txt) and any associated types/calls below: TYPE ConfigData : STRUCT Config : ARRAY[0..256] OF STRING(64); NumberOfStrings : UDINT; END_STRUCT END_TYPE TYPE Buffer : STRUCT Data : ARRAY[0..SIZEOF(ConfigData)] OF BYTE; DataLength : UDINT; END_STRUCT END_TYPE A case within my MAIN PRG: mode.WriteConfigDataToFile: VisuElems.CURRENTVISU := 'Screen_Write'; IF xModeHasChanged THEN iErrorCount := 0; iRoute := 0; END_IF CASE iRoute OF 0: inBuffer := ConfigData_To_Buffer(GVL.UnitData); xConfigError := FALSE; xDataConfigured := FALSE; iRoute := 1; 1 : //Read Data from Card SD_Card_Bin.strFileName :=FileName; SD_Card_Bin.iFileOperation := 2; SD_Card_Bin(xExecute :=TRUE, WriteBuffer := inBuffer, xDone =>xDataConfigured, xError=>xConfigError, strErrorCodes=>strError); IF xDataConfigured THEN SD_Card_Bin(xExecute :=FALSE); IF xConfigError THEN iRoute := 32767; ELSE iRoute :=100; END_IF END_IF 100: // The end bCurMode := mode.DisplayProcessVariables; 32767: // Config error iErrorCount := iErrorCount + 1; IF iErrorCount > 2 THEN // Repeats 3 times, if no progress abandons and returns error bCurMode := mode.WriteError; ELSE iRoute := 0; // Try again END_IF END_CASE I'd like to rule out my application as the cause of this bug - help via comments or criticism would be greatly appreciated.
Last updated: 2025-03-19

Post by dclements on Feature Request: Read-Only References / Pointer-to-Const Support ^{CODESYS Forge talk (Post)}
I would like to suggest adding support for persistent read-only references or pointers in CODESYS, similar to a C++ pointer-to-const (const T*). For example, something conceptually similar to: POINTER TO CONSTANT ST_MyData or REFERENCE TO CONSTANT ST_MyData The important distinction is that the reference itself may still be passed around or reassigned, but the referenced object cannot be modified through that reference. CODESYS currently supports VAR_IN_OUT CONSTANT, which provides read-only reference semantics for parameters, but there does not appear to be an equivalent type that can be stored in a variable or returned from a method. A practical use case is a registry that owns long-lived definitions. The registry needs to retain ownership of the data while downstream systems maintain persistent references to it. Currently, the main options are: Return the struct by value, which loses reference semantics and requires a copy. Return POINTER TO ST_Definition, which allows consumers to modify registry-owned data. Convert the structure into a Function Block and expose a getter-only interface, which provides the desired encapsulation but introduces more complexity and memory overhead. A read-only reference/pointer type would allow libraries to expose persistent, zero-copy access to internally owned data while preserving encapsulation. This would be particularly useful for library APIs and object-oriented CODESYS architectures where ownership of data should remain with one component while other components are allowed to observe it. Similar requests for constant references/pointers have been discussed on CODESYS Forge previously, so this appears to be a recurring use case rather than something specific to one application.
Last updated: 2026-09-01

Post by banialuk on Modbus TCP Server ^{CODESYS Forge talk (Post)}
Hello, I have poroblem with define input in function block modbusFB.serverTCP 'dataModel', in my aplication I need starting Input Registers from 3000, and I must define this in 'data Model' but I dont now how exacly to do it. Anybody now somethin about this?
Last updated: 2024-10-19

Sort by relevance or date