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: 264 seconds]
Degi has joined #scopehal
t4nk_fn has quit [Ping timeout: 256 seconds]
<d1b2> <kerr4592> Got capstone done in time for demo, hooking our thing up to ngscopeclient with at least 1 working channel
<d1b2> <kerr4592> I had surgery on the demo day and the team botched telling the professors anything about it, so I spent the next few days negotiating a chance to actually get to present the thing I did 95% of the work on
<d1b2> <kerr4592> Overall, capstone passed I guess lol. Working with ngscopeclient code to implement it was a breeze! After the team member (with 1 year of a SWE internship experience) gave up on trying to get it to work, it only took me a few hours to start over, and implement the new scope and get it working.
<d1b2> <azonenberg> Sounds about like my experience with team members for group projects
<d1b2> <azonenberg> Minus the whole surgery bit that is
<d1b2> <kerr4592> One thing that might be nice: Generic file transport. Since "everything in Unix/Linux is a file" it would have been nice for testing
<d1b2> <kerr4592> I ended up making virtual serial devices to use for testing with socat, which worked well enough
<d1b2> <azonenberg> we already support socekts and uarts, what else would you have wanted? pipes?
<d1b2> <kerr4592> Oh I didn't even think of using sockets
<d1b2> <kerr4592> But, yeah, that's what I was thinking, using a fifo pipe
<d1b2> <azonenberg> yeah the "lan" transport (TCP sockets, over 5025 by default if not specified) is actually probably our most common by far
<d1b2> <azonenberg> in terms of how much hardware is normally used with it
Kerr has joined #scopehal
<d1b2> <kerr4592> Oh, there was one thing: Is it possible to specify a non-bilateral voltage range? IE, I had to specify +/-5v instead of 0-5v
<d1b2> <azonenberg> Yes, that's what the offset is for
<d1b2> <azonenberg> voltagerange is the full-scale range of the channel (i.e. 10 for -5 to +5)
<d1b2> <azonenberg> offset is the center position, i forget the convention for sign
<d1b2> <kerr4592> Oh, I must have not noticed offset, or it wasn't set in the rigol oscilloscope I copied from
<d1b2> <azonenberg> e.g. for -4 to +6 it'd be either +1 or -1, i cant remember
<d1b2> <azonenberg> but there's comments in the Oscilloscope class header that should explain the necessary details
<d1b2> <azonenberg> @johnsel ping me when you're around BTW
<d1b2> <johnsel> ‘Sup
t4nk_freenode has joined #scopehal
t4nk_freenode is now known as t4nk_fn