<d1b2>
<Attie> i can't verify it right now, but i'll make an issue for it
<d1b2>
<Attie> (updated / reloaded)
<_whitenotifier-f>
[glasgow] whitequark commented on pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIszn
<_whitenotifier-f>
[glasgow] 0x53A synchronize pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIs0H
<_whitenotifier-f>
[glasgow] 0x53A commented on pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIszx
<_whitenotifier-f>
[glasgow] attie opened issue #241: In-Use Glasgows can be interrupted by firmware reload - https://git.io/JIsgv
<_whitenotifier-f>
[glasgow] whitequark commented on pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIsgR
<_whitenotifier-f>
[glasgow] whitequark commented on issue #241: In-Use Glasgows can be interrupted by firmware reload - https://git.io/JIsgg
<whitequark>
Attie: why do you have Glasgows at API level 0 around in the first place?
<whitequark>
if you update the firmware (or remove it), you won't have this problem again
tomtastic has quit [Ping timeout: 240 seconds]
tomtastic_ has joined #glasgow
<_whitenotifier-f>
[glasgow] 0x53A synchronize pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIs0H
<d1b2>
<Attie> I'm not sure - I presumed level 1 was related to revC2... but I was also confused why that was in master
<d1b2>
<Attie> I'll reflash and that'll probably resolve it for me, though I imagine this "problem" still stands for those with out-of-date firmware (or no firmware)
<whitequark>
Attie: no firmware is 100% fine
<whitequark>
the only problematic case is outdated firmware
<_whitenotifier-f>
[glasgow] 0x53A commented on pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIs2n
<whitequark>
API level 1 has nothing to do with revC2
<d1b2>
<Attie> ok
<whitequark>
the one addition in API level 1 is uh... detection of outdated firmware
<d1b2>
<Attie> hah, very topical
<d1b2>
<Attie> so, this is an edge case: a long-running applet and hardware with out-of-date firmware
<d1b2>
<Attie> if you're content with that, feel free to close as wont-fix. that's probably okay with me
<whitequark>
the real question is how you even ended up with two different firmware versions?
<whitequark>
like, did you `git pull` in between?
<whitequark>
because when you started the long-running applet, it should have updated the firmware on the first glasgow
<whitequark>
(in the RAM, not in the flash)
<d1b2>
<Attie> honestly, not sure - but I would expect so
<d1b2>
<Attie> agreed
<_whitenotifier-f>
[glasgow] whitequark commented on pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIs26
<_whitenotifier-f>
[glasgow] whitequark commented on issue #241: In-Use Glasgows can be interrupted by firmware reload - https://git.io/JIs2y
<_whitenotifier-f>
[glasgow] whitequark closed issue #241: In-Use Glasgows can be interrupted by firmware reload - https://git.io/JIsgv
<_whitenotifier-f>
[glasgow] 0x53A synchronize pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIs0H
<_whitenotifier-f>
[glasgow] 0x53A commented on pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIsaF
<d1b2>
<0x53A> Do you think it might be possible at all to run glasgow on android? There is a linux environment (termux) with libusb support: https://wiki.termux.com/wiki/Termux-usb Would be really cool to be able to use an old smartphone instead of an r-pi I don't know how "complete" the termux environment is, but with python and wasm, at least ARM vs x86 shouldn't be an issue?
<whitequark>
0x53A: it's possible
<whitequark>
i didn't know about termux-usb
<whitequark>
let me try
<d1b2>
<0x53A> You have two install two apps, Termux and Termux:API. The second one failed to install for me, so I couldn't try it myself.
Stormwind_mobile has quit [Ping timeout: 260 seconds]
<whitequark>
ugh, i hate type-C
<whitequark>
0x53A: ok, i got it to work
<whitequark>
sort of
<whitequark>
it requires modification of applications, so someone will have to patch python-libusb1
kernelmethod has joined #glasgow
kernelmethod has quit [Client Quit]
<d1b2>
<0x53A> wow cool! I don't know much about libusb, what needs to be added? libusb_wrap_sys_device ?
<whitequark>
yeah
<whitequark>
and... i don't know how to integrate this into the glasgow enumerate loop
<whitequark>
basically, there should be no reason to have this custom API in libusb
<whitequark>
libusb should be able to execute the helper & acquire the fd entirely without API changes using fd passing over unix pipes
<whitequark>
the reason i'm saying "the only way" is because historically speaking, my work on glasgow is done to benefit the entire ecosystem rather than making one-off hacks (see: yowasp)
<whitequark>
and termux
<whitequark>
*termux's current libusb patch is kind of terrible and mostly useless
<whitequark>
so if i were working on that, i would fix it in a way that benefits everyone. unfortunately, it would probably be a lot more effort for you than for me, and at the same time, i don't really have time to do it myself.
<_whitenotifier-f>
[glasgow] whitequark closed pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIs0H
<_whitenotifier-f>
[GlasgowEmbedded/glasgow] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/JIsMK
<_whitenotifier-f>
[glasgow] whitequark commented on pull request #240: add InfluxDB2DataLogger (cli name influxdb2) to log into an InfluxDB 2.x - https://git.io/JIsM6
<d1b2>
<0x53A> Yes I was asking mostly out of curiosity and expected a "no, not possible". I wouldn't expect Android to be at the top of your priority list, I'm amazed that apparently usb would be the only real blocker. There do seem to be a few other interested parties, so maybe it'll be fixed in a few weeks/months/years :D
<whitequark>
i mean, glasgow is mostly pure python
<whitequark>
... hm i should check if yowasp works in termux
<whitequark>
it... doesn't
<whitequark>
can't find libdl?
<d1b2>
<0x53A> this kinda sucks, to keep co2 reasonable, i'd have to vent for 5 minutes every half hour
<d1b2>
<0x53A> I've probably lived in >> 2k co2 for months
<whitequark>
oh dear
<d1b2>
<0x53A> reasonably sized room, but with good isolation
<d1b2>
<0x53A> I think you're supposed to keep it under 1.5k, preferably under 1k?
<whitequark>
i know i don't suffer noticeable ill effects until ~1200 ppm or so, but 2k is a bit too much
<whitequark>
yeah
<whitequark>
i couldn't find a conclusive answer to when cognitive effects start being measurable, but 2k is *definitely* too much
<d1b2>
<0x53A> eye-balling it, it rises by 200ppm per half hour. Working for ~4 hours would mean +1600 if it is linear.
<d1b2>
<0x53A> I'm gonna keep the pc on for the next night so I can see how it rises while I sleep
<d1b2>
<0x53A> hmm, would it be possible to add an alarm sub-applet to scd30? so it can beep if it rises above a configured threshold?
<whitequark>
I don't think it belongs in glasgow
<whitequark>
you can configure an alarm in grafana though
<d1b2>
<0x53A> I could do it with influxdb, but the free cloud version only supports slack notifications for alerts, and I'd want it to work offline, too. I'm just gonna hack it in locally for now and then think about it later.
<whitequark>
the reason logging is in glasgow is because it's kinda critical for exploration; many sensors' readings only make sense as time series
<whitequark>
but i don't want it to grow an entire general purpose sensor framework
<d1b2>
<0x53A> makes sense for the base framework
<d1b2>
<0x53A> alright I love glasgow, I was able to hack it in and it works (I'll not send a PR though)
<d1b2>
<uep> for the base framework, is it an 'alarm' or is it a 'trigger' (in the same sense as a logic analyser or oscilloscope trigger)?
<whitequark>
0x53A: i think you can use `glasgow run-script` to avoid hacking on the codebase itself
<d1b2>
<uep> by the time you know the sensor works and want to build an actual monitor for it, it seems like time to hook it to a vanilla microcontroller maybe 🙂
<whitequark>
yes esp given that glasgow is a $150 device
Ekho has quit [Ping timeout: 244 seconds]
<whitequark>
0x53A: basically, copy the code in the "log" operation into a script file, use run-script to run it
<whitequark>
boom, custom behavior that works on unpatched upstream glasgow
<d1b2>
<0x53A> > by the time you know the sensor works and want to build an actual monitor for it, it seems like time to hook it to a vanilla microcontroller maybe sure, but I currently have neither a soldering iron nor a spare MCU. (and no circuit board, though a bread board would work with a DIP avr) With glasgow, all I need is a usb cable, I even glued the wires to the SDC30 for now because of no soldering iron.
<d1b2>
<0x53A> > basically, copy the code in the "log" operation into a script file, use run-script to run it ohh, thats cool, thank you!
<whitequark>
wow, GLUED the wires
<whitequark>
i admire your dedication
<d1b2>
<0x53A> thank you
<d1b2>
<0x53A> it only works if I put pressure on the connection 😐
<whitequark>
ouch
<d1b2>
<0x53A> alright I'm gonna sleep. Thank you so much for your help specifically, and glasgow and everything else generally.
<whitequark>
happy to help!
Ekho has joined #glasgow
egg|laptop|egg_ has quit [Remote host closed the connection]
<electronic_eel>
i found that quite interesting, they were able to read out a protected eeprom cell when injecting a glitch with a laser (on a back-decapped ATECC)
Getorix_ has joined #glasgow
Getorix has quit [Ping timeout: 240 seconds]
FFY00 has quit [Remote host closed the connection]
electronic_eel_ has joined #glasgow
electronic_eel has quit [Ping timeout: 260 seconds]
Stormwind_mobile has quit [Ping timeout: 272 seconds]
<d1b2>
<j4cbo> neat stuff
<d1b2>
<j4cbo> but disappointing as I’m using that part in a project :/
Stormwind_mobile has joined #glasgow
Stormwind_mobile has quit [Ping timeout: 260 seconds]
FFY00 has joined #glasgow
egg|laptop|egg has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
gruetze_ is now known as gruetzkopf
_whitenotifier-f has quit [Ping timeout: 260 seconds]
gillesmauve has quit [Ping timeout: 240 seconds]
emily has quit [Ping timeout: 240 seconds]
promach3 has quit [Ping timeout: 268 seconds]
disasm[m] has quit [Ping timeout: 268 seconds]
jevinskie[m] has quit [Ping timeout: 268 seconds]
fridtjof[m] has quit [Ping timeout: 260 seconds]
jschievink has quit [Ping timeout: 246 seconds]
pepijndevos has quit [Ping timeout: 264 seconds]
egg|laptop|egg has joined #glasgow
pepijndevos has joined #glasgow
gillesmauve has joined #glasgow
Stormwind_mobile has joined #glasgow
egg|laptop|egg has quit [Remote host closed the connection]
emily has joined #glasgow
promach3 has joined #glasgow
jevinskie[m] has joined #glasgow
disasm[m] has joined #glasgow
fridtjof[m] has joined #glasgow
jschievink has joined #glasgow
egg|laptop|egg has joined #glasgow
Stormwind_mobile has quit [Ping timeout: 246 seconds]
egg|laptop|egg has quit [Remote host closed the connection]
_whitenotifier-4 has joined #glasgow
<_whitenotifier-4>
[GlasgowEmbedded/glasgow] electroniceel pushed 1 commit to wip-revC2-firmware [+0/-0/±5] https://git.io/JIn6D
<_whitenotifier-4>
[GlasgowEmbedded/glasgow] electroniceel e472c43 - firmware: handle voltage alerts on revC2
Stormwind_mobile has joined #glasgow
<_whitenotifier-4>
[glasgow] electroniceel opened pull request #242: Bring revC2 firmware to the same level as revC1 - https://git.io/JInii
<electronic_eel_>
good news: with the firmware from the wip-revC2-firmware branch, you can now fully use the voltage command with revC2