Posts: 3
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 1
Joined: Aug 2017
Reputation:
0 23-Aug-2017, 11:30 AM (This post was last modified: 23-Aug-2017, 03:27 PM by eddiel454.) I read Oscarliangs blog for using the lua script for PID tuning a BetaFlight FC but I am having some technical issues with trying to tune through my Taranis Q X7. I ccould change and save almost all parameters (PID, RC rates, super rate, RC Expo) except for the P parameters of Roll and pitch, after adjust the parameters and saving it, the values for P on roll and pitch drop to 0, I confirm that it isnt showing the wrong value because betaflight also reads 0 from the FC via USB cable. Hope someone can help.
Im using:
SP racing F3 Deluxe (one with OSD but not betaflight's OSD)
XSR with firmware version 170619
Taranis Q X7 with version 2.2.0 openTx with lua & luac
• Posts: 2,416
Threads: 51
Likes Received: 1,861 in 1,175 posts
Likes Given: 3,315
Joined: Mar 2016
Reputation:
74 eddie, you don't need to cross post. People will see your question in one place. Also, being new, you should try to do a search on a topic before you post. This question was answered recently. I'll let you search, but it involves downgrading the software on your XSR.
Posts: 3
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 1
Joined: Aug 2017
Reputation:
0 23-Aug-2017, 12:36 PM (This post was last modified: 23-Aug-2017, 01:37 PM by eddiel454.) I thought the issue is on for softwae version 170605, unless the issue is persistent on version 170619 too
Update: downgrading XSR did not fix the issue, the p value still drops 0 to zero. I notice it dropping by reloading every second or so, the p value drops bit by bit at a steady constant rate.
• Posts: 5,314
Threads: 672
Likes Received: 3,155 in 1,743 posts
Likes Given: 2,027
Joined: Jan 2016
Reputation:
139 23-Aug-2017, 02:34 PM (This post was last modified: 23-Aug-2017, 02:35 PM by Oscar.) Try to roll back XSR version back to the 15XXXX. by the way what version of BF do you run? You might want to try 3.1.7 as well in case it's bug in 3.2 (RC)
•