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.
What is this
Our real-world system has (partly, mainly beetle) supported ESC telemetry, but the simulation does not support. Thus, this PR adds a publisher and two msgs to pub the ESC data.
Details
Add a "krpm_rate" to yaml config with (kRPM)^2/N unit.
I find the original equation for rotor speed is "force_ * speed_rate_", which is incorrect, since the thrust is proportional to the square of the motor speed. However, when I change it to the correct equation, the robot may diverge in simulation and I don't know why.
Hence, I add an additional topic to convert the thrust directly to RPM.
TODO