Getting low RSSI while using Flysky rxs on 2.8

EdgeTX / edgetx

EdgeTX is the cutting edge open source firmware for your R/C radio

https://edgetx.org

GNU General Public License v2.0

1.64k stars 345 forks source link

Getting low RSSI while using Flysky rxs on 2.8 #2349

Open Mikey1968 opened 2 years ago

Mikey1968 commented 2 years ago

Is there an existing issue for this problem?

[X] I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

When I was on 2.7 everything works great, when I went to 2.8 Nightly and flew my planes I was getting low rssi warnings that I never had before

Expected Behavior

Hopefully you guys fixed the problem

Steps To Reproduce

Version

Nightly (Please give date/commit below)

Transmitter

Radiomaster TX16S

Anything else?

No response

raphaelcoeffic commented 2 years ago

@Mikey1968 we will need a bit more detail ;-)

Are these assumptions correct?

Multi-protocol Module (MPM)
AFHDS2A
Original ADFHS2A receiver? (which one? I have only very few)

Could you give us more details on the specific of what you consider low RSSI values? How where they before, how does it look like now?

Mikey1968 commented 2 years ago

I have the Radiomaster TX16s Mk2 using AFHDS2A using the FS-iA6B rx . Before when using 2.7 everything works great no rssi while flying . When I updated to 2.8 Nightly everything was working great until I did a flight and noticed at close flying I was getting rssi warnings. So decided to land . Wasnt trusting it so went back to 2.7 . Might be nothing and just a glitch . Im going to download the new 2.8 RC1 and see if it happens again

Mikey1968 commented 2 years ago

also another thing I noticed , when you pick a track , you used to be able to scroll backward s from X to A to pick a sound. Put the version I was using you could only scroll a-z

pfeerick commented 2 years ago

The actual RSSI is unlikely to change, since everything RF is the job of the RF module, in this case the internal MPM. So you shouldn't have any changes there - only potentially how ETX is interpreting the RSSI/or the warning value being lower (higher?). IT may be worth adding a SD logging special function assigned to a switch, and log a flight (or even just walking say 30 metres away and turn around or something - something easily repeatable) with 2.7 then the same with 2.8 if you can, and see if the telemetry logs show anything different.

And yes, all the lists are one way now, but that is a different issue - whether that will change I don't know - the velocity tweaks make it so you can go from one end of the list to the other with nearly one fast turn of the rotary encoder (and not keep going around a second time). ;)