Closed lakemurrybc closed 3 years ago
The misspelling is definitely an issue.. not sure about the voltage - I'll hook one up when the kid goes to sleep and verify
I’ve noticed the same voltage measurement on mine when powered externally. Just assumed it was due to the Ferm.
This is a comment I received from Pico Brew in 2019: Yes, when using the usb it won't accurately report battery power... Seems the Picoferm will not report power when on an external supply.
Just pushed a fix for the spelling error & captured 2 logs (one on battery, one on usb):
127.0.0.1 - - [07/Mar/2021 11:19:09] "GET /API/PicoFerm/logDataSet?uid=xxxxxxxxxxxx&rate=5&voltage=3.16&data=[{"s1":67.36,"s2":0.00},{"s1":67.53,"s2":0.00},{"s1":67.86,"s2":0.00},{"s1":68.00,"s2":0.00},{"s1":68.01,"s2":0.00},{"s1":68.09,"s2":0.00},{"s1":69.68,"s2":0.00},{"s1":74.28,"s2":0.00},{"s1":74.47,"s2":0.00},{"s1":75.42,"s2":0.00}] HTTP/1.0" 200 -
127.0.0.1 - - [07/Mar/2021 12:23:32] "GET /API/PicoFerm/logDataSet?uid=xxxxxxxxxxxx&rate=5&voltage=0.03&data=[{"s1":75.24,"s2":0.00},{"s1":74.61,"s2":0.00},{"s1":74.18,"s2":0.00},{"s1":73.89,"s2":0.00},{"s1":73.71,"s2":0.00},{"s1":73.57,"s2":0.00},{"s1":73.44,"s2":0.00},{"s1":73.31,"s2":0.00},{"s1":73.19,"s2":0.00},{"s1":73.08,"s2":0.00},{"s1":73.02,"s2":0.00},{"s1":73.00,"s2":0.00}] HTTP/1.0" 200 -
Looks like an arbitrary (or .03V) is expected when not running on battery.
Thanks for all the hard work.
On Mar 7, 2021, at 2:52 PM, Pete notifications@github.com wrote:
Just pushed a fix for the spelling error & captured 2 logs (one on battery, one on usb):
127.0.0.1 - - [07/Mar/2021 11:19:09] "GET /API/PicoFerm/logDataSet?uid=xxxxxxxxxxxx&rate=5&voltage=3.16&data=[{"s1":67.36,"s2":0.00},{"s1":67.53,"s2":0.00},{"s1":67.86,"s2":0.00},{"s1":68.00,"s2":0.00},{"s1":68.01,"s2":0.00},{"s1":68.09,"s2":0.00},{"s1":69.68,"s2":0.00},{"s1":74.28,"s2":0.00},{"s1":74.47,"s2":0.00},{"s1":75.42,"s2":0.00}] HTTP/1.0" 200 - 127.0.0.1 - - [07/Mar/2021 12:23:32] "GET /API/PicoFerm/logDataSet?uid=xxxxxxxxxxxx&rate=5&voltage=0.03&data=[{"s1":75.24,"s2":0.00},{"s1":74.61,"s2":0.00},{"s1":74.18,"s2":0.00},{"s1":73.89,"s2":0.00},{"s1":73.71,"s2":0.00},{"s1":73.57,"s2":0.00},{"s1":73.44,"s2":0.00},{"s1":73.31,"s2":0.00},{"s1":73.19,"s2":0.00},{"s1":73.08,"s2":0.00},{"s1":73.02,"s2":0.00},{"s1":73.00,"s2":0.00}] HTTP/1.0" 200 - Looks like an arbitrary (or .03V) is expected when not running on battery.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Since the device can't possibly run under 2v, we could detect this as "running on power" and reflect that in the UI. Or at leave change it to 5V so it's sane :)
I'd say detecting "external power" or "constant power" would be a nice improvement to explain what is going on here. Not sure why PB choose to emit that specific voltage "reading".
This I very minor but I thought I would let you know. It looks like the Voltage value may have the decimal point in the wrong place. Mine is showing 0.03 volts and I am on a 5 volt supply but that may show as 3 volts to match the 2 AA batteries it was designed for. Additionally, Voltage is spelled wrong. See attached.