Skip to content
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

Global Persistent Timer #4950

Closed
CraigHB opened this issue May 23, 2017 · 13 comments · Fixed by #4985
Closed

Global Persistent Timer #4950

CraigHB opened this issue May 23, 2017 · 13 comments · Fixed by #4985

Comments

@CraigHB
Copy link

CraigHB commented May 23, 2017

There's no simple way I can find to create a persistent global timer that runs whenever the transmitter is on. Would like to be able to keep track of how long the radio runs on a charge. Any persistent timers created using a model revert to the last time recorded with that model active so it can't be done there. Running Companion on Windows OS, OpenTX version 2.2.0 N371.

@kilrah
Copy link
Member

kilrah commented May 23, 2017

Radio type?

@CraigHB
Copy link
Author

CraigHB commented May 24, 2017

Taranis Q X7

@kilrah kilrah added this to the OpenTX 2.2.X milestone May 28, 2017
@rdeanchurch
Copy link

rdeanchurch commented May 28, 2017

A nice feature. It could also be used for the total time the Tx has been used.
If there was an EVENT for power off button depressed and maybe a Function script could write this data to the SD....given some processing time after EVENT _POWER_OFF button detected. The delay for power off seems like more than enough time would be available.
This could also be expanded to include a log for each models selected time.
(the model log could be implemented now, I believe, for all except the last model, before the supposed EVENT _POWER_OFF.)

@jj604
Copy link

jj604 commented May 29, 2017

Kilrah, can I just comment that IMO it would be good to have a "simple" option exactly as CraigHB requested however in addition to any more powerful functionality. Not many users will be into scripting while all might find a "Time since last charge" useful. Both my original DX8 and my 10 year old Cockpit SX have such a manually resettable timer. Thanks. John

@mpjf01
Copy link

mpjf01 commented May 29, 2017

There presumably is a reason why only the QX7 is indicated as the enhancement target? From the discussion on RCG that prompted the request it would seem that it is desired on all platforms.

@kilrah
Copy link
Member

kilrah commented May 29, 2017

All platforms already have a global running timer. It's simply not displayed anywhere on the X7 (and other 128x64 ARM platforms) and this is about adding it in the UI. Nothing to do with Lua or anything advanced, please open separate issues for that (there might even already be one).

@3djc 3djc self-assigned this May 29, 2017
@3djc 3djc modified the milestones: OpenTX 2.2.1, OpenTX 2.2.X May 29, 2017
@3djc
Copy link
Contributor

3djc commented May 29, 2017

There is a timer responding to requirement of : " keep track of how long the radio runs on a charge.". On x9 for example, it is shown in statistics, and can be reset on demand by long menu press.

There is no UI for it (yet) on x7, that's what we will be adding

@mpjf01
Copy link

mpjf01 commented May 29, 2017

Thanks. What is SES - is it Session? My TOT showed a value of 15C9:26 or something before I reset it, what is the upper limit of this timer?

@3djc
Copy link
Contributor

3djc commented May 29, 2017

It is a manual triggered thing, so you can use it to track whatever you want

@CraigHB
Copy link
Author

CraigHB commented May 29, 2017

Excellent, is there a way to find out when this will be added so I can make use of it?

@3djc
Copy link
Contributor

3djc commented May 29, 2017

Not before 2.2.1, as can been seen in the milestone setting

@CraigHB
Copy link
Author

CraigHB commented May 29, 2017

So do I check a change log on 2.2.1 to find out if it's there?

@kilrah
Copy link
Member

kilrah commented May 29, 2017

This issue will be closed when it's added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants