write data to the CSV file ^{CODESYS Forge talk (Thread)}
write data to the CSV file
Last updated: 2018-01-20

To write a binary file ^{CODESYS Forge talk (Thread)}
To write a binary file
Last updated: 2018-12-10

Write and read in sd ^{CODESYS Forge talk (Thread)}
Write and read in sd
Last updated: 2021-03-01

Read/write variables Codesys <> Python script ^{CODESYS Forge talk (Thread)}
Read/write variables Codesys <> Python script
Last updated: 2020-10-24

Modbus Read/Write Function 23 Problem ^{CODESYS Forge talk (Thread)}
Modbus Read/Write Function 23 Problem
Last updated: 2020-08-12

File Write and Read using Codesys ^{CODESYS Forge talk (Thread)}
File Write and Read using Codesys
Last updated: 2014-11-28

read/write to XLS file ^{CODESYS Forge talk (Thread)}
read/write to XLS file
Last updated: 2015-03-11

EtherCAT SDO Data Read/Write ^{CODESYS Forge talk (Thread)}
EtherCAT SDO Data Read/Write
Last updated: 2021-02-03

Write variable of type TIME ^{CODESYS Forge talk (Thread)}
Write variable of type TIME
Last updated: 2018-04-27

File Write and Read using Codesys ^{CODESYS Forge talk (Thread)}
File Write and Read using Codesys
Last updated: 2018-09-17

Modbus read/write, PI as slave ^{CODESYS Forge talk (Thread)}
Modbus read/write, PI as slave
Last updated: 2018-10-02

write new IP address from Codesys ^{CODESYS Forge talk (Thread)}
write new IP address from Codesys
Last updated: 2020-09-08

PFC200 (8208) Com port write ^{CODESYS Forge talk (Thread)}
PFC200 (8208) Com port write
Last updated: 2022-09-21

Codesys read and write with MicroLogix1100 ^{CODESYS Forge talk (Thread)}
Codesys read and write with MicroLogix1100
Last updated: 2021-12-14

Problem mit Canopen SDO Write ^{CODESYS Forge talk (Thread)}
Problem mit Canopen SDO Write
Last updated: 2019-10-31

Read xml and write values ^{CODESYS Forge talk (Thread)}
Read xml and write values
Last updated: 2014-07-04

I2c write is BeforeWriteOutputs needed? ^{CODESYS Forge talk (Thread)}
I2c write is BeforeWriteOutputs needed?
Last updated: 2024-02-07

CANOpen SDO to write VISIBLE STRING ^{CODESYS Forge talk (Thread)}
CANOpen SDO to write VISIBLE STRING
Last updated: 2024-04-29

Modbus write via FB failure ^{CODESYS Forge talk (Thread)}
Modbus write via FB failure
Last updated: 2025-11-06

Post by kumareasu on Code Size ^{CODESYS Forge talk (Post)}
Hello, How to find the following for for my application when I want to switch over to "Application Based Licence"... Code Size. IO size When I use Analog IO. IO size when I use AC inverter(Drive for AC induction motor). For example we read/write few EtherCAT registers.
Last updated: 2023-09-07

Post by kurtk on Modbus TCP Server ^{CODESYS Forge talk (Post)}
ditto I'm just getting my codesys wheels on and the modbus stuff is confusing. I am re-platforming an existing PLC application On that platform one could simply tag variables to register numbers and the whole shooting match could be accessed via modbus and typically holding registers and input registers were treated the same way... On codesys I see there is a modbus TCP server Device I/O mapping tab and a Modbus TCP server IEC objects tab I get the sense that one can configure the serving of variables both/either way but am unclear about the optimum/necessary path. Apparently in the IEC Objects tab one can "ADD" something or other - presumeably channels. I have created a preliminary function block but the Select Function Block window shows nothing to select WTH ? I exported the Device mapping and was surprised to see the entire Device IO map - complete with all the bit-mapped holding/input registers!! WTH!!?? Bit-mapped words are strictly a nichey special purpose application. I am targetting making a couple hundred variables available which would turn into hundreds of pages of IO/mapping Is the FUnction Block IEC objects thingy an alternative to that ? I notice that CODESYS shows the tags which the PLC used to specify the register address... are tags used in CODESYS for any specific hard-core purpose ?
Last updated: 2025-08-19

Post by timvh on Problem Reading Registers via Modbus from non Codesys device ^{CODESYS Forge talk (Post)}
According to the documentation: https://wiki.teltonika-networks.com/view/RUT956_Modbus You need to create a Channel to read 2 registers from address 143 to get the lattitude. It doesn't specify if you need to read it as a Holding Register or as an Input Register. You could try both. So in the Teltonika router, you need to enable it as being a Modbus Server. Then in CODESYS add an Ethernet Adapter, then a Modbus Client (Master) and to the Client (Master) add the Modbus Server (Slave). Set the IP address and add the Channel. The please consider that CODESYS doesn't update any variables when they are not used in the application. In the I/O mapping tab of your I/O configuration, you can set the "Always update" to enabled.
Last updated: 2025-03-08

Post by timvh on Modbus Extended Registers ^{CODESYS Forge talk (Post)}
Maybe the following helps: https://forge.codesys.com/prj/codesys-example/modbus/home/Home/
Last updated: 2023-08-26

Post by ph0010421 on MODBUS TCP REGISTERS CODESYS V3.5 ^{CODESYS Forge talk (Post)}
hello Use FC3 instead of FC4
Last updated: 2024-10-11

Post by ben1 on How to write multiple coils (Modbus FC15) ^{CODESYS Forge talk (Post)}
When you say it does not work, does nothing happen or do you get an error? I have not used this function in codesys but from my past experience with Modbus I believe the coils need to be contiguous, which may be why yours is failing? Have you tried using Write Registers (16) to do the job? Or is their data in-between you do not want to edit in the transaction?
Last updated: 2024-11-17

Sort by relevance or date