openrcforums

Still thinking your CPU is toast and that radio shouldn't be used again without replacing it or the whole mainboard. Next thing you know it might stop working while you're in flight.

Your choice what your stuff and safety is worth to you.

Why do you want DFU in the first place? This is ONLY for flashing with power off, not for model data access nor flashing in the recommended bootloader mode. DO NOT play with DFU or Zadig while in bootloader mode. Uninstall the device while in bootloader mode, making sure to select "remove driver" to...

1. Do a ""Reset telemetry" from the home screen long enter menu
2. The widget isn't made to take a Cels sensor, that returns a table with all cell voltages instead of just the total voltage, so it needs to be modified to sum those.

On FPV models I use a trim as camera centering adjustment. On quads for gain settings. The trim being also available as a switch allows things like playing a custom sound when you trim, being used in logic that triggers everytime you trim... No chance for mutual exclusion. OpenTX is all about flexib...

Yes it is normal and intended that display stays linked to the physical buttons since the trims can be used for anything, not just sticks.

Waynosan wrote: ↑

Thu Mar 21, 2019 3:14 pm

It's possible that I didn't disconnect the battery when I disconnected the ribbon cables (was my second time in it that evening and I was in a hurry to finish).

This is a well known "proven recipe" for blowing the microcontroller.

Way to flash is there as he said. Why do you want a crystal?

It will when you make 2 radio profiles, one for each, and correctly select the one you're going to write to. You absolutely must not transfer files between different radio types manually. Data is different, companion needs to convert it. This needs review afterwards due to different input control ty...

You must not manually mess with the model files at all.

Always use "Read models and settings form radio" to read things from radio into companion, do your changes, then "write models and settings to radio" to transfer that back to the radio.

Please say what you're actually trying to do.
.otx files are what companion uses to store model/setting data. They are not used on the radio.

If that is working you should be getting about 10 sensors from the flight controller when you discover sensors, one of which being the battery voltage. It will NOT be A2.

For A2 to supply a valid value you need to connect a battery voltage sensor to the battery and feed it to the AD2 input of the receiver on the side connector. Did you do that? Alternatively, if your flight controller supports reading battery voltage you may be able to connect the telemetry output of...

No, only risks.

flexr9m option is for when you have the module flashed with flex and nothing else.

I think the DM9 needed some weird PPM settings, like 350 or 400us for the pulse.

For the images update your SD card contents, the folder name has changed and is now IMAGES. Sounds have changed too.

That's unrelated, joystick hasn't been a firmware option for a while.

What firmware version on the radio? Did you make sure to set USB mode to Joystick in the settings?

goos wrote: ↑

Tue Mar 12, 2019 8:07 pm

Maybe the problem is going to be that the plane is off when the clone receiver is connected and tested an the startbox.
After it is learned in we switch on the plane.

That's not a problem, FrSky's system doesn't know or care how many receivers are listening.

AFAIK that is limited to the old Hub protocol, and again it is irrelevant to the case at hand for which a 2-module solution isn't appropriate at all.

You can of course do that on OpenTX as well but it makes no sense at all in this case (it would actually allow cheating, the whole point is for the judges to receive the exact same thing as the aircraft...)

Windows updates reset the drivers, assuming your radio is on <2.2.2 you need to reselect the right one or reinstall it with Zadig.

Yes, no problem. Just bind the ground receiver with the 1-8, no telemetry option.

Ah, confused with another common mistake.

Use L01 as timer switch instead of THt.

Use THs instead of THt. t is a one-time trigger.

Adjust the relative levels of the various things in the radio setup menu.

Nothing to do with the simulator, but the Cells sensor handling in the radio is not meant to handle irrealistic values that the sensor will never send in the first place. Possible that you even go above what the protocol the sensor uses can handle.

The download page on frsky site has a document that explains all of it.
You just flash the bootloader with companion, then put the firmware file on the card at the appropriate location and power on with the encoder wheel pressed.
The Flash files don't go on the SD card but on the internal memory.

Copy the same firmware file to the radio's SD card, then from the radio's SD browser in the radio settings menu go to it, select it and "flash bootloader".

What's the name of the file you flashed?

Are you holding the power button for 2 seconds or so? There was a bug with 2.2.0 where it turned on instantly, but now you need to hold the button for a while to prevent accidental turn on.

I don't know if there is a minimum requred firmware version for the X10 internal module nor for the RX8R Pro for the binding options to work like with the Taranis.

Sold and shipped, have fun