Repeatability
One validated module that travels with the machine, across series and sites.
For machine builders
You build machines that ship with vision. Start with a product set you can repeat: camera, lens, lighting and software or SDK. Interfaces that survive the next series.
What you need
Vision is part of what you ship, not a station added later. Packaging, sorting, recycling, logistics or internal transport: the same requirement. One module, multiple sites or formats.
One validated module that travels with the machine, across series and sites.
A focused set of cameras, lenses, lighting and software you can keep for the long term.
SDK, API and product choices that do not break field machines years later.
Architecture
PC-based with application software when the function is heavy. A smart camera when the job is standard. Choose the lens and LED lighting with the camera, not after.
| Job on the machine | Typical setup | What must stay stable |
|---|---|---|
| Core machine function | PC-based + stable SDK or library | Documented interfaces, version discipline |
| Standard station on the machine | Smart camera | Fast rollout, limited custom code |
| Robot guidance | PC and/or 3D | Pose, variation, feedback to the controller |
| Optics and lighting | Selected with the camera | Otherwise you miss field of view or cycle time later |
You can buy a camera, lens, lighting or software from us and integrate it yourself. New machine function: we look at samples, field of view and how vision sits in your machine software. Your team is the integration, or we help build the first module.
Camera, lens, lighting and software or SDK. Documentation you can ship with the machine.
Samples, field of view, interfaces. A PoC only when selection alone is not enough.
Vision Master for stations. SDK or library when the code lives in your machine software.
Send an application or a product question. We will look at whether an existing set fits, or whether the function in the machine needs more.