openrcforums

Correct.

No, not on the radio itself.

You don't need companion though, any device holding a copy of your SD card contents and that supports external USB storage would work... that would include most android phones with an OTG cable.

Or just have a 2nd SD card with a duplicate of the contents?

This would be because of an SD card problem, either bad contact or card corrupted. Remove/reinsert hopefully clears the bad contact.

Through a D8 RX yes since that doesn't process the data, but an D16 one in D8 mode does!

It's been so long I don't remember everything clearly, but if I'm not mistaken the Hub protocol had only 3 frames defined, and Vertical speed was never part of any of them. The community added a definition and a new frame for it later and since the D system was pretty much transparent feeding it to ...

The simulator was never expanded to new sensors after someone wrote it and then disappeared.

MPM has always been supported.
A battery is needed but the radio will feed and charge off of USB when connected.
Trainer port is standard.

It is for the logfile as well.

Again your 2.0 screenshot is useless for 2.1, things have completely changed.

Telemetry works completely differently in 2.1, the Cels sensor will just log the total voltage, you have to create more sensors yourself to get individual cell values. Similarly if you use 2 sesnors for a 12S battery and want to see the total voltage you have to create a sensor that adds the 2 Cels ...

What exactly is the problem? Both sensors are there so it seems all good.

That warning is there to remind you to install the antenna before continuing if it was removed to put the radio in the case since turning the module on without the antenna attached can damage it.

Anytime you change what sensors are logged you need to delete the existing logfile for that day if there is one.

You must first fork, then make a branch fix on that, then make a PR to the original repo.

The default application ID for an FLVSS is 0x0300.

You must only change physical ID, not application ID, that must stay default.

By Devo I meant running Deviation, not the Walkera Devo series.

The T12 uses an F205.

Maybe post where you got that info from? AFAIK the Devo radios use smaller chips that don't have enough memory for OpenTX, and drive the RF chips directly instead of through a separate proccessor.

Guess you can always charge outside until a more appropriate time...

Sounds like a warranty case.

The eu option in OpenTx does only one thing, hide the D8 setting.
What is sent only depends on module firmware.

You probably don't have EU firmware on the radio's IXJT internal module.

SBUS stream on pin2 is not supported on the color LCD radios, unlike the B/W ones this is not an uart pin. On the RM it would end up on the exposed UARTs, due to the design you'd need an inverter, and it's untested on the Tx16S. Maybe it works "by magic" because it's similar enough to others, but no...

I see it was renamed "Flsky2A". at some point.

DIY multiprotocol is what you have.

This is an AFHDS2 receiver so that's what you should select as protocol, FlySky is the older protocol.

Resistance at end of travel is 0...

There is no RSSI. It shows TRSS * 3, that's what the people from the multiprotocol module project decided was the best that could be done in the context of range test.

+ and - are min/max.
The RSSI shown there is TRSS. It's only the strength of the received telemetry and is thus only useful with receivers will full range telemetry, which yours isn't so it's mostly meaningless.

Open the radio and reseat all the flex cables, in your case that will include the LCD one under the mainboard.

Reorder the channels on the mixer page.

Those features have never been available for color screen radios, on those backing up is keeping a copy of the SD card.