Comments

• 

  Cala May 29, 2016 at 1:07pm

  No GPS, the green light work, horrible that any stamped references, any documentation, bad product. :(
• 

  Cala May 29, 2016 at 7:47am

  Thank's Tony, perhaps devs take in consideration your intersting sugestions in gihtub https://github.com/ArduPilot/ardupilot_wiki/pulls

  

  ArduPilot/ardupilot_wiki

  Repository for Ardupilot wiki issues and wiki-specific website infrastructure. - ArduPilot/ardupilot_wiki
• 

  Tony Wall May 29, 2016 at 7:47am

  ...so this one defaults to 56k baud out the box, and must be set to 9k to get a reliable flash to the new 3.01 firmware for Galileo support and other improvements. So expect to get hold of a CP2102 USB serial adapter and make-up a cable to connect this GPS directly if you want the best out of it. It should still work out the box on the old firmware, but then in APM you must enable GPS auto config and save config when needed, then hopefully it will set the GPS to 38k and you won't get garbled data (by default from HK it's sending 56K but APM wants 38k kind of hard coded from what I gather). That was my impression, after many hours of work with these devices (like 4 different units/quadcopter builds). The debug messages on the console clearly indicate APM has issues with GPS serial speed, disregarding what the physical port is set to (strange).
• 

  Tony Wall May 29, 2016 at 7:40am

  By the way this GPS unit is very good. It will run up to 10Hz in GPS mode and 3Hz in SBAS-DGPS mode. The only issue is that APM is unable to detect this device at speeds higher then 38k baud, so best leave the update RATE at 500ms (2Hz), The problem is with APM not the GPS, if you connect to a PC with u-Center you should get good results. Until the GPS issues are solved in the current APM (and there are, those horrible arm delay horiz/vert GPS errors still) it will force the GPS back down to 38k baud even after you successfully configure higher rates. You can't even disable auto detection in APM because if you do it doesn't bother detecting any GPS at all (doh).
• 

  Tony Wall May 29, 2016 at 7:36am

  You can derive the pin-outs of the GPS from the PixFalcon documentation here: http://www.pixfalcon.com/download/MICRO-PX4.pdf

  Page 4 GPS & I2C port.
• 

  Cala May 28, 2016 at 5:44pm

  the only thing that I found that wire is compatible with Pixfalcon and I found Pixfalcon  labels but 5v is in the middle and not the red one
• 

  Cala May 28, 2016 at 5:41pm

  I opened but anything :(
• Craig May 28, 2016 at 5:10pm

  Guys, someone have this micro gps m8n from Hking?http://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idProduct=...

  I need diagram connections and I can't find and nothing write on the board :( , I only find that red isn't 5v .I'm afraid to burn it. (is for connect to a Pixracer) 

  open the case, the board should have the labels to which pin goes where.
• 

  Cala May 28, 2016 at 4:00pm

  Guys, someone have this micro gps m8n from Hking?http://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idProduct=...

  I need diagram connections and I can't find and nothing write on the board :( , I only find that red isn't 5v .I'm afraid to burn it. (is for connect to a Pixracer) 
• Paul N Braida M.E April 18, 2016 at 6:30am

  both boards have a 3DR stamp on the bottom and used to work. Now the one will upload and verify the firmware but not connect to Mavlink and the other will not upload firmware or anything. Both boards are receiving the required 3.3 volts.

  I don't know, maybe just scrap the boards?

  3DR do not seem to want to help me on this. Maybe I will forget APM and go with the NAZA controller.