Skip to content
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_SENSOR adopting #2200

Closed
wants to merge 61 commits into from
Closed

DISTANCE_SENSOR adopting #2200

wants to merge 61 commits into from

Conversation

TSC21
Copy link
Member

@TSC21 TSC21 commented May 19, 2015

[work in progress] This PR pretends to add DISTANCE_SENSOR msg as the main message for pub range sensor data, being altimeters or side sensors for obsavoid.

*/
struct distance_sensor_s {

uint32_t time_boot_ms; /**< Time since system boot */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please put this into the msg folder and let it auto-generate.

@TSC21
Copy link
Member Author

TSC21 commented May 20, 2015

@LorenzMeier can you please do a mavlink release so I can add msg.type = MAV_DISTANCE_SENSOR_INFRARED to mavlink/mavlink_messages.cpp? Thanks

@mhkabir
Copy link
Member

mhkabir commented May 20, 2015

@TSC21 Can you please remove the auto-generated uorb topic file. :)

@TSC21
Copy link
Member Author

TSC21 commented May 20, 2015

Remove? Lorenz asked me in a comment to add it :D

@vooon
Copy link
Contributor

vooon commented May 20, 2015

@TSC21 @mhkabir mean remove .h-file, now it generates from .msg-file.

@TSC21
Copy link
Member Author

TSC21 commented May 20, 2015

OK I understood now. I was comparing the .h in the repo vs the ones generated and checked that the autogenerated ones are not in the repo. Thanks for warning me ;)

@LorenzMeier
Copy link
Member

I updated the mavlink lib on master.

@TSC21
Copy link
Member Author

TSC21 commented May 21, 2015

@LorenzMeier thanks!

@TSC21
Copy link
Member Author

TSC21 commented May 24, 2015

I'm closing this PR, as #2224 is the current one!

@TSC21 TSC21 closed this May 24, 2015
@bansiesta
Copy link
Contributor

@Zefz and @TSC21: thanks for the work here. I made a bunch of changes, mostly to the LidarLitePWM, and finally got the PWM driver running in #2224 which is now merged.

@TSC21 TSC21 deleted the distance_sensor branch May 26, 2015 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants