Collect and Publish Data the Way You Want
groov RIO is edge I/O for the IIoT: standalone industrial I/O that collects and securely publishes data from field to cloud.
Place groov RIO near the sensors and equipment that have the data you need, and wire them up.
Configure I/O channels from any computer or mobile device using the web-based configuration software, groov Manage. groov RIO immediately begins making data available.
groov Manage is your central command to your groov RIO, helping you configure and troubleshoot I/O, security, and communications.
- Configure I/O (discrete and analog).
- Configure networking and device firewall, including a VPN client.
- Set up security and user accounts, including LDAP management (groov RIO firmware 3.0 or higher).
- On groov RIO universal I/O models, set up and tune PID control loops (requires groov RIO firmware 3.0 or higher).
- See I/O specs and wiring diagrams.
- Check I/O status and values.
- Enable Data Service protocols, including the native OPC UA server and MQTT for efficient data communications.
- Access other software: Node-RED, Ignition Edge on groov RIO MM2.
Use the data
And now, where do you want to use the data? You don’t need a PLC or PC or middleware to store it or move it where you want it to go. groov RIO handles all that, because it speaks the protocols used by IT as well as OT networks. See how groov RIO fits in your system architecture.
RIO’s embedded software can store data locally and share it with:
- On-premises and cloud-based software, like Canary historian, SQL databases, and Ignition SCADA from Inductive Automation®, plus cloud services like AWS, Microsoft Azure, and IBM Cloud
- HMIs, including Ignition and Opto 22’s groov View, on computers and mobile devices
- Other devices on your OT network
Node-RED data flows
Create simple data flows with groov RIO’s built-in Node-RED editor and runtime to store data locally and send data to cloud services, databases, other I/O devices, and APIs.
With Node-RED’s programming environment, you have the freedom to create the flows you like using any nodes you choose. You can even develop simple user interfaces (UIs) with Node-RED UI nodes and serve them directly from groov
RIO to any mobile or web-based device.
MQTT for efficient communications
Configure and enable MQTT
RIO to securely send data—as Sparkplug B or string payloads—to MQTT brokers on premises or in the cloud.
MQTT publish-subscribe communications
offer three main advantages over request-response for IIoT applications:
- Network efficiency. Network traffic is reduced overall, because data is published and sent only when it changes, rather than at regular intervals.
- Better field connections. Because the broker is a central source for data, multiple connections to field devices are not necessary. And even remote groov RIOs with intermittent connections or low bandwidth can publish or subscribe to data.
- Improved security. Data is published using an outbound connection. Most firewalls block inbound traffic (for example, an external client requesting data from an internal server), but they allow outbound connections—connections initiated by groov RIO. Once initiated, data can travel in both directions.
Custom software using SSH
With the addition of a free GROOV-LIC-SSH license, you can even gain secure shell access to the groov RIO's Linux operating system and create custom applications to run on the edge I/O module (requires groov RIO firmware 3.0 or higher).
Ignition Edge on RIO MM2
Yes! GRV-R7-MM2001-10 includes Ignition Edge from Inductive Automation. With a GROOV-LIC-EDGE8 you can run Ignition Edge on groov RIO and connect to Allen-Bradley®, Siemens®, and Modbus®/TCP devices via OPC UA.
OPC UA Server options
Use any of groov RIO's OPC UA Server options to communicate data with OPC UA clients:
- The groov RIO's built-in OPC UA server exposes I/O values, PID values, and Scratch Pad areas to clients.
- Downloadable OPC UA Server Node-RED nodes give access to Node-RED messages and flows.
- In the GRV-R7-MM2001-10, use Ignition Edge to access Ignition tags, including to any 3rd party device connections configured via Ignition's built-in drivers.
What data do you need to collect, and where will you publish it?