Can't Flash RX6R Access

[DJC]

First time with the X9D+2019 and the RX6R. Succeeded in updating X9D+ to OpenTx 2.3.15. Got the Rx firmware in the SD Firmware folder: RX6R_ACCESS_2.1.7.frsk.
Enabled the External RF port,
connected the Rx with the cross-wire adapter to the External Bay pins.
Rx is flashing Red LED.
Navigate to SD-HC CARD/FIRMWARE/RX6R_ACCESS_2.1.7.frsk,
press scroll wheel,
get menu with "Flash S.Port Device",
press Scroll wheel,
pops up file name, says "Device Resetting", (Red LED stops),
then says "Firmware update error, Device not responding", Red LED resumes blinking.

I have an O'scope, and can see the Tx sending data on the Sbus wire, and I see 7.4 VDC on the power pin.
I see 17.6 usec pulses at 3.3 v, good shape, which implies 57600 baud.
Was expecting 115200 baud or 460800 baud.

How do I know what the OTx baud rate is? and Where do I set it? What should it be?

So many questions.
Thanks

 

[DJC]

Adding:
External Port set to SBUS

 

[HENNY]

SBUS has nothing to do with flashing a receiver. Yes sometimes the transmitter does not get the receiver reset. If you initiate the flashing a second time it almost always works.

 

[DJC]

Henny, Ok, I get that the Rx SmartPort doesn't want to see SBUS protocol. But what should the External RF module be set to? Does flashing Rx set a protocol independent of the External RF settings? I notice when I press "Flash S.Port Device" the +voltage to the Rx turns off. So I hooked up an external 5VDC supply to the RX, disconnected the +Bat wire from the Tx pins and tried flashing with various settings of the External RF. No change, still says "Firmware update error, Device not responding" (And the Red LED blinks continuously).

Help!
Thanks

 

[DJC]

Now I see... with the X9D+2019, there is a SmartPort connector in the battery bay. When I used this port, the Rx flashed immediately. Not sure if the External RF pins were sending data at all in my previous attempts.

 

[HENNY]

Now I see... with the X9D+2019, there is a SmartPort connector in the battery bay. When I used this port, the Rx flashed immediately. Not sure if the External RF pins were sending data at all in my previous attempts.

It would have worked if you had used the reversing cable and selected External as the flash to source. Anyway you are done and on your way. Good Job.

 

[DJC]

So, now binding troubles. I have for the RF:
ISRM-S-X9DP2019_2.1.6.frsk
And for the RX:
RX6R_ACCESS_2.1.7.frsk

Do they both need to match? Both 2.1.6 or Both 2.1.7?

Thanks

 

[Flying Dutchman]

A word of warning on the RX6R: it's very easy to brick it by using the wrong update file. Upgrading this Rx to ACCESS does not make it an Archer model, so you can't use the latest Archer update (currently 2.1.10). You already have the latest update for this one (2.1.7), so don't be tempted to use the Archer update on it. If you do, you WILL brick an RX6R and you will NOT be able to recover it. I'm usually pretty careful with these things, but I bricked mine this way.

 

[DJC]

Henny, I did use the external port with crossed cable, didn’t work. Because, the +bat line went low during flash attempts. I’m thinking the X9D+2019 doesn’t support flashing from ext RF bay?

Dutch, not trying for Archer, no prob. But still, do Rx and RF have to have same versions? 2.1.6 or 2.1.7?

Thanks

 

[Flying Dutchman]

No, the Tx and Rx versions do not need to match. The only thing that matters is that they're both V2. The fact that these numbers are so close is a source of confusion, one that bit me.

I don't expect much updating of our 'older' radios and ACCST Rx's now that FrSky is focusing completely on Tandem and Ethos, but they'll probably do more ACCESS Rx updates.

 

[HENNY]

With ACCESS the binding process is a two steep operation. Firstly you need to register, then bind. Is that what you are doing.. So to register push and hold the RX button then power on the RX, wait a second or so before letting the button go, and the red and green leds should be on solid. Then on the TX select register, keep the TX and RX about 3 feet apart, if reg is successful the tx will confirm your RX type and then confirm registration successful. To Bind put the TX in bind mode then power on the RX don't press any buttons. If successful the TX will confirm binding successful.

 

[Chris]

FYI... When flashing a receiver through a module bay, leave the module OFF. The radio will turn it on to update the receiver. It will not work with the module bay on.

 

[DJC]

FYI... When flashing a receiver through a module bay, leave the module OFF. The radio will turn it on to update the receiver. It will not work with the module bay on.

Yeah, I observed that the module bay +V was going OFF during flash. Maybe that was because Ext RF was set to ON and the s/w can't cope with turning module OFF while turning flash device ON. Should test this, but once I got it to flash using the SmartPort in the battery bay, I moved on to other things.

 

[DJC]

With ACCESS the binding process is a two steep operation. Firstly you need to register, then bind. Is that what you are doing.. So to register push and hold the RX button then power on the RX, wait a second or so before letting the button go, and the red and green leds should be on solid. Then on the TX select register, keep the TX and RX about 3 feet apart, if reg is successful the tx will confirm your RX type and then confirm registration successful. To Bind put the TX in bind mode then power on the RX don't press any buttons. If successful the TX will confirm binding successful.

My misunderstanding on the Bind sequence, I was pressing the scroll wheel for Bind AFTER powering the Rx. Once I pressed Bind first, it all worked. Thanks,