Same obstacle: the AGV stops on its printed line; the AMR's sensor cone plans a path around it.
FramtidRMotion You Can Repeat14 / 30
SLAM
Knowing Where You Are While Mapping It
SLAM builds a map of an unknown space while tracking where you are in it — each one needs the other.
Different sensors are fused so each covers the others' weak spots — reliability comes from fusion, not one star sensor.
FramtidRMotion You Can Repeat15 / 30
Machine vision
From Light to a Decision
A vision system turns light into decisions through fixed steps — the result is only as good as the image going in.
1
Image capture
lens, sensor, lighting
▶
2
Clean-up
remove noise, boost contrast
▶
3
Find features
edges, blobs, key points
▶
4
Make sense of it
locate / measure / classify
2D = position & presence in a flat view; 3D = depth, pose, volume. Lighting is half the job — most failures are lighting, not the code.
FramtidRMotion You Can Repeat16 / 30
Visual servoing
Letting the Camera Steer the Arm
Closed vision-motion loop. Vision corrects the motion; the motion gives a new view.
Image-Based (IBVS). Acts on the error seen in the image; no full 3D pose needed.
Position-Based (PBVS). First work out the object's 3D pose, then move toward it.
Why it matters. Track and grab moving parts on a conveyor instead of needing perfect fixturing.
Camera → image error → controller → robot → part moves in view → back to camera.
FramtidRMotion You Can Repeat17 / 30
Section 4
Building & Guarding the Cell
Atoms vs bits, collaborative safety, tooling, layout, and plant integration.
FramtidRMotion You Can Repeat18 / 30
Atoms vs bits
Same Word, Two Machines
Physical robots move atoms; RPA bots move bits.
Industrial robot
moves atoms
Physical work: weld, paint, assemble
Cost: machine, floor space, guarding
Fails: mechanical, calibration drift
Changes when: the physical part changes
RPA bot
moves bits
Software on screen: emails, invoices, DBs
Cost: licences, scripting; no hardware
Fails: breaks if the UI or access changes
Changes when: the screen changes
FramtidRMotion You Can Repeat19 / 30
Collaborative safety
Sharing the Floor With People, Safely
"Collaborative" = the whole application. Not the robot alone; the same arm can be safe when slow or deadly when fast.
ISO 10218 (Parts 1 & 2). Part 1 = the robot; Part 2 = the cell, system and integration.
ISO/TS 15066. Four methods: monitored stop, hand guiding, speed & separation, power & force limiting.
2025 update. 15066 was merged into ISO 10218-2:2025; the field now says "collaborative applications."
A spectrum of speed/force vs human proximity, with the four collaborative methods.
FramtidRMotion You Can Repeat20 / 30
EOAT
The Part That Touches the Work
The arm only positions; the end-of-arm tooling does the job — and it's where most cells succeed or fail.
▤
Mechanical jaw
2- or 3-finger; flexible, forgiving on part-to-part change
◯
Vacuum / suction
fast on flat sealed parts; fails on porous or warped ones
■
Magnetic
ferrous parts only, very fast; left-over magnetism & double-picks
⚙
Process tool
weld torch, nozzle, screwdriver — the gripper is the operation
FramtidRMotion You Can Repeat21 / 30
Cell layout
Drawing the Cell: Reach, Guarding, Flow
Reach & envelope. Check coverage with the EOAT fitted, not just the bare wrist.
Guarding. Fixed fences, light curtains, area scanners, interlocked gates — sized to the stopping distance.
Material flow. Parts go in and out without a person reaching into live motion.
Access. Service and teach access without switching off the safety system.
The integrator's risk assessment (per ISO 10218-2) drives guarding choices, not preference.
Top-down plan: dashed reach circle, fixed fence, light curtain at the load opening, infeed/outfeed.
FramtidRMotion You Can Repeat22 / 30
Integration
The Robot Is One Node: PLC, MES & Recovery
PLC. Real-time, fixed-timing controller of conveyors, sensors, interlocks and start/stop signals.
MES. Sends out work orders, tracks each unit, records quality and history.
Handshakes. Digital I/O or a fieldbus tell the cell when a part is present, clamped, checked, cleared.
Error recovery is the dividing line. Detect, isolate, recover and log a fault — not just stop and wait.
Three-tier stack with a one-fault recovery loop: a production cell expects faults, a prototype is surprised by them.
FramtidRMotion You Can Repeat23 / 30
Section 5
Prototype → Production
Payback, the integration valley, and when not to automate.
FramtidRMotion You Can Repeat24 / 30
ROI
Does It Pay? The ROI of a Cell
A money decision, not just engineering. Hardware is often the smaller half of the cost.
The hidden half. Integration, programming, safety sign-off, setup, maintenance and spares.
Returns. Less labour, more output, fewer defects/scrap, steady quality — but less flexibility.
Payback = cost ÷ yearly savings. Use is the lever: a 3-shift cell pays back far faster than a 1-shift one.
Installed cost stack and payback by utilization — illustrative teaching figures, not sourced benchmarks.
FramtidRMotion You Can Repeat25 / 30
The integration valley
A Demo Cell Is Not a Production Line
A demo works once; a line must work every shift, for years.
Cycle time vs takt time
the cell must finish a part faster than demand needs
Reliability / MTBF
tiny per-cycle failure rates add up to daily stops at volume
Safety certification
the guarded, risk-checked, ISO version is slower and costs more
PLC / MES integration
the robot is one node; it must hand off to conveyors and scanners
Calibration drift & recovery
heat, wear and crashes shift accuracy; detect, recover, log
FramtidRMotion You Can Repeat26 / 30
Maturity
When Not to Automate
Automation is a tool, not a goal. It's the wrong answer when:
✓Volume is low or up-and-down. too few cycles to spread the cost over; payback never comes
✓The product changes all the time. frequent redesigns happen faster than you can re-program and re-tool
✓Parts vary far too much. heavy variation beats fixturing and vision; people handle the odd cases cheaply
✓The process itself isn't steady. automating a broken process just makes bad parts faster
✓Skill or judgment is key. fine assembly, handling exceptions, craft work where people still win
FramtidRMotion You Can Repeat27 / 30
Recap
Module Summary & What to Ask Your Vendor
Joints. Nested control loops; gearboxes (harmonic, cycloidal) buy precision by removing backlash.
Kinematics. Transforms, FK/IK, Jacobian, singularities — programmable, sometimes impossible.
Mobility & vision. AMR/AGV, SLAM, fusion, visual servoing free robots from fixed paths and fixtures.
The cell. EOAT, guarding/layout, PLC/MES integration, error recovery — where projects live or die.
Category & safety. Physical vs RPA vs cobot; respect ISO 10218 / 15066 → 10218-2:2025.
Production ≠ demo. Takt, MTBF, certification, drift, recovery — and it must pay back at real-world use.
Five questions for any vendor: repeatability at my payload and speed? Cycle time vs my takt? Independently checked MTBF? Which safety method and certification? How does it recover from a fault and talk to my MES?