AutonomyLab/ardrone_autonomy — pull request #36 by JakobEngel (2012-11-22 10:22:01+00:00)
Title: made loop_rate variable

I need high-frequency and low-latency navdata (full 200HZ sent by the drone), which I get by setting this to e.g. 500. I dont notice any problems / unstabilities; even cpu usage doesnt change significantly.

maybe not the cleanest solution, but doesnt change anything as long as you dont change the loop_rate parameter.

Alternatively, it would be nice to do the ros::publish directly in the SDK callback (navdata_custom_process).