Three days on FANUC R-30iB: the iPendant, power up and jogging, fault recovery, tool and user frames, then motion programming, testing into production, registers, I/O and backup.
About this course
Nine modules, an hour of material and an hour of hands-on work each, which is three days end to end.
Safety first, then the robot system and the iPendant: the key groups, the screen structure, and the operating modes. From there, powering up and down properly, jogging, speed override and software limits, and a module on faults, because the first thing that happens to a new programmer is a fault they do not understand.
Frames get their own module. Tool frame, user frame, jog frame: what each is for, how to set them, and how to verify them. This is the step most people skip and later regret.
The last four modules are programming: teaching positions and motion instructions including what CNT does to the path, testing a program step and continuous before anything runs in auto, then editing, branching, registers and position registers, I/O, program adjust and backup and restore.
What you work through
Industrial robot hazards, how a cell is safeguarded, the deadman switch, emergency stops and the teach-mode speed limits that exist because people were hurt.
Controller, mechanical unit and pendant, the key groups and what they do, the screen structure, and the operating modes and their consequences.
Powering up and down properly, jogging in joint and world, speed override, and checking and setting the software limits before you move anything.
Reading what the controller is telling you, clearing faults, recovering from a servo fault or a collision, and knowing when not to just press reset.
What each frame is for, setting a tool frame by the three-point method, setting a user frame, and verifying both, the step most people skip and later regret.
Creating a program, teaching positions, joint against linear against circular motion, speed and termination type, and what CNT actually does to the path.
Step and continuous testing at reduced speed, checking the path, then putting a program into production mode and handing it over safely.
Copying and editing programs, jumps and labels, calling subprograms, and registers and position registers used the way production programs actually use them.
Digital I/O and the instructions that drive it, shifting a taught path with program adjust, and backing up and restoring a controller.
Lab times are approximate: they are a guide to how long the hands-on part usually takes, not a limit. You can ask for more lab time whenever you need it.
All nine module decks for this course are written and can be read now. Each one teaches its procedures as an illustrated sequence of pendant screens and keystrokes: what is on the display at each step, and which key or soft key comes next, so the material can be followed without a teach pendant in your hands.
What is not here yet is the robot. There is no hardware and no simulator for this brand in the lab, so the hands-on hour listed against each module cannot be booked and the knowledge checks are still being written. Reading a procedure is not the same as having done it, and this course does not pretend otherwise.
Written against R-30iB with the iPendant. Earlier controllers (R-J3, R-30iA) and the R-30iB Plus differ in screen detail; the procedures are close but not identical.