Products > Test Equipment
Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
frozenfrogz:
--- Quote from: RoGeorge on October 28, 2017, 10:34:56 am ---I wouldn't mix the 'bugs list' with the 'wish list'
--- End quote ---
That is what I meant with the OP needing some sorting out and reformatting.
The bug list will be reorganized by severity / urgency and quirky feature issues that are not real bugs have to be moved into a separate list - maybe as wish list items (that I had not touched yet :) )
Karel:
--- Quote from: RoGeorge on October 28, 2017, 10:34:56 am ---8 divisions on the vertical screen is not a bug.
--- End quote ---
That was not the issue. Nobody here, including me, cares about the number of vertical divisions.
The issue is/was that the scopes display isn't showing the complete waveform as captured by the adc,
i.e. the dynamic range is (unnecessary) limited.
lundmar:
--- Quote from: RoGeorge on September 07, 2017, 11:27:36 pm ---
Now, try this:
--- Code: ---:WAV:STAR 1201
:WAV:STAR 120
:syst:err?
--- End code ---
That's it, after the last ':SYST:ERR?' SCPI hangs, and no other SCPI commands will work until the next power on.
Later edit:
It would be useful if anybody else can reproduce this, please. Does your DS1000Z hangs, too?
--- End quote ---
I can confirm that this sequence of SCPI commands results in the ":syst:err?" command hanging. I can also confirm that the hanging command ends up blocking the telnet/nc connection on port 5555.
That being said, the best way to fire SCPI commands to any LXI enabled device is to use tools that use the VXI11 protocol to communicate/handle the commands. In case of the hanging command, using the VXI11 protocol simply results in the command timing out and then you can continue sending commands - no need to restart the instrument. As demonstrated here using the wonderful/fantastic/amazing lxi-tools:
--- Code: ---$ lxi scpi --address 192.168.1.210 --timeout 5 --script crash-test.scpi
Connected to 192.168.1.210
Running script crash-test.scpi
:WAV:MODE:NORM
:syst:err?
-113,"Undefined header; keyword cannot be found"
:WAV:STAR 1201
:WAV:STAR 120
:syst:err?
Error: Read error (timeout)
Error: Failed to receive message
*IDN?
RIGOL TECHNOLOGIES,DS1104Z,DS1ZA171206207,00.04.04.SP3
--- End code ---
With nc/telnet you don't get any timeout management etc. - it is less robust and it results in locking up your instrument when you hit buggy commands.
RoGeorge:
--- Quote from: Karel on October 28, 2017, 12:34:22 pm ---
--- Quote from: RoGeorge on October 28, 2017, 10:34:56 am ---8 divisions on the vertical screen is not a bug.
--- End quote ---
The issue is/was that the scopes display isn't showing the complete waveform as captured by the adc,
i.e. the dynamic range is (unnecessary) limited.
--- End quote ---
"8 divisions" is just a bad name I choose in order to refer to your findings, I understand the complain is about why keeping some margins outside the viewing area. Sorry about the bad name I used. What I am trying to say is that it's not a bug.
A bug is something unintended, a side effect that the designer didn't planed for. Your findings is not something unintended by design. It was intentionally designed and implemented to be exactly how it is now, so not a bug.
--- Quote from: lundmar on October 28, 2017, 10:57:45 pm ---...the best way to fire SCPI commands to any LXI enabled device is to use tools that use the VXI11 protocol to communicate/handle the commands. In case of the hanging command, using the VXI11 protocol simply results in the command timing out and then you can continue sending commands - no need to restart the instrument.
...
With nc/telnet you don't get any timeout management etc. - it is less robust and it results in locking up your instrument when you hit buggy commands.
--- End quote ---
That's a very interesting finding, thank you for testing the hang!
AFAIK it should work without VXI, so I will try your code in order to see what are the main differences introduced by using VXI11.
lundmar:
--- Quote from: RoGeorge on October 29, 2017, 08:50:44 am ---That's a very interesting finding, thank you for testing the hang!
AFAIK it should work without VXI, so I will try your code in order to see what are the main differences introduced by using VXI11.
--- End quote ---
No problem. I just upgraded to the latest 1000z firmware and I wanted to test the updated LXI module to make sure it is ok. Luckily nothing is really broken. It's just missing error handling that makes some specific commands hang - still something for Rigol to fix though.
If you do take lxi-tools for a test spin please install the latest versions of liblxi and lxi-tools from https://lxi.github.io - the latest versions contains new features and many bug fixes but it is now in a pretty good state. I'm quite happy with how it works. Finally we have a solid commandline tool for Linux to talk to our various instruments.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version