Knowledge · Cameras

What is a smart camera? Operation and practical limits

When a machine must check a cap, marking or assembled part, it needs a repeatable inspection decision at the right moment. A smart camera captures the image and runs the inspection inside the camera. This guide explains that signal path, the surrounding equipment and how to test whether the device can perform the complete task.

Understand processing, inspection tools and machine communication before comparing models.

Industrial smart and Computer Vision camera family
A smart camera runs inspection functions inside the device.

What a smart camera is

A smart camera combines an image sensor, processing hardware and configurable inspection functions. It can send a pass/fail result, measurement or decoded text to another device. Manufacturers also use terms such as vision sensor, smart vision system, or all-in-one camera. These labels do not establish which tools, lenses or communication interfaces are included.

The defining feature is where image processing runs. Many smart cameras use a rectangular area-scan sensor, so “smart” and “area scan” describe different aspects of the same device. Check which tools run on the camera, which functions need external software and how results reach machine control.

Browse the available families under Cameras . For a comparison of processing architectures, read smart camera vs PC-based vision. That guide covers the selection decision; the explanation below follows the operation of one smart-camera inspection.

What remains outside the camera

The machine still needs suitable lighting, a defined product position and a controller that acts on the result. A setup computer may be required to configure the inspection even when it is not needed for processing during production.

How a smart camera works

Follow one product from its arrival at the inspection point to the controller receiving a valid result. Each stage has a separate condition to verify.

Industrial camera connected in a vision setup
Trigger in, result out, networking and PLC handshake matter as much as the sensor.

1. The scene and the trigger

A sensor or machine controller requests an image with a trigger. The camera must be ready to accept it. Exposure and lighting determine whether moving details remain sharp enough to inspect. Test the highest permitted speed and confirm what happens if another trigger arrives while the camera is busy.

2. Optics still matter

The lens determines which area appears in the image and how large the inspected feature is in pixels. Check focus across the permitted product heights. Some cameras have an integrated lens; others need a separate lens. For the optical selection, see lenses.

3. Onboard tools run the recipe

The camera executes a saved inspection configuration, often called a recipe or job. Typical functions locate a product, inspect a region or read a code. The available functions, licences and processing limits depend on the model and software release. A configuration PC normally loads the recipe; confirm that all required processing then runs on the camera.

4. Results leave via industrial I/O

The result reaches the machine through supported digital signals or a communication protocol. Define how the controller distinguishes a new result from the previous one, and when it may issue the next trigger. Saving images for diagnosis is a separate requirement: verify storage, transfer time and behaviour when the destination is unavailable.

StageWhat happensWhat this means
TriggerExternal start of exposureSynchronize the trigger with the machine cycle.
AcquisitionSensor + optics capture a frameCheck field of view, lighting and motion blur.
InspectOnboard tools run the recipeTest all inspection functions within the available time.
ReportI/O / protocol to machinePLC handshake & logging

Comparing camera arrangements

For the processing decision, see the guide to smart vs PC. The main differences are summarized below.

ApproachWhere tools runUseWatch-outs
Smart cameraOn the deviceCheck presence, dimensions or codes using the supported tools.Test the complete recipe against the result deadline.
PC + area scanIndustrial PC / vision libraryCombine camera images or run custom algorithms.Define software maintenance, licensing and recovery.
Line scan (usually PC)Typically PC / controllerBuild an image of moving material from individual lines.Synchronize line acquisition with measured material movement.
3DDevice or PCMeasure height, shape or part position.Check where depth data is processed.

Acquisition and processing: area scan describes a rectangular image, while smart describes onboard processing. Both can apply to the same camera. For image acquisition, see the area scan guide.

Smart vs code reader: compare a dedicated code reader when reading identifiers is the only task. Test both options on the same code sizes, damaged examples and movement. Read rate, communication and setup effort determine suitability; the product category alone does not prove performance.

Where smart cameras are used

Industrial production environment for Computer Vision
Typical smart-camera contexts: packaging lines, assembly cells and machine-builder stations with standard QC tools.

The following tasks may suit a smart camera, depending on the model and inspection requirement.

  • Presence and assembly, Clip seated, label present, cap on, insert oriented.
  • Simple dimensional checks, Width, gap or position within tool capability and calibration care.
  • 1D/2D codes and OCR, Cartons, labels, nameplates when a dedicated reader is not required.
  • Color / contrast presence, Wrong wire color, missing print block, fill-window cues.
  • Machine-builder standard stations, Repeatable recipes across many shipped machines with limited IT footprint.
  • Retrofit cells, Add vision where there is no appetite for a full PC cabinet.

Compare external processing when images from several cameras must be combined or custom algorithms are required. Include image storage and production-system interfaces in that decision.

Specs that actually matter when you buy

Smart-camera datasheets mix sensor specs with tool lists. Prioritize both.

Tool set and recipe limits

Write down every required decision. Check that the exact model supports the required tools together, including locating the product, handling invalid images and combining results. Record any licence and software-version requirements.

Resolution, FOV and working distance

Calculate the required pixels across the smallest feature and include positioning margin in the field of view. Verify sharpness at the near and far height limits. More image data can increase processing and transfer time, so test the chosen image size with the full recipe.

Cycle time

Measure trigger-to-result time with every required tool enabled and with image logging active if production needs it. Compare the longest observed time with the actual result deadline. The sensor’s maximum frame rate does not specify this end-to-end duration.

I/O and protocols

Confirm digital I/O count, industrial Ethernet protocols your PLC speaks, and how recipes are switched (job select bits, Ethernet commands, HMI).

Lighting dependency

Test whether the defect produces enough contrast under the proposed lighting. Verify the integrated light before relying on it; the application may need a separate light and controller.

Environment and mounting

IP rating, operating temperature, and cable connectors matter on real machines. Compact bodies help in tight cells; heat and vibration still apply.

Before you buy, eight questions

  1. Can all required inspections run together within the available time?
  2. Is a PC-based library clearly required for complexity or multi-camera logic?
  3. What field of view, smallest feature and working distance are required?
  4. What PLC protocols and I/O does the machine already use?
  5. Who will maintain recipes after handover, operators or vision engineers?
  6. Do you need image archival, and how much?
  7. What lighting geometry works on real good/bad samples?
  8. Would a dedicated code reader meet the requirement?

Building a working smart-camera setup

Vision hardware stack with camera and controller
Even “all-in-one” stations still need mounts, lighting, trigger and PLC handshake.

A reliable station remains a system:

  1. Smart camera, sensor + tools + I/O matched to the recipe.
  2. Lens, integrated or separate, sized for FOV and feature.
  3. Lighting, often the make-or-break element.
  4. Mechanics, stable mount, cable strain relief.
  5. Triggering, consistent part presentation.
  6. PLC & recipe management, job select, reject logic, changeover.

Common first-system mistakes

  • Choosing smart for a problem that needs custom PC algorithms from day one.
  • Ignoring lighting because “the camera is smart.”
  • Overloading one recipe with too many tools for the cycle time.
  • No plan for recipe backup and version control across machines.
  • Assuming USB configuration PCs will stay connected on the factory floor.
  • Skipping sample variation, shiny, dark and dirty parts on Monday morning.

How to read a smart camera product page

On Sedeco product pages for smart camera families you will typically see resolution, tool cues, I/O or protocol notes, and optics options. Read them as answers to the eight questions:

  • Resolution / sensor, pixels available for FOV; check cycle-time impact.
  • Tool environment, which inspections are supported onboard.
  • I/O & networking, how results reach the PLC.
  • Optics package, integrated vs mount; FOV ranges if stated.
  • Protection / housing, IP and industrial readiness.

Use the model page to verify the hardware and the smart vs PC guide to assess the architecture. Then compare suitable models in the camera catalogue.

Worked example: the result deadline

Consider an illustrative bottle inspection with label-presence, DataMatrix and cap-colour checks. Products arrive at an average of 120 per minute, one camera sees all required features, and the machine selects a recipe for each bottle format. These are design assumptions, not a reported installation.

The average arrival interval is 60 ÷ 120 = 0.5 seconds. Suppose, separately, that the reject point is 150 mm downstream and the conveyor moves at 500 mm/s. Transit time is 150 ÷ 500 = 0.30 seconds. If controller processing and actuator response require an assumed 60 ms, 240 ms remain before adding a timing margin. The inspection deadline is therefore shorter than the average product interval. Measure the actual delays and shortest trigger spacing before accepting a camera.

Run all three checks on independent good, defective and borderline bottles. Record missing-code cases separately from decoded-but-wrong codes. Include format changes, a trigger while busy and loss of communication. Confirm that the PLC associates each decision with the correct bottle and rejects or stops according to the agreed invalid-result procedure. If processing cannot meet the deadline, compare a simpler validated recipe or external processing.

Use the feasibility checklist and the smart vs PCpage before ordering hardware.

What the calculation establishes

A timing budget defines the test requirement. It does not prove inspection accuracy or that a particular camera will meet the deadline. Validate those separately with the selected hardware and representative products.

Industry snapshots

Packaging and FMCG

For label, code and cap checks, include every permitted pack format and surface finish in the sample set. Confirm that a format change loads the intended recipe before the next product is inspected.

Automotive component cells

For component-presence checks, test the range of positions delivered by the feeder or robot. Dimensional checks additionally require calibration and comparison with an independent measurement reference.

Electronics assembly

For connector seating or character checks, establish whether the distinguishing feature is visible from one view. A hidden contact or underside feature may require another view or a different test method.

Machine builders / OEMs

Industrial lenses and optics for Computer Vision cameras
OEMs standardize optics and recipes so field service can repeat the station worldwide.

For repeat machines, retain the camera, lens, light and software versions with the machine bill of materials. Test restoration on a replacement device; importing a recipe alone does not establish equivalent imaging.

Integrating with PLC, HMI, and IT

Typical loops:

  • Trigger in, photoelectric or PLC fires acquire.
  • Inspect, onboard recipe runs.
  • Result out, discrete or protocol to PLC; optional image to NAS.
  • Changeover, HMI selects job; camera loads recipe.

Define the ready, busy, result-valid and acknowledgement sequence supported by the device. Test timeouts, stale results and communication loss with the PLC. Record the network configuration, backup owner and permitted remote-support access.

Cost, quality, and what good enough means

Compare the complete station cost: camera, optics, lighting, software licences, integration, configuration and training. Also estimate maintenance, replacement and future recipe changes. Removing a separate processing PC changes these costs, but does not establish a lower total cost for every application.

Evaluate image quality on the actual feature, including glare, dark surfaces and height variation. Compare lighting arrangements before assuming that more pixels solve a contrast problem. Keep the images and settings used for acceptance.

Calculate engineering cost as configuration, PLC, validation and training hours multiplied by the relevant rates. For operating costs, record maintenance hours, replacement parts and licence renewals. Compare these with measured inspection labour, reject costs and intervention time. Avoid counting the same production loss under both downtime and lost output.

Agree separate limits for missed defects, false rejects and result time. Test those limits on samples not used for configuration and under the expected operating conditions. Include restart, recipe change and restoration from backup in acceptance.

Practical project checklist for a smart-camera project

Follow this sequence so architecture and optics are settled before catalogue shopping.

  1. List every inspection in plain language, presence, code, color, gauge, and mark which must run in the same view and cycle.
  2. Decide smart vs PC, use smart vs PC with honesty about custom logic and multi-camera needs.
  3. Size FOV and feature resolution, same discipline as area scan; involve lenses early if optics are not integrated.
  4. Trial lighting on real samples, start from lighting; do not trust demo booth contrast.
  5. Map PLC I/O and job select, bits, protocols, HMI screens, reject timing.
  6. Benchmark cycle time with the full recipe, not empty acquire fps.
  7. Define recipe ownership, who edits, who approves, how backups travel with machine serial numbers.
  8. Run feasibility, feasibility checklist, then browse the camera catalogue.

When smart cameras struggle

Reconsider onboard processing when the required tools are unavailable, several cameras must share calibration or the complete recipe exceeds the measured deadline. Use the architecture guide to assess external processing. Keep the failed test and its conditions so that the alternative is evaluated against the same requirement.

Control recipe changes. Give each approved configuration a version and backup location, and record who may change limits. After a change, repeat the affected acceptance tests before releasing the recipe for production.

Use the completed checklist as the handover record: selected hardware, tested image conditions, inspection limits, communication sequence and recovery procedure. Open items should identify the missing evidence and its owner.

Handover: what operators and maintainers need

Record working distance, lens and lighting settings, exposure, PLC signals and decision limits with example images of borderline products. Store the approved configuration with the machine documentation. Verify that a maintainer can restore it without recreating the inspection from memory.

Define a recovery procedure matched to the machine: inspect lens and light windows, check trigger and communication status, then restore an approved recipe where appropriate. Record who may change settings and when engineering support is required. Test the procedure during handover.

Use operator-facing names that identify the product format and the reason for rejection. Match the language to the people operating the machine. Further background is available in Knowledge.

Short glossary

Smart cameraThe camera processes images using built-in inspection functions.
Vision sensorThis is a product label; check each model’s supported functions.
Recipe / jobA recipe stores inspection regions, functions and limits.
PC-based visionSoftware on a PC processes the camera images.
ToolA tool performs an inspection step, such as measuring or reading text.
Job selectThis command selects the recipe required by the machine.
Cycle timeThis is the time to acquire, inspect and report a result for one part.

FAQ: smart cameras

Is a smart camera the same as an area scan camera?

Many smart cameras use area-scan sensors, but “smart” refers to onboard processing. A plain area scan camera needs external software. See the area scan guide.

When should I choose PC-based vision instead?

When complexity, multi-camera logic, custom algorithms or IT integration exceed onboard tools. Use smart vs PC.

Do smart cameras need lighting?

Yes. Integrated lights help some jobs; many stations still need external industrial lighting for stable contrast.

Can one smart camera replace five inspection stations?

Only if one FOV and one cycle time cover all checks. Often multiple views or stations remain necessary.

Are smart cameras good for deep learning?

Some support onboard or edge DL tools; others do not. Confirm licenses, training workflow and inference time on your hardware class.

What about line scan or 3D?

Classic smart cameras target discrete 2D tasks. High-speed webs and advanced 3D often stay PC- or controller-based, pick the family for the physics first.

How do I maintain recipes across a fleet?

Treat recipes like software: version, backup, and controlled deploy. Document optics and lighting with the recipe file.

Next steps

Choose a smart camera when the selected device supports the complete inspection, timing and machine interface. Validate good products, defects and borderline cases, and test recipe changes, missing images and recovery after interruptions. Use the linked selection guides for the next hardware decision.

Related: Knowledge hub· Area scan guide· Feasibility.

Next step

Which camera should I choose?

Use the camera-selection guide to turn the inspection requirements into a choice of sensor, optics and triggering. Bring the sample results and timing budget from the trial.

Selecting cameras for Computer Vision