Bird|otherbox has quit [Remote host closed the connection]
Bird|otherbox has joined #scopehal
<Bird|otherbox>
and back up on the new card :)
<Bird|otherbox>
and, IT WORKS! \o/
<azonenberg>
the card works or glscopeclient works? or both
<Bird|otherbox>
both!
<azonenberg>
Awesome
<azonenberg>
what scope are you testing on?
<Bird|otherbox>
DS1054Z
<azonenberg>
Great. yeah that one is a little bit slow due to the wimpy CPU scope-side, but it's fairly well supported i think
<azonenberg>
I guess spend a little time getting familiar with the software, playing around with protocol decodes etc
<azonenberg>
make sure you have the latest version from git obviously as development is moving rapidly
<azonenberg>
And then let me know when you're ready to start actually doing development and what your intentions are with that
<azonenberg>
One thing that might be worth doing soonish, althouhg not the UI work you were originally talking about, is adding support for more types of trigger to the Rigol driver
<azonenberg>
i'm rapidly adding lots of new trigger types to LeCroy but right now none of the other instrument classes support anything but simple edge trigger
<azonenberg>
and i want to at least get a couple of trigger types implemented for at least one other scope class so we can see how well the object model works across different types of scope
<Bird|otherbox>
yeah, I managed to forget the passphrase I put on my public key, just as I thought I would :/
<Bird|otherbox>
err, on my key :P
<Bird|otherbox>
guess I'll need to make a new SSH key with a passphrase I'll actually remember?
<Bird|otherbox>
done
Degi has quit [Ping timeout: 272 seconds]
Degi has joined #scopehal
electronic_eel_ has joined #scopehal
electronic_eel has quit [Ping timeout: 272 seconds]
<_whitenotifier-f>
[scopehal] azonenberg pushed 1 commit to master [+2/-0/±10] https://git.io/JURWV
<miek>
re pulse triggers: on my scope at least, the trigger point is on the edge after the pulse, so a high pulse trigger will effectively trigger on the falling edge
<azonenberg>
Yes, that is the case here too
<azonenberg>
it triggers at the ending edg eof the pulse
<miek>
so i still think configuring it based on edges is going to be confusing - "is it the leading or trailing edge of the pulse?"
<azonenberg>
Yeah i'll revisit that at some point. right now i'm modeling all of these triggers on lecroy's settings as that's what i know best
<azonenberg>
and then i'll work on making the ui prettier
<azonenberg>
lecroy's ui has nice little graphics showing what the trigger does in some cases
<azonenberg>
i might try drawing something similar
<azonenberg>
But again some of the object model may change as we add support for more devices. That's why i wanted folks to add some of these new trigger types to agilent, rigol, etc
<azonenberg>
So we can see if there's differences from device to device that my initial model didn't take into account
<azonenberg>
also *this* is interesting
<azonenberg>
i'm not sure how i'll enforce this in the UI
<azonenberg>
but it appears that the lecroy SPI decode does not allow you to mix analog and digital channels in the same decode
<azonenberg>
so if you have a SPI decode with data on an analog channel, you must use analog channels for CLK and CS#
<azonenberg>
and if data is digital, CLK and CS# must be digital too
<azonenberg>
This applies to triggering, not just decoding. I'm not interested in the decodes from the scopehal side, but if i'm using a serial protocol trigger i obviously need to understand the limitations of it
<azonenberg>
aaaand i just found a bug in MAUI around this lol
<azonenberg>
If you configure a SPI decode with some of the inputs analog and some digital, it will work. But as soon as you select "link to trigger" it will silently configure the trigger with D0 instead of the analog channel you expected
<azonenberg>
This is the third lecroy firmware bug i've found this week
azonenberg_work has quit [Ping timeout: 240 seconds]
azonenberg_work has joined #scopehal
Bird|otherbox has quit [Remote host closed the connection]