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

Indication that LIST is running with long DWELl times #99

Closed
prasimix opened this issue Apr 3, 2017 · 3 comments
Closed

Indication that LIST is running with long DWELl times #99

prasimix opened this issue Apr 3, 2017 · 3 comments
Assignees
Milestone

Comments

@prasimix
Copy link
Member

prasimix commented Apr 3, 2017

We need some sort of indication that programmed output values are in fact set using LIST in case of long DWELl times what is currently not apparent in any sense. The real case scenario is battery charging when DWELl time for set current could last up to 14 hours (over 50 000 seconds). Optimal solution could be that we add some sort of down counter that will be visible when DWELl time is longer then e.g. 5 seconds. Question is where to place it? Maybe it's time that we start to use upper line now reserved for error and warning messages only for this and some other things.

@prasimix prasimix added this to the M5 milestone Apr 3, 2017
@prasimix prasimix changed the title Inducation that LIST is running with long DWELl times Indication that LIST is running with long DWELl times Apr 3, 2017
@prasimix prasimix modified the milestones: v1.0, M5 Apr 19, 2017
mvladic added a commit that referenced this issue May 5, 2017
@prasimix
Copy link
Member Author

Add channel number before displayed time. Use e.g. 0x0041, 0x0042 or 0x0061, 0x0062 pair.

digits.zip

@prasimix
Copy link
Member Author

prasimix commented May 15, 2017

Another possibility (not a real substitute for previous comment) is to display step number, e.g. if step 2 has long DWELl time then format should be: 2:45s or 2>45s

@prasimix
Copy link
Member Author

Fixed, last two comments ignored.

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

No branches or pull requests

2 participants