# Modbus - 750-460 configuration by codesys **URL:** \ **Category:** CODESYS\ **Created:** [September 24, 2026, 5:41am UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889 "2026-09-24T05:41:00Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://www.wago.community/u/lorenzo)\ **Post date:** [September 24, 2026, 5:41am UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/1 "2026-09-24T05:41:00Z")
Hello everyone, I have a 750-469/0003-000 thermocouple module connected to a 750-362 Modbus coupler, which is in turn connected to a PFC300 (FW31). I need to read Type J thermocouples, so I have to change the module’s channel configuration/import settings Is it possible to modify the thermocouple type through CODESYS code, without using configuration tools? If so, does anyone have an example? Thanks. ---
**Author:** ![AdamReeve](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/adamreeve/32/59_2.png) [@AdamReeve](https://www.wago.community/u/AdamReeve)\ **Post date:** [September 24, 2026, 1:18pm UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/2 "2026-09-24T13:18:23Z")
Someone please correct me if I am wrong, but I do not believe this is possible over Modbus. For many “configurable” modules such as 3-phase power measurement, serial comms, CAN gateway, etc., you can use the WagoSysFieldbusModule library to create an instance of the module’s type that can be used by application libraries (WagoAppPowerMeasurement, WagoAppCom, etc). However, the WagoSysFieldbusModule function block for the 750-469 modules does not have any associated output data, only input data. This means it has no way to communicate with the module’s configuration data (like the FbModule\_75x\_469 fb within WagoSysModule\_75x\_469 library can for modules directly on the Kbus). ---
**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://www.wago.community/u/lorenzo)\ **Post date:** [September 24, 2026, 3:40pm UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/3 "2026-09-24T15:40:04Z")
Hi, For the 750-363, I see that the documentation refers to the **Modbus configuration registers**. Are these the registers that should be used for this purpose? I’m not sure how to configure them. Alternatively, can the **Modbus Server Init** function be used directly from the CODESYS Modbus Server configuration, or is this not supported? Help me Thanks very much. ---
**Author:** ![AdamReeve](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/adamreeve/32/59_2.png) [@AdamReeve](https://www.wago.community/u/AdamReeve)\ **Post date:** [September 24, 2026, 7:44pm UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/4 "2026-09-24T19:44:49Z")
The Modbus configuration registers are for handling the communication watchdog and reading the number and type of attached modules. They won’t help you with setting configuration values of the 750-469/003-000 module. I believe you will need to use WAGO-IO-Check for this. ---
**Author:** ![Thruser](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@Thruser](https://www.wago.community/u/Thruser)\ **Post date:** [September 25, 2026, 6:28am UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/5 "2026-09-25T06:28:30Z")
Hi, here is a WAGO Video tutorial for mapping remote modules with modbus: [![](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/f/fa68f41230b8765dca1402bc0e248354aaa2fd2f.jpeg "Modbus in CODESYS 3.5 | Capture all modules in an array using Function Code 23") ](https://www.youtube.com/watch?v=h6HE4GIantw) and here a tutorial to implement remote complex modules using the mentioned WagoSysFiledbusModule library: [![](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/7/7401714ccff8b1914e84b7e4bd0ce5ceca9eb7d6.jpeg "WagoSysFieldbusModule | Commissioning complex modules on a fieldbus coupler") ](https://www.youtube.com/watch?v=izEoxbqc5YM) The functions for configuring the module are available when you are using the fb for this module. The documentation for the configure functions you will find in the WagoSysModule\_75x\_469 library @AdamReeve what version of the libray do you use? 1.9.4.5 shows me GetNewPaOutputs and SetNewPa Inputs ---
**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://www.wago.community/u/lorenzo)\ **Post date:** [September 25, 2026, 9:07am UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/6 "2026-09-25T09:07:40Z")
Thanks a lot, that’s great news. I will review and analyze the video. I am using CODESYS 22.2 with WagoSysModule\_75x\_469 version 1.9.9.0. Regards ---
**Author:** ![AdamReeve](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/adamreeve/32/59_2.png) [@AdamReeve](https://www.wago.community/u/AdamReeve)\ **Post date:** [September 25, 2026, 12:54pm UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/7 "2026-09-25T12:54:01Z")
> [@Thruser](#): > > @AdamReeve what version of the libray do you use? 1.9.4.5 shows me GetNewPaOutputs and SetNewPa Inputs The problem is that the Modbus Process Image Output size for the 469 module is zero. Even if the WagoSysModule ↔ WagoSysFieldbusModule exchange could work, there are no Modbus Registers in the coupler that you can use for a write channel to the 469 module. ---
**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://www.wago.community/u/lorenzo)\ **Post date:** [September 25, 2026, 1:38pm UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/8 "2026-09-25T13:38:30Z")
I am currently testing this and I have encountered the following issue. Sorry, I’m new to the WAGO ecosystem. On the 362 coupler, I also need to add an IO-Link master. Is this the recommended way to pass parameters to the different devices? ---
**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://www.wago.community/u/lorenzo)\ **Post date:** [September 25, 2026, 3:02pm UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/9 "2026-09-25T15:02:50Z")
![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/4/436d81daf3ecdc3a40371ae9240cd36766d69a2c.png) I tried to compile the project, but I keep getting compilation errors related to the library. Has anyone else experienced this? ---
**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://www.wago.community/u/lorenzo)\ **Post date:** [September 26, 2026, 11:33am UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/10 "2026-09-26T11:33:42Z")
Sorry, I have resolved the compilation issue. I am using version 22.2, and some libraries were incompatible. I downloaded the correct libraries, and the compilation completed successfully. Best regards ---
**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://www.wago.community/u/lorenzo)\ **Post date:** [September 28, 2026, 6:12am UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/11 "2026-09-28T06:12:39Z")
![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/f/f7d4d929c4bb6fa38f81916ed8ebe2f43d69da1e.png) Hello, I tried reading the configuration, but it doesn’t work. It still seems strange that “FBModule\_75x-469” is included in “WagoSysFieldbusModule” if it cannot actually be used. Does anyone have any ideas? I will now try using the “IO-Link Master” module via Modbus. Hopefully, it will work without any issues. Thanks. ---
**Author:** ![Thruser](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@Thruser](https://www.wago.community/u/Thruser)\ **Post date:** [September 28, 2026, 7:40am UTC](https://www.wago.community/t/modbus-750-460-configuration-by-codesys/2889/12 "2026-09-28T07:40:47Z")
Hi, unfortunately the modbus coupler maps only the input data of the module, not the output for communicating with the module. This is, what Adam meant with his posts. You can use this functions only when the module is directly attached to the PFC.