Hi all,

We are just starting out with the hobby and trying to connect the TinyHawk 3 Plus ExpressELRS with a Betafpv Lite Radio 3 Pro (ExpressELRS). 
However, this does not work. We tried via the Betaflight Configurator, via the CLI and via the GUI ("Bind Reciever"-button) but doesn't bind. 
When we put the drone in bind mode, the lights keep on flashing in different colours, by the way. Don't know if this is ok. 
Could someone help us out with a correct binding procedure or some tips ? 
Maybe they are not compatibel ? If somebody knows, let us know.

Thanks !

You would need to be sure that both your radio and receiver are on the same (main) ELRS version. TH3 Plus comes with a SPI ELRS RX where the ELRS version is tied to the BF version, in which case it is ELRS 3.x since it is BF4.4.
LR3 Pro radio, depending on when you purchased it, might have ELRS 2.x or ELRS 3.x. If you run the Expresslrs lua script and scroll down to the bottom, it should show you which version you are on. If it is 2.x, then you would need to upgrade the radio, but if that radio is bound to any other receivers, then that would mean you would also need to update those receivers to 3.x and rebind them.

This is the link on Betafpv website for updating the radio
https://support.betafpv.com/hc/en-us/art...to-ELRS-V3

Agreed. This is a very very very common issue. You have to get both transmitter and receiver on the same major version of ELRS.

When you connect the TH3 to Betaflight and connect, look on the upper left. In faint lettering it will tell you which version of the BF firmware is installed. If it says something that begins with 4.4, then you have ELRS 3 onboard. If it begins with 4.3 then you have ELRS 2 onboard. You have to upgrade the firmware. Usually you can do this directly with BF since the receiver is SPI.

And yes, like mstc says above, you have to check your transmitter, too. Follow his instructions.

Hello,

We have just tried to flash the lite radio 3 pro, but whenever we tried to do that an error message always came up.
We also could not connect the radio to the betafpv configurator.
do you regconize any issues?

Best regards,

What error are you getting? Seems there maybe some extra steps that Betafpv did not document. You might want to try following the instructions on Expresslrs website.

https://www.expresslrs.org/quick-start/t...fpvlr3pro/

Otherwise Betafpv also has this guide
https://support.betafpv.com/hc/en-us/art...-4-version-

(27-Jan-2024, 09:41 PM)mstc Wrote: What error are you getting? Seems there maybe some extra steps that Betafpv did not document. You might want to try following the instructions on Expresslrs website.

https://www.expresslrs.org/quick-start/t...fpvlr3pro/

Otherwise Betafpv also has this guide
https://support.betafpv.com/hc/en-us/art...-4-version-

When we tried flashing we got an error that there is not enough space...

Could update firmware with tutorial from Joshua Bardwell. First flashing repartioner.bin and then 3.0 firmware.
We now got some response in Betaflight Configurator and drone responds to Radio, but motors don't work.
Get message "RF Signal Critical" on the radio and "telemetry lost/telemetry recovered".
Does not seem a range thing, because we tried up close and further away.

Great progress!, fpvNewbie.

Lots of info to absorb in a short time!  I'm sure V-22 and mstc will be weighing in on the final issues, but I can add that I myself got stuck in these areas, and the info was spread out far and wide.

1) If the quad is on the bench and given power, the props should be removed. (Safety)
2) You may make some adjustments here that take some time, so a small fan should be directed at the quad to save the VTX from undue heating (will burn up).
3) Tab one in Betaflight shows "Disarm Flags" to show you why the quad will not enter armed status. (USB plugged, for example )
4) Aux1/Chan5 for Arming (1000=disarm/2000=arm) is a requirement unique to ELRS, but commonly used by other links, a nice "standard".
5) Motor RPM climbing on first arm (without props) is fine, not a problem, the FC is trying to do its thing!

As to the Controller feedback on RF Signal and telemetry alert, often the packet-rate and telemetry ratio settings (on the Radio LUA menu page ) are suitable for more advanced link/FC hardware and can be reduced to clear those alerts.  The standard range check (3meters, -dB readings) ...

https://www.expresslrs.org/quick-start/pre-1stflight/  and other tips on this page will clarify.

You've learned a lot in a short time.  "Make one change at a time and make note of the effect, many of the notes will later be presumed."

Good work,
wizofwires

If you go into the BF Configurator RECEIVER tab and move the radio sticks, do you also see the respective channel bar moving?

If it does, then go into the MODES tab and look at the arm mode to see which channel it is mapped to. If you move the appropriate switch on your radio, you should see the ARM mode get highlighted. If you need to use a different switch, you can reassign the channel. Change the dropdown to auto, and then move the switch on the radio you want to use, configurator should automatically show the corresponding AUX channel.
You may also want to remap any of the other switches (such as beeper or flip over after crash).

If you want more details on the RECEIVER tab, maybe this will help.


For the warnings on your radio, if you only hear this once when you first turn it on, it may not be a issue. But if it is repeatedly giving you those warnings, then check that the antenna on the AIO is not damaged. I am not sure what EMAX is using, either there is a tiny cube/ceramic tower antenna on the board, or an approx 28mm stiff wire sticking out, or a T-dipole antenna. Also what is the packet rate set on your radio (you can see it in the lua script)?

(28-Jan-2024, 06:09 PM)mstc Wrote: If you go into the BF Configurator RECEIVER tab and move the radio sticks, do you also see the respective channel bar moving?

If it does, then go into the MODES tab and look at the arm mode to see which channel it is mapped to. If you move the appropriate switch on your radio, you should see the ARM mode get highlighted. If you need to use a different switch, you can reassign the channel. Change the dropdown to auto, and then move the switch on the radio you want to use, configurator should automatically show the corresponding AUX channel.
You may also want to remap any of the other switches (such as beeper or flip over after crash).

If you want more details on the RECEIVER tab, maybe this will help.


For the warnings on your radio, if you only hear this once when you first turn it on, it may not be a issue. But if it is repeatedly giving you those warnings, then check that the antenna on the AIO is not damaged. I am not sure what EMAX is using, either there is a tiny cube/ceramic tower antenna on the board, or an approx 28mm stiff wire sticking out, or a T-dipole antenna. Also what is the packet rate set on your radio (you can see it in the lua script)?

Hi,
First of all thank your for all your help ! Very much appreciated !
For your questions:
Channel bars are moving.
Switch is mapped to AUX1 and mode gets highlighted.
Packet rate in the lua script is 500 Hz.

Its good that is setup correctly, you can also refer to Wiz's post of additional points to check.

Your throttle stick must be at minimum to arm, and if your throttle low point is set too high that could prevent arming. But there can also be other reasons.
If your video feed is working and with OSD, it will often show a message there. Otherwise you can plug in to BF configurator as Wiz described, it will not arm, but the flags will tell you if there are other issues. It should show MSP and ARM_SWITCH only, if there are other flags then that is the reason your quad will not arm.

We just got airborne ! ;-)
Thanks to the Reciever video and your help.
Massive thx all !!!!!

Hello

I recently bought the meteor 65 pro, I want to connect it to betaflight so I can flash it...
But when I get into betaflight there doesn't shows a serial port up and if I look in device management it also doesn't show up...
Can anyone give me an answer as soon as possible cause it's a gift for my son's birthday...

Regards

Hi NewtoFPV,

Try running the ImpulseRC DriverFixer utility, (download) from here. Don't fret if it takes a minute, to see if the serial port you need appears in the upper right
connection area.  (it's a pulldown menu, but should auto-populate).  Don't go about any tuning or flashing immediately, wait to see what you've got, then ask questions about proposed changes here.  From my limited experience (3 Meteor 65s), the out of box functionality was fine. With ELRS, the most difficulty has to do with binding, which may also require connecting to the ExpressLRS Configuator.  WiFi should be an option there, but "flashing" and "setting the binding phrase" are two sides of the coin ( and often confused ).  Might help if you can give a deeper dive into the issue that requires flashing??

All the best!
WizofWires

Hello,

Thanks for the reply, I fixed the problem the problem was not that my drone was not on the same version but because I had turned on model match...
Thanks for your reply!