-
Notifications
You must be signed in to change notification settings - Fork 993
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
APMcopter and Mavros #588
Comments
Run |
Hi vooon, This is my result
Was unsure how to implement the ``` for code blocks. Thanks |
https://help.github.com/articles/creating-and-highlighting-code-blocks/ Hmm, FCU only sends HEARTBEAT messages, no response on parameter request and mission list request. Check electrical connection of Edison Tx ←→ Pixhawk Rx and GND ←→ GND. |
Thanks! I had the tx on the wrong pin on the edison but I still get this Received 15 messages, from 1 addresses However now i get this
|
Check diagnostics, then use |
Hi Vooon, I have used rostopic hz (I don't have rqt installed and space is limited) instead to check if topics such as imu/data are publishing, which they are not. The only topic which seems to work is /mavros/state. Diagnostics seems ok and gives more data when the drone is armed. Can you please advise further? Do I still need to run rqt to check the message rates? Thanks |
Actually.. Got it to work by changing the message stream rate. rosservice call /mavros/set_stream_rate 0 10 1 Except my quaternions dont seem to publish in my imu data.. |
Hi,
I have built a platform using an Intel Edison and Pixhawk which are mounted on a conventional helicopter using the APM flight stack.
So far I have manage to get mavros to partially load but the work flow does not seem to be complete nor am I able to see topics such as imu data.
What I would like to know is, have I hit a brick wall due to my flight stack(not being PX4) or is there some simple fixes that can be applied here to get full functionality of mavros/mavlink.
I have included below is a copy of what initialised, warnings and errors.
-_-
Thanks
Tom
P.s I forgot to mention we did modify some of the cpp files to include the helicopter platform and get the follwoing when I run diagnostics
The text was updated successfully, but these errors were encountered: