We aim to fly M1000 quad by T-motor with 24" propeller, however, for now we are checking the Herelink with a cheaper and smaller scale quad with orange Pixhawk. Please note the following issues have arisen upon flight tests:
Q Ground Control app crashes if put in background while parallelly accessing the Here Link app and also if the drone is disconnected in between while the app is open.
Battery voltage is not showing despite enabling the HV module in the app.
With the throttle stick not centered (non-zero) by default (like DJI), the drone climbs very steeply soon after arming. With the throttle stick centered at zero, it climbs well, however, with fingers always pressed on the throttle stick (since it is spring mounted).
Please find the attached video links for reference:
Throttle stick non-zero: Redirecting
Q Ground Control app crashes if put in background while parallelly accessing the Here Link app and also if the drone is disconnected in between while the app is open.
This doesn’t sound right. Did you have Solex running in the background?
Try to reflash the firmware on Herelink to get QGC re-installed
Battery voltage is not showing despite enabling the HV module in the app.
Have you set up the parameters in Mission Planner? Or at least is voltage monitor available in your Mission Planner HUD?
With the throttle stick not centered (non-zero) by default (like DJI), the drone climbs very steeply soon after arming. With the throttle stick centered at zero, it climbs well, however, with fingers always pressed on the throttle stick (since it is spring mounted).
OK, looking at the first video that was definitely an aggressive takeoff, the second one looked relatively normal. It looked like all Stabilise mode from the video.
If that was Stabilise mode the behaviour was probably expected. Stabilise can be hard to hold at a steady altitude, and is the best mode for making that moon shot
Can you test AltHold mode?
PILOT_THR_BHV,7 suits a RC control with spring-centred throttle.
Hi Shawn, just reading through the thread. I think it’s still relevant to me.
I was interested in knowing why BHV 7 and not just 1.
I have the EDU450 v2 and am finding under Stabalise it’s shooting for the moon!
I’m utilising the Herelink HD with the spring-loaded stick and I have reversed the throttle and added a DZ @ 50. this was the only way I could determine how to maintain the arming process.
I’ve set all the min/max mot_spin parameters and mot_hover_learn is 2.
So when I arm it spins up fine at 0.14 arming the throttle just enough to get the motors spinning. Soon as I let the stick spring back to centre it’s like it hits warp drive and I have to be on stick to bring it back to 2-3m AGL.
Now in my mind soon as it’s mid-stick it’s hitting 1500 PWM, right?
Is this normal behaviour for a spring-loaded throttle?
That is normal for a spring-centered throttle and stabilise mode.
If you use AltHold or Loiter you will have to manually raise the throttle past centre to get a positive climb rate.
That’s what I’m seeing so it’s good to know. I guess I kind of thought that at mid stick in Stab it would more or less have an equivalent hover even if it’s not governed by a barometer but it seems to have a bit more boot. Not sure if you can dial back thrust or I’m missing something? I’ve collected the logs and can see the thrust converges over time from mot_hover_learn.
It’s interesting because once I move from Alt_hold back to Stab, land and then take off in Stab its more what I’m expecting and just floats nicely in front of me. So I’m trying to understand what this is so I can replicate all the time.
