Robust handling of missing messages with retry

I don't have a lot experience with Modbus, so bear with me. When using modbus flex-getter, if anything fails, the message disappears - no output. And yes, I have enabled warning and error checkboxes to no avail.

Not sure what the root cause is, as I'm left blind without any output. How about a retry mechanism with a delay of x seconds? Is there any ready-made examples of this in node red? Doesn't need to be related to modbus in particular, but a general purpose way of handling missing messages.

I'm playing around with function nodes to make duplicate message, send it around the faulty node, then join after.

did you try adding a catch node pointed at the failing node?

1 Like

Thanks, it felt like I had forgotten something. And after a few attempts, yes indeed errors goes to catch - brilliant!

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