Source: https://broxme.com/robotics-sdk

In development 

# Broxme Robotics SDK

We’re developing interfaces for tools that extend Studio workflows and connect robotics projects to other software and devices.

Studio’s internal extension contracts inform this work. Public packages, versioned APIs, and compatibility commitments are planned.

[Explore SDK Development](https://broxme.com/robotics-sdk#development) [Read developer guidance](https://broxme.com/developers#documentation)

Focus Areas 

## What the SDK is intended to support.

The SDK direction builds on Studio’s engineering work on interfaces and extensions.

### Clear Interfaces

Understandable programming contracts and reusable abstractions.

### Hardware Adapters

A structured approach to integrating boards, sensors, and robot platforms as support is validated.

### Simulation Compatibility

Consistent project workflows between virtual environments and supported physical systems.

### Developer Extensibility

A path toward custom tools, extensions, and community contributions.

### Documentation

Examples, integration guidance, and clear compatibility information for tested interfaces.

Integration design 

## Define what an adapter expects and returns.

These are design considerations for the SDK’s developing interfaces. An adapter needs an explicit contract for what data it accepts, how it handles delayed messages, and what callers can observe when it loses a connection.

### Units and coordinate frames

State the unit, frame, timestamp, and valid range for each measurement and command. Check conversions with a known pose before feeding sensor data to a planner. ROS REP 103 defines common SI units and coordinate conventions used in ROS.

[Read ROS REP 103](https://github.com/ros-infrastructure/rep/blob/master/rep-0103.rst)

### Delivery and freshness

Set acceptable age and delivery behavior per data stream. A high-rate sensor stream can often tolerate dropped samples, while its consumer still needs to detect stale data. When evaluating a ROS 2 bridge, verify compatible quality-of-service settings at both ends.

[Read ROS 2 quality-of-service guidance](https://github.com/ros2/ros2_documentation/blob/jazzy/source/Concepts/Intermediate/About-Quality-of-Service-Settings.rst)

### Recovery and compatibility

Test startup, interruption, reconnection, and shutdown with a simulated endpoint. Define the expected result for unsupported versions, invalid input, and a device that reconnects during a run. Repeat the checks on each supported physical configuration before claiming device compatibility.

[Review Broxme’s integration boundaries](https://broxme.com/robotics-development-guide#compatibility)

In Development 

## What the engineering build establishes.

Studio’s engineering work on extensions includes a sandboxed runtime and a limited read-only host interface. The public Robotics SDK is in development.

### Extension foundation

The engineering build verifies signed extension packages and checks what each extension is allowed to access.

### Public API development

Release work includes defining versioned contracts, examples, and compatibility information.

### Engineering guide

Read how projects, programs, and recordings fit together in the current engineering build.

[Read the guide](https://broxme.com/robotics-development-guide)

## Follow the SDK’s development.

See what the Studio engineering build supports and what a public SDK release still requires.

[Explore SDK Development](https://broxme.com/robotics-sdk#development)