X7 - Crossfire constantly telemetry warning

[lichtl]

Had an interesting behaviour on a X7 from a friend. Seems that Crossfire telemetry generate constant report telemetry lost/regained.

X7 running RC18 (no-heli, lua, diy module)

The behavior is similar to described in. http://fpvlab.com/forums/showthread.php?42097-TBS-CROSSFIRE-Next-Generation-Long-Range-R-C-System&p=832994&viewfull=1#post832994

Crossfire module run on latest stable but even on the beta behavior is the same. This seems once the receiver connect (crossfire telemetry is enabled). Module works fine in X9D plus. PPM also run error free on X7

[bsongis]

No connection problem? Mine doesn't fit well, I have no contact between the X7 and the module ...

[bsongis]

I just tested with XFire version 1.63 X7 with OpenTX 2.2.0 Everything runs perfectly

Which XFire version are you testing?

[lichtl]

We tried 1.63 and latest stable (think 1.57). Will gonna try to bend the pins a bit more (maybe only TLM pin) do not have proper connect.

[bsongis]

yes I think it's a bad connection

[stevef1966]

Hi im having the same issue, telemetry looping, connection seems fine to the crossfire, everything is on latest recommended firmware

[stevef1966]

dont know if this is the correct way to do this but....

I have re-flashed all firmware (yet again) and checked for loose pins/bad connections to the crossfire TX still get the telemetry lost/recovered issue, have tried to use the PPM protocol in openTX to talk to the crossfire TX and this is the only way to stop the constant telemetry warnings, is this a bug?

[bsongis]

I will provide a test firmware for you so that you will collect traces as a basis for investigation

[stevef1966]

thanks, look forward to testing

[stevef1966]

hi did you get a chance with the firmware?

[bsongis]

Here: http://downloads.open-tx.org/2.2/firmware/tests/firmware-x7-telemetry-logs.bin

[bsongis]

You will have a new file telemetry.log on your SD. This will be interesting

[stevef1966]

Awesome do I just upload the file back here?

[stevef1966]

telemetry.log.txt

[stevef1966]

put the firmware on the qx7, turned on and changed from PPM on the radio to CRSF, the looping starts at that point, moved sticks and switchs to confirm connection with receiver via betaflight.

[bsongis]

perfect, I will investigate when I have one minute, I prepared a script for this

[bsongis]

we really miss a lot of bytes! do you have complex scripts, SD logging or a lot of functions running in parallel?

[stevef1966]

i have nothing running, just a basic model, have not setup any functions other than a count down timer on the main arming switch (SF i think), dont believe SD card logging is turned on at all, but i can check just to be on the safe side

[bsongis]

if you disconnect everything from your XF Rx is it better? just to remove betaflight from the equation...

[stevef1966]

just disconnected the TX/RX pins (so the FC just provides power) from betaflight and its the same

[stevef1966]

do you want me to do another test without the flight controller in and send the logs, see if you can see anything different?

[bsongis]

yes please!

[stevef1966]

will upload tomorrow if thats ok

[stevef1966]

telemetry.log.txt

[stevef1966]

hows it going, did you find anything new?

[bsongis]

telemetry-decoded.txt

[bsongis]

Almost all frames are received with a wrong CRC

[bsongis]

obviously, and provided the wiring is good it's a bug on OpenTX side

[bsongis]

and the wiring is good, you receive channels on the CC and channels are transmitted via the same S.PORT PIN

[stevef1966]

i believe so, i will double check, previously i'd even re-soldered the internal qx7 pins just in case, i've even made a small harness to connect the qx7 pins to the crossfire to test the pins LOL... i'll reconnect and check today and let you know..

[stevef1966]

just tested again, tried to jiggle the pins, the only place (if its a pin/connection problem) is inside the crossfire itself, might try and see if i can open it up

[bsongis]

I don't believe it's possible, you wouldn't receive the channels

[bsongis]

I have Crossfire V1.63 (beta account) And I flashed the OpenTX firmware from the link above And my logs (after decoding) look like this, no CRC error ...

[2000-01-01,00:04:06.220] ea 0c 14 1f 1f 64 56 ff 02 01 17 64 5f 87 [Link Statistics] 
[2000-01-01,00:04:06.220] ea 0c 14 1f 1f 64 56 ff 02 01 17 64 5f 87 [Link Statistics] 
[2000-01-01,00:04:06.230] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 5f 13 [Link Statistics] 
[2000-01-01,00:04:06.230] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 5f 13 [Link Statistics] 
[2000-01-01,00:04:06.240] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 5f 13 [Link Statistics] 
[2000-01-01,00:04:06.240] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 5e c6 [Link Statistics] 
[2000-01-01,00:04:06.240] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 5e c6 [Link Statistics] 
[2000-01-01,00:04:06.250] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 5e c6 [Link Statistics] 
[2000-01-01,00:04:06.250] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 5e c6 [Link Statistics] 
[2000-01-01,00:04:06.260] ea 0c 14 1f 1f 64 55 ff 02 01 17 64 65 4e [Link Statistics] 
[2000-01-01,00:04:06.260] ea 0c 14 1f 1f 64 55 ff 02 01 17 64 5b 10 [Link Statistics] 
[2000-01-01,00:04:06.260] ea 0c 14 1f 1f 64 55 ff 02 01 17 64 5b 10 [Link Statistics] 
[2000-01-01,00:04:06.270] ea 0c 14 1f 1f 64 55 ff 02 01 17 64 5b 10 [Link Statistics] 
[2000-01-01,00:04:06.270] ea 0c 14 1f 1f 64 55 ff 02 01 17 64 5b 10 [Link Statistics] 
[2000-01-01,00:04:06.280] ea 0c 14 1f 1f 64 55 ff 02 01 17 64 5b 10 [Link Statistics] 
[2000-01-01,00:04:06.280] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5b 61 [Link Statistics] 
[2000-01-01,00:04:06.280] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5b 61 [Link Statistics] 
[2000-01-01,00:04:06.290] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5b 61 [Link Statistics] 
[2000-01-01,00:04:06.290] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5b 61 [Link Statistics] 
[2000-01-01,00:04:06.300] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5b 61 [Link Statistics] 
[2000-01-01,00:04:06.300] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5c 35 [Link Statistics] 
[2000-01-01,00:04:06.300] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5c 35 [Link Statistics] 
[2000-01-01,00:04:06.310] ea 0c 14 1f 1f 64 52 ff 02 01 17 64 5c 02 [Link Statistics] 
[2000-01-01,00:04:06.310] ea 0c 14 1f 1f 64 52 ff 02 01 17 64 5c 02 [Link Statistics] 
[2000-01-01,00:04:06.320] ea 0c 14 1f 1f 64 52 ff 02 01 17 64 5c 02 [Link Statistics] 
[2000-01-01,00:04:06.320] ea 0c 14 1f 1f 64 52 ff 02 01 17 64 5c 02 [Link Statistics] 
[2000-01-01,00:04:06.320] ea 0c 14 1f 1f 64 52 ff 02 01 17 64 5c 02 [Link Statistics] 
[2000-01-01,00:04:06.330] ea 0c 14 1f 1f 64 52 ff 02 01 17 64 47 d3 [Link Statistics] 
[2000-01-01,00:04:06.330] ea 0c 14 1f 1f 64 52 ff 02 01 17 64 47 d3 [Link Statistics] 
[2000-01-01,00:04:06.340] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 5f 9f [Link Statistics] 
[2000-01-01,00:04:06.340] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 44 4e [Link Statistics] 
[2000-01-01,00:04:06.340] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 44 4e [Link Statistics] 
[2000-01-01,00:04:06.350] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 63 be [Link Statistics] 
[2000-01-01,00:04:06.350] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 63 be [Link Statistics] 
[2000-01-01,00:04:06.360] ea 0c 14 1f 1f 64 59 ff 02 01 17 64 43 1a [Link Statistics] 
[2000-01-01,00:04:06.360] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 64 66 [Link Statistics] 
[2000-01-01,00:04:06.360] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 64 66 [Link Statistics] 
[2000-01-01,00:04:06.370] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 63 32 [Link Statistics] 
[2000-01-01,00:04:06.370] ea 0c 14 1f 1f 64 57 ff 02 01 17 64 63 32 [Link Statistics] 

[stevef1966]

do you think its the radio or the crossfire unit thats at fault? tell me what you need me to do, think i might start from scratch and try to eliminate everything where possible

[stevef1966]

just had the crossfire module bay adaptor in bits, have reworked the connections on the board... still the same, not looking like a physical hardware issue on my radio..

[bsongis]

do you confirm you use Crossfire V1.63?

[stevef1966]

currently im on the latest version, think its 1.65, i have tried all versions, i can go back to that specific version if you like, if it helps

[bsongis]

I just received a new production X7 and I reproduce your problem, I need now to investigate further

[bsongis]

Same firmware on the 2 radios, almost the same curve on the S.PORT Pin, same level. I need now to know if something changed recently (which would remove the possibility of going up to 400kBauds)

[stevef1966]

Good news, in a weird way I guess, if I can help further please let me know

[tonycake]

I can confirm this behavior. A crossfire taken from an 'old' Taranis, with telemetry working fine, then plugged into a Taranis X7, has an extremely poor telemetry link. Looking with an oscilloscope on the S-PORT pin shows a beautiful 400k baud serial stream in both directions.

[stonefoxfpv]

Also having the same problem, I had the Crossfire module installed into my X9D Plus and worked fine, on latest bata's was able to see telemetry from KISS FC from Crossfire on the Taranis. Now I've installed it on the QX7 and it seems to be recieveing telemetry but constantly says telemetry recovered/lost. Insterestly it does it when the quad isn't powered on. My brother is also having same issue. I did notice there is a folder called Crossfire in the X9D Plus SD card files, but no folder in the X7 SD card files. Which seems odd to me...

[bsongis]

The crossfire receiver has an internal battery, it continues to send telemetry once powered off

[stonefoxfpv]

Sorry, I'm using the Crossfire micro RX, which I don't think has a battery. Do you know why there isn't a Crossfire folder on the X7?

[bsongis]

Right for the micro RX. OpenTX has also a buffer for prompts to be played, so your buffer is full of "tememetry lost" / "telemetry recovered". Makes me think that we could do better, but this is not the issue we are discussing here

The crossfire script needs to be adapted for the small X7 screen. I will try to take care of this, but once we have a correct link ...

[stonefoxfpv]

Oh, gotcha. That makes sense. Thanks!

[stevef1966]

Hi any news on a fix for this?

[Drewlrox]

Was about to order the new smaller crossfire module then I saw this, anyone find any fixes? Would deleting the files work? Or could that cause the radio to freeze with all the requests to play the sound?

[Kalored]

Hi, I have the same issue on my QX7 as written above. My QX7 is about 3 month old and my Crossfire has V1.63 Version. With CRSF enabled. Would love to see a fix to that as it is crucial to me to have Telemetry packages. PPM also only have 8 channels which are a little too less. Running also with MicroRX v2

[Drewlrox]

Have you tried deleting the telemetry voice files and flying that way? If so did it work fine?

[Drewlrox]

So I have a crossfire micro pre ordered, somebody told me erasing the voice files has been working fine for them. Is a lua script being developed? The micro tx has no screen and relies on the lua script to change settings.