<d1b2>
<azonenberg> You can make ngscopeclient work with any data source you can find or invent
<d1b2>
<azonenberg> Just a question of how much work it will be
<d1b2>
<azonenberg> what are you thinking of using for the PC interface?
<d1b2>
<azonenberg> We support function generators, power supplies, and scopes. No instrument that exists to date implements all three classes but there's no inherent reason it wouldn't work, we just never found such a creature in the wild
<d1b2>
<azonenberg> we have drivers for scope + function generator combos that work fine
<d1b2>
<azonenberg> What class of MCU did you have in mind for the project? were you looking to do real time streaming or more conventional scope style capturing at full speed to a buffer, then downloading the data potentially at a slower rate than it was acquired?
<d1b2>
<azonenberg> The absolute simplest interface would be to have a UART on the MCU that talks directly to ngscopeclient using a usb-serial bridge (either an off the shelf adapter cable or putting a usb-uart chip on your board)
<d1b2>
<azonenberg> you could implement a SCPI-esque command interface in firmware on the MCU, then write a scopehal driver that talks to it
<d1b2>
<azonenberg> Given the amount of data you're talking about (maybe 1 Msps and a few tens to hundreds of kpoints per waveform), this might be more than sufficient
<d1b2>
<azonenberg> and will be a lot less work than jumping up to native USB on the MCU and running a whole usb stack etc
<d1b2>
<azonenberg> also eliminates the need for messing around with libusb or installing hardware drivers on the OS
<d1b2>
<azonenberg> you can just use any industry standard usb-serial chip with its existing driver
<d1b2>
<azonenberg> the only thing you'd have to code is the firmware on the MCU to do the scpi stuff, and the driver class for libscopehal which is pretty straightforward