How do I configure a visualisation text object to enter data? ^{CODESYS Forge talk (Thread)}
How do I configure a visualisation text object to enter data?
Last updated: 2016-05-20

3.5.17: Setting up OPCUA Client data source to another PLC OPCUA server ^{CODESYS Forge talk (Thread)}
3.5.17: Setting up OPCUA Client data source to another PLC OPCUA server
Last updated: 2021-11-02

i need to do a data logging with 750-842 ^{CODESYS Forge talk (Thread)}
i need to do a data logging with 750-842
Last updated: 2013-08-26

exporting or copying the COE online data from an ethercat slave device ^{CODESYS Forge talk (Thread)}
exporting or copying the COE online data from an ethercat slave device
Last updated: 2019-10-30

PM564 ETH for reading data from modbus serial slave using COM1 port ^{CODESYS Forge talk (Thread)}
PM564 ETH for reading data from modbus serial slave using COM1 port
Last updated: 2017-11-28

Save the data log file in the USB from the visualization ^{CODESYS Forge talk (Thread)}
Save the data log file in the USB from the visualization
Last updated: 2021-01-25

Send Data to a specified Register with TCP/IP Cleint Server ^{CODESYS Forge talk (Thread)}
Send Data to a specified Register with TCP/IP Cleint Server
Last updated: 2021-08-25

Can't link process data variables to IO from a positionsensor while using a demo soft PLC ^{CODESYS Forge talk (Thread)}
Can't link process data variables to IO from a positionsensor while using a demo soft PLC
Last updated: 2022-03-04

can I send data over udp/tcp in simulation mode? ^{CODESYS Forge talk (Thread)}
can I send data over udp/tcp in simulation mode?
Last updated: 2016-06-05

Profinet Master on RPI3 with CodeSys Control - No live data on I/O ^{CODESYS Forge talk (Thread)}
Profinet Master on RPI3 with CodeSys Control - No live data on I/O
Last updated: 2017-07-06

Wie kann ich auf alle Benutzerdaten zugreifen? How to access User-Data? ^{CODESYS Forge talk (Thread)}
Wie kann ich auf alle Benutzerdaten zugreifen? How to access User-Data?
Last updated: 2018-01-16

Wago_IO-Link Master 750-657 unable to read all data frame ^{CODESYS Forge talk (Thread)}
Wago_IO-Link Master 750-657 unable to read all data frame
Last updated: 2022-06-10

Error 3803: (2): Out of data global memory. Variable 'CAN1_CANREMOTE_INFO'. 5904 bytes. ^{CODESYS Forge talk (Thread)}
Error 3803: (2): Out of data global memory. Variable 'CAN1_CANREMOTE_INFO'. 5904 bytes.
Last updated: 2019-09-10

Trend to display Wago 750-880 SD memory data logging ^{CODESYS Forge talk (Thread)}
Trend to display Wago 750-880 SD memory data logging
Last updated: 2012-10-24

Error 3803: (2): Out of data global memory. Variable 'CAN1_CANREMOTE_INFO'. 5904 bytes. ^{CODESYS Forge talk (Thread)}
Error 3803: (2): Out of data global memory. Variable 'CAN1_CANREMOTE_INFO'. 5904 bytes.
Last updated: 2019-09-06

Cold reset / exchange of data between applciation on one PLC ^{CODESYS Forge talk (Thread)}
Cold reset / exchange of data between applciation on one PLC
Last updated: 2016-04-16

Not able to see input data coming from eip adapter on codesys ^{CODESYS Forge talk (Thread)}
Not able to see input data coming from eip adapter on codesys
Last updated: 2024-03-07

Has anyone fed ESP32 sensor data into CODESYS (via MQTT/Modbus)? ^{CODESYS Forge talk (Thread)}
Has anyone fed ESP32 sensor data into CODESYS (via MQTT/Modbus)?
Last updated: 2025-10-29

Post by critcho on WebVisu Numpad dialog - Dialogtitle not accepting string variable ^{CODESYS Forge talk (Post)}
I have a WebVisu page which is re-used for multiple types of gas; it displays the alarm thresholds etc. for one gas at a time. I have an array of structures holding the set-points for each of the gasses. I'm trying to change the dialog title for the value input pop-up (VisuDialogs.Numpad). The Dialogtitle is set to Gas_Alarms.HighAlarmActivationLevelDialog, which is a string(50): When the gas type is changed (page first loaded, or prev/next buttons), METHOD Gas_Alarms.Update_Display_Variables is called, to update the strings used for the dialog titles so it shows GasName High Alarm Activation Level (EngineeringUnits), e.g. CO2 High Alarm Activation Level (PPM): HighAlarmActivationLevelDialog := Insert(' High Alarm Activation Level ()', EngineeringUnits, 30); HighAlarmActivationLevelDialog := Insert(HighAlarmActivationLevelDialog, GasName, 0); (That's not where the problem is, I'm just explaining why I'm using a variable dialogue title.) The variables used are definitely strings, but i'm always getting the error: "The type of the dialog title must be either STRING or WSTRING". I've tried moving HighAlarmActivationLevelDialog etc. to the GVL and also changing them to WSTRING, I even tried adding them to the structure array, but I always get the same error. Clearing the dialog title for that element removes the error - so I'm confident it's not a phantom error caused by something else. But I should be able to add these titles, can't just nuke them all to make it work. The MinVal and MaxVal for the Numpad are called from the array, e.g. GVL.Gas_Alarm_Configs[0].ScaledValueMIN, they are not getting an error. I am using array indexes 1 - 5 for the gasses, when I load the form or change gas, I copy the selected index to index 0 of the array, and values from Gas_Alarm_Configs[0].[ALL] are displayed on the page. When they hit save, I copy Gas_Alarm_Configs[0].[ALL] to Gas_Alarm_Configs[CurrentGasIndex].[ALL]. (ALL just means every element, I can't figure out how to display an asterix in this question... :) ) I've searched online for variable title dialog, but not found anything to help. Thanks for your help!
Last updated: 2025-05-29

Post by talhaali on Data logging from codesys to Microsoft Access ^{CODESYS Forge talk (Post)}
Hi, I want to write data from Codesys to Microsoft access and want to save it as mdb file. There is a way to store data in excel(CSV) file but instead of this, I want to save data in access (mdb) file. Does anyone have a solution? Thanks
Last updated: 2024-04-04

Post by talhaali on Data logging from codesys to Microsoft Access ^{CODESYS Forge talk (Post)}
Hi, I want to write data from Codesys to Microsoft access and want to save it as mdb file. There is a way to store data in excel(CSV) file but instead of this, I want to save data in access (mdb) file. Does anyone have a solution? Thanks
Last updated: 2024-04-04

Post by trycyclepower on How to transfer data from DINT to Union(16 Bools) which I need to use in Few FBs ^{CODESYS Forge talk (Post)}
I have DINT data from drive input and would like to use this data in Bools in bunch of the FBs. I have tried using Union but it is not working. Please suggest
Last updated: 2023-12-14

Post by alez on CANOpen SDO to write VISIBLE STRING ^{CODESYS Forge talk (Post)}
Hello, I am experiencing difficulties in configuring a CANopen device by sending SDOs. In particular I am attempting to write an Object Dictionary that has VISIBLE STRING as the Data Type. When I try to configure the sending of an SDO from Codesys to configure this parameter I am not allowed to enter a string value. In my particular case I am trying to change the Manufacturer Device Name ( Index 0x1008 ). Could it be that Codesys doesn't manage these types of variables?
Last updated: 2024-04-29

Post by ndzied2 on Rounding error in simple addition ^{CODESYS Forge talk (Post)}
This is a consequence of how computers store floating point numbers. 0.1 cannot be exactly represented in a computer. This is not a CoDeSys thing. Here is a link to a converter to show you the exact value that is represented when you use a REAL data type (which is a 32 bit float). https://baseconvert.com/ieee-754-floating-point If you really need to keep track of 0.1 increments. use INT OR DINT and then add 1 each time and assume that there is one decimal place.
Last updated: 2024-05-24

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

Sort by relevance or date