I sitting here with everything hooked up. I have the six wire going to the GPS, so that isn't the problem. If I fire it up without the I2C line plugged in it will boot fine. Soon as the I2C is connected it will fail to boot and give me those two depressing long beeps indicating startup fail right after the startup success sound.
I formated the SD card, I deleted the *.log file and I re installed the firmware a couple of times with no success.
Suprisingly if I upload the PX4 firmware I could connect via mavlink in mission planner but what I need is the arduplane. So this would suggest it being a software rather than firmware problem.
nevertheless the engineer at 3DR suggested to send the Pixhawk back to them.
Hi mark, firstly thanks for the info- you saved me much head scratching!
Interestingly my initial connection was ok but was having difficulty in calibration. Following that I started losing the link after 20 secs or so, it could only be restored by unplugging/ plugging the USB. I checked the wire after finding your post and it was the five wire;-) changed it for the six and hey presto- all good!
Owe you one mate,
Thanks so much for your post. I had the exact problem.
I struggled to connect with teh supplied USB cable to load the firmware, "unrecognised USB device", then after a couple of hours, tried changing the cable and worked.
Tried to connect to MP to configure and no connection.
Unplugged the magnetometer and it worked perfectly.
Did you find a solution to get it to connect WITH the magnetometer?
PIXHAWK USB COM PORT FAILS IN DEVICE MANAGER WHEN CONNECTING & DOESNT SHOW.
FOUND YOUR POST & CORRECT!
I UNPLUGGED THE "UBLOX COMPASS ( SDA/SDL 3V3 ) CONNECTOR".
AND THE PIXHAWK COM PORT SHOWED UP!
SUGGEST I HAD THIS DF13 UBLOX SDA/SDL WIRED INCORRECTLY.
I WILL CONFIRM WIRING & POST RESULTS.
Garrett Min > Garrett MinOctober 23, 2014 at 1:10am
FOUND IF A FAILED DEVICE IS CONNECTED TO PIXHAWK THE USB WILL NOT LOAD IN MISSION PLANNER. COULD BE ANY DEVICE, EXAMPLE IF THE APM POWER MODULE IS NOT POWERED ON IT WILL SHOW UP AS A FAILED DEVICE AND PREVENT MISSION PLANNER FROM CONNECTING OVER USB. CONFIRMED MISSION PLANNER ERROR LOG ON USB CONNECT SAYS "A DEVICE ATTACHED IS NOT FUNCTIONING."
Replies
I sitting here with everything hooked up. I have the six wire going to the GPS, so that isn't the problem. If I fire it up without the I2C line plugged in it will boot fine. Soon as the I2C is connected it will fail to boot and give me those two depressing long beeps indicating startup fail right after the startup success sound.
Definitely the magnetometer.
When I boot up the pixhawk with magnetometer, I get no big flashing LED. When I boot up without it, all good.
Aus
Well,
I formated the SD card, I deleted the *.log file and I re installed the firmware a couple of times with no success.
Suprisingly if I upload the PX4 firmware I could connect via mavlink in mission planner but what I need is the arduplane. So this would suggest it being a software rather than firmware problem.
nevertheless the engineer at 3DR suggested to send the Pixhawk back to them.
Interestingly my initial connection was ok but was having difficulty in calibration. Following that I started losing the link after 20 secs or so, it could only be restored by unplugging/ plugging the USB. I checked the wire after finding your post and it was the five wire;-) changed it for the six and hey presto- all good!
Owe you one mate,
Cheers!
Brilliant!
Used the 6 wire for the GPS and now all good. Thanks.
I have the SBUS working.
Now just have to calibrate everything and work out why all 8 DJI escapes just keep beeping at me!
AUS
You are probably right,
Is it a failsafe that no heartbeat will be sent unless all vital components are live (ie compass gps etc)
I hadn't connected the GPS precisely because I didn't have the right cable, (as you mentioned they send the wrong cable with unit).
Which basically is going to set me back I dunno how many weeks before my PX4 ships to CA and then back to UK , oh dear !
Thanks so much for your post. I had the exact problem.
I struggled to connect with teh supplied USB cable to load the firmware, "unrecognised USB device", then after a couple of hours, tried changing the cable and worked.
Tried to connect to MP to configure and no connection.
Unplugged the magnetometer and it worked perfectly.
Did you find a solution to get it to connect WITH the magnetometer?
Thanks,
AUS
CONFIRM:
I HAD SAME PROBLEM,
PIXHAWK USB COM PORT FAILS IN DEVICE MANAGER WHEN CONNECTING & DOESNT SHOW.
FOUND YOUR POST & CORRECT!
I UNPLUGGED THE "UBLOX COMPASS ( SDA/SDL 3V3 ) CONNECTOR".
AND THE PIXHAWK COM PORT SHOWED UP!
SUGGEST I HAD THIS DF13 UBLOX SDA/SDL WIRED INCORRECTLY.
I WILL CONFIRM WIRING & POST RESULTS.
FOUND IF A FAILED DEVICE IS CONNECTED TO PIXHAWK THE USB WILL NOT LOAD IN MISSION PLANNER. COULD BE ANY DEVICE, EXAMPLE IF THE APM POWER MODULE IS NOT POWERED ON IT WILL SHOW UP AS A FAILED DEVICE AND PREVENT MISSION PLANNER FROM CONNECTING OVER USB. CONFIRMED MISSION PLANNER ERROR LOG ON USB CONNECT SAYS "A DEVICE ATTACHED IS NOT FUNCTIONING."