Deviation v5.0.0 build with latest protocols

What happened to the D8 protocol of this build. Are there any changes regarding the rssi calculation?
Well, only read about changes on X_protocol.
There is now significant difference to my DFT/FLD-02 of about plus 11 at my typical test distance & environment.
This is no good, because all my crashes happend with my Devo.

Edit:
My last used build was dated 02 Dec 2016 and there I had identical readings

I beg your pardon, was thinking you would know more about that than a normal user who is not up to date with every change
hexfet does.on the nightlys. I do not use the nightly builds anymore. And the bug tracker does not tell anything about it.
Ok. will revert to the older one.

Edit: Yes ask this before on 02 Dec 2016, because it was the first time the readings were equal.

The last time the interpretation of RSSI was changed in the D8 protocol was 2015 Jun 22 (see below). The code is the same in 5.0.0 and the nightly build.

The change to D8 on Dec 2 corrected the sequence number transmitted to acknowledge receipt of telemetry packets. That shouldn't affect the RSSI seen at the receiver. Possibly Frsky lowers the RSSI reported in telemetry if it's getting sequence errors, but that seems unlikely.

Ok. thanks for the reply.
In a few weeks,hopefully, I have a new radio, a Taranis Q X7, to compare even the D16 protocol.
Then I have the chance to test the Devo against two Frsky devices. Meanwhile I stay tuned.

has anyone had any luck binding a Furious Mini RX for FRSKY to their Devo running vlad's build? I updated my controller about a month ago or so... and was trying last night to bind but it wasn't binding.

I tried this just now, using increments of 10 from -40 to + 40, and had no luck.

I have a Frksy .. X4RSB - binding is ok telemetry is working with DEVO 10 and F12E

Furious Mini use protokoll "D" - it is in deviation frsky V8

Artus wrote: I have a Frksy .. X4RSB - binding is ok telemetry is working with DEVO 10 and F12E

Furious Mini use protokoll "D" - it is in deviation frsky V8

Thanks Artus. it was your comment that led to the answer... I finally got it to bind. it took several attempts for some reason but in the end it did bind. I had to use the "FRSKY" protocol option, not the FRSKY V8 or FRSKY X. Only the plain FRSKY setting will bind. I tested this on 2 RX / Piko combinations.

Yeah . A wrong answer - but a success hope next time i have a better solution ...

There isn't a Devo 12e in the 5.0.0 build... or can we use the parts from Devo 10?

vlad_vy wrote: I can integrate into this build "Devo 12e". Can anybody test it???

(19.01.2017) Firmware DFU file only, you can get filesystem from official Devo10 v5.0.0 release.
...

Loaded this up on my Devo 12E and it looks like everything is running as expected. I have a 4-in-1 in mine, and all the protocols are visible and appear to be usable. I'll load up some models and fly some around the house tonight. First installed the DFU, then copied the Devo 10 v5.0.0 release without a hitch.

I flew a couple of small quads around the house tonight and they worked well. Channel assignments are good and I used some Ini files converted from my Devo 7e just fine. I'm still getting used to all these switches and pots, and they all responded as expected. I couldn't really tell for certain that everything is crisp, but it seems so. I'll get some outside time tomorrow.

Once again, thanks for your dedicated efforts.