The following directory is interesting for watching the battery
behavior:
/sys/class/i2c-adapter/i2c-1/1-0010
Code:
--------------------
. alarm_time input:input2
.. ambient ir
adc_0 battery_capacity kill
adc_1 battery_charge modalias
adc_10 battery_charge_rate msp_buffer
adc_11 battery_disable name
adc_12 battery_discharge_rate power_mode
adc_13 battery_temperature rtc:rtc0
adc_14 battery_vmon1_voltage subsystem
adc_15 battery_vmon2_voltage sys_voltage
adc_2 battery_voltage test_1
adc_3 bus test_2
adc_4 charger_event test_4
adc_5 charger_state test_8
adc_6 driver time
adc_7 flash uevent
adc_8 fw wall_voltage
adc_9 gp_register
--------------------
You can find out how some of the readings are interpreted by looking
in:
/usr/share/jive/applets/Diagnostics/DiagnosticsApplet.lua
/usr/share/jive/applets/SqueezeboxBaby/SqueezeboxBabyApplet.lua
But some values like battery_charge_rate (10) aren't used in the lua
files and don't have meanings that are obvious to me. It appears to be
using at TI MSP430 microcontroller. Here is some info on charging
options with the MSP430:
http://focus.ti.com/lit/ml/slap106/slap106.pdf
http://focus.ti.com/lit/ug/sluu369/sluu369.pdf
http://focus.ti.com/lit/an/slaa287/slaa287.pdf (has some MSP430 C
code)
I'm probably going to set up a remote syslogd so I can dump battery
stats regularly (every 10 seconds say) and graph them to understand the
charging characteristics.
-Jeff
--
jdoering
------------------------------------------------------------------------
jdoering's Profile: http://forums.slimdevices.com/member.php?userid=17482
View this thread: http://forums.slimdevices.com/showthread.php?t=75056
_______________________________________________
Radio mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/radio
