-
Notifications
You must be signed in to change notification settings - Fork 990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distance sensors: uncrustify and and new sensor type #747
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some changes done by uncrustify a bit strange, but rest looks good.
Next mavlink release planned on friday (2017.7.7).
switch (dist_sen.type) { | ||
case enum_value(MAV_DISTANCE_SENSOR::LASER): | ||
case enum_value(MAV_DISTANCE_SENSOR::RADAR): | ||
case enum_value(MAV_DISTANCE_SENSOR::UNKNOWN): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why unknown assumed as IR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the most common type on copter are 1-D Lidar that are laser type and IR on ROS. So that is why I chose this. Another posibillity could be to add another parameter on the config file. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another posibillity could be to add another parameter on the config file.
What parameter would that be?
Seems that Travis was broken:
|
Yeah. But this can get in now, as Mavlink is already on deb packages. |
need new mavlink released for : mavlink/mavlink@35a89a2