Cameras & acquisition

Part positioning: camera and coordinate setup

Fix the camera view and original coordinate frame for positioning; separate pixel localization from calibrated robot coordinates and height.

Send samples for engineering review
Part positioning: camera and coordinate setup
Engineering illustration, not a photograph or measured result.

Inspection task

A useful positioning image preserves the coordinate meaning of the target. Mount the camera rigidly and choose a visible feature whose location is not changed by grasping or presentation. Define the original image origin, axis directions and allowed travel envelope. A screen overlay that follows the object can look correct even when crop or resize coordinates are wrong.

Prerequisites and sample controls

Declare whether the task is a pixel-position check or a calibrated motion command. The simple fixed-station baseline checks the horizontal center of one separated dark target. It does not certify vertical position, rotation, height or a robot pick. Prepare one visible target, no target and multiple targets; preserve the original coordinate origin and independently annotated centers.

Choose the camera route

Use a fixed area-scan camera for a stable plane and observable feature. A global-shutter route helps when the part still moves during capture. If height or overlap affects the pickup point, evaluate a verified depth route instead of treating a 2D center as a 3D pose. Camera-to-robot transformation and tool calibration are separate from image localization.

Run the controlled procedure

Before connecting a live camera, work with saved original images and a fixture drawing. Record the sensor dimensions, pixel format, lens, working distance and acquisition backend. An imported image proves that an algorithm can inspect that file; it does not prove that the camera is supported, that a trigger is reliable or that a live station has passed acceptance. Confirm the device route with the installed runtime before issuing acquisition commands.

  1. Mark the image origin and physical fixture datum.
  2. Capture one target at center and allowed travel extremes.
  3. Keep raw dimensions and record any crop or orientation transform.
  4. Verify unique target visibility before accepting a center output.

Process map

The fixture datum, fixed view and original pixel axes establish a consistent localization frame before any motion transformation.

  1. Original frame
  2. Fixture
  3. Native pixels
  4. New frame
Engineering illustration, not a photograph or measured result.
View full-size diagram

Record the evidence

Record original dimensions, target center, fixture location and capture identity. The x = 32 px and 28–35 px entries are illustrative pixel checks, not calibrated robot coordinates. Keep measured physical positions in a separate column with their measurement method.

Make a coordinate-map check that does not depend on the locator being correct. Mark a visible datum on a copy of the original image and record its original pixel position independently. Display the same input through the intended crop and preview route, then identify the corresponding displayed point. Save the crop origin, any scale and any orientation change so the displayed point can be mapped back. For an unscaled, unrotated crop, the original location is the crop-local location plus the crop origin; other transformations require their explicit inverse map. Verify this with more than one visible mark spread across the usable field. A single center mark can conceal a mirrored axis or a wrong scale. Retain the annotated copy and the untouched original as separate files.

Illustrative recording sheet; enter your own results
ControlRequired observationDecision boundary
X32: one visible targetIllustrative original-image center x = 32 pxExample window: 28–35 px; not a robot tolerance
X26: one visible targetIllustrative original-image center x = 26 pxOutside the example horizontal window
M: multiple or hidden targetsNo unique observable target centerReview; no motion command inferred

Diagnose failed cases

A changing preview scale, mirrored image or loose camera mount can shift the coordinate interpretation. Do not compensate with an arbitrary robot offset. Restore the image map first; when the target height changes, reassess the planar assumption.

Failure isolation

Compare an original point with a cropped, resized or mirrored display. Each transformation needs an explicit map back to original coordinates.

  1. Original origin
  2. Crop offset
  3. Scale
  4. Mirror
Engineering illustration, not a photograph or measured result.
View full-size diagram

Validate independently

Keep gain, exposure and automatic image adjustments fixed during comparisons. Capture after mechanical settling, then repeat at the allowed loading extremes. Check the original image at native size rather than judging a scaled browser preview. Verify that a new trigger produces a new frame identity and that missing frames become explicit failures. A stale but sharp picture is unsuitable evidence for the current part.

Compare centers with independent marks in original pixels. Any later robot use requires a separately verified camera-to-robot map, tool reference and safe physical test.

Challenge the camera mount and declared geometry without letting the software compensate invisibly. Capture the fixed target at the permitted loading locations while retaining one coordinate definition. Move the part physically, not by editing its pixels, and compare the observed displacement with the independently recorded move. An image locator should follow the physical feature consistently in the original coordinate frame. If changing the view, crop or fixture causes a new origin, record that as a new configuration requiring comparison rather than silently adding an offset. When the task will feed a robot, keep the camera-to-robot reference identity separate from the image map and request a controlled physical calibration test. The camera setup is ready for that next stage only when its original-pixel evidence and transformation history are reproducible; a moving crosshair on the screen is not enough.

Continue the engineering handoff

For an engineering handoff, supply original frames, fixture positions, camera/interface details and the capture log. Deyi Vision can review the imaging route from this evidence. Browser-local OpenCV.js execution remains a development requirement in the current capability record; do not assume that displaying a workflow makes its nodes executable in the browser.

Save the original image and the resulting record together.

Sources and technical references

These references explain the methods and limits used in this tutorial. Example checks are guidance; production acceptance requires evidence from your own samples.

  1. Inspection resolution planningDeyi Vision

    Field of view and object-side sampling must be checked with optics, exposure and contrast.

    Checked
  2. Structural analysis and shape descriptorsOpenCV

    Connected component areas and centroids describe image regions, not hidden physical part counts.

    Checked
  3. 2D and 3D machine vision selectionDeyi Vision

    Image contrast and calibrated depth answer different inspection questions.

    Checked

Engineering review

Bring the inspection problem and the evidence.

Send sample images, your current setup and the check that failed. Include field of view, working distance, line speed and acceptance criteria for a practical review.

Send samples for engineering review
Contact

Direct RFQ contact

Talk to engineering about the inspection problem.

Send sample images, competitor model, FOV, working distance and line speed before model selection.

Target: selection brief within 24h
Send sample images