AimFactoryCore

Every device,
run from one platform

Camera, feeder and robot alike — driven by one controller and one set of software.

One controller

One controller connects everything.

No separate controller per device. One box means less wiring and a faster install — and one place to look when something goes wrong.

Line control PLC TCP/IP and DIO supported

Integrated controller + integrated software

Standard Camera a separate vision program to open

Integration Industrial robot a teach pendant to pick up

Option Flexible feeder a dedicated controller to fiddle with

One software

One integrated software runs all of it.

Set up and drive vision, feeder and robot from here — and keep those settings as a recipe per product.

6 seconds to switch

Unlimited recipes stored

The screen for feeder vibration and hopper supply

The 3D screen for aligning robot, feeder and camera

One product = one recipe

Commissioning takes about four hours. It depends on the site.

Robot

Three things that always block vision-to-robot.

We built this to solve them.

01 Reference
02 Link
03 Scale

The reference disappears

When the reference frame is built on a jig, the jig goes away — and with it, any way to check that reference again.

We take the robot’s own reported coordinates as the reference. It stays inside the robot, so when something drifts you can trace it back.

Calibration result with per-point error in mm — Nine pairs of vision pixels and robot millimetres, each with its error in mm.

A table pairing vision pixels with robot millimetres across nine points — Nine pairs of vision pixels and robot millimetres, each with its error in mm.

You cannot tell it dropped

Did the robot miss it, or did the link drop? You find out after the line has already stopped.

Connection state is live on screen, and every send and reply stays in the log with its timestamp.

The communication log for the command and data channels — Command 3000, data 4557 — every coordinate sent carries its own waiting or unconfirmed mark.

Coordinates sent to the robot, marked waiting or unconfirmed — Command 3000, data 4557 — every coordinate sent carries its own waiting or unconfirmed mark.

More models, less control

Each new product piles up settings — vision on one side, robot on the other. Nobody knows what is stored where.

The robot program goes into the recipe too. Pick the product and the robot side changes with it.

Option · Tier 1 robots (Hyundai Robotics · Agilebot)

Editing the robot program (JOB) — Edit the robot program here, and keep one slot per product.

The screen where recipes are managed — Edit the robot program here, and keep one slot per product.

One cycle

One capture finds the spot to pick.

From locating the part to the detailed checks — all inside one cycle.

Locating

Detailed checks

Parts scattered across the field, each tagged with coordinates and a rotation angle — One capture finds many, and each part gets its coordinates and rotation.

Overlapping outlines in red, pickable ones in green — Overlapping parts drop out; only what can be picked remains.

0.5s vision compute · up to 6 picks per capture

Feeder motion

It shows where the parts moved — before and after the vibration.

The image viewer puts the part positions side by side, before and after the vibration. You see which way the parts moved, and by how much, while setting the vibration up.

Software screen · 0:28 Watch on YouTube →

Scope

Part size handled 0.4 mm – 230 mm

Part size handled

Many parts, many fields.

A robot and camera picking small parts from a tray

Electronics

Chips · modules · connectors

A robot descending to pick a part placed on a tray

Automotive

Brackets · housings

A robot picking a part from a backlit tray

Battery

Electrodes · vents

A robot descending to pick a part from the feeder

Medical / Cosmetics

Needles · syringes · Mascara brushes · bottles

Configuration

What one set is made of

One set that sees, decides and instructs. Keep the robot and feeder you already have and move only the control.
One set drives up to 2 cameras · 2 feeders.

Selected · supplied together

Controller specifications

Only the values you can put straight into a design. Details such as dimensions and electrical ratings come in the datasheet (PDF).

Controller (summary)

Communication ports: 6 ports (standard)
I/O: DI 8 / DO 8
OS: Windows 10 IoT

Expansion / options (reference)

PoE ports: 2 (standard) / 4 (max) — varies by configuration
Camera support: 1 (standard) / 2 (max) — varies by configuration

Supplied by AIM

Controller · software

The set we build ourselves.

Selected · supplied together

Camera · lens

We choose between standard (5 MP global shutter) and high-resolution (12 MP) to match your part size and field of view, and ship it with the set.

What you keep

Robot · feeder · PLC

Your existing equipment stays. Hopper and lighting belong to the feeder configuration; only the control moves to our screen.

Drawings · documents

Parts in detail → All downloads →

Controller 3D drawing (STEP) Download →

Datasheet (PDF) Coming soon

User manual Coming soon

Release notes — changes by version View →

Getting started

We start by confirming it works

We do not send a quote first. We first see whether it works with your actual parts.

Send us your parts

We first confirm it works with the real parts.

See the test results

We send you the recognition rate and the cycle, with video.

Settle the configuration

We set the configuration and scope around the robot and feeder you already use.

Ask about a part test See the specs first

Keep the robot, camera and feeder you use today — we will show you how much of it can be brought together.

Every device,
run from one platform

One controller connects everything.

One integrated software runs all of it.