<_whitenotifier-4>
[starshipraider] azonenberg pushed 1 commit to master [+17/-0/±0] https://git.io/JmpJ3
<_whitenotifier-4>
[starshipraider] azonenberg pushed 1 commit to master [+17/-0/±0] https://git.io/JmpJ3
<_whitenotifier-4>
[starshipraider] azonenberg a7d2cc6 - Initial draft of AKL-PT2 manual. Still pending final figures of test setup and rise/fall times and typical waveforms.
<_whitenotifier-4>
[starshipraider] azonenberg a7d2cc6 - Initial draft of AKL-PT2 manual. Still pending final figures of test setup and rise/fall times and typical waveforms.
Degi_ has joined #scopehal
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 276 seconds]
Degi has quit [Ping timeout: 276 seconds]
Degi_ is now known as Degi
Degi_ is now known as Degi
sam210723 has joined #scopehal
sam210723 has joined #scopehal
sam210723_ has quit [Ping timeout: 240 seconds]
sam210723_ has quit [Ping timeout: 240 seconds]
maartenBE has quit [Ping timeout: 245 seconds]
maartenBE has quit [Ping timeout: 245 seconds]
maartenBE has joined #scopehal
maartenBE has joined #scopehal
_whitelogger_ has quit [Remote host closed the connection]
<d1b2>
<david.lenfesty> okay that was because I was using deep memory
<d1b2>
<david.lenfesty> okay that was because I was using deep memory
bgamari has joined #scopehal
bgamari has joined #scopehal
bvernoux has joined #scopehal
bvernoux has joined #scopehal
<azonenberg_work>
david.lenfesty: still file a bug
<azonenberg_work>
david.lenfesty: still file a bug
<azonenberg_work>
no matter what you do on scope settings, glscopeclient / libscopehal should not segfault
<azonenberg_work>
no matter what you do on scope settings, glscopeclient / libscopehal should not segfault
<azonenberg_work>
at worst, print an error and abort
<azonenberg_work>
at worst, print an error and abort
<d1b2>
<david.lenfesty> yeah there's a few other issues w/ usability
<d1b2>
<david.lenfesty> yeah there's a few other issues w/ usability
<d1b2>
<david.lenfesty> I gave up, but some point soon I'll try and track them down and get issues filed for them
<d1b2>
<david.lenfesty> I gave up, but some point soon I'll try and track them down and get issues filed for them
bvernoux has quit [Quit: Leaving]
bvernoux has quit [Quit: Leaving]
<d1b2>
<mubes> Oh dear, had a quick punt at adding SDS2000XPlus to scopehal...it's not quite that straightforward, lots of protocol barfs. I guess Siglent came to a bit of a fork in the road with LeCroy.
<d1b2>
<mubes> Oh dear, had a quick punt at adding SDS2000XPlus to scopehal...it's not quite that straightforward, lots of protocol barfs. I guess Siglent came to a bit of a fork in the road with LeCroy.
<azonenberg>
mubes: Yes, there's an open ticket on that
<azonenberg>
mubes: Yes, there's an open ticket on that
<azonenberg>
the siglent driver has to be completely split off
<azonenberg>
the siglent driver has to be completely split off
<azonenberg>
tl;dr none of the siglent scopes except for the SDS3000 (aka wavesurfer 3000) support COM automation, as they're not windows based
<azonenberg>
tl;dr none of the siglent scopes except for the SDS3000 (aka wavesurfer 3000) support COM automation, as they're not windows based
<azonenberg>
and the lecroy driver now makes heavy use of automation calls
<azonenberg>
and the lecroy driver now makes heavy use of automation calls
<azonenberg>
i've been waiting for a siglent owner to be willing to put in the time to do the clean split
<azonenberg>
i've been waiting for a siglent owner to be willing to put in the time to do the clean split
<azonenberg>
If you're interested i'll assist to the extent practical
<azonenberg>
If you're interested i'll assist to the extent practical
<azonenberg>
Right now the siglent driver is basically bitrotted to the point of unusability on any non-windows ce based siglent scope
<azonenberg>
Right now the siglent driver is basically bitrotted to the point of unusability on any non-windows ce based siglent scope
<d1b2>
<mubes> Yup, took me about 30 mins to reach that conclusion...and it seems to be pretty easy to hang their current implementation to the level of Big Red Button. I think this one is going to be worth the investment because it'll also work for the 5000 and probably the 6000 if/when it comes out too.
<d1b2>
<mubes> Yup, took me about 30 mins to reach that conclusion...and it seems to be pretty easy to hang their current implementation to the level of Big Red Button. I think this one is going to be worth the investment because it'll also work for the 5000 and probably the 6000 if/when it comes out too.
<d1b2>
<mubes> No promises and don't rely on me cos I'm up to my hocksters in my own stuff at the moment..but I'll try and take a look.
<d1b2>
<mubes> No promises and don't rely on me cos I'm up to my hocksters in my own stuff at the moment..but I'll try and take a look.