Groov Rio inputs are slow to update in Node Red

I have a pushbutton as an input on a Groov RIO, configured as a Switch Input, Powered Digital Input, which is being read by node red. There is a delay, and the button has to be held for the press to be registered. I’ve changed the input type to latch on, which helps, but there is still a noticeable delay before action takes place.

If I had to wager, I’d say there is a scan time schedule in which the nodes read from the RIO.

Is there a way to speed up the read time into node red?

1 Like

Hi Scott. Welcome to the OptoForums.

Yes. By default the Node-RED scan rate is 1 second.
Is that the sort of delay you are seeing?
If its longer than 1 second, then I’d like to see a screenshot of the way you have things hooked up.
The latch should mean you can just hit the button and the flow takes it from there.

Thank you, I’m happy to be here.

Yep, that seems about right.

The button turns on a light and changes text on a marquee. The feel of it is off, akin to walking into a room and turning on a light switch, and waiting for a second for it to come on.

Is there a way to increase that scan rate from default?

Depends on what node you are using.

Are you using an inject node?

EDIT: Screenshot to explain the two methods / nodes.

AAhhhh. Yes I was using the groov i/o input.

Thank you for updating with the picture. That was very helpful.

1 Like

No problem I would not go quicker than 150 msec. In fact, if you can live with 250msec, that would be better still. Its a RESTful call each scan and so there is some processing time involved.
Also be mindful if you have a lot of these (well, 8 in the case of a RIO).
If you end up with more than 3 inputs scanned at this rate come back with a post and we can look at some other options.

2 Likes