NexusVisionOrchestrator — the vendor-neutral hub between cameras, AI engines and PLCs.
NexusVisionOrchestrator is an on-premise .NET 8 platform that routes image-evaluation requests to any AI engine (Maddox Edge, Estek, CodingNexusVision, ONNX) and talks Siemens, Beckhoff and CODESYS PLCs natively over OPC UA / ADS / S7.
One hub, three jobs.
NexusVisionOrchestrator sits between three layers that traditionally couple too tightly. Cameras and triggers on one side — GigE Vision, USB3 Vision, file-watchers, trigger inputs from the line. AI engines on the other — multiple vendors at once, scored side-by-side, swapped in production without code changes. PLCs and downstream systems on the third — Siemens S7 via Sharp7, Beckhoff TwinCAT via ADS, anything OPC UA can reach. Recipes are designed visually in a Rete v2 flow editor; the same recipe runs in dev and prod.
The vendor-neutral position is the architectural choice that makes everything else possible. The plug-in SDK lets you write an adapter for a new AI engine in a day; the standardized port colors (PLC blue, CV teal, AI violet, trigger amber) keep complex flows readable; the live-flow board makes "what is the line doing right now" answerable without SSH and a grep pipeline.
Where it lands.
Defect inspection
Multi-engine inspection with vendor scoring. Vendor A on parts of the recipe, vendor B on others, picked by the architecture.
PLC-driven verification
Trigger from the line, image acquired, AI verdict back to PLC over OPC UA / ADS / S7 in under 100 ms typical.
Vendor evaluation
A/B run two engines on identical inputs in production. Decision is data, not vendor pitch.
Recipe migration
Move from a legacy vendor pipeline to a new architecture without ripping out the line.
Looking for the full product site? Live demos, pricing, the live flow board, the plug-in SDK, the comparison table, and the booking widget for product demos all live on the dedicated product subdomain.
Visitnexusvision.coding-nexus.com →
Discuss an orchestrator deployment.
For a product demo, the booking widget on the product site is the canonical entry. For an engagement that wraps the orchestrator (consulting, retrofit, integration), use this widget — topic pre-filled for the orchestrator track.
Email instead: