I need help - motors don't react to RC?

[mjr.tom.s]

Hello everyone.

I have purchased a replacement controller board for TinyHawk2 on Banggood. I thought is would be plug-and-fly....
But it doesn’t seem to work?
I installed and connected the board the same way as the original board was - same motor wiring - just plugged them. When I plug the battery the motor-beep (tü-te-lü-taaa-tüüüü) comes up correctly but then nothing happens (except the blinking of the LEDs RED and BLUE).
Checking the response in Betaflight (with USB connection) the radio is there and reacts normal (so binding seems to be ok?) and (with battery and USB attached) the motors work correctly when I use the slider in Betaflight. But no reaction when I move the throttle of the radio transmitter.
When I have battery and no USB connection it's the same. The BLUE LED light becomes steady though and when I arm the quad the RED LED changes frequency for a moment. Also the beeper works when I switch the AUX switch.

So my question is, is this controller board defective? Or do I have to do something differently to make it work (if so what)?

here is also a link to a short video that is supposed to show the issue. https://wetransfer.com/downloads/9dfaea08112068ef318fb348c9364e0920210509143002/452fd1

Thanks for your help.

 

[wafflejock]

Ah you cannot arm normally with USB connected. Just verify your modes has arm switch setup right but if you disconnect from computer should be all good They don't normally let it arm while USB is connected since would be tethered to the computer and dangerous with bigger quads. If you have goggles go into the OSD configuration and add "warnings" to the OSD and it should indicate why it won't arm if it is flipped over or throttle above 0 when arm switch hit etc.

 

[mjr.tom.s]

Ah you cannot arm normally with USB connected. Just verify your modes has arm switch setup right but if you disconnect from computer should be all good They don't normally let it arm while USB is connected since would be tethered to the computer and dangerous with bigger quads. If you have goggles go into the OSD configuration and add "warnings" to the OSD and it should indicate why it won't arm if it is flipped over or throttle above 0 when arm switch hit etc.

Hi. Thanks for your reply.
I suspect too, that I make a (beginner-) mistake somewhere.
But regarding your suggestion, no, that's not the problem. when I have battery only and no USB connection it's the same. When I arm the quad the LED is flickering but no reaction to the sticks... the beeper works when I switch the AUX switch.
So it must be something else...

 

[wafflejock]

Yah make sure your throttle reads 1000 when stick is at 0 and make sure stick is at 0 when hitting the arm switch that'll stop it from arming. Also if you can get dumps of the blackbox logs from betaflight configurator blackbox logs tab/section then can see why it is failing to arm potentially in there too, generally I just rely on the OSD/warnings text to give me some indication as to why things aren't arming though.

 

[mjr.tom.s]

Hi. Thanks. My throttel reading is 988 when stick is at 0. So I assume that's fine.
I have dumped my quad firmware and placed the one of the old board on it. Now the motors react to YAW, PITCH and ROLL. But no reaction to the THROTTLE... Strange, isn't it? When I connect the TinyHawk2 to Betaflight the sliders in the receiver section move when I move the throttle...
So I have connected the quad to BLHELI CONFIGURATOR and there seems to be something wrong with the esc 2 (file attached). But I cannot flash this esc (that's probably why the "FLASH ALL" button is not active. Is there any other way to get that straightened out?

 

[wafflejock]

That is indeed a weird one. After watching the clip a second time I saw you did try disconnecting at the end and were still seeing the same. Regarding the esc flashing or rather not being flashable I haven't encountered that issue myself yet ever but could certainly be related. Extra weird thing is I would still expect the other three to try and spin up and the fourth if unresponsive to cause it to flip out and then would disarm because of runaway take off protection built into betaflight. Think blackbox logs are the only way aside from osd to see what's happening with the arming though or why it's refusing that. Maybe expand the range on the modes tab for arm mode too in case the switch for some reason sees slightly different value than when bench testing.