<azonenberg>
I don't parse LabMaster part numbers correctly :p
<azonenberg>
I'm connecting glscopeclient to MAUI Studio which can be set up to pretend to be a lot of different LeCroy scopes
<azonenberg>
Right now i have it emulating a labmaster with almost all software options
<azonenberg>
but the device ID it reports over SCPI is "MCM-Zi-A"
<azonenberg>
since you're talking to the labmaster master control module
<azonenberg>
And thus it doesn't know how many channels you have
DanRoh has joined #scopehal
<_whitenotifier-f>
[scopehal] azonenberg pushed 3 commits to master [+0/-0/±17] https://git.io/JU4Pa
<_whitenotifier-f>
[scopehal] azonenberg 59ed1a8 - Initial work on trigger enumeration and dynamic creation. See #216.
<_whitenotifier-f>
[scopehal] azonenberg b8eb887 - Oscilloscope: now default to not syncing trigger (otherwise nothing was caching)
<_whitenotifier-f>
[scopehal] azonenberg 9ae2b90 - LeCroyOscilloscope: initial LabMaster 10Zi support. Only tested against MAUI Studio simulator, may not work on real hardware. Anybody have a LabMaster I can borrow to test? ;)
<_whitenotifier-f>
[scopehal] azonenberg pushed 2 commits to master [+0/-0/±4] https://git.io/JU4DO
<_whitenotifier-f>
[scopehal] azonenberg e39a518 - Initial support for MDA800 series, added channel colors for 8-channel scopes. Major revamp of option detection
<_whitenotifier-f>
[scopehal] azonenberg b913237 - Initial HDO4000A memory depth/sample rate support. More rework of option detection code
<_whitenotifier-f>
[scopehal] azonenberg commented on issue #64: Figure out channel bonding support for Rigol scopes that can interleave 1/2/4 channels - https://git.io/JU4yk
<_whitenotifier-f>
[scopehal] azonenberg pushed 4 commits to master [+0/-0/±8] https://git.io/JU4Sg
<_whitenotifier-f>
[scopehal] azonenberg 7fc4468 - Initial HDO6000A support
<_whitenotifier-f>
[scopehal] azonenberg cdf4d17 - Initial WaveRunner 9000 support
<_whitenotifier-f>
[scopehal] azonenberg 5cf965d - Initial WaveRunner 8000HD support
<_whitenotifier-f>
[scopehal] azonenberg 43c65de - Initial WavePro HD support
<azonenberg>
So in case you folks haven't guessed i'm running through all of the 8 scope models supported by the MAUI Studio simulator
<azonenberg>
making sure i properly detect all of the features, options, etc as well as adding legal memory depths/sample rates to the table
<azonenberg>
as well as fixing any other minor quirks that arise, like not having the colors for the second half of an 8-channel scope in the table either
<azonenberg>
only one or two left and then i can get back to working on the trigger dialog
<_whitenotifier-f>
[scopehal] azonenberg pushed 1 commit to master [+0/-0/±2] https://git.io/JU49a
<_whitenotifier-f>
[scopehal] azonenberg 05d1a01 - Initial WaveMaster 8Zi-B support
<_whitenotifier-f>
[scopehal] azonenberg pushed 1 commit to master [+0/-0/±5] https://git.io/JU47J
<_whitenotifier-f>
[scopehal] azonenberg 6784f97 - LeCroy scopes now report PulseWidthTrigger as a valid trigger type, but can't actually configure the instrument yet
<_whitenotifier-f>
[scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±6] https://git.io/JU457
<_whitenotifier-f>
[scopehal-apps] azonenberg 914dbb0 - Trigger properties dialog now allows listing all supported triggers for the selected instrument and viewing properties for them. No support for changing trigger settings yet.
Nero_ has joined #scopehal
Nero_ is now known as NeroTHz
Nero_ has joined #scopehal
NeroTHz has quit [Ping timeout: 240 seconds]
Nero_ is now known as NeroTHz
<_whitenotifier-f>
[scopehal] azonenberg pushed 1 commit to master [+0/-0/±2] https://git.io/JUBvP
<_whitenotifier-f>
[scopehal] azonenberg a12152c - Renamed "outside" to "not between" in pulse width trigger
<_whitenotifier-f>
[scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±4] https://git.io/JUBvD
<_whitenotifier-f>
[scopehal-apps] azonenberg 0836291 - TriggerPropertiesDialog: now show list of trigger properties and allow them to be configured
<azonenberg>
OK, so we now have a trigger properties dialog that dynamically queries the scope to figure out what trigger types are supported
<azonenberg>
then displays a list of properties and inputs you can manipulate, creates a new trigger object, and passes it back to the scope
<azonenberg>
i think the UI side is now done
wbraun_ has joined #scopehal
kc8apf_ has joined #scopehal
<azonenberg>
So now all that remains is to define more Trigger-derived object types for new kinds of trigger
<azonenberg>
and add logic to each scope class to process those
<azonenberg>
My first test case is doing pulse width triggering on LeCroy
<azonenberg>
noopwafel: if you want to play around with this object model and picoscope i'm curious what you'll come up with
gruetze_ has joined #scopehal
lukego has quit [Ping timeout: 272 seconds]
wbraun has quit [Ping timeout: 272 seconds]
kc8apf has quit [Ping timeout: 272 seconds]
gruetzkopf has quit [Ping timeout: 272 seconds]
kc8apf_ is now known as kc8apf
wbraun_ is now known as wbraun
maartenBE has quit [Ping timeout: 246 seconds]
lukego has joined #scopehal
maartenBE has joined #scopehal
gruetze_ is now known as gruetzkopf
<miek>
azonenberg: sooo i got a new toy to really test the limits of the agilent driver.. an old hp sampling scope (with TDR) :)
<azonenberg>
Nice. I've never tried using it with a sampling scope
<azonenberg>
So will be interesting to see how it works
<azonenberg>
can it do eye patterns or just repetitive waveforms?
<azonenberg>
should we make it so the native waveform output is an eye and not an AnalogWaveform?
<miek>
it can do eye patterns i think, i've only done initial tests then had to get back to work :p
<azonenberg>
well what i mean is, what should the output data type be
<azonenberg>
eye, analog, or both?
<miek>
that should probably be an option at some point, but initially i think it can build and return a single waveform so it should actually fit the existing driver/api quite well
<azonenberg>
ok
<miek>
aside from the trigger detection, i think the acquisition loop in the existing driver should just work. i'll have to get GPIB transport done first
azonenberg_work has quit [Ping timeout: 244 seconds]
azonenberg_work has joined #scopehal
DanRoh has quit [Ping timeout: 260 seconds]
<azonenberg>
Great. Also let me know if alternating trigger works now
<azonenberg>
it's not going to show up in the context menu for the channel (I may actually remove that, it seems redundant?) but if you go to the setup menu you should be able to select it from the trigger settings dialog
bvernoux has joined #scopehal
<miek>
yep, it works :)
<azonenberg>
great
<azonenberg>
I have a pulse width trigger class too
<azonenberg>
If your scope supports it, feel free to add support in the driver
<azonenberg>
PulseWidthTrigger exists, and can be instantiated in settings for the lecroy driver, but doesn't actually do anything yet
<azonenberg>
because no driver will report having it, or accept it, yet
<azonenberg>
the nice thing about this new trigger model is it's easy to define new types of trigger then hook them up to scopes as you add driver support
<miek>
having it derive from EdgeTrigger is a bit confusing, it's not clear to me whether rising/falling means high pulse or low pulse
<miek>
also i'm worried that the current model is going to end up with a lot of edge-case classes for each driver (looks like agilent doesn't do "not between" for pulse width, for example). trying to share trigger types might not be worth it?
<azonenberg>
miek: That's why the trigger revamp ticket is still open
<azonenberg>
I'm still figuring out the object model
<azonenberg>
Having each class only used by one driver is possible
<azonenberg>
The problem is just that it might require a lot of special casing in the UI
<azonenberg>
also i'll have to figure out the RTTI side of things since i require each trigger type to have a unique global name right now
<azonenberg>
for dynamic creation
juli965 has joined #scopehal
DanRoh has joined #scopehal
bvernoux has quit [Quit: Leaving]
DanRoh has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]