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  
Steve Balaam21/11/2019 15:49:30
avatar
110 forum posts

After many hours a small success today. Managed to revert back to the Original FROS.

Bound it an X8R Receiver and once again no PWM outputs.

Re flashed the Rx with a slightly older Firmware and the system now looks like it's operating normally

Next step is to update to OpenTX 2.3.2 as I had before I'll steer clear of the 2.3.2 update for now as I'm convinced this is the cause of the original problem

Bob Cotsford21/11/2019 17:01:09
avatar
8064 forum posts
444 photos

The Horus Opentx 2.3.2 I used was current as of last night.

Peter Christy21/11/2019 17:44:20
1619 forum posts
Posted by Ron Gray on 21/11/2019 15:42:09:

Access comes up as Access!

Thanks, Ron! What Tx were you using? Just wondering if its the same for all, due to differences in screen resolution, etc...

--

Pete

Ron Gray21/11/2019 18:03:56
1552 forum posts
367 photos

I have a Horus 12s, Taranis Plus and a Taranis 2019, it’s the last one I was referring to as I haven’t yet upgraded the other 2 to 2.3. The Taranis 2019 came with a Beta version of 2.3 so I e been upgrading it every time a new release has been made available.

Steve Balaam22/11/2019 19:04:58
avatar
110 forum posts

After a lot of effort and frustration I think I've managed to recover my Horus X12S back to OpenTX successfully, just have to put my Models, custom sounds and Model Images back on. To cut a long story short I flashed FRSKY OS back to the Transmitter then installed the last known good OpenTX version V2.2.4 again.

I would like to thank everybody who contributed their help and advise it was very much appreciated.

GrumpyGnome23/11/2019 16:36:08
avatar
512 forum posts
145 photos

Hi all

More info re my binding issues..

x9d se plus 2019

open tx 2.3

isrm1.1.3 firmware

rc is rx8rpro, flashed to non EU.

From banggood not only because it was cheaper but largely because it was available immediately. Did not think it would be an issue due to the ability to flash to EU/Non EU.... And I never said i expected T9 to look at it free of charge.....

GG

P.S.

Peter Christy25/11/2019 10:18:26
1619 forum posts

GG: Sorry for the delay, the topic vanished off the front page before I realised you'd posted an update.

If you are using ACCESS, the binding procedure is somewhat different from before, and there is a good guide here: ACCESS binding

If this doesn't work, it maybe because we don't actually know what firmware is in your Tx! We're assuming its non-EU, but we don't know for sure. Be aware that the firmware for the RF board has nothing to do with OpenTx or FrOS. OpenTx is the bit which governs the encoder functions (model memories, stick modes, etc) The RF board firmware controls - er - the RF board (D16, ACCESS, etc).

I would recommend that you flash the Tx RF board AND Rx to a common standard so that you know that everything is the same. Unless you have good reason not to, I would recommend using the EU firmware, as this is well proven and reliable.

Now I have no experience with ACCESS, but the more recent versions of OpenTx can flash the Tx RF module from OpenTx itself, without having to worry about connecting to a PC. The process is dead easy and there is a guide here: Flash RF module

You can also flash receivers from the Taranis, using a special lead connected to the module bay: Rx update

I note that you've already flashed the receiver, so you probably know how to do this anyway, but you can also do it over-the-air with receivers using the ACCESS protocol, but I haven't seen a guide for this yet.

One final warning: Just make doubly sure that you have not only the right firmware for both your Tx and Rx, but that the two MATCH! (EU, non-EU, ACCESS capable, etc)

Hope this helps!

--

Pete

 

 

Edited By Peter Christy on 25/11/2019 10:20:03

Mike Blandford25/11/2019 11:13:20
avatar
544 forum posts
22 photos

On the X9Lite with the ACCESS module, the EU/non-EU mode is set simply by running a script to change the mode, the module doesn't need re-flashing. You may need to enquire about getting a script to run on your Tx.

My understanding of the ACCESS protocol is the Rx (running ACCESS of course) automatically detect the EU/non-EU mode when binding.

Mike

Peter Christy25/11/2019 11:42:12
1619 forum posts

Thanks for that update, Mike! There's not a lot of info out there yet on ACCESS.

I see FrSky are advertising upgrade RF boards for the X10(S), but the pdf manual doesn't reveal much at all - nor is there any sign of them being in stock anywhere yet.

Also, having just bought an RX8R-Pro myself, the sticker on it says EU-LBT (got it from T9). The instructions say default is D16 and that D8 can be used by jumping pins during bind. It bound instantly in D16 mode.

I wonder if GG has a non-ACCESS Rx and is trying to bind it to an ACCESS Tx? He says he's flashed the receiver, but not which firmware he used.

Too many variables to offer an accurate remote diagnosis!

--

Pete

 

Edited By Peter Christy on 25/11/2019 11:42:51

Mike Blandford25/11/2019 12:51:17
avatar
544 forum posts
22 photos

I don't believe the RX8R-PRO has ACCESS firmware available for it, so it will still be ACCST (D16).

GG: Have you selected ACCST and not ACCESS when binding?

Mike

Bob Cotsford25/11/2019 15:46:52
avatar
8064 forum posts
444 photos
Posted by Bob Cotsford on 21/11/2019 11:30:31:

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.

not to put too fine a point on it, this was stated days ago.

Mike, interesting that you have the region switching script, I thought it was for dealers only?

Mike Blandford25/11/2019 16:16:34
avatar
544 forum posts
22 photos

Well I needed the LUA script so I could write the BASIC script version for erskyTx, which I then passed to T9 and Aloft for their use!

I have heard that dealers have sent the LUA script out to some people needing to change.

Mike

GrumpyGnome01/12/2019 08:12:25
avatar
512 forum posts
145 photos

So.................. this morning I tried (for what feels like the hundredth time) to bind my X9D 2019 SE+ to my RX8R.............. it just worked!

I don't think I did anything different to the previous times so I sense further frustration ahead Anyway, now to bung it in my UltraStik 60 and actually enjoy it !

Thanks for the help and comments - I now know my Tx is ROW so will need to make sure I buy ROW Rx's or flash them; until or unless FRSky add firmware to flash my internal module to EU.

GG

Peter Christy01/12/2019 10:31:57
1619 forum posts

Glad you got it sorted!

See Mike's post above about switching to EU. It sounds as if the new RF module has both, and just needs a script running to switch. I know he's talking about an X9Lite, but I can't believe they would be using a different RF module in different Txs. It would push the cost of compliance testing too high!

--

Pete

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! 

Support Our Partners
Slec
CML
Gliders Distribution
electricwingman 2017
Wings & Wheels 2019
Cambridge Gliding Club
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