Each one is a flow on the same canvas, built from nodes that ship today. The chips follow the editor’s colors: sources, processing nodes and sinks.
The MES or ERP posts a production order. The flow splits it into one job per printer, each printer loads its message and fills batch, dates and weights, and the caller gets an answer per printer. Every job is in the log afterwards.
Coding printersA host on the CNC network reads run state, axis positions, spindle data and alarms. Deadband and aggregation trim the stream at the edge, and the records leave through the signed push to OpexMX or any receiver that verifies it, or to NATS, ClickHouse or Postgres.
FOCAS runs on every build through the built-in client (beta, not yet tried on a real controller) or, on Windows and glibc Linux, through your own Fanuc library. MTConnect runs on any OS.
CNC adaptersA payment notification arrives signed by DOKU. The flow drops repeats, checks the event against its schema, and posts a journal entry to NetSuite, in read-only mode until cut-over. Both sides are tallied, and each day a report lists what only one side booked and what differs by more than your tolerance, with a CSV for finance.
ReconciliationThe same flows look different from the plant office, the integration desk and finance.
Something missing? Write to marketing@opexcg.com.
No. Coding printers are one node type among many. The same flow can read a PLC or a CNC, receive a signed payment notification, call NetSuite or another ERP, validate the event against a schema, and write to ClickHouse or Postgres.
Printers have their own page in the docs: nine protocols, production lines and a job log.
Run one binary, connect a PLC, a CNC or a webhook, and watch the records arrive in the editor.
Sizing questions or an air-gapped install? Email marketing@opexcg.com or read the quick start.