วีดีโอ

It doesn't work with mine. I can't setup the curves properly. As soon as I edit a curve, the next previous one gets edited with wrong values. I think it's a firmware bug. I have fdtx-tango firmware, version TBS-1.3.0

It's useful during blackbox logging when PID tuning a quad.

If you know anything about PIDtoolbox, you’d use this for pid tuning using the step response. I should have added that to the video but I assumed anyone following my channel would be familiar with this. It was a vid for Patreon that I just released to the public without thinking that many newcomers might need context. Probably time to do an updated video about pid tuning using PIDtoolbox

@@zofflex either works

Of course you can. You can join, get the software then downgrade to free member. It’s best to stay for the month then downgrade to free member as there’s content available, and in case you ever want to upgrade to future PTB versions it’s easier

PTB is only available on Patreon (link in the description). Older versions do not work with BF4.5 and onward anyway

PTB is only available through Patreon. Older versions of PTB do not work with BF 4.5 and onward. The latest PTB is BF 4.5+ ready and is also backward compatible with any version of BF

Leave angle strength at 50. Set rates to linear for tuning. Set angle feedforward to 0 (it’s in CLI)

@@PIDtoolbox ok thanks

@@PIDtoolbox ok I've done some tests and I'm confused : Test 1 acro, rates with expo, angle FF=50 Test 2 angle, rates with expo, angle FF=50 Test 3 acro, linear rates, angle FF=50 Test 4 angle, linear rates, angle FF=50 Test 5 acro, linear rates, angle FF=0 Test 6 angle, linear rates, angle FF=0 All tests (1,3,5) on acro mode are nearly similiar as expected... but, every test on angle mode (2, 4, 6) gives very different result and none of them are like tests on acro. If I have to choose which one on angle mode is closer to acro then test no. 2 will be closest, but it's different enought that it cannot be used in basement tuning method in angle and then fly in acro. Till BF4.4.3 everything was crispy clear, easy and repetitive but now it looks like you can't use angle to get the same result in acro If you want to look BB log tests then I can send it to you.

@@Prosto_o_Dronach send link to 2 logfiles that show a difference between angle vs acro

@@PIDtoolbox all 6 tests in zip drive.google.com/file/d/18we8sLN-JqOwQ5vtaDR3kCkQvikt5s8t/view?usp=drive_link

@@jirisolnicka2146 apologies. It’s moved to a paid application under Patreon ($3 CAD): www.patreon.com/posts/111617420?

@@PIDtoolbox Thank you for reply, no problem, 3 CAD is very reasonable price.

Most people do not understand the GPL software license. As the sole developer of PTB, I cannot violate the license of my own code. The GPL license is issued BY the owner (me) TO the user, giving the user rights to use, modify (even sell) that code provided the source is given freely as well. So in GPL, 'FREE' does not mean 0$; 'It means 'freedom to' use/modify/sell. The user can violate the license of someone else's code, but not their own. This gets complicated when there are multiple devs of a project. E.g. A BF dev (or other user) cannot fork a version of BF, modify it, release it, then close their source. This would be a GPL license violation because the code is the copyright of many many people (other devs). HOWEVER, each dev always retains the copyright of his/her own specific code, and can do whatever they want with that. He/she can decide to further develop his/her specific code (excluding contributions of others), without any obligation to anyone.

@@PIDtoolbox Yep, hence my edit. It always raises my hackles when I see GPL'd software go closed source since as you noted if there are multiple contributors it has to be done with their permission for it to be legal. (It would never be possible with the Linux kernel for example--by design.) But you've got a clean repo with no other contributors so it's 100% yours.

Thicc is fine. No issues with tuning it on 4.5

❤ 0.73 is also now available. Mainly just bug fixes

It means you didn’t follow the installation vid carefully

@@PIDtoolbox The thing is, the default install location is C:\Program Files\ and PID toolbox exe doesn't have anything in its manifest that forces it to run with admin rights. So obviously it cannot write into the folder where it runs. It can't create the log file. The dev could make things far more easier for users by 1) defaulting to a non C:\Program Files directory for install, for example, the Users folder as the standard approach followed by apps that doesn't need elevated rights and apps that install only for the current user 2) Even if the default install location is kept at C:\Program Files, the working directory could in within the Users folder. With these approaches, there's no need to have the program binaries separately shipped and no need to ask users to run it from another folder or anything. The installed binaries and the shortcut should just work well.

@@Sleeperknot MAtlab App compiler does not allow install locations besides the typical Programs Folder. The 'working directory has to include the 3rd party BB_decode programs to extract the data from .bbl files. It's just how it is. Most have no issue if they follow the instructions.