T8SG telemetry monitor: display inconsistencies

I am running 2 helis with Brain 2 and Spectrum Spm4649t via dsmx/srlx-protocol with telemetry.
The telemetry monitor looks different to the manual and has an overprint of text and number-fields.
The telemetry contains an additional field Misd; the meaning of this field in d-units is not specified.
I assume, that the order of displayed fades-numbers differs from other Devo-transmitters.
I assume that the calculation of the fade-B-number is far too high (in both helis).

Thanks for the answer. Do you know the meaning of the field Misd?

I think the values for Fades A and Fades R have to be swapped. Is that true?
The Rssi-value is 215d or 214d on the telemetry screen with RX an to next to each other although the FBL-system Brain2 is showing the -40 dbm. What does 215d represent?

I confirm that in your mentioned nightly build
1. the telemetry Monitor is standard
2. meaningful negative rssi-values are calculated and displayed in dBm units.
But I am not able to set meaningful negative limits in the telemetry alarm panels, because the appropriate right box is limited to nonnegative dBm integers.

I confirm that it is now (nighty from 2020-03-15) possible to set negative RSSI-range-values.
Thank you.

I'm running Jumper with this image

deviation-t8sg_v2_plus-v5.0.0-e801244

when running FlySKy AFHDS-2 protocol with IA6C receiver (and IA6B also) I found out that e.g. when receiver is disconnected, display on jumper is not refreshed i.e show last values of voltage and RSSI not 0. FlySky I6 transmitter shows OK ie.0 and can make an alarm. I also found out that RSSI shows strange values. When the binding is OK it shows 60d (40-44DB original FlySky transmitter) but when binding is not OK (4DB FlySky) Jumper shows like 90DB. Any idea what it can be ??? Why sometimes binding is not OK ??? Seems that due to this its not possible to get alarm when voltage or RSSI drops.

Krzysztof