Opto 22 Groov Rio Input- Ignition, Tag value Change for counter

Hi there, I am currently setting up a Opto 22 Groov Rio Universal I/O Unit. I have already pulled in several analogue inputs and had no issues. However, when pulling through 2x 24vDC Digital Inputs, Ignition doesn’t always register its change as a Boolean value. Therefore the signal value change is only being registered 40% of the time on Ignition ( Not ideal as these values are for product counters). I am able to see this issue, because you can see the input value changing on the Groov Manage Software. Is there a way of bypassing/ not having to set these up as tags and pulling directly from the OPC. If so, would this improve things or furthermore, is there a better way of doing it, as the count accuracies are pretty important. Any help would be appreciated, as I am relatively new to this. Thanks in advance.

How fast is the counter pulse? OPC events are polling at 1000ms from memory, so if your counter pulse is shorter than that, it will be missed some of the time.
Normally you would put product counters with pulses in a PLC and just read the counter value from Ignition. SCADA is not a real time platform, so do all your real time work on a PLC, then do the number crunching and storage on SCADA.

If you are using 8.3, you could use an event stream with MQTT to process these items as events not tags. This will queue up the events as they happen and also guarantee processing.

1 Like

Hi David, the signal value changes roughly every 15 seconds, however the pulse is only momentary, so that would make sense. I will have a look at setting it up as a counter on the Groov Manage software. We are currently still using version 8.1.43 for igntition. Thanks for your help.

The other option is to just delay the pulse turning off for 1.1 seconds, or also set the bit in the EPIC then reset it from ignition.

This is your best bet - I’m pretty sure the DI on the RIO offers the ability to have an “On” Counter. Let the RIO handle the high speed work, and just pull in the count.

Pulling in the count also covers situations where comms are lost or the gateway needs to be restarted. Consider using a never-resetting counter if the PLC has retentive count values. Log that and you can get the difference for any date range very simply.