Skip to main content

Reference: CAN ID and Model Cheatsheet

Why This Matters

Correct motor configuration requires matching:
  1. Model string - Motor type identifier
  2. Motor ID - CAN command ID
  3. Feedback ID - CAN response ID
Wrong values = no communication or wrong motor controlled.

Quick Discovery Workflow

Damiao Configuration

Model Strings

CAN ID Convention

Example Code

Serial Bridge Setup

RobStride Configuration

Model Strings

RobStride uses one upper-level command shape across RS models. Parameter read/write in MotorBridge v0.5.0 uses the common protocol section 4 runtime table (0x7005..0x702E). For the complete text tables used by the runtime encoder/decoder, see RobStride Parameter Tables.
Protocol ID roles: RobStride has three protocol paths — the private extended-frame path (default), the CANopen/CiA402 path (F_CMD=1, robstride_cia402, experimental), and the MIT path (F_CMD=2, robstride_mit, experimental). The feedback_id is the host/responder ID, not the motor/device ID. On Windows PCAN, scans probe one host/feedback ID at a time to avoid competing receive workers on the same CAN channel.

CAN ID Convention

Example Code

MyActuator Configuration

Model Strings

CAN ID Convention

Example Code

HighTorque Configuration

Model Strings

CAN ID Convention

Example Code

Hexfellow Configuration

Model Strings

CAN ID Convention

Hexfellow motors require CAN-FD transport. Standard SocketCAN will not work.

Example Code

Common ID Combinations

Single Damiao Motor

Multi-Motor Damiao Leg

4-Motor Quadruped Leg

Mixed Vendor System

ID Configuration Tools

Scan for IDs

Dump Register IDs

Change IDs (Damiao)

Change ID (RobStride)

Troubleshooting ID Issues

No Response from Motor

Check:
  1. Motor powered on
  2. CAN wiring correct
  3. Correct motor_id
  4. Correct feedback_id
  5. Correct model string

Wrong Motor Moves

Cause: Multiple motors with same ID or wrong ID in config. Solution:
  1. Power on one motor at a time
  2. Scan and record IDs
  3. Use id-set to change conflicting IDs

Intermittent Response

Causes:
  • Loose CAN wiring
  • Missing termination resistors
  • CAN bitrate mismatch
Solutions:

Configuration Template

See Also