Configuring WAGO 750-469 Type J Behind a 750-362 Coupler

A 750-469/0003-000 thermocouple module behind a 750-362 Modbus coupler cannot be switched to Type J from CODESYS code on the PFC300 (FW31). The Modbus path carries only the module's measured input data, not its parameters. Set the sensor type once with WAGO-IO-Check. The module then linearizes as Type J, and the PFC300 keeps polling the same input words it already reads.

Where does a Type J change request stop between the PFC300 and the 750-469?

Follow a write request from the CODESYS application to the module. The PFC300 acts as the Modbus client and the coupler acts as the server. Behind the coupler, each module on the internal K-bus contributes words to the coupler's process image. The Modbus client can only reach what the coupler exposes in that image and in its own configuration registers.

The request stops at hop 3. Nothing in the coupler's Modbus address space forwards into the module's parameter registers.

Part numbers in circulation for this setup vary. The same job is sometimes described with a 750-460 module or a 750-363 coupler. Read the actual module list from the coupler before acting on any of the checks below. The coupler's configuration registers report the number and type of attached modules, so a single Modbus read settles which hardware is on the rail.

Check 1: Is the 750-469 on the controller's local K-bus or behind the coupler?

The reading here is the physical location of the module. Check the rail, and cross-check it against the module list the coupler returns.

• If the module sits on the controller's own local I/O bus, the runtime has direct register access to it. The FbModule_75x_469 function block in the WagoSysModule_75x_469 library can read and write the module's configuration from the application, including the sensor type. Use that block and stop here.
• If the module sits behind the 750-362, the local-bus function block has no route to it. Go to Check 2.

Before you plan a redesign around the local block, confirm from the controller documentation that your controller variant has a local K-bus. Some controllers reach all of their I/O through remote couplers.

Check 2: Does the coupler's Modbus image give the 750-469 an output channel?

Parameter access on 750-series modules uses register communication. The master writes a control byte and a register number or value through the module's output image. The module answers through its input image with a status byte. A module with no output words in the mapped process image has no way to receive that handshake.

For configurable modules reached through a fieldbus coupler, the WagoSysFieldbusModule library creates a module instance that application libraries can drive. Examples include power measurement through WagoAppPowerMeasurement, and serial or CAN gateways through WagoAppCom. Those modules expose output data, so the library can tunnel register traffic through the coupler.

The WagoSysFieldbusModule function block for the 750-469 defines input data only. Take these readings to confirm it on your node:

1. Instantiate the 750-469 type from WagoSysFieldbusModule and inspect its interface. You will find input words and no output words.
2. Compare the coupler's reported process image. The module adds to the input area and adds nothing to the output area.

If both readings show inputs only, there is no in-band configuration path. Go to Check 3 to rule out the coupler-level registers.

Check 3: Can the Modbus configuration registers or Modbus init writes reach the module?

This is the usual next idea: write the coupler's Modbus configuration registers, or put the write in the CODESYS Modbus device's initialization list so it runs at connect time. Both land in the same place, which is the coupler's own register space.

An init write is not a separate channel. It is the same Modbus write issued once at startup, so it cannot reach a register the coupler does not map. This check resolves the question. Configure the module offline with WAGO-IO-Check.

Do not work around the problem by reading the channel under a different thermocouple type and converting the result to Type J in software. The module applies its own linearization and cold-junction compensation for the configured type. Undoing that in the PLC stacks the error of the wrong curve on top of the compensation error, across the whole range.

How do you set Type J on the 750-469 with WAGO-IO-Check?

1. Put the process that depends on this node into a safe state. While IO-Check holds the coupler, the Modbus data the PFC300 sees can freeze or drop, and the coupler's communication watchdog can trip.
2. Connect WAGO-IO-Check to the 750-362, using the service interface or the network connection your IO-Check version supports for this coupler.
3. Read the node configuration. Confirm that the module list matches the rail and that the 750-469/0003-000 appears in the expected slot.
4. Open the settings dialog for the 750-469. For each channel wired to a J thermocouple, set the sensor type to Type J. Leave any unused or differently wired channel at its correct type.
5. Write the parameters to the module. The settings persist in the module and do not live in the coupler or the PLC project.
6. Disconnect IO-Check, release the coupler to Modbus, and restore the PFC300 application.
7. Record the per-channel sensor type on the commissioning sheet and on the spare-parts label. A replacement module arrives with its own factory settings, and the PFC300 has no way to detect or correct that over Modbus.

How do you prove the channel now reads as Type J over Modbus?

1. Power-cycle the coupler and the module. The setting has to survive a restart, because nothing on the Modbus side rewrites it.
2. Confirm that the PFC300's Modbus client reconnects and that the coupler's watchdog is not in a tripped state.
3. Check the channel status bits in the input image for wire-break or range errors on each Type J channel.
4. Inject a known value with a thermocouple calibrator set to Type J, or place the sensor at a reference temperature. Compare the reading in CODESYS against the reference at two or more points across the working range. A wrong type shows up as a deviation that grows with temperature, not as a constant offset.
5. Leave the reference at the upper test point and trend the value in CODESYS for several minutes. A stable reading within the module's specified accuracy, taken from the datasheet, closes the job.

FAQ