Deploying the AVEVA Edge Data Store (EDS) on a WAGO PFC300 using Docker

[Jacob]

The AVEVA Edge Data Store (EDS) stores data locally in configurable data storage until it can be sent to permanent storage in a PI System and/or in CONNECT Data services through periodic egress.

Thanks to its 64-bit dual-core processor and 2GB RAM, WAGO’s highly flexible PFC300 removes the need for a separate edge device. The PFC300 allows data to be stored locally at the control level and sent directly to AVEVA CONNECT Data Services and/or the PI System. The PFC300 has enough performance to run both EDS and large CODESYS 3.5 control programs at the same time. The PFC300 is a part of the WAGO 750-series PLC family which offers more than 250 unique I/O modules to choose from.

In my application I used the EDS Built-in OPC UA connectivity. However, EDS can collect data using any of the additional methods: Built-in Modbus TCP connectivity, Custom application using Open Message Format (OMF), Custom application using REST API.

WAGO + EDS Application Overview:

1. CODESYS 3.5 runs the control program on the PFC300 and publishes selected variables to the controller’s built-in OPC UA server making them available over the localhost network.
2. The OPC UA adapter within EDS connects to the OPC UA server and ingests selected variables using parameters defined in the .json configuration file.
3. EDS stores the ingested data locally, and reliably forwards it to PI and/or CONNECT, creating a fully containerized, real-time data pipeline directly from the PLC.
4. Once the data is in AVEVA Data Services it can be visualized or analyzed using the many AVEVA CONNECT services.

The EDS .json file defines:

• The egress targets, including AVEVA PI Server and CONNECT Data Services, with authentication credentials and endpoint URLs.
• Which OPC UA node IDs (variables) to monitor and ingest.
• The local buffering behavior, ensuring data is retained during network loss.
• The schedule and frequency at which data is forwarded to each destination.
• Stream prefixes, namespaces, and filtering rules for organized and efficient data handling.

To learn more about the AVEVA Edge Data Store please refer to their Document website.