56kcloud/lamasar #120
Tracking: OPC UA connector for Hall B presses
Georges Roduit opened this issue on Oct 3, 2026 · 9 comments
Hall B runs twelve Engel presses with CC300 controls that expose an OPC UA server. Today their cycle data reaches Lamasar through a nightly CSV export, so the dashboards are a day behind.
This issue tracks the native connector: browse and subscribe to the press node tree, map tags to the machine model, survive network drops, and report its own health.
At risk: the certificate trust store took longer than planned and local buffering has not started.
Activity
Discussed with the Hall B team: they are fine with this approach.
Blocked on access to the staging plant network, asked IT.
Unblocked, the firewall rule is in place.
Added tests for the edge cases mentioned above.
Looks good to me, one comment on naming.
Moving this to the next iteration, the connector work comes first.
Demoed in the weekly, the plant manager liked it.
Picked this up, starting with the happy path.
Tried it against the simulator, works for the first three presses.