azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing | https://github.com/azonenberg/scopehal-cmake, https://github.com/azonenberg/scopehal-apps, https://github.com/azonenberg/scopehal | Logs: https://freenode.irclog.whitequark.org/scopehal
m4ssi has quit [Remote host closed the connection]
marcos__ has quit [Ping timeout: 268 seconds]
marcos__ has joined #scopehal
_whitelogger has joined #scopehal
_whitelogger has joined #scopehal
<azonenberg> futarisIRCcloud: cool idea, looks way too low end for the kind of work i'm interested in doing but if anybody gets their hands on one i'd gladly help get a driver written
<futarisIRCcloud> Yep. I'd help you out with drivers, for more high end gear, but I don't have access to any...
<azonenberg> A lot of the driver work is being done remotely
<azonenberg> marcos__ and whitequark have provide me with access to R&S and Rigol scopes for driver development which was very helpful
<azonenberg> however i've been so busy lately i havent had time to finish either
marcos__ has quit [Ping timeout: 246 seconds]
marcos__ has joined #scopehal
bvernoux has joined #scopehal
bvernoux has quit [Quit: Leaving]
marcos__ has quit [Read error: Connection reset by peer]
bluezinc_ has joined #scopehal
<bluezinc_> o/
<azonenberg> o/ bluezinc_
<bluezinc_> so, are there any other channels I should be aware of?
<azonenberg> for f/oss test equipment? just this one
<azonenberg> ##openfpga for f/oss FPGA toolchain work
<bluezinc_> maybe I should look into writing a handful of decoders for this.
<bluezinc_> or DSP, or filters, or basically anything but drivers
<azonenberg> There's lots of room on that side
<azonenberg> also miscellaneous UI improvements, performance tweaks, file load/save support for offline data analysis
<bluezinc_> I think I might go for load/save support, because I don't think I have a supported scope, and then I'll just be able to steal captures from y'all for decode work.
<bluezinc_> and sooner or later finish building my scope & then write a driver for it...
<azonenberg> Actually even before load/save support
<azonenberg> How about a dummy signal source that just spits out a sinewave or something 4
<azonenberg> something you can use for UI work etc without a real scope
<bluezinc_> not a bad idea.
<azonenberg> and maybe optional noise etc
<azonenberg> Then you can start implementing load/save using the dummy signal's output as the data you're saving
<bluezinc_> I'd probably do a handful of stuff there (square/sine/triangle/etc.)
<azonenberg> Actually, i wonder if we could bodge that onto the function generator API
<bluezinc_> probably?
<azonenberg> Create a simulated scope where one of the channels is tied to a function gen
<azonenberg> then just use the func gen API to control it
<bluezinc_> right now I'm on the "see if any of this stuff builds" step.
<azonenberg> or maybe multiple func gen channels, one per scope channel
<azonenberg> that's probably best
<azonenberg> And fair enough, gotta make it compile first :p
<bluezinc_> not a huge cmake fan, but I'll suffer through it.
<azonenberg> FYI i'll be out of town most of tomorrow but will try and be on IRC a bit from my phone tonight
<bluezinc_> well, there is always the alternative, where I write a bunch of code, commit it, and then just pray that it compiles. :)
<azonenberg> Lol yeah i want you to be able to debug and test
<bluezinc_> do you have a list of supported scopes?
<azonenberg> And having infrastructure for unit tests etc is highly desirable
<azonenberg> There's a list on the wiki that is a little out of date i think
<azonenberg> basically, there are drivers now for lecroy, siglent, rigol, and R&S scopes
<bluezinc_> funny, I was talking to siglent the other day.
<azonenberg> The lecroy driver should work with any MAUI based scope, meaning pretty much any windows-based lecroy scope (not the waveace which is a siglent OEM design)
<bluezinc_> apparently they're like rigol but slightly less terrible
<azonenberg> As of now the only transport implemented is ethernet, but i have the transport and driver layers separated so it would be easy to write a usb/rs232/gpib transport that would work with them plus any other scope down the road
<azonenberg> the siglent driver is for siglent+lecroy designs using a slight modification of lecroy's protocol with some firmware bugs, that's an Error_404 project
<azonenberg> it works with the waveace plus the siglent badged version of the same hardware (sds1204?) but is still a WIP
<azonenberg> then the rigol driver has been tested on whitequark's ds1104z (?) and works ok-ish in read only mode but most of the set* functions are unimplemented
<azonenberg> the R&S driver has been tested on marcos's RTM3000 series scope and works OK in read only mode over the internet, but when run locally it segfaults - we have not yet diagnosed this
<bluezinc_> Also, the more I read about it, the more I agree with you that 10/40Gbe is the interface that ought to be used for a custom scope.
<azonenberg> as with the rigol driver it's read only right now, most of the set* functions are empty
azonenberg_mobil has joined #scopehal
azonenberg_mobil has quit [Read error: Connection reset by peer]
azonenberg_mobil has joined #scopehal
azonenberg_mobil has quit [Ping timeout: 272 seconds]
azonenberg_mobil has joined #scopehal
<azonenberg_mobil> ok back. finally
<azonenberg_mobil> mobile clients don't seem to do a great job jumping from wifi to lte...
azonenberg_mobil has quit [Read error: Connection reset by peer]