Skip to content

Developer Hub

FAQ and Support

Support

For product and integration support, contact PULSAR HRI:

Include the actuator model, firmware version, host operating system, connection type, and a concise description of what happened.

For Developer Hub bugs or documentation requests, open an issue:

github.com/PulsarHRI/pulsarhri.github.io/issues

Do not post credentials, private packages, serial numbers, or other sensitive information in a public issue.

Frequently asked questions

Which interface should I use first?

Use Pulsar App for one physical actuator without code, direct USB with Pulsar Python SDK for Python development, CAN FD for several physical actuators, and VirtualWorld when no hardware is available and you want to explore the actuator's performance to your specific project.

Which firmware is required by Pulsar SDK?

Physical actuators require firmware 2.0.4 or newer. Update Firmware if an update is needed.

Is macOS supported?

No. Current supported hosts are Linux x86_64, Linux ARM64, and Windows x86_64.

Does Pulsar App control virtual actuators?

No. Pulsar App currently controls one physical actuator at a time through USB. Use Pulsar SDK for other phsycal/virtual actuators needs.

Do you support EtherCAT?

EtherCAT support is planned for Q1 2027 through native board integration, or through an EtherCAT-to-CAN adapter if you own CAN-based Pulsar Actuator.

Where are the Rust SDK docs?

The Pulsar Rust SDK is coming soon. Its section will be expanded when the crate, examples, and reference are released.

Open Pulsar Python SDK issues

The following issues are currently tracked for Pulsar Python SDK and will be fixed in a future release:

  • #1 — Reconnect isolation: queued transport-loss handling affects a newly reconnected actuator session.
  • #2 — Physical-domain validation: PulsarActuatorReal doesn't reject VirtualWorld as a domain.
  • #3 — Stale telemetry recovery: enable() is allowed to recover the actuators to operational state without clearing the faults first.
  • #4 — Co-simulation ergonomics: a future bulk exchange helper should return elapsed ticks and telemetry while retaining the low-level step() API.

For help with a current application, use Support or open an issue in the Developer Hub repository.