I've just released ArduPlane 2.65
This is what is known in the free software community as a "brown paper bag" release, because the developer (that's me) thinks he should hide his head in a brown paper bag out of sheer embarrassment.
Steven G noticed that my fix for stick mixing in CIRCLE mode in 2.64 broke STABILISE mode. When I test flew 2.64 I tested FBWA, but not STABILISE mode!
So the only change in 2.65 is to fix that. My apologies for the 2.64 release!
Cheers, Tridge
Replies
Direct fly and direct auto landing windly weather (wind up to 12m/c)
plane cruise airspeed is 14 m/s
gps 3339 globltop pa6c module about this module
route
1st point 100m attitude
2nd point one circle around it 40m altitude
then going to landing
direct auto landing runway width ~5m
Globaltop PA6C Gps module
Just had some success with 2.65 on my new Finwing Penguin. Unlike the Skywalker the Penguin uses alot more throws on the control surfaces, which made it somewhat easier to tune.
Stabilise mode worked well, and FBW-A worked well. The only issues was that at full forward stick the aircraft was very very slow to nose down, and full back stick it was slow at nose up. I've increased the max pitch down to -35 and pitch up to +25 hoping that this will help.
The only other issue I had was with the voltage and amp meter. Its reporting abut 7V and 255A no matter what. I'm using a Attopilot 180A sensor and I choose that in the APM mission planner. Disconnecting the sensor cable from the APM causes the V to rise with no change to the Amps.
param file attached, after flying the penguin, I am confident that it will become the FPV plane of choice. All the benefits of the skywalker, but none of the bad flight characteristics.
PenguinAPM.param
Ok, I have a definite issue here. I connect to the mission player and the plane's position is not displayed at all. The MP correctly shows that I have a 3D GPS lock, but it seems the data doesn't get passed on to the MP. The position data does not appear in the t-logs either.
This problem is absent when I load ArduPlane 2.5 on the same setup...
APM 1 2560
RFD900 modems
Ublox gps
hi all,
2 developers
new gps libraries works excelent it detect most types of gps
but if module has factory setting 9600 code no change this baud and as result low update rate 1hz only available with 9600 baud
I propose to add two parameters configurable from MP
1. gps_default_speed (gps factory setting as example 9600)
2. gps_custominitstring (as example $PMTK251,38400*27 for change mediatek baud rate to 38400)
if gps_custominitstring is not empty
before autodetect routine - gps port open at gps_default_speed, send gps_custominitstring
Hello everyone, today tried to auto 2.65.
Firmware excellent! aircraft ever to stick to the route despite the strong wind comparable to the speed of the aircraft.
Sometimes it was directed almost perpendicular to the route
But if applied airspid_use=1 the plane decrease altitude very bad. This is especially important when it lands.
I set the landing point on the four-meter, but the plane was 15 meters above.
Then I applied the patch and repeated the experiment, the plane was at the correct altitude and successfully landed
patсh here: http://code.google.com/p/ardupilot-mega/issues/detail?id=729
I experienced a similar issue like Rana.
In FBW-A mode the plane suddenly push down the nose (approx. -20 degree) and losing alt while the GCS/ArduPlane shows positive pitch.
You can see the event in this video: https://www.youtube.com/watch?v=6O5F5j9uAJg at around 0:35 and my PID settings are:
Do you have any idea what happened? What is wrong with my config?
I'm trying to load 2.65 onto an APM1.4 using Arduino1.0.1, but the sketch is too big: Binary sketch size: 130,702 bytes (of a 126,976 byte maximum)
Interestingly enough, the .hex loads fine using Mission Planner. Any thoughts?
hi...i compiled the 2.65 code for apm 2 and in stabilized mode the ailerons not respond...please any helps
thank you
Andrew,
Thanks for the update and congrats to your win.
I was flying 2.65 (last commit 1fe413e17d4634b2bc120dd76a0349e4d178090f to be precise) on APM 1 1280 a few days ago and noticed some strange startup effects. Before filing an issue I wanted to doublecheck that this is not specific to my setup. I power the APM, GPS and Xbee seperate from a 7805 voltage regulator (like a few other people and it works great) while servos and receiver are powered from the ESC.
In order to use AUTO_TRIM I power up first the receiver via the ESC (which doesn't arm when it doesn't get any input so I think I'm safe:-). Strange thing is if I power up in this order, in FBWA I get a correct control surface reflection which however is very slow (much too slow). If I first power up the APM, let it initialize and then connect the battery to the ESC all is fine (but I guess it does not get the trim values although I haven't checked that yet). So I wonder why this is..
Should maybe look at the code but I wanted to mention it here since I remember reading someone else wondering about slow control surface movement in pre-flight check of FBW.
Cheers, Andre
After your win Andrew me thinks that brown paper bag can be thrown away for good :))
-
1
-
2
of 2 Next