EdgeTX
Better and more timers
Is there an existing issue for this feature request?
- [x] I have searched the existing issues
Is your feature request related to a problem?
Posted this on RCGroups but seems it went under in a useless fight... : bumped into something strange ( not really a bug) in Edge TX 2.10.6 : In the manual I read this :
Throttle - The timer starts once the throttle is raised and the configured switch is activated. The timer will stop counting if either the throttle position is lowered back to the minimum value or the configured switch is deactivated.
Throttle % - The timer counts proportionally to the throttle. It counts in real time at full throttle and at half speed at 50% throttle.
Throttle Start - The timer starts once the throttle is raised and the configured switch is activated. After starting, the timer ignores the throttle position and will keep counting unless the switch is deactivated
When "programming" my timer(s) I supposed THs was Throttle Start and THt Throttle. This does not seem to be the case !
I had to use THt to get this behaviour : The timer starts once the throttle is raised and the configured switch is activated. After starting, the timer ignores the throttle position and will keep counting unless the switch is deactivated
So not really a big problem but it gave me a headache trying to understand how the timers work, a bit surprised nobody seems to have mentioned this. Apparently it already existed in 2.9. I had to use Throttle start because that is the only way I could use a different switch to stop the timer. I think it would be easier if all timers could have a start and a stop switch ( My PL18 timers use 3 switches : Start, Stop and Reset). And I could use a 4th timer....
Describe the solution you'd like
- Swap the behaviour from THt and THs. In my logic, s would be start and t Throttle.
- If possible, add start and stop switches to all timers.
- If possible, add a 4th timer
Describe alternatives you've considered
I am using THt when I want Throttle Start behaviour...
Additional context
No response
Given you are referencing the short form, it sounds like you are on a B&W screen radio?
Thus, this is the correct documentation => https://manual.edgetx.org/bw-radios/model-select/setup#timers
OFF - The timer is not used
ON - The timer runs all the time
Strt (Start) - The timer starts once the configured switch is activated. After the time is started, the timer ignores the switch position.
THs (Throttle) - The timer starts once the throttle is raised and the configured switch is activated. The timer will stop counting if either the throttle position is lowered back to the minimum value or the configured switch is deactivated.
TH% (Throttle %) - The timer counts proportionally to the throttle. It counts in real-time at full throttle and half speed at 50% throttle.
THt (Throttle Start) - The timer starts once the throttle is raised and the configured switch is activated. After starting, the timer ignores the throttle position and will keep counting unless the switch is deactivated.
Given it has been this since the OpenTX days, so also every single version of EdgeTX, I don't think this will (or should) change any time soon, but certainly not a straight swap, as that would just be confusing for everyone.
If possible, add start and stop switches to all timers.
While it might be debatable whether this is actually need (given you can craft LS/SF or lua tools) to do what you want there, I think it makes more sense to have the timer stuff all together and "complete".
If possible, add a 4th timer
Not just yet, but might be a part of 3.0 given the opportunity to redo some stuff, and lifting of some of the resource constraints.
IMHO the current mnemonics for timer setup are correct. Think of "Throttle triggered" for "THt" and "Throttle set" for "Ths", which describes the function correctly. Also, no use for a 4th timer here, but your milage may vary...
Thanks pfeerick for clearing this up for me. Icebreker-ch I disagree about the mnemonics though , unless Strt (Start) is called Thtr (please do not change!) I have a solution for not needing the 4th timer for what I want to do, but I do not really like it, I'll keep trying..
Timers Timer 1/2/3 - There are 3 configurable timers in EdgeTX. The following configuration options will be displayed once the timer is no longer set to OFF:
Timer 1 [Mode] [Switch] [Mode] - The options include: ...
Strt (Start) - The timer starts once the configured switch is activated. After the time is started, the timer ignores the switch position.
THs (Throttle) - The timer starts once the throttle is raised and the configured switch is activated. The timer will stop counting if either the throttle position is lowered back to the minimum value or the configured switch is deactivated.
TH% (Throttle %) - The timer counts proportionally to the throttle. It counts in real-time at full throttle and half speed at 50% throttle.
THt (Throttle Start) - The timer starts once the throttle is raised and the configured switch is activated. After starting, the timer ignores the throttle position and will keep counting unless the switch is deactivated.
I still think THS and THt should be swapped, but since it apparently has been like this since Open TX already I can understand it is not likely to be changed... I'll (reluctantly) live with it...
While it might be debatable whether this is actually need (given you can craft LS/SF or lua tools) to do what you want there,
What are the lua functions that start and stop timers? I've looked a bit and never found anything. You can get a timer and reset a timer but I haven't found a set or stop function. It would be nice to know if this was possible.
You can't AFAIK - start/stop condition for a firmware provided timer is expected to be based on the conditions you set for the timer. For Lua, I was referring the possibility of being able to create your own timers, managed and tracked via that Lua tool/widget - i.e. programming the timers entirely in Lua, rather than use the ones provided by the firmware. You can only directly get, set and reset firmware provided timers via Lua.