Fix conflicting multicopter controllers via launch-time selection #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The model.sdf contained both
MulticopterAttitudeControlandMulticopterAccelerationControlplugins running simultaneously. Both publish tocommand/motor_speedand control the same rotors, causing conflicts when users send commands to multiple topics.Changes
Separated controller configurations into dedicated model files:
model_attitude.sdf- attitude controller only (subscribes tocmd/att)model_acceleration.sdf- acceleration controller only (subscribes tocmd/acc)model.sdf- now contains only attitude controller for backward compatibilityAdded launch-time controller selection:
controllerargument instart_sim.launch.xml(defaults toattitude)model_$(var controller).sdfbased on user selectionDocumentation:
CONTROLLERS.md- detailed controller comparison and usageREADME.mdwith selection examplesUsage
Only one controller loads per instance, preventing motor command conflicts.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.