Originally Posted by
walid67
Hello Gents,
I have experienced exactly the same symptoms of shortandsweet below, I installed my new receiver (not updated yet) on my MXS EF 94'' and using my Spektrum DX9, airware 2.0 updated. When I started doing range test on low power, I was surprised that RSSI alarm message was coming up all the time although the range test went very well and I could reach 50 m at low power and still was able to connect with the receiver. Then I decided to move to high power and do another range check where I will go for 600 m, again all went well but RSSI alarm went down to 4%, I was still getting good link with the receiver.
I decided to fly and remove the alarm on RSSI, all went well, Frame losses sometimes were zero and sometimes 4 per flight. No Hold occurred.
I have already bought the cable to upgrade the receiver, its on the way.
What is causing this problem? the receiver is usable and performing well but having good working telemetry is also a must, this is part of the package I bought and paid for.
I'm not sure what you are seeing as the problem. If it is the low RSSI number when on the ground, this is normal. It's called the Fresnel Zone effect and you can read about it in many scholarly places on the web as well as some RC sites (which is sometimes in error). Basically, when you are close to the ground, signal range is dramatically lowered.
The best units for RSSI reporting are %Range. The raw % is useless in my opinion. The dBm value is the most valuable, but it is hard for most folks to understand. Note that at close range, the dBm value drops off rapidly but drops more slowly as you get farther away. That is because this is a logarithmic value.
If you are seeing telemetry range as an issue, keep in mind that telemetry range on these is about 40% of control range at most. You have control of your model for about 2km (it depends very much on environmental and installation, so I can't give you an exact number) in the air. You can only see it for a much shorter range, so if you can see your model then you can control your model.
There is also another issue with this same receiver and has to do with Servo twitching, but will leave it for another discussion
As noted in the previous message, that is corrected with the update. Please update your receiver to the new code.
Andy