Updated July 2026 · 6 min read · Adente Vision Engineering Team
Why embed one edge unit instead of building a vision subsystem?
A machine builder who wants inspection as a standard feature has two paths: co-develop a vision subsystem, camera, lighting, compute and model, for each machine, or embed one finished unit that already contains all four. The first path re-opens a vision project on every build and ties up engineering that should be shipping machines. The second turns inspection into a component you design around once.
Embedding a single edge unit is the leaner path because the vision work is already done and self-contained. Adente Vision is an edge-AI visual inspection unit built by ADENTE Advanced Engineering Technologies, part of the Aden Group, sold through automation system integrators. It packages the camera, lighting, edge compute and AI model in one fanless enclosure. For a machine builder that means one mechanical envelope, one power tap and one controller handshake to plan for, rather than a subsystem to architect per model.
What is the mechanical and power envelope for embedding?
The mechanical and power envelope is small and fixed, which is what makes embedding practical. The enclosure is 320 by 240 by 180 mm and weighs under 9 kg, and it is fanless, so it draws no cooling air and adds no filter to service inside your machine frame. You design one mounting position with a clear view of the inspected part, and the same envelope carries every AV variant because only the enclosure rating changes, not the size.
Power is a single tap. The unit runs on 90-240 VAC at about 60 W typical, so it takes an ordinary supply already present on most machines rather than a dedicated rail. Because inference happens on the unit, there is no separate industrial PC to find space, power and cooling for, which is usually the part of an embedded vision subsystem that eats the most cabinet room.
How does the unit trigger off the machine cycle and return a result?
The unit locks to the machine cycle through its own trigger input, so capture happens at the right point without a timer guessing. It accepts an encoder pulse, a photoelectric sensor or a fixed interval, which means you tie inspection to the same cycle signal your machine already generates.
The result goes back to the machine controller the way any other station reports. The unit carries four inputs and four outputs at 24V for a discrete handshake, and it speaks five protocols, PROFINET, EtherNet/IP, Modbus TCP, EtherCAT and OPC UA, so a pass, a fail or a variant class lands on the fieldbus your machine already runs. The OPC Foundation publishes the OPC UA specification if you standardise machine data on it. Inference and imagery stay on the unit, so no part image leaves the machine, and model updates arrive by USB, which suits a machine that ships to an air-gapped plant.
What is the embed checklist?
Six dimensions cover an embed: mechanical, power, trigger, I/O, protocol and data. Design each once and inspection becomes a standard option on the machine rather than a bespoke build.
| Embed dimension | What to design for | Spec to plan around |
|---|---|---|
| Mechanical | Space and mount inside the machine frame | 320 x 240 x 180 mm, under 9 kg, fanless (no air intake) |
| Power | A supply tap on the machine | 90-240 VAC, about 60 W typical |
| Trigger | Locking capture to the machine cycle | Encoder pulse, photoelectric sensor or fixed interval |
| I/O | Discrete handshake with the machine controller | 4 inputs, 4 outputs, 24V |
| Protocol | Result onto the machine's fieldbus | PROFINET, EtherNet/IP, Modbus TCP, EtherCAT or OPC UA |
| Data | Where inference and imagery live | On-device edge; updates by USB; images stay on the machine |
Choose the enclosure rating by where the machine ships. AV-S100 is IP54 for standard environments and AV-X100 is IP66 for hazardous atmospheres, with washdown and high-temperature variants in between, and the enclosure is the only thing that changes. The IEC 60529 standard defines what each IP rating protects against, which is the reference to cite in your machine documentation.
How do OEM terms differ from one-off reseller terms?
OEM embedding runs on different commercial terms than moving a unit as a one-off box, because the volume and the relationship differ. A machine builder shipping inspection as a repeatable feature commits to a program, not a single sale, and the terms are negotiated bespoke per partner to reflect that.
We do not publish prices, and the exact commercial band is set with the partner, but as an industry pattern an embedded OEM module typically sits on different terms than a single resale, reflecting integration commitment and volume. What stays constant is the technical package: the same optics, the same four inspection modes and the same on-device processing regardless of the terms. For choosing between reselling, integrating and OEM-embedding as a business model, and for putting the unit into a customer quote, see the sibling posts on specing an inspection unit into a tender and adding vision without a vision engineer.
This post is a spoke of the pillar guide on AI visual inspection; for the channel view of reselling, integrating and embedding, see how Adente Vision works with integrators.