# OMRON FINS stop timeout error spam

**URL:** <https://discourse.nodered.org/t/omron-fins-stop-timeout-error-spam/47520>\
**Category:** Industrial\
**Created:** [23 June 2021 09:32 UTC](https://discourse.nodered.org/t/omron-fins-stop-timeout-error-spam/47520 "2021-06-23T09:32:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JoshuaG](https://avatars.discourse-cdn.com/v4/letter/j/edb3f5/32.png) [@JoshuaG](https://discourse.nodered.org/u/JoshuaG)\
**Post date:** [23 June 2021 09:32 UTC](https://discourse.nodered.org/t/omron-fins-stop-timeout-error-spam/47520/1 "2021-06-23T09:32:42Z")

</div>

As the topic says.  
Quite regularly we'll get a Isolation on the machine and the spam of timeout logs that hit the console brings my node to a halt. Is there any way of turning this off?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [23 June 2021 11:51 UTC](https://discourse.nodered.org/t/omron-fins-stop-timeout-error-spam/47520/2 "2021-06-23T11:51:11Z")

</div>

> [@JoshuaG](#):
>
> Is there any way of turning this off

You can catch it  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/f/1fe20abb9cc45894c3d5862f6d9220699415411d.png)

A better solution is to reduce poll rate when you catch an error instead of continuously hammering the node. You can recognise this scenario by the context of the catch. Once you get a good read, revert to full speed polling.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 August 2021 11:52 UTC](https://discourse.nodered.org/t/omron-fins-stop-timeout-error-spam/47520/3 "2021-08-22T11:52:08Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.