#Been having Trouble with updating Module

164 messages · Page 1 of 1 (latest)

untold sphinx
#

Im on 1.5 configurator. I had trouble last night using this windows user so I uninstalled, and created a new User and Installed there.
I got it to build on the new user account but I could not get this HappyModel ES24TX to update. It's on 1.0 firmware at least thats what it says when I connect it it wifi.

So it lets me connect to the wifi and I choose the new firmware but when I press UPDATE, it goes to the next screen that says FAIL in small letters. It then automatically disconnects from my computer. Or I guess my computer D/C's from its hotspot.

I have radiomaster tx16s and I first downloaded the new LUA script for 3.1 but when I click on it, it says ERROR: 1.x firmware.

The only way I can get to the wifi on the module is by clicking ELRS. When I click on ELRS LUA it brings me to a screen that says
ExpressLRS 010200 0:500
(more items)
but then it says [bind] and [wifi update]
and this is the way that I've got it to start its hotspot.

If im missing anything please let me know. I've tried building earlier firmware (2.22 i think) and that doesnt work either. I think it has something to do with the LUA script but dont know which one to get.

ALSO I was able to get the matek receiver updated to 3.1 by connecting to its WIFI.

Thanks for the help!

untold sphinx
#

if anyone can help please

west edge
#

If you're on 1.x flash to 2.x first before flashing to 3.x

#

The wifi page changed a lot in 2.x

untold sphinx
#

So try flashing to 2.x firmware using that old ELRS LUA script?

dire cliff
#

since your module is still in 1.x, you will use the old v1 ELRS lua script to put it into wifi..

#

OR
flash the module via USB

untold sphinx
#

ok so I tried flashing module to 2.x and it worked! And then was able to click on expressLRS LUA. I still had the 3.1 file so I tried updating to 3.1. It got all the way to 100% but said Update failed.

#

I tried again and it said update failed - not enough space.

dire cliff
#

!re

native moatBOT
#

If you get a "Bad Size Given" or "Not enough data" error when flashing your TX module to ELRS 3.x, here's your fix: https://github.com/pkendall64/repartitioner#what-is-this
Visit the Releases page: https://github.com/pkendall64/repartitioner/releases/tag/1.0 and download repartitioner.bin. Flash repartitioner.bin to your TX module via WiFi.
If you receive an error, flash your TX module to ELRS v2.5.1 first, then try again.
Once flashed, exit the lua script, relaunch it, then reactivate WiFi on the module and upload the ELRS 3.x firmware.
Note this is for TX modules ONLY, not receivers

untold sphinx
#

ok thank you! If that doesnt work, do i need to downgrade the receiver back to 2.0? Both are now flashed with the bind key.

dire cliff
untold sphinx
#

alright they need to be on the exact same firmware right

dire cliff
untold sphinx
#

alright thank you! Im guessing 2.0 is a really old version

dire cliff
#

3.0 > 2.0

#

2.0 was released Dec 11, 2021
3.0 was released Sep 09, 2022

untold sphinx
#

oh ok. repartitioner just opens up some space on the tx im guessing im. hopefully i can do that from this user. i think i can. Its a pain to switch. Im half dumb though lol. I was feeling pretty dumb last night trying to fix it.

dire cliff
#

it could report a Target Mismatch, but pressing Flash Anyway should force flash it..

untold sphinx
#

sorry one more question before i flash. Will i need to build a 3.0 firmware or can I just use the 3.1 I have built already?

dire cliff
untold sphinx
#

it worked! I thought it broke my module at first because no LUA was working until i restarted radio lol

#

now all I need to do is bind. My packet rate is 500hz, Telem Ratio is 1:64, Switch Mode Hybrid, Model Match OFF, TX Power = 10mw. Besides the TX Power is there anything I should be changing?

dire cliff
#

if receiver and tx module have matching binding phrase, then they should auto-bind

#

(if both are working normally, that is)

untold sphinx
#

i mean for flying thats where I would change the settings right

#

in the lua?

dire cliff
untold sphinx
#

alright thanks I will try now

#

props are off

#

it didnt bind yet. RX is still flashing red

dire cliff
#

!webui

native moatBOT
#

Connect to your transmitter's or receiver's WiFi network to access the web UI:

untold sphinx
#

if your getting tired of me ill go somewhere else lol

dire cliff
#

those UID numbers should match

dire cliff
untold sphinx
#

not you just i know im getting annoying

dire cliff
#

a C in the top right corner of the Lua Script will indicate receiver and tx module is bound..

untold sphinx
#

yeah i didnt get the C

dire cliff
#

a solid LED in the receiver also indicates both are bound

untold sphinx
#

im gonna try the wifi now

untold sphinx
#

alright so I was having trouble getting Rx wifi to work but finally did. Turns out it didnt update. It says Update completed but it doesnt actually update it.

#

TX is 3.01 and RX is 2.2.0

#

Also when I connected to TX wifi, it shows the binding phrase as empty. Idk if its normally like that but I did set a binding phrase before building it. I did not mess with that while connected to WIFI though.

#

I tried updating rx again but it doesnt update its stuck on 2.2.0

dire cliff
untold sphinx
#

ok i wrote down the UID numbers for TX but RX did not have them in the older firmware

dire cliff
#

there's two other updating methods for receivers.. try those methods

untold sphinx
#

is it possible to just downgrade TX firmware back to 2.2.0? I would just do that to get it flying for now

dire cliff
#

although, the binding phrase on the receiver and the tx should match still for them bo sync up

untold sphinx
#

for that betaflight passthrough for RX, would i need anything new like drivers? If I can just plug it in through USB and pass throuogh the FC that would be the best.

dire cliff
#

(you don't need betaflight configurator open and connected to fc when doing the passthrough flashing though)

untold sphinx
#

I think that would be best. and I would press Build and FLASH

#

hey I wanna say thank you for the help because I would have never figured this out man

#

Few more weeks and Ill be flying lol

#

maybe.. lol

dire cliff
#

follow the flashing guide for your receiver (although esp-receiver flashing guide were almost the same anyway)

untold sphinx
#

im doing some reading on it now. When I first soldered this on there, I had XM+ receiver installed on the same UART accidentally because it just plugs in. I didnt know that it was using the same UART and the light was solid red on ELRS receiver before unplugging that XM+. Its on UART 2 and Serial RX is checked.

dire cliff
untold sphinx
#

I shouldnt have to now should I?

#

I unplugged XM+ and now its just the ELRS receiver on the UART 2

#

the light isnt solid anymore it flashes now just to be clear

dire cliff
untold sphinx
#

yeah i hooked it up right T-RX, R-TX, 5v-5v,g-g

dire cliff
# untold sphinx yeah i hooked it up right T-RX, R-TX, 5v-5v,g-g

Manufacturer-suggested Receiver UARTs, or UARTs alloted for Receivers usually have a pull-down resistor to aid with SBUS (RX pad inversion) which will result into SOLID LEDs on the ESP-based ExpressLRS Receivers. It is best to avoid those UARTs unless you know your UARTs.

untold sphinx
#

alright. I think the light was red to start because the XM + was on the same UART. Now after unplugging it just blinks normally

#

if this doesnt work Ill have to resolder it on and that is tough for me but ill have to do it.

#

my hands where so shakey lol I practiced a lot on practice board and it seemed easy lol.

dire cliff
#

relax, calm your nerves..

#

it is not complicated. it is not hard..

#

flux and leaded solder are your friends.

untold sphinx
#

yeah it was surprisingly easy on the practice board. it pretty much just flows right on

#

im worried about having to redo it because I did pull up a pad on the practice board

#

while using the desoldering copper wick. I held it on too long

dire cliff
#

heat up your iron to ~320degC
tin wires and pad
heat tinned pad, solder melts, put in wire, remove soldering iron from pad, connection solidifies.. done

untold sphinx
#

yup exactly what i did

#

did you help build ELRS?

dire cliff
untold sphinx
#

oh ok.

dire cliff
#

mainly here helping with tech support

untold sphinx
#

your doing amazing job

#

I found docs on flashing passthrough for my receiver. I am about to try that

#

seems easy. Just plug in usb on FC and build and flash like normal

#

seems like i dont need lipo because receiver is powered on with usb

untold sphinx
#

alright i think i bricked it...

#

I did the passthrough and it updated and said success. I noticed that the light started blinking fast after the update was finished and the light was dimmer.

#

It said Update complete and Success or w.e but not when i power it up. It wont bind, it flashes quickly like its in wifi mode but will not start its wifi.

#

so I cant get in the see if it actually worked because the wifi wont turn on now.

#

I should have just downgraded with 2.2 on my module!

dire cliff
#

!recovery

native moatBOT
#

Follow these steps to recover a bricked RX:

- Move the 5v wire going to the receiver to a 5V pad that only powers on when a LiPo is connected 
- Disable Telemetry in Betaflight
- Save and Reboot
- Close Betaflight Configurator and unplug USB and LiPo
- Bridge the boot pads or hold down the boot button on the receiver
- Plug in USB
- Click "Build and Flash" in the ExpressLRS Configurator, selecting via Betaflight Passthrough method
- Wait for the line PASSTHROUGH DONE to appear
- Plug in LiPo (with boot button held down/bridged)
- Wait for the process to finish (with success hopefully)
- Unplug everything, unbridge the boot pads, then power on to confirm the LED blinks, and then goes into WiFi mode

Video Tutorial: https://www.youtube.com/watch?v=jYLwaWBkM_A

YouTube
DeltaGeek
How to Recover a Bricked ExpressLRS Receiver

https://www.expresslrs.org/2.0/quick-start/unbricking/

▶ Play video
untold sphinx
#

alright will try that. I wonder why it messed up?? I will try do just got to 3.0 this time. That is if I can get it working.

dire cliff
untold sphinx
#

yeah i was thinking i had it beat lol then that. I do have a button on the receiver so hopefully it will go into bootloader mode. at least the receivers are cheap! Someone actually gave me this module and receiver for free

untold sphinx
#

I read in the comments of someone having a similar problem and they said this
PRAFUL GUPTA
1 month ago (edited)
"I did fix this after getting help from devs on discord.

Steps -
Bridge the boot pads
Solder the 5v wire into a pad that doesnt work without battery (should not work with usb), if its a plug connector that would be the best.

Connect usb and click flash
As soon as it displays port forwarding message connect the battery/plug for elrs and it would work as expected.

The only trick is to not turn on the elrs till the port forwarding message is printed "

#

so there saying I have to unsolder the 5v and find a 5v that doesnt work without a battery and then flash but wait for the message then immediatly plug a battery in and it will work lol

#

Right now I have the ceramic antenna on this receiver. Do you have any recommendations on another receiver that I could buy?

dire cliff
untold sphinx
#

oh i didnt see that

dire cliff
#

The recovery method is something I have come up with in accordance to how r9 receivers are flashed, and it has proven to work with other users, such as the one you mentioned above, and myself as well..

untold sphinx
#

what would u recommend me to flash to. It was on 2.2 originally and 3.0.1 didnt seem to work

dire cliff
#

2.4 and earlier cannot be built on some systems due to an update to the platformIO packages.. 2.5.0 have resolved that issue by using a different package.

#

if you want to keep using 2.x, flash 2.5.1 into it.
if you want 3.0, then flash 3.x

#

I am partial to 3.0 as that makes it a lot easier to troubleshoot with regards to link and connectivity issues

untold sphinx
#

alright in your steps you say in the beginning to press and hold boot button. Then wait for the certain message. Do I need to be holding the boot button during the entire process before the message? Or just press and hold again to enter boot before pluggin the battery in for power?

#

I was so close to getting this working I felt lol I shold have just downgraded to 2.2

#

and if I look up pinout for my FC (I have nazgul5 v2 6s) will i be able to find where the 5v pad is that I need to solder to?

#

or is it just trial and error

dire cliff
#

you don't have to press and hold the button through the whole process..
just during the power up sequence during that "passthrough done" section of the log..
an alligator can help and in that case, you can keep it pressed

#

get a multi-meter, set it to voltmeter mode, DC
plug in usb to the fc

#

with the voltmeter, check each of the 5v pad if it'll read around 4.5 to 4.8v.. if they read 0v, then that means that 5v pad needs a LiPo plugged in..
that's where you'd want to wire up the receiver

untold sphinx
#

alright will do. I have one somewhere

#

Most people dont have this many problems huh

#

this is what the log said at the end

#

======== PASSTHROUGH INIT ========
Trying to initialize COM3 @ 420000

Attempting to detect FC UART configuration...
** Serial RX config detected: 'serial 1 64 115200 57600 0 115200'
Enabling serial passthrough...
CMD: 'serialpassthrough 1 420000'
======== PASSTHROUGH DONE ========
======== RESET TO BOOTLOADER ========

  • Using full duplex (CRSF)
    Cannot detect RX target, blindly flashing!
    Uploading .pio\build\MATEK_2400_RX_via_BetaflightPassthrough\firmware.bin
    esptool.py v3.0
    Serial port COM3
    Connecting......................................_____

A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header
*** [upload] Error 2
========================= [FAILED] Took 165.08 seconds =========================

dire cliff
untold sphinx
#

i didnt solder anything yet Im just posting what it said on the last time I tried to flash it

dire cliff
#

well, this is irrelevant since the procedure wasn't followed

untold sphinx
#

im reading here on the elrs website. it says "If you have a receiver with a button, just hold it down while you apply power to enter the bootloader. Keep holding the button until the configurator starts uploading to the RX."

#

when i did it, i only held just before the power up and then let go to see the red solid light.

#

Maybe I should try again a few more times but how long should I hold the button

dire cliff
#

unplug-replug USB, receiver NOT YET powered up, no light on receiver LED
click build and flash with via Passthrough Method selected
wait for the PASSTHROUGH DONE line to appear in the Log
Plug in LiPo while pressing and holding the boot button,
receiver LED turns solid, no blinks, release button
wait for the process to finihs

untold sphinx
#

i meant for the original way without resoldering anything. Im just making sure i was doing it right. did I just need to get it into bootloader mode then let go of the button then start configurator? Thats what i did. But i was reading on the website and it says to "hold it down while you apply power to enter bootloader. Keep holding the button until the configurator starts uploading to the RX."

#

I was gonna try it again if i was doing it wrong didnt know if I had to hold the button until i started the flash process

dire cliff
#

your log above is still saying Serial RX is configured on UART2

untold sphinx
#

no i didnt yet and that might be the reason it bricked idk. I'm looking into the best way to desolder it. I'm brand new to all this and have only soldered once really.

untold sphinx
#

@dire cliff Hey just wanted to let you know that I got it working. At least binded lol

dire cliff
untold sphinx
#

Im about to try that now.

dire cliff
#

C in the top right corner of lua script?

untold sphinx
#

my multimeter wasnt working but i just moved it to uart 4 and luckily it needed battery. I flashed to 3.0 just to be safe and it went through

#

C in the corner yes

dire cliff
#

if it's wired correctly, and the settings were spot on, then it should be working

untold sphinx
#

in LUA script my TX power is 10mw and I go into change it to 250 and it still says 10mw when i back out

#

i think 10mw will be better than my old XM+ tho

dire cliff
untold sphinx
#

My ground wire is soldered on but it could be better its kinda high up and not pressed down like it should be but it is solid so im hoping it stays

#

i used ISP as my zone idk if that limits the power

#

im not in EU

dire cliff
#

ism doesn't have any power limits

untold sphinx
#

im gonna test sticks in betaflight now. I do really appreciate the help lol. I was getting annoyed so i know you had to be lol

dire cliff
#

no, not really..

untold sphinx
#

stick movements are good and i turned telemetry back on in betaflight. Telemetry setting in betaflight is for goggles or what?

#

because even with that off I had full bars on tx16s

dire cliff
untold sphinx
#

those bars on my radio though like cell signal bars (5 of them) they reflect my link signal right?

dire cliff
#

yes. (in this instance, it's actually tied to your Link Quality, RQLY in the Telemetry page)

untold sphinx
#

I had to send my goggles back to RDQ today because the power button broke but should be flying again in a few days

untold sphinx
#

this has a little ceramic antenna on it and my drone came with XM+ mounted in this little TPU mount in the back. I can put this new receiver in the TPU mount but the carbon fiber cover is close and might touch the antenna. If not touch, it will be close to it. Will this affect the signal much? I dont plan on going miles with it because my goggles would lose signal for sure.

dire cliff
#

keep in mind the basic RF and antenna mounting conventions and you should be okay

untold sphinx
#

yeah its like perfect in terms of looks and fit but i feel like it might be bad in terms of signal

dire cliff