Author Topic: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)  (Read 110264 times)

0 Members and 1 Guest are viewing this topic.

Offline JohnPi

  • Regular Contributor
  • *
  • Posts: 158
  • Country: us
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #325 on: September 03, 2018, 12:36:03 pm »
I looked through that code (I don't have a convenient system to build/run it on)-- it appears to download either 1200 or 250000 bytes. My problem is when downloading 8244+n*64 only -- 250000 is not an issue in that.

My problem arose when I was specifically downloading different lengths in the range below 30000; it arose from old habits of being frugal with memory. I changed my own code to download 8000 byte chunks, but I guess I could just download a single 30000 byte block and truncate it.

In the end, I don't know if this ia Rigol or a pyvisa bug.

p.s. I updated my example above to select the USB instrument more easily.
 

Offline MarkF

  • Super Contributor
  • ***
  • Posts: 2522
  • Country: us
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #326 on: September 03, 2018, 12:54:33 pm »
It looks like you're trying to use a USB connection?

I don't know if it will have any effect.  But, you could try changing the OS low level receive buffer size.  The default size for a LAN connection would be different than a USB connection.
 

Offline JohnPi

  • Regular Contributor
  • *
  • Posts: 158
  • Country: us
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #327 on: September 03, 2018, 04:19:50 pm »
@PeDre - thanks for checking. I see it works for you at 8244. What is that program you used ?

When I run my pyvisa program with different values for chunk_size:
DS1054Z = GPIB.open_resource([_ for _ in GPIB_Resources if re.search('^USB.*:DS.*INSTR$', _)][0],chunk_size=3000)

it doesn't appear to fail as often, but there are definite slow downs at some points (watch the results scroll by) -- they appear to be at 64-count intervals. In my case, starting at 8200:
for NPOINTS in range(8200,30100):# fails at 8244 first

gives a slowdown (but not a fail) at 8226.

3.6.5 |Anaconda, Inc.| (default, Mar 29 2018, 13:32:41) [MSC v.1900 64 bit (AMD64)]
visa 1.9.1
 

Offline JohnPi

  • Regular Contributor
  • *
  • Posts: 158
  • Country: us
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #328 on: September 03, 2018, 04:42:22 pm »
It looks like you're trying to use a USB connection?

I don't know if it will have any effect.  But, you could try changing the OS low level receive buffer size.  The default size for a LAN connection would be different than a USB connection.

Yes, USB. I have tried with the LAN with longer lengths with no problems. I haven't tried this code over the LAN -- will do (it appears you have to reboot the scope to switch from USB to LAN).

-- update: - I can't get my pyvisa to work over the LAN. Anyone know the magic resource name ? IP = 10.1.0.54, port = 5555
Code: [Select]
GPIB = visa.ResourceManager()
DS1054Z = GPIB.open_resource('TCPIP0::10.1.0.54::5555::INSTR')
print("DS1054Z:", DS1054Z.query("*IDN?"))
fails

Don't know how to change the OS buffer size. There is a chunk_size option in pyvisa which has an impact -- it moves the starting point of the issue around, but doesn't eliminate the issue.
« Last Edit: September 03, 2018, 05:17:03 pm by JohnPi »
 

Offline Hauke

  • Newbie
  • Posts: 7
  • Country: de
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #329 on: December 29, 2018, 07:15:48 pm »
Hi all,

for me the password login rigollan/111111 or test/111111 never worked, and since the headline post of this thread states that this problem should be gone with the current firmware version, I updated and tried again; no success. But this finally worked for me:

  • Connect to the scope via http://[IP-Address]
  • Select "Security"
  • Enter as old password: 111111
  • Enter as new password again: 111111 (twice)
  • Confirm --> Success message
  • log in with any username with four or less letters, pw 111111 --> Works!

So I used as username test, blah, 1234, a - all worked. 12345 or rigollan or rigolan did not work.

No idea why my scope behaves differently as others, but from the forum I find others that used test and blah also successfully.

Whatever - /me is happy now.

Cheers

Hauke
 

Offline ankerwolf

  • Regular Contributor
  • *
  • Posts: 58
  • Country: at
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #330 on: January 01, 2019, 03:39:47 pm »
Hello,
I posted sometimes:

With the last Version 00.04.04.03.05 the login is now working with:
username: rigolan
password: 111111

LG Wolfgang
 

Offline Hauke

  • Newbie
  • Posts: 7
  • Country: de
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #331 on: January 04, 2019, 06:17:15 pm »
Hi Wolfgang,

sorry to say: But not for me. It is as I write: any four letter (or shorter) username works, anything 5 digits plus: No success.

Or are we talking about different logins? I refer to accessing http://[IP of the scope]/, and then hitting "Network settings". Where do you refer to?

Cheers

Hauke
 

Offline Karel

  • Super Contributor
  • ***
  • Posts: 2214
  • Country: 00
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #332 on: May 24, 2019, 11:04:51 am »
DS1104Z-S, Software 04.04.SP4

Since the firmware update to 04.04.SP4, I cannot read waveform data with more than 10 MB via SCPI command.
The 6 MB work, the 12 MB data are aborted at 10 MB. The oscilloscope will then stop sending data. But you can read in data afterwards without any problems. The oscilloscope did not get stuck.
It worked with the previous software 04.04.SP3.

Can anyone confirm that?

Peter

Does the same happen when using DSRemote?
At this moment I don't feel like upgrading the firmware of the scope...
 

Online RoGeorge

  • Super Contributor
  • ***
  • Posts: 6146
  • Country: ro
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #333 on: May 24, 2019, 11:41:18 am »
Can anyone confirm this error?

No, because you gave no "Steps to reproduce" the error.



Can anyone confirm that?

No, because you still didn't give any "Steps to reproduce" the failure.
« Last Edit: May 24, 2019, 11:44:28 am by RoGeorge »
 

Offline Karel

  • Super Contributor
  • ***
  • Posts: 2214
  • Country: 00
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #334 on: May 25, 2019, 07:05:16 am »
DSRemote works with the LAN connection, very fast even. The USB connection doesn't work for me.

From the webpage of DSRemote:

Quote
Unfortunately, there's a bug in the firmware of the scope that causes connection problems
when your computer uses an xHCI host controller (USBv3.x).
Computers with an EHCI host controller (USBv2) will work fine.
Rigol has been informed about this firmware bug. They acknowledged the bug and said
they have no plans to fix it.
So, if DSRemote generates the error message "Can not read from device", check the following.
Open a terminal and enter

  echo "*IDN?" > /dev/usbtmc0; cat /dev/usbtmc0

If it response like this:

  RIGOL TECHNOLOGIES,DS1104Z,DS1ZA17040xxxx,00.04.04.SP3
  cat: /dev/usbtmc0: Connection timed out

the connection is ok. If not, there's a problem. Check the following:

  dmesg | grep -i xhci | less

This will show you if your computer has an xhci host controller.

  dmesg | grep -i ehci | less

This will show you if your computer has an ehci host controller.
Some computers have both. In that case use an USBv2 port, not an USBv3.x port (blue).

p.s.: not all xHCI host controllers causes connection problems. It depends on the brand and
model of the chip on the motherboard of your computer.
The cause is that Rigol presents itself as an USB 2.0 High Speed device but it uses a packetsize
of 64 bytes. The USB 2.0 protocol specification dictates that highspeed connections MUST use a
packetsize of 512 bytes. Now, some USB host controller chips are "forgiving" and accept the smaller
packetsize. Some USB host controllers are less forgiving and don't accept the too small packets.
You can see the packetsize protocol violation of Rigol when you type dmesg in a terminal after you
connected the scope:
Code: [Select]
  usb 3-2: new high-speed USB device number 4 using ehci-pci
  usb 3-2: config 1 interface 0 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64
  usb 3-2: config 1 interface 0 altsetting 0 bulk endpoint 0x3 has invalid maxpacket 64
  usb 3-2: New USB device found, idVendor=1ab1, idProduct=04ce
  usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  usb 3-2: Product: DS1000Z Series
  usb 3-2: Manufacturer: Rigol Technologies.
  usb 3-2: SerialNumber: DS1ZA17040xxxx
  usbcore: registered new interface driver usbtmc
 

Offline Karel

  • Super Contributor
  • ***
  • Posts: 2214
  • Country: 00
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #335 on: May 26, 2019, 07:28:59 am »
I'm glad to hear that you found a solution/workaround.

If I may say so, the firmware of the DS1000Z is a big unreliable mess.
(But still, a great value hobbyists scope for an excellent price.)
 
The following users thanked this post: PeDre

Online RoGeorge

  • Super Contributor
  • ***
  • Posts: 6146
  • Country: ro
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #336 on: May 27, 2019, 11:46:15 am »
SCPI commands takes time to execute.  Pushing too many commands at once, or too many one by one but too fast, might not work.

There are ready/busy and/or OK/error SCPI indicators, as words or as bits, that tells the status of the instrument.  The status indicators will tell whether the instrument is ready or not to process the next SCPI command(s).

Offline Karel

  • Super Contributor
  • ***
  • Posts: 2214
  • Country: 00
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #337 on: May 27, 2019, 03:38:31 pm »
SCPI commands takes time to execute.  Pushing too many commands at once, or too many one by one but too fast, might not work.

There are ready/busy and/or OK/error SCPI indicators, as words or as bits, that tells the status of the instrument.  The status indicators will tell whether the instrument is ready or not to process the next SCPI command(s).

I wrote the USB-TMC protocol in my program myself and tested it against several devices. I also programmed it for a PIC18F, so that I can test everything as good as possible.
The Rigol DS1000Z does not stick to the standard. You can query status bits, but their value is not updated, or not supported at all. The status byte in interrupt transfer is always zero. The MAV bit is ignored and so on.
 And that with all my five Rigol devices.

Peter

I can confirm that. Unfortunately...
 

Offline rob040

  • Contributor
  • Posts: 38
  • Country: nl
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #338 on: August 12, 2019, 11:30:35 am »
Not sure if every DS1000Z owner is following/reading all related threads, but to keep this one a little bit up-to-date, the latest SW is now:

v00.04.04.04.03  2019/05/30
- Fixed the wave error when STOP and changing Timebase


 
The following users thanked this post: frozenfrogz

Offline frozenfrogzTopic starter

  • Frequent Contributor
  • **
  • Posts: 936
  • Country: de
  • Having fun with Arduino and Raspberry Pi
Re: Rigol DS1000Z series buglist continued (from: 00.04.04.03.02)
« Reply #339 on: August 12, 2019, 11:34:29 am »
Sorry, I have been pretty busy lately and did not follow the forums much.

I will update the OP with links to the latest firmware. Can someone tell what bugs have been fixed (that are still listed as bugs) so I can put it into the OP also?

Thank you!
« Last Edit: August 12, 2019, 11:58:54 am by frozenfrogz »
He’s like a trained ape. Without the training.
 

Offline BravoV

  • Super Contributor
  • ***
  • Posts: 7547
  • Country: 00
  • +++ ATH1
« Last Edit: December 28, 2019, 09:02:36 pm by BravoV »
 
The following users thanked this post: I wanted a rude username

Offline rob040

  • Contributor
  • Posts: 38
  • Country: nl
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #341 on: October 29, 2021, 04:03:51 pm »
The latest update was already on the Chinese website for some time, but now also available in the US, version 00.04.05.02.00!

v00.04.05.02.00  2021/07/24
     - Version Updated.

[History]
-------------
v00.04.05.01.00  2021/06/01
     - Modify the vertical Display.
   
v00.04.05.00.00  2020/12/29
     - Add and modify some measurement functions
     - Modification of math problem
     - Modify some SCPI instruction errors
     - Modify some trigger problems.


I haven't tested it yet.

Edit: On the Chinese website it's already v00.04.05.02.02...  :palm:
« Last Edit: October 29, 2021, 04:09:08 pm by rob040 »
 
The following users thanked this post: DC1MC, Adrian_Arg., Deichgraf

Offline Adrian_Arg.

  • Frequent Contributor
  • **
  • Posts: 420
  • Country: ar
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #342 on: October 30, 2021, 12:30:01 am »
v00.04.05.01.00  2021/06/01
     - Modify the vertical Display.??

    -Modification of math problem ??

What did they modify? someone explain it to me! |O
 

Offline MarkF

  • Super Contributor
  • ***
  • Posts: 2522
  • Country: us
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #343 on: October 30, 2021, 01:59:45 am »
v00.04.05.01.00  2021/06/01
     - Modify the vertical Display.??

    -Modification of math problem ??

What did they modify? someone explain it to me! |O

More detailed change history:
https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg3745558/#msg3745558
 
The following users thanked this post: Adrian_Arg.

Offline Adrian_Arg.

  • Frequent Contributor
  • **
  • Posts: 420
  • Country: ar
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #344 on: October 30, 2021, 02:54:55 pm »
I read the list from version 00.04.05.02.00 onwards, and it scares me to update, it corrects a lot of errors, but what it can create scares me more  >:D, for something they still did not correct the 24bit deep, they do not want to think about what would happen !! :-//
 

Offline DC1MC

  • Super Contributor
  • ***
  • Posts: 1882
  • Country: de
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #345 on: October 30, 2021, 03:10:58 pm »
I read the list from version 00.04.05.02.00 onwards, and it scares me to update, it corrects a lot of errors, but what it can create scares me more  >:D, for something they still did not correct the 24bit deep, they do not want to think about what would happen !! :-//

I have loaded and tested the firmware, from calibration, to licenses (all active) to signal shapes compared with previously saved values, to measurement. I can tell that there are no visible regressions.

 Cheers,
 DC1MC
 
The following users thanked this post: Adrian_Arg.

Offline Adrian_Arg.

  • Frequent Contributor
  • **
  • Posts: 420
  • Country: ar
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #346 on: October 30, 2021, 03:49:56 pm »
I read the list from version 00.04.05.02.00 onwards, and it scares me to update, it corrects a lot of errors, but what it can create scares me more  >:D, for something they still did not correct the 24bit deep, they do not want to think about what would happen !! :-//

I have loaded and tested the firmware, from calibration, to licenses (all active) to signal shapes compared with previously saved values, to measurement. I can tell that there are no visible regressions.

 Cheers,
 DC1MC

Friend, I installed the firmware, it was installed correctly, the yellow trace and the others were left above the marker, and it does not allow to calibrate, it gives an error at 5 minutes, how degraded?
 

Offline DC1MC

  • Super Contributor
  • ***
  • Posts: 1882
  • Country: de
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #347 on: October 30, 2021, 03:55:29 pm »
...
Friend, I installed the firmware, it was installed correctly, the yellow trace and the others were left above the marker, and it does not allow to calibrate, it gives an error at 5 minutes, how degraded?


I've installed it on a MSO1074Z (I can provide pictures if needed), I was having exactly zero issues: the procedure was:
Installing -> Power Cycling -> Factory Reset -> Calibration -> Other tests regarding the the behavior.

Everything went A-OK

EDIT: The firmware was taken from here: https://www.rigolna.com/firmware/ and I've used the DS1000Z version, suitable for my scope.

DC1MC
« Last Edit: October 30, 2021, 03:58:27 pm by DC1MC »
 
The following users thanked this post: Adrian_Arg.

Offline Adrian_Arg.

  • Frequent Contributor
  • **
  • Posts: 420
  • Country: ar
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #348 on: October 30, 2021, 04:21:05 pm »
On the sixth try I calibrate, I really don't know what happened to the baby :(, gracias DC1MC :-+
 

Offline DC1MC

  • Super Contributor
  • ***
  • Posts: 1882
  • Country: de
Re: Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
« Reply #349 on: October 30, 2021, 04:56:46 pm »
On the sixth try I calibrate, I really don't know what happened to the baby :(, gracias DC1MC :-+
No hay de qué.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf