@t
Member level 3
Hello Dexter Dude,
This applies only if you've got some space left in program mem. of course..
Have you ever thought of doing some kind of "health" check on a battery, after it is charged up? Without using extra buttons, you could do a discharge for a fixed time (maybe 5 or 10secs) and translate the resulting drop in voltage into a number for display, to get a relative indication of how good the battery holds the charge.
If this action also is performed at start-up, you could check at any moment, and then abort the rest of the proces (by removing the battery).
For a better (time consuming) check, a suspected battery could be left in the charger and (after charging) this "drop" check could be repeated every hour automaticly (and recorded).
This way the batteries can be labeled with a (quality) number (9 to 1) and the 'lesser good' ones will get sorted out.
You did a nice job, greetings, At.
This applies only if you've got some space left in program mem. of course..
Have you ever thought of doing some kind of "health" check on a battery, after it is charged up? Without using extra buttons, you could do a discharge for a fixed time (maybe 5 or 10secs) and translate the resulting drop in voltage into a number for display, to get a relative indication of how good the battery holds the charge.
If this action also is performed at start-up, you could check at any moment, and then abort the rest of the proces (by removing the battery).
For a better (time consuming) check, a suspected battery could be left in the charger and (after charging) this "drop" check could be repeated every hour automaticly (and recorded).
This way the batteries can be labeled with a (quality) number (9 to 1) and the 'lesser good' ones will get sorted out.
You did a nice job, greetings, At.