I have the APM 1.0 on my tricopter. The latest tricopter firmware was downloaded today.
It seems the motors are working correctly. IE: They respond to input from RC Transmitter and seem act correctly as the tricopter is tilted.
I cannot however get any movement from the tail servo. When looking at the APM Planner -> Radio setup it is reading my rudder input from the RC TX...the servo just isn't doing anything.
I read a couple other people with this issue...however they were able to get movement when in manual mode. The firmware I downloaded today...does not have manual mode.
I checked all the connections against the diagrams think it is correct. The servo is connected to 7 on the APM
Does anyone know how to fix this or point me in the right direction?
It flies. Its very windy today and she didn't like it that well. It seems the gyros are a bit too sensitive for high winds. She did real good close to the ground not as exposed. Burned up a whole battery with no issues. The tweaking begins.
Any chance you could point me to a good tricopter config file?
I'm jealous that you got to fly... glad it went well-ish.
Since there's no standard airframe, a 'good' tricopter config file doesn't exist. It's entirely dependant on your frame, motors, weight, etc etc.
I've started working on a tuning procedure for my own use, that goes flight mode by flight mode. I'll be glad to share it when I'm done. Right now I'm still trying to collect all the different tips and changes and figure out what order they should all be in. It will probably be a couple of days.
My starting point was this from aeroquad. There's been some changes in the PID loops and config process based on Igor's changes. If you get 2.2b6, you can look at Igor's tuning procedure in his blog post here. Some, most or all of his changes were used in the latest release.
I wanted to let you know we flew today with only a slight wind. Maybe 3-5 knots and it flew great. The APM reacts to inputs much different than the KKBoard.
The config file has not been changed at all yet. I still think the gyros are bit sensitive...but need some more flight testing. Today...It hovered in my driveway for quite a few seconds at a time with no input. Thats in Stabilize mode.
The battery is on top so I can carry a camera on the bottom. This tri has probably 30-40 hours of flight time. After the first flight with my new Ardu...I completely refurbished this baby over the weekend and got her back in the air today. 2 Batteries worth...I can't even say how cool/different the take offs and landings are. When the wind died to almost nothing...I took off with NO inputs except throttle. It went strait up and hovered for a while...That's a stabilization system!!!!
Thanks again for your help!
How much fiddling did you have to do with the PIDs, or is that what you meant by when you said the config file hadn't been changed?
Could you share your motor and prop specs, motor to motor distances and all up weight? Since there's no 'official' frame, I'm thinking it might be nice to at least get a set of basic specs together and try and match them to a good starting set of tricopter PIDs.
You are correct...No fiddling with the PID's yet. This is stock...Actually...From the firmware you sent...all I did was go through the radio setup.
The motors are E-Flight Park 400 1020kv - Yes...If you give it full throttle it will go to the moon.
Props are 10 x 4.7
ESC's 30 A Turnigy
Distance between motors is 27.5 inches
Overall weight with a 5000 mah battery is approx. 2lbs. Don't have a scale to weight it.
With the KKBoard on it...I have flown in 30 mph winds without much of a problem. She is kind of a tank. If you couldn't tell...I am still on cloud 9 after flying that sucker. Just soldered the plugs for sonar and putting her back together again.
If you follow the instructions above and use the zip file Don provided you will get them fixed.
Can this be fixed please... Both my tri are down and need get back to work..
Tri should be fixed in ArduCopter 2.3, now out in the Mission Planner.
Ross, (or anyone else with a Tri), can you have a look at this issue and see if you can replicate it on 2.3? I would do it myself but I'm not near my equipment.
I had pulled fresh 2.2b6 code from GIT last night right before the version increment, and still had the problem. I'm unsure if I got it before or after the changes committed by Pat, but looking through the code changes I don't see anything relevant to channel 7 out. (maybe I just missed it?)
I am still at work...but happy to do it when I get home.
I just verified it after getting my new motors and APM2560 installed.
Either the issue was not fixed, or it was unfixed when the changes that messed up hex and octo were reverted.