Skip to content

Redesign Motorized Joint #126

@michalpelka

Description

@michalpelka

The motorized joint component is POC.
It has multiple features :

  • gathering measurements (e.g. protrusion of cylinder)
  • compute string PID
  • apply torque/force
  • print debug info
  • apply test signals

Describe the solution you'd like
I would like properly designed components. With small, well-defined features.
Example decoupling:

  • Encoder Controller
  • PID Controller
  • Motor Controller
  • Manual Controller (with Dear ImGUI interface)
  • Switch to Joint PhysX API

Additional points:

  • Remove test logic from this class and add a separate ImGUI base component for testing and tuning motorized joint.
  • Remove debug draw entity and use EntityDebugDisplayEventBus instead.

Additional context
Design needs to expose an interface to ROS2: RobotecAI/o3de-ros2-gem#226

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature/roboticsThis item is related to robotics.kind/enhancementEnhancement to an existing feature.priority/majorIssue causes friction in workflows, but can be worked around or avoided. Rare or difficult crashes.sig/simulationCategorizes an issue or PR as relevant to SIG Simulationtriage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions