This repository was archived by the owner on Apr 24, 2023. It is now read-only.
Motor output from MBED #583
Open
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.
Description
We currently have no idea what values our MBED is sending to the motors, which is kind of scary, and hard to debug controls problems.
This PR does the following:
igvc_msgs::motor_controlmessage type for modelling the MBED output to the motors (0 - 255)igvc.pb.candigvc.pb.hto include the newleft_outputandright_outputfieldsmotor_controllerto extract the motor outputs and publish them.Fixes #403.
Testing steps (If relevant)
Test on Jessii
motor_controlleron Jessii and a joystick node, with wheels decoupledrostopic echo /motor_outputExpectation: It should values corresponding to what you are joysticking
Self Checklist
make format