azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing | https://github.com/azonenberg/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 264 seconds]
Degi_ is now known as Degi
<_whitenotifier-1> [scopehal-apps] azonenberg pushed 1 commit to master [+2/-0/±2] https://git.io/Ji8FB
<_whitenotifier-1> [scopehal-apps] azonenberg 9feebbe - Initial work on scopevna test app
<azonenberg> this works better than i expected for no cal whatsoever lol
massi has joined #scopehal
someone-else has joined #scopehal
<d1b2> <dannas> The Rigol programming manuals for lower end scopes have their examples in USB. I wonder if the SCPI implementation for the usb stack and LXI are equivalent.e
<d1b2> <dannas> I'll do some experiments with pyvisa and see if I can get better results there using LXI. And I might take a peek at sigroks implementation. And I can try using USB as well to see if that makes a difference.
<d1b2> <dannas> Let's see how much time I have this evening. I hooked up the tracy profiler to glscopeclient during lunch break. That might be useful for me to get a quick grasp on how the parts fit together.
<d1b2> <dannas> I noticed that GTK doesn't own the main loop, but rather glscopelicent regularly makes Gtk::Main::iterations() calls from ScopeApp::Run()
<d1b2> <dannas> There's a couple of calls to iterations() from other places as well to make progress when the UI-thread is blocked on some long running task. Looked into that due to a couple of occasions when the glscopeclient did not respond to input while waiting for waveforms from the scope.
<azonenberg> Correct. That's why I did it
<azonenberg> If I have a slow thing in the UI thread I don't want to block other event handling
<azonenberg> I try to push stuff to background threads when possible but it doesn't always work out
Degi has quit [*.net *.split]
Bird|otherbox has quit [*.net *.split]
tnt has quit [*.net *.split]
kbeckmann has quit [*.net *.split]
tnt has joined #scopehal
kbeckmann has joined #scopehal
Bird|otherbox has joined #scopehal
Degi has joined #scopehal
bvernoux has joined #scopehal
d1b21 has joined #scopehal
balrog_ has joined #scopehal
balrog has quit [*.net *.split]
asy_ has quit [*.net *.split]
d1b2 has quit [*.net *.split]
d1b21 is now known as d1b2
asy_ has joined #scopehal
someone-else has quit [Quit: Connection closed]
massi has quit [Remote host closed the connection]
<Degi> dannas: I think Rigol wanted to make a better firmware where the LAN data transfer is faster sometime in june but till now there hasn't been an update yet.
<Degi> bvernoux, have you heard anything?
<bvernoux> re
<bvernoux> Degi, yes they have pushed again the dead line to release the firmware
<bvernoux> I checked this issue in our case management system. Well, our R&D has determined the planed finish date as Dec 31st, 2021.
<bvernoux> I am so sorry for keeping you waiting so long time. I will track this case and let you know immediately if I get any update.
<bvernoux> I really doubt we will see a release ...
<Degi> Hmm yes, kinda worried about that too, I hope that they stay with that date. Thank you for keeping on it !
<bvernoux> Yes I will ask again on Jan 2022 ;)
<bvernoux> Rigol MSO5k are really amazing but it is a raw diamond ;)
<bvernoux> If they could optimize that I think other lags will be solved too
bvernoux has quit [Quit: Leaving]
balrog_ is now known as balrog
someone-else has joined #scopehal