New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TriCopter: support servo with angle feedback to remove need to set YAW_SV_ANGLE #4294
Comments
This is quite an interesting enhancement. Has there been any development on implementing this sensor feedback? |
No a word. I am not a good coder but I bet if you look at at the triflight source code and port the control algorithm to Ardupilot it could work. Just beyond my abilities. |
@nmrdirtman @ChrisKrieg I have done a fix for this issue, It would be great if you could help me test it |
Hi there IamPete1... I have a tricopter under construction --- the same as described above by RCExplorer.se using but using a KakuteF7 AIO FC I would be very happy to thoroughly evaluate the performance of the servo feedback feature. Would you please advise how I can get hold of a firmware version with this feature for the Kakute F7 AIO v1.3? |
@doceave one build for Kakute F7 This is built on top of master, so it may be a little different if you have been flying stable. Set YAW_SV_PIN to the analog pin the feed back from the servo is connected to, RSSI pin is often used. Although I'm not sure what pin number that would be. Then set YAW_SV_SPEED to -1 to trigger a auto calibration. Have a look in the messages tab to see how it got on. You should then be good to fly. |
Many thanks indeed Peter!
I am happy to repeat the tri configuration. Perhaps I will make some
baseline recordings before implementation of tail servo feedback....
Please just confirm for me the process (I am but a simple end user of this
amazing software):
I update the firmware on the F7 using the .apj linked
I adjust the parameters YAW_SV_PIN and YAW_SV_SPEED using MissionPlanner
as you described
That's it!?
How is the file you link different from the latest .hex provided for the
Kakute F7?
Thanks
…On Thu, 02 Jul 2020, 14:46 Peter Hall, ***@***.***> wrote:
@doceave <https://github.com/doceave> one build for Kakute F7
<https://drive.google.com/file/d/1NqXTCk-rAsDAe64zqJ4P3oSIt--SilkT/view?usp=sharing>
This is built on top of master, so it may be a little different if you
have been flying stable. Set YAW_SV_PIN to the analog pin the feed back
from the servo is connected to, RSSI pin is often used. Although I'm not
sure what pin number that would be. Then set YAW_SV_SPEED to -1 to trigger
a auto calibration. Have a look in the messages tab to see how it got on.
You should then be good to fly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4294 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPBD3PKNJ4ZBTDM2J6VKDRZR6SPANCNFSM4CGGJ6AA>
.
|
@doceave Yep that's it, if you leave YAW_SV_SPEED at 0 then its just a old fashioned tricopter. The new params have a MOT_ prefix, so the full thing would be MOT_YAW_SV_SPEED MOT_YAW_SV_PIN, there are some voltage ones too, but they should be auto populated by the calibration. The .apj is exactly the same code as the .hex just packaged differently. Once you have uploaded a xxxx_with_bl.hex using betaflight configorator you then have the AP bootloader and can upload .apj's with Mission Planner. |
I think I'm almost good to go!
Any idea how I would find out the pin number used for RSSI by the FC?
The Kakute F7 has an STM32F745 at its core --- this has 3ADCs; but without
a schematic of the FC it would still be tricky to determine which GPIO is
connected to the RSSI pin on the board... ;)
Perhaps somone on this forum knows?
…On Thu, 02 Jul 2020, 16:41 Peter Hall, ***@***.***> wrote:
@doceave <https://github.com/doceave> Yep that's it, if you leave
YAW_SV_SPEED at 0 then its just a old fashioned tricopter. The new params
have a MOT_ prefix, so the full thing would be MOT_YAW_SV_SPEED
MOT_YAW_SV_PIN, there are some voltage ones too, but they should be auto
populated by the calibration.
The .apj is exactly the same code as the .hex just packaged differently.
Once you have uploaded a xxxx_with_bl.hex using betaflight configorator you
then have the AP bootloader and can upload .apj's with Mission Planner.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4294 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPBD2SPCHRR3PNDV23TCLRZSMA3ANCNFSM4CGGJ6AA>
.
|
@doceave Yeah worth a search on the forum, shouldn't take too long to just try a few, the RSSI_PIN param description gives the common ones. If you can work it out we should add it to the documentation, If not I have one here somewhere I can see If I can work it out. |
I endeavor to figure it out! :) There are only a handful of possibilities
according to the STM32F745 datasheet.
Will revert with an answer soon hopefully.
…On Thu, 02 Jul 2020, 17:52 Peter Hall, ***@***.***> wrote:
@doceave <https://github.com/doceave> Yeah worth a search on the forum,
shouldn't take too long to just try a few, the param description gives the
common ones. If you can work it out we should add it to the documentation,
If not I have one here somewhere I can see If I can work it out.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4294 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPBD3YJH6XRFDUKHVHCH3RZSULBANCNFSM4CGGJ6AA>
.
|
I have completed my tricopter build and tuned it up to the best of my ability with the time I had available --- slight low frequency tail wobble but tomorrow I hope to address this by tubing Yaw kP/I/D in flight... Sadly I have not managed to figure out the pin number associated with the RSSI pad on my FC, a Kakute F7 AIO v1.2 @IamPete1 --- Would you please call on your knowledgeable contacts to help me out re figuring out which pin to set as YAW_SV_PIN? I will then be able to make good comparison of flight characteristics achievable with and without feedback from the tail servo :) |
@doceave I had a trawl through the code, its pin 15 |
@IamPete1 ---- More than a year and some rebuilds later... Tricopter files nicely using the latest stable firmware without any servo feedback. There is, however, some tail wobble that is only bothersome when flying FPV. Would you kindly again provide me with link to firmware for the Kakute F7 AIO with servo feedback? This time I hope to actually implement it properly. Thanks. |
@IamPete1 Finally I built my mini tri! can probably just compile from a clone of your fork. However, I am not having much joy cherry picking that commit into my refeshed my fork of master. Here is what I get. Any ideas what the issue may be? $ git cherry-pick 1c9c179 |
@marcdornan I have rebased the branch. @doceave This is a Kakute F7 build https://drive.google.com/file/d/1N5RKUplQBa4Y_vTq-2GZhyARHIS95i8-/view?usp=sharing |
You are all wizards! :) |
@IamPete1 --- My tricopter has now returned for a 3rd time! This time around I endeavor to do some tail servo testing before the vehicle attempts an RTL through a mountain! Would you be willing to post a fresh link to a tricopter build with the servo angle feedback? Thanks. |
Issue details
Please describe the problem, or desired feature
Would like to make a request to consider adding dynamic yaw input from the yaw servo in a tricopter. Triflight ( https://github.com/lkaino/Triflight/releases ) uses this feed back data. Also RCExplorer.de sells a modified Blue Bird 210DMS servo with a feedback lead. http://rcexplorer.se/product/blue-bird-bms-210dmh-servo/ It uses a magnetic induction rotary encoder to know the rotor angle which can be used in calculations. This seems like a good idea. Please forgive me if its stupid or already address. I am willing to test.
Version
What version was the issue encountered with
Platform
[ ] All
[ ] AntennaTracker
[ x ] Copter
[ ] Plane
[ ] Rover
Airframe type
What type of airframe (flying wing, glider, hex, Y6, octa etc)
Hardware type
What autopilot hardware was used? (pixhawk, pixracer, PX4FMU etc)
Logs
Please provide a link to any relevant logs that show the issue
The text was updated successfully, but these errors were encountered: