Information

ArduCopter User Group

Discussion group for ArduCopter users

Members: 3059
Latest Activity: 6 hours ago

Discussion Forum

Throttle mid/hover.

Started by Jason Greening. Last reply by Walter Holliday 6 hours ago. 36 Replies

In mission planner it tells me that my throttle hover is 649 or 64.9%. So am I right in assuming I need to set my mid throttle at the same 649?Continue

Pixhawk external LED?

Started by Hugues. Last reply by André Zibaia da Conceição on Tuesday. 50 Replies

Hi,Anyone succeeded to install external LEDs on Pixhawk?On APM we could configure the param Led_mode to a binary value representing which actions turn LEDs on A5 and A6.Is there an equivalent feature…Continue

Mission Planner 1.3.43 problem

Started by Don Roberts. Last reply by Mark Brummett Jan 11. 4 Replies

Just updated to this and now I don have access to the full parameter list and some main menu items are missing.What is up?Continue

MAVLink Tutorial for Absolute Dummies (Part –I)

Started by Shyam Balasubramanian. Last reply by Randy Grinter Jan 11. 98 Replies

Hi All,I was recently fiddling around the code for a while and decided to create a tutorial out of it so that others may find it useful. If I would have known this knowledge long back, I am sure I…Continue

Tags: Ardupilot, Mega, the, program, to

Comment Wall

Comment

You need to be a member of ArduCopter User Group to add comments!

Comment by Tony Wall on 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).

Comment by Tony Wall on 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.

Comment by Cala on 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

Comment by Cala on May 28, 2016 at 5:41pm

I opened but anything :(

Comment by Craig on 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.

Comment by Cala on 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) 

Comment by Paul N Braida M.E on 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. 

Comment by bijoux-de-lithotherapie on April 18, 2016 at 1:47am

Hi All :)


Developer
Comment by Randy on April 13, 2016 at 5:14pm

@PaulNBraida,

Maybe try loading Plane onto the broken boards?  It's possible (if you're not using a 3DR APM) that the last copter firmware meant for the AVR boards doesn't fit on it because the manufacturer has put a bootloader that's slightly too large on it.

Also even though you can't connect via MAVLink you should still be able to upload firmware.  The issue is that Mission Planner (I assume this is what you're using) needs to first recognise the board (so it can get the correct firmware) and then it needs the board to be in bootloader mode to actually upload the firmware (the board is in bootloader mode for the first few seconds after being powered).  This means you might need to mess around a bit, connecting and disconnecting the board at the appropriate times.  I.e. plug in the board, push the MP's firmware upload button, disconnect and reconnect the board.

Comment by Paul N Braida M.E on April 13, 2016 at 8:36am

I still need help with my two APM 2.5. On one I can upload and verify firmware but it times out connecting to Mavlink. Error no heartbeat packets received. The other APM cannot upload firmware or connect. It has the same error. The port & baud are set ok. While counting down trying to connect I can see the small amber LED flashing slowly. Voltage on the outside pins of IC 2 is ok. I changed the volt regulator.

I'd really like to use these controllers, not just junk them.

Thanks

 
 
 

© 2017   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service