A shared operational edge platform that turns fragmented OT data into usable operational outcomes
In one sentence: E2C Trinity is a shared operational edge platform running on compatible Robustel gateways. It provides one engineering model for field data acquisition, edge processing, continuity, visualisation, integration and control, helping customers unlock existing operational data without replacing proven PLC, SCADA, BMS or cloud systems. |
1. Why E2C Trinity exists
Industrial, infrastructure and building environments combine equipment from different vendors, eras and protocols. Valuable data remains trapped in PLCs, controllers, sensors, meters and isolated applications. Connecting legacy OT directly to enterprise or cloud systems can add reliability, security and maintenance risk. The real constraint is not a lack of data, but the absence of a consistent way to collect, contextualise, preserve, visualise and integrate it.
2. Positioning and boundaries
E2C Trinity is | E2C Trinity is not |
An operational edge software layer between field assets, operational systems and business applications. | A rip-and-replace replacement for PLC, SCADA, MES, ERP, BMS or cloud platforms. |
A local platform for acquisition, filtering, logic, buffering, alarms, visualisation and protocol bridging. | A lightweight application limited to protocol conversion and cloud forwarding. |
A shared runtime and integration architecture for E2C Factory and E2C Field. | A deterministic PLC, SIS or safety control system. |
3. The shared 6C capabilities
Capability | Problem addressed | Customer outcome |
Collect | Mixed-vendor devices and protocols remain isolated. | A consistent and scalable field-data foundation. |
Compute | Raw data depends on the cloud for transformation or action. | Rules, Node-RED, scripts and applications process data locally. |
Continuity | Network outages interrupt data flows. | Local storage and store-and-forward preserve data integrity. |
Canvas | Operators lack local status, trend and alarm visibility. | Edge SCADA, dashboards and historical trends. |
Connect | OT data is difficult to deliver to operational and business systems. | Standards-based OT, IT and cloud integration. |
Control | Monitoring and response are disconnected. | Governed local workflows and bidirectional interaction. |
4. Two purpose-built applications
Application | Best-fit environment | Distinctive focus |
E2C Factory | Manufacturing, machine OEMs, process industry and automation | Broad industrial protocols, Edge SCADA, OEE and operational data modelling. |
E2C Field | Distributed infrastructure, LoRaWAN and remote assets | Embedded LNS, rapid mixed-sensor onboarding and wired/wireless integration. |
5. Customer value
- Reduce repeated engineering with a consistent runtime, configuration method and integration model.
- Turn raw data into usable information at the edge and improve local response.
- Maintain collection, storage, alarms and local logic during unreliable connectivity.
- Move from device connectivity to visible, actionable, integrated and controllable operations.
6. Recommended reading order
Stage | Read first | Expected outcome | Reference Articles |
10 minutes | This overview and the Factory or Field overview | Identify the right application and project boundary. | This overview article |
10 minutes | Product Version Overview and the relevant Version Comparison | Confirm region, edition, tag capacity and feature differences. | |
30–60 minutes | The relevant Quick Start or first How-to | Complete an acquisition-to-forwarding, alarm or control workflow. | |
Solution design | Software Manual Overview | Software Manual | |
Collect Data | Modbus TCP for example | ||
Transmit Data | Northbound Protocols, MQTT for example | ||
Build a Dashboard | Web SCADA | ||
Before go-live | APP Download, Release Notes and compatibility information | Verify gateway, firmware, application, memory and licence. | |
License Activation | License Activation |
7. Project-start checklist
- List all assets, protocols, tag counts and read/write needs.
- Confirm which systems will use the data: operators, SCADA/BMS, MES/ERP, cloud or maintenance teams.
- Test with representative devices first, then turn the proven setup into a reusable template.
- Review any remote write or control function separately for safety, security and approval.
8. E2C Factory and E2C Field comparison
Dimension | E2C Factory | E2C Field |
Positioning | Operational edge platform for industrial automation and manufacturing environments. | Operational edge platform for LoRaWAN and distributed infrastructure. |
Typical assets | PLCs, machines, controllers, robots, meters and production lines. | LoRaWAN sensors, RTUs, smart meters, pump stations, remote equipment and building controllers. |
Primary problem | Brownfield integration, mixed-vendor data, OT/IT integration, local visibility and production performance. | Remote visibility, fewer site visits, wired/wireless integration and consistent deployment at scale. |
Distinctive capability | Broad PLC and industrial drivers, private protocols, Edge SCADA, data management and OEE. | Embedded LoRaWAN Network Server, device codecs, rapid mixed-sensor onboarding and remote lifecycle operations. |
Typical hardware | EG3120e, EG5120, EG5200 | LG3120e |
International capacity | Free: 200 tags; Core: up to 2,000; Pro: up to 5,000 with OEE. | Free: 100 tags; Core: up to 2,000; Pro: up to 5,000 with SCADA. |
Local visualisation | Supported in Free, Core and Pro. | SCADA is supported only in the Pro edition. |
Choose first when | The customer leads with PLCs, machines, lines, SCADA, MES, OEE or industrial brownfield modernisation. | The customer leads with LoRaWAN, remote sites, wireless sensors, truck rolls or multi-site scaling. |
Selection tip: Select E2C Field for projects that need to connect LoRaWAN devices, and select E2C Factory for projects mainly involving PLCs or other industrial protocols. The two applications can be used together in the same project when different device types need to be integrated. |
9. Protocol and system-integration matrix
The following lists are based on the confirmed E2C Factory and E2C Field protocol matrices. Verify the final project against the applicable hardware, application, firmware and edition.
E2C Factory built-in protocol list
Southbound protocols connect field assets. Northbound interfaces deliver standardised data to cloud platforms or forward it to systems such as SCADA, MES and BMS.
Type | Category | Protocols |
Southbound | General Protocols | Modbus TCP, Modbus RTU, OPC UA, Full DLT645 series (DLT645-2007, DLT645-2007 OverTcp, DLT645-1997 overTCP, DLT645-1997), Full DLT698 series (DLT698, DLT698TcpNet, DLT698OverTcp), CJT188-2004, DI/DO/AI, BACnet IP, BACnet MS/TP |
Siemens | S7, FetchWrite, PPI, PPIOverTcp, WebApi | |
MITSUBISHI | FxLinks, FxLinksOverTcp, FxSerial, FxSerialOverTcp | |
Omron | Fins-Tcp, Fins-UDP, HostLink, HostLinkOverTcp, CMode, CmodeOverTcp, CipNet, ConnectedCipNet | |
Allen-Bradley | ConnectedCIP, CIP, MicroCIP, SLC, PCCC | |
Delta | Serial, SerialAscii, TCP, SerialOverTcp | |
XinJE | Serial, SerialOverTcp, Modbus TCP, Private TCP | |
Keyence | MC3E, Nano, NanoOverTcp | |
Inovance | Serial, TCP, SerialOverTcp | |
Panasonic | MC3E, Mewtocol, MewtocolOverTcp | |
Fuji | SPB, SPBOverTcp, SPHNet | |
FATEK | Program Port, Program Port over TCP | |
Beckhoff | ADS | |
Vigor | Serial, SerialOverTcp | |
Yokogawa | LinkTcp | |
Northbound | Data to Cloud | MQTT (TLS encryption, compatible with AWS IoT, Azure IoT and mainstream IoT platforms), HTTPS/RESTful, Sparkplug B |
Data Forwarding | Modbus TCP Slave, BACnet/IP Server, OPC UA Server |
E2C Field built-in protocol list
E2C Field combines LoRaWAN, industrial protocols and building protocols on one platform, then connects cloud and operational systems through standard northbound interfaces.
Type | Category | Protocols |
Southbound | General Protocols | LoRaWAN, Modbus TCP, Modbus RTU, OPC UA, DI/DO, BACnet IP, BACnet MS/TP |
Northbound | Data to Cloud | MQTT (TLS encryption, compatible with AWS IoT, Azure IoT and mainstream IoT platforms), HTTPS/RESTful, Sparkplug B |
Data Forwarding | Modbus TCP Slave, BACnet/IP Server, OPC UA Server |
10. Quick functional preview
A first-time user does not need to read the full manual before seeing value. Use one representative device and complete the following minimum end-to-end workflow to understand the main E2C Trinity operating model.
Preview step | Function to try | Expected result | Application |
1. Connect an asset | Create a device, select a protocol, configure connection parameters and tags, then publish. | Stable live field values appear on the tag page. | Factory / Field |
2. Organise data | Create a group or data table and define periodic/change reporting, calculated fields and retention. | Discrete tags become usable operational information. | Factory / Field |
3. Connect a destination | Configure MQTT, HTTP or a forwarding service and run a connection test. | SCADA, BMS, MES or cloud receives standardised data. | Factory / Field |
4. Add local logic and alarms | Configure thresholds, severity and recipients; build a simple Scenario or Node-RED flow. | An abnormal condition triggers immediate local action or notification. | Factory / Field |
5. Test continuity | Disconnect the WAN while acquisition continues, then restore connectivity. | Critical data is buffered and forwarded after recovery. | Factory / Field |
6. Visualise operations | Create a live screen, trend, alarm component and governed operator action. | A browser provides a local operational view. | Factory; Field (Pro only) |
7. Try the distinctive feature | Factory: configure OEE. Field: configure the LNS, import a codec and onboard mixed sensors. | The application-specific value is demonstrated. | Factory / Field |
8. Reuse the configuration | Export a configuration or template and import it to a second gateway. | The design proves repeatable and scalable. | Factory / Field |