I was attempting to register a new R8 pro rcvr for a new plane setup. The receiver would not register so I tried others to no avail. I then checked airplane that I had been flying and the LEDS ON THOSE RECVRS JUST HAD A RED led AS IF they were waiting for the Tx signal. I went to System on the Tx and scrolled to the info page and it is blank. It does not show what version the internal ISRM RF module is. I tried re-flashing the ISRM firmware but get this message, "Firmware update error Device not responding
Aloft Forums
Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
can't register Frsky access receivers receivers
- Thread starter richjanz
- Start date
I am using the internal antennas. I am running OpenTx 2.3.15. When I go to "System" on the Tx and page over to "INFO" and select "Module/receiver version" there is nothing listed there.
It's like the internal module doesn't exist. I don't know if I did something stupid or could it be that the internal ISRM RF module is bad. When I start up the radio all of my airplanes are there with all of the settings it just doesn't seem to be transmitting.
It's like the internal module doesn't exist. I don't know if I did something stupid or could it be that the internal ISRM RF module is bad. When I start up the radio all of my airplanes are there with all of the settings it just doesn't seem to be transmitting.
No it has not had any physical damage.My original intent was to register and bind a new receiver to a new plane I was setting up. After several attempts it finally did register and bind but when I tried to register and bind a second one it would not. Now none of the receivers in all of my planes do not respond. The LED on the receivers just remain red not green
Are you aware that the binding process for ACCESS is a two step operation. First you register, the TX will tell you if this operation is successful. To register first power up the receiver while holding the reg button down then apply power, then wait an addition second before releasing the reg button, if you have done this successfully the red and green led will be on. Then at the TX click on register. This sequence is important. After reg is successful then use the bind function. At the TX click on bind then power up the receiver, don't press the reg button simply power the receiver on. follow instructions to complete the operation.
Landru
Strong User
Good thinking.
What has me wondering whether the issue may extend beyond any possible operator error is the fact that the ISRM cannot be queried in the OS. Nor can its firmware be updated.
I'm not sure if we're dealing with OpenTx or EthOS here. In my QX7 ACCeSS running OTX, I couldn't find any means to reproduce the 'missing' ISRM via inappropriate settings in the OS. Perhaps such a scenario exists in EthOS? It might be weird if it did but, who knows, perhaps there is an unintended path to disabling the ISRM. Otherwise, could we looking at a hardware issue?
In OTX, there's a reset to factory defaults option. That might be something to try -- after making backups of all model and radio settings.
What has me wondering whether the issue may extend beyond any possible operator error is the fact that the ISRM cannot be queried in the OS. Nor can its firmware be updated.
I'm not sure if we're dealing with OpenTx or EthOS here. In my QX7 ACCeSS running OTX, I couldn't find any means to reproduce the 'missing' ISRM via inappropriate settings in the OS. Perhaps such a scenario exists in EthOS? It might be weird if it did but, who knows, perhaps there is an unintended path to disabling the ISRM. Otherwise, could we looking at a hardware issue?
In OTX, there's a reset to factory defaults option. That might be something to try -- after making backups of all model and radio settings.
Landru
Strong User
Hey again, Rich, I've just had another thought:
When you checked the model that you had been flying, did the model enter failsafe? Did you hear any warning about low RSSI or any other warning?
If model's failsafe settings were not applied and no warning was heard, your problem would resemble incidents a number of us have encountered, albeit ours were much more ephemeral. It's a long shot but I thought to ask.
Andrew
P.S. Please be careful if you test the scenario again. You're potentially dealing with an uncontrolled model with spinning prop(s).
Last edited:
I am well aware of the registering and binding process as I have a few other receivers that were were already registered and bound. None of them are responding to any commands from the tx.
I have OpenTx but cannot find the reset command, however there is a hard reset button on the bottom of the tx.
The models that I have been flying are not responding at all. There is no RSSI being sent back to the tx
I have OpenTx but cannot find the reset command, however there is a hard reset button on the bottom of the tx.
The models that I have been flying are not responding at all. There is no RSSI being sent back to the tx
Landru
Strong User
Yes, understood that there is no response to control commands and no reported RSSI. 
What I was curious about is whether the OS announced any alarm or whether the receiver went into failsafe.
Reading between the lines, my hunch is that neither occurred in your case. If so, your experience is at least superficially similar to other documented cases of a sudden loss of communication between a transmitter and receiver for no apparent reason -- and without warning or failsafe. A number of pilots have encountered such a problem, some more than once, myself included. Just as in your case, some incidents became apparent as soon as a model was powered up using a transmitter that had worked properly days, hours, or even minutes earlier.
The weirdness has been given the name of no failsafe lockout or NFL for short. A failure of communication between the transmitter OS and the transmitter RF module is one of the unproven hypotheses. Mind you, all previously reported NFL either resolved on their own after some time, or were resolved by power cycling the transmitter and/or receiver. In that regard, your issue is different. It may or may not be related.
Here's how to do a factory reset in OpenTx:
What I was curious about is whether the OS announced any alarm or whether the receiver went into failsafe.
Reading between the lines, my hunch is that neither occurred in your case. If so, your experience is at least superficially similar to other documented cases of a sudden loss of communication between a transmitter and receiver for no apparent reason -- and without warning or failsafe. A number of pilots have encountered such a problem, some more than once, myself included. Just as in your case, some incidents became apparent as soon as a model was powered up using a transmitter that had worked properly days, hours, or even minutes earlier.
The weirdness has been given the name of no failsafe lockout or NFL for short. A failure of communication between the transmitter OS and the transmitter RF module is one of the unproven hypotheses. Mind you, all previously reported NFL either resolved on their own after some time, or were resolved by power cycling the transmitter and/or receiver. In that regard, your issue is different. It may or may not be related.
Here's how to do a factory reset in OpenTx:
- Switch on your transmitter.
- Long press the MENU button.
- Keep pressing the PAGE button until you get to the HARDWARE page.
- Scroll down to the very bottom where you should find a [Factory reset] option.
- Select that option and then confirm you want to continue.
Hello Guys,
I use a Tandem X18 transmitter as my main radio. I updated it to Ethos 1.6.3, and the RF module to v3.0.3. On the other hand I have a R8 PRO ARCHER rx that i need to bind to my tandem radio. I updated the firmware on the R8 Pro rx to version 2.1.14 which i downloaded from Frsky website. I did the update on the Rx using the smartport.
My problem is that i could not bind the R8 Pro rx to my tandem transmitter, no matter what i do and how i do it the R8 Pro would not neither register nor bind to the tandem radio. I even try to bind the R( Pro to my Twin X14 radio, and the same thing happens. When I try to register, the transmitter recognizes the Rx, it shows a message that the R8 rx is there, but when I press the REGISTER button, nothing happens, I do not get the message "REGISTRATION OK" that I am supposed to get after going through the process. Same thing happens with both radios so i am pretty sure there is a firmware problem between the ethos transmitters (Tandem and Twin) with the RX. I even try the R8 Pro with another X9 Lite S transmitter, and it binds without a problem with this older radio. I do not know what else to do. Please help with any ideas on what could be the problem.
What version of the firmwares I should put on the Rx and on the radios? What version of Ethos and what version of the RF Module?
What should be the voltage that I should use to power the R8 Pro? I was using a 4 cell NimH battery since the Rx should work with a voltage between 3.5-10v.
I use a Tandem X18 transmitter as my main radio. I updated it to Ethos 1.6.3, and the RF module to v3.0.3. On the other hand I have a R8 PRO ARCHER rx that i need to bind to my tandem radio. I updated the firmware on the R8 Pro rx to version 2.1.14 which i downloaded from Frsky website. I did the update on the Rx using the smartport.
My problem is that i could not bind the R8 Pro rx to my tandem transmitter, no matter what i do and how i do it the R8 Pro would not neither register nor bind to the tandem radio. I even try to bind the R( Pro to my Twin X14 radio, and the same thing happens. When I try to register, the transmitter recognizes the Rx, it shows a message that the R8 rx is there, but when I press the REGISTER button, nothing happens, I do not get the message "REGISTRATION OK" that I am supposed to get after going through the process. Same thing happens with both radios so i am pretty sure there is a firmware problem between the ethos transmitters (Tandem and Twin) with the RX. I even try the R8 Pro with another X9 Lite S transmitter, and it binds without a problem with this older radio. I do not know what else to do. Please help with any ideas on what could be the problem.
What version of the firmwares I should put on the Rx and on the radios? What version of Ethos and what version of the RF Module?
What should be the voltage that I should use to power the R8 Pro? I was using a 4 cell NimH battery since the Rx should work with a voltage between 3.5-10v.
4 cell NimH battery is fine. I normally pick my battery to match the servos I am using. The higher voltage servos will want a little more than a 4 cell NimH.
Frsky rf 3.0.3 is for newer transmitters and receivers that use the ACCESS protocol, which requires compatible firmware on both the transmitter and receiver for communication.
Here is a quote from frSky's site about the new RF when it came out:
We were having fun with a customer's radio yesterday when trying to read the telemetry data from the Frsky servos on a Tandem receiver. It was being a royal pain. Like you he had taken his gear up to current firmwares. After a lot of testing and playing around, some firmware reinstalls were needed to get the functionality up and running correctly. In the end I think his receiver needed to be reinstalled a couple of times and rebound a couple of times. Makes little sense. FrSky could really refine things a bit more!
In your case it simply looks like there is no V3 RF firmware for the receiver, so best to take the transmitter back down 2.2.7 RF firmware.
Here is what RF 3 offers:
– Combined VFR telemetry data. (for TD & TW series)
– Optimized the frequency hopping map and CRC algorithm (for TD protocol).
Why this RF broke compatibility with the ACCESS stuff is beyond my pay grade, seems they only added TD and TW features.
I'm sure I am missing something. Maybe @Jarron can shed some more light on this subject?
Frsky rf 3.0.3 is for newer transmitters and receivers that use the ACCESS protocol, which requires compatible firmware on both the transmitter and receiver for communication.
Here is a quote from frSky's site about the new RF when it came out:
Yet, I see no newer firmware for many receivers.
We were having fun with a customer's radio yesterday when trying to read the telemetry data from the Frsky servos on a Tandem receiver. It was being a royal pain. Like you he had taken his gear up to current firmwares. After a lot of testing and playing around, some firmware reinstalls were needed to get the functionality up and running correctly. In the end I think his receiver needed to be reinstalled a couple of times and rebound a couple of times. Makes little sense. FrSky could really refine things a bit more!
In your case it simply looks like there is no V3 RF firmware for the receiver, so best to take the transmitter back down 2.2.7 RF firmware.
Here is what RF 3 offers:
– Combined VFR telemetry data. (for TD & TW series)
– Optimized the frequency hopping map and CRC algorithm (for TD protocol).
Why this RF broke compatibility with the ACCESS stuff is beyond my pay grade, seems they only added TD and TW features.
I'm sure I am missing something. Maybe @Jarron can shed some more light on this subject?
That would not make any sense because with my non Ethos radios there seems to be no problem.
I have a Taranis x9d-2019, x9liteS,QX7 and this radios are able to register and bind all my Archer (V2...) and Archer plus receivers (including SR8 Archer plus and Sr6mini with V3.0.3).
So I think there shouldn't be any major differences on the Access side of the receiver-firmware.
I agree, but confirmed that V2 receivers cannot talk to a V3 transmitter last night. I'm asking FrSky for a solution, we shall see what they say.
That is intersting that V3 receivers can talk with V2 gear. That is a major plus over what they did when V2 came out. i'll also add that Archer Plus can talk ACCST also, so that solved a backwards compatibility already, but this feature is not in the older Archer versions.
That is intersting that V3 receivers can talk with V2 gear. That is a major plus over what they did when V2 came out. i'll also add that Archer Plus can talk ACCST also, so that solved a backwards compatibility already, but this feature is not in the older Archer versions.
