nelgau has quit [Remote host closed the connection]
nelgau_ has joined #scopehal
nelgau has joined #scopehal
nelgau_ has quit [Remote host closed the connection]
bvernoux has joined #scopehal
massi has joined #scopehal
Degi has quit [Ping timeout: 256 seconds]
Degi has joined #scopehal
mandl has joined #scopehal
<mandl>
Mubes are you online ?
<mandl>
Or Dannes ?
mandl has quit [Ping timeout: 256 seconds]
massi has quit [Remote host closed the connection]
someone-else has joined #scopehal
<d1b2>
<dannas> @mandl I'm here now, if you're still around.
<d1b2>
<dannas> Looks like we had a bit of miscommunication regarding those switch-statements. The intention was to have separate cases for each supported model. I think @mubes tried to reach out to you a few times. He has a file where he's done most of the edits.
<d1b2>
<dannas> Communication on Internet is hard. 🙂
<d1b2>
<mubes> I'm here now.
<d1b2>
<mubes> Mandl is a bot reflection from elsewhere so I'm not sure what info he gets.
<d1b2>
<dannas> @mubes He stays true to the Internet spirit and stays on IRC. I feel like a sellout using discord. 🙂
<d1b2>
<dannas> Or did you mean a bot reflection from some parallell universe?
<d1b2>
<mubes> He he. I've just got burnt today by the GSuite grandfathering thing....guess I'll never learn.
<d1b2>
<dannas> Oh, they've dropped the free Gsuite. Oups.
<d1b2>
<mubes> Yeah, that's gonna hurt.
<d1b2>
<dannas> Who would ever know that Google would abandon or change terms for their services. (irony)
<d1b2>
<mubes> Obviously not making the profits they need (more irony)
<d1b2>
<mubes> Tbh, I've had it since 2006 so can't complain too much.
<d1b2>
<mubes> Just means I've got to debt-collect from a chunk of family users.
<d1b2>
<dannas> Re the siglent scpi driver: do you plan on adding more features to your 2000x/5000x?
<d1b2>
<dannas> How much usage have you gotten out of it?
<d1b2>
<mubes> Yes, digital eventually.
<d1b2>
<dannas> When I first heard of scopehal, I was hoping for much better wfms/s transfer rates
<d1b2>
<mubes> I use it a lot...mostly for protocol decode for SWD. The capture length is really useful.
<d1b2>
<dannas> I guess it's more of a post-processing tool than an interactive one.
<azonenberg>
dannas: it depends on the data source
<d1b2>
<mubes> Exactly.
<azonenberg>
with e.g. pico and lecroy gear it's more than fast enough for interactive use (tens of WFM/s)
<azonenberg>
most of the lower end hardware is slower
<azonenberg>
here's some stats on speed we've got with different memory depth and channel counts on various hardware
<d1b2>
<dannas> @azonenberg Yup, I fully understand that it's a limitation with the scope. Too bad your youtube demos were with a fast scope and not a slow one. 🙂
<azonenberg>
Yeah well that's what i have in my lab
<d1b2>
<mubes> There are tricks that we can play....there are facilities for reporting every nth sample for example, but that just speeds the UI, not the full dataset.
<d1b2>
<mubes> There's a graph in the manual for the 2000x+
<d1b2>
<dannas> @mubes swd, do you use it for reverse engineering?
<azonenberg>
Pushing low end vendors to improve their transfer rates is on our wishlist
<azonenberg>
we're working on it
<d1b2>
<mubes> Implementing ORBTrace.
<azonenberg>
if there's demand i think it will become a priority
<d1b2>
<mubes> Were in conversation with siglent about it.
<d1b2>
<dannas> @mubes Oh cool! It's like a replacement for JTrace, right?
<d1b2>
<mubes> Yes, with a 0 off the end of the price.
<d1b2>
<dannas> I wonder how much lower-end scopes are limited by less capable application processors and how much is about just not paying attention to performance.
<d1b2>
<mubes> Quite a lot the latter.
<d1b2>
<dannas> If you don't pay attention, then you can easily lose 5-10x of available perf
<d1b2>
<mubes> Historically most use for these interfaces was post processing
<d1b2>
<mubes> Scopehal is really the first compelling app for real streaming.
<d1b2>
<dannas> Yeah, it's not really that much data sent per second.
<d1b2>
<dannas> thinks about what to code on next
<d1b2>
<mubes> Well, 10Msamples....over a 100Mbit link.
<d1b2>
<dannas> I lost a little bit of direction. Waiting for that PR to be merged once all edits has been made.
<d1b2>
<mubes> I didn't even bother coding the 50 and 100 msample cases.
<d1b2>
<dannas> The bandwidth of the pico in that spreadsheet really stands out @azonenberg . What are you aiming for with your own scope projects? 10x of that?
<azonenberg>
dannas: 10G and 40G ethernet
<azonenberg>
at that point i think i am going to bottleneck on cpu/gpu performanec until scopehal gets a lot faster
bvernoux has quit [Read error: Connection reset by peer]
<azonenberg>
even the pico can challenge glscopeclient with more complex filter graphs
<d1b2>
<dannas> starts a savings account for the day that design is finished.
<azonenberg>
this is why i spend so much time profiling, optimizing, etc
<azonenberg>
I'm beginning initial ZENNECK R&D in 2020
<azonenberg>
2022*
<azonenberg>
the FPGA and ADC are ordered
<d1b2>
<dannas> checks calendar
<d1b2>
<dannas> That's this year!
<azonenberg>
Yeah
<azonenberg>
Some parts are already on the way/here
<azonenberg>
i'm going to be resurrecting the old frontend prototype to do some more measurements then respinning with fixes, higher bandwidth on the filter, and different connectors
<d1b2>
<dannas> @azonenberg I just wrote a question to the electronics subchat and realized that maybe your probe presentation will answer that. Is that presentation a good place to look?
<d1b2>
<dannas> I was asking about how come a probe input can have either a very low impedance or a million times higher.
<azonenberg>
I talk about that a bunch in my talk, if you havent watched the video definitely do so
<azonenberg>
Generally speaking, most probes claiming super high impedance in the megohm range are at near DC
<d1b2>
<dannas> Ok, I'll check it out.
<azonenberg>
because even tens or hundreds of femtofarads of input capacitance will drop your impedance rapidly as frequency climbs
<azonenberg>
much less pF
mandl has joined #scopehal
<mandl>
Good evening
<d1b2>
<dannas> @mandl Good evening! 🙂
<mandl>
Hi dannas
<d1b2>
<dannas> Did you see what we wrote above?
<mandl>
no
<mandl>
@Dannes Did you test our code on SDS1104x ?
<d1b2>
<dannas> @mandl I noticed that you closed the pull request. That really wasn't my intention. Wouldn't it be possible to apply your later changes to the file mubes provided?
<mandl>
@Dannes somethimes i am a bit lost in github ...
<d1b2>
<dannas> @mandl You might have done some more edits to SiglentSCPIOsciloscope.cpp after that file was created, if so please add them in as well in your PR.
<mandl>
@dannes never worked with @discord.com
<d1b2>
<mubes> Hi mandl....I can imagine this all gets confusing. I made edits to your file but wanted to retain the fact that is was your pr.
<d1b2>
<mubes> Let's just get the changes back into your pr and then Andrew can push it to master. It's certainly not working worse than anything that was there before.
<d1b2>
<mubes> @mandl you should be able to copy that file over the existing one and then commit it....I think you can push to the the existing pr to update it.
<_whitenotifier-7>
[scopehal-apps] azonenberg f9aae41 - Filter graph editor: don't stay in "dragging node" state after the second half of a double click
mubes has joined #scopehal
<d1b2>
<mubes> @mandl Just went over to IRC to try and ping you there but don't see you. I can put your changes into a patch if this is all getting complicated for you...just let me know. I'm off to bed now.
<azonenberg>
mubes: mandl signed off at 14:00 my time, half an hour before your prevous message
<azonenberg>
i guess quit messages don't get synced over to discord
<d1b2>
<mubes> Fair enough. I'll take a look at all this tomorrow. These patches are a bit in limbo at the moment. Night.