(I was using an EasyStar with XY & Z sensors)
The Good
--This version does away with the bind plug process for people who are using ArduPilot to control the throttle (which I am). Worked fine!
--Stabilization gains are dialed in fine. Earlier problems with people using the Z sensor are gone.
--Funky motor pulsing issues at startup and problems with ESC arming are gone.
--New GPS parser for uBlox works fine.
The Bad
--Altitude hold doesn't seem to be working in AUTO mode (although it does seem to work in RTL mode). The plane is supposed to stay at 50m, as you can see in the mission file above, but just seemed to go higher and higher. I had to bring it back manually from about 200m. We've had this problem before, and I think it has to do with the uBlox GPS parser. If it thinks the GPS is reporting that the plane is at an altitude of 0, it will just keep trying to fly higher. We'll need to fly with someone watching the telemetry to figure out what's going on.
--I accidentally set my waypoint radius limit too high (59m) so the plane was just approximately following the course. That should have been closer to 10m.
--The RTL loiter circles were more like figure eights. I think the loiter radius (45m) is too tight, and should be closer to 100m:
//4-7
#define LOITER_RADIUS 45 // radius in meters of a Loiter
The Stupid
Somehow I was under the impression that I could adjust the throttle while the plane was in AUTO mode (you can nudge the aileron/rudder and elevator in that mode). That doesn't appear to be the case. The reason this matters is that if you're trying to set a good time on a T3 run, you don't want the plane to leisurely go around at half throttle!
In the meantime, I need to change something in the settings below. I'm thinking I should crank the Absolute figure up, but how high? (Is it 0-10?). Jason, do you have some advice? Any chance we can allow the user to nudge the throttle when it's in AUTO mode?
//ATTITUDE: THROTTLE OUTPUT GAINS
//9-1
#define THROTTLE_ABSOLUTE 3 //Absolute
//9-2
#define THROTTLE_P .32 //Proportional
//9-3
#define THROTTLE_I .04 //Integrator
//9-4
#define THROTTLE_I_MAX 50 // (0-125) 50 = 40% Integrator limit.
//9-5
#define THROTTLE_CRUISE 30 // (0-125) 30 = 24% throttle, or (int)target airspeed for cruising
//9-6
#define THROTTLE_MAX 60 // (0-125) 60 = 48% maximum throttle
Comments
http://store.diydrones.com/ProductDetails.asp?ProductCode=BR-SCP100...
for the altitude hold function ?
An increase in airspeed eg throttle will cause a climb if the aircraft dose not pitch nose down to reduce the extra lift cause by the increase in airspeed.
I think this was happening when I was using 2.4.3
As I tried to increase throttle the plane just slowly climbed. What I think was happening was it was coming up against the #define ALTITUDE_ERROR_PITCH_MIN and would not pitch further forward so the result was a climb.
When I changed the #define ALTITUDE_ERROR_PITCH_MIN it seemed to hold altitude much better. And I could get a higher airspeed.
I’m not sure If 2.5 has the same line in the code or how increases in air speed are handled.
Unfortunately were I fly there is always thermals going off so lots of lift this make it hard to figger out watts really going on.
We can definitely nudge the throttle! I was thinking the same thing.
I'd also like to be able to nudge the throttle!
Thanks for the report!
-
1
-
2
-
3
-
4
of 4 Next