Editing Bme replacement
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 14: | Line 14: | ||
.debs are available from: | .debs are available from: | ||
- | + | https://atrey.karlin.mff.cuni.cz/~pali/rx51-bme-replacement/ | |
- | + | (might need to ignore expired certificate) | |
It works for everyday usage, but some major problems were found, see below. | It works for everyday usage, but some major problems were found, see below. | ||
- | |||
- | |||
- | |||
- | |||
=Problems/bugs and proposed solutions= | =Problems/bugs and proposed solutions= | ||
Line 32: | Line 28: | ||
'''1. gconf value''', that allow power users to change voltage, at which device shutdowns to any arbitrary value. | '''1. gconf value''', that allow power users to change voltage, at which device shutdowns to any arbitrary value. | ||
- | This is | + | This is preffered solution, as some devices are more like to have problems with GSM chip restarting at low voltage, even around '''EDV1''' 3248 mV. People with such problems, that preffer GSM stability over calibration, could bump voltage treeshold, to avoid problems. OTOH, people with less picky devices and/or dual-cell setups, could decrease limit, getting more from their batteries. |
- | This method can be also augmented by solution 2, for "default" shutdown | + | This method can be also augmented by solution 2, for "default" shutdown treeshold. |
- | '''1.a gconf value plus guard time''' use a timer plus frequent probing to ensure the voltage stays below the threshold set by gconf. This is the recommended method since the whole shutdown shouldn't get triggered by sub-second "brownouts" caused by power consumption spikes. A suggested guard time is 30..60s, a suggested sampling frequency for voltage is 1/s, though the hardware has limited support for such high sampling frequencies of voltage - further evaluation needed. Other alternative concepts like average over moving window (again | + | '''1.a gconf value plus guard time''' use a timer plus frequent probing to ensure the voltage stays below the threshold set by gconf. This is the recommended method since the whole shutdown shouldn't get triggered by sub-second "brownouts" caused by power consumption spikes. A suggested guard time is 30..60s, a suggested sampling frequency for voltage is 1/s, though the hardware has limited support for such high sampling frequencies of voltage - further evaluation needed. Other alternative concepts like average over moving window (again widow size: 300..60s) might be worth to consider. |
Note that the high sampling frequency is only needed during the guard time. For moving window average this complicates the design a fair bit. | Note that the high sampling frequency is only needed during the guard time. For moving window average this complicates the design a fair bit. | ||
Line 46: | Line 42: | ||
'''EDV1''' flag can be read from ''/sys/class/power_supply/bq24150a-0/registers'' address 0x55 0x0A, divided by 2. | '''EDV1''' flag can be read from ''/sys/class/power_supply/bq24150a-0/registers'' address 0x55 0x0A, divided by 2. | ||
- | '''2.a''' In case of '''EDV1''' flag being not available'''*''', fallback to using 3150 mV as shutdown | + | '''2.a''' In case of '''EDV1''' flag being not available'''*''', fallback to using 3150 mV as shutdown treeshold. Rationale: 3150 mV shouldn't cause GSM chip restarts on devices, where 3248 mV haven't caused it already. |
It doesn't guarantee calibration, as it require 15 seconds *straight* below 3248 mV (EDV1 voltage), and 3150 mV might be just momentary low voltage spike. But, it is better than current implementation, which permits calibration *ever* - and, after all, it is just theoretical fallback for hyphotetical, non-existing kernel. | It doesn't guarantee calibration, as it require 15 seconds *straight* below 3248 mV (EDV1 voltage), and 3150 mV might be just momentary low voltage spike. But, it is better than current implementation, which permits calibration *ever* - and, after all, it is just theoretical fallback for hyphotetical, non-existing kernel. |
Learn more about Contributing to the wiki.