Found some good bugs already. An issue with auto trimming being activated due to unusual Radio configurations fixed. Mavlink support is now up to par with APM. and A compass bug in the library squashed.

 

I revved the firmware's EERPOM fingerprint. You must redo the setup completely. (except ESC calibration.)

 

Thanks for the feedback!

Jason

Views: 67


Admin
Comment by John C. on May 9, 2011 at 6:45pm

I can tell you right now the camera stabilization works well.  I had to make a couple of small tweaks to the math, and it's probably not the right way to do it, but I'll send it to you.

 

Comment by Taylor Cox on May 9, 2011 at 8:08pm
@John...are you using a pan and tilt system? Are you controlling the camera with switches or knobs on your receiver?

Admin
Comment by John C. on May 9, 2011 at 9:11pm

Pitch and Roll - gyro stabilized with control mixing

 

Quick and dirty stabilization

Comment by Nigel on May 10, 2011 at 10:56am

I know Jason is aware of Mavlink issues but for the record, with today's current code I get different data from the USB port than from the UART.  The USB data seems to be complete with full telemetry and GPS whilst the data from the UART only seems to contain servo data...

(This is just for info - I know this is still being worked on)

Comment by emile on May 10, 2011 at 12:30pm
Just a studid question....
Why is the Z Accel now showing -1000?
Is this the normal behaviour?
If I move the copter everything seems fine, the data moves accordingly.
Comment by Magellan on May 10, 2011 at 12:34pm
It shows -1000 since the device is sitting on a level surface and gravity is pulling down on it. Gravity is always there.
Comment by emile on May 10, 2011 at 12:49pm

@Magellan, thanks for the answer. I was used to the always there "408" value. So I bet this is a 1G pulling down just a matter of showing it in a different way (maybe makes more sense now :))

Ok, so here is another Q.

In the PIDs D is a real D or is it the P-Rate as for the former AC? 

Cheers,

Emile


Developer
Comment by jasonshort on May 10, 2011 at 1:08pm

Our standard PID loop doesn't take into account the Sensor data for D term. 

This was Jose's original approach. Technically, it's a standard PID loop. Rate can be derived from a saved angle, or directly from the sensors. The reality is that we could use the saved rate and make it 100% standard. But it's not worth changing because we also use some nice constrains in there too.

Comment by Peter Seddon on May 10, 2011 at 1:14pm
Have you got GPS lock Nigel. On the ArdupilotMega you don't get GPS co-ordinates translated until you've got lock.

Peter
Comment by Vincent Mees on May 10, 2011 at 1:22pm
I'm having the same issue. Even with GPS lock no data.

Comment

You need to be a member of DIY Drones to add comments!

Join DIY Drones

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service