Heavy Duty Robot Track and Rail Systems

Motionwell Automation designs and builds heavy duty robot track and rail systems in Singapore, the rail a large industrial arm rides on when the work is longer than the arm is. The heavy-duty track we build carries platform loads to 2,000 kg on a rack-and-pinion drive, over strokes beyond 20 m, at travel speeds to 1.5 m/s with repeat positioning of ±0.1 mm, sized for arms of 500 kg and above and designed to mount FANUC, ABB, KUKA and Yaskawa platforms. On the delivered palletizing configuration a column palletizer of 100 to 200 kg payload sits on that track and holds ±0.5 mm along the rail using an absolute linear encoder, with a 6 m track serving three pallet positions and 2 to 3 seconds of transit between them. Machines are designed, assembled and tested at our Woodlands Link facility, and the company has delivered more than 150 special purpose machines since 2014 under ISO 9001:2015 and bizSAFE Level 3.

Where we stand, said plainly before you read further. We do not manufacture robot arms, rails, racks, gearboxes or drives. We buy them. What we design is the frame, the carriage, the drive train sizing, the interface to your floor, the cable management, the guarding and the integration with the robot controller. We also do not build production welding cells, and welding stations are one of the standard applications for a track of this kind, so that exclusion belongs up front.

This page is about the heavy end specifically: what changes when the moving mass is large enough that the engineering changes in kind rather than in size. The general case, including the reasons to put a robot on a rail at all and the 100 mm low-profile design, is on our robot seventh axis and linear track page. If you have an arm model, a stroke and a payload, skip ahead and talk to an engineer.

What Actually Changes Above Roughly a Tonne of Moving Mass?

Not the concept. A servo turns a pinion, the pinion walks along a rack, and a carriage on linear guides takes the arm to the next station. What changes is which component is the limit, and almost every limit moves off the motor and onto the structure.

There is no clean threshold, but three symptoms mark the crossing better than any number: the moving mass becomes a large multiple of the payload the arm handles, so the track is mostly moving itself; the carriage can no longer be stopped inside the guard setback the room allows; and the rail becomes long enough to be fabricated in sections.

Everything above the last row is engineering. The last row is availability, a business decision, and it is treated on its own further down.

What Have We Actually Delivered on Track and Rail Systems?

The figures below are our own series specifications and delivered configurations rather than a distributor’s catalogue, and the difference between the two track classes shows better in numbers than in prose.

Two things in that table get misread in tenders.

Speed is a configuration outcome, not a class property. The lighter track lists 500 mm/s and the heavy one 1.5 m/s, which looks backwards until you notice both are maximum speeds for their series rather than the speed any one cell runs at, and that the speed a track is finally commissioned to depends on its stroke, duty and stopping requirement. Ask what a track was configured for and why, not which class it sits in.

Repeat positioning is not placement accuracy. ±0.1 mm on the rail is the spread when the axis returns to the same commanded point under the same conditions. It says nothing about where the tool ends up, which is decided by the arm, the tooling, the fixture, the thermal state and how well the station is referenced. The ±0.5 mm quoted on the palletizing track is a positioning figure along the rail rather than a repeat figure, and neither number is what governs stack quality: on that cell ±1 mm placement was accepted because corrugated cases hold ±2 to 3 mm on their own dimensions, and chasing tighter placement than the case holds buys nothing measurable in the stack. Build detail is in the palletizing robot case study.

How Do Drive Torque and Gearbox Sizing Get Decided?

By working backwards from the tooth, not forwards from the motor catalogue.

The torque path is short: servo motor, planetary gearbox, pinion, rack. Motor torque times the gearbox ratio becomes torque at the pinion, and that divided by the pinion pitch radius becomes the linear force pushing the carriage. The force has to cover accelerating the whole moving mass, which is the large term, plus rolling and seal friction, plus any residual force from a rail that is not level.

Three sizing rules then apply, and two of them are easy to skip. All three run on a mass budget written down before the gearbox is picked, which is treated further down.

Size on RMS torque across the whole duty cycle, not on the peak of the move. Acceleration torque is transient; heating is governed by the root mean square across the cycle. A track that indexes continuously is a different thermal problem from one that makes a handful of moves a shift, with the same mass and the same profile. The same reasoning applies to every servo axis we build, and it is set out in our note on servo versus stepper motor selection.

Use the peak band deliberately. A servo will deliver short bursts well above its continuous rating, around three times continuous being a common figure on datasheets, which is exactly what a ramp needs. That headroom belongs in the acceleration budget, not in the continuous one, and a design that leans on it during the cruise phase is undersized.

Choose the ratio for two things, not one. The ratio sets the force available at the pinion and reduces reflected load inertia by the square of the ratio, which is what makes a large mass controllable by a small rotor. It also caps the top speed at the rail. Those two pull against each other, and the resolution is usually the motion profile rather than the ratio.

Why Does the Rack Set the Acceleration Limit Before the Motor Does?

Because the entire drive force is delivered into the structure through a small contact patch on a few teeth, and that patch does not care how the force was generated.

Tooth root bending and flank contact stress are the two limits, and both scale with force, which is mass times acceleration. Doubling the moving mass at the same ramp asks the same teeth to carry twice as much. A larger motor does not move that ceiling, it only reaches it sooner, and the failure is a drive fault, accelerated pinion wear, or a rack section that needs replacing under a robot.

Three responses work, and they cost different things.

Longer ramps. Cheapest, and it costs cycle time. On a track serving pallet positions, 2 to 3 seconds of transit is absorbed into the pattern cycle without touching throughput, which is where a slower ramp is genuinely free. Inside a takt with no slack it is not.

A jerk-limited profile. Shaping the acceleration rather than stepping it cuts peak force at the same average acceleration, which buys tooth life and reduces the shock the frame sees, for a little time and some tuning.

More tooth. A larger rack module, a wider face, or a second drive spreading the load. That is a redesign, which is why the force calculation belongs at concept stage.

A fourth limit arrives with length and is not a component at all. A rail long enough to serve a row of stations is not a rigid body: drive at one end and the mass at the far end responds through the frame’s own stiffness, so achievable acceleration is limited by structural response rather than by anything on the bill of materials.

What Do Rail Flatness and the Floor Have to Deliver Over a Long Span?

More than the floor was built to give, which is why the levelling interface is part of the machine rather than part of the installation. Our tracks are levelled on adjustable feet along their length, and the low-profile design bolts directly to the factory floor with no pit required. Both arrangements mean the same thing: the rail carries its own datum, and the slab only has to be strong and stable, not flat.

That matters because an industrial slab is not flat to machine tolerance, it has joints, and it moves under load. Floor flatness and forklift traffic are already on the site-constraint list we work through on automated palletizing systems, and on a long track they graduate from a constraint to a design input. Three failure paths follow from getting it wrong.

Preloaded bearing blocks. A rail out of plane forces the carriage to bend as it travels, which raises drive friction, wears guides unevenly and shows as position error at one end of the stroke only. An axis that is fine at one end and drifting at the other is a geometry problem, not a controls problem.

Joints between sections. A long stroke is fabricated in sections, and every joint has to carry rail flatness and rack pitch across it. That is a fabrication and alignment discipline rather than a component you buy, and it is where a track built to a drawing differs from one built to a measurement.

Foundation drift after handover. The pattern is familiar from robot cells generally: a system runs well through commissioning and starts missing in month three because something was nudged and the tolerance stack moved. On a track that something is a levelling foot or an anchor, so levelling checks belong in the maintenance schedule and the tool frame gets re-referenced after any foundation work, the tolerance-stack argument made on our robot integration services page.

What Does Thermal Growth Do to a Long Steel Rail?

It moves the far end of the axis relative to the near end by an amount proportional to length, on a daily cycle nobody is watching. Thermal growth is one of the machine-level error sources that dwarfs anything the motor contributes, alongside lead error, coupling wind-up and backlash, and repeatability lives in the mechanics generally: preload, guide quality, homing method and thermal state. On a short axis it is a footnote. On a long steel rail in a shed that is not air conditioned, it can separate a station taught in the morning from the same station in the afternoon, with drive heat at the pinion end adding to ambient along the length.

The design responses are about deciding where the error is allowed to land.

Anchor one end, let the other float. The structure grows somewhere, and deciding where is a design choice. Not deciding means the frame fights itself and the growth appears as bearing preload instead.

Put the datum where the tolerance is. The station needing the tightest placement should be nearest the fixed end, because it accumulates the least growth. This costs nothing at layout stage and cannot be retrofitted.

Do not ask the encoder to solve it, reference locally instead. An absolute linear encoder tells the controller where the carriage is on the rail without a homing routine, which is worth having, but it does not tell the controller that the rail itself moved relative to the station beside it. Where a station demands better than the rail can hold across a temperature swing, the answer is a local feature the robot references against, or a camera measuring the real offset before the move. This is the same layering we use where an autonomous mobile robot parks to within about ±50 mm and the arm still has to reach a rack slot to a fraction of a millimetre.

How Is a Heavy Carriage Held and Stopped?

These are two problems that share a component, and conflating them is how a heavy axis ends up with a brake that holds fine and stops nothing.

Two consequences follow that rarely surface on a light axis.

Kinetic energy scales with the square of speed. Doubling the travel speed quadruples what a brake, a buffer or an end stop has to absorb, so a speed increase agreed late to recover cycle time is not a parameter change. It revisits the brake, the buffers and the stopping distance, and therefore the fence.

Holding a load on a stopped axis is a sequence, not a component. If the arm is holding a case when the track stops, the brake is holding arm, tool and load together, and the release order matters: nothing moves until the system knows the pose is safe. We specify a motor brake on vertical axes rather than paying for continuous holding current, and that brake matters for safety when power drops. The same reasoning reaches a horizontal carriage the moment the floor is not level or the arm is extended to one side.

When Do Two Drives on One Axis Earn Their Cost?

Three different problems get solved by a second drive, and they are worth separating because only one of them is about backlash.

Force. When the required tractive force exceeds what one pinion can put into the rack at an acceptable stress, a second pinion halves the tooth loading. This is a sizing outcome, not a preference.

Skew. A wide carriage on two rails wants to crab if it is driven from one side. The mechanical answer is one motor driving two pinions through a common shaft, which is what our dual-rail truss manipulators use: rack and pinion mechanisms driven through a common pivot shaft, with V-shape roller guides for dusty and harsh environments. No electronic gearing to tune, and no way for the two sides to disagree. A recent installation in that family runs 4 picking units with 300 mm of Z-axis stroke over 12 m of Y-axis travel at up to 2 m/s and ±0.1 mm positioning repeatability, described on our warehouse and intralogistics page.

Backlash. Rack and pinion has lash by construction. Two servos on one rack, biased against each other so the teeth stay loaded on one flank, removes it electrically, at the cost of continuous current, heat and a tuning exercise. It is genuinely needed only where the axis positions bidirectionally to a tight band under load.

Before paying for that, check the cheaper fix: approach every station from the same direction. A single-direction approach takes most of the backlash error out for the price of a little extra travel, and on a track indexing between fixed stations it often costs nothing.

A different two-drive case is two carriages on one rail, each carrying its own robot, which is a configuration we design where two arms share a working line. Mechanically it is straightforward; the engineering moves to controls, because the envelopes overlap and an anti-collision arrangement between the carriages has to own the interlock.

How Does a Heavy Carriage Change the Safety Distance and the Guarding?

Through stopping performance, which means the guarding scope is decided when the drive is sized rather than when the fence is quoted. That is a cost which arrives late when it is missed.

Start with an ISO 12100 risk assessment driving the design rather than the reverse. The robot and the integrated system are covered by ISO 10218-1:2025 and ISO 10218-2, with each safety function rated for performance level under ISO 13849-1:2023. The 2025 edition is the first substantive revision of ISO 10218-1 since 2011 and it references the 2023 edition of ISO 13849-1, so a design documented against the 2015 edition needs its performance level calculations restated when the machine is reassessed.

Four things then behave differently because the carriage is heavy.

The minimum distance grows. ISO 13855 sets it from the approach speed constant, taken as 2,000 mm/s up to 500 mm and 1,600 mm/s beyond, plus the stopping performance measured on the built machine and a penetration factor. Stopping performance is where mass enters, and a slower stop pushes the scanner field or the fence line outward into floor area you pay rent on.

Plain interlocking may not be enough. Under ISO 14119, where run-down time after the stop command exceeds the time it takes to reach the hazard, the guard needs locking rather than plain interlocking, released by a standstill monitor. Run-down time grows with the mass, so the heavier the carriage the easier that condition is to meet, and solenoid-locking doors are a different bill of materials from switched ones.

Measure, do not calculate, the stopping time. Stopping performance is measured on the built cell, and it is the most important test after a control system retrofit, because a new servo drive on old mechanics changes run-down time in ways no datasheet predicts. A quotation stating a safety distance with no measurement plan behind it is stating an intention.

The hazard is a line, not an envelope. A fixed-base robot has one envelope to guard. A carriage travelling along a rail creates a moving trap against every fixed object beside it for the whole stroke, including the cable carrier trough and the fence structure itself. Reaching distances under ISO 13857 fix mesh aperture against standoff along that entire length, not only at the ends.

One question to put to any supplier: where the arm’s controller carries safe speed monitoring, safe standstill and safe axis range limiting, ask whether those cover the track running as a coordinated external axis or only the arm. The answer changes the safety architecture, and the wider method is on our machine safety and CE marking page.

Singapore does not require CE marking, but the Workplace Safety and Health Act requires dangerous parts of machinery to be securely fenced. We deliver the physical scope that follows: guard fencing, interlocked access doors, safety laser scanners, safety-rated stop circuits, LVD and CE testing, and Ministry of Manpower lifting certification where the machine includes lifting equipment.

What Does Maintaining a Long Rack Actually Involve?

A short axis is maintained by whoever happens to be nearby. A 20 m rack is maintained by design or not at all, because no single standing position reaches it.

Environment decides two of those rows. In dirty or dusty service we use V-groove roller guides rather than recirculating ball guides, because a roller on a V edge sheds debris a ball guide would ingest, and on long-travel builds we standardise on igus chain and flex-rated cable.

How Does Moving Mass Get Analysed Before the Frame Is Committed?

In an order that cannot be reversed cheaply, which is why the analysis belongs in concept review rather than in detail design. The chain runs: moving mass, then required force, then rack module and gearbox, then guide size, then frame section, then brake and buffers, then stopping performance, then the fence line and the cell footprint. Every downstream item is fixed by the one before it. Change the arm at concept review and it is a redraw; change it after the frame is fabricated and it is a new frame.

Three things belong in that analysis and are commonly missing from a quotation.

A written mass budget at worst case. Arm from the vendor datasheet, base plate, dress pack, tool, workpiece at its heaviest, and anything else riding along. Worst case rather than typical, because someone adds a heavier variant next year, and the arm is normally the dominant term.

A duty profile, not a single move. Moves per hour, distance per move and dwell at each station, across the shift pattern the line actually runs. That is what turns a peak torque into an RMS figure, and it is also where transit time gets counted honestly, including the ramp and the settle rather than a catalogue top speed.

Reach verified in offline simulation before anything is built, because a pose that cannot be reached is a mechanical problem rather than a software one. On a track that means checking both ends of the stroke with the dress pack in place.

A supplier who quotes a track length and a payload has quoted a price rather than done the engineering.

When Is a Heavy Duty Track the Wrong Answer?

This is the section that decides whether the rest of the page is worth trusting.

When availability matters more than utilisation. One robot on a track serving three pallet positions gives the throughput of three stations from one arm, and one failure that takes all three lanes down at once. Two robots on fixed bases fail independently. Where a stoppage on one line cannot be allowed to stop the others, buy the second robot, a trade set out in the palletizing robot case study.

When the machines are in a row and the parts drop vertically. Distance is cheap on a beam and expensive on a rail carrying an arm. A gantry travels overhead, leaves the floor clear and extends in modules, and one steel single-beam build with 10 to 30 m of X-axis travel services more than ten CNC machines. If parts enter a chuck vertically and the machines sit in a line, you are paying to move articulation you will not use, as our machine tending automation page sets out.

When the real problem is orientation, not distance. A track adds reach and no dexterity at all. If the part must be presented at an angle or reoriented between operations, more rail will not touch it.

When the takt has no slack. Transit absorbed into a pattern cycle is free. Transit inside a tight takt is a cycle time increase, and a heavy carriage cannot be accelerated out of it for the reasons above.

When you are past the height budget, not the load budget. If the constraint is that a conventional seventh axis eats 200 to 400 mm of vertical working height, the answer is the low-profile design at 100 mm rather than a heavier track, and that is covered on the robot seventh axis and linear track page.

When it is a welding cell. Welding stations are a standard application for a track of this kind. We do not build production welding cells, and that is not a scope we will stretch to win a project.

And where a standard machine or a shorter arm on a fixed base covers the application at a lower price, the useful answer is to say so. Lead time on a build of this shape runs 16 to 24 weeks from concept approval to factory acceptance testing, which is long enough that finding out halfway through is expensive for both of us.

Frequently Asked Questions

What payload can a heavy duty robot track carry?

The heavy-duty track we build is rated to 2,000 kg of platform load and is sized for arms of 500 kg and above, across strokes beyond 20 m, travel speeds to 1.5 m/s and repeat positioning of ±0.1 mm. Platform load is not the same number as robot payload and the two get confused in quotations. Platform load is everything the carriage carries: the arm itself, its base plate, the dress pack, the end-of-arm tool and the workpiece at its heaviest. On a track the arm is usually the largest term in that sum, which is why the arm has to be chosen before the track is sized rather than after.

Why is acceleration on a heavy robot track limited by the rack rather than the motor?

Because all the drive force passes through a few teeth. Motor torque becomes force at the pinion pitch radius, and that force is delivered into the rack across a small contact patch, so tooth root bending and flank contact stress set the ceiling. Force is mass times acceleration, so asking a heavier carriage for the same ramp asks the same teeth to carry proportionally more. A larger motor does not raise that limit, it only reaches it sooner. The usual answers are a longer ramp, a jerk-limited profile that cuts peak force at the same average acceleration, a larger rack module, or accepting a slower transit.

How does a heavy carriage change the guarding around a robot track?

Through stopping performance, which is why the guarding cost is decided at drive sizing rather than at the fence quotation. ISO 13855 sets the minimum distance from the approach speed constant, taken as 2,000 mm/s up to 500 mm and 1,600 mm/s beyond, plus the stopping performance measured on the built machine and a penetration factor. A heavier carriage takes longer to stop, so the distance grows and the fence line moves outward. ISO 14119 adds a second consequence: where run-down time after the stop command exceeds the time it takes to reach the hazard, the guard needs locking rather than plain interlocking, released by a standstill monitor.