-
Notifications
You must be signed in to change notification settings - Fork 99
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
IMU sensor topic publish start time #56
Comments
Hi @juanmed, The reason is that currently the dynamics simulation only starts once a thrust input of at least 1.1 times the vehicle weight (1.1*9.81) is received. This is to prevent the drone from immediately drifting away from its initial position (mainly due to IMU noise), once FlightGoggles is started. The IMU messages are only published if the dynamics simulation is running, hence those only start arriving after the initial thrust command. Prior to this moment, i.e. prior to the dynamics simulation running, the IMU messages would consist of only noise, since linear acceleration and angular rates are zero. -Ezra |
…r (issue #52). * Makes camera resolution configurable via ROS param files. Alleviates issues from #51 and #32. * Lowers takeoff thrust threshold to 9.9N (see issues #56, #45). * Adds Windows64 standalone build to releases page (requested in issues #53, #46). * Adds nominal gate location file to ROS param server. * Adds plotter for laser range finder. * Adds example stereo reconstruction pipeline launch file. Many thanks to @eatal and @varunmurali1 for their help with this patch!
Hi @juanmed, FYI, we've lowered the takeoff threshold to 9.9N. After inputting a thrust command Best, |
Hello,
I see the topic /uav/sensors/imu is being published only after messages to /uav/inpu/rateThrust start arriving. Is this the normal behaviour? Is there any reason for this?
The text was updated successfully, but these errors were encountered: