Everyone knows it’s all about the cloud—and the IIoT gateway is the critical component to getting all your real-world data to that cloud. And it matters. Without it, there’s no: big data, cloud computing, advanced analytics, AI, machine learning, and the list goes on… 

At Opto 22, we have a 50 year history of helping you collect and store real-world data. We know the cloud is where you want that data. So when we designed our sleek, rugged, industrial-grade I/O that lasts a lifetime, we also made them IIoT gateways.

What makes groov EPIC or RIO an IIoT gateway?

Let’s explore what an IIoT gateway does: gets real world sensor data (think: voltages, currents, pressures, flow rates, temperatures, frequencies, counts, and simple on/off statuses) and securely transmits them to the cloud. Our groov products have:

• Cloud connectivity: AWS, Snowflake, Microsoft Azure, IBM, and Ignition Cloud Edition are a few of the cloud computing platforms to which groov devices publish.
  
  
• Cybersecure communication: Using outbound communication with MQTT (Sparkplug 3.0 compliant) allows your groov device to pump data to the cloud without being vulnerable to inbound cyberattacks. Secure management with built-in VPN, configurable firewall, and LDAP for user authentication ensures approval from even the most restrictive IT department.
  
  
• Legacy compatibility: Onboard software packages like CODESYS, Ignition, and Node-Red provide drivers to widely used fieldbuses: EtherNet/IP, PROFINET, Modbus/TCP, EtherCAT, and even serial comms with CANbus, RS-232 and RS-485. 
  
  
• Plenty of I/O options: Grab groov RIO if you have a handful of sensors or groov EPIC for hundreds of sensors. For larger distributed systems, they also play nicely together. We support all the industry's popular signal and sensor types: 4-20 mA, 0-10 V^DC, AC/DC digital, thermocouples, RTDs, and more.
  
  

OK, groov, I’m listening. But will you work on MY IIoT architectures?

Global IoT Market Research Firm, IoT Analytics, defines four types of IIoT gateway architectures. Every architecture puts the IIoT gateway in a unique position. Here’s how groov devices fit into each one:

• Sensors/Devices > PLC/IPC > IIoT Gateway > Cloud:
  Challenge: Getting data from PLC/IPC that only uses legacy protocols.
  Solution: Convert old fieldbuses to modern interfaces like MQTT, OPC UA, and RESTful API using cutting-edge onboard software like Ignition, CODESYS, and Node-RED on your groov device.
  
  

• Sensor > I/O Module > IoT Gateway > Cloud:
  Challenge: Standalone I/O modules often use similar fieldbuses to PLCs (see above), but may even use serial communications.
  Solution: Add a groov EPIC serial module, or use an inexpensive serial-to-USB converter on your EPIC or RIO. Now your data can be securely pushed to the cloud.
  
  

• Sensor in Device > IoT Gateway > Cloud
  Challenge: Sensors inside of existing devices may be accessible via Ethernet or serial (see 1 and 2 above); however, oftentimes the data is trapped in the device.
  Solution: Throw a few sensors on there, and add an affordable groov RIO on top to avoid costly refits. I see this done ALL. THE. TIME.
  
  

• Sensors > IoT Gateway > Cloud
  Challenge: So many sensors will surely require a sophisticated and specialized IoT gateway.
  Solution: That’s right, but thankfully, the groov family of products has I/O and IIoT gateway covered in a single package.

So for every use case, groov has you covered

Interested in learning more about groov products? 

• groov RIO
• groov EPIC
• OptoU: Free Online Training
• Opto 22 Technology Partners
• OptoBlog

Keep calm,
groov on,
-Dan White