<d1b2>
(errno=11, Resource temporarily unavailable) [SCPISocketTransport::ReadRawData] Failed to get 2 bytes [SiglentSCPIOscilloscope::ProcessAnalogWaveform] V_Gain=0.000260, V_Off=0.000000, interval=50000000.000000, h_off=0.000000, h_off_frac=0.000000, datalen=80000 [SiglentSCPIOscilloscope::AcquireData] Waveform download and processing took 15389.811 ms
<d1b2>
<hansemro> :TRIG:STOP is a documented command present on older firmwares whereas :TRIG:MODE STOP was never documented. Closest would be TRIG_MODE STOP in 1xxxX/2000X models
<azonenberg>
Hmm, that code likely came from the older driver then
<azonenberg>
and since it worked, nobody ever noticed the command wasnt supposed to be available :p
<d1b2>
<hansemro> Oh interesting, TRIG_MODE STOP does not work also (which would break backwards comparability)
<d1b2>
<hansemro> Well, backwards compatibility was never advertised so whatever
<d1b2>
<hansemro> Update: 8-bit ADC mode works fine. 10-bit mode is broken due to incorrectly applying hdSizeWorkaround (which multiplies data length to fetch by 2). Issue was caused by 1.6.2R5 firmware updating changing the version format reported by *IDN? which broke SDS2000X+ version parser...
<d1b2>
<hansemro> *IDN? version now reports 5.4.0.1.6.2R5 but we expected 5.4.1.6.2R5
<d1b2>
<azonenberg> oh fun lol
<_whitenotifier-3>
[scopehal] hansemro opened pull request #875: Siglent: Replace :TRIG:MODE STOP with :TRIG:STOP; handle new SDS2000X+ version format - https://github.com/ngscopeclient/scopehal/pull/875
<_whitenotifier-3>
[stm32-cpp] azonenberg cf9eb11 - Initial STM32H735 MDMA support (WIP)
<d1b2>
<246tnt> @attiegrande BTW, all my scope schenanigans today were because I wanted to check HiSLIP and see if that provided any speed benefits, but now I exhausted my free time just updating the scope to a version that supports it 😅
<d1b2>
<attiegrande> gah! 😢 glad you got the firmware updated at least! 😂
<d1b2>
<azonenberg> ooh hislip support has been on the wishlist for a very long time
<d1b2>
<azonenberg> i havent had access to a scope that supported it to dev against
<d1b2>
<246tnt> Yeah, here I wanted to just do some quick tests see if there was any large perf benefit to it with my particular scope.