<azonenberg>
No nice prettifying or rounding of anything, all just boxes for now
<azonenberg>
this is all of the nodes in the graph showing input and output port names (which i should probably unify at some point, i'm not good at picking port names or even consistently using caps etc on them)
<azonenberg>
No lines connecting them yet
<azonenberg>
You can't drag them yet either
<azonenberg>
autoplace only
maartenBE has quit [Ping timeout: 240 seconds]
maartenBE has joined #scopehal
m4ssi has joined #scopehal
<_whitenotifier-f>
[scopehal-apps] azonenberg pushed 2 commits to master [+0/-0/±6] https://git.io/JIGRe
<_whitenotifier-f>
[scopehal-apps] azonenberg 0ff6604 - FilterGraphEditorWidget: draw lines between nodes. Autorouting avoids other nodes, but not lines yet. See #161.
<_whitenotifier-f>
[scopehal-apps] azonenberg 2200ef6 - Continued work on line autorouting. Now avoids colliding routes in vertical routing channels. See #161.
<d1b2>
<theorbtwo> Potentially silly question, but... if you are running clock recovery and then sending that to a "clock jitter" block, is it really a clock jitter block or just a jitter block? Could you also send it signal and a delayed signal and have it compute the jitter in the lag time?
_whitelogger has joined #scopehal
hlzr_ has joined #scopehal
gruetze_ has joined #scopehal
hlzr has quit [Ping timeout: 272 seconds]
gruetzkopf has quit [Ping timeout: 272 seconds]
hlzr_ is now known as hlzr
juli966 has joined #scopehal
juli966 has quit [Client Quit]
<bvernoux>
azonenberg, it will be nice to add USB HS support in scopehal
<bvernoux>
decoding ...
nelgau has quit [Remote host closed the connection]
nelgau has joined #scopehal
nelgau has quit [Ping timeout: 240 seconds]
nelgau has joined #scopehal
nelgau has quit [Ping timeout: 256 seconds]
electronic_eel_ has joined #scopehal
electronic_eel has quit [Ping timeout: 260 seconds]
nelgau has joined #scopehal
nelgau has quit [Ping timeout: 240 seconds]
<azonenberg>
d1b2: I'm measuring jitter in the tx clock
<azonenberg>
by comparing the filtered clock through the pll with the original
nelgau has joined #scopehal
<azonenberg>
bvernoux: we have partial HS support that miek was working on
<azonenberg>
I don't know how far he got
<azonenberg>
pretty sure it's not merged in master
<azonenberg>
and getting it set up and compiling. Would you be interested in primarily offline analysis working on saved waveforms acquired from somewhere else, or live processing on hardware you have?
NCFN has quit [Remote host closed the connection]
nelgau has joined #scopehal
nelgau has quit [Ping timeout: 240 seconds]
nelgau has joined #scopehal
nelgau has quit [Ping timeout: 240 seconds]
nelgau has joined #scopehal
nelgau has quit [Ping timeout: 246 seconds]
gruetze_ is now known as gruetzkopf
_whitenotifier-f has quit [Ping timeout: 260 seconds]
<NCFN>
Good question. What IRC client do you use, azonenberg? I have a Velleman 2channel scope and signal generator. I have only ever done minimal things with it. No idea even how one validates a scope past using a frequency standard and voltage standards.
<NCFN>
Where is help needed?
<azonenberg>
NCFN: I'm using pidgin. Does your scope have any kind of PC interface?
<azonenberg>
usb, ethernet, heck even rs232 or gpib
jevinskie[m] has joined #scopehal
<azonenberg>
And right now there are 142 open tickets against libscopehal, 88 against scopehal-apps, and 9 against scopehal-docs (and the only reason there's not more is that I haven't filed tickets for all of the things that aren't documented yet)
<azonenberg>
So there's a huge range of things to work on :))
<azonenberg>
At a high level the main categories of work needed are:
<azonenberg>
* Testing/debugging/build process improvements
<azonenberg>
* Instrument drivers
<azonenberg>
* Protocol decodes and math/DSP blocks
<azonenberg>
* GUI features
<azonenberg>
* Documentation
<azonenberg>
NCFN: So which of those sounds most interesting to you?
<NCFN>
You know, I've never written an instrument driver from scratch. Though I've hacked on drivers and firmware that are already written. That sounds like a worthwhile thing to do. Do you already have drivers for the Velleman?
<azonenberg>
Nope. The first step for that is filing a ticket against the scopehal repo requesting a driver, and including any information about the instrument
<azonenberg>
Better support for low cost hardware would definitely be nice
<azonenberg>
right now the best driver support is on the high end, like LeCroy and midrange Tek products
<azonenberg>
Also track down as much documentation as you can about the PC interface protocol the instrument uses
<azonenberg>
Do they have a SDK? Is there a documented SCPI command set?
<azonenberg>
Before you actually start writing the driver, make sure you have glscopeclient compiling on your machine and able to load waveforms from files
<azonenberg>
just to establish a baseline of functionality in case you have, say, a graphics driver problem or something
<NCFN>
For sure, with prototyping kits for around $10 including delta-sigma and SAR adc's, I think very-low-cost scopes up to MHZ or 10 MHZ range are very doable.
<NCFN>
I'll check. I bought this thing 6 or 7 years ago.
nelgau has joined #scopehal
<NCFN>
Yes, they have a SDK with examples on how to hook into their .dll's. It does not look like they have source code for the libraries, though it's USB, so it might not be hard to port sniff the commands off it.
<azonenberg>
Yeah. I'd suggest you start by making a ticket on libscopehal so people know you're working on it, link to the SDK and any other info you can find
nelgau has quit [Ping timeout: 265 seconds]
<azonenberg>
then start reverse engineering the USB protocol
<azonenberg>
are you reasonably familiar with libusb?
<NCFN>
I don't see any reference to SCPI so far. None in the source code for the demo program. And it's hard to search for because the Velleman PCSGU250 shows up on a lot of pages with other products that DO mention SCPI. Best guess right now is no. And it's the first time I've heard of SCPI
<NCFN>
I haven't used libusb. The other time I was debugging a serial over USB and I used some USB packet sniffer. I forget the name. I think sysinternals also has one, maybe?
<azonenberg>
Yeah, most likely it's not using SCPI at all, likely a full custom usb protocol
<azonenberg>
Are you running on windows, then?
<NCFN>
So, if the dll works reasonably, possibly no reason not to just use it.
<NCFN>
Yes, usually. I have an ubuntu stick, but I don't use it much.
<azonenberg>
As long as it's license compatible, that could work. It would just mean that scope couldn't be used except on windows
<azonenberg>
Which isn't ideal
<azonenberg>
But it's better than no support at all
nelgau has joined #scopehal
<_whitenotifier-4>
[scopehal] azonenberg pushed 2 commits to master [+0/-0/±2] https://git.io/JIn4P