Collapsing VAR in online mode ^{CODESYS Forge talk (Thread)}
Collapsing VAR in online mode
Last updated: 2018-04-20

Audio / Sprachausgabe über VAR oder UDP ? ^{CODESYS Forge talk (Thread)}
Audio / Sprachausgabe über VAR oder UDP ?
Last updated: 2009-11-24

Usage of VAR RETAIN PERSISTENT ^{CODESYS Forge talk (Thread)}
Usage of VAR RETAIN PERSISTENT
Last updated: 2021-02-02

Table Control on an array using a constant for its size. ^{CODESYS Forge talk (Thread)}
Table Control on an array using a constant for its size.
Last updated: 2016-01-08

Cannot pass array of constant size to a function as a reference ^{CODESYS Forge talk (Thread)}
Cannot pass array of constant size to a function as a reference
Last updated: 2024-01-09

How to have a persistent var on raspberry ? ^{CODESYS Forge talk (Thread)}
How to have a persistent var on raspberry ?
Last updated: 2018-01-03

Var declaration AT %MW...voiding memory overlapping ^{CODESYS Forge talk (Thread)}
Var declaration AT %MW...voiding memory overlapping
Last updated: 2023-06-30

VAR PERSISTENT RETAIN and how to shud down RPI ^{CODESYS Forge talk (Thread)}
VAR PERSISTENT RETAIN and how to shud down RPI
Last updated: 2017-08-08

Accessing a array instance variable is declared in VAR ^{CODESYS Forge talk (Thread)}
Accessing a array instance variable is declared in VAR
Last updated: 2015-10-10

PFC100 SL symbol configuration, var access problem ^{CODESYS Forge talk (Thread)}
PFC100 SL symbol configuration, var access problem
Last updated: 2023-03-08

Taster-Var setzt sich nicht zurück bei weiterem Touch-Input ^{CODESYS Forge talk (Thread)}
Taster-Var setzt sich nicht zurück bei weiterem Touch-Input
Last updated: 2012-03-23

How to find the var memory address table after compile ^{CODESYS Forge talk (Thread)}
How to find the var memory address table after compile
Last updated: 2015-11-30

Warnung 2501: Eine Callbackfunktion darf keine lokalen Var.. ^{CODESYS Forge talk (Thread)}
Warnung 2501: Eine Callbackfunktion darf keine lokalen Var..
Last updated: 2013-03-03

Post by agilename on J1939 manager DM1 message reading ^{CODESYS Forge talk (Post)}
https://content.helpme-codesys.com/en/CODESYS%20CANbus/_can_f_j1939_diagnosis_application.html you need this : VAR J1939_ECU:j1939.J1939RemoteECUDiag; DM1_ :j1939.DM1_Read; DTCliste : J1939.idtchandlerList; DTCWriter : j1939.DTCBufferWriter; arDTC:ARRAY[0..MaxDTC]OF j1939.DTC; END_VAR VAR CONSTANT MaxDTC:UDINT :=100; END_VAR DM1_( xEnable:=TRUE, xDone=> , xBusy=> , xError=> , itfSourceECU:= J1939_ECU, //My CAN J1939 ECU itfDTCHandlerList=> DTCListe , udiDTCCount=> , MalfunctionIndicatorLamp=> , RedStopLamp=> , AmberWarningLamp=> , ProtectLamp=> , xReceived=> , eError=> ); DTCWriter( xEnable:= TRUE, itfDTCHandlerList:=DM1_, eError=> , pDTCBuffer:=ADR(arDTC) , udiDTCBufferCount:=MaxDTC , udiDTCReceiveCount=> , udiDTCLostCount=> , xReceived=> );
Last updated: 2024-09-05

Post by fleaplc on FILE_OPERATION_DENIED ^{CODESYS Forge talk (Post)}
/var/opt/codesys/PlcLogic not work here, again FILE_OPERATION_DENIED. May I simply moved my files in /var/opt/codesys/PlcLogic or need some particular settings?
Last updated: 2023-09-30

Can't get the IEC var address correcttly when using the function "IecVarAccGetAddress 2" ^{CODESYS Forge talk (Thread)}
Can't get the IEC var address correcttly when using the function "IecVarAccGetAddress 2"
Last updated: 2018-12-25

Execute View Model Function block that is declared in the visualation interface as a VAR? ^{CODESYS Forge talk (Thread)}
Execute View Model Function block that is declared in the visualation interface as a VAR?
Last updated: 2022-07-15

PFC200 unresponsive with loads of messages in /var/log/wago/wagolog.log ^{CODESYS Forge talk (Thread)}
PFC200 unresponsive with loads of messages in /var/log/wago/wagolog.log
Last updated: 2022-04-14

Post by patch914 on Constant error in logs "SysEthernetGetPortConfigAndStatus: Adapter Not Found" ^{CODESYS Forge talk (Post)}
Did you find a solution for this? I am seeing the same errors.
Last updated: 2024-02-05

Post by timvh on Device diagnosis ( EtherCAT IO card ) ^{CODESYS Forge talk (Post)}
You can get the state by just using the name of your node (same name as in device tree): VAR etcState: IoDrvEthercatDriverLib.ETC_SLAVE_STATE; END_VAR etcState := EJ1100.wState; Alternatively, you can iterate through the device tree to get the status of all (Ethercat) nodes. See here an example (no guarantee it works, just give as suggestion): PROGRAM P_IO_State VAR CONSTANT uiMAX_NR_OF_TERMINALS : UINT := 100; END_VAR VAR // general device diagnosis // can only be used when the Device - PLC Settings - Advanced settings - enable diagnosis for devices is enabled // this will add the DED library coupler: DED.INode; terminal: DED.INode; aDeviceState: ARRAY[0..uiMAX_NR_OF_TERMINALS - 1] OF DED.DEVICE_STATE; uiTerminalCount : UINT; uiIndex : UINT; // for each terminal check if it implements device diagnostics xQueryResult: BOOL; itfDevice : DED.IDevice2; xDiagAvailable: BOOL; eError: DED.ERROR; xEverythingOK: BOOL; END_VAR uiTerminalCount := 0; // start at the top of the device tree with the first EtherCAT coupler coupler := EtherCAT_Master.FirstChildNode; WHILE coupler <> 0 DO // for each coupler that is found start at the first terminal terminal := coupler.FirstChildNode; WHILE terminal <> 0 AND uiTerminalCount < uiMAX_NR_OF_TERMINALS - 1 DO // for each terminal that is found get the status through the device diagnosis interface xQueryResult := __QUERYINTERFACE(terminal, itfDevice); IF xQueryResult THEN aDeviceState[uiTerminalCount] := itfDevice.GetDeviceState(xDiagnosisInfoAvailable => xDiagAvailable, eError => eError); uiTerminalCount := uiTerminalCount + 1; END_IF terminal := terminal.NextSiblingNode; END_WHILE coupler := coupler.NextSiblingNode; END_WHILE uiIndex := 0; xEverythingOK := TRUE; WHILE uiIndex < uiTerminalCount DO IF aDeviceState[uiIndex] <> DED.DEVICE_STATE.RUNNING THEN xEverythingOK := FALSE; EXIT; END_IF uiIndex := uiIndex + 1; END_WHILE
Last updated: 2025-02-06

Post by eschwellinger on FILE_OPERATION_DENIED ^{CODESYS Forge talk (Post)}
due security reason files could only be accessed in /var/opt/codesys/PlcLogic directory
Last updated: 2023-09-25

Post by eschwellinger on Loosing connection to emulation running on Linux ^{CODESYS Forge talk (Post)}
check the plc log /var/opt/codesys/codesyscontrol.log
Last updated: 2024-09-19

Post by eschwellinger on codesyscontrol.log exzessive Größe ^{CODESYS Forge talk (Post)}
/var/opt/codesys/codesyscontrol.log auf dem PI.
Last updated: 2025-03-18

Post by struccc on Release SP20 - Changes in behaviour? ^{CODESYS Forge talk (Post)}
Dear all, I've just started to migrate some of my ancient projects to SP20. There is one strange error (?) I have noticed so far. In a method call, depending on the circumstances I would like to return reference to an object, or an invalid reference: METHOD Add_EVT_OUT : REFERENCE TO FB_MSG VAR END_VAR IF __ISVALIDREF(refMSG_Entry) THEN Add_EVT_OUT REF= MANAGER.AddMsg_EVT_OUT( refMSG_Entry, _Get_EVT_Message(MSG_EVENT.OUT), _Get_EVT_AddCode(MSG_EVENT.OUT) )^; ELSE Add_EVT_OUT := 0; END_IF So far setting a reference variable to 0, did this. But now, the expression Add_EVT_OUT := 0; gives an error: [ERROR] DB_WTP_370: Add_EVT_ACK MSG_TRIGGER_EXT: C0032: Cannot convert type 'BIT' to type 'REFERENCE TO FB_MSG' Naturally... I can write: Add_EVT_OUT := DWORD#0; But is this the correct way? Is there any constant I could use instead, like "NULL"? Or this is totally wrong and to be avoided?
Last updated: 2024-03-24

Post by enricoghisla on Functional block ^{CODESYS Forge talk (Post)}
Good morning, i have a problem with an FB, i create VAR inside the block but outside i can't reach them, i can reach only IN/OUT/IN-OUT VAR, do you know which could be the problem? Regard
Last updated: 2024-04-16

Sort by relevance or date