This F@#$*ng Crossfire LQ thing again...
I really don't know why this is so hard for some people to understand. Here's a quick explanation if you can't read manuals.
Crossfire
Operation Modes - There are two Op. Modes: Normal and Forced Telemetry.
Normal Mode:
- Allows you to use 3 RF Profiles (see below)
Forced Telemetry Mode:
- 50Hz and 4Hz update rates (switches between RFMode1 and RFMode0 based on signal quality). Basically, like the manual says, do not use it if you don't know what you're doing. I believe there's a bug...try it and you will understand. Good luck.
RF "Profiles"
- Dynamic = Switches between RFMode 2 and RFMode 1 using unicorn magic.
- Forced 150Hz = RFMode 2
- Forced 50Hz = RFMode 1
RF "Modes"
- RFMode 2 = 150Hz update rate. LQ Scaled [RTFM..300%]
- RFMode 1 = 50Hz update rate. LQ Scaled [0..100%] <--not 100-200 ffs!
- RFMode 0 = 4Hz update rate. LQ Scaled [0..100%] (only used if Forced Telemetry mode is set).
LQ prewaring at 70%, critical at 60%
Tracer
Tracer = RFMode 1 at 250Hz mode. LQ scaled [0..100%]
LQ prewaring at 30%, critical at 20%. Now, if you are one of the few people that read manuals, you will notice why the TBS manuals need a bit of improvement. One place has the warning at 30% and another at 50%. Considering the issues people are having with random signal issues, I'd recommend starting with 50%. UPDATE: A later revision of the manual has 40% prewarning and 30% critical.
UPDATE 12/22/2021:
TBS is adding LoRa to Tracer. Initial tests look promising. That signal looks solid compared to "other" systems. RFMode 1 at 250Hz and RFMode 2 at 50Hz may break the OSD in INAV. Already thinking of a solution but TBS should change the modes to the corresponding numbers that align to legacy CRSF.
Now go and crash something.
Happy Halloween!
Comments