- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 432
feat: MT12 servo pulse #6528
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
base: main
Are you sure you want to change the base?
feat: MT12 servo pulse #6528
Conversation
d4e276a    to
    ce49372      
    Compare
  
    | Is there scope / room for this to be added as an actual output in the future (not necessarily in this PR!), thus allowing for model specific use of the port? This is how I thought it was supposed to implemented right from day one - i.e. be able to in a model configure mixer to control the PPM port. Which to be honest is why I don't like either implementation (if it is to be the only one)... while this is the better one, as it really shouldn't have been "hidden" on the hardware page as one use case is more of a tool - the other being to provide an easily pluggable PPM port for accessories/modules. | 
| That was the intention of my original design. This tool approach doesn't allow you to use it to plug say your steering servo and adjust outputs, since you would have to back out of tools, the outpiut would stop, change output settings, back into tools, not quite right yet, out of .. you get the idea.This tool approach really severly limits the use of it The way it was initially proposed and refused did allow you to choose a channel you don't use for RF output, and then you can use it differently per model using the mixer. | 
| Maybe I am/was just missing the imagination for the actual use-case. I was thinking about a simple servo tester. You guys seem to have something much broader in mind, right? That being said, I'm still not convinced we need a persistent setting here. The tool could however be made to keep the PWM output "open" when leaving the screen. Would that make it more useful? (while still keeping it dead simple) | 
| I think persistancy is required for some (yes, more exotic) usage. I have no preferences between radio or model setting | 
| 
 Any idea what that could be? What kind of accessories/modules? | 
| At the moment, nothing specific, but this is always a chicken and the egg
scenario... if we don't make it available, it can't happen, but how do we know what to make available (and have the capacity to implement?😂). This is why I
queried as to "room in the futurel?"
But on second thoughts (as the DSC port is right there next to it and is
more configurable, but crucially does not also provide power), perhaps all that would be needed is that the tool
should be persistent once it is configured (as IMO it being persistent from
only when it is opened for that session only is just stupid/not intuitive
at all... i.e. if I configure it, I want it to either work while I'm at
that screen or always work until I say otherwise). If adding that
persistence in a future PR is trivial given the current implementation,
I'll have to try this out first for final feedback, but in principal I see
no reason to not leave this in this form, and see if there is enough demand
to take it further.… On Wed, 20 Aug 2025, 1:26 am Raphael Coeffic, ***@***.***> wrote:
 *raphaelcoeffic* left a comment (EdgeTX/edgetx#6528)
 <#6528 (comment)>
 provide an easily pluggable PPM port for accessories/modules
 Any idea what that could be? What kind of accessories/modules?
 —
 Reply to this email directly, view it on GitHub
 <#6528 (comment)>, or
 unsubscribe
 <https://github.com/notifications/unsubscribe-auth/ABJ66KK3YQ4QWKVCIRVHFUL3OM6ZNAVCNFSM6AAAAACEE7GDJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMBRGIYTSNRRHA>
 .
 You are receiving this because you commented.Message ID:
 ***@***.***>
 | 
| Ok, so just leaving the output working when leaving the tool would be sufficient for now? That would at least cover the "servo tester" use case without having to stay on that screen, right? I'd need to find a non-invasive way to keep updating the output. ATM, this is done during screen refresh, which dead simple and does not require anything outside this one tool file. | 
| Probably for the present time, I'd just leave it as it is... as a tool, as I said before, I don't see it making sense it being persistent/active once you leave the screen, unless there is a specific setting to turn it on (and conversely off) persistently without going to the tool page. i.e. no different to the spectrum analyser. And wait for feedback to see if anyone actually wants more. This more of a "have you thought about if it gets extended this way" prompt ;) Note that I haven't even started on the where are the end points, update rate, manual/centre/sweep, etc options as I get that those will come later ;) Hm... the "PWM output" line should probably be "Source" ... you're configuring the source for the PWM output, not where it's going ;) | 
ce49372    to
    09d2c25      
    Compare
  
    
Follow-up of #6527 as a "Tool" (similar to spectrum analyser).