As soon as I arm the quad, the throttle goes high and wont stop until disarmed. It doesnt throttle as high when airmode is off BUT then the motors cut completely at 20% throttle... I dont think its an accelerometer or esc issue but any ideas are appreciated... Config version 10.5.1 firmware 4.0.0
Tinyhawk2 full throttle when armed?
- Thread starter zakks69
- Start date
Yes, Ive gone through the re bind process at least 5 times, every time the same result. Beta tells me the throttle, along with everything else, is responding normally. I have to set the stick low threshold to around 1200 to get it to arm, and initially when the motors arm (on battery not in beta), they seem regular low rpm. But when throttle goes about 20%, they spin high and are unresposive until disarmed.
FDS
Elite member
There’s some stuff to sort out then. The model of the quad moves correctly in Betaflight? On the other controls?
Have you set the endpoints? 1200 is stupidly high for min_check.
Get the basics right first, then we will slowly work through. Binding isn’t your problem. It’s either bound or not bound, there’s not degrees of it.
Throttle channel reverse is in the TRANSMITTER, in the mixer screen or inputs. Easy to make a basic error.
Are you using the stock tune? Did you reflash the board?
Have you set the endpoints? 1200 is stupidly high for min_check.
Get the basics right first, then we will slowly work through. Binding isn’t your problem. It’s either bound or not bound, there’s not degrees of it.
Throttle channel reverse is in the TRANSMITTER, in the mixer screen or inputs. Easy to make a basic error.
Are you using the stock tune? Did you reflash the board?
Yes the model moves and I meant to type 1100 for min check. Are you implying the throttle channel in the physical transmitter is reversed, or the signal being received by config? If its a setting in beta, I'm almost sure I wouldnt have it enabled, otherwise I wouldn't be able to bring it back down if I keep it under a certain threshold. I'm using bf 10.6 with 4.1 firmware. Stock settings. I'm hoping it IS something simple.
FDS
Elite member
I did some further checking, I forgot you can’t arm with the throttle up. 1100 is still high for min check.
I would start by calibrating the sticks on the radio, then setting the end point to 1000 and 2000, then min check can be 1015 and put 5 in the RC deadband. 100 is loads of throttle deadband. So the channels all move correctly in Betaflight? Pitch, roll and yaw all do the right ting in the model?
Inputs screen order should match Betaflight, mine looks like this. AETR in Betaflight. Some BF screen shots would help.
I would start by calibrating the sticks on the radio, then setting the end point to 1000 and 2000, then min check can be 1015 and put 5 in the RC deadband. 100 is loads of throttle deadband. So the channels all move correctly in Betaflight? Pitch, roll and yaw all do the right ting in the model?
Inputs screen order should match Betaflight, mine looks like this. AETR in Betaflight. Some BF screen shots would help.
If the rtf tx can be calibrated, I dont know how. When the tx is on, beta shows my low-high range to be 1064-2013, hence the 1100 low threshold. My throttle deadband is on 50 and I put mid back on .50 I tried clipping throttle limit at 50% and the motors sounded like they wanted to wind down after rocketing but very slowly. Yaw, pitch and roll are all fine. Its literally just the throttle going out of control.
FDS
Elite member
Ah, I didn’t know you had the toy TX, that can’t be calibrated and it will be hard to set the endpoints with as well. I will dig through the screenshots.
Did you change anything else?
One more question. Is this happening with the props OFF, or does it do this when the props are ON?
Did you change anything else?
One more question. Is this happening with the props OFF, or does it do this when the props are ON?
Are those the stock PID's?
FDS
Elite member
You could try downloading the stock set up and re flashing the whole board. Before you do that learn how to do diff_all in CLI and save the resulting file, plus save the settings in Betaflight and get the target correct.
I have not had this problem with a whoop board before.
Where did you buy it? If you can contacting their CS May now be worth it as there could simply be a fault in it.
I have not had this problem with a whoop board before.
Where did you buy it? If you can contacting their CS May now be worth it as there could simply be a fault in it.
So I flashed the board multiple times under the assumption that bench spool up only happened on the bench.... I guess I JUST learned today that it also happens battery in, without props OR if you have props on but are too paranoid to break it and leave your hand on it....... Real facepalm moment but it works fine for now
Similar threads
