FDCL-GWU UAV Gazebo simulator — device market

Install

Three ways to run this device. Each one serves its fake backend: no instrument, no simulator install and no upstream checkout.

OpenAI4S (one command)

shell

openai4s lab add robots/fdcl-gwu__uav_simulator

Installs the device into the OpenAI4S Lab on its fake backend and starts it. First time? See setup below.

Or, in the workbench, open the Lab tab → Market → Install.

Standalone MHS endpoint

shell

git clone --depth 1 https://github.com/PKU-YuanGroup/OpenMHS.git && cd OpenMHS
PYTHONPATH=MHS/sdk/src python3 -m mhs serve robots/fdcl-gwu__uav_simulator --port 7400
# in a second terminal, from the same directory:
PYTHONPATH=MHS/sdk/src python3 -m mhs describe --endpoint http://127.0.0.1:7400

Serves the device as an MHS endpoint on port 7400 from an OpenMHS clone (Python 3.10 or later, standard library only); describe prints what it offers.

Any MCP host (Claude Desktop, Cursor, …)

mcp configuration

{
  "mcpServers": {
    "uav-simulator": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "robots/fdcl-gwu__uav_simulator",
        "--mcp"
      ],
      "env": {
        "PYTHONPATH": "/path/to/OpenMHS/MHS/sdk/src"
      }
    }
  }
}

Add this server to the host's MCP configuration and replace /path/to/OpenMHS with the path of your OpenMHS clone. The host starts the server and talks to it on stdin and stdout.

What it does

Measures

mode
motors_on
read_state
read_imu

Adjusts

Nothing declared.

Actions

set_flight_mode: Publish one ModeData flight-mode request on /uav/mode; the receipt confirms transmission only, not mode execution, and the publication does not turn the motors on
motors_off: Publish one std_msgs/Bool false on /uav/motors_on, the same publication the e-stop sends; the receipt confirms transmission only, not the sensed confirmation, and repeating it does not turn the motors on

Names as the driver declares them. Units, limits and the safety declaration are in the package's REFERENCE.md.

First-time setup

The OpenAI4S workbench with the OpenMHS lab, from a source checkout:

shell

# OpenAI4S workbench with the OpenMHS lab (source checkout)
git clone --recursive https://github.com/PKU-YuanGroup/OpenAI4S.git
cd OpenAI4S && ./setup.sh && source .venv/bin/activate
openai4s lab add robots/fdcl-gwu__uav_simulator
openai4s serve        # open the Lab tab

The standalone endpoint and the MCP server need only an OpenMHS clone and Python 3.10 or later. More in the market's getting-started guide and on the OpenAI4S host page.

Source and evidence

Upstream: fdcl-gwu/uav_simulator
Pinned commit: 7270fe4e274f
Licence: MIT
Stars: 159
Evidence: contract_checked on the fake backend
Backends: fake

The driver package MHS/drivers/robots/fdcl-gwu__uav_simulator wraps the upstream code at the pinned commit. Its REFERENCE.md documents the full contract: every value, action, unit, limit and the safety declaration.