Post by pouyavakili on Execute Codesys Tests with python ^{CODESYS Forge talk (Post)}
Thank you for your input! What I'm ultimately trying to achieve is automated test execution as part of a CI/CD pipeline (e.g. in GitLab or Azure DevOps). For this, I need to: Open a CODESYS project via script Build the project Run the Test Manager tests from a .TestRepository.xml Collect test results (e.g., pass/fail + a report) Exit with a proper return code (for pipeline success/failure) To integrate this into automation, I’m using the CODESYS scripting engine via Python (headless), but the issue is that the get_testmanager() function isn't available on the project object — even though Test Manager is installed, licensed, and works interactively in the IDE. Are you suggesting that I should: Use the Test Manager GUI to script the logic with its internal scripting language? Or is there a way to launch the Test Manager in headless/scripted mode, while still being able to control things via Python? If there's a supported way to automate tests with the Test Manager using scripting, especially from pipelines or headless environments, I’d really appreciate any pointers or example workflows. Thanks again!
Last updated: 2025-07-24

Post by risele on Modbus connection via Qronox PCD3 M6893 ^{CODESYS Forge talk (Post)}
First, if you don't need to change conversion rules in runtime, take a look at "Unit conversion" module (Application -> add object -> UnitConversion). You can specify there biderectional conversion with different units, limits and so on. Second, since MODBUS don't have "real" types but only general 16-bit registers and Real is 32-bit, generally you need a byte-was conversion Real <> two Words. Note, that depending on the devices on both sides, there are two options: Real-> Word1, Word2 or Real-> Word2, Word1, where Word1 is minor register in Modbus register pair and Word2 is major. You can use simple union: TYPE u_Real : UNION rVal:REAL; wVal:ARRAY[0..1] OF WORD; dwVAL:DWORD; //same as previous, may be easier to specify the MB register END_UNION END_TYPE and convert it as following: VAR myUnion:u_Real; rValue_TO_SEND:REAL; rValue_TO_GET:REAL; END_VAR myUnion.rVal:=rValue_TO_SEND; rValue_TO_GET:=myUnion.rVal; Note, that WORD-order should be properly set in MODBUS registers, otherwise you will get strange values. This tool is helpful: https://www.scadacore.com/tools/programming-calculators/online-hex-converter/ Alternative, you can use functions as REAL_TO_DW and DW_TO_REAL from OSCAT_BASIC, for example.
Last updated: 2026-02-19

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 thomasrohnerch on Access to the path *** is denied ^{CODESYS Forge talk (Post)}
yes, this is working fine. for the moment this is acceptable.
Last updated: 2024-02-07

Post by micik on CAA File- FILE_OPERATION_DENIED error ^{CODESYS Forge talk (Post)}
Thank you wollview, it is clear now, it is due to security reasons that access to the file system is restricted.
Last updated: 2024-05-16

Post by timvh on Sensor not set ^{CODESYS Forge talk (Post)}
Your function block instance is not called, so the code is not executed to set the light on when the button is pressed.
Last updated: 2024-05-27

Post by squiggleypuff on RemoteTargetVisu creates Unresolved Reference ^{CODESYS Forge talk (Post)}
I have a project with a Festo CPX-E-CEC-C1-PN PLC (Run-time version 3.5.12.50) that I have been developing on just fine using Codesys V3.5 SP19 Patch 5 (64bit). I am at the stage where I wanted to use the Festo HMI screen, and have added a RemoteTargetVisu object to my application. After adding this object, I am no longer able to log in to the PLC as I get an Unresolved Reference warning for 'USERMGRUSERGETPROPERTY' towards the end of the download process. I was able to find this post (https://forge.codesys.com/forge/talk/Visualization/thread/fc686a6cb2/) where the two possible solutions are to "set the placeholder to emtpy" or update the runtime. Problem is, I don't know how to do either of these things, as I'm still very green in Codesys land. I'd be happy to update the Festo PLC runtime, as that seems like the better option, but have not had any luck in finding a tutorial for this online. If anyone could point me in the right direction I'd appreciate it.
Last updated: 2024-03-19

Post by anlebr on Alarm group template - Is it not possible with several instances? ^{CODESYS Forge talk (Post)}
Hi In the POU section of my project I have created a Fan function block and defined an alarm group template for this FB with one alarm (Motor fault). In the PLC program I define two instances of the fan function block. When going to the alarm configuration and pressing "Create or update alarm instances", I get two alarms listed. So far so good. However, when I start my program and check the alarm table in the visualization I only see one alarm, even if both are active. Am I doing something wrong, or is it not possible to define alarms on a function block level and get one set of alarms per instance of the function block?
Last updated: 2025-04-01

Post by andrax on Save Recipe on Paspberry ^{CODESYS Forge talk (Post)}
Unfortunately not. The folder does not work. There are neither error messages nor any other indication that this may be due to missing rights. I have searched the entire forum and also tested the Codesys example. The simple recipe management generally does not work! The Raspi crashes with the extended recipe management from the example. I have now found another sample that works. https://forge.codesys.com/forge/talk/Engineering/thread/61c6a04b79/ Many thanks to mcodem. After some trial and error I have found out: xcreate must be called at least once at runtime. After that xload_write and xread_save work All other functions do not work. It is also possible to save to the /home/Documents folder. So it is not due to the rights. It would be nice if Codesys would check where the problem really lies.
Last updated: 2023-12-30

Post by cvrettacos-dse on How to reset scroll of a table element ^{CODESYS Forge talk (Post)}
Hello, I would like to use swipe/pan gestures to scroll a table visualization element (CODESYS 3.5.21.10) ona DSE M810 display. The swipe / pan gesture control works fine, however, I cannot figure out how to reset / navigate to the top of the table again with code. I have tried the Scrolling begin variable, and the visu manager is setting it to FALSE right away but the table doesn't actually scroll back to top. If I check the “Scroll elements with scrollbar” box, then the Scrolling begin variable works perfectly, but now the swipe/pan scrolling no longer works and you have to use the scrollbar. Any assitence you can provide is appreciated. Thanks.
Last updated: 2026-04-21

Post by ewi04 on Git - User identification data is lost when codesys is closed ^{CODESYS Forge talk (Post)}
Hallo, it's not a big problem, but it is a bit annoying. The git user identification data is lost when codesys is closed. So I have to enter the information again and again. Is there a way to save the data? Environment: Codesys V3.5 SP19 Patch 4 (64Bit), Git 1.3.0.0 Thanks
Last updated: 2023-11-22

Post by charleskirkland on Connect to Azure IoT Hub ^{CODESYS Forge talk (Post)}
It sounds like your TLS setup is basically correct, since the handshake works via OpenSSL, so the issue is likely on the CODESYS side rather than the certificates themselves. From what I’ve seen with the Azure IoT Hub Client SL library, you should double-check that the SAS token is actually being generated and passed correctly to the function blocks (especially wsDeviceSaS) and that the MQTT/HTTPS FB is really triggered cyclically-otherwise the controller won’t initiate the connection at all. Also, make sure DNS, time (NTP), and full certificate chain trust are properly configured on the controller, since IoT Hub authentication depends on them even when using SAS tokens. Another thing worth checking is the library/runtime version-there are reports that certain versions changed behavior and caused connection issues. I’d recommend starting with the official demo project (AzureMQTTDemo) and comparing it step by step with your setup to see what’s missing or not triggered. Speed Stars
Last updated: 2026-04-27

Post by reinier-geers on Ping By Name ^{CODESYS Forge talk (Post)}
What library is that? Is there a version 9.2 ?
Last updated: 2023-08-25

Post by kumareasu on Code Size ^{CODESYS Forge talk (Post)}
Is this "Application Based Licence" is applicable for CODESYS Control RTE SL
Last updated: 2023-09-08

Where is data of ENIP getAttributeSingle stored? ^{CODESYS Forge talk (Thread)}
Where is data of ENIP getAttributeSingle stored?
Last updated: 2023-04-20

is there a way to make blink a text field ^{CODESYS Forge talk (Thread)}
is there a way to make blink a text field
Last updated: 2021-01-21

The required device description is not installed.. ^{CODESYS Forge talk (Thread)}
The required device description is not installed..
Last updated: 2023-10-03

Post by davidbo on RPI is license server down ^{CODESYS Forge talk (Post)}
It was but is running again
Last updated: 2023-10-19

Post by john-martin on RPI is license server down ^{CODESYS Forge talk (Post)}
In this moment the server is down.
Last updated: 2023-10-19

Detecting if a client is connected to webvisu server ^{CODESYS Forge talk (Thread)}
Detecting if a client is connected to webvisu server
Last updated: 2023-11-08

Is the Realtek RTL8119I-CG ethernet controler on supported list? ^{CODESYS Forge talk (Thread)}
Is the Realtek RTL8119I-CG ethernet controler on supported list?
Last updated: 2024-09-04

Is the Realtek RTL8119I-CG ethernet controler on supported list? ^{CODESYS Forge talk (Thread)}
Is the Realtek RTL8119I-CG ethernet controler on supported list?
Last updated: 2024-09-04

Is the Realtek RTL8119I-CG ethernet controler on supported list? ^{CODESYS Forge talk (Thread)}
Is the Realtek RTL8119I-CG ethernet controler on supported list?
Last updated: 2024-09-04

ERROR: CodeMAccess2: Used CmRuntime 2.61.2705.500 is too old ^{CODESYS Forge talk (Thread)}
ERROR: CodeMAccess2: Used CmRuntime 2.61.2705.500 is too old
Last updated: 2024-09-18

How to know if output if function block is used ^{CODESYS Forge talk (Thread)}
How to know if output if function block is used
Last updated: 2024-10-15

Sort by relevance or date