Hi,
So I replaced (and when I say I , I mean someone else, not have the soldering skills yet unfortunately) the reciever from R9 to express elrs),
I bind it to my controller, with no issues.
However beta flight doesn't get the commands from the remote.
I set it up as Serial , CRSF, UART 2, serial RX

In terms of soldering I am not too sure unfortunately but can take it back

Make sure rx/tx isn't soldered on in the wrong order. If everything else checks out, make sure this is right both on the receiver and the FC side.

This seems mostly like advertising, and this is the wrong forum for that. See the forum rules.

Why do you think that's the best place to get gear? I'm a fan of Pyrodrone.

How would we find your posts helpful? You only have one post. You might want to introduce yourself with an intro post.

Actually, I do find your battery recommendation interesting, but instead of posting a link to your website, you could have just shared your gear recommendations--perhaps in a new thread. That way your post isn't just clickbait.

(22-Jun-2023, 03:17 PM)aerokam Wrote: This seems mostly like advertising, and this is the wrong forum for that. See the forum rules.

Why do you think that's the best place to get gear? I'm a fan of Pyrodrone.

How would we find your posts helpful? You only have one post. You might want to introduce yourself with an intro post.

Actually, I do find your battery recommendation interesting, but instead of posting a link to your website, you could have just shared your gear recommendations--perhaps in a new thread. That way your post isn't just clickbait.

ummm what?


EDIT: ok I suppose that was meant to mattyfleischfpv, Not sure about the AD but I do appreciate the help.

Took me a minute to realize what aerokam was referencing- I usually access this forum on my phone, so I don’t see people’s signatures unless I switch off of mobile view.

To the OP, as Matty said, make sure that you are wired correctly- it doesn’t go tx to tx, or rx to rx.

The wiring needs to go from the tx pad on the receiver to the rx pad on the flight controller, and vice versa.

TX —> RX
RX —> TX

If you post clear pictures of your receiver and flight controller wiring, we can double check that it was done correctly. If it is, then we can move on to other troubleshooting possibilities.

A bit hard to see but looks like:
White R2->TX
Yellow T2->RX

So looks right.
Let me try post a photo...

I think I can see the issue!!
TX is connected to nR2
and not R2
so changing it to R2 should sort my issue?

Yes, or, you can just connect to the expressLRS web ui with your receiver, and select the “Invert TX pin” option, then click save and reboot.

https://www.expresslrs.org/quick-start/webui/

That nR2 pad is an inverted R2 pad. Setting the option above will make your ELRS receiver send out an inverted signal that can be read by the nR2 pad.

If that doesn’t make sense to you or you don’t know what I’m talking about, let me know and I’ll expand on it.

Definitely move it to R2, don't use the inversion option as if you leave it wired that way you will not be able to flash via Passthrough, use Betaflight over WiFi, etc.

If the receiver LED is on solid after making that change, you'll need to use a different uart for the receiver.

(23-Jun-2023, 03:01 AM)V-22 Wrote: If the receiver LED is on solid after making that change, you'll need to use a different uart for the receiver.

In that case would it still work on the nR2? If the OP is not comfortable doing their own soldering, maybe using the inverted tx setting is a better option. Firmware can always be upgraded by wifi, I still often find passthru flashing quite fussy as something on my PC seems to lock up the serial port if I don't get the timing just right.

(23-Jun-2023, 03:51 AM)mstc Wrote: In that case would it still work on the nR2? If the OP is not comfortable doing their own soldering, maybe using the inverted tx setting is a better option. Firmware can always be upgraded by wifi, I still often find passthru flashing quite fussy as something on my PC seems to lock up the serial port if I don't get the timing just right.

OP said it bound with no issues, so it would probably work, but still not ideal for the reasons I mentioned.

Do you have Cura or anything running? Next time you have trouble flashing via passthrough, post the log and I can help you figure out why it's failing.

Yes, I do usually have a cura window open. Is that what is stealing the serial port? I am so used to using wifi, but will try passthru on my next flash. I see Betafpv instructs turning off telemetry in BF, is that also a necessary step?

(23-Jun-2023, 05:18 AM)mstc Wrote: Yes, I do usually have a cura window open. Is that what is stealing the serial port? I am so used to using wifi, but will try passthru on my next flash. I see Betafpv instructs turning off telemetry in BF, is that also a necessary step?

Almost certainly! Cura is notorious for taking any available COM port as soon as it's available. Try killing Cura before flashing next time.

Telemetry only needs to be disabled during recovery flashing. For normal flashing it shouldn't be an issue.

Just tried passthrough with Cura closed and seems the configurator had no problems opening the serial port. However I get this error:
ModuleNotFoundError: No module named 'serials_find'

Per the discord support, seems 2.x is no longer supported for BF passthrough? Guess its back to wifi flashing for me as I am still on 2.x

I did manage to flash everything just fine but I think only the wifi worked.
Also asked a friend to change the soldering (only seeing the replies now) , I will see him tuesday and if it wasn't done yet, i'll try the command.
thanks.,