No throttle sent to ESC on channel 8

so Better to download the 3.6.7 since its free of problems and don’t really need 4 servos!

I installed the Qgroundcontrol in my PC and connected the pixhawk into the SUB
clicked the frimawre then on the right giving me two options;

Ardupilot flight stack
pix4 flight stak v1.9.1 stable release
down there is a chibios and nuttx

and I see only arduheli 3.6.9 I don’t see 3.6.7!

and down select what version of the above flight stack you would like to install
and choices ;
standard version stable
beta testing beta
developer build master

so how to get the 3.6.7 ?

I appreciate your help!
ozzy

If the 3.6.7 build is the one you want, you have to down the proper firmware for your controller from here ->

Then in the firmware install select the Advanced checkbox and install custom firmware file.

Chris, sorry about my so many questions;

I plugged the USB then clicked to choose px4 flight stack V1.9.1 stable release

then advanced setting and choose custom firmware

then hit OK
and the window opened to pick your saved file…

you gave me the link, I opened an I see only in the bottom
assets
and so many links for different devises

now my devise is PX4 FMU V2
that was the Qgroundcontrol telling me in the found devise (frimware window)

so I pick ArduHeli-3.6-Stable-fmuv2.bin

or any others ?

and even if I choose that one and finish downloading it and hear the music tone

still I can see on the summary that the firmware v is 3.6.9 !!

its little hard for me to tell which link need to pick?!

thank you

Ozzy

The firmware will still identify in the summay as 3.6.9 so you don’t get complaints from QGC about running outdated firmware. But in the logs I can identify it as ArduHeli 3.6.7 so if you have a problem I can tell what firmware version you got.

So is the ( Arduheli-3.6-stable-FMUV2.bin ) what I need to click and download ?

And my Pixhawk is the pix4 mfu v2 that what in the frimWare setup page saying !

I think I may have to calibrate and redo all tuning again !

Thank you very much !

I just re installed ArduHeli-3.6-Stable-px4v2.px4 nuttx

but the problem is that I can’t connect my wireless telemetry link to QGC or Mission planner!!

its frustrating! :frowning:

Ozzy

Still no hope to connect mavlink to any software!!!
I think it’s the frimware problem

I had no problem connecting mavlink with 3.6.9 before !!
Its look like the 3.6.7 not for wirless mavlink

Ozzy

I’m not sure what the problem is, but the firmware version has nothing to with connecting with MavLink. I run the 3.6.7 version and connect to it with MavLink all the time.

It’s keep telling me time out

And I tried all ports numbers
Also I checked my hardware usb port and it’s same as the qgc and mission planer

I also tried my Samsung tablet but not connecting

I had no problem connecting with the 3.6.9

But this happened after I installed 3.6.7

Do I use the right firmware between all those 3.6.7 versions ?

Thank you
Ozzy

To get a clean Firmware install I would load a Plane Firmware into the Flight controller first and than the Heli FW of your choice again.

problem solved //// problem solved !!!

I spend few days looking to solve the mavlink connection problem!

finally what I did is to Uninstall the driver then restart my PC and everything looks perfect!

I had my very first hover flight today in stabilize mode and its good but its forcing me when I want to move my cyclic sticks… and start swinging back and forth ! and very hard to tilt it left or right!

like a coax heli!

maybe that is the tuning job

but I have a message says ; parameters are missing from frimware. you may be running a version of frimware QGC does not working correctly with or your frimare ha s a bug in it.
missing parameters : 1- AUTOTUNE_AXES

dose that mean I need to redo all the frimware flashing and the reinstalling?

Thank you
Ozzy

No. That message is not an issue at all. Just ignore it.

the Althold at bench is little scary~

when I change the pitch to +3~ 4 degree and change the switch from stabilize to ALthold the pitch go negative fast!

hope that will not happen during the flight, otherwise will smash the ground and it may make a hole !

I am not setting up the Power section yet, its disable

but I use 2s lipo 4000 mah for the servos and the pixhawk
and the 6s 5000 mah for the motor

the battery monitor giving me few options to choose from which one to pick?

and the battery capacity also, do I have to enter the pack mah?

same with power sensor; what option do I need to pick?

sounds like its complected!
I appreciate your help!

Ozzy

Got my real stabilize flight today and with the MAVLink

The battery safe was enable and the heli didn’t want to arm…

I disabled he battery bower option

Then after hovering it I switched to ALT hold

But the heli drift to left and I fully control it to make stay on its spot !

I switched back to stabilize mode and the heli dropped down fast almost crashed it

Because it changed to -pitch

I was able to recover it by giving it full +pitch

Sounds like I am missing some tuning here

Ozzy

You will find that in Chris Olson setup Video#2 at about 16min.
It is about the curve in Stabilize mode. You need to get that value right when the Heli is hovering in STAB-mode.
link:http://ardupilot.org/copter/docs/traditional-helicopter-configuration.html

FRED_GOEDDERT
yes I re-watched Chris’s video again and this time I think I had it right, I had to keep my pitch stick in middle in both stab and ALThold when I setup the Max, 0, Min value -.25, 0.00, +11

I also find when I tested in 5 min flight ; I had to leave the heli at the last position for few seconds before I can switch between modes, otherwise will drop fast!

now the time for the AUTO mission planning flight! Auto take off, waypoints and auto land!!

can’t wait till then!

by the way do you set your battery fail safe page ? I just don’t know how to
since I am using 2s 4000 Mah battery for electronics and 6s 5000 mah for motor!

its so grate to to see people like you and Chris helping others !

Thank you
Ozzy

My IM_STAB_COL look different on my TR600. 1=0, 2=600, 3=650, 4=1000. The Heli is heavy loaded with camera gear and batteries.
Regarding Battery fail safe.
I do not have Battery FS because I plan my mission inside the time my Batteries will last.
FS is set for signal los only. But if I lose signal during mission I have set to finish the mission first. After my last way-point I have set RTL with Auto-Land, always. Chris never does Auto-lands!
Auto-take off is a NO-NO for me. It is a brutal shooting up into the air. I never do!
Good Luck.

Ok, I just crashed it !!! :frowning:

I flowed Auto mission
50F high and short distance

At landing started to swinging again and about 10 feet above ground start swinging really bad and I had to change to Stab mode to recovered but it went down so fast and crashed !!

Total loss $200.00
Blades, tail blades, front gears rear gears bearing, shaft …

Don’t know if it CG off little bit and that was cause the swinging !!!

I see people do auto mission and their landing straight down !!!

Also when it change between waypoints; it dose not do that in right way !!

She fly to the next point and fly backward then yaw then do the same with the next heading !!!

Sounds like Pixhawk is more complicated than what I was thinking !!

Thanks
Ozzy

Here some hints what might be better working.
WP_YAW_BEHAVIOR I have set to = 3

RTL_ALT =1500 ( to return above Trees, in case)
RTL_CLIMB_MIN =0
RTL_LOIT_TIME =4000
RTL_SPEED =0
RTL_CONE_SLOPE =3
It will than take the speed going down from the WPNAV_SPEED_DN settings
RTL_ALT_FINAL =0 the Heli will auto-land, if you which.
Sorry for your crash.

M_STAB_COL_2 400 d% is your value. I believe that is the reason it crashed.
Hovering below 50% Stick is only if you have a over powered Heli.
If you hovering above 50% Throttle stick you must set M_STAB_CPL_2 above 500 or it does exactly what I have seen in your video.
I hope you have not set H_LAND_COL_MIN to =0 That also smashes the Heli into the ground. I have set to 140. Chris is explaining that at the beginning of tape 2