azonenberg changed the topic of #scopehal to: ngscopeclient, libscopehal, and libscopeprotocols development and testing | https://github.com/ngscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
Degi has quit [Ping timeout: 246 seconds]
Degi_ has joined #scopehal
Degi_ is now known as Degi
<d1b2> <azonenberg> ok great
Degi has quit [Ping timeout: 244 seconds]
vup has quit [Quit: vup]
anuejn has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
vup has joined #scopehal
vup has quit [Remote host closed the connection]
vup has joined #scopehal
anuejn has joined #scopehal
juri_ has quit [Ping timeout: 265 seconds]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
<d1b2> <kretien> I pulled the latest ngscopeclient this morning (a9c8bc1a) but I'm getting an error when I run. Any hints what I should look for? ERROR: glfw init failed
<d1b2> <kretien> hm, may be a weird terminal issue. seems to launch fine in a new terminal instance
<_whitenotifier-4> [scopehal] fredzo opened pull request #920: Owon xdg support - https://github.com/ngscopeclient/scopehal/pull/920
<_whitenotifier-4> [scopehal-docs] fredzo opened pull request #92: Added Owon XDG function generator. - https://github.com/ngscopeclient/scopehal-docs/pull/92
<d1b2> <fredzo_72653> Hi @azonenberg, this is an easy one ;-): driver for Owon XDG function generator series: Driver: https://github.com/ngscopeclient/scopehal/pull/920 Doc: https://github.com/ngscopeclient/scopehal-docs/pull/92
<d1b2> <azonenberg> Awesome, will review later today. Sorry i've been overloaded lol
<d1b2> <fredzo_72653> lol no worries 🙂
<d1b2> <fredzo_72653> Anyone working on Function Generator node in StreamBrowserDialog ? If not, that would be my next task.
<d1b2> <azonenberg> Nope. I wanted to add RF generator support and fix the flashing scope badges at faster wfm/s
<d1b2> <azonenberg> but havent had time
<d1b2> <azonenberg> Could you maybe fix that yourself first?
<d1b2> <azonenberg> the scope badges i mean
<d1b2> <azonenberg> try with the demo scope at shallow memory depth or something and you should see it reach an annoying flickery state at a few WFM/s
<d1b2> <azonenberg> @fredzo_72653 the other thing i'd like if you could do, since i havent had time
<d1b2> <azonenberg> before you add any more stuff to the stream browser
<d1b2> <azonenberg> is try and refactor it a bit to not be one massive function for render
<d1b2> <azonenberg> see about breaking it up a bit
<d1b2> <azonenberg> also, for scope channels you render gain/offset using UNIT_VOLTS which is not right, you can have channels with other vertical units (e.g. amps for a current probe, dBm for a spectrum analyzer, etc). Check the actual y axis unit of the stream and use that
<d1b2> <azonenberg> See here for example of where it breaks down
<d1b2> <fredzo_72653> OK no problem, I'll have a look
<d1b2> <azonenberg> as a general rule we should be hardcoding units as little as possible
<d1b2> <azonenberg> streams come with units, use them
<d1b2> <azonenberg> (I just noticed that one yesterday while characterizing some LEDs on my spectrometer)
<d1b2> <duskwuff> (I'm still just amazed by how absurdly efficient newer green LEDs are)
<d1b2> <fredzo_72653> @azonenberg I can't seem to reproduce the flashing badge... What parameters where you using on demo scope ?