Automotive Parts · Vision Inspection Proposal

Automotive: Part-Presence Inspection on Outlet Pipe and Air Filter Assemblies — Field Deployment

Four checks on the outlet pipe, four on the air filter — 100% inline inspection at two stations, with missing and omitted parts alarmed and stopped on the spot.

Pipe · 4 checksFilter · 4 checksTwo stationsReal-time edge decision
Leo

Leo

Vision Solutions Lead · Industrial Vision & Deep Learning

Has spent years deploying vision on production lines, leading several assembly error-proofing and 100% inline inspection projects, across the full chain from camera placement and lighting to edge deployment.

This proposal is organised item by item against the site requirement: inspection content, system configuration and decision logic, ready to be taken straight into review.

Error-proofingFew-shot segmentationEdge inferenceInline inspection

At a glance

01

Background

Both parts are multi-component assemblies; watched by eye, one missed part becomes one warranty claim.

The outlet pipe carries a plastic ring, an iron ring, an iron hoop and a plastic post. The air filter must have all six screws present, the barcode applied, the foam ring fitted and the iron ring in place.

These parts are small, varied in colour and not fixed in orientation, so manual inspection tires and misses. The requirement is to move both parts from sampling to 100% inline inspection: any missing or omitted part raises an alarm on the spot and is stopped before the next process.

02

Objectives

Turn "is it fitted, and fitted right" into a question the system answers on the spot.

8 checks
4 on the pipe + 4 on the filter
100%
every unit, no sampling
2 stations
sharing one edge computer
1–10 images
per check to go live

The aim is not to replace people but to move the judgement off the human eye: the system decides each part's presence and seating on the spot, alarms and keeps the image for traceability, and the operator only handles the units that get stopped.

03

Inspection content

Listed item by item against the site requirement, each mapping to a decidable visual target.

Outlet pipe · 4 checks

Outlet pipe inspection content
Outlet pipe checks · plastic ring / iron ring / iron hoop / plastic post — 4 checks on every unit

Air filter · 4 checks

Air filter inspection content
Air filter checks · six screws / barcode / foam ring / iron ring — 4 checks on every unit; the barcode frame is cut from the on-site demo video
04

How it is configured: tensor flow to state machine

One flow, five nodes — every check lives in the configuration layer, so a changeover edits configuration, not the model.

Tensor flow: the inspection as one flow

Tensor flow editor
Fig. 1 · Tensor flow · industrial camera → image preprocessing → semantic segmentation → event detection → state machine; the pipe and filter stations each run one flow of the same shape

Drag operators from the library onto the canvas and wire them into a flow — that is the skeleton of the system. The pipe and the filter each get one flow, identical in structure; only the segmentation classes and the state-machine checklist differ. That is what makes the setup reusable: adding a station later means dragging out one more flow.

Semantic segmentation: one class per part

Semantic segmentation labelling UI
Fig. 2 · Semantic segmentation · frame taken from the pipe station's recording: labelling canvas on the left, detection result on the right — the coloured contours are drawn by the platform, one colour per part class

Build one class per part to judge: body + plastic ring / iron ring / iron hoop / plastic post for the pipe; screws / barcode / foam ring / iron ring for the filter. Label 1–10 site images per class, click "Transfer" to train and "Detect" to verify, and the class is live. Small parts, mixed colours and free orientation are just sample diversity to a few-shot segmenter — no per-pose modelling is needed.

Event detection: masks into pass / fail

GPU event orchestrator
Fig. 3 · Event detection · drawn to the pipe station's 6 events: one event per part, its condition built from primitives; the filter station is structured the same

Each part event needs a single "object present" primitive: once segmentation recognises the class, presence in the frame is the condition. "Piece arrived" and "piece left" watch the pipe body, the latter through "object absent". If a check needs to be stricter, drag in another primitive and join it with AND — parameters only change the decision, never the segmentation model.

State machine: released only when the checklist is complete

State machine editor: state diagram and rule table
Fig. 4 · State machine · start → inspecting → end; during "inspecting" the four part events only tick the checklist, in any order — when the piece leaves, any missing item means NG, alarm and image kept

No assembly order is enforced, so the state machine enforces none: a piece arriving enters "inspecting", the four part events tick their checklist entries in whatever order they fire, and when the piece leaves, four ticks mean OK while any gap raises an audible-visual alarm and keeps the image. The "start → inspecting → end" chain and the checklist on the dashboard are this state machine running.

For a changeover or a new part, a few sample images reconfigure the relevant class and one line is added to the checklist — no retraining of the whole model — which is what lets this approach fit high-mix, low-volume lines.

05

Live demo

Two on-site recordings, one for each station's real-time inspection screen.

Outlet pipelive inspection screen 4 checksticked one by one Faultsalarmed and kept on image
Air filterlive inspection screen 4 checksticked one by one Faultsalarmed and kept on image
In one sentence
Hand the 4 pipe checks and 4 filter checks to vision to decide on the spot, so missing and omitted parts are stopped at the station, not passed down the line.