AI Auto-ProgrammingGive it one good board.It writes the program itself.
The AI identifies and models each component, generates inspection boxes, and sets thresholds based on your reference board.
Hours of teaching, cut to minutes.
Traditional AOI programming takes time: preparing board data, maintaining component libraries, and tuning inspection settings for each new board.
Eight core detection capabilities.
Our latest AI model covers all eight, with ease and accuracy.
Missing, wrong, shifted, rotated or damaged components, and tombstoning.
In just four steps.
- STEP 01
Capture and choose
Capture the golden board, then tick the checks you want.
- STEP 02
Auto-program
The AI generates the inspection program in 30 seconds to 5 minutes. For panelized boards, it also generates the panel layout in the same run.
- STEP 03
Fine-tune
Change anything you are not happy with.
- STEP 04
Run it
Start inspecting production boards. Operators can review results and correct false calls directly at the machine.
The AI sets every threshold and gives
every component a score.
Scores come from a model trained on your board, and thresholds are set against those scores. One AI update retrains the model, regenerates the parameters and re-evaluates the board, whenever you want.
A score on every component
Each component gets a score, not just a pass or fail. View its score and detailed inspection results to see how far it deviates from the reference.
A threshold you can see
The threshold sits against those scores. You see how the good components and the bad components scored, and set the line between them.
Change anything the AI generated.
Bounding box sizes
Set detection bounding box sizes for each package type before auto-programming, instead of resizing them component by component afterward.
Choose which regions to inspect
For each package type, choose whether to skip a region, generate its geometry only, or include it in inspection. This includes pad, pin and bridge regions.
Keep selected parameters fixed
Lock a parameter to your chosen value so it stays unchanged when you run auto-programming again.
Named presets
Save the whole auto-programming setup under a name, apply it to the next product in one step, or export it to another machine.
Draw a box around the part of the board that changed and run auto-programming again inside it. Everything outside the box, including your edits, stays exactly as it was. Full Control has the whole list.
Add CAD whenever you want. Or never.
CAD/BOM data adds designators, part numbers and part-number grouping to components the AI has already detected. You can import it later without losing your tuning.
Accepted formats are the component information files SMT equipment already exports, in CSV, TSV or plain text. If one arrives late, or never, inspection quality is unaffected.
No pre-built component library is required for auto-programming. Component templates can be saved, reused and exported to other machines.
How we stand out from the alternatives.
The questions we get every time.
Does it need CAD or Gerber files?
No. One golden board is enough. CAD is accepted, and it adds designators, part numbers and grouping. It does not change programming quality. See the CAD comparison above.
What happens on a package the system has never seen?
It is detected and modelled from the board in front of it. There is no library entry to create first, which is the point of the whole approach.
If I tune a parameter by hand, will retraining overwrite it?
No. Generation compares when the parameter was last edited by hand against when its region was last generated, and it leaves the newer human edit alone.
How accurate is it before we tune anything?
98% detection accuracy on the program the machine writes itself, in one click. Reporting false calls from the review screen takes it further from there.
Watch it program a board it has never seen.
Join an engineer for a live, 30-minute demo. Watch a reference board become an inspection program, and ask questions at any point.
Programming gets you a working inspection on day one. Bringing the false call rate down after that is a different mechanism, and it starts with an operator telling it once.