summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rwxr-xr-xmanual/plugins/batterybenchmark.tex70
-rw-r--r--manual/plugins/main.tex2
2 files changed, 72 insertions, 0 deletions
diff --git a/manual/plugins/batterybenchmark.tex b/manual/plugins/batterybenchmark.tex
new file mode 100755
index 0000000000..0e05627287
--- /dev/null
+++ b/manual/plugins/batterybenchmark.tex
@@ -0,0 +1,70 @@
1\subsection{Battery Benchmark}
2The Battery Benchmark Plugin enables you to test your battery's performance,
3while making normal use of your \dap. Once loaded it will run in the
4background (TSR plugin), reading various info about your battery while you use
5it. Once you finish your session you can find the benchmark output data in a
6file on your \dap\ \fname{/battery\_bench.txt}.
7Please submit your results to the Rockbox wiki.
8\url{http://www.rockbox.org/twiki/bin/view/Main/BatteryRuntime}
9
10\subsubsection{How it works}
11After you load the plug-in the operation of your \dap\ continues as normal.
12You can do whatever you could do before loading the plugin except loading
13another plugin. If you happen to load a plugin while benchmarking, a splash
14screen will inform you about the termination of the benchmark.
15While you operate it will log various battery related information every time
16the disk is activated by external causes, (buffer refill, open folder,
17USB mode) or an hour passes without updating the log file.\\
18The plugin will continue to log info until:
19
20\begin{itemize}
21\item Another plugin is loaded.
22\item The \dap\ is shut down.
23\item The battery is empty.
24\end{itemize}
25Between disk activity (or an hour), it will log info in memory (every
26measurement is captured when the voltage changes). If there are too many
27measurements older entries will be deleted and the log file will inform the
28user about the interval where entries were lost. Benchmarks can be resumed if
29you accidentally load a plugin, or turn off your \dap, as long as the log
30file \fname{/battery\_bench.txt} is not deleted.
31
32\subsubsection{Information explained}
33On the top of the file you will see various info on how to use the plugin.
34\begin{description}
35\item[Time] It is the total time of operation of the \dap. It is not the time
36that you started the plug-in. If you have your player on for 5 minutes and then
37startt the plugin, it will start measuring from 5 minutes.
38\item[Seconds] As time, it shows time passed in seconds. Nothing special, it is
39there because it is free and maybe someone might want to make graphs with
40seconds.
41\item[Level] The percent level of the battery estimated by Rockbox. This is an
42estimation and not an accurate result. Using the real percentage (current
43battery voltage / top battery voltage) * 100) we can calculate the difference
44between the estimation. Goal of this column is to make the estimation algorithm
45of Rockbox more accurate.
46\item[Time Left] It shows the estimated (by Rockbox) remaining time until
47shutdown. Again, as Level, this column can be used to see differences between
48real time left and estimated time left. This could help make time left more
49accurate.
50\item[Voltage] The current, battery voltage, the moment the measurement was
51captured. Measurements are captured when this number changes while benchmarking.
52This column can be used to give quite interesting graphs in a spreadsheet
53program. (Excel, Calc, e.t.c)
54\item[M/DA] (Measurements per Disk Activity) The number of measurements stored
55temporarily in memory, before written on the log file. This can give you an
56idea on how many voltage changes are between disk activity (or one hour).
57\item[C] Stands for Charger. An "A" in that column shows if there was the power
58adapter attached to the unit, at the time of the measurement.
59\item[S] The "S" column shows the state of the device (Charging, or not). The
60"C" indicated that the unit was charging when the measurement was captured.
61\item[U] USB powered. Only for targets that support this. A "U" will indicate
62if the unit was using the USB port for powering.
63\end{description}
64
65\subsubsection{Making graphs}
66While you can tell how long your battery lasted, with a single look at the last
67line of the battery log (\fname{/battery\_bench.txt}), the most useful purpose of
68Battery Benchmark is to make graphs using a spreadsheet program like Excel or
69Calc. The battery log (\fname{/battery\_bench.txt}) is in CSV format (comma separated)
70so you can quite easily import it to a spreadsheet program.
diff --git a/manual/plugins/main.tex b/manual/plugins/main.tex
index 2da1180b37..8f568880e6 100644
--- a/manual/plugins/main.tex
+++ b/manual/plugins/main.tex
@@ -122,6 +122,8 @@ the associated file. Viewers are stored in the
122 122
123\section{Applications} 123\section{Applications}
124 124
125{\input{plugins/batterybenchmark.tex}}
126
125\opt{recorder,recorderv2fm,ondio,h1xx,h300,ipodcolor,ipodnano}{\input{plugins/battery_test.tex}} 127\opt{recorder,recorderv2fm,ondio,h1xx,h300,ipodcolor,ipodnano}{\input{plugins/battery_test.tex}}
126 128
127\opt{recorder,recorderv2fm,ondio,h1xx,h300,ipodcolor,ipodnano}{\input{plugins/calculator.tex}} 129\opt{recorder,recorderv2fm,ondio,h1xx,h300,ipodcolor,ipodnano}{\input{plugins/calculator.tex}}