kilrah
commented
4 years ago I just tried an X9D+ on 2.3.7, an R9M (non-2019) on 20190117 Flex set to transmit on 868 at 10mW in the menu and an R9 Mini on 20190201 Flex Fport. It needed a couple of tries but it bound and seems to operate correctly (don't have Fport capable hardware, but RX LED is green and telemetry is present). Maybe try a different "Receiver no" on the radio.
Make sure your radio has Flex FW loaded and is set to the right mode (868 or 900, not EU/FCC)
Your radio can't do ACCESS so no point checking that.
The receiver and module exchange their IDs and store them onboard or just the rx stores the tx module id?
The RX stores the module ID, that's all.
veselin4
stale[bot]
Highviz
Lagarda
3djc
X9D+(pre 2019) flashed with OpenTX 2.3.7 (opentx-x9d+-flexr9m-lua-noheli-sqt5font-en-2.3.7.bin) but I also tried without flexr9m option with different tx/rx firmwares. EEPROM 2.3.7 R9M 2019 Module (sticker on module says 2019 and SmartPort only but not specifying ACCST or ACCESS) is currently flashed with 20190117 flex accst firmware. R9MM/MINI receiver which i had for a while is currently flashed with 20190219 fport flex accst firmware. Problem is after upgrading from an old TX firmware that I had the receiver bound and working it stopped working and would not bind. Out of despair for the last 3-4 days I literally tried all possible firmware combinations available from FrSky (ACCESS,ACCST,FCC,LBT,with or without f.port even tried OTA firmware) and the closest I get to binding is I get telemetry back during the binding chirp, like it would say "low battery" and "telemetry recovered" but when i push the bind button again to store it or also tried pushing exit button it would disconnect and lose connection and resetting receiver or transmitter would not connect. It would say "telemetry lost" also the back of the module will switch from rapid blinking to just solid red after 1-2s of pushing the bind button to stop the chirping. Also the receiver will never go into a flashing red or green, it will be solind red and green in bind mode and just solid red if powered normally. One of the firmwares i had on during testing would cause the rx green light to be always on in bind or normal mode and the red would not be on at all which while looking promising would not bind and there was no connection between. The opentx firmware that was on the radio when they were bound and working was from a year ago and I am not exactly sure which version it was but believe it was 2.2.1 or 2.2.2. I was not updating tx for long time out of fear that something like that would happen or lose all my settings and models which was just 3 models. So flashing over 100 times the last 3 days and i noticed so many of the r9mm fw files were same in size but was flashing them anyway one by one and testing in between, then flash the next module fw and start over with all the rx firmwares, about 40 downloaded. Today I came up with the idea to sort them out and check them with a duplicate file checker that checks by their contents not just the file size and behold - only 8 different r9mm/mini file versions for ACCST from 20+ i was reflashing redundantly. I gave up on trying any more ACCESS versions as it looks like my pre 2019 x9d+ does not support it. As I also remember when I first started the r9 system an year ago I had no success with ACCESS fw. So I wrote some questions on some rc groups, read a dozen articles and videos. All instructional videos have slightly different hardware combinations, but most of them use older opentx fw. I assume the 2.3.7 opentx does not support intentionaly my combinaion of tx+r9module+r9rx becouse of the old internal hardware or there is bug. As just a consumer I have no idea of how the open tx and hardware work together and I am not even sure if I am asking the right questions or if I am using the right logic to come to my conclusions. I would like to ask if anyone on here is using 2019R9M module in their pre 2019 Taranis X9D+ ACCST 2.4GHz radio? Oh I also tried flashing the internal 2.4 module per a few online forum instructions, thankfully there were only 2 fw versions for it. Also some or most of you would probably know how the r9m binding process works would you please explain it quick to me? The receiver and module exchange their IDs and store them onboard or just the rx stores the tx module id? or maybe even the tx module sends it over to open tx to store it in the radio ?
Any help is appreciated, Thank You!