Documentation
DeYiVision documentation
On this page
Build an image inspection workflow, understand its result, and choose the correct environment before connecting equipment.
Engineering preview documentation · English · Reviewed 19 October 2026. This documentation describes an engineering preview. It is not a production acceptance certificate or an installer download. The release information supplied with your package is the authority for its exact edition, installer version and supported camera list.
Choose your environment
| Environment | Use it for | Equipment and data boundary |
|---|---|---|
| Windows Vision Workbench | Operate the Windows desktop and its React operator workbench; inspect configured camera jobs; develop PC image workflows | Requires the matching desktop, service and approved SDK/runtime package. Camera actions can change acquisition or jobs. |
| Browser Vision Lab | Try supported image-processing nodes using your own pictures or the synthetic example | Image calculation runs in the browser. No camera connection, PLC output or Windows service is provided by the public Lab. |
| Research and candidate builds | Qualify accounts, relay/Codex integration, OCR, reference or custom-code experiments | Separate build features and acceptance work. Availability in an engineering build does not mean availability in the public Lab. |
The Windows-facing web entry is an operator workbench. The public Lab is a separate entry that uses the browser image engine. This is the same distinction as on the DeYiVision Vision Workbench page: a Windows workbench for configured equipment and a Browser Vision Lab for trying image processing on your own pictures.
Start here
- Quick start: run the synthetic Lab example or prepare a supplied Windows package.
- System requirements: separate browser and Windows runtime requirements.
- Installation and configuration: prepare the workbench without enabling remote access.
- Camera connection: understand discovery, sessions, Online, Live and Trigger.
- Workflow editing: edit nodes, apply parameters, run and export.
- MCP connection: export the client configuration, connect an AI client and iterate on a workflow.
- Jobs and inspection results: distinguish a computation from a valid inspection decision.
- Permissions and security, troubleshooting, and deployment.
- Known limitations and integration guide.
How to interpret availability
Implemented means a code path exists in the reviewed engineering preview. Simulation means synthetic or fixture data is involved. Hardware validation pending means source or software tests cannot establish device behavior at your site. Planned / not qualified means the feature is absent, excluded from a public build or awaiting release qualification.
A browser result is marked for browser development use and does not carry server acceptance. A simulated camera card does not establish a physical connection. A dated test report applies to its recorded commit, package and conditions.
About these pages
Screenshots, where shown, come from a locally executed build using synthetic data. They illustrate the interface and are not camera or production evidence. These guides have English and translated editions. Software interface wording can differ by build.
Cognex is a third-party trademark. DeYiVision documentation does not imply affiliation, endorsement or certification by Cognex. Obtain licensed SDK components through authorized channels.