Author Topic: Rigol DP832 - Firmware list and bugs (Read 313705 times)

RustyCaliper · « **Reply #400 on:** September 06, 2015, 05:28:54 pm »

Hey there,

wanted to upgrade my 832 to v1.14 -- but apparently I'm too dumb to find the download link on Rigols website?! Could someone please enlighten me where it can be found?

Thanks! Rusty

_Wim_ · « **Reply #401 on:** September 06, 2015, 05:37:31 pm »

You have to "ask" rigol for the firmware. To do this, you need to fill in this form: http://beyondmeasure.rigoltech.com/acton/form/1579/0012:d-0001/1/index.htm

Dazed+Confused · « **Reply #402 on:** September 06, 2015, 05:56:29 pm »

@RustyCaliper
Link was posted in post #385 of this thread and still seems to be working. I used that one with no problems.

RustyCaliper · « **Reply #403 on:** September 06, 2015, 07:12:03 pm »

Quote from: _Wim_ on September 06, 2015, 05:37:31 pm

You have to "ask" rigol for the firmware. To do this, you need to fill in this form: http://beyondmeasure.rigoltech.com/acton/form/1579/0012:d-0001/1/index.htm

Wow, THAT is pretty damn retarded. Why would they do that? At least I'm not dumb enough to find the link then :-D

Quote from: Dazed+Confused on September 06, 2015, 05:56:29 pm

@RustyCaliper
Link was posted in post #385 of this thread and still seems to be working. I used that one with no problems.

Thanks, worked as a charm, upgraded. Unfortunately I was hoping for functioanlity that would have been SO easy to add (trigger output on switch CV -> CC), but they didn't :-(

Anyways, thanks you guys, take care, Rusty

GNU_Ninja · « **Reply #404 on:** September 08, 2015, 12:27:37 pm »

I'm in the market for a programmable PSU and the Rigol DP832 was on my shortlist; But having seen all the problems listed in this thread, I may have to revise my list $:-\$

McBryce · « **Reply #405 on:** September 08, 2015, 12:34:27 pm »

I've been using my DP832 for almost a year now without encountering any problem that made me regret the purchase. It's stable, accurate and user-friendly. Other than a single un-announced reset that it decided to do shortly after updating the firmware, I've never had an issue with it.

McBryce.

_Wim_ · « **Reply #406 on:** September 08, 2015, 05:48:46 pm »

Same here. Very satisfied. I think this long thread comes from the fact that many DIY-users have this suply, hence they can report back on every little issue they find. But this is not your typical low cost Chinese power supply, its way better then that!

Howardlong · « **Reply #407 on:** September 08, 2015, 06:47:26 pm »

In general it's OK, but I had a problem that it appeared no-one else had to with over current protection (not constant current) not working consistently. To my delight it was fixed in a recent firmware fix.

As the owner of a few other bits of Rigol kit, what seems to happen is that they modify their production runs with minor hardware tweaks on boards, but then don't fully regression test their firmware across all hardware permutations. I've seen this now on the DS1000Z series of scopes and more recently the DSA815-TG spec an, there may be others. On the plus side, given time, they do seem to fix things.

5ky · « **Reply #408 on:** September 08, 2015, 08:35:15 pm »

Quote from: GNU_Ninja on September 08, 2015, 12:27:37 pm

I'm in the market for a programmable PSU and the Rigol DP832 was on my shortlist; But having seen all the problems listed in this thread, I may have to revise my list $:-\$

I wouldn't be too worried. I"ve had mine for a few years now and have not had a single problem with it. I was running stock firmware until yesterday. (mine came with v1.05) I only updated the firmware so that I could get the "classic" UI that the 832 (non A) models come with. It's been rock solid and reliable. I have an Agilent PSU that's twice the power (and price) that I stopped using once I got my Rigol one. It doesn't have a keypad and the rotary encoder's acceleration is horrendous on the Agilent, as well as the fan being super loud, so now I'm happily using my Rigol as my day-to-day PSU and I couldn't be happier.

Also, since it's related to this thread, I figured I'd offer a link to the video I made last night where I show you how to update the firmware. It's not as simple as it is on devices from other brands so I thought people who might have been apprehensive about updating firmware might get use out of this video. It definitely helps to see someone else do it first.

UPDATE: gah, is there not a way to post a link without it loading the embedded video?

neslekkim · « **Reply #409 on:** November 03, 2015, 08:14:26 pm »

Do anyone know if there is information about when the psu's are produced?, the 832A that I'm supposed ot receive have an serialnumber starting with DP8B17**, the idea was that it was supposed to be an using produced this year..

megik · « **Reply #410 on:** November 16, 2015, 12:22:56 pm »

Hello
I need your help
someone has a working script for calibration DP832 in bundles in DM3050 (DM3068) ?
that here I could not get to work

apparently it through not completed and have tested
and I did not have enough knowledge to finish it

LaurentR · « **Reply #411 on:** November 16, 2015, 05:47:49 pm »

Quote from: megik on November 16, 2015, 12:22:56 pm

Hello
I need your help
someone has a working script for calibration DP832 in bundles in DM3050 (DM3068) ?
that here I could not get to work

apparently it through not completed and have tested
and I did not have enough knowledge to finish it

Which did you try running, my Matlab script (which has had reported issues on the Rigol DMMs) or bson's Python port (which should work on the Rigol)?

Macbeth · « **Reply #412 on:** November 16, 2015, 07:31:48 pm »

Actually neither of them worked on the Rigol. I ran across an issue with the DM3058 when in Agilent command mode that Rigol still haven't resolved. This bug is not an issue with the DM3068 AFAIK. There were some more bugs in the code which I fixed but never published.

I think I will revisit and make it work using Rigol command mode instead of Agilent, and also do a Keithley script as well. Watch this space.

(This was with bsons Python version.)

megik · « **Reply #413 on:** November 17, 2015, 11:16:14 am »

Quote from: Macbeth on November 16, 2015, 07:31:48 pm

Actually neither of them worked on the Rigol. I ran across an issue with the DM3058 when in Agilent command mode that Rigol still haven't resolved. This bug is not an issue with the DM3068 AFAIK. There were some more bugs in the code which I fixed but never published.

I think I will revisit and make it work using Rigol command mode instead of Agilent, and also do a Keithley script as well. Watch this space.

(This was with bsons Python version.)

Thank you!
I would like to see it finally working scenario for Rigol

Stupid Beard · « **Reply #414 on:** December 06, 2015, 12:16:43 pm »

In case anyone is watching this still, I hacked up a python-ivi based calibration script and a keithley 2000 driver for python-ivi. See here: https://www.eevblog.com/forum/testgear/calibrating-a-dp832-with-python-ivi-%28also-a-keithley-2000-driver-for-python-ivi%29/

I had a quick look at the python-ivi code; it supports the DM3068 but it uses agilent command mode so the issue with the DM3058 would probably still be an issue.

Neuromodulator · « **Reply #415 on:** January 04, 2016, 04:10:14 am »

Is there any way to get such "classic" GUI on the 832 (non A)? I find the numbers on the 832A "classic" far easier to read than the 7 segment imitation of the 832.

Omikron · « **Reply #416 on:** February 04, 2016, 04:49:10 am »

Quote from: Neuromodulator on January 04, 2016, 04:10:14 am

Is there any way to get such "classic" GUI on the 832 (non A)? I find the numbers on the 832A "classic" far easier to read than the 7 segment imitation of the 832.

I have to agree. Does anyone know of a way to do this without trying to get a whole firmware dump from another 832A?

apelly · « **Reply #417 on:** February 04, 2016, 05:11:45 am »

Quote from: Omikron on February 04, 2016, 04:49:10 am

I have to agree. Does anyone know of a way to do this without trying to get a whole firmware dump from another 832A?

I think we're pretty sure the firmware is identical in these. Has anyone had a look for simple config jumpers? Mine isn't accessible at the moment or I'd look myself.

Maverick71 · « **Reply #418 on:** February 04, 2016, 12:50:39 pm »

Hello,

I'm unable to enable the HighRes Accuracy on the Rigol DP832.

I get the Keys from here: http://web.archive.org/web/20131215225141/http://riglol.3owl.com/
I enteres my Serial and the Option and generate the Key.
I dont use the privatekey for anything.

I tried this update several times.
First it says "Invalid Serial Number" now it says "Installation Fails"

I also tried to Enable the desired Funtctions from USB Stick.
Made preformatted TXT with serial in the first line, key on the second Line
and enter the Cursor to the third line (nothing there) and saved this file to USB Stick.
I changed the file Extension ti .LIC

I tried this updates with Firmware .08
Now Im on 1.14 from here: https://onedrive.live.com/?authkey=!AMNb1hJqvwUjoJ8&id=4648F6D014FCE0A6!545&cid=4648F6D014FCE0A6

Any Ideas for this high accuracy unlock?

Regards,
Mav

Maverick71 · « **Reply #419 on:** February 04, 2016, 02:31:19 pm »

Hello

OK, I understand I tried with the wrong Key Gen.
Now I'm on Firmware 1.14 not on 08 anymore.

Is there a working KeyGen for DP832 Model with Firmware 1.14?

Regards,
Maverick

McBryce · « **Reply #420 on:** February 04, 2016, 02:49:30 pm »

If you got the "Installation Fails" message then you've probably put the wrong key in more than 3 times. As far as I can remember, the DP832 will block all license keys now for the next 24 hours, so you'll have to leave it running for a day before you can try the correct key.

McBryce.

Maverick71 · « **Reply #421 on:** February 04, 2016, 03:05:31 pm »

Thank You, I guess I tried this Codes for more than 20 times...
I'll report tomorrow.

Regards,
Maverick

kazam · « **Reply #422 on:** February 26, 2016, 10:49:28 pm »

Hi,

I'm observing some strange behavior on my DP832, FW:1.14. This is the output given from the cal program:

Starting Voltage: connect the DMM VOLTAGE inputs to PSU channel 1
Press Enter
Running DAC-V for channel 1
DACV Ch:1 - Step:0 - Nom:0.200000V - DMM:0.018149V
DACV Ch:1 - Step:1 - Nom:0.500000V - DMM:0.318225V
DACV Ch:1 - Step:2 - Nom:1.200000V - DMM:1.016125V
DACV Ch:1 - Step:3 - Nom:2.000000V - DMM:1.811329V
DACV Ch:1 - Step:4 - Nom:3.200000V - DMM:3.001484V
DACV Ch:1 - Step:5 - Nom:4.100000V - DMM:3.891267V
DACV Ch:1 - Step:6 - Nom:5.200000V - DMM:4.980547V
DACV Ch:1 - Step:7 - Nom:6.900000V - DMM:6.671674V
DACV Ch:1 - Step:8 - Nom:7.500000V - DMM:7.270375V
DACV Ch:1 - Step:9 - Nom:8.700000V - DMM:8.460897V
DACV Ch:1 - Step:10 - Nom:10.100000V - DMM:9.856518V
DACV Ch:1 - Step:11 - Nom:11.800000V - DMM:11.544770V
DACV Ch:1 - Step:12 - Nom:12.600000V - DMM:12.339850V
DACV Ch:1 - Step:13 - Nom:13.500000V - DMM:13.231560V
DACV Ch:1 - Step:14 - Nom:15.000000V - DMM:14.717630V
DACV Ch:1 - Step:15 - Nom:15.800000V - DMM:15.510480V
DACV Ch:1 - Step:16 - Nom:16.500000V - DMM:16.206660V
DACV Ch:1 - Step:17 - Nom:17.300000V - DMM:17.002720V
DACV Ch:1 - Step:18 - Nom:18.500000V - DMM:18.194970V
DACV Ch:1 - Step:19 - Nom:19.100000V - DMM:18.794810V
DACV Ch:1 - Step:20 - Nom:19.900000V - DMM:19.586580V
DACV Ch:1 - Step:21 - Nom:20.200000V - DMM:19.884750V
DACV Ch:1 - Step:22 - Nom:20.800000V - DMM:20.479630V
DACV Ch:1 - Step:23 - Nom:21.800000V - DMM:21.468360V
DACV Ch:1 - Step:24 - Nom:22.400000V - DMM:22.062930V
DACV Ch:1 - Step:25 - Nom:22.700000V - DMM:22.363750V
DACV Ch:1 - Step:26 - Nom:23.900000V - DMM:23.561490V
DACV Ch:1 - Step:27 - Nom:24.300000V - DMM:23.956440V
DACV Ch:1 - Step:28 - Nom:25.700000V - DMM:25.352280V
DACV Ch:1 - Step:29 - Nom:26.900000V - DMM:26.542070V
DACV Ch:1 - Step:30 - Nom:27.900000V - DMM:27.532260V
DACV Ch:1 - Step:31 - Nom:28.500000V - DMM:28.126970V
DACV Ch:1 - Step:32 - Nom:28.900000V - DMM:28.525230V
DACV Ch:1 - Step:33 - Nom:29.800000V - DMM:29.426520V
DACV Ch:1 - Step:34 - Nom:30.200000V - DMM:29.827590V
DACV Ch:1 - Step:35 - Nom:32.000000V - DMM:31.614140V
Running ADC-V for channel 1
ADCV Ch:1 - Step:0 - Nom:0.000000V - DMM:0.000032V
ADCV Ch:1 - Step:1 - Nom:0.050000V - DMM:0.049575V
ADCV Ch:1 - Step:2 - Nom:0.100000V - DMM:0.099314V
ADCV Ch:1 - Step:3 - Nom:0.500000V - DMM:0.499981V
ADCV Ch:1 - Step:4 - Nom:1.000000V - DMM:0.999880V
ADCV Ch:1 - Step:5 - Nom:5.000000V - DMM:4.999513V
ADCV Ch:1 - Step:6 - Nom:10.000000V - DMM:9.999473V
ADCV Ch:1 - Step:7 - Nom:12.800000V - DMM:12.799610V
ADCV Ch:1 - Step:8 - Nom:20.000000V - DMM:20.000810V
ADCV Ch:1 - Step:9 - Nom:30.000000V - DMM:30.000650V
ADCV Ch:1 - Step:10 - Nom:32.000000V - DMM:32.002000V

The DAC values seem a little whacky and sure enough, after I calibrate the voltages are spot on but the readouts are way off. It will measure 2.002V when set to 2.000V but the DP832 will read back and display 2.961V.

I haven't written the cal data so restarting brings me back to decent values.

Insights?

/K

Macbeth · « **Reply #423 on:** February 26, 2016, 11:00:18 pm »

Kazam, you don't say what cal program you are using or what your equipment is?

I had similar results when using my (modified) version of bsons python script. I put the issue down to the script not waiting long enough for the PSU to settle after changing its settings, but I didn't investigate as I gave up after encountering the DM3058E bugs (which Rigol have still not fixed).

I just chose not to commit the calibration when I had obviously faulty results.

kazam · « **Reply #424 on:** February 26, 2016, 11:12:10 pm »

To clarify:

Using Matlab script posted earlier in thread. modified to use my Keithley DMM7510.
I checked the strings and values manually when debugging the script and it all checks out.
I have tried different wait times between setting the output of the DP832 and reading the voltage back. It makes very little difference and now I'm using 5 seconds. Still getting really weird data.

Yes, I'm not committing any cal data at the end so no harm done. Just annoying!

/K

Quote from: Macbeth on February 26, 2016, 11:00:18 pm

Kazam, you don't say what cal program you are using or what your equipment is?

I had similar results when using my (modified) version of bsons python script. I put the issue down to the script not waiting long enough for the PSU to settle after changing its settings, but I didn't investigate as I gave up after encountering the DM3058E bugs (which Rigol have still not fixed).

I just chose not to commit the calibration when I had obviously faulty results.


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Rigol DP832 - Firmware list and bugs (Read 313705 times)

Share me