Recipe-based model change
Feeder conditions, vision conditions and robot pick conditions are bundled per product as a Recipe. When the model changes, the related conditions load together.
MULTI-MODEL
Vision, robot and feeder conditions are bundled in one Recipe to change the model. The operator only selects the model name, and vision, robot and feeder change together.
Recipe = vision + robot + feeder
Dozens of models run together
Vision, robot and feeder operated together
Pick coordinates from one capture
WHY
If vision conditions, robot paths and feeder patterns each have to be re-tuned every time the model changes, operation wobbles. AIM bundles these conditions from the setup stage to make model changeover stable.
Conventional
The vision engineer, robot engineer and feeder engineer each re-tune their conditions. The line stops for 30 minutes to 2 hours.
The AIM way
Vision, robot and feeder conditions are bundled in one Recipe. The operator selects the model and every condition loads automatically.
Result
Production resumes after a verification cycle. Operation stays stable as models grow.
RECIPE
The operator only needs to know four things. AimFactoryCore manages the detailed conditions inside them.
How to look at this model and where to pick it
Which posture to approach with and where to move it
How to spread and supply the parts
How to handle cycle, error and display information
FLOW
From selecting the model to resuming production — the 4 steps the operator follows.
Select the model on the AimFactoryCore operating screen. The operator only needs to know the model name.
The Recipe loads automatically through HMI → PLC → Robot → Vision → Feeder. No manual changes.
Recognition, pick-up and placement are checked with one or two test parts. Failures are shown and recovered.
Once alignment and repeatability are confirmed, production resumes. Shift changes follow the same flow.
OPERATION
Recipe selection, vision setup and the robot program all sit in one operating screen. The operator does not have to switch screens to work.
Integrated operation
AIM connects feeder conditions, vision recognition, robot coordinates and PLC/Robot signals into one operating flow, based on a Recipe per product.
Change the product and the required conditions load together; during operation, you can see at which stage a problem occurred, following the flow.
AimFactoryCore Operation
Product B Recipe
Product B Loaded
Model B / Score 86 / Pick OK
Vibration 58 / Supply OK
Ready → Trigger → Done
Position OK / Overlap Clear
Guidance Flow
Feeder conditions, vision conditions and robot pick conditions are bundled per product as a Recipe. When the model changes, the related conditions load together.
Vision recognition results are connected to coordinates the robot can use and to pick criteria. Coordinate alignment and position correction are part of the operating screen.
Feeder motion, supply status and Robot/PLC operating signals are connected in production order. The Ready, Trigger, Done and Error flow is organized from the floor's point of view.
Setup, monitoring, pick feasibility and error-cause checks continue on one screen. Training videos and remote support help with on-site operation.
DEMO
Hyundai Robotics × AIVE — a case where several parts and feeders were controlled together in one cell.

Hyundai Robotics × AIVE flexible feeder — full control
A real Pick & Place automation case where ROBOEYE 2D vision controls a flexible feeder and FlexiBowl together.
START
Tell us how many models you run today and how long a changeover takes, and we will review the Recipe structure with you.