Wookman

So every now and again I look on eBay, like you do. There is a cheap Taranis on there. Description was “looks new”. That was it. The pictures bore this out, it looked nice and clean. The picture of it snuggled in the aluminium case showed an external module and aerial. A quick message to the vendor about the module illicits no response at all. I waited until the last few minutes of the auction and stuck a bid on it. With seconds to go I was expecting the usual auto bids to gazump me. They never materialised and I won. So today it turns up. Lovely condition with the rather terse description being entirely accurate. The only thing missing was the dog clip on the neck strap. The module was there, a DJT, complete with aerial. So there I was, chuffed to bits with the package. A further rummage through the case revealed a further pleasant surprise. A X8R receiver that looks brand new. The price? We’ll suffice to say I would not have been unhappy to get the module and receiver for what I paid for the whole lot. And it all seems to work as FrSky intended. Happy bunny. 🐇🐇🐇.

Presumably, this problem is only with the V8 hack module and not the V8 "JR" plug in module?

Lemon rx might be the way to go.

Only the V8R4 II will work with the XJT module.

That what I said.

Good plan.

Accelerate slower so you can keep up withe rudder inputs required?

Easiest thing is to swap out the pcb aerials for whiskers. They are easier to get at ninety degrees to each other in a confined space.

You can bind as many rxs to one tx model memory as you like. Just select the required model memory and bind. No need to delink the other rx. That is why there is nothing in the instructions about doing it! If you really want to break the link just bind it to a spare model memory. You would naturally rebind if you reuse the original rx in another model as part of the set up process anyway.

Sorry Mike, I lost you in there somewhere.

Nice old slope soarer too. Early Phase something, MM Avenger, Myjet?

I am still wondering too especially as the model memories on T2, which does bind, were copied from T1, which would not.

Genius Mike. Thank you. New model memory created and both TXs now bind to the L9Rs. Still wierd though. The model memories on T2 were copied from T1 on Companion.

To sum up. X9D+ No 1 (OTx 2.3.15 and EU V2 2.1.0) will NOT bind with the L9R. X9D+ No 2 (OTx 2.3.15 and EU V2 2.1.0) will bind with the L9R. X9D+ No 3 (Edge 2.10.1 and EU V2 2.1.0) will NOT bind with the L9R. X9D+ SE (OTx 2.3.15 and EU V2 2.1.0) will bind with the L9R. Qx7S (OTx 2.2.2 and EU V1) will bind to the L9R. Note that there are 2 L9Rs and they both behave identically in terms of what they will and will not bind to. So why will the L9Rs bind to some TXs and not others?

All the txs have LR12 as an option on the internal module. X9d+ No 1 and X9D+ No 2 have identical OTx and EU firmware. The L9Rs bind to No 2 but not to No 1!