01:13 <azonenberg> New AKL-PT5 test board on the way, should be here mid week

03:34 <azonenberg> Yep, tracking says ETA Weds

03:34 <azonenberg> This one uses a single 350 ohm bog-standard 0402 resistor and a 100 ohm Vishay HML01

03:34 <azonenberg> as well as removing some extra ground plan to reduce input capacitance

18:34 <d1b2> <mokomull> @dannas I got your SDS1000 branch running on my 1104X-E last night and started poking around the codebase — anything you'd like me to tackle? I read through the Programming Guide to figure out what the waveform data looks like, at least 🙂

18:35 <d1b2> <dannas> @mokomull Maybe add triggers?

18:35 <d1b2> <dannas> I just found some time this evening and am about to add displaying of the captured waveforms.

18:36 <d1b2> <dannas> Let's see if I can give you a link... Just a sec

18:37 <d1b2> <mokomull> nice, hopefully the existing code is close enough for parsing the 8-bit samples

18:37 <d1b2> <dannas> The triggers that the sds2xxx/5xxx drivers supports are registered here: https://github.com/dannas/scopehal/blob/sds1104xe/scopehal/SiglentSCPIOscilloscope.cpp#L2934

18:38 <d1b2> <dannas> And the handling for triggers seems to start somewhere around here.

18:39 <d1b2> <mokomull> aye, I'll have a look probably tomorrow evening UTC-8

18:39 <d1b2> <dannas> I've used this script that relies on pyvisa for experimenting with SCPI https://gist.github.com/dannas/5cb06b883b306704e8319261c61878cb

18:40 <d1b2> <dannas> Re 8-bit sampling. There is already some code present for converting a downloaded trace into a format expected by glscopeclient. So I think it will be pretty straight forwared. (famous last word)

18:40 <d1b2> <dannas> I do have a bug in the code such that I need to run that siglent.py script first before I start glscopeclient.

18:40 <d1b2> <dannas> Probably some state variable that I haven't setup correctly.

18:41 <d1b2> <dannas> Let's see if I can figure out what that is about as well. Without that fixed, my branch won't properly work for you.

18:41 <d1b2> <mokomull> interesting, I didn't notice that issue. it did randomly re-enable channels I wasn't using once, though.

18:41 <d1b2> <dannas> Oh, it worked for you on first try? Interresting.

18:46 <d1b2> <dannas> @mokomull I started experimenting with triggers. There are some small notes about the format here: https://gist.github.com/dannas/5cb06b883b306704e8319261c61878cb#file-siglent_scpi-py-L122 Talk to you tomorrow.

18:51 <d1b2> <mokomull> Thanks for the pointers!

19:19 <d1b2> <dannas> Wow, there are quite a few different types of Waveforms in scopehal. But I just have to deal with Waveform<char>

19:19 <d1b2> <dannas> https://cdn.discordapp.com/attachments/776941750291267595/928004672722202685/unknown.png

19:21 <d1b2> <mokomull> I don't have the logic analyzer add-on to try out the digital signals on it 😦

19:24 <d1b2> <dannas> @mokomull me neither. It's so annoying that they had to create a separate dongle instead of doing like the Rigol and keysights where the logica analyzer is fully integrated into the scope.

19:25 <d1b2> <dannas> The worse thing is I don't think that dongle actually does much. Maybe someone has found a way to hack around it.

19:25 <d1b2> <mokomull> it's a separate dongle and a license key for the software!

19:26 <d1b2> <dannas> The license key can be obtained with siglent hack script that circulates on the Internet.

19:27 <d1b2> <dannas> Though if you do use it, you've voided your warranty and it is a violation of what Siglent allows you to do.

22:54 <azonenberg> dannas: specifically AnalogWaveform is the type you normally will be dealing with in a scope driver

22:54 <azonenberg> Which is an analog fp32 value for each sample

22:54 <azonenberg> but yes there's a ton of other ones for protocol decodes etc