# How to read several slaves - Modbus RTU

**URL:** <https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859>\
**Category:** CODESYS\
**Created:** [August 26, 2026, 8:03am UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859 "2026-08-26T08:03:55Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![WagoUser44](https://avatars.discourse-cdn.com/v4/letter/w/7ba0ec/32.png) [@WagoUser44](https://www.wago.community/u/WagoUser44)\
**Post date:** [August 26, 2026, 8:03am UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859/1 "2026-08-26T08:03:55Z")

</div>

Hello,

How can I read from multiple slaves? I know how to do it for one slave, but how do you handle multiple slaves?

The setup for slave ID 1 is working fine, but I would also like to retrieve the values for IDs 5 and 10.

```auto

mySerialMaster : FbMbMasterSerial := ( xConnect := TRUE,
udiBaudrate := 9600,
usiDataBits := 8,
eParity := WagoTypesCom.eTTYParity.Odd,
eStopBits := WagoTypesCom.eTTYStopBits.Two,
eHandshake := WagoTypesCom.eTTYHandshake.None,
ePhysical := WagoTypesCom.eTTYPhysicalLayer.RS485_HalfDuplex,
eFrameType := eMbFrameType.RTU,
tTimeOut := T#3000MS
);

utQuery : typMbQuery := (
bUnitId := 1, // Address
bFunctionCode := 16#03, // FC3 = read input registers
uiReadAddress := 50770,
uiReadQuantity := 2,
uiWriteAddress := 0,
uiWriteQuantity := 0,
awWriteData := [124(0)]
);

xTxTrigger : BOOL; (* Set this variable once to start a job.
                                       This variable will be automatically reset by the master
                                       when the job is completed.
                                    *)

utResponse : typMbResponse; (* Once the job is done, you can find the result in this structure.
                                    *)

tonDelay : TON := (PT := T#50MS); // This is the silence time between two requests

```

```auto
//--- delay between two requests ----------------------
tonDelay( IN := (NOT tonDelay.Q) AND (NOT xTxTrigger));
xTxTrigger S= tonDelay.Q; // trigger the next request

//--- call the master cyclically --------------
mySerialMaster( I_Port := _750_652_x, // my serial port
utQuery := utQuery,
xTrigger := xTxTrigger,
utResponse := utResponse
);

```

Thank you for your help.

---

<div class="post-metadata">

**Author:** ![WagoUser44](https://avatars.discourse-cdn.com/v4/letter/w/7ba0ec/32.png) [@WagoUser44](https://www.wago.community/u/WagoUser44)\
**Post date:** [August 26, 2026, 10:04am UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859/2 "2026-08-26T10:04:36Z")

</div>

Another question: Is it possible to retrieve multiple registers from a single slave?

---

<div class="post-metadata">

**Author:** ![Thruser](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@Thruser](https://www.wago.community/u/Thruser)\
**Post date:** [August 26, 2026, 10:50am UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859/3 "2026-08-26T10:50:08Z")

</div>

1.1 Collect Write Data for Request 1  
1.2 Start Request 1  
1.3 Wait until Request 1 is done  
1.4 Move Read Data Request 1 to target variables  
2.1 Collect Write Data for Request 2  
2.2 Start Request 2  
2.3 Wait until Request 2 is done  
2.4 Move Read Data Request 2 to target variables  
3.1 Collect Write Data for Request 3  
3.2 Start Request 3  
3.3 Wait until Request 3 is done  
3.4 Move Read Data Request 3 to target variables  
.  
.  
.  
n.1 Collect Write Data for Request n  
n.2 Start Request n  
n.3 Wait until Request n is done  
n.4 Move Read Data Request n to target variables  
go back to 1

---

<div class="post-metadata">

**Author:** ![WagoUser44](https://avatars.discourse-cdn.com/v4/letter/w/7ba0ec/32.png) [@WagoUser44](https://www.wago.community/u/WagoUser44)\
**Post date:** [August 26, 2026, 11:21am UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859/4 "2026-08-26T11:21:04Z")

</div>

Thanks Thruser, do you happen to have a code example, please?

---

<div class="post-metadata">

**Author:** ![Thruser](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@Thruser](https://www.wago.community/u/Thruser)\
**Post date:** [August 26, 2026, 12:40pm UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859/5 "2026-08-26T12:40:42Z")

</div>

See [here](https://www.wago.community/t/modbustcp-wahrend-laufzeit-server-slave-hinzufugen-auslesen-schreiben/2470). A slightly different approach for .1 and .4 Steps

It is for Modbus TCP but you can easily adapt it to Modubs RTU function blocks.

---

<div class="post-metadata">

**Author:** ![WagoUser44](https://avatars.discourse-cdn.com/v4/letter/w/7ba0ec/32.png) [@WagoUser44](https://www.wago.community/u/WagoUser44)\
**Post date:** [August 26, 2026, 1:27pm UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859/6 "2026-08-26T13:27:08Z")

</div>

Noted, thanks 🙂

Have a great day

---

<div class="post-metadata">

**Author:** ![MatthewKim](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@MatthewKim](https://www.wago.community/u/MatthewKim)\
**Post date:** [September 7, 2026, 2:04am UTC](https://www.wago.community/t/how-to-read-several-slaves-modbus-rtu/2859/7 "2026-09-07T02:04:21Z")

</div>

For MODBUS RTUs rather than RS-485, I prefer the following method.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/4/4c6b00336710d7c0297bc39adc042054c51d0cc8.png)
