Factory Docs

Factory Docs

Open in ChatGPT
Ask ChatGPT about this page
Open in Claude
Ask Claude about this page

MIR200 Autonomous Mobile Robot

Overview

The MiR200 is an Autonomous Mobile Robot (AMR) manufactured by Mobile Industrial Robots (MiR). It is designed for autonomous material transport in indoor environments and serves as a mobile robotics platform for manufacturing, logistics, automation, and research applications.

Within our research infrastructure, the MiR200 is used as an autonomous mobile platform for investigating manufacturing automation and co-robotics.

Note: Although the MiR200 is sometimes referred to as an AGV, it is more accurately classified as an AMR. Unlike a traditional AGV that follows a fixed physical path, the MiR200 localizes itself within a map, plans routes, detects obstacles, and dynamically navigates through the environment.


Specifications

Parameter MiR200
Maximum payload 200 kg / 440 lb
Towing capacity 500 kg / 1,100 lb
Dimensions 890 × 580 × 352 mm
Ground clearance 50 mm
Maximum forward speed 1.1 m/s / 4 km/h
Maximum reverse speed 0.3 m/s / 1 km/h
Positioning accuracy ±50 mm
Docking accuracy ±10 mm
Battery Li-NMC, 24 V, 40 Ah
Typical operating time Up to ~8–10 hours depending on load/configuration
Environment Indoor
IP rating IP20
Communication Wi-Fi, Ethernet, Bluetooth
Integration protocols REST API, Modbus

Runtime figures vary between MiR specification revisions and operating conditions, so the battery runtime should be treated as approximate.


Sensors

The MiR200 combines several sensor systems for localization, navigation, obstacle detection, and personnel safety.

Safety laser scanners

Two SICK S300 safety laser scanners are mounted at the front and rear of the robot. Together they provide 360° safety coverage around the robot.

The scanners define protective fields around the vehicle. The active field changes according to the robot's velocity: higher speeds require a larger protective region.

If an obstacle or person enters the active protective field, the robot enters a Protective Stop.

3D cameras

The MiR200 uses two Intel RealSense 3D cameras to detect obstacles above the plane monitored by the laser scanners.

Ultrasonic sensors

Four ultrasonic sensors supplement the laser and camera systems, particularly for objects whose optical properties can make them difficult to detect.


The MiR200 navigates using a stored map of the environment together with sensor observations from the robot.

Localization relies heavily on recognizable static landmarks, such as:

  • walls
  • corners
  • columns
  • doorways
  • shelving
  • other permanent structures

The localization system estimates the robot's location by comparing sensed features against features represented on the map.

Good mapping environments

The MiR200 performs best where the environment contains multiple distinct static features.

For example:

      Shelf
+----------------+
|
|        +-----+
|        |     | Column
|        +-----+
|
+------ Door --------

Corners, columns, doors, and other geometric features provide useful localization references.

Problematic environments

Localization can become less reliable in areas containing:

  • long featureless corridors
  • large uninterrupted walls
  • large numbers of moving objects
  • substantial changes to the mapped environment
  • highly reflective surfaces
  • transparent objects
  • strong direct sunlight

When initializing the robot, ensure its indicated position and orientation on the map correspond reasonably closely to its physical position.


Robot Interface

Most configuration and operation of the MiR200 is performed through its browser-based robot interface.

The interface provides access to functions including:

  • maps
  • positions
  • missions
  • mission queues
  • robot state
  • manual driving
  • hardware health
  • error information
  • users
  • system configuration

The interface can be accessed from a computer connected to a network from which the robot is reachable.

Operator PC
     |
     | HTTP / REST
     v
+------------------+
|      MiR200      |
|                  |
| Robot Interface  |
| Mission System   |
| Navigation       |
| Safety System    |
+------------------+

The robot's IP address depends on its network configuration.


Maps

A map represents the operating environment in which the robot localizes and navigates.

Maps should accurately describe static structures while excluding objects that move regularly.

Important mapping considerations

When preparing a map:

  1. Preserve useful static landmarks.
  2. Remove transient obstacles from the finished map.
  3. Confirm walls and fixed structures correspond to the real environment.
  4. Check narrow corridors and doorways.
  5. Verify that the robot can successfully localize throughout the operating area.
  6. Test all intended routes under realistic operating conditions.

A technically valid map is not necessarily a reliable operational map. Always validate navigation experimentally.


Positions

A Position is a defined pose on a MiR map that can be referenced by missions.

Positions are useful for repeatable destinations such as:

  • workstations
  • loading areas
  • unloading areas
  • inspection stations
  • robot cells
  • waiting locations
  • charging stations
  • docking locations

Conceptually, a position represents:

Position = (x, y, orientation)

Missions should normally reference named positions rather than depending on manually entered coordinates.


Missions

A Mission is a programmable sequence of actions executed by the MiR200.

A simple transport mission might conceptually look like:

Move to Loading Station
        |
        v
Wait for Load
        |
        v
Move to Processing Station
        |
        v
Signal External Equipment
        |
        v
Return to Standby

Missions can be used to construct repeatable autonomous workflows rather than manually controlling the robot.

When developing missions, build and test them incrementally. A useful sequence is:

  1. Verify localization.
  2. Test navigation to individual positions.
  3. Add mission logic.
  4. Test interactions with external equipment.
  5. Test abnormal conditions.
  6. Test recovery behavior.
  7. Run the complete workflow under realistic traffic conditions.

External Integration

The MiR platform can be integrated with other automation and research systems using network interfaces including the MiR REST API and Modbus.

A typical research architecture may look like:

                 +-------------------+
                 | Research Software |
                 | / Orchestrator    |
                 +---------+---------+
                           |
                        REST API
                           |
                           v
+-----------+       +------+-------+       +-------------+
| Sensors / | <---> |    MiR200    | <---> | Workstation |
| Equipment |       |              |       | / Robot Cell|
+-----------+       +--------------+       +-------------+

This allows higher-level software to coordinate the mobile robot with manufacturing equipment, sensors, manipulators, or experimental systems while leaving low-level navigation and safety behavior on the MiR controller.


Safety System

The MiR200 contains a dedicated safety system controlled primarily by a safety PLC.

Its built-in safety functions include:

  • collision avoidance
  • overspeed avoidance
  • drive stability monitoring
  • emergency-stop monitoring
  • speed-dependent protective fields

Safety-related functions are designed around ISO 13849-1 and support installations designed in accordance with standards including ISO 3691-4.

Types of Stop

Operational Stop

The robot has been stopped normally through the robot interface or mission logic.

Power may still be available to the robot and attached equipment.

Protective Stop

The safety system automatically stops the robot because a safety condition has been detected.

Common causes include:

  • an obstacle entering a protective scanner field
  • a safety-system fault
  • a motor-control discrepancy
  • startup/reset conditions

If an obstacle triggered the stop, the robot can resume after the protective field has been clear for the required period.

Emergency Stop

An Emergency Stop is initiated through the physical emergency-stop circuit.

This state removes power from relevant motion systems through the robot's safety circuitry.

Do not use the Emergency Stop as the normal method of stopping the robot.


Operating Safety

Before operating the MiR200:

  • Ensure the operating area is suitable for autonomous navigation.
  • Verify Emergency Stop functionality.
  • Inspect the robot for obvious mechanical or electrical damage.
  • Confirm the robot is correctly localized.
  • Confirm the intended mission and payload configuration.
  • Ensure paths, doors, and docking areas provide sufficient clearance.
  • Keep personnel clear of operating hazard zones.

Do not modify SICK safety scanner protective-field configurations without performing the required safety engineering and risk assessment. Modifications to the safety configuration can invalidate the assumptions under which the robot's safety system was certified.

Any new payload, top module, manipulator, or other mechanical integration should be considered part of the overall machine and evaluated accordingly.


Environmental Considerations

The MiR200 is intended for indoor operation.

Pay particular attention to:

Floor condition

The floor should be dry and provide adequate traction.

Slippery floors can affect braking and vehicle stability.

Reflective and transparent objects

Glass, polished surfaces, and other transparent or highly reflective objects can reduce sensor performance.

Lighting

Strong sunlight can interfere with optical sensing.

Dust and contamination

The MiR200 is rated IP20 and should not be treated as a sealed industrial vehicle.

Geometry

Validate:

  • inclines
  • thresholds
  • floor gaps
  • door widths
  • corridor widths
  • turning areas
  • docking areas

with the actual robot and payload configuration.


Charging

The MiR200 supports autonomous charging using a MiR charging station as well as cable charging.

For autonomous operation, missions can be designed so that the robot returns to a charger when required.

Battery endurance depends on factors including:

  • payload
  • acceleration
  • travel distance
  • floor conditions
  • mission behavior
  • auxiliary equipment
  • battery condition

For research deployments, battery state should therefore be treated as an operational variable rather than assuming the nominal runtime.


Troubleshooting

Robot will not move

Check:

  1. Emergency Stop state.
  2. Protective Stop state.
  3. Robot operating mode.
  4. Active errors.
  5. Monitoring > Hardware health.
  6. Whether an obstacle is inside a safety scanner field.
  7. Localization quality.

Robot repeatedly loses localization

Check:

  • starting pose on the map
  • changed or moved landmarks
  • large dynamic obstacles
  • long featureless walls
  • reflective surfaces
  • scanner obstruction
  • whether the physical environment still matches the map

Robot stops unexpectedly

Check Hardware health and determine whether the event is:

  • an operational stop
  • a protective stop
  • an emergency stop

Do not repeatedly reset safety faults without identifying their cause.

Test the problem separately as:

  1. localization,
  2. global path planning,
  3. local obstacle avoidance,
  4. mission logic.

Separating these layers usually makes MiR navigation problems substantially easier to diagnose.


Research Use

The MiR200 is particularly useful as a research platform because navigation and safety can remain under the MiR controller while experimental systems operate at a higher level.

Possible research uses include:

  • autonomous material handling
  • human-robot interaction
  • flexible manufacturing
  • mobile manipulation
  • robot fleet coordination
  • machine tending
  • sensor-data collection
  • manufacturing logistics
  • human-aware navigation
  • coordination between mobile and stationary robots

For experimental integrations, prefer communicating with the MiR through its supported software interfaces rather than bypassing its navigation or safety systems.


References

  • Mobile Industrial Robots, MiR200 User Guide, revision 3.1, October 2020.
  • Mobile Industrial Robots, MiR200 Specifications.
  • ISO 3691-4, Industrial trucks — Safety requirements and verification — Driverless industrial trucks and their systems.
  • ISO 13849-1, Safety of machinery — Safety-related parts of control systems.
Last updated 2 days ago
Was this helpful?
Thanks!