New FrSkyX protocol

Hello,
Test Ver. 18a

DEVO8s

AD2GAIN at 1000 shows Volt3 / 10 . The Calculation is ok, but the 1/10 Divider does reduce the Voltage around 0.4X Volt to the AD2 Input Pin.
Here we need a bit more Room with the 1000 at AD2GAIN. May be 1500 ?

I think we need a little AD2 Adjust to compensate the Volt loss of the Divider Board to get better on Point of the real Volt.

DEVO7e

Menu is now ok.
yes , i think it is better to remove all things who are not supported by the System to get not confused .

doing a deep Test later

greetings Alex

To get it fully correct, in addition to the divider ratio, might be needed an offset field in +/- 0,01 Volt correction steps. I believe Taranis radio has this option.
However AD2 Volt just as purpose end of flight empty battery indicator, adgain setting only is probably accurate enough.

Test build is updated - 070.
- Removed extended telemetry values from 7e telemetry and main page config pages (except Volt2 - see below)
- Set max AD2GAIN to 2000, corresponding to a multiplier of 20.00
- Restored normal function for Volt3 telemetry value

Decided against further AD2GAIN changes at this time. A fixed offset doesn't seem right because then a zero input would not read 0. There are only 255 ADC steps so error is about 4% anyway. For 3S that's about 0.04 volts.

The 7e telemetry still shows Volt2 available because this code is shared with Frsky (D8) and there the 7e does receive Volt2 telemetry. I didn't want to add a runtime check to several places in the code. The other values are excluded at compile time.

Thanks again for all the testing!

Went flying with 18a earlier today, put 8 packs through 2 quads, XSR and X4R receivers.. no issues. Only using RSSI telemetry, though.

Good to hear. Thanks!

Could you create a Devo 7e-256 test file please?

Hello,
Test Ver. 070

Devo 7e
PWM out 1 to 8 : ok
Volt1 : ok
RSSI : ok

-> looks good , time to Test fly it . Maybe Tomorrow

Devo 8s
PWM out 1 to 8 :ok
Volt1 : ok
Volt2 : ok <- it is the best to calibrate it at the Volt you need ( 3.6 for 1 s, ........ ) The difference is not par. with the Voltage drop ( Batt full to Batt low) , but i think it is ok.
RSSI : ok
Alt : looks good
Dis : looks good
Vspeed: looks good

-> all in all looks good, doing some deep Test (Alt,Dis,Vspeed,SBUS ) tomorrow to cross check with Taranis. Maybe i do a Devo 10 Test to

greetings Alex

Arakon wrote: Could you create a Devo 7e-256 test file please?

Nevermind, just managed to get it compiled myself.
If anyone wants to try it on an "Ultimate" 7e, I attached the file.

Edit:PB removed attachment

@Arakon

Maybe some Days at looking at 7e 256 i cant resist to fire up my hot Air Station
Thanks for the File, i saved it at my Destop

greetings Alex

Hi, quick question about this...

I have a X9E and have X4R's installed in all my models which is why I'm so interested in this now. I have the blue CC2500 module from BG en route via fast shipping and expect it this week. My concern is the "model match" feature of the frsky receivers.
Before when I was flying DSMX and using my pair of devo's (7E and 10) all I had to do was set the fixed ID the same in each tx .ini then bind one tx after the other (but ONLY ONCE). As long as I turned one of the two tx's on first (and only one at a time) I could pick up and fly any model with either tx just having to sellect the proper model file for that model. I didn't have to re-bind each time I wanted to use the other tx since the fixed ID was set the same, just power it up and go flying.

The question-
Will I be able to do something similar going from X9E to devo back and forth or will I have to completely rebind every time (and if so, what does that do to the telemetey aspect, will I have to re-discover every sensor every time)? I'm concerned about this "model match" feature (I use the term feature loosley), is it going to make it hard for me to switch between tx's? Does devo allow the setting of the "receiver number" somewhere like in have to do in taranis?

Not tested it, but according post Tom Peer, you can use multiple devo bind to same rx,

Type in your hardware.ini file: txid = 86668963 (8 digit code), use same id for your radios.
www.deviationtx.com/forum/3-feedback-que...xedid-question#41711

But not sure how to find the id of your Taranis?

I'd be interested in how to find your current one so you can adjust it in case of a CPU change.
Edit: Tried to make it write the ID to the tx.ini in a really dirty way, but both MCU_serialnumber and Transmitter.txid seem to return 0 there. Unfortunately I don't know jack about coding, so I'm guessing this is way beyond my ability.

Does this protocol work for EU and non-EU RX firmware?

And if not, is there a way to flash a X4RSB without a Taranis?

Only non-eu, I believe. You can flash the X4R either using Frsky's official flash tool and smartport adapter, or a normal FTDI and a resistor.

Test build is updated - b02.
- Added support for 7e-256 with extended telemetry enabled (and included in test build)
- Merged latest changes from deviationtx/master

The merge brought in the changes PB talks about here for buttons and display. Noticed a couple menu titles missing on the 10 but haven't yet looked at the code.

I've created a pull request for the protocol_frskyx3 branch.

Hello,
Deep Test with Ver. 070

Devo 10

Telemetry :ok
SBUS : ok


found some little Error on AMP.
0.2 Amp shows 0.6 Amp at the TX , DIS calculate with the 0.6 A and is then to high.


o.t. the Frsky D8 Telemetry does not get any Data from the X - extension, black Background and showing 0.

greetings Alex

delete

Fernandez wrote: Not tested it, but according post Tom Peer, you can use multiple devo bind to same rx,

Type in your hardware.ini file: txid = 86668963 (8 digit code), use same id for your radios.
www.deviationtx.com/forum/3-feedback-que...xedid-question#41711

But not sure how to find the id of your Taranis?

Taranis doesn't have a "fixed ID". For model match, it simply uses what it calls "receiver number" which is just a one or two digit number (that usually corresponds to the model file number but doesn't have to. It automatically chooses the next unused number each time you create a new file). Do you think I should try entering that number into the devo's fixed ID field (for example on my 200 I want to use the devo 10 on it's rx #2, model file 2)

Let's say I can't get it working back and forth, will I have to rediscover all the telemetry sensors each time I bind back and forth? Does devo even require the discovery step? FWIW I don't have a single smart port sensor, I get all my telemetry data from cleanflight and A2 pack voltage.

Cereal_Killer wrote:

Arakon wrote: ...or a normal FTDI and a resistor.

Don't even need a reaistor, just an FTDI and a program from FDTI called FT PROG to invert the output.

Not for the X receivers.. they use s.port, which is a single wire serial protocol. You need the resistor to join RX and TX into a valid signal for that.

Ah yea you got me. I read X series, I typed X4r but because most recently I had flashed a D4r-ii that's the process I had in my head.
-will edit above post to remove incorrect info when I'm at my desk later today

Thx
-C_K


P.s. any idea about fixed ID vs receiver #? Can fixed ID in devo be a single digit number?