Veridex · edge runtime
Inspection decisions in milliseconds, at the station
Veridex runs Coreon models on a ruggedized NVIDIA edge node beside your cameras. It checks every part at line speed, flags defects it has never seen, and sends uncertain frames back to learn from.
Specification
- Hardware
- Certified NVIDIA Jetson Orin or IGX appliance
- Cameras
- GigE Vision and USB3 Vision industrial cameras
- Runtime
- Holoscan, DeepStream and TensorRT
- Outputs
- Verdicts, masks, defect events, uncertain-frame buffer
What Veridex does
- 01
Multi-camera at line speed
DeepStream pipelines process several high-resolution streams on one node.
Core - 02
TensorRT engines
Models are compiled per camera and node for the latency the line needs.
Core - 03
Flags the unknown
An anomaly head catches defect types that were never in the taxonomy.
Core - 04
Captures uncertainty
Frames between the review and reject thresholds are buffered for review.
Core - 05
Closed-loop reject
Divert or stop the part through your PLC over OPC UA (planned).
Planned - 06
Over-the-air updates
Staged model updates from the control plane, with rollback.
Core
What Veridex produces
Four cameras, one edge node
- Node
- Jetson AGX Orin
- Cameras
- 4 × GigE 5 MP
- Line speed
- 120 parts/min
- Latency target
- < 50 ms per frame
- Model
- AX-204 adapter v7
- Passed
- 7,912 Pass
- Rejected
- 61 Reject
- Sent to review
- 27 Review
- New anomalies
- 2
Inside Veridex
Capture
Holoscan reads frames from each camera with low latency.
Infer
TensorRT runs the adapter on every frame.
Decide
Thresholds decide pass, reject or review.
Act
The verdict goes to the PLC and the audit trail.
Specification
Items marked planned are in design with pilot partners.
| Item | Detail |
|---|---|
| Hardware | Certified NVIDIA Jetson Orin or IGX appliance |
| Cameras | GigE Vision and USB3 Vision industrial cameras |
| Runtime | Holoscan, DeepStream and TensorRT |
| Outputs | Verdicts, masks, defect events, uncertain-frame buffer |
| Integration | OPC UA and digital I/O for reject actions (planned); REST and MQTT events |
| Offline | Inspection keeps running with no network connection |
Veridex in the Viseena loop
- P01 · GenerateSynvex
Renders labeled defect images from CAD, materials and a defect taxonomy.
- P02 · TrainCoreon
Fine-tunes a shared defect model into a per-SKU adapter, closing the sim-to-real gap.
- P03 · InspectVeridex
Runs the model on edge hardware at the station, at line speed, on every part.
- P04 · ExplainPilora
Turns flagged frames into defect reports, triage and probable root cause.
- P05 · CommissionTwinix
Simulates cameras and lighting in a line twin before anything is mounted.
Uncertain and confirmed real frames from Veridex flow back to Synvex and Coreon. Pilora triggers retraining when it sees drift, and Twinix sends new scenarios to Synvex before a changeover.
About Veridex
What happens if the network goes down?
Inspection carries on. Veridex runs entirely on the edge node and syncs events when the connection returns.
Can it run beside our current inspection?
Yes. Shadow mode runs Veridex in parallel without acting, so you can compare verdicts before switching over.
Do we have to buy your hardware?
Pilots use a certified Viseena appliance so performance is predictable. Supporting your own Jetson or IGX hardware is planned.
Try Veridex on one SKU
Pilots start with one part, one defect list and accuracy measured on real frames.