03:13
Degi has quit [Ping timeout: 246 seconds]
03:14
Degi has joined #scopehal
05:30
Stary has quit [*.net *.split]
05:31
Stary has joined #scopehal
05:39
<
_whitenotifier-7 >
[scopehal-apps] azonenberg b9f20b6 - Continued filter support. Fixed a bunch of bugs, can now pass inputs to filters. See #515.
05:54
_whitelogger has joined #scopehal
05:55
mithro has joined #scopehal
06:06
Ekho has joined #scopehal
09:22
bvernoux has joined #scopehal
16:20
_whitenotifier-e has joined #scopehal
16:20
<
_whitenotifier-e >
[scopehal-apps] azonenberg ddd3def - Now using ImGui_ImplVulkan_RemoveTexture to delete texture objects. Refactored a bunch of code for more control over object destruction order.
16:20
<
_whitenotifier-e >
[scopehal-apps] azonenberg 920650e - Refactoring: removed no-longer-used descriptor pool object
17:09
<
_whitenotifier-e >
[scopehal-apps] azonenberg e0d8103 - Added imgui-node-editor submodule
17:22
<
bvernoux >
@azonenberg, I have found a regression on latest glscopeclient to load spi example which now crash and exit
17:22
<
bvernoux >
on older version it works perfectly it is very strange and the backtrace does not really help so far
17:24
<
azonenberg >
oh? where's it crashing?
17:24
<
bvernoux >
it's crashing during lof of spi example (your example)
17:25
<
bvernoux >
even if I'm doing it by hand in fact
17:25
<
bvernoux >
so either in commande line or manually
17:25
<
bvernoux >
command line
17:26
<
bvernoux >
I shall test on Linux too as so far it is reproductible on windows10
17:29
<
bvernoux >
@azonenberg, also I will do a talk at Hardwear.io NL on 27 Oct 2022
17:30
<
bvernoux >
I have found really funny things with standard simulation with LTSpice or QucsStudio
17:30
<
bvernoux >
Especially such simulation are useless when frequency exceed >1MHz without accurate model of capacitor/inductors ...
17:30
<
azonenberg >
Interesting. i'm trying to integrate the node editor you found and having build issues
17:31
<
bvernoux >
Yes I prefer you focus your time on ngscopeclient
17:31
<
bvernoux >
as it seems it is not far to be used with filters
17:31
<
bvernoux >
and probably after to load existing session and I could try spi example ...
17:32
<
bvernoux >
I have just finished to rebuild it now
17:32
<
bvernoux >
the build is really faster than before
17:32
<
azonenberg >
We actually can use filters right now in ngscopeclient
17:32
<
azonenberg >
what's missing is a lot of the rendering
17:33
<
azonenberg >
We can only
*draw* waveforms of sparse/uniform analog/digital type
17:33
<
azonenberg >
no protocols, eye patterns, or spectrograms
17:33
<
azonenberg >
and of course file load/save is still missing
17:35
<
bvernoux >
latest version of ngscopeclient work fine
17:35
<
bvernoux >
no issue so far
17:37
<
bvernoux >
I do not how we can use filter
17:38
<
bvernoux >
right mouse button display only cursors & add markers which both work fine
17:40
<
azonenberg >
Right click on the channel button
17:40
<
azonenberg >
you can't do it on the main plot area anymore, because it's now possible to have many waveforms in a single plot
17:40
<
azonenberg >
so it would be ambiguous which you intended to work with
17:41
<
bvernoux >
very nice !!
17:41
<
bvernoux >
I'm testing Thresholds
17:41
<
bvernoux >
it is so fast
17:43
<
bvernoux >
oups drag & drop FFT on the ramp crash
17:43
<
azonenberg >
yeah ngscopeclient is massively better than glscopeclient performance wise. none of the actual filter code is different
17:43
<
azonenberg >
FFT is untested
17:43
<
bvernoux >
FFT was working fine
17:43
<
azonenberg >
ah it only died when you dragged it? interesting
17:43
<
azonenberg >
i know we dont have peak drawing working yet
17:43
<
bvernoux >
but it does not like to be drag&dropped on ramp
17:44
<
azonenberg >
interesting. ok i'll investigate
17:44
<
bvernoux >
yes it crashed instantly
17:44
<
azonenberg >
probably confused because of the different Y axis units volts vs dB
17:44
<
azonenberg >
but it should have detected that and not let you drop it
17:44
<
bvernoux >
I'm pretty sure it could be reproduced on your computer too
17:44
<
bvernoux >
yes I suspect it is because the scale is different
17:44
<
azonenberg >
maybe the problem is that it crashes if you try to drop on an incompatible area?
17:44
<
bvernoux >
and incompatible
17:44
<
azonenberg >
well what i mean is, i detect this
17:44
<
azonenberg >
and don't show the drop icon as available
17:44
<
azonenberg >
it's possible if you try to drop on an incompatible area, it tries anyway and hits a null pointer or something
17:44
<
azonenberg >
i'll look into it after i finish some of this other stuff
17:45
<
bvernoux >
the only missing things on FFT is the peak details
17:46
<
bvernoux >
but I suspect you have not implemented it so far as it was using 2D Txt before IIRC
17:48
<
azonenberg >
Yeah. Peak rendering is not currently implemented
17:48
<
azonenberg >
like i said only basic analog and digital waveform drawing works so far
17:50
<
bvernoux >
yes but it is amazing
17:50
<
bvernoux >
and so fast
17:50
<
bvernoux >
The FFT is really fast too
17:51
<
bvernoux >
yes Frequency also does not like to be drag&dropped on it's signal
17:57
<
bvernoux >
except some drag&drop which crash everything is nice and smooth
17:58
<
bvernoux >
Threshold drag&drop also crash
17:58
<
bvernoux >
when it come back to it's own window which same scale
17:59
<
_whitenotifier-e >
[scopehal-apps] azonenberg cff94b3 - Initial work on filter graph editor. Just an empty window, but we now compile the node editor code.
18:00
<
azonenberg >
yeah i fixed a few segfaults related to drag and drop recently
18:00
<
azonenberg >
seems we still have some left
18:00
<
azonenberg >
i'll work on that after i get the initial filter graph editor up and running
18:01
<
azonenberg >
bvernoux: you missed the dev call i think, but i mentioned we set a new record for streaming performance with ngscopeclient and the experimental thunderscope driver last week
18:01
<
azonenberg >
something like 7.6 Gbps of streaming waveform data :D
18:01
<
bvernoux >
yes unfortunately I missed the call
18:01
<
bvernoux >
ha great I will say amazing !!
18:02
<
bvernoux >
it was with a big 3D GFX card too ?
18:02
<
bvernoux >
and fast PC I Imagine
18:02
<
azonenberg >
40M points * 4 channels * 22.5 WFM/s * 8 bit resolution
18:02
<
azonenberg >
or wait, let me make sure i'm reporting the right numbers
18:03
<
azonenberg >
ok so the record number was
18:03
<
azonenberg >
5M points * 4 channels * 44.8 WFM/s
18:03
<
azonenberg >
that's 896 Msps out of a theoretical 1000 coming off the ADC on the scope
18:03
<
azonenberg >
times 8 bits is 7168 Mbps / 7.168 Gbps
18:04
<
bvernoux >
yes very nice
18:04
<
azonenberg >
iirc aleksorsist has an nvidia 3070, unsure what CPU but it was something fast
18:04
<
azonenberg >
with the scope connected to the PC via thunderbolt aka pcie
18:04
<
azonenberg >
this was just displaying waveforms, no filter graph processing yet
18:05
<
azonenberg >
but still, this is an enormous amount of data. idk if it's a record for pc based scopes but it's certainly up there
18:05
<
bvernoux >
yes just DMA PCIE => GFX card
18:05
<
azonenberg >
not direct from pcie to card, it still passed through system ram
18:06
<
azonenberg >
and the int8 to float32 conversion was done with AVX on the CPU
18:06
<
bvernoux >
so the CPU was pratically not involved in theory
18:06
<
azonenberg >
(we will likely optimize further by pushing that conversion to the GPU, but that's not done in the current driver)
18:07
<
bvernoux >
I was thinking about your latest probes
18:07
<
bvernoux >
as it is quite complex to simulate them
18:07
<
bvernoux >
Why do you not try with test fixture and your VNA to take fill caracteristics of each bloc from few KHz to 8.5GHz ?
18:07
<
bvernoux >
then you will have full modelisation with s2p that you can plug
18:08
<
bvernoux >
and so on for each step
18:08
<
bvernoux >
like that you could correct impedance or other parameters if they are bad
18:08
<
azonenberg >
Yes. De-embedding the individual components especially things like the tip resistor is extremely nontrivial
18:09
<
bvernoux >
with a TRL
18:09
<
azonenberg >
I'm actively working with a support engineer from Sonnet to develop good EM models of all the parts
18:09
<
bvernoux >
I have done few design of TRL and they are perfect for that
18:09
<
bvernoux >
you just need to solder the component and do full TRL calibration
18:09
<
azonenberg >
Ideally I want full EM models of the tip including coupling to other components etc
18:10
<
bvernoux >
yes but for that you need also full model of your PCB with connector
18:10
<
bvernoux >
as they have big influence on the results
18:10
<
bvernoux >
and for that TRL and VNA is a must have
18:11
<
azonenberg >
So one of many things i want to do is make a PCB with pads for solder in probes and a 2x thru for de-embedding
18:11
<
azonenberg >
that seems to be the way to go for modern high performance characterization work, that's what IEEE 370 etc is recommending
18:11
<
bvernoux >
yes it is the purpose of TRL
18:11
<
bvernoux >
it is used as test fixture at end
18:12
<
bvernoux >
It is an old version I shall push latest version (which is very similar)
18:13
<
bvernoux >
this example of TRL board can be modified to adapt it for other components to be fully caracterized
18:13
<
bvernoux >
here it is for Series/Shunt Fixture for 0402
18:15
<
bvernoux >
I have improved the connectors on latest version
18:16
<
bvernoux >
to be compatible and easier to solder any SMA connector
19:42
<
_whitenotifier-e >
[scopehal] miek 114eb39 - AgilentOscilloscope: fix waveform drawing
19:42
<
_whitenotifier-e >
[scopehal] miek 3279966 - AgilentOscilloscope: use standard sample conversion function
19:42
<
_whitenotifier-e >
[scopehal] azonenberg f9fa9c4 - Merge pull request #717 from miek/agilent-fixes Fix waveform drawing for the AgilentOscilloscope driver
23:29
bvernoux has quit [Quit: Leaving]