-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Move servo from S1 to S6 pin for MATEKF405 #2954
Conversation
Please don't break my existing tri-copters. We've been through this before. |
Oh, sorry. |
It would have to be another target. I agree this is really inconvenient one way or the other. The way the MATEKF405_OSD is a "fork" of the MATEKF405 target. |
Thank you, now I understood. |
I have MATEK-OSD on one, and MATEK-STD on the other. |
All right, let's think about how these targets can be separated.
The question is: do we need to create separate targets for all of these boards? |
Another option is to create MATEKF405_SERVOS5 or MATEKF405_SERVOS1 target. |
This is not a particularly helpful target name, as it may confuse tricopter users with a MATEKF405-STD board. Perhaps MATEKF405FW would be an alternative? |
I can explain, It's not for fixedwing, it's for quadcopter users like me, who need S1..S4 for motors and S5 or S6 for camera-tilt servo. |
OK, but it's still confusing to name it for a particular FC when it's a servo configuration setting across multiple FCs (F405, F405CTR, F405STD). |
And however the variant is named, the Boards documentation file will need to be updated, to avoid further user confusion. |
Ok, I agree. Thank you for reminding me of documentation. |
We have a winner! In fact, I think your solution is the correct one, and the initial setup was a mistake (with the benefit of hindsight, of course). In a perfect world, we would rename the original target to MATEKF405_LEGACY and call your solution MATEKF405, but that might just be too confusing (even if it's my preferred outcome). |
Let's create a SERVOS6 target and see some usage statistics. Then we could make a decision renaming them |
merging per @digitalentity's advice |
Thank you for your work @alexeystn. I believe that this is exactly what I am looking for. I've posted a comment on RCGROUPS that explains some problems I'm having. Here is the text - Subject flight controller with S6 pad connected to tilt servo, running development (@alexeystn ) MKF4 firmware dtd Apr 6. SERVO_TILT feature is active. In INAV servo tab I can successfully attach the servo0 to a flight control output but am unable to get a servo mix that will add stabilized pitch. Also, changing rates to negative does not appear to change servo direction. versionINAV/MATEKF405_SERVOS6 1.9.1 Apr 6 2018 / 10:23:25 (7332ceb)resourcesmixermixer QUADX mmix reset servo mixsmix reset smix 0 0 1 100 0 servoservo 0 1000 2000 1500 -124 1 featurefeature -RX_PPM beeperbeeper RUNTIME_CALIBRATION mapmap AETR namename - serialserial 20 1 115200 38400 0 115200 ledled 0 0,0::C:0 colorcolor 0 0,0,0 mode_colormode_color 0 0 1 auxaux 0 0 0 1775 2100 adjrangeadjrange 0 0 0 900 900 0 0 rxrangerxrange 0 1000 2000 masterset looptime = 1000 profileprofile 1 set mc_p_pitch = 72 |
My bad. I neglected to enable CAMSTAB. This works great for pitch stabilization - even with a small 9g servo. thanks! |
When SERVO_TILT is enabled, servo signal goes to S1 output. Motor 1 stops working therefore.
Now servo can be attached to S6 output of MatekF405:
feature SERVO_TILT
servo 0 1000 2000 1500 100 8
#2644