Open Source RoboticsRobots, software & learning

Climb-SDK

Software

Climb-SDK supplies planning/control and robot-interface code for climbing research, originally developed for LORIS. [1] [2] [3] [4]

Installation & first result →Official websiteGetting started

For
Robotics developers investigating the named source configuration [1] [2] [3] [4]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

Climb-SDK supplies planning/control and robot-interface code for climbing research, originally developed for LORIS. Its useful starting point is an inspectable source workflow, not an independently verified climbing robot or manufacturing release. [1]

Is this for you?

Known limitations
  • Failedhardwareconnection auto-switches toDummyInterface; runningstack isnot physicalconnectionproof.
  • SoftwareSDKnotLORISmanufacturingdesign; noautonomousclimbing/forcecontrol verified.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] · Editorial assessment

What you need

Operating system
  • Ubuntu 24.04 (upstream ROS 2 Jazzy environment)

Documented source requirements/route, not installation or compatibility reproduced by this catalog.

[1]

Dependencies
  • UpstreamROS2Jazzy/Ubuntu24.04; colconworkspace/setup dependencies
  • LORISconfiguration andexplicitoffline-vs-hardware interface selection

[1] [2] [3] [4]

Installation & first result

Open the upstream getting-started guide [1] [2] [3] [4]

  • Inspect the named configuration, source interfaces and required external components.
  • Attempt only the matched documented workflow after resolving environment and rights gaps; no operation reproduced here.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] · Editorial assessment

Installation

Documented ROS 2 colcon workspace/source checkout, setup.sh, build and source route; Docker alternative is separate and neither was executed.

Documented source requirements/route, not installation or compatibility reproduced by this catalog.

[1]

Project notes

Select the documented environment and offline task

The README reports testing with ROS 2 Jazzy on Ubuntu 24.04. Its source route creates a colcon workspace, clones the repository, runs setup.sh and builds/sources packages. Those commands and the Docker alternative were not executed here. Current dependency resolution and device support still need a matched environment. [1]

For an offline investigation, it documents climber_plan.launch.py with camera:=false and a command sequence beginning simulate tube, followed by planning/control/execution commands. That is a simulation/source workflow. It does not establish a physical camera, valid grasp contact or autonomous climbing in this review. [1]

A hardware launch can fall back to a dummy interface

The base launch selects robot description/configuration and starts the robot driver. In the inspected HardwareNode source, a failed interface connection is logged, then the implementation is replaced with DummyInterface, connected and enabled. The source explicitly logs that switch. A live process or plausible joint output therefore cannot be taken as evidence that hardware connected; inspect the actual interface and logs before interpreting a result. [3] [4]

That fallback is upstream implementation evidence, not a failure reproduced by this catalog or an assertion that all source paths are simulated. No ROS node, actuator interface, camera, contact-force loop, footstep plan, physical climbing or recovery test was run. [4]

The MIT notice concerns the SDK contribution. It does not establish rights or setup requirements for external LORIS geometry, bought-in actuators/sensors or dependencies; inspect the relevant component documentation separately. [2]

What we checked

Pinned source/document inspection only; no installation, compile, credentials/API use, simulator, lab experiment or physical hardware test.

Not yet established

  • Requirements: host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
5b5fbba

Source files and licenses

Concrete scoped robot-facing software/research workflow, not complete manufacturing or verified operational behavior.

LayerAvailability / license
softwareavailable · MIT
Selected source availability/notice only; external hardware, models, data and dependencies have separate rights. No blanket redistribution or operational clearance. [1] [2] [3] [4]
documentationavailable · MIT
Selected source availability/notice only; external hardware, models, data and dependencies have separate rights. No blanket redistribution or operational clearance. [1] [2] [3] [4]

No separate physical design, pretrained distribution or dataset is selected as the released contribution in this scoped software review.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history