To move a robotic work cell, treat the arm and the controller as separate rigging problems, lock or remove the axes per the OEM shipping brief, and expect to re-master and re-teach the robot at the new site because absolute position data does not travel reliably through a move. Fencing, light curtains and interlocks get recommissioned and re-verified before the cell runs production again, not just reconnected.
A robotic work cell looks like the easy machine on the floor. No coolant, no hydraulics, no tie bars to protect โ just an arm bolted to a base, a fence around it, and a cabinet full of electronics. Riggers who treat it that way get the arm to the new building without a scratch and then spend three days finding out the robot no longer knows where it is.
The physical move of the robot is genuinely simple compared to a press or a mill. What is not simple is that a robot's whole value is a set of taught positions and calibration data referenced to a base that has to land in almost exactly the same relationship to the world it left. Move the base a few millimeters off from what the controller expects, or lose the mastering data on the way, and the robot runs its program with total confidence into the wrong point in space.
What is different about moving a robot arm versus the controller?
The arm is a mechanical rigging problem; the controller is a data problem, and they get planned as two separate items from the start. The arm itself โ the manipulator, on its base or pedestal โ has axes that need locking in a safe travel position, joints that need bracing so they cannot swing under vibration, and a base that gets lifted and blocked the same disciplined way any machine tool base does: from the manufacturer's designated points, never the wrist, forearm links or cable conduit.
The controller cabinet is a different animal entirely. It holds the drives, the safety PLC, the teach pendant connection and, critically, the program and calibration memory. Some of that memory is backed by battery, and a battery that dies in transit can wipe position registers that took days to teach the first time. Before the cell is touched, someone pulls a full backup of the controller โ programs, I/O configuration, calibration and mastering data โ to external media, not just trusting the onboard battery to hold it through a move that might take weeks between disconnection and re-power.
What is mastering, and why does a move put it at risk?
Mastering is the calibration that tells the robot's controller exactly where each joint's zero position sits relative to its resolver or encoder, and it is the single most common casualty of a careless robot move. Every industrial arm has a reference position โ often marked with mastering pins, dowel holes, or scribed alignment marks โ that the controller's absolute position data is built around. As long as encoders stay powered and mastering data stays intact in controller memory, the robot knows where it is down to a fraction of a degree at every joint.
Two things break that during a move. First, a battery failure on an absolute encoder system erases position memory the moment power and backup battery are both gone, which is why battery packs get checked and often replaced before a long move rather than trusted to outlast it. Second, a jolt hard enough to move a resolver relative to its shaft can throw mastering off without visible damage. A robot that looks perfect and passes every mechanical check can still be a few tenths of a degree off at the shoulder, which multiplies into inches of error at the tool center point by the time it reaches the wrist.
The practical response is to plan for a re-master as a normal step, not a failure mode. Crews record the OEM's mastering method before disconnection โ pin mastering, where physical dowels lock each axis at a known reference, or single-axis mastering done joint by joint with a teach pendant โ so whichever one applies gets redone cleanly at the new site instead of guessed at.
What happens to the safety fencing and light curtains?
They get decommissioned as a system, not just unbolted panel by panel, because a cell's safety case is the fencing, interlocks and controller safety logic working together โ all three get re-verified together before the cell runs again. Fence panels get numbered and photographed in their original layout first, since the perimeter is sized to the robot's reach envelope plus a margin, and rebuilding it from memory is how a gap ends up where an arm can reach an aisle.
Light curtains, safety mats, interlocked gates and e-stop circuits are wired into the safety PLC or the controller's dedicated safety inputs, and that wiring gets labelled and documented before it is disconnected โ not left to a picture on someone's phone. On reassembly, distance calculations matter again: a light curtain has a minimum safe distance from the hazard based on the robot's stopping time and the curtain's response time, and if the new layout changes that distance, the curtain needs to be repositioned or reselected, not just remounted where it happened to sit before.
None of the safety system gets called functional on the say-so of a reconnected wire diagram. E-stops get pulled and verified to stop the robot, light curtains get walked through to confirm they trip the safety circuit, and interlocked gates get opened under power to confirm the robot drops out โ the same discipline any machinery moving job applies to a re-guarded machine tool.
What has to happen to end effectors and tooling?
End-of-arm tooling comes off and travels as its own item, because it is usually the most fragile, most application-specific part of the cell. Grippers, welding torches, spray guns, vacuum cups and their hose and cable bundles get disconnected at the wrist flange, individually packed, and labelled by station if the cell runs more than one tool through a changer.
- Tool changers โ the quick-disconnect coupling between wrist and tool โ get inspected for wear before reinstall, since a worn changer that repeated fine at the old site can develop problems once it is reloaded.
- Wrist-mounted sensors โ force-torque sensors, vision cameras, seam trackers โ are precision instruments and travel in cases, not bolted to an arm being jacked through a plant.
- Cable and hose bundles running up the arm get unclipped, since a bundle built to flex with the joints is not built to take a static load in a lift.
- Process-specific hardware โ a welding wire feeder, a dispensing pump, a paint reservoir โ is disconnected, drained or purged per its own service requirements before it travels.
Peripheral equipment in the cell โ index tables, part-presentation fixtures, conveyors, vision stations โ moves as ordinary rigging work, but it gets surveyed and documented for its position relative to the robot base before disassembly. A fixture off by a few millimeters from where the program expects it is functionally the same failure as a mismastered arm: the robot goes exactly where it was taught, and the part is not there.
What the site walk has to capture
- Robot make, model and controller type, plus whether a current backup of programs and calibration exists
- OEM shipping and mastering procedure for that specific arm, and whether mastering pins or fixtures exist on site
- Encoder battery status and age, and whether a spare battery pack should travel with the controller
- Full inventory of end effectors, changers, sensors and process hardware, each as its own line item
- Fence layout, light curtain model and mounting distances, and all safety wiring documented before disconnection
- Base mounting method โ bolted pedestal, shared machine base, or floor-mounted stand โ and the new site's foundation
- Floor flatness and levelness at the new location; a twisted base under a robot pedestal reintroduces the same error mastering is meant to eliminate
How is a robot cell rigged and loaded for transport?
The arm gets locked into a travel or park position โ most manufacturers specify a pose where the joints are near their mechanical stops and the load is balanced โ and every axis that can swing freely gets braced with the OEM's shipping brackets if they still exist, or with blocking built to the same intent if they do not. The base is lifted and jacked from the points the manufacturer designates, and a pedestal-mounted robot is treated as top-heavy even when the published weight looks modest, because the mass sits high and the tip-over risk on a forklift or a skate is real.
The controller cabinet rides upright, secured against tipping, and protected from moisture and static the way any electronics cabinet is on a machine move. Cables get coiled, tagged at both ends and bagged with the connector they belong to โ a cell can carry dozens of individually numbered cables between the arm, controller, safety system and peripherals, and a mislabeled cable is a slower problem to fix than a damaged one. Everything travels between sites through our licensed broker and carrier partners on equipment matched to the cell's real dimensions and fragility, which for a robot with sensitive optics or force sensors usually means an enclosed, air-ride trailer rather than an open deck.
Why does a robot need to be re-taught after a move, not just recalibrated?
Because mastering only restores the robot's sense of its own joint positions โ it does not restore the relationship between the robot and everything around it that the program assumes. A robot's taught points are references to fixtures, conveyors, part presentation and tooling in the exact location they occupied when someone jogged the arm to each point and recorded it. Move the robot, the fixture, or both, and even a perfectly mastered arm will run its program to positions that no longer line up with the real part.
The practical sequence at the new site: master the robot first per the OEM procedure, verify repeatability with a dial indicator or laser tracker at a few known points, then re-teach or offset the program against the actual as-installed fixture locations. With a well-documented base coordinate frame and fixtures reinstalled to the same relative position, that can be a matter of a few offset adjustments. Where fixtures shifted, or the robot base sits in a different orientation than before, expect a genuine re-teach of the affected points โ a controls and process engineering task that belongs to the plant's automation team, working from a robot and cell the rigging and millwright crew has already leveled, anchored and mastered correctly.
What goes wrong most often?
Skipping the program and calibration backup before the controller is powered down, then discovering the encoder battery did not survive the move. Lifting or bracing the arm from a link or the wrist instead of the OEM's designated points. Reassembling the fence from memory instead of the photographed layout, so a light curtain sits too close to the hazard for its stopping distance. And the most expensive one: mastering the robot and calling it done without re-verifying against the actual fixtures, so the cell passes a dry run and places its first real part off center. Every one of these is a planning step, not a rigging skill โ the crew handling the physical move and the team handling recommissioning need the same site walk and timeline.
Bottom line
- Treat the arm and the controller as two problems: mechanical rigging on the arm, data backup on the controller.
- Back up programs and calibration to external media before disconnection โ do not trust the battery alone through a move.
- Budget for a re-master as a normal step, not a failure. Encoder battery loss and travel shocks both put it at risk.
- Fencing and light curtains get rebuilt to the documented layout and re-verified as a working safety system, not just reconnected.
- Mastering the robot is not the same as re-teaching it. Fixtures and part presentation need to be surveyed and offsets checked before production runs.
Moving a robotic cell, a robot-tended machine tool, or a whole automated line? That is machinery moving and millwright work built around the same base-leveling discipline covered in machine leveling and alignment. Send the cell layout, the robot make and model, and the fixture list, and we will build the plan โ start here.