Mobvynt fits your existing stack.

MV Bridge connects to your ROS 2 robot, your fleet management system, and your WMS without touching firmware or middleware. 12+ tested configurations.

MV Bridge Mobvynt ROS 2 Nav2 topics WMS timing windows Fleet Mgmt REST / MQTT Sensor Hardware LiDAR / Camera

ROS 2 Native — standard Nav2 topics

Mobvynt publishes and subscribes to standard ROS 2 Navigation2 topics. No custom middleware fork. No firmware changes.

Supported versions: Humble (22.04 LTS), Iron, Jazzy. Tested against standard Navigation2 action server and topic interfaces.

Subscribe

/scan /camera/image_raw /odom

Publish

/cmd_vel /mobvynt/obstacles /mobvynt/path

ROS 2 Launch Snippet

# mobvynt_launch.py
from launch import LaunchDescription
from launch_ros.actions import Node

def generate_launch_description():
    return LaunchDescription([
        Node(
            package='mobvynt_perception',
            executable='perception_node',
            name='mobvynt_perception',
            parameters=[{
                'sensor_mode': 'lidar_2d',
                'risk_tolerance': 0.7,
            }]
        ),
    ])

12+ tested fleet systems

MV Bridge connects via REST API or MQTT. Native support for the two largest warehouse AMR fleet platforms; tested configurations for the rest.

Locus Robotics FleetKeeper native
6RS Chuck Fleet native
inVia Robotics tested
GreyOrange Butler tested
Fetch Robotics FetchCore tested
VGo Fleet API tested
OTTO Fleet Manager tested
Custom / Open API in progress

WMS timing window input

Mobvynt receives pick-slot timing windows from your WMS. The timing window is used by MV Plan to enforce arrival deadline constraints.

Accepts: REST endpoint push, MQTT order event, or local file polling for legacy WMS systems. The timing window feeds directly into MV Plan's constraint solver.

Each pick slot includes an arrival deadline in UTC. MV Plan threads this constraint alongside obstacle clearance — configurable risk tolerance controls how aggressively the planner trades safety margin for deadline adherence.

Sample JSON Payload

{
  "route_id": "RT-2847",
  "robot_id": "AMR-12",
  "pick_slots": [
    {
      "slot_id": "PICK-07-B3",
      "deadline_utc": "2026-01-15T14:32:00Z",
      "priority": 1
    },
    {
      "slot_id": "PICK-12-A1",
      "deadline_utc": "2026-01-15T14:35:00Z",
      "priority": 2
    }
  ]
}

Tested robot hardware

Minimum compute: ARM Cortex-A72 or Intel Atom class, 4GB RAM, Ubuntu 22.04 + ROS 2 Humble.

Clearpath Husky MiR 100 MiR 200 MiR 250 Fetch Freight 100 Fetch Freight 500 Boston Dynamics Spot (warehouse) OTTO 100 OTTO 1500 Geek+ P-series (open API)

Don't see your platform?

Tell us what you're running. If it speaks ROS 2, we can almost certainly integrate. We'll give you a direct answer about what custom work, if any, would be needed.