Hello all,

I am just getting into this, I managed to get this far with all the used stuff I purchased online, but I am having issues I can't seem to isolate.

I have a Jumper T12 (firmware v2.2.2) Transmitter with External module that binds to the FrSky XM SBUS Micro Receiver (solid green light) but no response. I see the gimbal response on the transmitters display with it registering movement. Beta flight also is showing response to my TAER1234 channel mappings.

My arm, buzzer and turtle switches are configured on the transmitter as well with responses indicating on Betaflight.

I have factory reset the transmitter thinking it would fix it, but nothing.

One thing: My flight controller is a F3 Mini Magnum, before and after being bound I see the blue light solid and the red light blinking constantly, is that normal?

Anyway, I am pretty close to just buying a new drone tired of buying parts for it, however I am glad in a way as I have learned a lot so far.

Thanks in advance for your help!

A blue LED and blinking red on the flight controller is normal. It means that the Betaflight firmware is installed and running on the FC.

When you say you aren't getting any responses, what do you mean? If you move your transmitter sticks are you seeing any movement of the bars in the Receiver tab of Betaflight Configurator, or not?

Update:

I just issued the CLI command serialrx_inverted=ON and the red light on the FC stopped the steady blinking. It stays blue, but no throttle response (armed), but after moving the throttle it seemed to be that the red light started to blink in sync with the beeping on and off.

(20-Mar-2021, 12:04 AM)SnowLeopardFPV Wrote: A blue LED and blinking red on the flight controller is normal. It means that the Betaflight firmware is installed and running on the FC.

When you say you aren't getting any responses, what do you mean? If you move your transmitter sticks are you seeing any movement of the bars in the Receiver tab of Betaflight Configurator, or not?

I am not getting throttle basically, with it armed. The transmitter and Betaflight show inputs, it just the Babyhawk motors not spinning when throttle is given. Which makes me believe even if I am hitting the arm switch, it's not really armed.

Your throttle needs to be in the fully down position to successfully arm the quad, so make sure that is definitely the case.

If it's still not arming then with the arming switch in the disarmed position, run the "status" command in the CLI and post the results back here. Run the same command again (and also post the results of that) with the switch in the armed position.

MCU F303 Clock=72MHz
Stack size: 2048, Stack address: 0x10002000
Config size: 2522, Max available config: 4096
System Uptime: 10164 seconds
CPU:40%, cycle time: 141, GYRO rate: 7092, RX rate: 110, System rate: 9
Voltage: 1041 * 0.01V (3S battery - WARNING)
I2C Errors: 0
SD card: None inserted
Arming disable flags: CLI MSP

# status
MCU F303 Clock=72MHz
Stack size: 2048, Stack address: 0x10002000
Config size: 2522, Max available config: 4096
System Uptime: 10178 seconds
CPU:40%, cycle time: 137, GYRO rate: 7299, RX rate: 111, System rate: 9
Voltage: 1037 * 0.01V (3S battery - WARNING)
I2C Errors: 0
SD card: None inserted

Does the ESC/Motor Protocol matter? The Babyhawk R has the Emax RS1106 motors.
I have these options available in Betaflight:
PWM
ONEHSOT125
ONESHOT42
MULTISHOT
BRUSHED
DSHOT150
DSHOT300
DSHOT600
DSHOT1200
PROSHOT1000

You missed off the "Arming disable flags" line from the second "status" command.

What is the ESC protocol currently set to? It should be set to either DSHOT600 or DSHOT300.

Okay, I got it to work, my Mode AUX settings were incorrect.
Now I have another problem of the throttle not being linear, its very erratic and unpredictable. I tried all the Motor Protocols seems that only DSHOT600 is the one it responds to...

If you are testing the motors with props off on the bench then that behaviour is normal. Have a watch of the following video to understand why. You need to do a hover test with the props on outside to see if everything appears to be working properly. Just make sure you have your finger over the disarm switch in case anything goes wrong.

(20-Mar-2021, 02:33 PM)SnowLeopardFPV Wrote: If you are testing the motors with props off on the bench then that behaviour is normal. Have a watch of the following video to understand why. You need to do a hover test with the props on outside to see if everything appears to be working properly. Just make sure you have your finger over the disarm switch in case anything goes wrong.

Yeah, unfortunately, that is not the behavior from that video.

The problem is better described as; when I arm the Babyhawk, the motors spin slow, but increase in throttle doesn't happen till about mid way on the gimbal. Even then the throttle at mid, the motors spool up all the way up. Then any further movement to increase throttle on the gimbal doesn't do anything. It also does not slow down after it reaches the max, when bringing gimbal down to minimum, I have to disarm it.

I don't know if it's the PID tuning, or the ESC proto? I am using DSHOT600 

If you are doing any testing of the throttle with the props off, or by holding the quad down with props on (which you definitely shouldn't be doing for safety reasons) then the behaviour is unpredictable. The only way to properly test the behaviour of the motors is to take it outside for a test hover while keeping your finger over the disarm switch just in case it tries to fly to the moon.

Are you running the Betaflight settings as supplied on the EMAX Babyhawk from the factory, or have you been changing values?

(21-Mar-2021, 12:24 AM)SnowLeopardFPV Wrote: If you are doing any testing of the throttle with the props off, or by holding the quad down with props on (which you definitely shouldn't be doing for safety reasons) then the behaviour is unpredictable. The only way to properly test the behaviour of the motors is to take it outside for a test hover while keeping your finger over the disarm switch just in case it tries to fly to the moon.

Are you running the Betaflight settings as supplied on the EMAX Babyhawk from the factory, or have you been changing values?

Arming it beings a low RPM spin with the throttle all the way down at minimum.
The bottom half of the throttle stick seems to show no increase in throttle with props on. As soon as I pass the half way, it spools up an then shoots to the moon.

I am trying to find the EMAX Babyhawk settings for BF from factory for the life of me. I can't find it for the Babyhawk R. Will keep looking.

I think i might of found another prob. I am running BF 4.0.3 and it seems it needs to be downgraded to 3.2.3 because of features issues, per my research anyway.

https://emaxusa2.freshdesk.com/support/s...3-firmware