The Tricopter yaw problem has been on the forum for months, and as fas as I can see it has not been resolved. There is a massive deadband on the yaw servo so that yaw control is like slamming a barn door, smooth control is impossible. A solution was offered recently to fix the problem by changing the deadband value of 600 in the radio.pde. I'm using 2.0.42, when I change the the deadband to 200, compile and upload using arduino IDE it appears that the deadband is reduced to an acceptable level. But when you fly it the yaw does not hold, there is crosstalk between pitch and yaw and if you select altitude hold it goes banana's with pitch and roll swopped ??.
It seems to me that the various airframes + x Y6 octo etc are all good. But the code does not work when you introduce a servo as in the TRI.
If you can propose a fix, we'd be glad to implement it. But I don't think any of the developers are flying Tris, so we can't test them ourselves.
Well I don't know Chris, it seems this problem has been around ever since the TRI got introduced into the range of airframes. There have been many posts on the forum about this, it's been suggested that there is a flaw in the software which will get fixed at some point in the future. It's not trivial, it's a primary control that does not work .
For people who have invested time and money in building tricopters it's disappointing that none of the developers have even tested the tricopter software so there's little hope of this problem getting fixed.
I'm not naive, I understand there's been a lot of development, and you are close to developing a great system. But if you read your Wiki, first page, 'about Arducopter' there is no mention of development or Beta, it reads like a done deal, all the fabulous features work, have fun and fly. I think this is some way from the truth and could mislead newcomers.
Sorry this is a bit of a rant, but this problem is frustrating me a many others, my Tricopter is about to grow another arm.
As Jason mentioned, if someone can identify a problem with the latest code and Tricopters, we'll get right on fixing it. We support so many configurations and platforms that it's hard to keep up with all of them with each version of the code, so we count on community members with unique setups to help us catch and fix any issues that crop up. Although none of the core dev team flies Tricopters regularily, we do have members such as Jani who have access to one and can check any issues that are identified.
Have you flown the latest code? The deadband issue was fixed in 47. The deadband no longer has a hard step. Instead it has a smooth transition.
The pitch and yaw problem sounds completely unrelated to Tri's. Disable your compass and try it again to confirm.
I believe it's most likely your compass causing issues when the new firmware is loaded. The calibration is erased with the EEPROM and must be flown a few minutes and saved. Also you don't have any Ublox running do you?
Please put up any other issues to the issues list.
Have just loaded 2.0.48, and the yaw problem is fixed, thankyou. But I'm sorry to say that even after adjusting the stable mode PID's it does not fly as well as 2.0.42. There roll and pitch controls seem less smooth and there's a big deadband on the pitch control. Sorry about this.