openrcforums

Try a nightly if you doubt it... Common that people forget to tag things.

Envoyé de mon 16th en utilisant Tapatalk

There's been a fix for the X10e that will be in 2.3.2 it seems. https://github.com/opentx/opentx/issues/6910

X-Lite Pro does have a trainer jack, combined with the headphone output. If you looked inside one you'd see there isn't the slightest hint of spare room to fit a 2nd jack.
There's also the X9 Lite that's smaller than an X9D.

It works, but only with other PARA radios.

EEPROM stores your settings. If you radio is running there is nothing to do to it.

Old versions of OpenTX did use eepe files before the extension was changed to otx.

Yes you want to update the SD card contents too, but you said you couldn't flash and the SD card is not involved in that, so forget about it until you've flashed succesfully.

SD card is not involved or needed for flashing firmware.

Envoyé de mon 16th en utilisant Tapatalk

No, not without modifying source code and compiling your own firmware.

Lua won't run on this board anyway, the processor it uses doesn't have enough RAM.

Looks like you flashed the firmware for the X9D and not the X9D+. Just flash the right one, file should have "taranisplus" in the name on 2.0.

Nothing's been posted by FrSky so far.

Futaba failsafe is set on the receiver, not the transmitter

Envoyé de mon 16th en utilisant Tapatalk

That's the one exception yes.

Then you probably didn't install 2.3.1 downloaded from companion, or it wasn't flashed correctly.

They will all do everything, some just have additional features that may be more useful/interesting on one type than another.

2.3 works, but you said 2.2.3 in the previous post.

Use OpenTX 2.3 with the radio type properly set to X9D+ 2019.

It's "no" indeed.

He posted on RCGroups that he always had flashing errors even with ST DFU tool, it seems some area of the flash is faulty.

and it is not the fault of a restricted project But it is the fault of the restricted project that I cannot easily rectify the situation becasue of a restriction that brings me nothing. Just like I said recently regarding FrSky's recent mess a protection is a good thing but only if it has no detrim...

Yes.

If you swap them that often, flashing a receiver is no problem at all ha ha ha ;) :mrgreen: Get to the field with one radio, realize model was bound to the other and you can't rebind, how fun. When I DIY something it's to be fully free of doing whatever with it, not to have some stupid restriction....

jhsa wrote: ↑

Fri Oct 25, 2019 11:19 am

and how many times do you bind a receiver if it is installed in a model? Yes, probably never again unless you crash it.

A lot, I often swap between 2 radios depending on what I do.

I say they won't copy because there is a firmware limitation that should make it unattractive as a product. It is limited to 2 binds only and on 3rd bind it stops working. Unless you flash it again. This is not a problem for a DIYer Even as a DIYer I would definitely not want such a limitation. Mak...

All radios with the same screen size use the same pack.

Clone won't have their latest protocol though, as far as I understand.. No, at least not for now, but the necessity/advantages of the new protocol are debatable. Yes there are useful things, but no "must haves". A lot of FrSky customers have already expressed not even wanting to try it until it's s...

Yep. My stance is that protection measures ARE necessary, but rule n°1 is that they must never have any measurable effect on your own users. In the past 6 months all those they have put or tried to put in place affected/restricted their users so much that in the end it actually has the opposite effe...

FrSky have decided last minute that they would add measures to prevent their modules from working with anything else than their own radios. So they have replaced the original modules by some that require authentication, becasue it's better to put users in danger by having their servos and motor do r...

2.2.3 does not run on an X10s Express.