# Errors in MODBUS RTU communication

**URL:** <https://discourse.nodered.org/t/errors-in-modbus-rtu-communication/66255>\
**Category:** Industrial\
**Tags:** modbus\
**Created:** [9 August 2022 23:12 UTC](https://discourse.nodered.org/t/errors-in-modbus-rtu-communication/66255 "2022-08-09T23:12:54Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [15 August 2022 10:22 UTC](https://discourse.nodered.org/t/errors-in-modbus-rtu-communication/66255/28 "2022-08-15T10:22:08Z")

</div>

> [@rob2](#):
>
> All stays working fine now till one (or more) of the meters does not react (I shut one and two down to test it). In that case the chains stops till the meter(s) starts reacting again.

yes .. by default the Modbus nodes dont output a msg when they fail to poll a device.  
Unless you enable that option. (See the flow i shared above)

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/1/d134e024193cbd5e6ceba6622368b374d6ef4bb6.png)

This will trigger the next Modbus node in the chain.  
But i also used a Function node to filter those fails and handle them differently and not send them to buffer-parser.

> [@rob2](#):
>
> I saw no errors at all,

Have you enabled the options ?

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/0/004a575b084ac2e61369457734500768b6ad4bbe.png)

---

_[View the full topic](https://discourse.nodered.org/t/errors-in-modbus-rtu-communication/66255)._
