Open GoogleCodeExporter opened 8 years ago
if your using the maestro, the pwm field doesnt actualy do anything. its all in
the maestro setup.
Original comment by Meee...@gmail.com
on 25 Sep 2012 at 10:18
in maestro set the range as 380 / 2 = 190
neutral as 1590
min and max as you said.
and that should take care of it.
Original comment by Meee...@gmail.com
on 25 Sep 2012 at 10:19
Original comment by Meee...@gmail.com
on 25 Sep 2012 at 10:21
Yes I we are using a maestro, I will try that as it is slightly different to
what we have setup already.
Original comment by QandG...@gmail.com
on 25 Sep 2012 at 10:24
let me know how you go.
Original comment by Meee...@gmail.com
on 27 Sep 2012 at 12:37
Tried it today, not quite there, starts to track, then loses it and wanders
away,eventually comes back close to target. I'll try tweaking it a bit more
over the next week when the weather improves.
The 3DR trim function, does that only work with the 3DR radio or does it work
with any radio? We are using an xbee 2.4GHz on one drone and an XRF
http://shop.ciseco.co.uk/xrf-wireless-rf-radio-uart-rs232-serial-data-module-xbe
e-shape-arduino-pic-etc/ would the auto trim work with those?
Original comment by QandG...@gmail.com
on 28 Sep 2012 at 6:12
Tried lots more times, once I worked out that the aerial needs to face North it
improved. I was using the trim, but didn't realise the it was based around
North.
Sort of works, just overturns now, not sure the best way to deal with that,
maybe reduce the min max settings as the 8 bit is at the the minimum 156? Tried
190 was too sensitive, so slowly reduced it.
Original comment by QandG...@gmail.com
on 10 Oct 2012 at 12:14
if you are using the trim, make sure the plane is 20m+ away from you. otherwise
the calculation isnt updated
Original comment by Meee...@gmail.com
on 10 Oct 2012 at 12:16
Hmm, that may explain it. We have the tracker on our vehicle roof and usually
the drone is armed quite close by, at least a few metres. I'll test it again.
Original comment by QandG...@gmail.com
on 10 Oct 2012 at 12:26
ie detailed version.
if the plane is within 20 m and not been outside of that 20 m the tracker will
point north. as the angle to the plane is still 0. ie north.
once the plane is outside of the 20 m radius the tracker should turn to that
angle. and the trim value should be adjusted then. This was to prevent ranndom
360 degree spins if the plane was close the ot tracker location.
Original comment by Meee...@gmail.com
on 11 Oct 2012 at 2:28
Yes that makes sense, thanks for the more detailed answer. Is that on the wiki,
it would help others.
Original comment by QandG...@gmail.com
on 11 Oct 2012 at 7:13
Original issue reported on code.google.com by
QandG...@gmail.com
on 25 Sep 2012 at 9:19