# Modbus reading
**URL:** https://discuss.saleae.com/t/modbus-reading/3610
**Category:** Logic 2 Software
**Created:** [January 14, 2026, 11:31am UTC](https://discuss.saleae.com/t/modbus-reading/3610 "2026-01-14T11:31:04Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@giampieroferrotti](https://discuss.saleae.com/u/giampieroferrotti)
#### Post date: [January 14, 2026, 11:31am UTC](https://discuss.saleae.com/t/modbus-reading/3610/1 "2026-01-14T11:31:04Z")
I needs read code modbus but I didn’t understand how to do it, whereas in async serial I managed to read the values sent and received by the Modbus server and client.
---
### Author:  [@timreyes](https://discuss.saleae.com/u/timreyes)
#### Post date: [January 17, 2026, 12:17am UTC](https://discuss.saleae.com/t/modbus-reading/3610/2 "2026-01-17T00:17:10Z")
@giampieroferrotti I’m glad to hear you were able to decode data using the Async Serial analyzer as a workaround!
First, can you help confirm if both Master and Slave communications are sharing a single data line? If so, this mode of operation is currently not supported by our built-in Modbus analyzer. We’re tracking this request here at the moment:
>
>
> Specifically, we should have a combined mode, called "Modbus/RTU - Master & Slav…e", which auto-detects the messages on a single data line as either Master or Slave. Modbus can have both Master & Slave messages on a single line.
>
> The simplest solution is to try both decodings modes (master and slave) for each decoded frame (single blue decoded box) – the correct one for is the one with a valid Checksum.
Otherwise, if you are attempting to decode any of the following Modbus modes in the image below, feel free to share your .sal capture file with me and we can take a closer look!
