Author Topic: Who's buying a Rigol product this weekend?  (Read 704 times)

0 Members and 1 Guest are viewing this topic.

Offline RigolOnline

  • Contributor
  • !
  • Posts: 32
  • Country: gb
Who's buying a Rigol product this weekend?
« on: September 15, 2017, 10:07:24 am »

The weekend in nearly upon us and we now have a bit of time to do our own thing, so on that basis, who has plans on buying a Rigol product this weekend, and more specifically what product?

The DS1054Z is still immensely popular with our customers but what else is grabbing your attention?

Do you think the carry cases are worthwhile? And what's your thoughts on the two new products that Rigol have released? DS2102E & DS2202E.

Who's looking for a Rigol Power Supply? Any new products that you would like to see Rigol release?

Have a good weekend everyone!


Offline Karel

  • Super Contributor
  • ***
  • Posts: 1477
  • Country: 00
Re: Who's buying a Rigol product this weekend?
« Reply #1 on: September 15, 2017, 11:05:40 am »
... what else is grabbing your attention?

Dear Mike,

A couple of years ago, we bought Rigol's flagship: the DS6104, including most options (uart, spi, i2c decoding etc.).
When we started to use the remote connection (via LAN), we hit the following three bugs:

bug no. 1: (reported at, and confirmed by, Rigol in October 2015)

When I run this software: and select LAN connection,
I get randomly the response: "command error". This blocks the connection for 5 seconds and a timeout occurs.
This happens randomly, and when it happens, it does after sending different commands.
So, it's not related to one and the same command. Sometimes the program runs fine for minutes.

bug no. 2: (reported at, and confirmed by, Rigol in Januari 2017)

Apply a squarewave of 1KHz to channel 1.
Set triggering to normal, rising edge.
Set the memory depth to 1.4Mpts.
Acquire the signal, then set the scope to STOP mode.

Download the waveform in RAW mode, format BYTE.

When you observe the downloaded waveform, the triggerpoint is
shifted about 460 nanoSec.

bug no. 3: (reported at, and confirmed by, Rigol in December 2016)

When setting  the treshold for the UART serial decoding,
it seems to work fine.
But when asking for the threshold setting, the value is always 10% of
the actual value.
This bug happens when the probe attenuation is set to 10:1.

These bugs are still unresolved and make it impossible for us to use the remote connection.

So, when we talk about Rigol, this is what grabs my attention.

Have a nice weekend.
The following users thanked this post: hans, mike1305, BradC, nugglix, MrW0lf

Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo