Documentation
Jobs and inspection results
On this page
Camera jobs and PC workflows
A camera job runs on the camera. A PC workflow evaluates images through the workbench's PC runtime. A Browser Lab workflow runs in a browser. A similar-looking node diagram does not make these interchangeable.
The Windows Job browser · read only can expose the selected camera's job, operators, graph and current result where the backend supports them. Reading a cached result does not acquire a new frame.
Change a job only in a controlled session
Camera writes require the correct device/session, permissions and an eligible state. The UI explains the effect before confirmed execution. Controlled cell/job writes check prerequisites, retain a backup and a persistent operation record, write, and perform readback checks. An unknown or mismatched outcome leaves a recovery requirement rather than silently continuing.
Load job selects an existing job on the camera and replaces the running job; it is not a local-file upload. Save job can change the startup job. Restore backup replaces running content with the recorded backup; it does not automatically rewrite the persisted startup job, and later changes to the running job can be lost. Review the exact consequence and record before proceeding.
Batch job-cell writes are gated pending hardware validation. Do not turn off acceptance gates to expose a feature.
Interpret a result
| State or evidence | Meaning |
|---|---|
| Computation completed | The requested calculation returned. It does not establish a correct industrial decision. |
| OK / NG | Must come from the configured final decision for the whole job. Confirm the actual field and meaning for each job. |
| Unknown / unavailable / missing | Insufficient valid evidence. Do not classify it as a real NG or a pass. |
| NoRead | A decoder did not return a valid code. A positive sample can therefore be a missed read; this is distinct from an execution failure. |
| Stale / previous revision | Result belongs to an older frame, input or parameter set. Run/read the intended current operation. |
| Save failed | The image/output was not confirmed saved. This is distinct from the inspection decision. |
| Browser result | Development-only result, explicitly without server acceptance. |
Verify the frame/input identity, acquisition time or operation record, workflow revision, decoded text/measurement, final decision and image-save receipt separately. A current-looking picture is not proof of a fresh acquisition.
Image files, annotations and CSV
The Windows image writer prepares original/result files and configured CSV/log output. User image folders can distinguish camera name, original/result and OK/NG. A result image or annotation must correspond to the same snapshot; do not combine an old image with a new status.
Enable only the required storage options, test permissions and free space, and check both the inspection result and writer receipt. Internal capture/recovery materials are separate from the user's output folders. A database backup does not prove a camera job was restored.
Acceptance and release
The software includes dataset, frozen acceptance, candidate and release-management code. Their presence does not establish that your installed package and live inputs have completed qualification. Record the package identity, original image provenance, physical-item split, human-confirmed answers, thresholds and timing boundary.
Historical barcode work used only two development physical items with no independent holdout or confirmed negative set; one case remained unread. Those records cannot establish a production read rate, a zero false-read rate or a line cycle-time guarantee.