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

When BRD_SAFETYENABLE is set to 0 MP won't connect to Pixhawk #821

Closed
gmorph opened this issue Mar 27, 2015 · 3 comments
Closed

When BRD_SAFETYENABLE is set to 0 MP won't connect to Pixhawk #821

gmorph opened this issue Mar 27, 2015 · 3 comments

Comments

@gmorph
Copy link

gmorph commented Mar 27, 2015

I set BRD_SAFETYENABLE to 0 in MAVProxy and then exited MAVProxy and power cycled the Pixhawk. I started MAVProxy again and it was able to reconnect to the Pixhakw just fine - the safety switch is glowing solid red as expected.
I then disconnected the pixhawk and connected to my windows machine running a newly updated MissionPlanner and the connection timed out both when selection AUTO or specifying the COM port.
All connections to the pixhawk were done via USB.

jean-luc first reported this problem about 8th post down.
http://diydrones.com/group/arduboat-user-group/forum/topics/using-ardurover-for-a-4m-solar-powered-boat-for-long-distance?page=1&commentId=705844%3AComment%3A1945089&x=1#705844Comment1945089

@meee1
Copy link
Contributor

meee1 commented Mar 27, 2015

why is this a MP issue?

@gmorph
Copy link
Author

gmorph commented Mar 27, 2015

Hi Michael. It only happens with MissionPlanner. MAVProxy can connect to the Pixhawk just fine when BRD_SAFETYENABLE is set to 0 but MP doesn't seem to be able to.

@meee1
Copy link
Contributor

meee1 commented Mar 28, 2015

ive tested here, and cant find an issue. what firmware? does it happen with all firmwares? ie plane rover copter

@meee1 meee1 closed this as completed Mar 31, 2015
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

No branches or pull requests

2 participants