Frsky R9M & R9MM, low LQ barely controllable #1023
Comments
|
I had similar problems with v1.1 where the control link was completely lost until I cycled the transmitter power. I thought the ticket below might have solved this but seems to have changed the problem slightly. Many thanks Matt |
|
Hi, i had the same issue yesterday with my Mini Talon. TX: X9D with OneBitFirmware R9Mv1 I had a nice 25min flight without issues, on the 2nd flight, it started to get FS, and i only could regain control when i power cycled the TX. Nearly killed my mini talon as it went in FS again on landing and went to RTH and yanked itself into the ground... |
|
a short video of the failure. I had previous problems with V1.1, so did a 360 as a range check then it failed. Took a few seconds of fighting betaflight rescue and working out what control was available but had the same level of control all the way home. https://www.youtube.com/watch?v=2RyGFkSGeb0&ab_channel=MatthewCattell |
mattcattell
changed the title
That YT vid does not help, please upload the DVR with the OSD information. (LQ and RSSI-dbm at least.) |
|
Unfortunately the DVR on DJI goggles doesn't record the OSD but from memory LQ was bouncing between 0 & 6%. I'll setup the black box recorder in betaflight to grab some data for when it happens again. |
|
Same Problem. loos LQ. i Try to CLI : failsafe_stick_threshold = 10. |
|
|
Hi, sry for the delay, here is my video with the problem: https://www.youtube.com/watch?v=6f6MEF7zJM8 |
|
I’ve finally got chance to go flying again. Betaflight blackbox wasn’t much use for capturing the failure, I thought capturing the crossfire statistics would give some useful data but I don’t think ELRS is sending the statistics packet as it’s always returns 0 but I have captured some data in opentx. This data freezes when the telemetry falls over but on the OSD the LQ (AUX11) is cycling from 0 to 6 - 10% every few seconds, as per x4FF3's video.
|
|
ELRS seems rock solid, if I'm flying without anyone else on 868 Mhz but as soon as a Crossfire transmitter is on it causes a problem. One thing i noticed the TQly stays up at 100% with just ELRS on but as soon as a Crossfire transmitter is on, this value will cycle from 100% down to 90% around every 5 seconds without being in the air. I'm not sure if this is related or not?? |
|
The 868MHz band is pretty small so it's very likely that the signal quality takes a hit with other transmissions on the same band. That is true for telemetry data + control data. @mattcattell do you get a FS when a crossfire transmitter is on or does the signal quality go down? |
@schugabe, Yes this triggers a FS in some situations but from this point forward ELRS drops into a strange mode where telemetry is permanently lost and the model will be difficult to control due it only receiving an updated command every 0.2/0.3 seconds. This can only regained by cycling the power on my transmitter. The crossfire transmitter being switched on doesn't instantly cause a FS or fault but i do see a drop in TQly. |
|
I flew 6 batteries today with V2.0 RC2 and every flight had the problem above, some batteries I landed & restarted the transmitter and it happened again shortly afterwards. A few things to note, the controllability has improved when ELRS drops into this mode but this build seems more susceptible to it failing and also occurred without a crossfire transmitter powered. The improved controllability in this failure mode is due to a slightly faster update rate, probably something like 0.1S, presumably due to the variable sync pulse frequency? I also recorded the following video of the OSD LQ (AUX11) when ELRS drops into this mode, these LQ values are identical to all the failures I've had, the distance from home doesn't change these values. All these flights where short range, 50/60 meters maximum. |
your LQ shows the same behaviour as mine on my talon. |
|
Something similar happened to me last week approx. three times, on the table. TBS Mambo + R9M ELRS 2.0.0-RC3 It works ok, but sometimes transmitter lose telemetry and refresh rate drops down to 1-2Hz, I checked it in receiver tab in inav configurator. It confirms what I see on plane, low refresh rate. CPU load was 14%. If it happens lua ELRS script can't load settings from R9M module, I see only "??????". Only way how to "recover" it to normal is turn off/on transmitter. I would like to help to debug it, but I'm not familiar with platformio + stm32, I use clion + cmake. Would be nice to create simple manual how to start debugging over SWD from platformio. |
|
I set my plane on table and then without any reason again lose telemetry. R9M FW: ELRS compiled from 2.0.x-maintenance R9mini receiver: ELRS 2.0.0-RC2 DVR: https://www.youtube.com/watch?v=sp4njBPYISo |
Do you have the 2018 or 2019 version of the r9m module? Did you use an older version of elrs before that did not have that issue? |
|
I have 2018 + resistor mod. Over summer I used 1.x.x version without any problem. I will test it today whether 1.x.x is still ok. |
I had another report of a 2018 module 1.1 working and 1.2 not working. Can you try both versions and report back if this is also true in your case? |
|
Do you mean 2.x.x? Not " 1.2 n" |
|
The other guy reported that the issues did start with version 1.2 but version 1.1 was working fine |
|
Ok, will try it |
|
try 2.0.x-maintenance, afaik barry's fix did get merged into it |
|
It's difficult to reproduce, because failing is randomly. I did a few tests. 1.1 -I couldn't get a failing |
|
I'd agree with your findings v1.1 was definitely harder to fail and the latest 2.0rc3 fails easily and is giving me big problems at the moment. The problem with v1.1 is that you lose control of your model and have to rely on the rescue/rth while you cycle the power on your transmitter. |
|
is it fixed? |
|
No, still having problems. I tried turning off telemetry today and it removes all the failure problems but with 2.0 rc3 the range was shocking at 250mW. My frsky xm+ receiver out performed it by a mile !! So as a work around i think v1.1 with telemetry disabled might work for short term fix until this problem is resolved, something to try |
|
what do you guys do to make it fail on the bench? |
|
I don't know what you want to know. I turn on transmitter, turn on plane and just wait to connection failure. I bought new antenna, it didn't solve issue. |
More details please: how far appart are tx+rx, how long does it take, how often do you have to plug it in until the error comes up |
I think that R9 has header pins with uart, maybe would be nice to use it for debug information, or add debug information to lua script. |
|
I spent whole day to try out what can be wrong or how to reproduce the issue. The issue is randomly. I tried another FC, inav 3 and 4, different distance between TX and RX. Sometimes it fails within 30s after TX bootup, sometimes it works 30min withou any issue. |
I did flash my R9M + R9mm with RC4
And did test like 10 power cycles with 1min run time and had it running once for 60min and everything is working without any issues. I'm not saying that your problems are not real but I can't reproduce it and would suspect something wrong with the hardware. Did you try to lower the baud rate in the opentx settings? @error414 |
|
I can't change baud rate because there is not option for that. I use TBS Mambo. It uses freeTx, Should be released edgeTX for TBS mambo soon, so then I will try change baud rate. And I will order new ELRS 868 module. I understand that this kind of issue is difficult to find. |
|
New R9M 2019 flashed to ExpressLRS version 2.0.0 here. Issue affects this version/hardware as well. Occurs randomly: sometimes after 20 minutes, sometimes after 2 hours or even longer. Quad does not go into RC FAILSAFE when this happens and is hardly controllable because of the low update rate (1Hz?) of the remaining radio link after error occurred. |
|
Updated the R9M RX and TX to version 2.0.1 EDIT: still happens. First test session seemed perfect. When it happened I did disarm and arm again and did not get the telemetry feedback from doing so. Then i powercycled the whole transmitter and hence its r9m tx module. |
|
So it looks like this issue happens on the r9m 2019 and the r9m v1? |
|
Still problem with R9 System?!! MMm. All others no Problem but R9 failt. Thats not good. I want fly !!!! i hope That will fixt soon. i dont want more Quands damaget. My patience is at the end. |
|
I had to switch to tracer, I don't have time to wait half year to fix. :(((( Maybe some day I will try ELRS again. |
|
@brandonrc Yes. It affects me on r9m 2019. And @mattcattell and @error414 ran into it on the v1. Issue happens on both openTX 2.3.14 and on edgeTX 2.5.0. How can we investigate this further? Might a st-link be of any help here? |
|
wat is st-link? |
device for flashing/debuging STM32 micro controllers. urksl: |
|
did someone test another tx+r9rx? as i would order an es900tx for comparison. |
|
Same problem with ELRS 2.0.1, Dynamic power (MAX250mw), 200Hz, Telem 1:8, R9M 2019 + R9 MM-OTA, ErskyTX on AR9X board |
|
Please test with 2.1: this release does contain some fixes that could help with this issue. I still cannot reproduce the issue with my hardware so it's hard to verify if the release changes the situation. |
Maybe is not possible, since R9M firmware doesn't compile with debug anymore because of lack of space. |
|
I am very happy to test the new firmware 2.1.0. I will then report it to you. Not sure which Hz rate and tlm ratio is best for long range. What do you all mean? |
|
yesterday I tested ELRS v 2.2.0 - in the same place 8 flights with another pilot nearby on a crossfire with 250mw. It looks like everything is fine. I didn't have a problem with low LQ |
|
Yes me too. 20flights without problems. Longrange are comming (to much Snow at the moment). The Dynamic Power; regulates relatively late, around 105-110 db at 50 hz, only then does it go higher to 25mW, I think that should happen earlier, 10% or 20% db before. But first i have to test the Long range. |
|
Hi, i tested 2.2.0 on the bench with 25mW@50Hz, it stops working after 30s - 60s. Later on i can do a video with OSD and movement of the sticks and servos. EDIT: |
|
This issue was closed because it has been inactive for 12 days since being marked as closing. |
Current Behavior
The radio link fails giving no telemetry with an LQ of < 10%, the control link doesn’t completely stop working but gives the impression of very high latency due to very few error free packets making it thru.
Cycling the power to the model makes no difference, only cycling power to the transmitter corrects the problem.
Steps to Reproduce
??
Possible Solution (Not obligatory)
Details
I had this failure on 3 out of 15 flights today 24/10/21, flying with a friend using crossfire seems to provoke the problem.
Extremely difficult to control model & not trusting the expresslrs over any distance.
stock v1.2.0 build
Your Environment
REGULATORY_DOMAIN_EU_868
FEATURE_OPENTX_SYNC
HYBRID_SWITCHES_8
ENABLE_TELEMETRY
TLM_REPORT_INTERVAL_MS – 300LU
JUST_BEEP_ONCE
The text was updated successfully, but these errors were encountered: