Post by williamjmak1 on Current Visu name without Current Visu Variable ^{CODESYS Forge talk (Post)}
Hello everyone, I was just wondering if anybody knows if there's a way to pull the string name of the current visualization without using the current visu variable. I'm working on a project where we don't want web clients to change the current visualization on the HMI of the machine. Thanks!!
Last updated: 2025-08-07

Post by mos89p on how to use UseDataExpanding() in datasource ^{CODESYS Forge talk (Post)}
Hi I need to update by software some structures in my datasource, i found this example: https://content.helpme-codesys.com/en/CODESYS%20Communication/_cds_update_data_interface.html it seems that because i use complex variable structure i need to use UseDataExpanding() instead of use data, the question is how to get an instance of IDatasourcesMgr3 i have the global variable g_Datasources is instantiated automatically
Last updated: 2024-06-18

Post by struccc on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Strangely reminds me to my struggles... Want to do something "Elegant", reusable, universal, practical... In CODESYS??? 🙃 First of all, before you get too deep into this: If you could find a way, to make a "universal" log entry object, containing the variable length data itself, you wouldn't be able to store them in an array, or access them like an array, or pass them by value as a type. (please correct me, if I'm wrong, incorrect, or not precise). Because... Basically you can't declare a type with variable memory footprint. This is a very deeply embedded characteristic of CODESYS, and all IEC 61131-3 systems, and it has many reasons behind. And yes, it is a very common trap / mistake, to forget about. So, with a log entry - I guess - it's pretty much the purpose: store data and metadata together, and then handle it in a uniform way. There are ways to handle this, really depends on what is the purpose. For example: 1. Entries with fixed length (Maybe it is not as evil as it looks for the first time. Depends on the situation, but definitely the fastest and easiest code) You can have your base object, with an internal, fixed length string or byte array variable. I would go with a string, and call it _Data.; And then you can make properties, like As_Bool, As_Int, As_Real... In the 'set' accessors, you can do like: pReal := ADR(_Data); // POINTER TO REAL As_Real := pReal^; In the 'get' accessors, evidently: pReal := ADR(_Data); // POINTER TO REAL pReal^ := AS_Real; Or, can use ANY type, if you are not obsessed with variable / property like access: 2. Fixed length, but nicer First, some disadvantage to any values: - You can only assign values with write access. No literals, constants, etc... - Can only be used as input variable of function or function_block - Therefore, stg you could reach: LogEntry.Initialize (stVariable|rVariable|iVariable|xVariable); Just a quick example (it's funny to play with ANY): Be careful it was not tested. I'm sure can be done better, please feel free to comment FUNCTION_BLOCK FB_LogEntry VAR_INPUT MsgClass : UDINT; // Like DEBUG, WARN, ERR... MsgCode : UDINT; // Like Errors.ERR_FAILED MsgTS : DT; // The timestamp END_VAR VAR _Data : STRING(80); // Our data container... _Descr : __SYSTEM.AnyType; // A standard descriptor for our data, containing TYPE_CLASS, address and size END_VAR METHOD SET_Value : BOOL VAR_INPUT anyValue : ANY; END_VAR VAR I : DINT; diSize : DINT; pStr : POINTER TO STRING; END_VAR // Check what did we receive in anyValue. diSize := anyValue.diSize; // We use constant __SYSTEM.TYPE_CLASS to identify the received data type CASE anyValue.TypeClass OF // Maybe we don't want to store references, pointers... and who knows what else... __SYSTEM.TYPE_CLASS.TYPE_REFERENCE, __SYSTEM.TYPE_CLASS.TYPE_POINTER : SET_Value := FALSE; // For the planned types we will be just fine. TYPE_CLASS.TYPE_BOOL, TYPE_CLASS.TYPE_INT, TYPE_CLASS.TYPE_REAL : SET_Value := TRUE; // Optionally string can be handled separately, maybe we have received STRING(255), but practically it is shorter than 80 bytes... TYPE_CLASS.TYPE_STRING : pStr := anyValue.pValue; diSize := MIN(anyValue.diSize, LEN(pStr^) + 1); // Get the actual size, and rewrite the received structure member diSize := MIN(SIZEOF(_Data), diSize); // Can chop down the received string to our length... SET_Value := TRUE; // Maybe want to play a little bit more here, to narrow down or convert datatypes, etc... // Or just reject any other datatype ELSE SET_Value := FALSE; RETURN; END_CASE // Fail, if the received value is still larger than our container... IF diSize > SIZEOF(_Data) THEN SET_Value := FALSE; END_IF // Here we should be ok, just set up the _DataType structure, and copy store the data IF SET_Value THEN THIS^._Descr.TypeClass := anyValue.TypeClass; // The typeclass is already filtered THIS^._Descr.diSize := diSize; // Set the (adjusted) size THIS^._Descr.pValue := ADR(_Data); // This will not change, just to be sure {IF defined (pou:SysMem.SysMemCpy)} SysMem.SysMemCpy(_DataType.pValue, anyValue.pValue, TO_UDINT(anyValue.diSize)); {ELSE} // An ugly replacement MemCpy FOR I:=0 TO diSize - 1 DO _Descr.pValue[I] := anyValue.pValue[i]; END_FOR {END_IF} // Otherwise, in case of failure maybe better set an empty value (overwrite the former data descriptor) ELSE THIS^._Descr.TypeClass := TYPE_CLASS.TYPE_NONE; THIS^._Descr.pValue := ADR(_Data); THIS^._Descr.diSize := 0; END_IF METHOD GET_Value : BOOL VAR_INPUT anyValue : ANY; END_VAR VAR I : DINT; END_VAR // We just have to serve the data, using the __System.AnyType structure received // Roughly we can say: IF anyValue.TypeClass = _Descr.TypeClass AND anyValue.pValue <> 0 // This should not be possible, already taken care of by Codesys (?) THEN {IF defined (pou:SysMem.SysMemCpy)} SysMem.SysMemCpy(anyValue.pValue, _DataType.pValue, TO_UDINT(MIN(anyValue.diSize, _Descr.diSize))); {ELSE} // An ugly replacement MemCpy FOR I:=0 TO MIN(anyValue.diSize -1, _Descr.diSize - 1) DO anyValue.pValue[I] := _Descr.pValue[I]; END_FOR {END_IF} // Just to make sure, that our string is terminated... IF anyValue.TypeClass = TYPE_CLASS.TYPE_STRING THEN anyValue.pValue[anyValue.diSize -1] := 0; END_IF GET_Value := TRUE; RETURN; END_IF // ... But can play more CASE anyValue.TypeClass OF TYPE_CLASS.TYPE_WSTRING : ; // Could do conversion TYPE_CLASS.TYPE_XSTRING : ; // Wow, I have to figure this out TYPE_CLASS.TYPE_PARAMS : ; // BTW, what is this, how to use? TYPE_CLASS.TYPE_ANYNUM : ; // ... END_CASE Be careful it was not tested. I'm sure can be done better, please feel free to comment 3. If you really want to do entries with variable size In a standard environment, it would be similar to the previous, except you dont have the container variable _Data, just use a pointer, practically _Descr.pValue At Initialize (SET_Value), you have to allocate the memory, would be easy with SysMem.SysMemAlloc - nowadays with SysMem.SysMemAllocData -, and you make sure to release it after use with SysMem.SysMemFreeData... SysMemAlloc was already hidden. The problem with this, that sooner or later your application will totally fragment the dynamic memory, and fail... So should look for some form of dynMaybe MemUtils.MemoryManager (I am not sure what is the status and the future of it). 4. You will end up by a LogEntry Factory ... 5. You could still have a look at this IEC Snippets BTW, Standard Codesys Logger is not a bad choice either. If you are really interested, I share some more code / library.
Last updated: 2025-03-09

RAMP_REAL FB is retaining my output value when i try to re use the FB ^{CODESYS Forge talk (Thread)}
RAMP_REAL FB is retaining my output value when i try to re use the FB
Last updated: 2024-07-29

Post by kims2024 on Timer change online ^{CODESYS Forge talk (Post)}
with codesys v2.3, I want to extend a timer value online. I have tried the value does not go !
Last updated: 2024-08-24

How to check whether one input is assigned a value? ^{CODESYS Forge talk (Thread)}
How to check whether one input is assigned a value?
Last updated: 2008-01-15

Is it possible to send a real value close to 0 through modbus? ^{CODESYS Forge talk (Thread)}
Is it possible to send a real value close to 0 through modbus?
Last updated: 2023-02-25

Test Manager - Having a user value persist from one execution to the next ^{CODESYS Forge talk (Thread)}
Test Manager - Having a user value persist from one execution to the next
Last updated: 2023-05-08

raspberry pi as PLC all GPIO input pins are TRUE value ^{CODESYS Forge talk (Thread)}
raspberry pi as PLC all GPIO input pins are TRUE value
Last updated: 2020-10-29

how read analog value from Arduino Uno in Raspberry pi through I2 C protocol ^{CODESYS Forge talk (Thread)}
how read analog value from Arduino Uno in Raspberry pi through I2 C protocol
Last updated: 2022-05-30

CANopen Manager on TURCK PLC sends PDO only on value change ^{CODESYS Forge talk (Thread)}
CANopen Manager on TURCK PLC sends PDO only on value change
Last updated: 2023-06-30

Modbus TCP Server connection is ESTABLISHED but all holding registers are value 0? ^{CODESYS Forge talk (Thread)}
Modbus TCP Server connection is ESTABLISHED but all holding registers are value 0?
Last updated: 2026-01-07

Post by fless on Warning C0564 when compiling CNC project with variables program ^{CODESYS Forge talk (Post)}
Hello, we are porting a CNC project from codesys 3.5.16 to codesys 3.5.19. The project has lots of CNC programs with variables. now we get hundreds of messages like this. [WARNING] CNC Test SP19: TestCNC SPS: PLC Logic: Application: C0564: A reference to uninitialized variable varCNC is used for initialization of TestCNC_D. Accessing the uninitialized variable may result in unexpected behavior. The objects program_name_D are implicit generated by codesys. I see no way to generated them after the variables. Is there a way to correct the initialization order? We know how to suppress this warning. But we need a clean solution as the warning already saved us in a other nonCNC project. Attached a small demo of the problem.
Last updated: 2024-03-21

Post by bjarne-pagaard on Multiple WebVisu ^{CODESYS Forge talk (Post)}
You can use the switch frame variable, but there should be a variable for each active visu user. You can put the switch frame variable in an array, and use CURRENTCLIENTID as index into the array to get what you want. The CURRENTCLIENTID is assigned to new users automagically by the Visu Management.
Last updated: 2024-03-14

Post by nico-hefr on Python script command for "Access Control" ^{CODESYS Forge talk (Post)}
Hi everyone, I use Python Script to generate some POU in Codesys V3.5 SP19 and I would like to limit the "Access Control" to them thanks to the Python command. Is there any commands that allow to edit the "Properties... >> Access Control" of the POU? The other possibility is to set the permissions with "Project >> User Management >> Permissions... >> Project objects >> Modify >> ... >> myPOU", but I did not find the related Python commands. Otherwise, is there a global setting that allows to set the permissions by default? For example, Modify = Denied for everyone user by default. Thank you in advance for your help, Nico
Last updated: 2024-07-18

Post by ranadheer on Implementation IEC-104 ^{CODESYS Forge talk (Post)}
Hi Everyone, As we didn't have client for IEC - 104 - only server server is available , so because of that we are trying to make establish the communication between the external simulator as a Client and codesys itself as a server. We are looking for the variable behavior from CODESYS has to change according to the message triggered by the CLIENT (we are using simulator Application like Redisant). We are able to see the log data as the status of triggering the SCS from Client received to the Log data of the codesys device(attached screen shot of it) and in simulator panel we had set the details to trigger the data from Redisant to Codesys. Current Status: The project builds and runs successfully, but I need guidance on how to connect this to an external IEC-104 simulator for testing and visualization by using demo mode.
Last updated: 2025-10-14

Post by stuartjr on Disabling forcing of specific variables ^{CODESYS Forge talk (Post)}
OK.. so maybe I miss understood for how the forcing order works. It seems that the force list is applied at the beginning of every task call (I'm assuming this based on what I am seeing). If I force my variable FALSE and then write it TRUE in a task, then it stays TRUE for that task, but then in the next task it will go back to FALSE.
Last updated: 2024-03-15

Post by pernockham on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Im looking for a way to define predefined version of the same structures through "extends"/inheritance. What I want to do is best shown with an example: TYPE log_item_val_type : ( BOOL_ := 0, INT_, REAL_, STRING_ ); END_TYPE TYPE LOG_DATA_BASE STRUCT val_type : log_item_val_type; (* value, name etc *) ENDSTRUCT ENDTYPE (* this/below is not possible as I understand from the compiler?? *) TYPE LOG_DATA_BOOL extends LOG_DATA_BASE : STRUCT val_type : log_item_val_type := log_item_val_type.BOOL_; END_STRUCT END_TYPE TYPE LOG_DATA_INT extends LOG_DATA_BASE : STRUCT val_type : log_item_val_type := log_item_val_type.INT_; END_STRUCT END_TYPE etc. for LOG_DATA_REAL and ..STRING. The system will not allow me to "re-define" "val_type" however. Instead I must do the work-around of defining four different types with all fields individually defined. The benefit if I could extend the base item would be that Im (more) sure the structures are identical. In usage I can call in a specific type rather use the base type and assign which type. Usage by pointer/ref to log_data_base would also be easier.. (* Usage: *) log_data : log_data_int := (name, value etc.) (* Instead of: *) log_data : log_data_base := (name, value, val_type).. Is this possible to achieve in some way that I have missed?
Last updated: 2025-03-05

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 dogulas on numeric text box control ^{CODESYS Forge talk (Post)}
Ok, this is how I made a numeric text field: use a Text Field properties -> Texts -> Text := %f (or %d or whatever you need) properties -> Text variables -> Text variable := (your numeric variable) properties -> Input configuration -> OnMouseDown -> Configure: Write Variable Input type := VisuDialogs.Numpad Use another variable (your numeric variable) Min val Max val etc. Please tell me there is an easier way to do this.
Last updated: 2025-10-02

Post by simone on Preferred way of managing Ip-adress/es for linux (debian) host? ^{CODESYS Forge talk (Post)}
Hi pernockham, I think you should ask your device vendor. For some time I used one from an Italian company where they had made a library where you can manage the ip with a function (something like SetIPAddr...), it was based on connmann on linux. From my little experience is better to use the "default" way, so for me is to manage the config file on interfaces or use the ip addr utility
Last updated: 2025-03-24

Post by larboardinner on Alarm Table Issues ^{CODESYS Forge talk (Post)}
Variable for Selected Alarm ID only updates when the visualization is actually configured to send the alarm’s ID back to the control. On some devices/visualization profiles this isn’t enabled by default. Make sure your Alarm Table element has “Send Selected Alarm ID” activated in the visualization properties. you could check this example: https://store.codesys.com/alarm-manager.html Geometry Dash Lite If that option isn’t available in your version, then unfortunately the “Selected Alarm Group” is the only one that updates reliably in older 3.5.x builds.
Last updated: 2025-11-17

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 ben1 on Access Variable Visu Dialog ^{CODESYS Forge talk (Post)}
Tough to know exactly what you are asking for here. Can you give a more thorough explanation and/or provide snips?
Last updated: 2024-11-17

Post by lucaver89 on Raspberry pi 3 and runtime 4.9.0.0 ^{CODESYS Forge talk (Post)}
Good morning, I'm using a raspberry pi3 as plc with the runtime 4.9.0.0. My program has many of retrain variables but when an update is performed the retrain variables comes back to default values. Is the a way to backups the retrain variables n a csv file? Is still the way to restore them from the csv? Thank you for helping Luca
Last updated: 2023-09-23

Sort by relevance or date