Products > Test Equipment
Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
<< < (65/74) > >>
JohnPen:
If you select any single channel, no inputs, and with triggering set for that same channel you get the full 1GSa/s and 24M Mem depth available.  Move just the trigger source to a different channel (not enabled/displayed) and the sample rate changes to 500 MSa/s and 12M Mem depth.  So both previous comments are correct.  if you enable CH1 or (2) and Ch3 or (4) together and trigger off either of those live channels you get 500 MSa/s and 12M Mem depth as expected.  However if you select the trigger to be either of the disabled channels the sample rate drops to 256 MSa/s and 6M Mem depth.  So I suppose it could be a bug but then why would you trigger off a waveform/trace you are not displaying?
metrologist:
You may want to use a channel for triggering but not care to see the triggering signal. You are still using the channel, just not displaying the data.
RoGeorge:

--- Quote from: JohnPen on May 17, 2018, 05:50:55 pm ---If you select any single channel, no inputs, and with triggering set for that same channel you get the full 1GSa/s and 24M Mem depth available.
--- End quote ---

That was it, the trigger source must be on the same channel (or on AC Line). Didn't know that.

I noticed that the trigger still works even when set on a disabled channel, so it might be useful to trigger on a rare event from another channel, then sample a different signal with full 24 Mpoints, but I wouldn't call that a bug. I think that was a design choice. In my case it just happened that my trigger was left on CH2 from some previous measurements. My bad, sorry.

Thank you all for taking the time to test this.
JohnPi:
I have a new bug (I posted this as a separate topic earlier; I'll try to delete that post):
I am trying to read binary waveforms from my 1054Z using pyvisa over USB. Using sockets over LAN (not pyvisa) works. I have a problem when reading certain specific lengths of data from the instrument -- specifically lengths of 8244 and increments of 64 beyond; using MDEPTH of 30000. I don't know if the issue is in the instrument or pyvisa. I have filed a ticket at https://github.com/pyvisa/pyvisa/issues/354 also. I have tried pyvisa 1.9.1, 1.9.0 & 1.8. My 1054Z is unlocked to 1104Z. This is the *IDN? RIGOL TECHNOLOGIES,DS1104Z,DS1ZA20100****,00.04.04.SP3

If anyone has the same setup, perhaps with different software/firmware versions, I would appreciate if you could run this example and report:

--- Code: ---import visa
import numpy as np
import sys
import re

print(sys.version)
print("visa", visa.__version__)
#visa.log_to_screen()

GPIB = visa.ResourceManager()
GPIB_Resources = GPIB.list_resources()
for resource in GPIB.list_resources(): print(resource) # list instruments -- selects the 1054Z in the next line
DS1054Z = GPIB.open_resource([_ for _ in GPIB_Resources if re.search('^USB.*:DS.*INSTR$', _)][0])
print("DS1054Z:", DS1054Z.query("*IDN?"))

DS1054Z.write(":WAV:FORMAT BYTE;:WAV:MODE RAW;:SYSTEM:BEEPER OFF")
DS1054Z.write(":ACQUIRE:MDEPTH 30000")
DS1054Z.write(":STOP")
err=0

#for NPOINTS in range(20010,30100):
for NPOINTS in range(8200,30100):# fails at 8244 and increments of 64 beyond
  print(NPOINTS, end='')
  err+=1 
  DS1054Z.write(":WAV:START 1;:WAV:STOP %i;:WAV:DATA?" % NPOINTS)
  print(">",DS1054Z.read_bytes(11),"<", end='') # Contains '#90000ddddd'
  try:
    CURVE1 = np.frombuffer(DS1054Z.read_bytes(NPOINTS), dtype='b')
  except:
    print("\nError at", NPOINTS, " after ", err)
    err=0
  print(len(CURVE1), "chars")
  DS1054Z.read_bytes(1) # trailing '\n'

--- End code ---

This tests reading lengths from 8200 on in increments of 1. I see fails like this:

--- Code: ---8241> b'#9000008241' <8241 chars
8242> b'#9000008242' <8242 chars
8243> b'#9000008243' <8243 chars
8244> b'#9000008244' <
Error at 8244  after  8243
8243 chars
8245> b'#9000008245' <8245 chars
8246> b'#9000008246' <8246 chars
8247> b'#9000008247' <8247 chars
--- End code ---

and filtered, the patterns looks like:


--- Code: ---Error at 8244  after  8243
Error at 8308  after  64
Error at 8372  after  64
Error at 8436  after  64
Error at 8500  after  64
Error at 8564  after  64
Error at 8628  after  64
Error at 8756  after  128
Error at 8820  after  64
Error at 8884  after  64
Error at 8948  after  64
Error at 9012  after  64
Error at 9076  after  64
Error at 9140  after  64
Error at 9268  after  128
Error at 9332  after  64
Error at 9396  after  64
--- End code ---

Has anyone seen anything similar to this ?
Karel:

--- Quote from: JohnPi on September 02, 2018, 08:05:51 pm ---I have a new bug (I posted this as a separate topic earlier; I'll try to delete that post):
I am trying to read binary waveforms from my 1054Z using pyvisa over USB. Using sockets over LAN (not pyvisa) works. I have a problem when reading certain specific lengths of data from the instrument -- specifically lengths of 8244 and increments of 64 beyond; using MDEPTH of 30000. I don't know if the issue is in the instrument or pyvisa. I have filed a ticket at https://github.com/pyvisa/pyvisa/issues/354 also. I have tried pyvisa 1.9.1, 1.9.0 & 1.8. My 1054Z is unlocked to 1104Z. This is the *IDN? RIGOL TECHNOLOGIES,DS1104Z,DS1ZA20100****,00.04.04.SP3

--- End quote ---

Are you claiming that you have found a new bug in the scope's firmware?
I'm asking because DSRemote seems to work fine when downloading binary waveforms via USB.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod