Documentation
Camera connection and acquisition
On this page
These instructions apply to the Windows workbench. Browser Vision Lab does not connect to cameras.
Confirm compatibility first
Use the model, firmware and SDK combination accepted for the supplied package. The software contains Classic and Web SDK adapters and historical 8405/3805 evidence, but family-wide or all-model qualification is incomplete. D900 is excluded from the documented Web HMI backend; L38 point-cloud display/export is not implemented.
The UI exposes controls according to the service's registered tools and device capabilities. A missing or unavailable control is not permission to substitute an undocumented command.
Connect a configured device
- Arrange a controlled commissioning window with the equipment owner. Know the current job and trigger arrangement before changing acquisition state.
- In desktop settings, select the intended device. Discover locally if supported, or enter the approved address manually. Save the settings.
- Open Camera in the operator workbench, select the configured camera and inspect its status/next-step message.
- Use Connect only for that device and review the stated consequence. This creates a session using locally configured credentials; it does not upload a new job.
- Verify actual identity, connection state, current job and a relevant result/frame. Refresh status after a failed or uncertain operation.
A connection uses a device HMI session slot. Another editor/session, permissions or a session limit can prevent access. Close only the session you own through its normal UI; coordinate with other users before changing their tools.
Understand the controls
| Control | Current workbench meaning |
|---|---|
| Connect / Disconnect | Establish or close the configured SDK session. These are session operations; they do not replace the job. |
| Online | Run according to the job's trigger configuration; Offline keeps the connection but stops online job operation. External signals or device permissions may prevent the requested state. |
| Live | Preview mode. The current Web control path first confirms Offline and keeps the camera Offline during preview; it does not execute the job continuously. |
| Trigger once | Request one manual acquisition. The current state-control path temporarily manages Online as required and restores it; triggering is blocked during Live or job loading. |
| Refresh / Verify | Read current state. Use this after an unknown state result before attempting another change. |
Legacy reports describe a different Live/continuous-trigger arrangement. Do not use those old instructions to predict a current Web camera control path. Verify behavior for the exact backend/package during commissioning.
If the result is uncertain
A timeout or cancelled wait does not prove the SDK action stopped or never happened. Preserve the request ID and operation record, refresh/verify the existing state and follow the displayed recovery guidance. Do not repeat a write with a new ID to force a result.
Multiple cameras
Device-level write locks exist for identified Web devices; same-device operations remain serialized and some Classic/global operations retain a global barrier. Software and cross-process concurrency tests do not prove throughput or isolation for four/eight physical cameras. Establish each site's supported camera count and failure isolation through hardware acceptance.
Do not use diagnostic probes, network-address changes, trigger loops or job-edit commands merely to make a camera appear connected.