Aller au contenu principal

Edge Runtime overview

The Edge Runtime runs on a factory host between Ennea and your machines. It caches assigned work centers and executable orders, connects to configured OPC UA servers, buffers outgoing events in SQLite, and exposes local PLC interfaces.

Ennea cloud ← HTTPS / WebSocket → Edge host ← factory network → PLCs
                                 SQLite cache and event buffer

What it does​

  • Registers a connector in a fixed organization/site/environment and requires cloud approval.
  • Authenticates a scoped service identity and synchronizes assigned resources.
  • Reads configured OPC UA nodes and writes supported order values to machines.
  • Offers local REST and OPC UA methods for PLC-side order/recipe reads and reporting.
  • Processes supported label-print jobs through configured printer targets.

Registration, cloud connectivity, PLC connectivity, and successful event application are separate checks. A green local health response does not establish the other three.

Prerequisites​

An administrator must provision the connector and service permissions, assign work centers, and arrange the required cloud and factory-network access. The host needs the supplied runtime package, Node.js 24 for a source installation, persistent writable storage, and a deployment-specific network/security configuration. See Installation and Security.

Offline behavior and limits​

SQLite stores cached data and buffered events. The current default maximum buffer age is 72 hours; events can enter a dead-letter state after repeated failures. Disk exhaustion, expired credentials, invalid identifiers, unsupported event mappings, and conflicts can prevent application. This is not a guarantee of lossless or indefinitely offline operation.

The cache can be stale while disconnected. Cloud order synchronization selects released and in-progress work for assigned work centers. Verify recovery with a representative order and counter before relying on it for a production process.

Some older examples describe capabilities broader than the implemented path. Generic production subscriptions currently lack a populated order number; scrap, station-progress, and custom machine behaviors must be checked through the exact deployed interface. Do not assume a configured node automatically updates every corresponding Ennea record.

First successful connection​

Follow Installation, configure OPC UA mappings, and verify a read-only machine value first. Then perform a small authorized event test and confirm the intended cloud record and receipt. Use the API reference for payload semantics and Troubleshooting for failure isolation.