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!
S6R and S8R configuration questions and concerns
- Thread starter Scott Page
- Start date
J_B_Wingnut
New User
Does anybody know if the SxR PC Configuration Tool (v1.8.4 is what I currently have) can be used to set up stability receivers that have been updated to ACCST 2.1? I was about to update all my Frsky equipment to ACCST 2.1, but before doing that, I went to download the latest version of the PC Configuration Tool, and found that Frsky no longer has that available on it's download page. It appears that the PC Configuration Tool has been replaced by the Free Link Configuration Tool. I tried out the Free Link tool, but it flat won't work on my Windows 10 PC. Doing some internet research, that seems to be one of the problems with that tool that hasn't been fixed (and it looks like the current Free Link PC release is over two years old!) I don't want to start updating everything to 2.1 if I can't configure the many SxR receivers in my fleet. I much prefer using my PC instead of the LUA script, and it sounds like the LUA script has it's own problems anyway.
Zipper1949 Wally
New User
By Configuration Tool, do you mean the STK USB to Smart Port Tool? I just used it today after I updated everything to 2.1.x. The Freelink App works but you have to open it as an Administrator. Also you need to update the tool itself (dip switch down) after downloading it's update. Also Download the Tool Driver and make sure you know which COM port your PC assigns. Typically 1 or 3. I updated my TX X9D+ to Companion 2.3.11 Make sure you put the SxR Lua Script on your Sound Card. You use the STK tool to minimally calibrate the SxR receiver, I picked out using the defaults when I wrote to the SxR. Now, all the other stuff is easily accessed right from the radio. The Lua Script is very easy on 2 pages on the radio. No programming. Just menu driven and easy peasy.
Last edited:
J_B_Wingnut
New User
Thanks, Zip, for the quick reply. Yes, I was referring to the STK USB to Smart Port Tool ("PC config tool" is the name of the folder for the SW on the Frsky site). It's good to know that will still work.
I was playing with the Freelink PC tool last night, and figured out what I was doing wrong: When I would run the software (as administrator), I was clicking "YES" to the "Do you want to update the software online" pop-up. The tool would load, but the window would be blocked by a large, never-ending progress bar. I discovered (duh!) that by clicking "NO" at the pop-up, I can run the tool. That's typical me... overthinking things
.
Maybe I was subconsciously trying to make up an excuse for not diving into ACCST 2.1 Update Hell. Guess I've run out of excuses now...
I was playing with the Freelink PC tool last night, and figured out what I was doing wrong: When I would run the software (as administrator), I was clicking "YES" to the "Do you want to update the software online" pop-up. The tool would load, but the window would be blocked by a large, never-ending progress bar. I discovered (duh!) that by clicking "NO" at the pop-up, I can run the tool. That's typical me... overthinking things
.Maybe I was subconsciously trying to make up an excuse for not diving into ACCST 2.1 Update Hell. Guess I've run out of excuses now...
Konrad
Very Strong User
What issues are you having with ACCST v2.1.xx?
ACCST v 2.1 is very stable. You shouldn't have any issues as it is a straight forward FW update. Now you need to make sure you are updating the ISRM or if you have an older FrSky XJT RF module. (THIS IS DIFFERENT FROM THE UPDATES TO OPENTX) Also you will need to update your receivers to ACCST v2.1.xx. This FW will be unique to each RX model you have. This can be a bit of a pain keeping track of what RX FW you have on your SD card. But look at this as being some of the power we get with FrSky. When I updated my Spektrum system I had to replace all my DSM2 RX as there where no FW updates to DSMX for the old DSM2 RX.
ACCST v 2.1 is very stable. You shouldn't have any issues as it is a straight forward FW update. Now you need to make sure you are updating the ISRM or if you have an older FrSky XJT RF module. (THIS IS DIFFERENT FROM THE UPDATES TO OPENTX) Also you will need to update your receivers to ACCST v2.1.xx. This FW will be unique to each RX model you have. This can be a bit of a pain keeping track of what RX FW you have on your SD card. But look at this as being some of the power we get with FrSky. When I updated my Spektrum system I had to replace all my DSM2 RX as there where no FW updates to DSMX for the old DSM2 RX.
Zipper1949 Wally
New User
Yes. I ran into that green bar also. Eventually hit "No" to get it to work like you. FrSky always has some kind of nuance in the software that stops it from working. Need for new driver, check the COM port, open as Administrator, name changes, etc. Having fought the beta versions of the SxR I really find that using the scripted SxR Lua in the Tools menu on the updated radio software works well. It basically is a wireless hookup. I know it's a lot of downloading from FrSky website, but it's worth it. Previously I'd have to access or take out the receiver to make minor attitude adjustments which can all be done on the radio at the field. BTW, the bonus I now see with the Freellink app is you can update a variety of devices, not only the SxR's. I only have a Lipo sensor, but good to know the STK Tool will come in handy if I need it.Thanks, Zip, for the quick reply. Yes, I was referring to the STK USB to Smart Port Tool ("PC config tool" is the name of the folder for the SW on the Frsky site). It's good to know that will still work.
I was playing with the Freelink PC tool last night, and figured out what I was doing wrong: When I would run the software (as administrator), I was clicking "YES" to the "Do you want to update the software online" pop-up. The tool would load, but the window would be blocked by a large, never-ending progress bar. I discovered (duh!) that by clicking "NO" at the pop-up, I can run the tool. That's typical me... overthinking things
Maybe I was subconsciously trying to make up an excuse for not diving into ACCST 2.1 Update Hell. Guess I've run out of excuses now...
I offered FrSky an idea, an improvement to the SxR software. In the same manner that you can adjust the gain with a knob, imagine plane's attitude adjustment. It's just a value if you look at the csv spreadsheet data. Aerodynamic balance (while flying) is different than static balance on the ground. Now, you likely should land, make the adjustment and fly again. I don't know if you can update your Lua values while flying easily being distracted. Just never tried.
J_B_Wingnut
New User
Not having any issue with ACCST v2.1.xx yet... I'm just getting all my ducks in a row before I begin the process, so as to minimize down-time for my fleet. Frsky stuff can be a real pain at times, but I knew what I was getting into when I dove into the Frsky/OTX ecoculture. Although I get frustrated with it at times, it's still the best system on the books, as far as I can tell, for having the flexibility of doing things I want to do.
In the For-What-It's-Worth category, here's the to-do list I made up of SW and FW needed for my transition to the ACCST v2 universe. I've got a lot to do...
• OpenTX Update:
- Current installed version is 2.2.3, released 7 Jan 2019
- Current released version is 2.3.11, released Jan 2021
• X9D+ Transmitter Update: XJT_ACCST_V2.1.0_FCC.frk
• S6R Update: S6R_ACCST_2.1.0_FCC.frk
• S8R Update: S8R_ACCST_2.1.0_FCC.frk
• RX4R Update: RX6R_ACCST_V2.1.1_FCC.frk
• X4R Update: X4R_ACCST_V2.1.0_FCC.frk
• X8R Update: X8R_ACCST_V2.1.0_FCC.frk
While I'm here, I'll ask: Will all of my models translate seamlessly? Also, am I correct in my assumption that I will need to re-bind all my converted receivers, and run the Freelink configuration tool on all my stabilizer receivers?
In the For-What-It's-Worth category, here's the to-do list I made up of SW and FW needed for my transition to the ACCST v2 universe. I've got a lot to do...
• OpenTX Update:
- Current installed version is 2.2.3, released 7 Jan 2019
- Current released version is 2.3.11, released Jan 2021
• X9D+ Transmitter Update: XJT_ACCST_V2.1.0_FCC.frk
• S6R Update: S6R_ACCST_2.1.0_FCC.frk
• S8R Update: S8R_ACCST_2.1.0_FCC.frk
• RX4R Update: RX6R_ACCST_V2.1.1_FCC.frk
• X4R Update: X4R_ACCST_V2.1.0_FCC.frk
• X8R Update: X8R_ACCST_V2.1.0_FCC.frk
While I'm here, I'll ask: Will all of my models translate seamlessly? Also, am I correct in my assumption that I will need to re-bind all my converted receivers, and run the Freelink configuration tool on all my stabilizer receivers?
Zipper1949 Wally
New User
I know the SxR's must be calibrated. I did the re-bind reading a Scott Page suggestion. I have no idea technically if that is necessary. Easy enough to do. If you transfer your SD card Models, as I did, hook up and check them out and I will range check before flying at the field. IMHO.
I would back uo your models using Companion and then reload if something happens.
I see you didn't grab the STK Tool Update and the new Driver for it.
I would back uo your models using Companion and then reload if something happens.
I see you didn't grab the STK Tool Update and the new Driver for it.
Last edited:
Scott Page
Very Strong User
Frankly I don't know if it's absolutely necessary either. In some cases binding again has solved (or seemed to solve) issues. I bind all of mine. A buddy had not re-bound his (only about two weeks in) and he has not had an issue.
By take on it is that it's cheap and easy insurance.
Zipper1949 Wally
New User
It should be unrelated to this upgrade, but I ran into some issues while trying to check my DSM/DSMX2 hack RF module. Somehow I lost my models and had to re-enter my eFlite Spitfire in my X9D. This hack RF module, which is in a DM9 case, won't turn on. I checked RF bay pin voltage and saw battery voltage. So I think the module is toast because there is no light, but I have to open it to see if it has an LED. I also have a real DM9 (old DSM protocol only). It's LED turned on and I bound it using PPM, my only choice. I have to dig into the hack's required voltage and pray it is not 3.7V max or something. I'll have to do more research.
Without a true DSM/DSMX2 module protocol, I can't seem to turn off the self leveling by a Channel 7 assigned switch. These are quirks with the Spektrum AR636A receiver installed in this plane. They have a feature of interacting with the TX to assign a new switch for on/off any time you want by holding the joysticks in a certain position. I'm sure OpenTX wouldn't have installed this kind of code.
Edit after trying some things:
My Hack RF Module did bind with the DSM/DMSX choice on the external module, but not the PPM Protocol as two years ago. Again, I didn't expect the upgrades would affect the hack module. The hack module does not have an LED. so I couldn't tell if it was on.
However, I still can't get a switch to function on Channel 7 to effect the flight mode status OFF/Stabilization/Auto-leveling. This worked before my upgrades. Not sure if there is a correlation, has anything to do with my OpenTx upgrade 2.3.11 on an X9D and perhaps an OpenTx bug.
So far, I rebound all the FrSky stuff and most works well, even the S8R's. I set the S8R's only in Quick Mode regardless, and it actually seems more predictable and solid switching from OFF to Stabilization to Auto-leveling more so than the AR636A. The gain adjustment works well and translates to observable changes in servo response.
Edit 05092021:
I installed S8R into a plane. I didn't notice before, but I don't get the temporary blue led when turning on the RX. I calibrated RX using the Lua script. I checked also servos working correct way. I tried invoking the self check by toggling the 3 -pos swiich on Channel 12 and no blue light. I then tries to press the F/S button on the RX and again, no blue LED. There was no initial servo movement as expected. I moved functions to extremes and moved the throttle as you should. The control services respond to plane's movement as expected. But I have no idea whether the self-check has worked and the blue light is just not turning on. I see it GitHub that there was a Blue LED light bug reported and supposedly fixed March of 2020. Both of my S8R's were updated and both do not show Blue LED as expected.
Correction: 5/10/2021:
The bug was not fixed. The Self Check Routine is still missing. I wrote issues on GitHub in two areas. OpenTX and FrSkyRC/ Firmware-Test
"I searched for "Blue LED" open or closed issues on OpenTx GitHub and found none. I wrote this as new issue #8493 on OpenTx GitHub. We'll see how they respond.
"I am a "normal" FrSky User. I updated old X9D Tx and older X9D+ (pre 2019) using Companion 2.3.11. I read about need to update FrSky receiver software to 2.1.x Software. I updated internal module in Tx to XJT 2.1 off the FrSky website. Also updated all my Rx's to the latest 2.1 .x software and specifically for the S8R Rx using SXR_ACCST_2.1.0_FCC.frk.
The update was flashed successfully using the Tx FIRMWARE directory, with firmware loaded on the SD Card and flashed to external device connected to the Rx Smart port.
I bound the Rx using XJT D16, 1-16 Ch and Telemetry On and then used the scripts copied into the SD Card to calibrate the receiver. Calibration successful. (Thumbs up) Using the S8R setup lua script, I chose orientation and enabled both SxR function and Quick Mode. I left all other values alone.
I installed Rx into a plane. I tried the 3-pos switch on Channel 12 to attempt the Self Check routine. The Blue LED did not come on. I next tried to press the F/S button on the Rx and there was no Blue LED or servo twitch as I expected. I moved the other joystick function as indicated and then the throttle servo. The plane's functions responded correctly to movement as expected. The assigned Channel 10 switch turns the QM off to Stabilize to Auto-level as expected. The software seems to work, just no confirmation or indication of Self Check routine working and no temporary Blue LED when first turning the Rx on
I have two S8R's and both will not turn Blue LED on. I only get the yellow, red and green lights as expected, green to indicate bind ok.
I reference RCDIY Oscar Liang video for correct setup of an S8R as I know it as a "normal" user. http://rcdiy.ca/sxr-setup-s6r-s8r/
I don't know if this Blue Light issue is FrSky Rx 2.1.x or Lua Script or OpenTx software related. It just doesn't seem to work as expected.
Kindly, WTS"
Apparently a known bug since June of 2020 and still open. See link below.
github.com
Also reported here in FrSky Firmware-Test
github.com"
One minor issue regard general 2.1 updates, one of two X8R receivers doesn't have Channel 1 active for some reason. Either the pin is boke inside or software glitch. I mixed Ail on Channel 5 and it works ok. It's only a 4 channel sport plane. I still have to do range checks.
Without a true DSM/DSMX2 module protocol, I can't seem to turn off the self leveling by a Channel 7 assigned switch. These are quirks with the Spektrum AR636A receiver installed in this plane. They have a feature of interacting with the TX to assign a new switch for on/off any time you want by holding the joysticks in a certain position. I'm sure OpenTX wouldn't have installed this kind of code.
Edit after trying some things:
My Hack RF Module did bind with the DSM/DMSX choice on the external module, but not the PPM Protocol as two years ago. Again, I didn't expect the upgrades would affect the hack module. The hack module does not have an LED. so I couldn't tell if it was on.
However, I still can't get a switch to function on Channel 7 to effect the flight mode status OFF/Stabilization/Auto-leveling. This worked before my upgrades. Not sure if there is a correlation, has anything to do with my OpenTx upgrade 2.3.11 on an X9D and perhaps an OpenTx bug.
So far, I rebound all the FrSky stuff and most works well, even the S8R's. I set the S8R's only in Quick Mode regardless, and it actually seems more predictable and solid switching from OFF to Stabilization to Auto-leveling more so than the AR636A. The gain adjustment works well and translates to observable changes in servo response.
Edit 05092021:
I installed S8R into a plane. I didn't notice before, but I don't get the temporary blue led when turning on the RX. I calibrated RX using the Lua script. I checked also servos working correct way. I tried invoking the self check by toggling the 3 -pos swiich on Channel 12 and no blue light. I then tries to press the F/S button on the RX and again, no blue LED. There was no initial servo movement as expected. I moved functions to extremes and moved the throttle as you should. The control services respond to plane's movement as expected. But I have no idea whether the self-check has worked and the blue light is just not turning on. I see it GitHub that there was a Blue LED light bug reported and supposedly fixed March of 2020. Both of my S8R's were updated and both do not show Blue LED as expected.
Correction: 5/10/2021:
The bug was not fixed. The Self Check Routine is still missing. I wrote issues on GitHub in two areas. OpenTX and FrSkyRC/ Firmware-Test
"I searched for "Blue LED" open or closed issues on OpenTx GitHub and found none. I wrote this as new issue #8493 on OpenTx GitHub. We'll see how they respond.
"I am a "normal" FrSky User. I updated old X9D Tx and older X9D+ (pre 2019) using Companion 2.3.11. I read about need to update FrSky receiver software to 2.1.x Software. I updated internal module in Tx to XJT 2.1 off the FrSky website. Also updated all my Rx's to the latest 2.1 .x software and specifically for the S8R Rx using SXR_ACCST_2.1.0_FCC.frk.
The update was flashed successfully using the Tx FIRMWARE directory, with firmware loaded on the SD Card and flashed to external device connected to the Rx Smart port.
I bound the Rx using XJT D16, 1-16 Ch and Telemetry On and then used the scripts copied into the SD Card to calibrate the receiver. Calibration successful. (Thumbs up) Using the S8R setup lua script, I chose orientation and enabled both SxR function and Quick Mode. I left all other values alone.
I installed Rx into a plane. I tried the 3-pos switch on Channel 12 to attempt the Self Check routine. The Blue LED did not come on. I next tried to press the F/S button on the Rx and there was no Blue LED or servo twitch as I expected. I moved the other joystick function as indicated and then the throttle servo. The plane's functions responded correctly to movement as expected. The assigned Channel 10 switch turns the QM off to Stabilize to Auto-level as expected. The software seems to work, just no confirmation or indication of Self Check routine working and no temporary Blue LED when first turning the Rx on
I have two S8R's and both will not turn Blue LED on. I only get the yellow, red and green lights as expected, green to indicate bind ok.
I reference RCDIY Oscar Liang video for correct setup of an S8R as I know it as a "normal" user. http://rcdiy.ca/sxr-setup-s6r-s8r/
I don't know if this Blue Light issue is FrSky Rx 2.1.x or Lua Script or OpenTx software related. It just doesn't seem to work as expected.
Kindly, WTS"
Apparently a known bug since June of 2020 and still open. See link below.
S8R with FW-SxR-v2.1.0_Beta_0529 self-check procedure doesn't start with bind button · Issue #59 · FrSkyRC/Firmware-Test
Can't trigger self-check procedure by pressing and releasing (F/S) Bind Button as explained in the manual with S8R. Tested with S8R with FW-SxR-v2.1.0_Beta_0529 With S6R it's okay and works...
Also reported here in FrSky Firmware-Test
S8R Blue LED not Working · Issue #119 · FrSkyRC/Firmware-Test
I am a "normal" FrSky User. I updated old X9D Tx and older X9D+ (pre 2019) using Companion 2.3.11. I read about need to update FrSky receiver software to 2.1.x Software. I updated interna...
One minor issue regard general 2.1 updates, one of two X8R receivers doesn't have Channel 1 active for some reason. Either the pin is boke inside or software glitch. I mixed Ail on Channel 5 and it works ok. It's only a 4 channel sport plane. I still have to do range checks.
Last edited:
Zipper1949 Wally
New User
I got advice through GitHub. Ensure that Thr is at -100%. Mine was not and locked out.
I ensured that the order of setup was done correctly. Bind, Calibrate Rx using Calibration Lua, Use setup Lua to choose wing type and mounting type (in my case Horizontal Reverse), and ensure SxR function and QM is enabled. My throttle was reversed so Thr forward was -100%. The 3-pos switch activated the Blue LED. You have to move sticks quickly or it will time out and go green and then must repeat.
At least for now, all the issues I had were related to not having at least the switch invoke the self check routine. Ensuring that the Thr is at or below -100% was key. Again, the self check had to be repeated a few times to ensure the joysticks were moved before the witch occurred. If not, I would only get, for example, partial elevator movement.
Within RCDYI website written words, there was a comment made, that "depending on the software version used, the blue LED may not come on when Rx is powered up."
rcdiy.ca
Bottom line, the Rx Blue LED does not come on temporarily when in Quick Mode and powered up as historically expected. The F/S button press will not invoke the self check, only the switch toggle. These little details were changed in the new update. At least I have one plane's complete functionality checked out with S8R 2.1.x
I ensured that the order of setup was done correctly. Bind, Calibrate Rx using Calibration Lua, Use setup Lua to choose wing type and mounting type (in my case Horizontal Reverse), and ensure SxR function and QM is enabled. My throttle was reversed so Thr forward was -100%. The 3-pos switch activated the Blue LED. You have to move sticks quickly or it will time out and go green and then must repeat.
At least for now, all the issues I had were related to not having at least the switch invoke the self check routine. Ensuring that the Thr is at or below -100% was key. Again, the self check had to be repeated a few times to ensure the joysticks were moved before the witch occurred. If not, I would only get, for example, partial elevator movement.
Within RCDYI website written words, there was a comment made, that "depending on the software version used, the blue LED may not come on when Rx is powered up."
SxR – Stabilizer Gyro (S6R, S8R) – RCdiy
rcdiy.ca
Bottom line, the Rx Blue LED does not come on temporarily when in Quick Mode and powered up as historically expected. The F/S button press will not invoke the self check, only the switch toggle. These little details were changed in the new update. At least I have one plane's complete functionality checked out with S8R 2.1.x
stephen66
New User
New to FrSky. How do I turn OFF the stabilization on the SR6? Do I need the STK tool and FreeLink?
I am getting the most bizarre behavior. For one plane...right aileron adds in Down Elevator. One plane #2 left aileron moves in the opposite direction then corrects to proper direction. Yank out the SR6 and put in an R6...all works as designed.
FRos and RX firmware 2.1.6
I am getting the most bizarre behavior. For one plane...right aileron adds in Down Elevator. One plane #2 left aileron moves in the opposite direction then corrects to proper direction. Yank out the SR6 and put in an R6...all works as designed.
FRos and RX firmware 2.1.6
Zipper1949 Wally
New User
stephan66,
Watch this video I posted above from RCDIY. It will help a lot so you can set up your radio. Hopefully you have matching software versions and installed Lua scripts on your SD Card. If you do it right, a 3-pos switch on Channel 10 will turn on/off your auto-leveling. Watch the video.
Watch this video I posted above from RCDIY. It will help a lot so you can set up your radio. Hopefully you have matching software versions and installed Lua scripts on your SD Card. If you do it right, a 3-pos switch on Channel 10 will turn on/off your auto-leveling. Watch the video.
stephen66
New User
Thanks I had watched the video and while helpful, it was talking OpenTX and LUA. i am running FRos.
I saw a post in this thread where someone asked how to turn ON the gyro. Never saw an answer.
Scott Page
Very Strong User
It's my opinion that the LUA script is the easiest way to turn off the stabilization. The catch of LUA script is that the Tx need to be a couple meters from the Rx or the fields won't populate reliably.
EDIT: Just saw you have FrOS. For that I have no idea. Also -- RCDIY videos and site are becoming dated and he'd no longer maintaining his site or the OpenTX University site.
stephen66
New User
Thanks. I feel like I bought a product (FrOS) that no one uses. What's up with that?
I did notice the comments about physical distance between TX and RX and wonder if that contributed to some of my registration/binding issues.
Zipper1949 Wally
New User
Stephan66,
What radio are you using and what version(s) of software is installed on it? On your Rx?
What is your background with computers? and are you comfortable engaging in downloads? Using Zip files? Drivers? etc.?
For guys here to help you, some basics need to be shared to get on the same page. In my perspective I'm a "normal" FrSky user. I understand computers. Scott above, is one of the FrSky experts who taught a lot of people, me included. And then there are "beginners." And that's ok because every journey starts with the same foot. It's just that these are "Computer" radios and when they work correctly, they have amazing features at a fair price. When things don't work right, for a lot of reasons, you can enter "Update Hell" till it all gets straightened out and you get caught up. That's the good, the bad, and the ugly of it.
Just keep in mind, as I've learned and as stated by others who worked with FrSky stuff since 2013, is that FrSky is a hardware maker and they put software inside and sometimes the software is not "ripe." We as users, then suffer through the updates till all is working correctly.
The latest "Update" problem going on for over a year is the ACCST v2.0.x hardware updates for both transmitters and receivers. I don't think the dust has totally settled on it yet. FrSky's released software for sure, doesn't always match its latest software documentation. Also, they broke their own code ACCST v1.0.x either intentionally or by accident and had to do a major fix. ergo, ACCST v2.0.x. version. (Not to be confused with ACCESS)
OpenTx as a source of the Tx operating system (User interface) has well meaning and more disciplined software developers and more responsive to OS bugs than FrySky in my opinion. They are worth a donation every once in awhile because they try to help us poor users faster than FrSky. But they are separate. As a result when you need to update the Tx RF module, that only comes from FrSky. Their is some symbiosis here, but there is a careful dance between the two organizations because they have different objectives.
So, I don't know what you mean by FRos. Because if you mean FrSky Operating System, then take a close look at the FrSky download page, FrSky downloads (for the X9D+) are based on OpenTX 2.2. See https://www.frsky-rc.com/taranis-x9d-plus-2/ Others Tx's are different.
"Including .dfu and .bin file.
Including _EU and _nonEU file.
Based on openTx v2.2.2."
Minor edit: I see that Fros is FrSky's in-house OS and I know nothing about it! You need to find a FRos expert if you don't overwrite to OpenTx My comments are based on what I know.
FrSky also advocates the download of the Lua scripts for the SxR receivers. It is their attempt to "simplify" the SxR experience.
In my case for the S8R, FrSky SxR_R9S.lua and SxR_R9S_Calibrate.lua. along with the images the radio needs for you to use the menu driven script comes from FrSky installed on the SD Card and is "Easy-Peasy."
Look, I battled the beta software war of the SxR receivers because I was teased by Spektrum's BNF and FrSky's competitive answer was the SxR's. Like what Scott says above, it may have it's quirks, but I can assure you, the interface setup shown by RCDIY for just Quick Mode, which emulates Spektrum BNF the best, is your best approach ASSUMMING you are willing to use it AND you really want the SxR receiver to work right. But be prepared for confusing differences.
For example, this little answer I got from someone on GitHub, a place where you can post software issues or "suspect bugs" is a prime example. I got emails from this person on GitHub: https://github.com/FrSkyRC/Firmware-Test/issues/119#issuecomment-837561395. The issue is now closed.
1. "Glad it works now.
Once you have all the details in mind, setting up a SxR or SRx is pretty easy.
Enjoy."
2. "In v2.x.x the F/S button is disable so is the blue light at power up
"
Keep in mind, this doesn't match FrSky's manual nor what I saw or expected and it through me into a tizzy for 2 days! Partially my fault (I'm not expert status like Scott) but they took out the Blue LED from QM Rx power up and the F/S button press for Self Check! Go figure!
So if you want some help, guys here need to know what you know, what you have, and what you are willing to do. And realize that the devil is in the details. After all, this is SOFTWARE. You either love it, or hate it.
I got one S8R Rx completely working and bench tested. I have yet to try it at the flying field. Perhaps by the weekend.
Regards and Good Luck, WTS
What radio are you using and what version(s) of software is installed on it? On your Rx?
What is your background with computers? and are you comfortable engaging in downloads? Using Zip files? Drivers? etc.?
For guys here to help you, some basics need to be shared to get on the same page. In my perspective I'm a "normal" FrSky user. I understand computers. Scott above, is one of the FrSky experts who taught a lot of people, me included. And then there are "beginners." And that's ok because every journey starts with the same foot. It's just that these are "Computer" radios and when they work correctly, they have amazing features at a fair price. When things don't work right, for a lot of reasons, you can enter "Update Hell" till it all gets straightened out and you get caught up. That's the good, the bad, and the ugly of it.
Just keep in mind, as I've learned and as stated by others who worked with FrSky stuff since 2013, is that FrSky is a hardware maker and they put software inside and sometimes the software is not "ripe." We as users, then suffer through the updates till all is working correctly.
The latest "Update" problem going on for over a year is the ACCST v2.0.x hardware updates for both transmitters and receivers. I don't think the dust has totally settled on it yet. FrSky's released software for sure, doesn't always match its latest software documentation. Also, they broke their own code ACCST v1.0.x either intentionally or by accident and had to do a major fix. ergo, ACCST v2.0.x. version. (Not to be confused with ACCESS)
OpenTx as a source of the Tx operating system (User interface) has well meaning and more disciplined software developers and more responsive to OS bugs than FrySky in my opinion. They are worth a donation every once in awhile because they try to help us poor users faster than FrSky. But they are separate. As a result when you need to update the Tx RF module, that only comes from FrSky. Their is some symbiosis here, but there is a careful dance between the two organizations because they have different objectives.
So, I don't know what you mean by FRos. Because if you mean FrSky Operating System, then take a close look at the FrSky download page, FrSky downloads (for the X9D+) are based on OpenTX 2.2. See https://www.frsky-rc.com/taranis-x9d-plus-2/ Others Tx's are different.
"Including .dfu and .bin file.
Including _EU and _nonEU file.
Based on openTx v2.2.2."
Minor edit: I see that Fros is FrSky's in-house OS and I know nothing about it! You need to find a FRos expert if you don't overwrite to OpenTx My comments are based on what I know.
FrSky also advocates the download of the Lua scripts for the SxR receivers. It is their attempt to "simplify" the SxR experience.
In my case for the S8R, FrSky SxR_R9S.lua and SxR_R9S_Calibrate.lua. along with the images the radio needs for you to use the menu driven script comes from FrSky installed on the SD Card and is "Easy-Peasy."
Look, I battled the beta software war of the SxR receivers because I was teased by Spektrum's BNF and FrSky's competitive answer was the SxR's. Like what Scott says above, it may have it's quirks, but I can assure you, the interface setup shown by RCDIY for just Quick Mode, which emulates Spektrum BNF the best, is your best approach ASSUMMING you are willing to use it AND you really want the SxR receiver to work right. But be prepared for confusing differences.
For example, this little answer I got from someone on GitHub, a place where you can post software issues or "suspect bugs" is a prime example. I got emails from this person on GitHub: https://github.com/FrSkyRC/Firmware-Test/issues/119#issuecomment-837561395. The issue is now closed.
1. "Glad it works now.
Once you have all the details in mind, setting up a SxR or SRx is pretty easy.
Enjoy."
2. "In v2.x.x the F/S button is disable so is the blue light at power up
"Keep in mind, this doesn't match FrSky's manual nor what I saw or expected and it through me into a tizzy for 2 days! Partially my fault (I'm not expert status like Scott) but they took out the Blue LED from QM Rx power up and the F/S button press for Self Check! Go figure!
So if you want some help, guys here need to know what you know, what you have, and what you are willing to do. And realize that the devil is in the details. After all, this is SOFTWARE. You either love it, or hate it.
I got one S8R Rx completely working and bench tested. I have yet to try it at the flying field. Perhaps by the weekend.
Regards and Good Luck, WTS
Last edited:
Scott Page
Very Strong User
To be brutally honest -- FrOS was a miserable failure on the part of FrSky from the get go. They flogged that dead horse for a couple years and then gave up on it. Many if not most Horus users changed over to OpenTX -- fortunately this was possible. They then started work on a new OS they call ETHOS. ETHOS is in the oven and not near fully baked - let alone cooled and frosted. That said, ETHOS is already showing more promise than FrOS ever did IMO. Still -- I prefer the initially steep walk up the OpenTX slope to where unlimited raw power is found.
To assure that their efforts at creating an inhouse OS was successful this time FrSky has at best discouraged or at worst thwarted the option of having OpenTX installed on the new X20 series transmitters. All that did for me was cause me to not purchase an X20 as I'd rather have a fully baked, cooled, frosted, and decorated product. I'd buy an X20s in a heartbeat if I could have OpenTX on it.
Zipper1949 Wally
New User
Good comments Scott. As a "normal" user, I couldn't agree more. I jumped all in to OpenTx 2.3.11 on an old X9D and an old X9D+ (pre-2019) So far, other than the self contained issues of my S8R receiver, all bench testing across X8R, RX8R Pro, RX6R, XM+ seems that they all work. I'm solving some unrelated JR RF Module issues for BNF planes, but I'm getting there. If I were Stephen66, I might load Companion 2.2.4 which even they say was the most stable version prior to the 2.3.x updates. I jumped from 2.0.17 to 2.3.11 biting the bullet.
So what's up with FRos? You hit the proverbial nail head. As long as OpenTx supports his radio, I agree OpenTx is the best approach. It gets him into an arena where he could get help and get going. Why don't people use Zoom to help out? Sometimes that might cut through some of the "PC hesitancy." Just saying....
BTW, if someone hasn't thanked you lately for all you (and guys like Konrad) have contributed to "normal users," THANK YOU!
So what's up with FRos? You hit the proverbial nail head. As long as OpenTx supports his radio, I agree OpenTx is the best approach. It gets him into an arena where he could get help and get going. Why don't people use Zoom to help out? Sometimes that might cut through some of the "PC hesitancy." Just saying....
BTW, if someone hasn't thanked you lately for all you (and guys like Konrad) have contributed to "normal users," THANK YOU!
Scott Page
Very Strong User
A few years ago when there was not a plethora of help for OpenTX I did many screen share sessions with people around the world. This was before the bootloader when we were stuck with Zagdig (or whatever it's called) and people forever had issues with drivers. It's effective -- but exhausting.
Similar threads
