Replies to This Discussion

ModeratorPermalink Reply by Sebastian Gralla on December 28, 2010 at 5:36am

but two usb ports need more space, an extra FTDI chip (which is ~10$) and an extra UART (wo only have 4, one for USB, one for GPS, one for telemetry, and one left for future use)

 

switch to the back for CLI, and to the front for normal flight and configurator

• ▶ Reply

Permalink Reply by brakar on December 28, 2010 at 8:54am

I do not intend to be critical, but I see all the leds, buttons and switches as signs of apm still being a dev. Board, (not designed or intended to be embedded in an airframe). At next hw rev. I would expect to see a simpler layout with more minimalistic user interface.

• ▶ Reply

ModeratorPermalink Reply by Chris Anderson on December 28, 2010 at 9:38am

Yes, APM is development board, like all open source autopilots. That's why they're open source--so that people can modify them.  This is true for Paparazzi, the UAVDevBoard and every other open source autopilot on the market.

 

But we agree that many people do what simpler, more "plug and play" autopilots, so you should see several of that sort coming out from DIY Drones over the next year.

• ▶ Reply

ModeratorPermalink Reply by Chris Anderson on December 28, 2010 at 9:35am

The Configurator page in the manual shows which direction the switch should be. That reflects the current firmware.
https://code.google.com/p/arducopter/wiki/Quad_ConfiguratorTool

What page were you looking at?

• ▶ Reply

Permalink Reply by brakar on January 2, 2011 at 7:45am

I am now at the initial setup of the tx/rx part in the configurator tool manual. Everything appears to be fine until the moment when I try to save the settings, then I recieve an "Update unsuccessfull, try again?" message.

 

Any ideas what I might have done wrong this time?

• ▶ Reply

ModeratorPermalink Reply by Chris Anderson on January 2, 2011 at 9:16am

There's a timeout situation with the Configurator that crops up in some versions of the code (I can't remember if it's been fixed in the released code yet). Can you try again (disconnect from the configurator, then conect again and do the radio setup) but do it more quickly and see if that makes a difference?

• ▶ Reply

Permalink Reply by brakar on January 2, 2011 at 9:54am

I have gone through the config procedure as fast as I could a couple of times, disconnecting everything in between, but still same result.

The rx-connections looks like in the pickture, no lipo is attached, all esc's and bec's disconnected.

ModeratorPermalink Reply by Chris Anderson on January 2, 2011 at 10:31am

Hmm. I've never seen that error, so I'll just try a few other suggestions. 

 

First, can you try with a LiPo plugged in? I see your power distribution board is connected to your APM, so that should ensure that it's getting enough power.

 

Second, you might try initializing your EEPROM again.

 

Finally, we can always do this through the CLI and see if that reveals anything different.

• ‹ Previous
• 1
• 2
• Next ›
• Page