azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing | https://github.com/azonenberg/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
lain has quit [Quit: brb~]
lain has joined #scopehal
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 265 seconds]
Degi_ is now known as Degi
<azonenberg> sys64738: sorry, was at work
<azonenberg> So, you will want to inherit from either Oscilloscope or SCPIOscilloscope depending on whether you use SCPI commands or not
<azonenberg> as far as we're concerned a LA is just a scope with no analog channels
<azonenberg> To register it, just do AddDriverClass(YourClass) in DriverStaticInit() in scopehal.cpp
<azonenberg> Your constructor will need to take a SCPITransport pointer regardless of whether you use SCPI as the native transport. For stuff that talks to libusb etc, you'd just pick "null" as the transport in the GUI and ignore the transport in the constructor
<azonenberg> DemoOscilloscope provides a good example of how that works
<azonenberg> The Pico and LeCroy drivers are good examples for how to actually populate all of the data structures associated with digital waveforms
<GyrosGeier> sys64738, ffts is in Debian NEW
<GyrosGeier> so it should be available as packages Real Soon Now
bvernoux has joined #scopehal
someone--else has joined #scopehal
CarlosEDP has joined #scopehal
<d1b2> <sys64738> ah
<d1b2> <sys64738> (i run void tho)
<d1b2> <sys64738> also it uses a custom thing over libftdi, having this dependency is ok?
<GyrosGeier> the plan is to add a few testcases later today
<GyrosGeier> so we can actually verify that it works
<d1b2> <sys64738> ah
someone--else has quit [Quit: Connection closed]
<azonenberg> sys64738: yeah i think libftdi is a reasonable dependency
<azonenberg> the main thing i'm trying to avoid is hard dependencies on vendor blobs
<azonenberg> e.g. Pico Technology's SDKs
<azonenberg> Since its silly to force people to install that sdk if they dont have a scope of that make
<azonenberg> So for those, we've usually made external bridge servers that link to the vendor SDK and can be installed only by people who have the appropriate hardware
<azonenberg> and libscophal talks to the bridge over sockets
<d1b2> <sys64738> fair
<azonenberg> One reason to consider this architecture anyway is that it permits network transparency for usb attached instruments
<azonenberg> i.e. you can plug the usb scope/LA into one machine and then remotely control and stream data from another one
<azonenberg> i use this all the time with my PicoScope
someone--else has joined #scopehal
someone--else has quit [Quit: Connection closed]
someone--else has joined #scopehal
<bvernoux> Very interesting video https://www.youtube.com/watch?v=a-v53hfAyDU
<bvernoux> EEVblog 1402 - Rohde & Schwarz NGA100 PSU Teardown
<bvernoux> THere is very ugly overshoot for a 1500USD R&S Power Supply !!
<bvernoux> I really prefer my EEZ BB3 which is less expensive fully open source and without those ugly overshoot !!!
bvernoux has quit [Quit: Leaving]
someone--else has quit [Quit: Connection closed]