| Svp | hm, taping off pins still doesnt work, what a headache... | 00:15 |
|---|---|---|
| ch | i assume vpack is now very close to bat_v | 00:15 |
| ch | i hope the 51% are not correct, otherwise that will charge for a very long time | 00:15 |
| ch | "charge" | 00:15 |
| minute | ch: yeah my theory is it will just soldier along until its cap counter reaches 4000? | 00:17 |
| ch | if you unplug it, what does vpack drop to? | 00:17 |
| ch | might also give a better % | 00:18 |
| ch | current cycle got to 83% on the constant voltage charge and is now at 87% in this 0, -2, -4, -1 state | 00:19 |
| ch | slowly going up | 00:19 |
| ch | i do wonder if it will learn 5000 for your cells | 00:20 |
| ch | for mine it claimed 4100 at some point | 00:20 |
| ch | if you want to accel it you can unplug/plug/wait 5min or so/unplug/..., that should stay in the CV charge phase, unsure what negative effects that has | 00:23 |
| minute | ch: which one is vpack in the log? bat_v i guess? | 00:26 |
| minute | ah no i see now | 00:27 |
| minute | vpack is on the left | 00:27 |
| ch | vpack comes from the max, bat_v from mp2650 | 00:27 |
| ch | so all values before the word "mps" are from the max | 00:27 |
| minute | yes, makes sense | 00:28 |
| minute | ch: vpack dropped from 8345 to 7966 on disconnect | 00:28 |
| minute | % stayed the same this time! | 00:28 |
| minute | currently at 67% | 00:28 |
| minute | i wonder if it's balancing or not | 00:30 |
| ch | i didnt find much about balancing | 00:30 |
| minute | yeah it's quite underdocumented | 00:30 |
| ch | my hope is that if the vcells are the ~same, then it did? | 00:31 |
| minute | yeah | 00:31 |
| minute | ok gonna watch tv show and then check in if it reaches the 100% | 00:32 |
| josch | minute: thank you for your qcs8550 feedback -- should i nearly copypaste this for qcs6490 as well? | 00:32 |
| ch | ack | 00:32 |
| josch | about your emmc vs. lun feedback i guess for now we can just have DEV_MMC="sdX" and find a good X later | 00:32 |
| josch | that extlinux is not going to be used but efi does not matter right now for the machine.conf file i think | 00:33 |
| ch | The IC temporarily interrupts cell balancing to prevent interference with voltage and current measurements. Balancing is | 00:34 |
| ch | disabled 45ms minimum prior to making a measurement to allow for settling of the external filter on the pin. This pause | 00:34 |
| ch | occurs once every task period and has minimal impact on the average balancing current as shown in Figure 25. | 00:34 |
| ch | hmm | 00:34 |
| minute | josch: yes makes sense @ qcs6490! | 00:34 |
| ch | maybe it also interferes with the voltage measurement on the mp2650? | 00:34 |
| josch | thank you! have a good time relaxing :) | 00:34 |
| minute | thaaaanks | 00:35 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@h69.128.19.98.dynamic.ip.windstream.net) | 00:37 | |
| + bkeys1 (~Thunderbi@98.19.128.69) | 00:37 | |
| * bkeys1 -> bkeys | 00:39 | |
| ch | i turned off balancing (hopefully), but no change i think | 00:42 |
| - pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0) | 00:48 | |
| + pomel0 (~pomel0@user/pomel0) | 00:49 | |
| - pomel0 (QUIT: Remote host closed the connection) (~pomel0@user/pomel0) | 00:50 | |
| + pomel0 (~pomel0@user/pomel0) | 00:51 | |
| - lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah) | 01:07 | |
| + lidstah (~lidstah@gateway/tor-sasl/lidstah) | 01:07 | |
| * robin__ -> robin | 01:19 | |
| - Ar|stote|is (QUIT: Ping timeout: 246 seconds) (~linx@149.210.3.83) | 01:20 | |
| minute | ch: meanwhile my % is at 83%, cap still slowly going up. | 01:24 |
| + Ar|stote|is (~linx@149.210.3.83) | 01:25 | |
| minute | ttempty and ttfull are all around 10 hours, that means "unknown" probably :D | 01:25 |
| ch | yes | 01:26 |
| ch | i'm somewhat convinced that the cap going up is mostly a fuel gauge calibration thing. the voltage drop on disconnect - not sure how high that should be | 01:27 |
| minute | i think voltage drop is normal at least under load | 01:27 |
| minute | haven't checked with device off | 01:28 |
| - chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:85f:9a42:1100:1ac0:4dff:fedb:a3f1) | 01:28 | |
| minute | it's pretty much the same behavior with lifepo4 cells... they can only stay briefly above like 3.4V | 01:28 |
| ch | right. i'll see if i can test without unplugging | 01:28 |
| minute | i also think the cap going up is some form of calibration we're seeing | 01:29 |
| minute | maybe some moving average slowly moving | 01:29 |
| ^alex | the PD in the pocket should be able to charge from a 9V negotiation, yeah? | 01:32 |
| ch | ok, so disabling the chg fet causes a jump from 8358 to 8150 | 01:32 |
| ch | hmm | 01:33 |
| ch | nah | 01:33 |
| ch | forget what i said | 01:33 |
| ch | ^alex: it should yes | 01:33 |
| josch | working display with kernel 6.18 and LS1028A: https://mister-muffin.de/p/eEY2.jpg | 01:33 |
| ch | ^alex: depending on tolerances it might be very slow though | 01:34 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@98.19.128.69) | 01:54 | |
| + bkeys1 (~Thunderbi@98.19.128.69) | 01:54 | |
| ^alex | gotcher | 01:56 |
| ^alex | thenks | 01:56 |
| - bkeys1 (QUIT: Client Quit) (~Thunderbi@98.19.128.69) | 01:57 | |
| + bkeys (~Thunderbi@98.19.128.69) | 01:57 | |
| + bkeys1 (~Thunderbi@98.19.128.69) | 02:01 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@98.19.128.69) | 02:01 | |
| * bkeys1 -> bkeys | 02:01 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@98.19.128.69) | 02:02 | |
| + bkeys (~Thunderbi@98.19.128.69) | 02:02 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@98.19.128.69) | 02:04 | |
| + bkeys1 (~Thunderbi@h69.128.19.98.dynamic.ip.windstream.net) | 02:04 | |
| * bkeys1 -> bkeys | 02:06 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@h69.128.19.98.dynamic.ip.windstream.net) | 02:08 | |
| + bkeys (~Thunderbi@98.19.128.69) | 02:09 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@98.19.128.69) | 02:12 | |
| + bkeys (~Thunderbi@98.19.128.69) | 02:12 | |
| minute | josch: woah woah! | 02:14 |
| minute | josch: how did you do it? | 02:14 |
| josch | minute: by being lucky. Kernel 6.12 and kernel 6.17 is borked and when i started to bisect, I typoed 6.17 and tried 6.18 first. And that worked... | 02:15 |
| josch | *kernel 6.12 works | 02:15 |
| josch | i'll leave figuring out what broke between 6.12 and 6.17 and what fixed it in 6.18 as an exercise to the reader | 02:16 |
| josch | but i guess this should serve as a reminder to always try the litest git HEAD | 02:16 |
| josch | usb also works again and so does emmc | 02:17 |
| josch | i see no problems with ls1028a and kernel 6.18 from that MNT gitlab CI pipeline | 02:17 |
| ^alex | who's colonel panic? is he related to general protection-pfault | 02:20 |
| josch | m) | 02:22 |
| minute | josch: wow @ typo | 02:22 |
| minute | josch: i wonder when 6.18 will finally trickle down to us | 02:23 |
| josch | it's in experimental so we could have it now if we want to | 02:24 |
| josch | the reason it's still there is, that quite a few things changed in how the kernel is packaged in Debian in 6.18 | 02:24 |
| josch | and for example both flash-kernel and reform-tools in unstable break with 6.18 right now | 02:24 |
| josch | namely, /usr/lib/linux-image-$kvers is now a symlink to lib/modules/$kvers | 02:25 |
| josch | so files changed and you may say: why is that a problem if a compatibility symlink is in place? | 02:25 |
| josch | turns out that both reform-tools as well as flash-kernel run "find" on that directory but they both do not pass -H to find, so find will not follow the symlink and fails to install device trees... | 02:26 |
| minute | ah uff | 02:41 |
| minute | 94% | 02:42 |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 02:58 | |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156) | 03:14 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@98.19.128.69) | 04:26 | |
| + bkeys (~Thunderbi@98.19.128.69) | 04:26 | |
| + bkeys1 (~Thunderbi@98.19.128.69) | 04:34 | |
| - bkeys (QUIT: Ping timeout: 240 seconds) (~Thunderbi@98.19.128.69) | 04:34 | |
| * bkeys1 -> bkeys | 04:34 | |
| - pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0) | 07:00 | |
| + pomel0 (~pomel0@user/pomel0) | 07:01 | |
| - voltaire28 (QUIT: Ping timeout: 264 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 07:12 | |
| - pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0) | 07:13 | |
| + pomel0 (~pomel0@user/pomel0) | 07:38 | |
| grimmware | ch: can you send me the configuration you used in the windows tool if it's not a bunch of hassle? I've actually got it open on my gaming PC but couldn't muster the willpower to do anything else. Doing all of the parameters would have been overwhelming but I'd love to fuck around with the capacity and see what happens (my cells are 7000mAh) | 11:38 |
| grimmware | I've had some cell balancing issues so I'd probably be a good person to test it, I just want to build some understanding and confidence around the different capacity first | 11:39 |
| ch | tbh i think we dont setup the chathing term | 11:40 |
| ch | charging term current correctly | 11:40 |
| ch | so i'm doubtful it balances | 11:41 |
| minute | ch: interesting | 11:53 |
| minute | ch: btw it went to 100% overnight | 11:53 |
| ch | oh nice | 11:57 |
| ch | mine stuck to 99% | 11:57 |
| ch | 4028 reported max cap | 11:59 |
| ch | minute: what did the max cap converge to? | 12:00 |
| minute | ch: ah well it stuck to 98% in the log. just 100% reported to OS :D | 12:01 |
| minute | ch: cap 3946/4000mAh | 12:01 |
| minute | and only around 10mV difference between cells | 12:02 |
| ch | ah | 12:04 |
| ch | hm | 12:04 |
| gordon1 | what would happen if there is a short on one of usb a ports on reform classic? will that bring down all usb devices? | 12:04 |
| gordon1 | looks like it will happily deliver up to 4A there and then fuse will blow disabling all usb ports, is my understanding correct? | 12:11 |
| + mjw (~mjw@gnu.wildebeest.org) | 12:12 | |
| - digitalrane (QUIT: Ping timeout: 264 seconds) (~digitalra@user/digitalrane) | 12:21 | |
| + digitalrane (~digitalra@user/digitalrane) | 12:27 | |
| + johl (~johl@wikidata/Jens-Ohlig) | 12:28 | |
| - johl (QUIT: Client Quit) (~johl@wikidata/Jens-Ohlig) | 12:30 | |
| + paperManu (~paperManu@146.71.9.156) | 12:32 | |
| - digitalrane (QUIT: Ping timeout: 264 seconds) (~digitalra@user/digitalrane) | 12:46 | |
| minute | gordon1: on 3.0 yes, it's like that | 12:50 |
| + digitalrane (~digitalra@user/digitalrane) | 12:51 | |
| gordon1 | cool, i need to buy those little fuses then if i'm gonna plug my usb hack jobs in there | 12:54 |
| gordon1 | or just get a usb hub | 12:54 |
| gordon1 | minute: just an idea, maybe it would be good to put usb power to internal usbs through separate fuse, so short on external usb ports won't bring the keyboard and trackball down | 13:04 |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 13:15 | |
| * Guest160 -> mjw | 13:50 | |
| - bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@98.19.128.69) | 13:51 | |
| - paperManu (QUIT: Ping timeout: 255 seconds) (~paperManu@146.71.9.156) | 14:07 | |
| + chomwitt (~chomwitt@2a02:85f:9a42:1100:1ac0:4dff:fedb:a3f1) | 14:08 | |
| + siviq (~siviq@user/siviq) | 14:20 | |
| jah | elb: I see make sense, honestly 200hz is plenty enough imho | 14:20 |
| jah | anyone have cool hack to have tiny thing I could feel on the "f" and "j" key on the pocket? I mean those thing that you usually have on keyboard to know where to put your finger when you touch type... I was thinking sticking something with glue, or maybe just some glue itself could be enough | 14:21 |
| ch | i think josch had something there? | 14:24 |
| ch | (i also want it) | 14:24 |
| - siviq (QUIT: Quit: Client closed) (~siviq@user/siviq) | 14:31 | |
| ch | cell1 3286 cell2 3196 vpack 6477 age 115% 1% cap 0/ 4028mAh curr -1035 mps bat_v 6425 sys_v 6437 status 0x0080 prot_alert 0 | 14:34 |
| ch | cant really be 0, eh :> | 14:35 |
| + bkeys (~Thunderbi@13.sub-97-227-227.myvzw.com) | 14:35 | |
| ch | ~100mV imbalance too, meh | 14:35 |
| minute | gordon1: that's right | 14:37 |
| minute | jah: if you have a co2 or fiber laser you could maybe engrave a bump :D | 14:38 |
| elb | I thought I wanted it, but it's honestly only been a problem for me like twice | 14:38 |
| elb | (once was yesterday, I tried like three times to get my fingres on the right keys because I was off at an angle) | 14:38 |
| minute | ch: i think the balancing only works on the way up, while charging (on that chip) | 14:38 |
| minute | ch: but i guess cool that 0% is at 3.2v | 14:39 |
| ch | ah yes, UNTIL VFSOC < FULLSOCTHR | 14:39 |
| minute | ch: i wonder what safety cutoff is now? | 14:39 |
| minute | ch: undervoltage i mean | 14:39 |
| ch | cell1 3191 cell2 2567 vpack 5755 age 115% 0% cap 0/ 4028mAh curr -1070 mps bat_v 5662 sys_v 5637 status 0x8080 prot_alert 1 undervoltage, | 14:50 |
| ch | windows tool claims the setting is 2.440V | 14:50 |
| ch | well | 14:50 |
| + paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 14:54 | |
| jah | elb: yeah I realize it might not be so much of an issue in practice, because when I look at the screen I see the keyboard as well | 14:55 |
| jah | minute: that is a neat idea! I'll see if we have such thing at the local hackerspace | 14:55 |
| ch | grimmware: https://tmp.deduktiva.com/p/maxim2.ini note that this may very well be wrong | 15:01 |
| elb | jah: that might actually be related, yeah; my expectation that it was going to be a problem was based on a set of non-sculptured keycaps without such markings that I had tried on an atomic-style keyboard, which drove me crazy, but it's also possible that the missing markings weren't the root problem there | 15:10 |
| + murphnj (~murph@user/murphnj) | 15:35 | |
| - chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@2a02:85f:9a42:1100:1ac0:4dff:fedb:a3f1) | 15:57 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@13.sub-97-227-227.myvzw.com) | 16:06 | |
| grimmware | ch: that's perfect, I just wanted a reference from someone who knows more than I do :) I will take it with a pinch of salt | 16:16 |
| grimmware | thank you! | 16:16 |
| + mark_ (~mjw@gnu.wildebeest.org) | 16:20 | |
| + chomwitt (~chomwitt@2a02:85f:9a42:1100:1ac0:4dff:fedb:a3f1) | 16:34 | |
| - mark_ (QUIT: Ping timeout: 246 seconds) (~mjw@gnu.wildebeest.org) | 16:50 | |
| minute | ch: cool @ that file, maybe can you check that in to pocket reform git in a "docs" folder? so that one can load and tweak that later if necessary | 16:52 |
| - chomwitt (QUIT: Ping timeout: 255 seconds) (~chomwitt@2a02:85f:9a42:1100:1ac0:4dff:fedb:a3f1) | 16:54 | |
| + synnfynn (~synnfynn@user/synnfynn) | 17:08 | |
| gordon1 | wow antenna work confirmed, and looks like it behaves at least as well as the stock one on 5Ghz, need to find how to test 2.4G | 17:24 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 17:28 | |
| gordon1 | https://tinystash.undef.im/il/5E61ADj3RSpKM3FrCpTsPWyCVnna987cyn7xrhvrHzXJ2e7w7xwyPWN5QcGtMgMbvBqY6BT9FgZHgfMnnpwd17dU.JPG a bit close but didn't short | 17:55 |
| gordon1 | this one is fine https://tinystash.undef.im/il/5rsg4bMYQRtkFwuDPUU5n2MYHrZcJd7ZJidqtUPY9av3ZBQHeT1wHfqCeWdSqo7wh3aGmVbrZ6zaZMQs7mPPRd2r.JPG | 17:56 |
| mhoye | nice | 17:57 |
| minute | gordon1: awesome! | 18:08 |
| gordon1 | https://tinystash.undef.im/il/4bMCoK5dhGXKzPmrnjWK99tnwuisHr6wgvUFLZ1uFKmMK4pfAucMjTN3GjrNpckvkziwAWdiL98UM4UdpNYhW36f.JPG | 18:11 |
| + L29Ah (~L29Ah@wikipedia/L29Ah) | 18:17 | |
| minute | gordon1: really cool stuff | 18:18 |
| gordon1 | minute: want some for tests? | 18:18 |
| gordon1 | i have 4 spares | 18:19 |
| + aloo_shu_ (~aloo_shu@90.166.193.166) | 18:23 | |
| - aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.17.216) | 18:24 | |
| * aloo_shu_ -> aloo_shu | 18:24 | |
| gordon1 | one annoying part is that orientation is a bit suboptimal so it radiates less towards the display or back (on that axis) | 18:29 |
| gordon1 | but can't say it iperf3 benches too much | 18:30 |
| gordon1 | probably because in the room everything is reflected multiple times | 18:31 |
| minute | gordon1: yes would be cool! | 18:42 |
| minute | gordon1: address is on the very bottom of mntre.com | 18:42 |
| gordon1 | cool | 18:43 |
| + spew (~spew@user/spew) | 18:50 | |
| + voltaire28 (~jlafon@28.162.2.93.rev.sfr.net) | 19:08 | |
| - pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0) | 19:26 | |
| + pomel0 (~pomel0@user/pomel0) | 19:26 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 19:29 | |
| * mjw -> Guest3144 | 19:36 | |
| - Guest3144 (QUIT: Killed (calcium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 19:36 | |
| * mark_ -> mjw | 19:36 | |
| + Guest3144 (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 19:37 | |
| - voltaire28 (QUIT: Ping timeout: 240 seconds) (~jlafon@28.162.2.93.rev.sfr.net) | 19:43 | |
| - spew (QUIT: Quit: nyaa~) (~spew@user/spew) | 19:56 | |
| + jogu_ (~jogu@user/jogu) | 20:01 | |
| - jogu (QUIT: Ping timeout: 244 seconds) (~jogu@user/jogu) | 20:04 | |
| + jogu (~jogu@user/jogu) | 20:10 | |
| - jogu_ (QUIT: Ping timeout: 265 seconds) (~jogu@user/jogu) | 20:11 | |
| - digitalrane (QUIT: Remote host closed the connection) (~digitalra@user/digitalrane) | 20:30 | |
| + digitalrane (~digitalra@user/digitalrane) | 20:30 | |
| + voltaire28 (~jlafon@28.162.2.93.rev.sfr.net) | 20:52 | |
| + siviq (~siviq@user/siviq) | 21:16 | |
| josch | gordon1: really cool stuff! | 21:18 |
| + chomwitt (~chomwitt@2a02:85f:9a42:1100:1ac0:4dff:fedb:a3f1) | 21:56 | |
| - siviq (QUIT: Quit: Client closed) (~siviq@user/siviq) | 21:58 | |
| - synnfynn (QUIT: Quit: exiting..) (~synnfynn@user/synnfynn) | 22:11 | |
| - paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 23:06 | |
| + paperManu (~paperManu@146.71.9.156) | 23:26 | |
| - schalken (QUIT: Quit: nyaa~) (~schalken@117-118-178-69.gci.net) | 23:28 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
