I'm doing some tests and I need to have separate telemetry values for the 2 antennas of my crossfire diversity receiver.

The only values available are 1RSS and 2RSS, good, but... they are always exactly the same value... and this doesn't make any sense.

I already tried to re-discover the telemetry sensors but with no difference.

I'm on firmware 6.17

Is there anyone with crossfire diversity receiver who can confirm that 1RSS and 2RSS values are always identical?


Another issue I have (maybe related) is that, even with fixed mode (50Hz), in the telemetry I keep seeing the mode switching between 50 and 150 Hz...

Anyone else having this issue? (this is not just for diversity receiver)

I don't have a Crossfire Diversity RX but there have been a number of issues with the 6.x firmware so I wouldn't be surprised if it's some kind of bug.

Does the receiver you have require firmware version 6.10 or higher to be installed on it (i.e. was there a sticker on it stating that)? If not then try going back to firmware version 4.11 and see if you experience the same behaviour.

(03-May-2022, 07:50 PM)SnowLeopardFPV Wrote: I don't have a Crossfire Diversity RX but there have been a number of issues with the 6.x firmware so I wouldn't be surprised if it's some kind of bug.

Does the receiver you have require firmware version 6.10 or higher to be installed on it (i.e. was there a sticker on it stating that)? If not then try going back to firmware version 4.11 and see if you experience the same behaviour.

I know that 6.x is a   ...but I have 2 other builds with nano RX v3 which require 6.x... this is why I'm stuck here. If no one will confirm my problems then I'll downgrade and try.. but lately I don't trust TBS about firmware flashing (bricked a MicroTX v2 with a simple reset after a flash)... so if I can I'll avoid downgrading.

With all 6.x firmwares I have both problems.

If someone confirms then I'll open a ticket with TBS... So in a couple of years maybe they fix them.

I do not have a Crossfire Diversity RX to confirm anything but I will suggest you raise a ticket with TBS.

Lately they have been struggling with firmware issues and hopefully they get around to sorting those bugs out.

For the 50Hz fixed mode that keep switching between 50Hz and 150Hz I received this answer from TBS:

"50Hz won't allow transmission of internal module data. With the new Betaflight there is a bug as it sends a frame that pretends to be internal module data for the "CRSF V3 keep-alive", so it kind of disables the "fixed 50Hz" mode for the moment. We will have a fix for this in 6.19, which is slated to arrive middle of the month. "

..so, for now I'll keep it in dynamic mode.


I'm still waiting an answer about the identical 1RSS and 2RSS values issue.

And I ask TBS if they can give separate values for RSS and LQ for antenna 1 and 2... and a telemetry value showing which antenna is used at the moment.


I think it would be so useful having those informations while reviewing a long range log. You could check the antennas usage while turning... or just check that both are working and use those extra informations to optimize the antenna positioning.

Let's see what they say.

I asked FalconRad if he noticed the same problem and this is the answer:

"I was actually just looking at that the other day.  They do seem to be identical, I was wondering what the point of it was.  No way they should be the same, especially with a horizontal immortal t and a vertical antenna for the second one."

So the telemetry issue is there... what we still don't know is if the antennas are chosen correctly (diversity) or not.

Another interesting thing is that I looked at old youtube videos about the diversity receiver and in all of them I always see 1RSS and 2RSS identical values... have this ever worked?


The ticket is in standby, TBS requested a long range video with log... so I sent them this:



...but with the blackbox log I didn't have 1RSS and 2RSS separated values.

...so this weekend I setup the logging on my TX16s and I recorded another flight... this is the video (check the RSSI value at top right):

Interesting, hope they can fix it as its useful information for testing antenna placement and different antennas. I do think the antenna switching is working thought as with one antenna i got signal low warning when i turned and the carbon/battery blocked the antenna (1x Horizontal Imortal T on arm). With Diversity i have not had signal low warning when i turn (2x horizontal Imortal T on arms). It was before i started logging in the radio so i only had the audio warning setup if the signal dropped low.

I have never had a Crossfire Diversity RX but I will not be surprised if this went unnoticed or no one ever reported it.

Similar question was asked on the flitetest forum without any response: https://forum.flitetest.com/index.php?th...ssi.68003/

Diversity is not hard to do and I think this is more related to the wrong telemetry data being transmitted back to the TX. Should be easy to fix in firmware.

I just mentioned this on the TBS Live stream just so Trappy is aware and hopefully they can look into the 1RSS and 2RSS identical value issue on the Crossfire Diversity Nano RX.

They will probably look into this at some stage.

I am fairly confident its just a firmware fix but they have some major issues to resolve first.

Oh.. thanks kafie! Let's see what they do.


On the emails with Mike Chin I proposed, if possible, to have every possible separate value for the 2 antennas, like:

-RSSI
-LQ
-SNR

and which antenna is active in every moment. You could setup a voice feedback on the radio that tells you if is using the horizontal or vertical antenna.... and do flight comparisons with tx antennas vertical or horizontal.

From long range flights you'll get so much valuable data from the logs.



The past hour I searched for schematics and datasheet of components, but I haven't found enough.. so I still don't know which data they could possibly get from the two 1272 radio ICs.

I think separate RSSI and SNR should be no problem while LQ could be that is calculated just after the diversity section, from the dropped packets.... so.. just a single value... I hope I'm wrong on that.

Im not sure they will want to add more telemetry sensors to the feed because it takes up additional bandwidth but as long as the have the RSSI for individual antennas/receivers it should be good.

I received an update from Trappy (TBS) about the 1RSS = 2RSS issue:

"It is indeed a bug - it works in fullsize RX but not in the diversity nano RX. We will fix it asap."

and later...

"We already found the reason as well. The bug in the Diversity Nano RX RSSI is due to RSSI sensor functionality being inherited by the Nano RX instead of the Diversity RX. NanoRX simply duplicates the values of the active RF to both RSSI sensors, whereas Diversity RX pipes the values to the respective sensor port. It's on our roadmap to be fixed, no specific ETA as the issue has been deemed non-critical. But we do expect it within the next 4 weeks (4 internal release cycles)."




So, I'm quite happy that my ticket has been considered and that Trappy took the time to answer personally.

Now let's wait... there should be a v6.19 firmware coming the next few days and including the fix for the fixed 50Hz mode that wasn't working and then, in a month, another release with diversity telemetry fixed.

One month ago I was quite disappointed with TBS support, today I changed a bit my mind... let's see.

I think this is a positive outcome and definitely assures the community that the vendor is listening and responsive.

(20-May-2022, 01:24 PM)noize Wrote: I received an update from Trappy (TBS) about the 1RSS = 2RSS issue:

"It is indeed a bug - it works in fullsize RX but not in the diversity nano RX. We will fix it asap."

and later...

"We already found the reason as well. The bug in the Diversity Nano RX RSSI is due to RSSI sensor functionality being inherited by the Nano RX instead of the Diversity RX. NanoRX simply duplicates the values of the active RF to both RSSI sensors, whereas Diversity RX pipes the values to the respective sensor port. It's on our roadmap to be fixed, no specific ETA as the issue has been deemed non-critical. But we do expect it within the next 4 weeks (4 internal release cycles)."




So, I'm quite happy that my ticket has been considered and that Trappy took the time to answer personally.

Now let's wait... there should be a v6.19 firmware coming the next few days and including the fix for the fixed 50Hz mode that wasn't working and then, in a month, another release with diversity telemetry fixed.

One month ago I was quite disappointed with TBS support, today I changed a bit my mind... let's see.

I'm on v6.19 which was released July 21st (https://intofpv.com/t-tbs-crossfire-trac...e-released) and the problem still exists.  I'm using Tracer.  I'm not sure whether the firmware is identical.

@noize have you tried this on the latest firmware?

(27-Sep-2022, 03:04 PM)tonyyng Wrote: I'm on v6.19 which was released July 21st (https://intofpv.com/t-tbs-crossfire-trac...e-released) and the problem still exists.  I'm using Tracer.  I'm not sure whether the firmware is identical.

@noize have you tried this on the latest firmware?

Seems like this still has not been fixed on the diversity?   It's been a lot more than a few weeks.