Scott Page
Very Strong User
Try slowing down the speed with which you toggle the switch.
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
No telemetry after flashing S8R fw to 2.1.0?? ACCST
Migrating from older X9d+ to X10s with updated ixjt module to 2.1.0. So I needed to flash my S8r to v2.1.0 also and then bind to X10s. Update went fine with STK, Bound to X10s D16 mode with Ch1-8 telemetry ON.
All controls seem to work as they should, but no longer do I have any telemetry....no rssi, rx bat voltage, etc. Tried deleting and rediscovering telemetry sensors to no avail.
Also the lua SxR scripts do not seem to work.....
Did I do something wrong, or is this a bug?? Same issue on 2 different in-plane rx's.
Thx
Migrating from older X9d+ to X10s with updated ixjt module to 2.1.0. So I needed to flash my S8r to v2.1.0 also and then bind to X10s. Update went fine with STK, Bound to X10s D16 mode with Ch1-8 telemetry ON.
All controls seem to work as they should, but no longer do I have any telemetry....no rssi, rx bat voltage, etc. Tried deleting and rediscovering telemetry sensors to no avail.
Also the lua SxR scripts do not seem to work.....
Did I do something wrong, or is this a bug?? Same issue on 2 different in-plane rx's.
Thx
Scott Page
Very Strong User
I've got S8R and S6R on 2.1.0 with no telemetry issues on my X9D-SE2019. I suggest updating the X9D+ to ACCST 2.1 and checking to see how the receivers do with that Tx.
Thank you Scott. I did sort of the reverse testing.
Have a brand new S8R, With X9d+ running v1 Xjt and Otx 2.2.0 created new model, and bound it right up to the S8r, D16, ch1-8 Telem On. This was stock out of the box FW on the S8r, probably one of the later 1.x version. Good RSSI, rx bat telemetry, "telemetry lost" warning when powered off. So its ok.
Then updated the S8r to v2.1.0 accst freshly downloaded right from the frsky site. Created a new model on X10s (with 2.1.0 xjt) running Otx 2.3.11. It bound right up, good solid green light, but NO telemetry!!
Maybe it the radio? Or version of OTX??
Not sure how to proceed.....
Many thanks for help
Have a brand new S8R, With X9d+ running v1 Xjt and Otx 2.2.0 created new model, and bound it right up to the S8r, D16, ch1-8 Telem On. This was stock out of the box FW on the S8r, probably one of the later 1.x version. Good RSSI, rx bat telemetry, "telemetry lost" warning when powered off. So its ok.
Then updated the S8r to v2.1.0 accst freshly downloaded right from the frsky site. Created a new model on X10s (with 2.1.0 xjt) running Otx 2.3.11. It bound right up, good solid green light, but NO telemetry!!
Maybe it the radio? Or version of OTX??
Not sure how to proceed.....
Many thanks for help
Scott Page
Very Strong User
That is why I suggested updating the older radio. If telemetry works on the older radio then we know it's not firmware in the Rx. If it doesn't then we know something is wonky about the new firmware in the Rx -- or something in your procedures.
X9d+ with updated 2.1 iXJT bound up nicely with the S8R and an X8R, and good rssi and RxBat signal.
So indeed it is something with the X10s itself. All FW has been flashed, reflashed, downgraded, updgraded, etc. All with no probs. I suspect that something internal is awry. Before I started this recent attempt to update to 2.1, some time ago this past winter, I took the X10s apart to replace the RTC battery. It sat for a good long while until this process ensued without activity, only to check the date and time, but I am thinking something got knocked around on the inside and will no longer receive telemetry, although it would bind and control surfaces fine. I looked at the internals again last nite, and did not see anything amiss, but don't know circuit boards!
I sent a note to Aloft about a repair yesterday.....just waiting to get a reply.
So indeed it is something with the X10s itself. All FW has been flashed, reflashed, downgraded, updgraded, etc. All with no probs. I suspect that something internal is awry. Before I started this recent attempt to update to 2.1, some time ago this past winter, I took the X10s apart to replace the RTC battery. It sat for a good long while until this process ensued without activity, only to check the date and time, but I am thinking something got knocked around on the inside and will no longer receive telemetry, although it would bind and control surfaces fine. I looked at the internals again last nite, and did not see anything amiss, but don't know circuit boards!
I sent a note to Aloft about a repair yesterday.....just waiting to get a reply.
iflylilplanes
Strong User
Apparently, I've turned off the stabilisation accidently, (don't know how I did it), so now my S6R is just a X6R. I remember reading somewhere this could be done, I don't remember where.
Anyone know how to turn the stabilisation back on? turn it back into an S6R.
Many Thanks,
Dave
Anyone know how to turn the stabilisation back on? turn it back into an S6R.
Many Thanks,
Dave
I finally found what I was doing wrong with the self test. I was able to successfully do the test on 2 SR8s and on a SR6. I used my X10S Express and the model of an electric jet. Work consistently every time. When I tried it on two of my gas models, no matter what I did, it would not go into self test. Tried it with the electric planes and it went into self test. I set everything up just like the electrics. What I found was I had the throttle channels in the reverse direction on the output screen. I also set the limits to -512 and 512. Once I did that, the self test worked everytime On both gas planes. I also made sure the calibration lua. that I used was the one under scripts and tools for the archer receiver.
j ferguson
User
Here's what worked and then what doesn't
TX X9D OpenTx-X9D firmware 2.21(cca71808) Date 2017-12-17
S6R firmware S6R_FCC_20161129.frk THIs WORKED fine for installing working firmware in new S6R.
Same TX setup, but this time S6R_ACCST_2.1.0_FCC.frk
no joy, receiver will not bind. ??
I tried various number for receiver without effect.
what should I do or which of the various schemes would make sense. I also have the stk which seems to work fine for configuration.
john ferguson
TX X9D OpenTx-X9D firmware 2.21(cca71808) Date 2017-12-17
S6R firmware S6R_FCC_20161129.frk THIs WORKED fine for installing working firmware in new S6R.
Same TX setup, but this time S6R_ACCST_2.1.0_FCC.frk
no joy, receiver will not bind. ??
I tried various number for receiver without effect.
what should I do or which of the various schemes would make sense. I also have the stk which seems to work fine for configuration.
john ferguson
j ferguson
User
wouldn't this be a step backwards from the 2.21 it appears to have now?
j ferguson
User
Is it possible that there are three (3) firmware installations in this system; one in the transmitter, one in the transmitter module and one in the receiver? If so, that would explain my confusion.
Flying Dutchman
Strong User
Yes, and there is also the OpenTX version. The "2.21" you mention is the OpenTX version, not the Tx or Rx. The latest OpenTX version is 2.3.11.
As Kilrah stated, the Tx (internal, and external module if you use one) needs to be the same revision as the Rx, in this case 2.1.0 is recommended.
Flying Dutchman
Strong User
BTW, does anyone know what the 'S' in "ISRM" stands for?
j ferguson
User
Thanks Kilrah and FD. I think I have it. But just to be sure.
If I have a single X9D transmitter and 6 different FRSKY receivers and I update the RF TX firmware in the X9D, will I have to update the firmware in each receiver? Will I lose the setups in the receivers when I do this?
If I am going to lose the setups, would it make sense to write them to OpenTX, and if I do, will I be able to write them back to the receiver after the update? I assume I will have to manually update the radio setups in the receiver in each case.
Is any of the above wrong? Am I missing anything important?
If I have a single X9D transmitter and 6 different FRSKY receivers and I update the RF TX firmware in the X9D, will I have to update the firmware in each receiver? Will I lose the setups in the receivers when I do this?
If I am going to lose the setups, would it make sense to write them to OpenTX, and if I do, will I be able to write them back to the receiver after the update? I assume I will have to manually update the radio setups in the receiver in each case.
Is any of the above wrong? Am I missing anything important?
Last edited:
j ferguson
User
I've figured it all out. OpenTX Companion is a real help with this.
Not sure if it has been mentioned here, but FrSky put the labels onto some S6R recently in the wrong orientation. This will add confusion during the calibration process as the instructions have your position the receiver based on this stickers correct placement. So please keep this in mind if you are having issues with calibration.
Question.
Have Horus TX 10s with FrOS (not opentx). Updated radio to latest firmware (3/24/2020, ver:1.3.07 with iXJT v2.1.0 update). Also updated S8R in current aircraft build to latest firmware. Can not put receiver into "Self Check" by tx or bind button I have worked on that problem for three days now.. Have not had this problem before.
I have also found that all my other aircraft using SXR (older firmware) are no longer bound to the radio. Is it possible to flash the Tx & Rx with a older firmware version and get my other aircraft back on line? Or do I now have to update all the other Rx's and have to reconfigure each one?
Thank you.
Have Horus TX 10s with FrOS (not opentx). Updated radio to latest firmware (3/24/2020, ver:1.3.07 with iXJT v2.1.0 update). Also updated S8R in current aircraft build to latest firmware. Can not put receiver into "Self Check" by tx or bind button I have worked on that problem for three days now.. Have not had this problem before.
I have also found that all my other aircraft using SXR (older firmware) are no longer bound to the radio. Is it possible to flash the Tx & Rx with a older firmware version and get my other aircraft back on line? Or do I now have to update all the other Rx's and have to reconfigure each one?
Thank you.
Similar threads
