sgstair_ has quit [Read error: Connection reset by peer]
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 252 seconds]
Degi_ is now known as Degi
ALTracer has quit [Read error: Connection reset by peer]
ALTracer has joined #scopehal
ALTracer has quit [Ping timeout: 260 seconds]
ALTracer has joined #scopehal
_whitelogger has quit [Ping timeout: 260 seconds]
_whitelogger has joined #scopehal
cyborg_ar has quit [Ping timeout: 260 seconds]
cyborg_ar has joined #scopehal
ALTracer has quit [Read error: Connection reset by peer]
ALTracer has joined #scopehal
sgstair has joined #scopehal
ALTracer has quit [Read error: Connection reset by peer]
ALTracer has joined #scopehal
ALTracer has quit [Read error: Connection reset by peer]
ALTracer has joined #scopehal
Kerr has joined #scopehal
<d1b2>
<kerr4592> Which of the oscilloscope drivers would be a good starting point to try and implement one minimally?
<d1b2>
<azonenberg> Hmm, Rigol is probably not a horrible one. It's mostly free of weird quirks and workarounds and isn't overly complex like e.g. the lecroy driver with a zillion features
<d1b2>
<kerr4592> We've had to downgrade the plan, and are just using UART at 16Mbaud for transport now, btw. The EZ USB fx3 documentation and software stuff has been a nightmare - when they were bought out, they did not do a good job of keeping everything accessable
<d1b2>
<azonenberg> Fuuuun
<d1b2>
<kerr4592> Yeah, I've got a strong distaste for this chip and company after the past month lol
<d1b2>
<kerr4592> Just, like, needing some driver or library and not being able to find it since they closed down the old company's servers and didn't migrate it over
<d1b2>
<kerr4592> But all the upfront stuff was there, so we got a ways in before hitting a wall
<d1b2>
<azonenberg> oof
<d1b2>
<kerr4592> Is uart transport not implemented?
<d1b2>
<kerr4592> Not a big deal, but if I'm just missing something I'd like to not miss it
<d1b2>
<azonenberg> UART transport is implemented. what's missing is the command to throw out data in the rx buffer
<d1b2>
<azonenberg> does your scope implement the *IDN? command? and do you have echoing turned on?
<d1b2>
<azonenberg> (the driver will get very confused if stuff it sends gets echoed back at it)
<d1b2>
<azonenberg> The impression i'm getting from that error log is that your device is echoing input back at the source
<d1b2>
<azonenberg> Echoing can happen either in firmware or in uart settings and i'm pretty sure our uart driver turns it off. so if you're still getting echo its probably your code doing it