AimDK Protocol (Link-U OS Robot Interface)

The AimDK protocol is AgiBot's first-party Protocol Buffers definition of its robots' interfaces, published as the aimrt_protocol repository of Link-U OS. It defines 33 gRPC services and 175 RPCs across four domains: hal/ (hardware abstraction — hands and grippers including the OmniHand O10 and AgiClaw, arms, audio, RGB/fill/strip lighting, neck, battery management, temperature, emergency stop, operation mode, RealSense cameras, camera intrinsics and snapshots, MCU fault clearing), mc/ (motion control — locomotion, walking and standing, joint and servo control, forward and inverse kinematics, force primitives, collision and safety, action sequences, planning, simulation and teleoperation from AimMaster, Quest Pro controllers and universal gamepads), hds/ (health and diagnostics — alerts with levels and solutions, module exceptions, process heartbeat and health, system status, fallback), and common/ (SE(2)/SE(3) poses, velocities, accelerations and trajectories, quaternions, RPY, twists, wrenches, joints, odometry, images, timestamps and the shared RPC request/response headers). The same repository also ships 14 ROS 2 .msg and 19 .srv definitions, so the contract is consumable both as native protobuf/gRPC and as ROS 2 interfaces. Endpoints are served by the robot itself over the AimRT runtime on the local network; there is no public cloud host.

API entry from apis.yml

apis.yml Raw ↑
aid: agibot:aimdk-protocol
name: AimDK Protocol (Link-U OS Robot Interface)
description: 'The AimDK protocol is AgiBot''s first-party Protocol Buffers definition of its robots''
  interfaces, published as the aimrt_protocol repository of Link-U OS. It defines 33 gRPC services and
  175 RPCs across four domains: hal/ (hardware abstraction — hands and grippers including the OmniHand
  O10 and AgiClaw, arms, audio, RGB/fill/strip lighting, neck, battery management, temperature, emergency
  stop, operation mode, RealSense cameras, camera intrinsics and snapshots, MCU fault clearing), mc/ (motion
  control — locomotion, walking and standing, joint and servo control, forward and inverse kinematics,
  force primitives, collision and safety, action sequences, planning, simulation and teleoperation from
  AimMaster, Quest Pro controllers and universal gamepads), hds/ (health and diagnostics — alerts with
  levels and solutions, module exceptions, process heartbeat and health, system status, fallback), and
  common/ (SE(2)/SE(3) poses, velocities, accelerations and trajectories, quaternions, RPY, twists, wrenches,
  joints, odometry, images, timestamps and the shared RPC request/response headers). The same repository
  also ships 14 ROS 2 .msg and 19 .srv definitions, so the contract is consumable both as native protobuf/gRPC
  and as ROS 2 interfaces. Endpoints are served by the robot itself over the AimRT runtime on the local
  network; there is no public cloud host.'
humanURL: https://github.com/Link-U-OS/aimrt_protocol
x-endpoint-pattern: on-robot / LAN — AimRT serves the AimDK services from the robot over its configured
  RPC backend (gRPC, HTTP, ROS 2, Zenoh, Iceoryx or shared memory); no public internet base URL is published.
tags:
- Robotics
- gRPC
- Protocol Buffers
- ROS 2
- Motion Control
- Hardware Abstraction
- Diagnostics
properties:
- type: Protobuf
  url: grpc/aimdk/protocol/mc/mc_service.proto
- type: SourceCode
  url: https://github.com/Link-U-OS/aimrt_protocol
- type: Documentation
  url: https://github.com/Link-U-OS/aimrt_protocol/blob/main/document/en/index.md
- type: GettingStarted
  url: https://github.com/Link-U-OS/Link-U-OS/blob/main/document/cn/index.md