-
Notifications
You must be signed in to change notification settings - Fork 986
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
Remove boost::asio from plugin code (UAS breaking) #59
Comments
List of plugins that use TimerService:
|
Sys_status and waypoint done. Param require some refactoring. |
Also move message rx to it's own handlers. Issue #59.
Also add some debug messages for next debugging PX4. Issue #59.
As said in #1041 from PX4 Firmware, CON goes down immediately when it enters position lock. Meaning that when it (the PX4) receives the first vision_estimate, the connection is lost. Till then it works ok! |
@vooon OK, Libev seems to cause a slowdown too :( I am streaming a message a 200Hz from PX4. On boost::asio I got the full 200 Hz rate, but with libev, it seems to get limited at ~160Hz |
@mhkabir Can you show system load produced by Use |
@mhkabir does the connection is also lost when your Pixhawk enters position lock? |
No, but I am not using tf messages, just PoseWithCovarianceStamped @ 200Hz On Wed, Jul 23, 2014 at 8:18 PM, TSC21 notifications@github.com wrote:
|
Where the hell do you get a pose estimation at that rate? :D ---Nuno MarquesAlferes Aluno de TransmissõesAluno de Mestrado em Engenharia Electrotécnica e de ComputadoresInstituto Superior Técnico | Universidade de Lisboa Date: Wed, 23 Jul 2014 08:53:57 -0700 No, but I am not using tf messages, just PoseWithCovarianceStamped @ 200Hz update. On Wed, Jul 23, 2014 at 8:18 PM, TSC21 notifications@github.com wrote:
— |
Semi-direct visual odometry fused with IMU correction. |
Using PTAM? |
SVO On Wed, Jul 23, 2014 at 9:57 PM, TSC21 notifications@github.com wrote:
|
After removing asio from mavconn (#54) need to remove it from UAS and plugins.
The text was updated successfully, but these errors were encountered: