HUMANOID · Experimental lab

From your idea
to a hardware prototype.

Bring boards, manuals and code into one project. T-Chat supports development; Companion handles the hardware connection. Physical testing remains an explicit step.

HUMANOID is experimental. Software features have been checked using simulated devices; compatibility, compilation, upload and behaviour must be tested on the actual hardware. It is not a certified safety system or universal board support.

Identification

Start with the actual device

Select USB devices detected by Companion and document the board, sensors, power and wiring. Detection cannot automatically infer the entire circuit.

  • Inventory of selected devices and association with the project.
  • Attached manuals as development references.
  • Official guides and datasheet searches only when authorised.

Development

Write, review and retain the code

Describe the desired behaviour in the project chat and define constraints and tests. Keep source code, manifests and manuals in the Workspace so you can return to editing.

  • Private projects with versions and component references.
  • Reusable presets and .thumanoid packages.
  • Imported presets do not automatically inherit hardware permissions or web consent.

Upload

Confirm the right device

Use a compatible toolchain and check the artifact, board and port before uploading through Companion. Generating code does not automatically run firmware on the device.

  • Compilation and upload are separate stages.
  • Authorisation applies to the selected action and device.
  • No automatic actuator restart on reconnection.

Testing

Verify behaviour on the bench

Compiled or uploaded firmware does not prove safe circuit operation. Begin with supervised tests, appropriate power and an accessible physical stop where needed.

  • Check sensors and outputs before introducing movement.
  • Record tests and separate software outcomes from physical results.
  • Assess board requirements before planning onboard autonomy.

Frequently asked questions

Is connecting an Arduino board enough?

No. You need the exact model, components and wiring diagram, plus a compatible toolchain already prepared. USB connection is a starting point, not a complete device check.

Can I reuse a project on another device?

You can export and import the package into a new project. Board identity, configuration and tests must be checked again; permissions do not transfer with the files.

Can a robot work without the Mac?

That depends on the board, firmware and available resources. The initial workflow is Mac-assisted; onboard autonomy requires a separate assessment and testing.

Use cases

Start with a real process.

Choose an activity, prepare a non-sensitive data sample and let’s define the expected outcome, hardware and checks together.

Use cases