By continuing to use this site, you agree to our use of cookies. Find out more
Forum sponsored by:
Forum sponsored by CML

FrSky Taranis - user chat

All Topics | Latest Posts

Search for:  in Thread Title in  
Chris Bott - Moderator19/11/2019 20:19:23
avatar
Moderator
6675 forum posts
1384 photos
1 articles

Steve there's always a way back, someone here will be able to help.

It sounds very unusual that an OpenTx ungrade should affect the RF side of things.

Just to check:-

The selections in Companion Settings-Radio Profile must be made BEFORE the firmwre for the radio is downloaded. Because then Companion will download all the correct components for your particular radio.

Are you sure you had the correct radio selected and the correct chckboxes checked before you downloaded the radio firmware?

Steve Balaam19/11/2019 20:23:04
avatar
110 forum posts

Hi Chris

Yes done everything you suggested.

I have also noted in system settings on first switch on, Country code = USA and Tx mode is Mode 1 even though EU box is checked in Companion and Mode 2 TAER.

Chris Bott - Moderator19/11/2019 21:56:56
avatar
Moderator
6675 forum posts
1384 photos
1 articles

If no one here comes up with a useful suggestion, then I'd suggest you join here and post your question. The openTx developers are really good about offering support there and you might even have come across a bug that they'd like to know about.

Prob best not to use this for every simple query but for something like this **LINK**

Ron Gray19/11/2019 22:31:19
1554 forum posts
367 photos

Have you flashed the RXs to the latest firmware, I had a similar problem a while back with some of my older X series RXs but flashing them fixed the issue.

Steve Balaam20/11/2019 09:16:04
avatar
110 forum posts

All my X Series RX's are kept to the latest firmware . It also seems that after trying to bind with the updated Tx the Rx swill not go back in to bind mode. Very puzzling at the moment.

Today I'm going to try two things, first remove the CMOS battery for a few minutes from the main board and try again, if that fails revert back to Frsky OS and then back to a known good OpenTx version.

TigerOC20/11/2019 10:08:15
311 forum posts
13 photos

The notes that come with 2.3.2 indicate an upgrade to the new ACCESS protocol. The protocol encrypts transmission from the Tx to the Rx. The Rx's would require flashing with the new firmware to be able to handle the ACCESS protocol.

Ron Gray20/11/2019 10:47:56
1554 forum posts
367 photos

You do not need to use the ACCESS protocol if you don’t want to. I upgraded my TX to 2.3.2 a couple of days ago and can still operate my RXs with no issues.

Steve Balaam20/11/2019 11:06:00
avatar
110 forum posts

I agree with Ron the update notes say 2.3.2 suitable for both Access and non Access Tx's. On the X10s the RF board needs replacing to get Access I'm not aware of any X12S upgrade being available yet. I use mainly X8R, X6R, S6R and S8R Rx's non of which can be updated to Access yet as far as I'm aware.

Bob Cotsford20/11/2019 13:09:58
avatar
8068 forum posts
444 photos

I've got to pop out to the sorting office to pick up a parcel (WM Crazy Panda maybe?) and when I get back I'll try sticking 2.3.2 on my X9D. What options are you using in Companion Steve?

Steve Balaam20/11/2019 15:30:57
avatar
110 forum posts

Latest update.

Took the CMOS battery out of the X12s for several minutes to hopefully clear memory.

Reverted back to OpenTx V2.2.4 on the Tx and re flashed an X8R Rx with latest firmware.

Companion Profile Settings = Horus X12S, No Heli, Lua, EU, Default Stick =2, Channel Order = TAER, RF=XJT(D16)

Transmitter seems to be doing everything it should do

I manged to bind with an X8R I'm getting RSSI and Rx Battery Telemetry but no drive to the servo's, I put a Rx tester on the Rx and found there is SBUS output but absolutely nothing on the PWM outputs. I also bound to an S6R Rx and there are outputs on the PWM pins the S6R doesn't have an SBUS connection.

Next step would be to revert back to the FROS to see if that helps then back to OpenTX I'd welcome members thoughts on that. I'm really just wandering if the 2.3.2 update has somehow been affected the RF board? maybe a reversion to FROS may help in this respect

Bob Cotsford20/11/2019 17:38:14
avatar
8068 forum posts
444 photos

Steve, I've just updated my Horus from 2.2.4 to 2.3.2, first I backed up my tx, then downloaded the v22 SDcard contents and copied them to my tx (tx switched on) and downloaded the .bin file for your options - except that I didn't select EU as I still run D8 receivers in a couple of models. With the tx switched off I selected 'write firmware', it went through the DFutil write process ok so I bound an S6R with a couple of servos. I'm sorry to say it worked for me, including telemetry returns. My tx now shows Opentx v2.3.2 when I look in System.

Can you try downloading the bin file again?  Maybe change a Settings option to force a fresh download?  The other optin is to back up your SDcard, then do a full format on it before reloading the Opentx contents and running the update.

Edited By Bob Cotsford on 20/11/2019 17:42:40

Steve Balaam20/11/2019 20:22:46
avatar
110 forum posts

Hi Bob

I've done everything you have described above checking and double checking each move.

I hooked a Rx Output checker to my X8R and found the Tx is outputting SBUS signals but there is nothing on the PWM pins. I also bound to an S6R and got it to work from the PWM outputs so the plot thickens.

I thought I would try reverting to FROS but this process doesn't work either.

If you have a normal X series Receiver could I ask if you could see if it outputting fro the PWM pins ?

I'm still thinking something happened on the Rf Board

Peter Christy20/11/2019 22:06:44
1619 forum posts
Posted by Steve Balaam on 20/11/2019 20:22:46:

Hi Bob

I've done everything you have described above checking and double checking each move.

I hooked a Rx Output checker to my X8R and found the Tx is outputting SBUS signals but there is nothing on the PWM pins. I also bound to an S6R and got it to work from the PWM outputs so the plot thickens.

I thought I would try reverting to FROS but this process doesn't work either.

If you have a normal X series Receiver could I ask if you could see if it outputting fro the PWM pins ?

I'm still thinking something happened on the Rf Board

I'm sure you mean " that the RX is outputting SBUS signals".

That tells me that the Tx is working perfectly. Its the RX that is not correctly decoding the signals to PWM.

The RX is clearly receiving the signal correctly. If it were not, there would be no output at all. What it is NOT doing is correctly splitting the SBUS signal down to PWM. (For the benefit of any pedants out there, I know this isn't the correct terminology, but lets stick with what Steve understands.)

I would suggest leaving the Tx alone, and concentrating your efforts on the Rx. Are you sure you got the correct files for the Rx? Try downloading them again, paying particular attention to EU Vs international, and making sure that the correct file is flashed to the correct receiver. It may be worth trying an older version of the Rx firmware, again paying attention to Eu Vs international, and the correct receiver file (X8R, X6R, S8R, S6R, etc...)

Best of luck!

PS: I may have older files for the X8R. PM me if you are still stuck and I'll send them on to you.

--

Pete

Bob Cotsford20/11/2019 23:03:30
avatar
8068 forum posts
444 photos
Posted by Steve Balaam on 20/11/2019 20:22:46:

Hi Bob

I've done everything you have described above checking and double checking each move.

I hooked a Rx Output checker to my X8R and found the Tx is outputting SBUS signals but there is nothing on the PWM pins. I also bound to an S6R and got it to work from the PWM outputs so the plot thickens.

I thought I would try reverting to FROS but this process doesn't work either.

If you have a normal X series Receiver could I ask if you could see if it outputting fro the PWM pins ?

I'm still thinking something happened on the Rf Board

X8R, everything working perfectly, sorry sad. If it weren't for your US setting I'd suggest you checked that you've bound selecting ch1-8 with telemetry or without a shorting plug across channel output pins on the rx. I'd still try downloading again on the off-chance you picked up a corrupted compile. If all else fails try posting on RCGroups Opentx2.3 or Horus threads in the Radio section. A lot of developers visit there on a regular basis or soone else may have seen something similar.

One thing I did notice was that my tx's clock and calendar zeroed themselves!

GrumpyGnome21/11/2019 07:49:27
avatar
512 forum posts
145 photos

My X9D+SE 2019 is driving me nuts! I just can't get it to bind.

I think it's an International version as it came from Bangood - how can I tell ?

On the understanding I do have an international Tx, I flashed my Rx, but it still won't bind. What should I check before sending the Tx to T9 to check it's working ..... ?

I'm sure it's going to be worth the rather steep learning curve ...........................

TIA

GG

Trevor Crook21/11/2019 08:16:52
874 forum posts
65 photos

The QX7 I bought from T9 has a sticker stating LBT EU. Not sure that Bangood would put on a sticker. Also not sure that T9 would want to sort out a tranny you didn't buy from them for free!

Peter Christy21/11/2019 08:40:20
1619 forum posts

GG: You haven't done yourself any favours by buying from outside the EU. It may have been cheaper, but you are now paying the price!

It is probable that you have an international version. This *can* be flashed to EU standard, but this means flashing the RF board, NOT the OpenTx operating system. Do not confuse the two! There is no easy way of telling which version of RF firmware you have.

You don't say what kind of receiver you are trying to bind. If you bought it along with the Tx, I would expect it to be compatible. However, the Tx you have bought uses the new ACCESS protocol, along with the older D16 protocol. If you are trying to bind, say and X8R or X6R, it is quite possible that these are using the D16 protocol. Did you select that correctly before trying to bind?

Basically, more information needed!

--

Pete

Bob Cotsford21/11/2019 11:30:31
avatar
8068 forum posts
444 photos

From what I've read (mostly relating to the Horus rather than Taranis) the RF firmware is common to both EU and ROW, but only dealers can switch between the two. As Peter says, more info is needed. An X series receiver with ROW firmware should bind in ACCST mode (D16), D or V series will not bind, though Mike Blandford has written software to run D series receivers in D16 mode.

Peter Christy21/11/2019 15:30:03
1619 forum posts

The new 2019 version supports ACCESS or D16 (ACCST), as I understand it (I don't have one, so just going on reports!).

I don't know if ACCESS is the same for EU and Rest Of the World (ROW), but certainly D16 is different.

Unfortunately GG hasn't told us exactly what type of receiver he is trying to bind to it, so until we know that, we can't really advise. If he bought it at the same time (and from the same supplier) as the Taranis, I would expect it to be compatible. However, if he bought one from Banggood and the other in the UK, I would anticipate issues!

The naming system (ACCESS and ACCST) is also confusing. I usually refer to it as D16, although the older D8 system is also referred to as ACCST! I've no idea what the ACCESS protocol comes up as. Maybe D24? Its supposed to be 24 channels.

--

Pete

Ron Gray21/11/2019 15:42:09
1554 forum posts
367 photos

Access comes up as Access!

All Topics | Latest Posts

Please login to post a reply.

Magazine Locator

Want the latest issue of RCM&E? Use our magazine locator link to find your nearest stockist!

Find RCM&E! 

Latest Forum Posts
Support Our Partners
CML
Cambridge Gliding Club
Slec
Gliders Distribution
Wings & Wheels 2019
electricwingman 2017
Pepe Aircraft
Sarik
Advertise With Us
Do you use a throttle kill switch?
Q: This refers to electric-powered models but do you use a throttle kill switch?

 Yes
 No
 Sometimes
 Rarely

Latest Reviews
Digital Back Issues

RCM&E Digital Back Issues

Contact us

Contact us