I am still using several SR10pro receivers on the latest firmware v2.1.14. I also have some TD receivers that I have not updated to the latest firmware v3.0.1 frequency, stabilization changes, Lua script changes etc. It seems like a considerable update and I would like to update. However, in the firmware "notes" they specify updating rx, tx, and ethos 1.6.0 or later so I'm a bit apprehensive. I'm wondering if I will still be able to use my SR10pro receivers after this update? Or anything else I should be aware of would be appreciated thx.
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!
Firmware update question
- Thread starter Amxman
- Start date
You did not indicate which Transmitter you are using. The latest RX firmware is version v3.01. So this also then needs the TX RF firmware to be version v3.01. The radio firmware is seperate and currently at v1.6.1. Think of the TX having two micro computers, one for the radio functionality v1.6.1 and one for the RF communication v3.01. When you use Ethos Suite it's very simple to update the TX.
I have the X20S and various receivers on the latest firmware whithout any issues.
No Dumb questions, we are all learning together.
Use Ethos Suite to update your (TX) radio firmware and if you click on the module tab it will perform the RF module update as well.
Zipper1949 Wally
New User
I have a new X20RS that was fairly easy to update through Ethos 1.6.2. Bootloader 1.5.9, RF ISRM 3.02, all green and updated. I have seen and read just about everything regarding OTA and cable updates using 3 pins in the module. I updated by OTA two TD SR10's and 1 stubborn TD SR10 by cable to 3.01.
Problem
I don't recall EXACTLY what I did while trying to update AND configure 2 Archer plus SR8's but they were also updated to 3.01 software. Now when I power them up, I only get a blue LED and failure to bind, and 0 RF output. (i.e. no bind)
I think I was trying to write down and take notes regarding all the registering, binding and configuration steps. I was trying to learn any nuance between Owner Registration ID, receiver name, RX1, RX2, RX3 and other RF Configuration settings. I recall taking notes as I went through a Register, bind, clear, reset, Owner Registration ID changes (of the radio) even power 15-25mw changes and at the end, the Archer's LED stays blue and won't bind. I tried a second Archer receiver following more consistent web suggestions after an update and it too won't re-bind. They act like they are registered but they won't pass the "waiting for receiver" call.
I even tried to factory reset of the radio. I tried creating new models. The TD's work ok, but no joy with the Archer's. I do recall that in the process that one Archer was once indicated on the tab where RX1 is listed in the RF configuration. I'm sure I have the RF ACCESS protocol and other selections set correctly. But I did try the ACCST protocol just to see if it wakes up.
Regarding Factory Reset
Now, I'm thinking I'd like to factory reset the Archer receiver or at least return it to the older software in hopes that the X20RS will recognize it as a new receiver and allow a new Registration and bind. But since it won't bind, I can't OTA change it. I want to cable update it, but I want to connect the correct pins on the receiver to the pins in the RF Bay. I know the RF bay is Signal- Ground- Positive from bottom to up. The Archer has - , AIN2 , + and FBUS/Smart Port pins clearly marked. I don't know what the AIN2 pin is, but I believe the signal from the RF bay signal pin should connect to the Smart Port pin (Far right.) Correct?
And also, do you think the Archer receiver(s) will reset enough to re-register and re-bind? I searched the web for hours and the blue LED problem has come up before. I thought by now it may have been addressed. I even found somewhat related OPEN issues on Github.
Any advice or helpful comments would be appreciated. Is there a solution to the Blue LED light / no bind problem? Otherwise, my two stabilizing Archer's are bricked and unusable.
Edited comments after I posted. I used the top of the radio, JR type servo connector to the receiver and did a 3.01 repeat flash update. No bind, still blue LED.
I reflashed old 1.0.10 software into the receiver by cable, flash external device. Then I reflashed 3.01 software by OTA option. It still wouldn't bind. I reflashed again to old software and went to RF Configuration to check. I conected to receiver and it had green LED. I had RF. I was able to now Register OK. Bind OK with old software. Next I tried File manager OTA update to 3.01. Lost RF, no bind. I flashed receiver again by cable to 3.01. Even though receiver not connected, I had SR + 1 as the name instead of RX1. The update to 3.01 turned off the RF allowing no bind. Only Blue LED.
Bottom line is that 3.01 software in Archer Plus S8R won't bind. Only the old software binds. Don't know if it will configure, It might just be in ACCST mode,
Problem
I don't recall EXACTLY what I did while trying to update AND configure 2 Archer plus SR8's but they were also updated to 3.01 software. Now when I power them up, I only get a blue LED and failure to bind, and 0 RF output. (i.e. no bind)
I think I was trying to write down and take notes regarding all the registering, binding and configuration steps. I was trying to learn any nuance between Owner Registration ID, receiver name, RX1, RX2, RX3 and other RF Configuration settings. I recall taking notes as I went through a Register, bind, clear, reset, Owner Registration ID changes (of the radio) even power 15-25mw changes and at the end, the Archer's LED stays blue and won't bind. I tried a second Archer receiver following more consistent web suggestions after an update and it too won't re-bind. They act like they are registered but they won't pass the "waiting for receiver" call.
I even tried to factory reset of the radio. I tried creating new models. The TD's work ok, but no joy with the Archer's. I do recall that in the process that one Archer was once indicated on the tab where RX1 is listed in the RF configuration. I'm sure I have the RF ACCESS protocol and other selections set correctly. But I did try the ACCST protocol just to see if it wakes up.
Regarding Factory Reset
Now, I'm thinking I'd like to factory reset the Archer receiver or at least return it to the older software in hopes that the X20RS will recognize it as a new receiver and allow a new Registration and bind. But since it won't bind, I can't OTA change it. I want to cable update it, but I want to connect the correct pins on the receiver to the pins in the RF Bay. I know the RF bay is Signal- Ground- Positive from bottom to up. The Archer has - , AIN2 , + and FBUS/Smart Port pins clearly marked. I don't know what the AIN2 pin is, but I believe the signal from the RF bay signal pin should connect to the Smart Port pin (Far right.) Correct?
And also, do you think the Archer receiver(s) will reset enough to re-register and re-bind? I searched the web for hours and the blue LED problem has come up before. I thought by now it may have been addressed. I even found somewhat related OPEN issues on Github.
Any advice or helpful comments would be appreciated. Is there a solution to the Blue LED light / no bind problem? Otherwise, my two stabilizing Archer's are bricked and unusable.
Edited comments after I posted. I used the top of the radio, JR type servo connector to the receiver and did a 3.01 repeat flash update. No bind, still blue LED.
I reflashed old 1.0.10 software into the receiver by cable, flash external device. Then I reflashed 3.01 software by OTA option. It still wouldn't bind. I reflashed again to old software and went to RF Configuration to check. I conected to receiver and it had green LED. I had RF. I was able to now Register OK. Bind OK with old software. Next I tried File manager OTA update to 3.01. Lost RF, no bind. I flashed receiver again by cable to 3.01. Even though receiver not connected, I had SR + 1 as the name instead of RX1. The update to 3.01 turned off the RF allowing no bind. Only Blue LED.
Bottom line is that 3.01 software in Archer Plus S8R won't bind. Only the old software binds. Don't know if it will configure, It might just be in ACCST mode,
Last edited:
The SR6, SR8 has 4 different LED indicator colors. Green, Red, Yellow and Blue. Blue means its in self check mode. The current firmware for SR8 is v2.1.14. If you have used a version v3.01 you have used the SR8 plus version which is not suitable for the SR8..
Last edited:
Zipper1949 Wally
New User
Thank you for the responses.
This is the receiver(s) I am working with. https://www.frsky-rc.com/product/archer-plus-sr8/
This is the recommended version on the download. https://www.frsky-rc.com/archer-plus-sr8/
It shows 3.01 as current. Wayne can check my order of May 13, 2024. He was out of stock and I bought 2 more. One is in plane and flying on X9D+ radio. Iv'e been working with the two remaining. Both repeat the blue LED state. I picked up a barely used X20RS (a deal) from person who caved into Spektrum radio systems because of easier use and no update issues. I connect as expected to TDSR10's and they work. I updated by RF bay but found out I could update from top of radio. I broke off the tab on top to make sure I was pressing the internal button during Registration. See pic. (a little blurry. but connected correctly. I am an old earlier user of S8R's on the X9D and X9D+)
No Readme.txt but what does Step 5 really mean? I can't get to receiver factory reset of Rx because it won't connect over the air. 0 RF, blue LED. I can only bind with 1.0.10 or 1.0.11 preceding software. Then I get the other colors during reg/bind which end up green. Servos move. Should I connect by cable for the 3.01 update and remain connected? i.e. no OTA update from 1.0.x software to 3.01? I have gone back and forth several times. Can't proceed to Configure Stab if no bind. No RF.
Step5. Factory Reset operation should be done after updating the Rx firmware, and then Rebound and Reconfiguration (especially the Stab functions including the 6-axis calibration) of all the functions are required. (due to adding the new feature of Fasilsafe data saving on the Rx end.).
Attachments
I cant see anything usefull on the attached image.
Zipper1949 Wally
New User
The image just shows that it is an Archer Plus SR8 with a blue LED. More importantly, do you have an interpretation of what step 5 is all about? I think it's time for a Github issue to be written. If no one has any suggestions, thanks for trying. My knowledge is limited about this radio but I am resolving that daily. I'm currently under the opinion that the receiver is not compatible with the latest version of all the other updates.
OK. So from the manual step 5 do you mean the Registration and automatic binding menu?
So a bit of background info. Previous to "ACCESS" protocols, any receiver could only bind to it's mating transmitter. The process of binding sends the transmitter RF modual serial number to the receiver. So this is how a TX and RX can communicate even when there are multiple transmitters and receivers at your flying field. Each receiver only responds to commands to the TX it bound too. So one of the FRsky goals was for a receiver to be able to store multiple transmitter Serial Numbers. This could be useful if you are an FPV pilot and just before a race you drop your TX resulting in you having to switching to a backup TX. Also in the bind part of the menu you see room for 3 reciever locations to bind too.
So the process is as follows.
1. On the receiver press and hold the bind button and apply power, you should get two solid leds. Release the Bind button. On your TX select a reciever number (Each air craft should have a new number) also select ACCESS protocols. then click Register, if succesfull the TX will indicated the receiver type then click OK and the TX will indicate registration successful.
2. If all three bind positions are free you can proceed to the binding function.
3. On the TX click bind position one, then from the popup menu select bind. The TX will indicate waiting for the RX. Power up the required reciever, don't press the bind button, just power it up, if compatable the TX will find the receiver, follow the prompt OK and then TX will indicate binding succesfull.
I have not found and any issues with the update.
So a bit of background info. Previous to "ACCESS" protocols, any receiver could only bind to it's mating transmitter. The process of binding sends the transmitter RF modual serial number to the receiver. So this is how a TX and RX can communicate even when there are multiple transmitters and receivers at your flying field. Each receiver only responds to commands to the TX it bound too. So one of the FRsky goals was for a receiver to be able to store multiple transmitter Serial Numbers. This could be useful if you are an FPV pilot and just before a race you drop your TX resulting in you having to switching to a backup TX. Also in the bind part of the menu you see room for 3 reciever locations to bind too.
So the process is as follows.
1. On the receiver press and hold the bind button and apply power, you should get two solid leds. Release the Bind button. On your TX select a reciever number (Each air craft should have a new number) also select ACCESS protocols. then click Register, if succesfull the TX will indicated the receiver type then click OK and the TX will indicate registration successful.
2. If all three bind positions are free you can proceed to the binding function.
3. On the TX click bind position one, then from the popup menu select bind. The TX will indicate waiting for the RX. Power up the required reciever, don't press the bind button, just power it up, if compatable the TX will find the receiver, follow the prompt OK and then TX will indicate binding succesfull.
I have not found and any issues with the update.
Last edited:
Zipper1949 Wally
New User
Again thank you for helping. To your first question, I hoped that I indicated above what "Step 5" is and where it is found. It is the written words found in the FrSky receiver firmware update on the download page for this receiver. If you go to the latest, 3.01, there is highlighted in red font, under IMPORTANT Updating steps: 1-5. I trust you pulled up the FrSky download page to verify. When first read by me, it explains a critical Factory reset requirement after you update the receiver. I just wanted some knowledgeable clarification that this was pertaining to factory reset of the receiver and not also the Radio.
What I'm claiming is that I took an Archer Plus SR8, at version 1.0.10 and registered and bound it to my newly completely updated X20RS radio. An Ail Channel Servo connected moved, as expected. I then proceeded to update OTA using system File Manager. The 3.01 receiver firmware was downloaded and placed into Firmware folder under "receivers" in my radio. The OTA was "successful." However as I tried to perform some kind of "Clear" or "Factory Reset" operation, the LED of the receiver remained consistently Blue, "0 RF" yet ithe RX1 position Tab, still had a custom assigned receiver name "SR8Plus"
I tried to Register/ Bind the updated receiver holding receiver bind tab down all different ways, power on or off to register or simply just bind. mostly just bind, assuming receiver is already registered. Nothing worked. I broke off the tab puposely so that I could assure myself that I was depressing the internal bind button properly with a "click." No joy. It simply wouldn't bind.
FYI, FrSky Steve posted a video using a Tandem TD10R receiver fresh out of stock. After a reg/bind and update to his example receiver, he got a Green LED. (At this point I get the Blue LED with the SR8.) He proceeded to "Clear" as he had RF connection to this receiver. His purpose was to teach how to enable Telemetry by an Update, and reset process. His endpoint was to finish the process and put the example receiver back into inventory.
As an FYI, I contacted him, basically saying that the Archer with present software updates, will not connect again after the 3.0.1 update. I elluded to opening up an issue on GitHub.
Henny, I'm sorry if can't make this issue clear enough in my writte communication, but I feel I am clearly stating what I am doing and I fear a real bug here, but I reached out to this forum as a "go to" resource to solve any problems I encounter in my learning process. I really do appreciate your help.
I also feared that there was some inadvertent "User" issues that caused all this. i.e. Changing the name of the radio's Owner Registration ID, receive name, receiver location, RX1, RX2, or RX3, some hidden receiver ACCST binding only that I am ignorant about. Lastly, I factory reset the radio, I can go back and forth from 3.01 to 1.0.10, I created new models, and I only end up with a Blue LED, non-binding receiver. (until I go back to 1.1.x older software.) I don't know what else to try.
And BTW, your process for ACCESS receivers written above 1-3 is spot on. IF YOU HAVE RF CONNECTION. My Tandem SR10's update and bind as expected. The ACCESS receiver ArcherPlusSR8, at least 2 of mine, won't.
Henny wrote: So the process is as follows.
1. On the receiver press and hold the bind button and apply power, you should get two solid leds. Release the Bind button. On your TX select a reciever number (Each air craft should have a new number) also select ACCESS protocols. then click Register, if succesfull the TX will indicated the receiver type then click OK and the TX will indicate registration successful.
2. If all three bind positions are free you can proceed to the binding function.
3. On the TX click bind position one, then from the popup menu select bind. The TX will indicate waiting for the RX. Power up the required reciever, don't press the bind button, just power it up, if compatable the TX will find the receiver, follow the prompt OK and then TX will indicate binding succesfull.
I'm going to paraphrase copy and paste all of this on GitHub and Open an Issue, and hopefully get a good answer to all this. Thanks again.
Kindly, Wally
Last edited:
Zipper1949 Wally
New User
Zipper1949 Wally
New User
Well Wayne, I hope you've seen or can look at my GitHub open issue #5309. Another user posted this.
https://github.com/FrSkyRC/RF_Feedback_Group/issues/95
Apparently, the Blue LED issue is known by FrSky, sometimes permanently bricking Archer receivers. In my case, I can at least revert to 1.0.11 receiver firmware. Others can't. All due to OTA updates as the primary cause.
I will yet have to see if they will still work (bind and configure) on my 9XD+ radio.
I will, one last time, try a cycle of old firmware to 3.0.1 firmware using a cable to update to see if this receiver will work on the X20RS. I won't be able to calibrate and configure it without older lua scirpts working in the X20RS. The bootloader corruption they comment about is a little more difficult for me. I have 1.5.9 and I'll research and try installing a newer bootloader version. Honestly, I don't understand what "corruption" is really happening, but I understand that only FrSky techs could fix them if the receivers are permanently "bricked" and can't even be reversed to older software using a cable.
At least now you know what the Blue LED issue is all about. I'm hopeful that FrSky will eventually fix this somehow, when it becomes a priority for them to do so.
Thanks to Henny and you for your attempts to help.
Kindly, Wally
OK - Glad you got a plan of attack. We do have a warning about the OTA receiver updating to V3. FrSky doesn't seem to be doing much to figure out what is going on. It sounds like a lot of folks have bricked receivers. We suggest they send them back to the local FrSky warehouse as it is their software causing the bricking, thus should be their expense, not yours.
Zipper1949 Wally
New User
I have good news here, hope that I was able to recover my receivers. On FB someone recommended that I flash the receiver with the old software 1.0.11 by cable.
I did that and registered and bound it to a test model on the radio and checked Chan 1 for servo movement. Success.
No OTA. I then flashed it again with a new copy of the 3.0.1 software by cable. I did that making sure I was connected to GitHub server through Ethos and downloaded the new copy and after extraction I put the *.frsk file in the Firmware>receivers directory.
I was able to register and bind to the receiver. After this I checked for servo movement. Success. I then powered off and Cleared the bind for the model. I then powered up the receiver, selected RX1 and selected the Factory Reset option. This is recommended on the FrSky Firmware download page, Step 5.
I Registered and bound the receiver again because reset wipes out Reg/Bind info. After again binding, the receiver worked.
Perhaps since my two receivers can go back and forth (by cable) I can recover from the dreaded Blue LED problem. I will now, after Factory Reset process, calibrate and configure in a real model. First to see it works on the bench and perhaps later, if it works while flying. Based on this, I closed GitHub issue. #5309.
I did that and registered and bound it to a test model on the radio and checked Chan 1 for servo movement. Success.
No OTA. I then flashed it again with a new copy of the 3.0.1 software by cable. I did that making sure I was connected to GitHub server through Ethos and downloaded the new copy and after extraction I put the *.frsk file in the Firmware>receivers directory.
I was able to register and bind to the receiver. After this I checked for servo movement. Success. I then powered off and Cleared the bind for the model. I then powered up the receiver, selected RX1 and selected the Factory Reset option. This is recommended on the FrSky Firmware download page, Step 5.
I Registered and bound the receiver again because reset wipes out Reg/Bind info. After again binding, the receiver worked.
Perhaps since my two receivers can go back and forth (by cable) I can recover from the dreaded Blue LED problem. I will now, after Factory Reset process, calibrate and configure in a real model. First to see it works on the bench and perhaps later, if it works while flying. Based on this, I closed GitHub issue. #5309.
