You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The waveform I see on the oscilloscope is different from the waveform in glscopeclient. The timebase settings also differ between glscopeclient and the oscilloscope; glscopeclient won't allow me to configure the timebase settings that I see on the scope.
glscopeclient waveform:
Oscilloscope waveform:
glscopeclient timebase settings (set to maximum possible sample rate, memory depth):
Oscilloscope timebase settings:
The text was updated successfully, but these errors were encountered:
Reducing the memory depth manually (on the scope) to 12.5 Mpts worked. My assumption is that glscopeclient doesn't support 500 Mpts memory depth per channel.
Max memory depth in the Siglent driver is I think 12.5M; the waveform download on Siglent scopes is incredibly slow with deep memory so we add an early-out to avoid timeouts on these huge waveforms.
@mubes, can we improve failure behavior here in the driver if the user has deep memory enabled when connecting to a scope where memory depth is higher than the driver allows?
This issue is probably obsolete as anyway glscopeclient is replaced by ngscopeclient which probably does not have such limitation @dan-gies Could you test with ngscopeclient ?
System Info:
Glscopeclient version: 0.1-0ec5f20
OS: Windows 10
Oscilloscope: Siglent SDS6204A
Probe: SAP2500D
Description:
The waveform I see on the oscilloscope is different from the waveform in glscopeclient. The timebase settings also differ between glscopeclient and the oscilloscope; glscopeclient won't allow me to configure the timebase settings that I see on the scope.
glscopeclient waveform:
Oscilloscope waveform:
glscopeclient timebase settings (set to maximum possible sample rate, memory depth):
Oscilloscope timebase settings:
The text was updated successfully, but these errors were encountered: