Discussion Beta85 ELRS quad and General Discussion Thread

[Lemonyleprosy]

You’re using ELRS- ELRS requires you to use aux1 2 position switch for arming.

[Pathfinder075]

The battery question was mainly because I came across two USB chargers for 2S packs, but they output 400ma and 600ma, which is more than the C rating for my batteries. It would be a nice hack to keep in my drone bag if it would work. The ability to plug into any USB port and charge a couple of LiPo's would be nice. Useful when I'm away from home and have access to USB socket, which seem to be found pretty much everywhere nowadays (shops, cafes, buses, trains, even my local McDonalds). It would be useful to be able to grab a cup of coffee and charge a couple of packs while I drink it.

https://www.ebay.co.uk/itm/184729291106
https://www.ebay.co.uk/itm/284509037677

The arm/disarm will be the advanced bit. I will re-watch the Joshua Bardwell video on setting up arming/disarming on the Jumper T-Pro ELRS. But I remember him saying it had to be on ch 5 for ELRS. His suggestion was to use the two top left switches to arm and disarm, but another Youtuber (Daniel Singer) suggested just using one of them with a duration requirement to allow something useful like turtle mode to be bound to the other one. Anyway, I haven't decided yet how I will set the buttons up. Probably one of the rockers will be mode, the other i don't want arm on, as it will be too easy to disarm if I knocked it. I should probably read whatever manual exists for EdgeTX and then try and build a plan of how to map everything.

Thanks for also clearing up the Betaflight/Betaflight Configurator bit. It seems a bit complicated to have two products to do what one could do, but c'est la vie.

Is their anything else I need to learn/do, prior to flying. Does ELRS need updating? I was sure I read somewhere you had to have versions match for both the drone and radio. Is that correct?

[Lemonyleprosy]

For ELRS, major firmware versions need to match on tx & rx. (ie: v2.x on tx, v2.x on rx). Can be 2.0 on tx and 2.1 on rx etc.
Set up a binding phrase, it makes life easier- you just power on and you’re bound, no fiddling with tiny buttons or repeatedly unplugging/plugging in the battery.

https://oscarliang.com/setup-expresslrs-...s-firmware
(If you scroll up to the top of that link he’s got a full overview of ELRS and guide to setting it up)

Edit- just realized what you bought has an spi rx:
https://www.expresslrs.org/2.0/hardware/spi-receivers/

If you run into any problems getting ELRS working, the ELRS Discord has active and very helpful people. Wouldn’t hurt to drop in and ask any questions before you start trying to update things:
https://discord.com/invite/dS6ReFY

I don’t believe you can update an spi rx through ELRS configurator- I think it’s baked into the flight controller firmware. I’ve got no experience with that, so I’m going to stop answering your ELRS questions so I don’t give you bad info. Definitely check out the discord channel linked above though.

[Pathfinder075]

After reading through those links and watching some videos I realised I should definitely be sober when i do that.

I will get on the discord and have a chat before I do anything with the radio/drone. For now i don't have them yet, they'll probably arrive Mon/Tues next week. So I have some study time.

So I had a look at the BetaFPV site and grabbed a text file containing the following:

Code:

# Betaflight / BETAFPVF4SX1280 (BHER) 4.3.0 Nov  3 2021 / 15:43:00 (0265565fa) MSP API: 1.44

# start the command batch
batch start

board_name BETAFPVF4SX1280

# name: 85 Pro 2-ELRS

# serial
serial 30 2048 115200 57600 0 115200

# led
led 0 0,0::A:0
led 1 1,0::A:0

# aux
aux 0 0 0 1600 2100 0 0
aux 1 1 1 900 1300 0 0
aux 2 2 1 1325 1700 0 0
aux 3 13 3 1700 2100 0 0
aux 4 35 2 1550 2100 0 0

# vtxtable
vtxtable bands 5
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B FACTORY 5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E FACTORY 5705 5685 5665 5645 5885 5905 5925 5945
vtxtable band 4 FATSHARK F FACTORY 5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable powerlevels 4
vtxtable powervalues 0 1 2 3
vtxtable powerlabels 25 100 200 350

# master
set acc_calibration = -59,29,96,1
set max_check = 2000
set dshot_idle_value = 450
set motor_pwm_protocol = DSHOT600
set yaw_motors_reversed = ON
set small_angle = 180
set osd_vbat_pos = 2391
set osd_rssi_pos = 2276
set osd_link_quality_pos = 2244
set osd_rssi_dbm_pos = 2212
set osd_tim_2_pos = 2403
set osd_flymode_pos = 2371
set osd_crosshairs_pos = 2253
set osd_current_pos = 2422
set osd_craft_name_pos = 2410
set osd_core_temp_pos = 182
set vtx_band = 4
set vtx_channel = 4
set vtx_power = 3
set vtx_low_power_disarm = ON
set vtx_freq = 5800
set expresslrs_uid = 240,8,209,216,234,88
set expresslrs_hybrid_switches = ON
set name = 85 Pro 2-ELRS

profile 0

# profile 0
set i_pitch = 99
set d_pitch = 35
set f_pitch = 105
set i_roll = 96
set d_roll = 34
set f_roll = 99
set p_yaw = 48
set i_yaw = 99
set f_yaw = 99
set d_min_roll = 0
set d_min_pitch = 0

rateprofile 0

# rateprofile 0
set tpa_rate = 60

# end the command batch
batch end
set dshot_bitbang = OFF

save

It also states to use the following firmware.

This Meteor85 Pro 2 ELRS CLI can be used for F4 1S 12A PRO ELRS V2.0 FC which is fit for Betaflight_4.3.0_BETAFPVF411 firmware. The picture and file name were marked as 2.

https://support.betafpv.com/hc/en-us/art...ta85-Pro-2

I have no clue what most of that means at the minute, but thought I'd post it here so i can retrieve it later if I need to.

What i do know.

Code:

set expresslrs_uid = 240,8,209,216,234,88

That is the binding phrase and it can be altered using the UID editor at the SPI link you provided.

[Lemonyleprosy]

Okay. It appears that the meteor85 comes running ELRS v1.
If your radio also comes running ELRS v1.x, then all you would need to do is use the ELRS configurator to set you binding code and flash that (making sure you stick with a v1.x) to your radio, then use that cli command (set expresslrs…. modified to match your binding phrase) in betaflight.

If your radio comes running ELRS v2.x, or you want to update it, then you’ll also have to flash betaflight 4.3 to your quad using the supplied target, and copy/paste the cli code they provide into the cli editor in betaflight. Then set your binding phrase.

Did I confuse you more?

[Pathfinder075]

No I kind of get it. But I might have more questions next week when it's all sat in front of me.

Also from what little info i can garner, the Jumper ELRS comes with version 2 of ELRS, so will probably have to flash the drone with the new betaflight, since the radio has a possible bricked flash issue that I would rather not encounter this early in my FPV'ing life.

[iFly4rotors]

No I kind of get it.  But I might have more questions next week when it's all sat in front of me.

Also from what little info i can garner, the Jumper ELRS comes with version 2 of ELRS, so will probably have to flash the drone with the new betaflight, since the radio has a possible bricked flash issue that I would rather not encounter this early in my FPV'ing life.

Hi Pathfinder,

Even if ELRS is different, you shouldn't have to flash Betaflight. You should be able to 
just reset the ELRS portion as Lemonyleprosy outlined.

Here is what I would suggest and I do this for EVERY new quad or new FC board that I buy.
In fact, I do these things BEFORE a battery is ever connected. This is just a good "safety"
measure and ensures that I can recover should something go sideways.

Make sure that you have the Betaflight configurator installed on a computer (PC) first:

1) Open the Betaflight configurator on the PC.
2) Plug a USB cable {must be a DATA cable} into the quad and into the PC.
3) Click "Connect" in the Configurator.
4) Open the CLI tab.

              For each command:
              CLEAR the screen.
              Type the command press [Enter].
              Save to File {I generally leave the name, but add to the end of it}.

6) DUMP   { I would do this even though it looks like you have the DUMP file}
7) DUMP ALL 
8) DIFF
9) DIFF ALL
10) RESOURCE
11) RESOURCE SHOW ALL

Just me , but I also take screen prints of the important stuff just so 
that I know what things were from the factory. I like having the visual. 

Now, if all of this sounds like "Overkill"...well, maybe it is, but I have all sorts of
backups and information just in case something should go sideways with the 
firmware for any reason. 

With all of this information, I can recover should I mess something up. 

[cst3x6]

Hi iFly4rotors,

What is the difference between the 6 commands above?

Also, do you know what is the difference between those and the Save Preset option on the Presets tab?

cheers

[cst3x6]

No I kind of get it.  But I might have more questions next week when it's all sat in front of me.

Also from what little info i can garner, the Jumper ELRS comes with version 2 of ELRS, so will probably have to flash the drone with the new betaflight, since the radio has a possible bricked flash issue that I would rather not encounter this early in my FPV'ing life.

I recently went through this with my meteor75 and zorro elrs.

I had the Zorro on the newest edgeTX and elrs firware versions and that did not work with the stock firmware of the meteor.  Flashing the new firmware is quite straightforward, just save a copy of settings as suggested by iFly4rotors and as you will see on the JB videos as well, then proceed with the flashing, reload the configurations and off you go..

There are a lot o people willing to help here as well in case you get stuck somewhere, which is a great thing.

[Pathfinder075]

I went on the ELRS Discord last night but havent got the kit here yet so it's kind of pointless to ask questions yet. My plan was to follow the ELRS Updating part on the SPI Guide, because the major versions are different from what i can tell between the Radio and Drone. If I can just update the ELRS that sounds easier. i wasn't sure if I could, or at least the BetaFPV site kind of made it out you had to upgrade everything to get ELRS 2.0 on to the drone.

Updating

As mentioned, you must flash a Betaflight firmware that's compatible with the ExpressLRS major version on your transmitter. ExpressLRS 1.x.x TX only works with Betaflight firmware for ExpressLRS 1.x.x, and upgrading the transmitter to ExpressLRS 2.x.x means flashing the flight controller with a different Betaflight version (e.g. Betaflight 4.3-RC1 5933d96). You don't need to update the FC firmware whenever there's minor updates on the main ExpressLRS codebase, unless there's any update on the Betaflight codebase itself for the SPI ExpressLRS receivers.

In preparation for updating, you should save a copy of your diff all dump.

Using the latest Betaflight Configurator, navigate into Firmware Flasher and select the latest Betaflight release (at the time of writing, it should be set to Release and Release Candidate; and use the latest 4.3.0 Release Candidate). Depending on your AIO board, the target will differ:

Happymodel AIO: CRAZYBEEF4SX1280
BetaFPV AIO: BETAFPVF4SX1280
SPRacing SPH7RF: Coming soon!

The Happymodel Mobula6 900MHz AIO with the CrazyF4 ELRS FC (Target: CRAZYBEEF4DX) doesn't use an SPI ExpressLRS receiver. Check the page for ES915RX instead.

Once flashed, you will need to paste in the diff all you have saved. Don't forget to type in save and press enter once done. Power cycle your flight controller, and you should be set. You may need to set your Binding Phrase once again if you pasted in Factory Diff All. Review your Betaflight settings (no changes needed for the Receiver Type and Protocol; should already be set with SPI Receiver, with Provider as ExpressLRS), and check your RC link in the Receiver Tab (were sticks moving?).

iFly4rotors, I will do your dump and diff bit before plugging any batteries in. To be honest I was going to do that anyway. Then save it somewhere safe, so I can always revert to it if I need to.

The confusing bit in Lemony's post is the supplied target part. Is the Supplied Target the firmware version, ie, Betaflight_4.3.0_BETAFPVF411?

If your radio comes running ELRS v2.x, or you want to update it, then you’ll also have to flash betaflight 4.3 to your quad using the supplied target, and copy/paste the cli code they provide into the cli editor in betaflight. Then set your binding phrase.

Remind me after doing this to write a step by step tutorial in plain English and publish it to this thread. It might save another newbie some grief and head scratching.

On a side note, I now have everything that i basically need to get flying. The batteries and charger(s) are now ordered. So in short I now have or have ordered:

Code:

Meteor85 ELRS Drone - £90
BetaFPV VR02 Goggles - £38
Jumper T-Pro ELRS - £58
SkyRC E3 charger - £13
Generic 2S USB balance charger (that may or may not fit my battery packs, but is modifiable) - £2
3x GNB 380mah LiHV batteries - £15
2x LG HE2 2500mAh 18650 batteries (for the Jumper T-Pro) - £10
4x Gemfan 2020 props - £3

I already have basic electronics gear (soldering iron, multimeter, cable, fuses, etc).

In case anyone is wondering how much all this cost I have included prices I paid for each item and the total was roughly £250 including postage charges. Bought from a host of different UK shops. YourFPV, UnmannedTech, HobbyRC, 18650.uk, WhoopStore.uk

Is their anything else important anyone can think of, that I am missing?

[cst3x6]

Is their anything else important anyone can think of, that I am missing?

I'd buy at least a couple more batteries if you can.

[SnowLeopardFPV]

I went on the ELRS Discord last night but havent got the kit here yet so it's kind of pointless to ask questions yet.  My plan was to follow the ELRS Updating part on the SPI Guide, because the major versions are different from what i can tell between the Radio and Drone.  If I can just update the ELRS that sounds easier.  i wasn't sure if I could, or at least the BetaFPV site kind of made it out you had to upgrade everything to get ELRS 2.0 on to the drone.

On the AIO FCs with a built in ELRS SPI receiver the ExpressLRS firmware code is baked into the Betaflight firmware code, so to update the version of ExpressLRS on one of those boards you need to completely flash a new version of Betaflight to the board. Just flash the latest version of Betaflight 4.3.0 to your FC and it will then be on ELRS 2.x. Then you just need to make sure your transmitter module is also flashed to ELRS 2.x and you are good to go. I highly recommend that you configure and use a binding phrase on both the receiver and transmitter as detailed in the ExpressLRS guide, then you won't ever have to worry about manual binding. The receiver and transmitter will just automatically bind themselves together when both powered on.

The confusing bit in Lemony's post is the supplied target part.  Is the Supplied Target the firmware version, ie, Betaflight_4.3.0_BETAFPVF411?

Just flash the same target that is already on the FC (i.e. CRAZYBEEF4SX1280). When you get the FC, connect it to Betaflighr Configurator and run the "version" command in the CLI. That will then tell you what Betaflight target your FC uses. Betaflight Configurator 18.8.0 does have an target auto-detect feature but I would still manually make a note of the already installed target before flashing any new firmware just in case something goes wrong or the auto-detect somehow manages to pick up the wrong target. In fact, before you do any configuration changes of flashing at all to the FC, run the "dump all" and "diff all" commands in the CLI and save the output somewhere safe on your computer. Then you will have a complete backup of the factory supplied configuration that you can always restore back to if you manage to screw anything up. Configuration backups are the first thing you religiously get into the habit of doing with any new FC, ESC or quad that you get as soon as you take it out of it's packaging.

[Lemonyleprosy]

Have the discord channel walk you through setting up a binding phrase on your tx, especially if it’s got a known bug. They can tell you what to do to not brick it.

For the quad:
Snow explained things much clearer.
Yes, you DO have to update the firmware on your quad in this case.
Do all of this without a battery connected. When I say unplug or plug in, I’m referring to the usb cable. It’s much easier to unplug it just from the computer side throughout all of this.

Betafpv says your target should be BETAFPVF4SX1280
But do as snow said and run version command in betaflight configurator to double check.

Once you’ve checked your version and made backups of everything, you’ll need to enter boot loader mode.
Easiest way to do this is to type bl into the cli and hit enter. It should reboot, and now at the top right of the screen instead of showing a com port it’ll say DFU.

Click the update firmware button next to that.
It should bring up a new screen below. Somewhere near the top of that screen is going to be a checkbox that you have to check or uncheck to get it to show you not just stable releases.
Pick the most recent 4.3 release candidate version (ie: 4.3 RC6)
^^^^EDIT: if your board has a ICM20869 gyro, don’t pick the latest release candidate, follow V-22’s direction later in this thread.

There’s another drop down menu where you choose your target. Choose BETAFPVF4SX1280 (or whatever you found when you ran the version command).

Make sure “full chip erase” is checked.

Near the bottom right of the screen click the “load firmware online” button.

Now click the flash button. Eventually it should tell you it’s successful.

Unplug your quad. Plug it back in. Hit the connect button. It’s going to ask you if you want to apply defaults. Click yes.
Now it’s going to tell you that it needs to be calibrated. Put your quad on a level surface and hit the calibrate accelerometer button.

Go to the cli tab. Copy paste the code you found before. Hit enter- it’s going to reboot.

Once you’re reconnected, go back to the cli tab.
Enter the code to change your binding phrase.
Type save. Hit enter. It’s going to reboot.

Unplug your quad. Make sure you’ve already set up a binding phrase on your radio. Turn on your radio. Plug your quad back in and connect to betaflight configurator.

Go to the receiver tab. Move your sticks on your radio, you should see movements on screen.

Now go to the modes tab and set up your buttons. You need to set up arm/disarm. Your using ELRS so this has to be aux1 (channel 5). You also need to set up your flight modes. Then hit save at the bottom of the screen.

Go fly.
Anytime you change something in betaflight, make sure you hit the save button before you change tabs or it won’t save. Anytime you change something in the cli, make sure you type save and hit enter or it won’t save.

Before you go fly, I’d suggest going back into the cli and entering: set vbat_sag_compensation=100
Then typing save and hitting enter. This will make it so that your battery output feels more even throughout the flight, rather than the throttle being super sensitive in the beginning and then requiring more and more throttle as your battery voltage goes down.

Also, anytime you’re plugged in on the bench, keep a fan blowing over your quad for airflow. I didn’t know what I was doing when I first started and had it plugged in for like half an hour trying to figure things out- that’s a real good way to burn out video transmitter. Once you’ve gotten it in the air and had a few flights, we can walk you through flashing bluejay on your esc’s and setting the pwm to 48khz so that you can maybe get a little extra flight time out of it. (If it’s not already set to 48. Also, this tends to be more noticeable on smaller whoops- regardless, it would still allow you to setup rpm filtering and dynamic idle. I think those are good things).

[iFly4rotors]

Hi iFly4rotors,

What is the difference between the 6 commands above?

Also, do you know what is the difference between those and the Save Preset option on the Presets tab?

cheers

Hi cst3x6,

I am not sure. In theory the DUMP ALL should get everything, but it seems you normally only
need the DIFF or DIFF ALL {again, I don't know the actual difference}. I do think that some
of the versions of Betaflight have different things so you can't just apply the DUMP or DUMP ALL
to just any version and have it work; so generally you use DIFF or DIFF ALL. The last two
things I like to have so that I don't have to weed through the code for it. Even though I have
not had to actually use these backups, I have them just in case.

I don't actually know what the "Save Preset" actually saves, so I not much help there.

[Lemonyleprosy]

Dump = all configurable settings
Diff = only things that have been changed from default in the current profile and rate profile
Diff all= only things that have been changed from default in all profiles and rate profiles

https://oscarliang.com/use-diff-not-dump-betaflight/

You can’t always use the same diff between betaflight versions. IE: don’t take your diff from bf 4.2 and try to use it in bf4.3 without running it through Safe Migrator:
https://bf43-safe-migration.robertodedomenico.it/

If by “save preset” you mean “save backup”, it’s the same as running the diff all command, and will save the diff all in a text file.