Replies to This Discussion

Permalink Reply by Matt Gaige on August 25, 2011 at 12:29pm

You are in the wrong Discussion group, this is ACM.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on August 25, 2011 at 12:41pm

I've now moved it to the right section for him.

David, did you check the mode assignments in the Mission Planner?

• ▶ Reply

Permalink Reply by Avalerion on August 26, 2011 at 6:27am

I'm noticing something like this in 2.23. My plane was going along in auto just fine, and when I switched to RTL, it death spiraled into the ground. I checked my modes in the MP and they were setup correctly... Previous versions the RTL mode worked fine.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on August 26, 2011 at 7:13am

Did you guys clear your EEPROM and set up your APM again after loading APM 2.23? You must do that.

• ▶ Reply

Permalink Reply by Avalerion on August 26, 2011 at 7:15am

I did a a setup>>erase and then loaded the new code with my custom config file.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on August 26, 2011 at 7:40am

Averlerion: any chance you can post your logs?

As I understand it, it was working fine in stabilized and auto, but when you switched in RTL it crashed. Given that RTL is just another form of auto, that's odd. I'd love to see the logs on that.

BTW, it tests fine on the sim in all those modes.

• ▶ Reply

Permalink Reply by Avalerion on August 26, 2011 at 7:44am

Correct- stabilize and Auto were fine. I posted my track on another post a short time ago. I wasn't knowingly recording any logs- though I will check in a little bit and post if there are any. Otherwise I'm planning to load defaults/firmware via the MP and see if that has any effect.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on August 26, 2011 at 8:12am

Logs are autorecorded in MP if you have MAVlink telemetry connected. Also autorecorded onboard in dataflash.

• ▶ Reply

Permalink Reply by Avalerion on August 26, 2011 at 8:22am

Here's the log

Attachments:

• 11-08-26 08-41-12.tlog, 2 MB

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on August 28, 2011 at 12:38pm

Looking at the log, it looks like you have a pretty normal waypoint mission that goes a long time (you could tune your NAV and Crosstrack gains a bit for a smoother course, but it broadly goes where it's supposed to go), and then at the end something happens that I can't see from the logs.It might be a brown-out, which can be caused by a low voltage situation or over-current situation caused by high-drain servos on an insufficiently high-capacity ESCs.

 

Very unlikely to be software. It's hard to get embedded microprocessors to reboot with software bugs; they tend to lock up instead, which was obviously not the case here. If you check your onboad datalogs, you'll be able to tell if in fact the board did shut down due to a brownout/low voltage situation.

• ▶ Reply

Permalink Reply by Avalerion on August 28, 2011 at 12:52pm

I have voltage telemetry on the ground and it's OK (via the Spektrum TX/RX combo). However, since this happened recently after switching to the Xbee xtend, it might be a power issue. The only thing is that when I powered the Xbee from the APM, it worked fine. When I tried a separate power supply, it wouldn't transmit data... any ideas on that one?

Permalink Reply by Avalerion on August 29, 2011 at 6:44pm

Do you know the max output of the APM board telemetry port @ 5v? 500mA? My Xtend was set to auto TX power based on voltage, and it may have been trying to transmit at 1W for most of the flight... At 1W, it sucks up 730mAh at 5v. If I can confirm that the setting is way to high (and what a reasonable limit is on the APM), then I can try this again.

 

I can also go with the 500mw setting, 500mA at 5v.

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