Picking the right robot for the patrol route

Most patrol and inspection routes could be automated by more than one kind of robot, and the format you choose decides how much of the round a single machine can cover. The route itself holds the answer.

How to read your route

Before comparing robots, walk the round, on foot or on the site plan, and break it into sections. Real industrial routes are rarely one kind of terrain:

• Long flat stretches. Perimeter roads, plant floors, and yards, often measured in hundreds of metres, where speed and battery efficiency per metre dominate.
• Ramps and loading bays. Graded surfaces and thresholds that can slow down robots.
• Stairs, kerbs, and debris. The transitions that end an inspection for anything that cannot step.
• Confined sections. Tight tanks, ducts, and crawl spaces where the entry aperture, not the terrain, sets the hard limit.

The winning format is the one that covers the majority of your route without a detour or a handover. The table below shows how the three formats handle each section type.

When the wheel-legged quadruped is the pick

For most mixed-terrain routes, the answer is a wheel-legged quadruped, sometimes called a wheeled quadruped or hybrid quadruped. On the flat, it rolls: wheels move a robot faster than a walking gait and use less energy per metre, so it covers perimeter roads and plant floors quickly and stretches each charge across more of the round. At the transitions, it steps: up the staircase, over the kerb, through the clutter, matching everything a purely legged robot can do. It is not a compromise between the two formats; it is both of them in one platform.

If you already own a legged robot, like the Unitree Go2, this may still be the most cost-effective option rather than investing in new hardware. A legged quadruped can walk almost every route a wheel-legged robot can, but is often slower and less efficient, splitting routes across multiple charges.

The wheel-legged robot pays off wherever distance and terrain changes coexist:

• Perimeter and security patrols. Long outdoor loops on roads and hardstanding, with the occasional kerb or step where legs take over.
• Yards and outdoor storage. Large flat areas where a walking robot spends most of its battery simply covering ground.
• Plant floors connected by stairs or ramps. Multi-level facilities where one robot can cover levels a wheeled platform cannot reach.
• Ramped logistics sites. Loading bays, dock ramps, and warehouse aisles that mix smooth floors with thresholds and gradients.

Like every capable quadruped, wheel-legged models can be augmented with inspection payloads: cameras for visual checks, thermal imagers for hotspot detection, and gas sensors where atmosphere matters. Because one robot covers the whole round, a single payload set collects the full route's data in one run, captured from the same positions every time so readings stay comparable between patrols.

When a compact rover is the pick

Confined spaces flip the decision. Inside a tight tank, a duct, or a crawl space, the entry aperture and internal clearances matter more than terrain capability, and a small rover fits where even a crouching quadruped cannot. On a flat tank floor there are no stairs to climb, so the rover can glide along and its compact footprint becomes the deciding strength. Our confined space inspection solution covers this workflow in full. OLO natively supports Fictionlab's Leo Rover, a ROS 2-native platform well suited to cramped or hard-to-access inspection routes, so the confined sections of a site run on the same mission software as everything else. A conventional wheeled robot also competes on a route that is entirely flat and obstacle-free, but real sites rarely stay that way for long.

Choosing a specific model

Several manufacturers now ship wheeled variants alongside their legged ranges, such as the DEEP Robotics Lynx M20, and the Unitree A2-W or Go2-W. The buying rules are the same as for any quadruped: confirm the exact SKU exposes SDK and ROS 2 interfaces rather than app-only teleoperation. Our guide to ROS 2 quadruped inspection covers variant selection, SDK access, and the build-vs-buy software decision in detail; everything there applies to the wheeled models too.

From teleoperation to scheduled patrols

No inspection robot, whichever format you pick, ships with the mission layer. That is what automated security patrol software like the OLO platform adds.

Whichever robot you choose, OLO connects to it through ROS 2, and supported models work from first use. Everything happens in the browser. Start by rehearsing the patrol in simulation against a 3D model of your site, then drive the robot around the real thing to build a SLAM map. Place your waypoints, tell the robot what to do at each one, and put the patrol on a schedule. From there it runs on its own, wheels on the flat and legs on the stairs, while you watch the live feeds and dig into the timestamped ROSBag recording after each round. Nobody needs to write ROS code for any of this, though typed Python and TypeScript SDKs are there when your developers want custom behaviour. Enterprise plans start at £175 per seat per month, and a free trial lets you evaluate the workflow in simulation first.

Getting started

If you are still weighing automated patrols against manual rounds, our robotic vs manual inspection comparison works through the consistency, safety, and cost cases. Once the case is made, the fastest evaluation path does not need the robot at all: OLO's simulation runs in the browser, so you can watch your chosen robot patrol your own site virtually before purchase. Bring a 3D model of the environment, book a session with the team, and make the buying decision with the mission already proven.