| 00:26.12 | arossdotme | looks like it's ok to use li-ion charges with li-po |
| 00:26.44 | arossdotme | so whats the darn vottage to let to dischage to before the cut off point? |
| 00:26.57 | arossdotme | let it discharge too |
| 00:27.13 | arossdotme | it's hard to find itfo |
| 00:46.26 | *** join/#qi-hardware porchaso0 (~quassel@218.231.187.25.eo.eaccess.ne.jp) |
| 01:27.05 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.53) |
| 01:45.16 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 01:48.50 | arossdotme | looks like lowbat is 3.2v according to adafruit's low batt led on there products |
| 01:58.35 | *** join/#qi-hardware archang (~archang@111.198.29.54) |
| 02:15.23 | *** join/#qi-hardware dandon (~dandon@88.151.79.206) |
| 02:21.08 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 02:52.09 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 03:28.43 | *** join/#qi-hardware qi-bot4 (~qi-bot@turandot.qi-hardware.com) |
| 03:29.09 | *** mode/#qi-hardware [+o qi-bot] by ChanServ |
| 03:31.01 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d36:0:18a9:1888:bb6c:5ae9) |
| 03:44.02 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.54) |
| 04:19.33 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 04:31.20 | DocScrutinizer05 | arossdotme: I'd rather use 3500mV aka 3.5V |
| 04:31.58 | DocScrutinizer05 | LiIon (incl LiPo) chemistry suffers *massively* from deep discharge |
| 04:32.40 | DocScrutinizer05 | 3.00V is the ABS MAX deep discharge where you're supposed to dicard the cell safely when ever crossing that line |
| 04:32.50 | DocScrutinizer05 | aiui |
| 04:35.30 | DocScrutinizer05 | anyway >>90% of the available capacity of a LiIon standard chemistry cell are in a discharge voltage range between 4200mV and down to 3550mV |
| 04:35.51 | DocScrutinizer05 | I'd not charge the cell to >4100mV either |
| 04:38.51 | DocScrutinizer05 | those designs that use 4200mV-3200mV or even lower, are made for maximum effect in time of sale, not bothering at all about expected livespan of product / battery. A careully gently managed battery can live >7 years, while those "max perfomance" designs calculate with a battery livespam of < 2 years |
| 04:39.01 | DocScrutinizer05 | oftem < 1 year |
| 04:44.21 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.53) |
| 06:45.04 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-107.telecom.by) |
| 06:53.56 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d36:0:18a9:1888:bb6c:5ae9) |
| 07:06.34 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 08:00.09 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 08:27.25 | *** join/#qi-hardware tumdedum (~tumdedum@unaffiliated/espiral) |
| 08:45.28 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 09:07.57 | *** join/#qi-hardware sb0 (~lekernel@APuteaux-651-1-205-49.w92-154.abo.wanadoo.fr) |
| 09:51.33 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 10:52.24 | *** join/#qi-hardware Haswell (~broaderba@unaffiliated/haswell) |
| 10:55.05 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 10:55.26 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 11:17.10 | *** join/#qi-hardware jekhor (~jek@port-129-adslby-pool36.infonet.by) |
| 11:18.46 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 11:48.06 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 12:10.26 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 12:13.34 | arossdotme | DocScrutinizer thx iw ould like max batt life span, |
| 12:14.11 | arossdotme | the chrager is setup to charge upto 4.19v if i'm not missing out the 3rd digect |
| 12:14.27 | DocScrutinizer05 | then use 3.55 .. 4.1V (dis)charge cycle limits |
| 12:14.40 | arossdotme | which i realise now the 3rd digect makes a diff when talking about it |
| 12:14.41 | arossdotme | ok |
| 12:15.35 | arossdotme | the min vottage in the sys power info is something like 4.7something |
| 12:15.38 | DocScrutinizer05 | 4.15 is maybe still ok, 4.2 is pushing it quite a bit |
| 12:16.01 | arossdotme | ok |
| 12:16.07 | DocScrutinizer05 | 4.7 doesn't make sense |
| 12:16.26 | arossdotme | i'mm ignore that vaule then |
| 12:16.30 | arossdotme | i'll |
| 12:16.32 | DocScrutinizer05 | 4.7 sounds like min USB VBUS voltage |
| 12:18.53 | arossdotme | my bad |
| 12:19.12 | arossdotme | its 3475000v |
| 12:22.15 | arossdotme | it's hardware charged |
| 12:22.34 | arossdotme | i'm just refering to the sys files the batt monitors use |
| 12:23.06 | arossdotme | but i now have a better idea of what votage to dischage too before rechage |
| 12:59.23 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 13:28.08 | *** join/#qi-hardware atommann (~atommann@222.248.72.156) |
| 14:24.33 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 14:24.33 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 14:24.33 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 15:04.21 | *** join/#qi-hardware sb0 (~lekernel@murphy.electrolab.fr) |
| 15:27.13 | DocScrutinizer05 | 3475000µV sounds like a reasonable End of Discharge Voltage |
| 15:44.49 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 16:09.43 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 16:19.15 | *** join/#qi-hardware jekhor_ (~jek@port-129-adslby-pool36.infonet.by) |
| 16:24.51 | *** join/#qi-hardware jekhor__ (~jek@port-129-adslby-pool36.infonet.by) |
| 16:33.06 | *** join/#qi-hardware jekhor (~jek@port-69-adslby-pool38.infonet.by) |
| 16:35.10 | arossdotme | EDV so thats what its called |
| 16:35.31 | arossdotme | thx |
| 16:50.58 | eintopf | in german: electronische datenverarbeitung |
| 16:51.05 | eintopf | s/elec/elek/ |
| 16:51.05 | qi-bot | eintopf meant: "in german: elektronische datenverarbeitung" |
| 16:51.17 | eintopf | qi-bot: thanks |
| 16:59.28 | eintopf | http://www.libreboot.org/docs/install/images/x200/x200_pomona.jpg - what's the name of such blue connector? |
| 17:00.44 | eintopf | oh, I need such connector |
| 17:08.44 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 17:12.53 | eintopf | Pomona 5250 |
| 17:12.57 | eintopf | that's the name |
| 17:15.21 | eintopf | very expensive |
| 17:16.18 | *** join/#qi-hardware Haswell (~broaderba@unaffiliated/haswell) |
| 17:41.35 | *** join/#qi-hardware kyak (~kyak@128-72-36-237.broadband.corbina.ru) |
| 17:41.35 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 17:56.52 | kristianpaul | wpwrak: had you looked the msp432? |
| 17:59.03 | *** join/#qi-hardware sb0 (~lekernel@murphy.electrolab.fr) |
| 18:06.29 | wpwrak | kristianpaul: not really. yet another vendor-specific architecture, much like avr. why build on this if we can have nice arm-based MCUs, from so many different sources ? |
| 18:07.57 | kristianpaul | well, just thinking on the power comsuption could be not as low as the msp430 but interesting |
| 18:08.20 | kristianpaul | to be honest the only 32 bits mcu i can get here is fro microchip :D |
| 18:08.43 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 18:19.40 | eintopf | I worked with the msp430 |
| 18:19.47 | eintopf | and it was a mess with the toolchain |
| 18:20.14 | eintopf | but I heard that ti did some project with redhat to support msp430 to "mainline" gcc |
| 18:20.18 | eintopf | before it was a mess |
| 18:20.51 | zeiris | I think msp432 is just an Cortex M4 with TI's modules. That doesn't sound so bad. |
| 18:21.02 | zeiris | The FRAM MSP430s are very cool. |
| 18:21.26 | eintopf | http://www.ti.com/tool/msp430-gcc-opensource - looks better |
| 18:22.08 | eintopf | and I had a hardware bug and I couldn't start the bsl via bitbanging |
| 18:22.54 | eintopf | I implement a small bootloader which starts the bsl when user button is pressed application start :D |
| 18:23.10 | eintopf | s/pressed/pressed after/ |
| 18:23.12 | qi-bot | eintopf meant: "I implement a small bootloader which starts the bsl when user button is pressed after application start :D" |
| 18:30.54 | wpwrak | zeiris: oh. msp432 is not just another msp430. i see. |
| 18:32.57 | wpwrak | "The Device Descriptor Information (TLV) section contains a 128-bit true random seed " ;-) http://dilbert.com/strip/2001-10-25 |
| 18:35.26 | kristianpaul | Lol |
| 18:38.53 | *** join/#qi-hardware valhalla (~valhalla@149-71-148-166.v4.ngi.it) |
| 18:39.12 | larsc | probably even the same on each device |
| 18:39.15 | wpwrak | the idea is good, but they really should have use different words to describe it |
| 18:39.38 | wpwrak | larsc: no, apparently each device gets its own |
| 18:40.25 | wpwrak | similar to the unique numbers other manufacturers use |
| 18:50.11 | zeiris | Would trusting the silicon vendor to discard the random seed immediately after generation+burn be reasonable given that you must trust them to not insert backdoors into the silicon? :) |
| 19:00.34 | *** join/#qi-hardware wolfspraul (~wolfsprau@xd9ba33e7.dyn.telefonica.de) |
| 19:27.59 | larsc | even if they'd store it, would still be pretty hard to match it to the hardware |
| 19:53.39 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-107.telecom.by) |
| 19:54.20 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
