Robots · Mobile robots

Duke Humanoid V1 (biped_controller.BipedController)

Duke Humanoid V1 (biped_controller.BipedController), adapted from generalroboticslab/dukehumanoidhardwarecontrol. It reads joint_positions, joint_velocities, joint_currents, dof_position_target and 6 more; sets command_forward, command_lateral and command_yaw; runs control_step and halt. control_step: run one closed-loop control step: update the command, refresh the observation, compute the policy action and write the motor target. A hardware driver: the market serves its fake backend, so no instrument is needed.

hardwareRisk R2licence not assertedcontract_checkedserved on the fake backend
openai4s lab add robots/generalroboticslab__dukehumanoidhardwarecontrol

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/generalroboticslab__dukehumanoidhardwarecontrol

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/generalroboticslab__dukehumanoidhardwarecontrol --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": {
    "dukehumanoidhardwarecontrol": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "robots/generalroboticslab__dukehumanoidhardwarecontrol",
        "--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

  • joint_positions
  • joint_velocities
  • joint_currents
  • dof_position_target
  • foot_force_raw
  • foot_contact
  • angular_velocity
  • gravity_vector
  • base_quaternion
  • sample_rate

Adjusts

  • command_forward
  • command_lateral
  • command_yaw

Actions

control_step
Run one closed-loop control step: update the command, refresh the observation, compute the policy action and write the motor target
halt
Stop the motors: set every motor's torque limit to 0 and end the EtherCAT motor loop, the first two steps of the upstream's check_termination

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/generalroboticslab__dukehumanoidhardwarecontrol
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

Pinned commit
3a9c3cd4c8da
Licence
NOASSERTION
Stars
0
Evidence
contract_checked on the fake backend
Backends
fake, hardware

The upstream repository asserts no licence (NOASSERTION); check it before you redistribute the upstream code.

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