Post by sajid on NMEA Serial data read in Control win v3 x64 ^{CODESYS Forge talk (Post)}
I am using the SerialCom example program from the CODESYS website to read NMEA strings in CODESYS Control Win V3 x64 through a serial-to-USB converter. However, I occasionally receive only partial data or encounter errors in the received string. A screenshot of expected NMEA string attached for reference. Could you please advise on how to ensure the full NMEA string is received consistently? Error in strRead variable is <value of="" the="" expression="" cannot="" be="" retrieved=""></value>
Last updated: 2025-10-16

Post by sajid on NMEA Serial data read in Control win v3 x64 ^{CODESYS Forge talk (Post)}
I am using the SerialCom example program from the CODESYS website to read NMEA strings in CODESYS Control Win V3 x64 through a serial-to-USB converter. However, I occasionally receive only partial data or encounter errors in the received string. A screenshot of expected NMEA string attached for reference. Could you please advise on how to ensure the full NMEA string is received consistently? Error in strRead variable is <value of="" the="" expression="" cannot="" be="" retrieved=""></value>
Last updated: 2025-10-16

NMEA Serial data read in Control win v3 x64 ^{CODESYS Forge talk (Thread)}
NMEA Serial data read in Control win v3 x64
Last updated: 2025-10-16

Post by xcqt on Oop best practice ^{CODESYS Forge talk (Post)}
Hi all, I’m currently trying to improve my OOP structure in CODESYS and I’m looking for some input on how others approach this. I understand the basics like inheritance, interfaces, abstract FBs, methods, and properties, but I still struggle a bit with the overall architecture and what’s considered clean or scalable in bigger projects. As an example, I’m working on two different energy meter function blocks: FB_EnergyMeter_MQTT reads data from MQTT (strings) FB_EnergyMeter_Modbus reads data from Modbus (words) Both have their own Update() method and implement the same interface (something like IF_EnergyMeter). Later on, I’ll probably add more meter types, but they should all behave the same from the controller’s point of view. Now, there’s a FB_GridControl block that needs power data from these meters. I see two options here: Define the meter blocks inside FB_GridControl and call them directly (for example fbModbusMeter.UpdateModbus()). Keep the meter blocks outside and pass them into FB_GridControl as interface references, so the control block doesn’t know which specific type of meter it’s dealing with. Option 2 feels cleaner and more flexible to me, but I’m not entirely sure how to handle the data flow in that case. Should I pass the meter instance through an interface reference (REFERENCE TO IF_EnergyMeter)? Or is there a better way to link the external FBs to the control block? I’d like to hear how you structure this kind of setup or see an example from someone who has done something similar. EDIT: I think i need to do something like this fbModbusUpdateInput(wInput:= wWordValue); fbMqttUpdateInput(strInput:= strStringValue); IF bUseMqtt THEN Meter REF = fbMqttUpdateInput; ELSE Meter REF = fbModbusUpdateInput; END_IF fbControl.SetMeter(UsedMeter := Meter); Or am i thinking wrong? Thanks, Thomas
Last updated: 2025-10-16

Oop best practice ^{CODESYS Forge talk (Thread)}
Oop best practice
Last updated: 2025-10-16

Post by etalp on Eaton XC303 firmware update via USB ^{CODESYS Forge talk (Post)}
Hi, I'm struggling with updating my xc303 to firmware 3.5.17. It is possible only via USB port. I've installed proper update files on the USB then plug it into the PLC's USB port and restarted the device. Shortly after LED's on the PLC started to blink, so updating process has started. But after 10 minutes the PLC LED turned off and after all I could't serach for this PLC in Codesys, but could ping it. Could someone eplain to me proper procedure of updating the fimrware in XC303 via USB? Is it neccesary to STOP the PLC switch after pluging the USB?
Last updated: 2025-10-15

Post by eildp on Adding a Softmotion License to a Weintek HMI ^{CODESYS Forge talk (Post)}
I am here with the same question wondering if you found an answer. Anyone? Thanks!
Last updated: 2025-10-16

Post by eschwellinger on Adding a Softmotion License to a Weintek HMI ^{CODESYS Forge talk (Post)}
You need to ask Weintek if they support the licensing. For Softmotion the device should be realtime capable.
Last updated: 2025-10-17

Adding a Softmotion License to a Weintek HMI ^{CODESYS Forge talk (Thread)}
Adding a Softmotion License to a Weintek HMI
Last updated: 2025-10-17

Request for IFM ecoPlus21 installation package ^{CODESYS Forge talk (Thread)}
Request for IFM ecoPlus21 installation package
Last updated: 2025-10-17

Post by dekelec on Request for IFM ecoPlus21 installation package ^{CODESYS Forge talk (Post)}
Hello, I’m looking for the ecoPlus21 development environment used with early IFM controllers (e.g., CR0020_Q firmware). We have an old project created in ecoPlus21 that cannot be opened in CoDeSys 2.3, and IFM no longer provides this software. If anyone still has the ecoPlus21 installer or knows where it can be downloaded, please let me know. It’s needed only for recovery and migration of an existing project. Thanks in advance,
Last updated: 2025-10-17

Request to share documents about SoftPLC Extension SL ^{CODESYS Forge talk (Thread)}
Request to share documents about SoftPLC Extension SL
Last updated: 2025-10-18

Control Win SL licensing ^{CODESYS Forge talk (Thread)}
Control Win SL licensing
Last updated: 2025-10-18

Post by ranadheer on Request to share documents about SoftPLC Extension SL ^{CODESYS Forge talk (Post)}
Hello Everyone Our team is planning to begin an industrial automation project and we are currently evaluating the use of SoftPLC Extension SL as a potential solution. As we are in the early stages and have yet to start the implementation, we kindly request access to official reference documents, technical manuals, and datasheets relating to SoftPLC Extension SL. Thank you very much for your assistance. We look forward to your response.
Last updated: 2025-10-18

Post by ranadheer on Control Win SL licensing ^{CODESYS Forge talk (Post)}
Hi johnlee and jeffgamsby Is Control win SL is a SoftPLc Extension SL
Last updated: 2025-10-18

Post by s1mon on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
If I add "PlaceholderFilePath.2=/sys/devices/w1_bus_master2, $OneWire2$" to the CODESYScontrol.cfg I can use a 2nd OneWireMaster in the Codesys Runtime. But then my EtherCAT_Master is not working any more. Any Idea? Is there any instruction or documentation how a 2nd OneWire Bus Master can be used within Codesys Runtime on a raspberry pi 5?
Last updated: 2025-10-18

Post by eschwellinger on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
you need to have an own task for the one wire and io update these slaves in an own low prio task!
Last updated: 2025-10-18

Scripting: exportPLCopenXML ^{CODESYS Forge talk (Thread)}
Scripting: exportPLCopenXML
Last updated: 2025-10-18

Post by kaotic2499 on Upgraded Raspberry 2b to Raspberry 5, Trends Broken? ^{CODESYS Forge talk (Post)}
Hello! Raspberry pi 2b just is getting a bit slow so decided to go for a Raspberry 5. Project is now upgraded to suit Pi 64 SL... so, now although everything runs perfectly... for some reason my trends will not save! its driving me nuts... ^Tried merging tasks with main program & trends ^tried re-prioritizing tasks (shifting 1 - 31 etc) ^Recreated the Trend Recording manager from scratch ^Tried swapping persisitant vars to GVL Retains then non-retains... (Project attached is as per before trial&error) Raspberry Pi 2b still runs "perfectly" though its very chuggy (Still saves the trends, note this is of an pretty much identical project minus the device compatibility) Does anyone have any advice to offer? project attached.... I feel it could be outside of Codesys itself causing the issues, but cant see/find anything on the internet to assist (or anyone else with the same problem as me...) Can attach project in another format (non archive) any assistance is much appreciated!
Last updated: 2025-10-19

Post by s1mon on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
All Sensors from the OneWire Master are assigned already to a seperate task with low prio (26) that runs with 1s cycle time. My EtherCat Task is running with Prio 1. It all works fine, until I adjust the CODESYScontrol.cfg or the CODESYScontrol_Usr.cfg files so that it supports a 2nd OneWire Master in the Codeys Runtime. If I change something in this config file and reboot my EtherCat Master stops working.
Last updated: 2025-10-19

Post by cmj-icsys on Custom configure tab in device editor ^{CODESYS Forge talk (Post)}
Hi everyone, I’m developing a custom CODESYS I/O driver for my company’s device, and I’ve been studying the example projects in CODESYS V3.5 SP20 Patch 5. In the IOMappingExample.project, I noticed that EtherCAT devices provide additional configuration tabs in the Device Editor, such as General, Process Data, etc. However, for custom I/O driver examples (based on IoDrv), the Device Editor only shows the default tabs like <devicename> I/O Mapping or <devicename> Parameters.</devicename></devicename> I’d like to create custom tabs or configuration pages in the Device Editor (e.g., “General Settings”, “Communication”, etc.) to allow users to configure parameters in a more structured way. Could anyone explain: How to define and register custom tabs or UI pages in the Device Editor? What tools or SDKs are needed to create UI elements such as combo boxes or check boxes? How to bind those UI controls to device parameters defined in the XML (device description)? Any example, SDK reference, or documentation link would be really helpful. Thanks in advance!
Last updated: 2025-10-20

Post by s1mon on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
yes sure. Thx for your support! This is the Codesys project stripped down only to my EtherCat and OneWire Configuration. The Project now contains only one OneWire Master on GPIO4.
Last updated: 2025-10-20

Post by eschwellinger on Two OneWireMaster on one Raspberry PI 5 ^{CODESYS Forge talk (Post)}
hm.. could you add the project or at least parts of it?
Last updated: 2025-10-20

Post by e13740e on Parameterized Property syntax for array element processing ^{CODESYS Forge talk (Post)}
Since parameterized (indexed) properties are not possible, I decided to use architectural approach "Indexing Property Adapter" to achieve the intended goal — avoiding code duplication for validated access to array elements. Essence: Create a Function Block Adapter (FB_PropertyAdapter) that encapsulates the logic for working with a single element of the target array (e.g., with one settings structure). Declare Properties inside the adapter block for accessing each individual field of the data structure. All validation logic is implemented within the Set accessors of these properties. Data Binding via VAR_IN_OUT: The adapter block receives a reference to a specific data element from the global array through its VAR_IN_OUT section, which ensures direct work with the original data without copying. Create an Array of Adapters: In the parent POU (e.g., FB_SettingsManager), an array of these adapter blocks is created — one for each element of the global array that needs to be managed. Initialize Bindings: In a FOR loop, each adapter instance from the array is given a reference to the corresponding data element. Result: This approach allows accessing the data via the index of the adapter array, and then through the property name, which simulates the behavior of an indexed property: MyAdapterArray[Index].MyProperty Thus, the validation and data access logic is written only once inside the adapter block and is then reused multiple times by creating instances of it in an array. This completely solves the problem of code duplication while providing a clean, scalable, and object-oriented architecture compatible with standard CODESYS features. Question closed.
Last updated: 2025-10-19

Parameterized Property syntax for array element processing ^{CODESYS Forge talk (Thread)}
Parameterized Property syntax for array element processing
Last updated: 2025-10-19

Sort by relevance or date