Edge2Cloud (E2C) is a collection of software applications that can run within Robustel’s “RobustOS” operating system to provide IoT Gateway functionality at both a hardware and software level. For many years, Robustel have been writing custom applications to help connect legacy industrial protocols (eg Modbus) and equipment to application servers in the cloud and E2C is a ‘root and branch’ attempt to formalize that capability saving customers time and cost when developing new applications.
The most common example of this at the time of writing (2021) is the requirement to move Modbus (RTU or TCP) data from the edge to cloud services such as MS Azure and Amazon AWS. E2C provides a framework to make such requirements easy to implement in Robustel’s gateways.
1 – Connect Industrial devices (Modbus/OPC UA/Siemens S7 etc.) to the Cloud with zero edge software effort
2 – Simple to implement and low-cost solution can replace an additional Embedded PC and reduce Panel size leading to significant cost-savings!
3 – When used in R1520G gateway, the customer gets a globally certified solution in a single box – no need for regional variants
4 – E2C runs in Robustel’s R152X low cost “Lite Industrial” range providing customers with a very cost-effective solution for high volume deployments
5 – E2C allows a single Gateway to capture and concentrate multiple different industrial protocols over a single connection to the cloud
6 – E2C runs within the Linux based “RobustOS” operating system – an environment written and managed exclusively by Robustel providing excellent tech support and customization capability
E2C comprises 3 layers of software that run on a Robustel Gateway.
The diagram below highlights the fundamental structure of E2C with the “Southbound” app responsible for interfacing with industrial protocols/sensors over RS232, RS485, Bluetooth, Ethernet, etc., and the “Northbound” app responsible for transmitting data to Cloud services/Protocols as required by the customer application.
In between Northbound and Southbound app is the “Broker” which decouples the two interfaces and provides a generalized “any to any” transmission path for disparate types of data and destinations. The Broker in this instance should not be confused with a typical MQTT Broker used elsewhere in the solution architecture.