Industrial robot programming is the skill that turns a robot technician from the person who resets faults into the person who fixes the program. For most technicians it starts on the teach pendant, the handheld console wired to the robot controller, and later expands into offline programming on a laptop. This guide covers both: what each method is, the core concepts you need before you touch either one, and how to decide which to learn first.
If you are still building your controls foundation, read our PLC ladder logic basics first. Robots almost never run alone. A PLC usually tells the robot which program to run and when, and the robot hands status back.
Two Ways to Program an Industrial Robot
Nearly every industrial arm you will meet on a plant floor can be programmed two ways.
Online, with the teach pendant. You jog the robot to each position, record it, and build the program line by line on the pendant. The pendant ships with the robot, so there is no extra hardware to buy, and because the manufacturer builds it, it reaches functions a third-party tool may not. The catch, as the Association for Advancing Automation's breakdown of programming methods points out, is downtime: the robot has to stop production while you program it.
Offline, in simulation. You build and test the program against a 3D model of the cell on a computer, then load it onto the real controller. Manufacturers sell their own simulators, such as FANUC ROBOGUIDE and ABB RobotStudio, and brand-neutral tools such as RoboDK support many robot makes from one interface.
There is also hand guiding (physically pushing a lightweight or collaborative arm to positions), but most industrial robots do not support it and it lacks the precision most applications need. For a technician, the two methods that matter are pendant and offline.
Core Concepts You Need Before You Touch the Pendant
The brand-specific menus change. These ideas do not. Learn them once and every pendant gets easier.
Coordinate systems (jog frames)
When you press a jog key, the robot moves relative to whatever frame is active. Yaskawa Motoman's training material lays out the four you will use most:
- Joint: each axis moves on its own. Useful for getting out of awkward poses and near singularities.
- World (base): the tool point moves in straight X, Y, Z lines relative to the robot's base.
- Tool: moves relative to the tool itself. Pushing "Z+" moves along the tool's axis, which is how you approach a part straight on.
- User: moves relative to a frame you define, usually on a fixture or conveyor. If a fixture gets bumped, re-teaching the user frame can save you from re-teaching every point.
The most common rookie mistake is jogging in the wrong frame and watching the arm go a direction you did not expect. Always glance at the active frame before pressing a key.
The tool center point (TCP)
The TCP is the point the robot actually steers: the tip of the welding wire, the center of a gripper, the nozzle of a dispenser. If the TCP is wrong, linear moves curve, reorientation swings the tool off target, and offline programs miss. Most controllers have a built-in routine that calculates the TCP by touching the tool tip to one fixed reference point from several different arm orientations. After any crash, a tool change, or a bent torch neck, checking the TCP is one of the first things to do.
Motion types
- Joint moves get all axes to the destination at the same time, but the path in between is not controlled. Use them in open air, away from fixtures.
- Linear moves drive the tool in a straight line. Use them for approaches, departures and straight work paths.
- Circular moves follow an arc defined by three points.
Each move also carries a speed and a termination or blending setting that controls how close the robot gets to the point before rounding the corner toward the next one. Fast speeds with loose blending cut corners. That is fine in air and a problem near a clamp.
I/O and handshakes
A robot program is full of waits and outputs: wait for part present, close gripper, wait for gripper closed, tell the PLC the robot is clear. When a cell stops mid-cycle, the cause is very often a robot sitting on a wait instruction for a signal that never came. Learning to read the I/O screen on the pendant is as important as learning to teach points.
Teach Pendant Programming: What It Looks Like on the Floor
Each manufacturer has its own language. ABB uses RAPID, Yaskawa Motoman programs are stored as JBI files, and FANUC and other makers have their own pendant languages. Universal Robots uses a graphical interface instead of text. The vocabulary differs, but a typical pendant task follows the same pattern:
- Put the controller in manual (teach) mode and confirm the reduced-speed limit is active.
- Select the correct tool frame and user frame.
- Jog to the position, check the approach angle, and record or touch up the point.
- Step through the program one line at a time, forward and backward, at low speed.
- Run the cycle at reduced override, then increase speed in stages.
- Back up the program before and after you change it.
On most plant jobs you will spend far more time touching up existing points than writing new programs. A gripper gets replaced, a fixture shifts a few millimeters, a part revision changes a pick height. Point touch-up and safe step-through are the bread-and-butter pendant skills that employers look for in a robot technician.
Pendant Safety Is Not Optional
Teaching is one of the few times a person is regularly inside the robot's restricted space with power on. The OSHA Technical Manual chapter on industrial robots spells out the safeguards:
- Reduced speed in teach mode. OSHA's guidance limits manual-mode speed to 10 inches per second (250 mm/s).
- Three-position enabling device. The deadman switch on the back of the pendant must be held in the middle position for the robot to move. Squeezing it hard or letting go stops motion. Never tape, zip-tie or defeat it.
- Know the program before you run it. OSHA notes that wrong activation of the pendant is a frequent worker error, and that direction confusion is common with overhead-mounted robots, where the arm can move opposite to what you expect.
- Lockout/tagout for maintenance. Teach mode is for programming. Mechanical repairs that do not need power fall under lockout/tagout.
OSHA also says anyone who programs robots should be trained and demonstrate competency before being assigned the work. Expect your employer to sign you off before you get pendant privileges in production.
Offline Programming: Where It Fits
Offline programming (OLP) moves the work off the floor. You import CAD of the cell, place the robot, build paths, check reach and collisions, and estimate cycle time before anyone touches the real hardware. FANUC's ROBOGUIDE, for example, lets you simulate full workcells in 3D, preview arc and circular moves, and use application packages for welding, palletizing, painting and material handling. ABB describes RobotStudio as running on its virtual controller so simulated behavior should match the real robot.
OLP pays off most when:
- A new cell is being built and the robot is not installed yet.
- The program has hundreds of points, such as welding or dispensing along complex parts, where CAD-to-path tools save days of jogging.
- Production cannot afford the robot being down for teaching.
- A plant runs several robot brands and wants one programming interface.
The trade-off is accuracy between the model and the real world. Simulated points are only as good as the CAD, the TCP and the frame calibration on the real robot. In practice, an offline program almost always needs a round of pendant touch-up during commissioning. That is why OLP does not replace pendant skill. It sits on top of it.
Teach Pendant vs. Offline Programming at a Glance
| Factor | Teach pendant | Offline programming |
|---|---|---|
| Where you work | At the robot, in the cell | At a computer, anywhere |
| Production downtime | Robot must stop | Little until final load and touch-up |
| Extra cost | None; ships with the robot | Software license and a capable PC |
| Language | Brand-specific | Brand-specific (OEM tools) or one interface for many brands (third-party) |
| Best for | Touch-ups, small changes, troubleshooting | New cells, long complex paths, layout and cycle-time studies |
| Accuracy risk | Low; points are taught on real parts | Depends on CAD, TCP and calibration |
| Who usually does it | Plant robot and automation technicians | Integrator programmers, robotics engineers, senior techs |
How to Learn Robot Programming as a Technician
Pick the brand your target employers run. In a plant, that is whatever is bolted to the floor. If you are job hunting, read local postings and count brand names. Our guide to FANUC, Yaskawa and ABB certifications covers how manufacturer training fits on top of general credentials.
A practical learning order:
- Safety and jogging. Modes, enabling device, the four frames, and how to recover from a stopped or faulted state.
- Reading programs. Open existing programs and trace the motion, waits and outputs before you write anything.
- Touch-up and backups. Modify points on a real cell under supervision, and learn the controller's backup and restore procedure cold.
- TCP and user frames. Teach and verify both. This is where most "the robot is off" problems live.
- Simulation. Once the pendant feels natural, use the manufacturer's simulator to rebuild a program you already know. You will see exactly how the model and the real cell differ.
The federal O*NET profile for robotics technicians lists modifying robot movements, programming robot controllers and troubleshooting with PLC and pneumatics knowledge among the core tasks. Robot programming is not a separate career track from automation work. It is one of its central skills.
Bottom Line
Learn the teach pendant first, then offline programming. Pendant skills such as frames, TCP checks, safe step-through and point touch-up are what plants need every week, and they are what make offline programs work in the real cell. Offline programming becomes worth your time once you can predict how a robot will move before you press a key, or when you move toward integrator or commissioning work where new cells are built in simulation first.