Post by pedrorgd on SFC Exit Action during SFCReset Flag ^{CODESYS Forge talk (Post)}
I have an SFC POU with an SFCReset Flag that I use to restart it from the beginning. It works properly. During an Action Step I set one variable to TRUE and I reset it to FALSE during the Exit Action. My question is if this Exit Action will be activated -and the variable reset to FALSE- if I get out of the active step using the SFCReset Flag.
Last updated: 2025-02-11

Post by camjam on BOOL variable in OPC UA and modbus simultaneously ^{CODESYS Forge talk (Post)}
I have come across this. The only way i could get it to work would be to define a word that is also the same address as the Bools. eg %MX600.0 through to %MX600.15 would be individually defined in the variables and them have another variable word defined at %MW300. You still need to break out the word in what ever program you are using to read/write the OPCUA tags.
Last updated: 2025-08-18

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 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

Post by automa on Defining local variables that can be independent with several users. ^{CODESYS Forge talk (Post)}
Hi, I am looking for a way to define a local variable that will be multi user independent. This is so several user can connect at the same time select frames independent of each other.
Last updated: 2023-09-04

Post by sturmghost on Specify Input Configuration "OnDialogClosed" Action to only react to certain Dialogs ^{CODESYS Forge talk (Post)}
You could work around this problem by implementing some sort of "state machine". Each dialog sets a boolean variable when they are closed so you know which dialog was closed. Then you can react to this accordingly.
Last updated: 2023-10-01

Post by gorditron on Modbus Slave RTU in der Applikation abschalten ^{CODESYS Forge talk (Post)}
Hallo, gibt es eine Möglichkeit die Modbus Slaves (ModbusSlaveComPort) innerhalb der Applikation über ein Variable zu aktivieren oder zu deaktivieren? Bilder als Datei Danke!
Last updated: 2023-11-09

Post by imdatatas on Axis variable indicating modulo of finite setting ^{CODESYS Forge talk (Post)}
You could try with "iMovementType" member of AXIS_REF_SM3 struct. https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/DriveInterface/AXIS_REF/AXIS_REF_SM3.html https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/DataTypes/DriveInterface/SMC_AXIS_TYPE.html
Last updated: 2023-11-25

Post by nathant on Saving variable values on power cycle (RevPi Connect) ^{CODESYS Forge talk (Post)}
Hello, this seems to be a known issue, but persistent/retain variables don't seem to work properly on RevPi devices. Is there a workaround to this? All I need is for a few configuration variables to be remembered through power cycle.
Last updated: 2023-12-03

Post by hwopereis on How to use Application Trigger in Modbus TCP Server ^{CODESYS Forge talk (Post)}
I'm now circumventing the problem by creating a separate TCP client for all Write actions. Upon registering a changed variable, I enable this client, until the change is processed.
Last updated: 2024-07-01

Post by kevinjordan on C0244: No VAR_PERSISTENT list is part of the application to enter instance path for variable ^{CODESYS Forge talk (Post)}
Do you still have this image, or can you tell me where I need to click to enable persistant variables? I'm getting the same error:C0244: No VARPERSISTENT
Last updated: 2024-07-17

Post by ljg007 on Variable assignments ^{CODESYS Forge talk (Post)}
That is an output of the Function Block ModbusMasterRTU example: xIsConnected=> xIsConnected In this line the VAR ModbusMasterRTU.xIsConnected is written to VAR xIsConnected xError=> is writing to nothing here.
Last updated: 2024-07-22

Post by c3po on Visualisierung wechseln über SPS Variable Codesys 3.5 ^{CODESYS Forge talk (Post)}
kann das bitte noch mal jemand genauer beschreiben? Der Link funktioniert nicht, weil Codesys so schlau war seine Onlinehilfe abzuschalten. Das denen das nicht peinlich ist -.-
Last updated: 2024-08-26

Post by open on (no subject) ^{CODESYS Forge talk (Post)}
Hello, I want my button to be attached image ON_Good when variable true but however when i copied the visualization object into a new visualization screen it become attached image ON_Bad. Anyone know how to make it attached image ON_Good? Warmest regards,
Last updated: 2024-09-03

Post by dengsberg on Check Connection Status of the OPC-UA Server for Data Source Manager with OPC-UA Client ^{CODESYS Forge talk (Post)}
Another question is how to test the quality of the individual variable?
Last updated: 2024-09-07

Post by ph0010421 on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
So it's currently mapped to an array of BYTES? Can you create a UNION? TYPE sBytesString : UNION AsBytes: ARRAY[0..127] OF BYTE; AsString: STRING(128); END_UNION END_TYPE Map it to the bytes, read it in the STRING!
Last updated: 2024-09-23

Post by arwie on Shared memory between Python and Codesys ^{CODESYS Forge talk (Post)}
Hi, I wrote a tutorial how to do this. Fast variable exchange between CODESYS and PYTHON via shared memory: https://gist.github.com/arwie/ff56783d9a2fff52940de82ae1bc1a22
Last updated: 2024-10-04

Post by arwie on Read bytes from Codesys runtime into external Python script ^{CODESYS Forge talk (Post)}
Hi, I wrote a howto setup shared memory between CODESYS and Python. Working example code is linked. Fast variable exchange between CODESYS and PYTHON via shared memory: https://gist.github.com/arwie/ff56783d9a2fff52940de82ae1bc1a22
Last updated: 2024-10-04

Post by timvh on Refresh visulization realtime ^{CODESYS Forge talk (Post)}
Should work by using the property Dynamic bitmap - Bitmap version. Change the value of the variable you linked to this property after you updated the image. See: https://content.helpme-codesys.com/en/CODESYS%20Visualization/_visu_elem_image.html
Last updated: 2024-10-23

Post by pistola on Case Function - Multiple Conditions, Is it possible? ^{CODESYS Forge talk (Post)}
Thanks for the information, I ended up just making a long if else statement as each variable had 3 possible options, I figured at least this way it would still work.
Last updated: 2024-11-05

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
thank you, i tried your library and device description but i don't get analog values. Do i something wrong? i also got an library error at the I2C_BASE functionblock the calcCycleTime gave an variable size error, so i added thet conversion from ULINT_TO_UDINT.
Last updated: 2024-11-07

Post by pistola on Checking or changing objects dimensions using code. ^{CODESYS Forge talk (Post)}
That works, thanks, I was trying to get a variable into the Position>Height and was struggling, then I was using absolute movement, never though to try relative movement.
Last updated: 2024-11-19

Post by timvh on VisuElems.cmpDynamictext.DynamicTextGetTextW returns pointer to empty string ^{CODESYS Forge talk (Post)}
Try this: VAR sTextList : STRING; END_VAR sTextList := 'NameOfTheTextList'; // call to the function with the address of the string variable which contains the name of the textlist : ... ADR(sTextList), ....
Last updated: 2025-02-07

Post by fil on Using Latch Variable in Alarm as input from text list ^{CODESYS Forge talk (Post)}
Good morning, I am currently working on a project where this would be of enormous value. Any input would be very welcome - thanks in advance. Best regards Fil
Last updated: 2025-03-06

Post by tvm on Passing properties as VAR_IN_OUT variables. ^{CODESYS Forge talk (Post)}
Use a VAR_INPUT for properties. The reason for the error is that you can't get a reference to a property. Using a VAR_INPUT will copy the property to an input variable.
Last updated: 2025-03-06

Sort by relevance or date