Replies to This Discussion

Permalink Reply by Ellison Chan on May 11, 2012 at 5:12pm

Hey Monroe, what do you mean, "It passes threw just fine to the servos but no response from the autopilot."?  Could be a bad encoder.  Did you try re-programming it?

Permalink Reply by Ellison Chan on May 11, 2012 at 5:50pm

So, the servos are connected to the APM, like in the picture?

I noticed the RC input #7 is connected to what looks like the battery port of the receiver.  This should be connected to a toggle switch channel so that you can switch the autopilot on and off.

If it is encoder problem, you'll need to re-program by connecting the ISP port for the atmega32, and use avrdude or some other flash program.

The hex is available here.

Permalink Reply by Ellison Chan on May 11, 2012 at 6:30pm

If you'r connected via USB, I would say no.  Your bps is very low and you're getting a lot of bad packets from MAVLINK.

Permalink Reply by Ellison Chan on May 11, 2012 at 6:54pm

How about swapping your old oilpan for this new oilpan.  Maybe it's got a problem.

Permalink Reply by Ellison Chan on May 11, 2012 at 7:40pm

Ok, I thought you had a second oilpan.  You definitely seem to have a problem with the mavlink connection.  Since the USB is on the oilpan, it could be a problem there.  Right now, you can only start troubleshooting and eliminating things.  Could be a problem with the USB drivers too.

Also, from the console window, does it show that all 128 params were loaded?

Permalink Reply by Ellison Chan on May 12, 2012 at 6:30am

A quick thing would to just remove and re-install the drivers.

Permalink Reply by Andre S on May 12, 2012 at 7:11am

Didn't you set up an Ubuntu system a while ago? You could try it there. On linux usbserial drivers are more a non-issue normally.