How abijith0/plc_scada_demo_mes works
This repository delivers a deployable Ignition SCADA/MES project for a tank-control process. The main workflow carries PLC tag data through Kepware OPC UA to the Ignition Gateway, where it supports the Perspective operator interface and exception-based MySQL historian logging; operator inputs are routed back toward the PLC. The README documents the project export’s contents and system connections, but no project source excerpts are available, so internal wiring beyond those documented relationships is omitted.
Main entry points: SmartFactory_MES_2026-02-22_1410.zip Ignition Gateway
Components 12
Field Control
- CODESYS PLC
- Kepware OPC UA
Supervisory Gateway
- Ignition Gateway
SmartFactory_MES_2026-02-22_1410.zip - Tag Configurations
SmartFactory_MES_2026-02-22_1410.zip
Operator Interface
- Perspective Client
SmartFactory_MES_2026-02-22_1410.zip - Operator Controls
SmartFactory_MES_2026-02-22_1410.zip - PV/CV Trends
SmartFactory_MES_2026-02-22_1410.zip - Level Alarms
SmartFactory_MES_2026-02-22_1410.zip - Operator Prompts
SmartFactory_MES_2026-02-22_1410.zip
Historian
- Historian Connections
SmartFactory_MES_2026-02-22_1410.zip - MySQL Historian
Other components
- Operator
Connections 12
- CODESYS PLC → Kepware OPC UA: sends tag data
- Kepware OPC UA → Ignition Gateway: OPC UA tags
- Ignition Gateway → Perspective Client: serves via HTTPS/WebSockets
- Operator → Perspective Client: uses
- Perspective Client → Operator Controls: accepts input
- Operator Controls → Ignition Gateway: sends operator values
- Ignition Gateway → CODESYS PLC: routes control
- Ignition Gateway → Historian Connections: routes tag data
- Historian Connections → MySQL Historian: exception logs
- Ignition Gateway → PV/CV Trends: provides PV/CV data
- Ignition Gateway → Level Alarms: provides level state
- Ignition Gateway → Operator Prompts: provides process state