truly new to the hobby. This morning I have tried to takeoff in stabilized mode but the quad looked like it wanted to flip forward.
All calibration done. ESC synced before flight just in case.
Looking at the log
something doesn’t look quite right but I’m not sure how it should be.
Just in case here is my params list.
If you are truly new to the hobby you should not be running a beta release of the firmware.
Get your copter flying with a stable release before venturing into release candidate firmware.
There is why it wants to flip.
There is no RCout on Motor3???
Does motor3 spin at all?
Have you bench tested this quad with the props off?
Arming, RC stick input and motors rev accordingly? Roll? Pitch?
Armed and throttle at 1/4, tilt quad, do low motors speed up, high motors slow down?
You also have NO battery sensor readings?
Have you calibrated compasses? Accelerometers? ESC’s?
How carefully have you been through the Wiki?
As mentioned by @LuisVale it is the only way to use ArduCopter on Pixhawk 4 (FMU_V5).
Regrettably, I don’t know what is RCOut on motor 3. Is that the signal that goes from Pixhawk to motor 3?
To your other questions:
All motors calibrated numerous times and also before flight on the field.
Al motors tested on bench and are operational A,B,C,D (1,4,2,3) and also in sequence and together.
Disabled PreArm checks and radio (X9D) arms and fires up all motors as it should.
Reversed channel 2 - pitch (ele) on radio (-100 instead of 100)
Also did the test where I hold the quad, motors seems to try to balance.
Battery sensor I believe is a problem with the FW, however I do get a reading on my OSD.
I have been reading Wikis and Youtube for the last two month, I have taken my quad apart more times that I wanted. This Holybro Pixhawk 4 gave me so much grief and I still do not know what is the reason for RCOut 3 at 1000.
I did flew this quad once with the same hardware with Matek f405 CTR FC, but it lacks so many thing that I want which exists in ArduPilot.
Could you please explain to me, what is missing and what might be the reason for that?
Is it possible that my FC is faulty?
Thanks @LuisVale, I didn’t notice he was running PixHawk4.
And I must agree, 3.6 is flying very well on all the machines I have been testing it on.
Love the new Loiter.
First off, this is only the .tlog with these values.
A .bin file with the RCin and RCout values logged would be preferred.
When you say All motors calibrated numerous times and also before flight on the field.
What are referring to? Do you mean you calibrated the ESC’s at the field?
As the motors run when doing the motor test it doesn’t seem the PixHawk has a faulty output.
The only other thing I can think of is that you are being too cautious in your attempt to take off.
It can be a bit daunting for the first flight, but even the big octo’s will tip on their very first lift off.
You need to arm then ‘jump’ the copter into the air.
Not too hard, just aim for a metre high to get it out of ground effect.
To play it safe, when on first lift off and the copter wants to tip, say forward, I will back off and then raise the throttle again with some back elevator added.
Usually the copter will want to tip backwards then.
So I know the controls are working in the correct sense.
I usually check the roll that way as well.
When I am happy that I have control I will give the throttle just enough to get it light on its feet, then a little ‘punch’ to clear the ground quickly to a metre high.
Yes, when first the copter looked like its going to flip I did the ESC calibration sequence after I took off the props at the field just to be on the safe side.
Actually, cautious is my middle name so maybe I do play it too safe.
I shall try your advice tomorrow if its not too windy.
ok, so some data:
frame X IronMan F650
ESC Hobby Wing pro 50A
Motors: Tarot 320kv 6s
Battery: 6S 16000mah 25c/35c
Total weight: 3250g
Props: 17"
radio X9D
receiver: X8R
I believe the errors shown in the log are from the boot sequence after connecting the battery and turning the radio afterwards, does it make sense?
I shall set the MOT_PWN_MIN to 1000 and the MOT_PWN_MAX to 2000 and re-calibrate the ESCs.
I shall try to do a flight tomorrow morning, its summer here and the winds picks up here early to about 15-25mph.
P.S. @LuisVale I have tried setting MOT_PWM_MIN /MAX, however Pixhawk and my ESCs don’t like the values - Pixhawk is in error and escs are beeping fast - so I left it at 0. UPDATE, it accepted the values and it servos output in MP does seem better. I shall try it this evening again.