Posts: 12,099
Threads: 125
Likes Received: 3,739 in 2,836 posts
Likes Given: 99
Joined: Feb 2017
Reputation:
388 The endpoints should not be the issue. But the larger jitter could be your problem. When you move the yaw stick to the left, does the value in the radio match the value in betaflight?
Posts: 9
Threads: 2
Likes Received: 0 in 0 posts
Likes Given: 3
Joined: Aug 2020
Reputation:
0 17-Aug-2020, 07:10 AM (This post was last modified: 17-Aug-2020, 07:10 AM by Liamriley1986.) Hi Voodoo, really appreciate the reply! The Left gimbal doesn't appear to have the correct readings in most of its positions. (i.e.)
BOTTOM LEFT- 1028
LEFT- 1026
UP-2000
DOWN 1000
RIGHT-1883
I tried some further troubleshooting last night after some more thinking about it, it appears to be my radio transmitter. Its a 'FAT SHARK radio', I plugged in to my freerider sim and it seems to perform drastically better that on my actual quad but does seem to have a similar issue at times. This could be down to my poor computer spec as its always glitchy. I just struggle to believe that its the controller as its so new (beginning of July).
The issue comes recently after a frame replacement, a couple of motor bells and a new Vtx antenna but this may all be a coincidence as immediately after the repairs all was well for around 10 battery flights.
Thanks again.
Liam.
• Posts: 12,099
Threads: 125
Likes Received: 3,739 in 2,836 posts
Likes Given: 99
Joined: Feb 2017
Reputation:
388 I don't think you can calibrate the Fatshark radio. So you will need to use the rxrange. You have to change the rxrange through CLI. Go to cli and type "rxrange". It should see four rxrange
rxrange 0 1000 2000
rxrange 1 1000 2000
rxrange 2 1000 2000
rxrange 3 1000 2000
In your case, yaw is only 1026-1883. So copy and paste the two lines below.
rxrange 2 1026-1883
Save
• Posts: 9
Threads: 2
Likes Received: 0 in 0 posts
Likes Given: 3
Joined: Aug 2020
Reputation:
0 Hi mate, thanks for the information. I gave it a whirl, when I press enter after the copy and paste the software flashed up a quick error message and then disconnected. When it reconnected again I typed dump in to the cli to check the rxrange 2 limits and there was no change.
I also found that when my gimble is all the way to the left and I start to move throttle up the YAW just becomes completely erratic, even though by rights it should be reading 1000. It's spiking to 1400-1600 in some cases.... very weird!
I have however contacted the shop I purchased it from and they asked for a video of the issue, they went back to FS and I now await their response. The RC was just a cheap start in to the hobby but now I'm looking to purchase the Taranis Xlite as I look to complete my first 5'' build. Really appreciate you helping me get to the bottom of the issue, its nice to know a hobby like this has good people ready to help out!
• Posts: 12,099
Threads: 125
Likes Received: 3,739 in 2,836 posts
Likes Given: 99
Joined: Feb 2017
Reputation:
388 So instead of the two lines. Just type the one line and enter. Tell me what error you get.
rxrange 2 1026-1883
That is weird with what the radio is doing. You might have a defective radio. Hopefully the vendor gives you a replacement or refund.
• Posts: 9
Threads: 2
Likes Received: 0 in 0 posts
Likes Given: 3
Joined: Aug 2020
Reputation:
0 Hi mate, I get the following message
# rxrange 2 1026-1883
###ERROR: PARSE ERROR###
Yes I think they will send a new one or a refund. Hoping for a refund to go towards the new one tbh.
• Posts: 1,312
Threads: 50
Likes Received: 832 in 504 posts
Likes Given: 372
Joined: Jul 2018
Reputation:
51 Try it without the dash:
rxrange 2 1026 1883
The ground is for dead people.
•