openrcforums

I have been flying a X6R in my Yak and all had been great. I started to have a servo searching causing a rudder wiggle. I thought it was caused by the receiver so I decided to flash it with FrSky's latest firmware.

Since flashing the receiver I have replaced the receiver and antenna in the same exact spots. But, what I am finding is that when put on range checks mode I can only get about 16ft from the receiver and am getting a low or critical warning. I can then walk 100+ft from it and still have control. I have moved the antenna the all over and get the same results. Out of range check and only a couple feet from it RSSI is only 85-90.

Is there a known issue with this version of firmware? Is there a better version than FrSky's latest firmware?

Thanks
Steve

Wildvortex wrote: ↑Tue Oct 24, 2017 4:19 pm I have been flying a X6R in my Yak and all had been great.
I started to have a servo searching, causing a rudder wiggle.
Thanks
Steve

My first though that may be the cause of your "servo Rudder wiggle",
dose this happen at the same time when moving other servo controls,
like Ailerons and/or Elevators servos ?

If servo wires are to close together, a spike of signal from one wire can jump
to the other servo-wire causing the servo to flutter (servo wiggle).

I do not believe FrSky receiver firmware is your problem.

The wiggle turned out to be some grass caught up under there servo arm, or so it seems.

You found it ! COOL !

Yah found the wiggle problem but am still getting the low/critical warning way too close no matter the orientation of the antenna, which was the actual problem posted. I had the wiggle problem solved days ago.

I was not getting the warning anywhere I flew prior to flashing. Now I get it when flying in the normal flight path.

Hummmm .......

I use both D-Series and X-Series receivers and Yes, when the X-Series came out
it does Alarm much sooner then the D-Series which work a lot better reporting signal Alarms.
Normally (X-Series) we first get lost of telemetry "NO Telemetry" Alarm warnings.
Next alarms we then will get "Low RSSI" Alarms.

If MikeB see this, he can better explain why S.Port (X-Series) alarms sooner than the analog (D-Series) telemetry alarms do.

I may not have my facts right, but I will make a try at it.

FrSky X-Series XJT modules to there X-Series Receivers use the S.Port telemetry, which runs faster then the D-Series telemetry system.

The signal strength between your XJT transmitter and its Receivers is changing up and down all the time when flying and this telemetry data is being collected and this group of telemetry data is processed before it is sent to your radio, which will then report its results of this group of collected telemetry data.
So if the average data results is low then it will trips the Alarm and if it is high it does not trip the alarm.

So it looks like, it is more difficult to manage the faster S.Port telemetry data then the slower analog D-Series telemetry data.

The X-Series does have a longer signal range then the D-Series, but does alarm much sooner than the D-Series.
(people have complained about this, but it seems to be difficult to fix, I use erSky9x on Taranis firmware and seem to work better for me)

The many other variables you have been working on can be one or several causes too.
It is hard to find because there can be a lot things and some of these things can not be seen visually.

Trying to see (understand) what the signal is doing is not an easy thing to figure out.
I can point you to more info about this if you like, I got go for now.

=================================================================================================
Added info Oct 29 2017: How do Antennas work ? : (https://www.youtube.com/watch?v=fSoXIqBlg9M&t=610s),
(https://www.youtube.com/watch?v=xCVd3QGQhKU),
(http://www.immersionrc.com/downloads/ma ... Manual.pdf),
(https://www.hobbyking.com/hobbyking/sto ... duct=51616),
(http://j3.rf-explorer.com/40-rfe/articl ... cification),
more info about spectrum analyzers: (https://www.youtube.com/watch?v=19JNDCVHaQQ)
and (https://en.wikipedia.org/wiki/Radio_spectrum).
Why I modified the antenna on my 2.4GHz RC radio: (https://www.youtube.com/watch?time_cont ... nK3HGzdmTc).
CP omnis near ground = Increased gain ?: (https://www.youtube.com/watch?v=ej3_kZ5zi1I).
(https://www.youtube.com/watch?v=1NXFps7ZIlg)
Testing Home-Made 5.8ghz Antennas: (https://www.youtube.com/watch?v=jlz8MTTntGI).

Directional Antenna find lost model: (viewtopic.php?f=45&t=10466),
GPS Racing Discussion: (https://www.rcgroups.com/forums/showthr ... Discussion)
FrSky GPS 10Hz firmware: (https://www.rcgroups.com/forums/showthr ... z-firmware).
=================================================================================================

Blessings,
Bob B.

Problem is that I have always flown X series and this is not a new RX in the aircraft it is the same RX just that it has been flashed with the latest firmware.

Is there a place to download old Firmware?

ow did you flash the receiver? using the radio?

João

jhsa wrote: ↑Wed Oct 25, 2017 2:59 pm ow did you flash the receiver? using the radio?

João

I flashed using the computer and the STK board.

https://www.frsky-rc.com/x6r/ has also the older firmware versions. What is the exact name of the firmware you have flashed?

X8R_NONEU_build170210.frk

You can try, if the 150115 version works for you, but imo it is a hardware issue, eventually caused by static discharge, when you were handling and flashing the RX.

I hope not, the thing is as stated in the beginning I can put the TX in range check mode and walk over 100ft and still have control of the aircraft. it starts telling me a low or critical signal just 10 ft. away. With the Tx in normal mode I can be on top of it and only have about an 80 - 85 RSSI. I will try a re-flash and hope that that takes care of the problem. Otherwise I guess I will be back on here some more.

I guess that I must have gotten a bad package when I flashed the RX. I tried flashing an earlier firmware to the RX and was totally unable to get it to bind, even with going through the bind procedure. I then Reflashed the latest software and then did a range test and all was well. so, I guess a bad upload? I don't care as long as it works. Thanks for the help or attempt at help.

Steve

Glad to see you got it fixed.
Faulty flashing then.

Seems that way.

Do you think you needed to flash your receiver in the first place ?

Wildvortex wrote: ↑Tue Oct 24, 2017 4:19 pm Since flashing the receiver (low/critical warning issue)

No, I flashed it because the rudder was searching for center. After flashing it I still had that problem. There was some trash under the servo arm. It was actually acting like I had digital mixed with analog servos.

OK