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

LaurentR · « **Reply #425 on:** February 26, 2016, 11:27:23 pm »

Kazam,
every time I have run the script, it has been like this or worse for the DAC.

I have no definitive insight, but my theory is that the DAC is just outputting uncalibrated values (vs. values calibrated with the current calibration), which makes sense.

Having run the script many times during development, I have anecdotal evidence that this is what happened. I have more than once written totally erroneous calibration data and the supply was then totally unusable, but, even after that, the calibration script turned up similar results. So I assume it is indeed just ignoring current calibration values altogether while running the script. And in my experience, the DAC is off by similar (noticeable) amounts during calibration, with the ADC being very close.

Laurent

kazam · « **Reply #426 on:** February 26, 2016, 11:55:51 pm »

OK, so is it safe to write this data then?

I was expecting to see the current calibration in effect before comitting and saving coefficients!

And thanks for the script, BTW.

I will upload ans share my Keithley version once I make sure it works.

/K

Quote from: LaurentR on February 26, 2016, 11:27:23 pm

Kazam,
every time I have run the script, it has been like this or worse for the DAC.

I have no definitive insight, but my theory is that the DAC is just outputting uncalibrated values (vs. values calibrated with the current calibration), which makes sense.

Having run the script many times during development, I have anecdotal evidence that this is what happened. I have more than once written totally erroneous calibration data and the supply was then totally unusable, but, even after that, the calibration script turned up similar results. So I assume it is indeed just ignoring current calibration values altogether while running the script. And in my experience, the DAC is off by similar (noticeable) amounts during calibration, with the ADC being very close.

Laurent

bson · « **Reply #427 on:** February 27, 2016, 03:06:59 am »

Quote from: LaurentR on February 26, 2016, 11:27:23 pm

Kazam,
every time I have run the script, it has been like this or worse for the DAC.

I have no definitive insight, but my theory is that the DAC is just outputting uncalibrated values (vs. values calibrated with the current calibration), which makes sense.

Having run the script many times during development, I have anecdotal evidence that this is what happened. I have more than once written totally erroneous calibration data and the supply was then totally unusable, but, even after that, the calibration script turned up similar results. So I assume it is indeed just ignoring current calibration values altogether while running the script. And in my experience, the DAC is off by similar (noticeable) amounts during calibration, with the ADC being very close.

Laurent

Indeed, during calibration it disables the calibration corrections, or it wouldn't be able to calibrate. After calibration and installing new calibration data it's important to power cycle the PSU or it will continue operating without calibration data. If I were to guess I'd say it loads calibration tables during power-up.

LaurentR · « **Reply #428 on:** February 27, 2016, 03:42:45 am »

I just ran the calibration program on my setup. Looks different, but not better :-)

Code: [Select]

Running DAC-V for channel 1
DACV Ch:1 - Step:0 - Nom:0.200000V - DMM:-0.110548V
DACV Ch:1 - Step:1 - Nom:0.500000V - DMM:0.189599V
DACV Ch:1 - Step:2 - Nom:1.200000V - DMM:0.883774V
DACV Ch:1 - Step:3 - Nom:2.000000V - DMM:1.677662V
DACV Ch:1 - Step:4 - Nom:3.200000V - DMM:2.875726V
DACV Ch:1 - Step:5 - Nom:4.100000V - DMM:3.772613V
DACV Ch:1 - Step:6 - Nom:5.200000V - DMM:4.859532V
DACV Ch:1 - Step:7 - Nom:6.900000V - DMM:6.556295V
DACV Ch:1 - Step:8 - Nom:7.500000V - DMM:7.156451V
DACV Ch:1 - Step:9 - Nom:8.700000V - DMM:8.348862V
DACV Ch:1 - Step:10 - Nom:10.100000V - DMM:9.744890V
DACV Ch:1 - Step:11 - Nom:11.800000V - DMM:11.444056V
DACV Ch:1 - Step:12 - Nom:12.600000V - DMM:12.240194V
DACV Ch:1 - Step:13 - Nom:13.500000V - DMM:13.133796V
DACV Ch:1 - Step:14 - Nom:15.000000V - DMM:14.624108V
DACV Ch:1 - Step:15 - Nom:15.800000V - DMM:15.419533V
DACV Ch:1 - Step:16 - Nom:16.500000V - DMM:16.115537V
DACV Ch:1 - Step:17 - Nom:17.300000V - DMM:16.911583V
DACV Ch:1 - Step:18 - Nom:18.500000V - DMM:18.105339V
DACV Ch:1 - Step:19 - Nom:19.100000V - DMM:18.707224V
DACV Ch:1 - Step:20 - Nom:19.900000V - DMM:19.505043V
DACV Ch:1 - Step:21 - Nom:20.200000V - DMM:19.800305V
DACV Ch:1 - Step:22 - Nom:20.800000V - DMM:20.398841V
DACV Ch:1 - Step:23 - Nom:21.800000V - DMM:21.389631V
DACV Ch:1 - Step:24 - Nom:22.400000V - DMM:21.989582V
DACV Ch:1 - Step:25 - Nom:22.700000V - DMM:22.289575V
DACV Ch:1 - Step:26 - Nom:23.900000V - DMM:23.482165V
DACV Ch:1 - Step:27 - Nom:24.300000V - DMM:23.879192V
DACV Ch:1 - Step:28 - Nom:25.700000V - DMM:25.280637V
DACV Ch:1 - Step:29 - Nom:26.900000V - DMM:26.476796V
DACV Ch:1 - Step:30 - Nom:27.900000V - DMM:27.470796V
DACV Ch:1 - Step:31 - Nom:28.500000V - DMM:28.067346V
DACV Ch:1 - Step:32 - Nom:28.900000V - DMM:28.462864V
DACV Ch:1 - Step:33 - Nom:29.800000V - DMM:29.346933V
DACV Ch:1 - Step:34 - Nom:30.200000V - DMM:29.744620V
DACV Ch:1 - Step:35 - Nom:32.000000V - DMM:31.525673V
Running ADC-V for channel 1
ADCV Ch:1 - Step:0 - Nom:0.000000V - DMM:-0.000376V
ADCV Ch:1 - Step:1 - Nom:0.050000V - DMM:0.049855V
ADCV Ch:1 - Step:2 - Nom:0.100000V - DMM:0.100064V
ADCV Ch:1 - Step:3 - Nom:0.500000V - DMM:0.500868V
ADCV Ch:1 - Step:4 - Nom:1.000000V - DMM:0.999522V
ADCV Ch:1 - Step:5 - Nom:5.000000V - DMM:4.998767V
ADCV Ch:1 - Step:6 - Nom:10.000000V - DMM:9.999298V
ADCV Ch:1 - Step:7 - Nom:12.800000V - DMM:12.799996V
ADCV Ch:1 - Step:8 - Nom:20.000000V - DMM:19.999685V
ADCV Ch:1 - Step:9 - Nom:30.000000V - DMM:30.002926V
ADCV Ch:1 - Step:10 - Nom:32.000000V - DMM:31.999284V

bson · « **Reply #429 on:** February 27, 2016, 04:50:51 am »

Quote from: LaurentR on February 27, 2016, 03:42:45 am

I just ran the calibration program on my setup. Looks different, but not better :-)

Code: [Select]
Running DAC-V for channel 1 DACV Ch:1 - Step:0 - Nom:0.200000V - DMM:-0.110548V

A negative voltage... How is that even possible?

LaurentR · « **Reply #430 on:** February 27, 2016, 07:22:22 am »

Quote from: bson on February 27, 2016, 04:50:51 am

Quote from: LaurentR on February 27, 2016, 03:42:45 am
I just ran the calibration program on my setup. Looks different, but not better :-)

Code: [Select]
Running DAC-V for channel 1 DACV Ch:1 - Step:0 - Nom:0.200000V - DMM:-0.110548V
A negative voltage... How is that even possible?

It's always been like that on my DP832. I assume that, just as they go to +32V internally so that they can guarantee that they can do +30V after calibration, they have to go to somewhat negative values to guarantee a good 0.

kazam · « **Reply #431 on:** February 28, 2016, 02:25:30 pm »

Success!

I just went ahead with the script and then power cycled. All readings are within 1mV.

Attaching the updated Matlab script as well with notes.

/K

kazam · « **Reply #432 on:** February 28, 2016, 02:41:44 pm »

Looking good!

/K

LaurentR · « **Reply #433 on:** February 28, 2016, 03:18:51 pm »

Looks great (making me have Keithley envy)!

Note that for the "readings within 1mV", if you do a full sweep, you'll discover the DAC is a bit all over the place in some spots. See this thread for more background:
https://www.eevblog.com/forum/testgear/noob-dac-linearity-in-the-dp832/
So across the sweep, it's actually much closer to the quoted 10mV accuracy.

kazam · « **Reply #434 on:** February 28, 2016, 07:04:19 pm »

Haha, yes. Great DMM. Highly recommend.

I did a sweep across voltages and attaching the plots. Could be useful for someone I suppose.

I did open it up and soldered a rod across the common terminals of CH2 and CH3 as well. Since I'm working with the unit I might as well do everything properly.

/K

Quote from: LaurentR on February 28, 2016, 03:18:51 pm

Looks great (making me have Keithley envy)!

Note that for the "readings within 1mV", if you do a full sweep, you'll discover the DAC is a bit all over the place in some spots. See this thread for more background:
https://www.eevblog.com/forum/testgear/noob-dac-linearity-in-the-dp832/
So across the sweep, it's actually much closer to the quoted 10mV accuracy.

kazam · « **Reply #435 on:** February 28, 2016, 07:56:28 pm »

10mV sweep included for completeness. There's some positive bias. Overall well within spec.

I'll stop spamming the thread with plots now...

/K

bson · « **Reply #436 on:** February 28, 2016, 09:48:39 pm »

Quote from: kazam on February 28, 2016, 07:56:28 pm

10mV sweep included for completeness. There's some positive bias. Overall well within spec.

I'll stop spamming the thread with plots now...

Thanks for sharing - very informative!

kazam · « **Reply #437 on:** February 28, 2016, 10:34:14 pm »

No problem!

One other finding worth mentioning is that the internal voltage measurement takes a long time to become available. On the order of 1 second. That's why I didn't bother waiting for that in the 10mV sweeps. Takes ages.

A firmware enhancement would be to sample the voltage when you request it remotely and not simply read out the currently displayed value which I think is what they're doing now. That would speed up things considerably.

Quote from: bson on February 28, 2016, 09:48:39 pm

Thanks for sharing - very informative!

Skimask · « **Reply #438 on:** April 28, 2016, 06:41:06 am »

Quote from: McBryce 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.

Leave it running as in leave power on for a good 24hrs or so?

I got 3 out of 5 keys put in before I got the "Installation Fails" message. Thought I was doing something wrong. That's what I get for being in a hurry. Maybe not so much.

P.S. Using the riglol generator on a DP832 w/ 1.08, but using the 1.09 key gen on the site.

McBryce · « **Reply #439 on:** April 28, 2016, 07:45:02 am »

Yes, if you put a wrong key in 3 times then you need to leave it running for 24 hours. It doesn't have an RTC, so the timer is only ticking when it's powered up.

McBryce.

Skimask · « **Reply #440 on:** April 28, 2016, 01:28:50 pm »

Quote from: McBryce on April 28, 2016, 07:45:02 am

Yes, if you put a wrong key in 3 times then you need to leave it running for 24 hours. It doesn't have an RTC, so the timer is only ticking when it's powered up.

McBryce.

DOH...and I was just thinking changing the date/time might work.

Skimask · « **Reply #441 on:** April 30, 2016, 06:46:51 am »

Success...after leaving it on and idling for a little over 30 hours.

staze · « **Reply #442 on:** April 30, 2016, 06:50:52 am »

So, I have a DP832 that I purchased in November from tequipment, and twice now, the unit has randomly reset on me. It's running the latest firmware, and is newer than the revision with the old crappy undersized LM317 heatsink... anyone had this happen on their unit? One of the times it did it, I thought it was due to an accidental short of the outputs, but the second time, I wasn't in my lab, and came back to the unit having it's output off... and the leads couldn't have been shorted.

Thoughts? Am I crazy, or have others seen this type of thing with their fully updated units?

Macbeth · « **Reply #443 on:** April 30, 2016, 07:40:02 am »

I've certainly seen it reset itself, and can't pin down what causes it as it is quite rare and in my case appears to have only happened when the PSU has been mains powered on and hasn't even warmed up... So far when I've left it running and come back to it a day later there have been no signs of the reset (ie. outputs switched off)

pa3bca · « **Reply #444 on:** April 30, 2016, 08:12:17 am »

I've had this once - coincidentally, last week. The unit was on for about a minute, channel 1 output enabled (5 Volt, 0.1A current limit, actual current abt 10 mA). I saw the display suddenly go off, and then the unit rebooted.
I sure hope this was a once in a (my)lifetime glitch...

staze · « **Reply #445 on:** April 30, 2016, 03:23:21 pm »

Hmm. "Good" to hear.

Let's see what we have in common then? I have all the licenses installed. The unit is plugged into the network (using DHCP for IP). I had all three outputs on, with the positive of 1 being tied to the negative of 2 (so I had output 1 supplying -12V, output 2 supplying +12V, and output 3 supplying +5V).

I have the unit on a shelf with other stuff on top and around it, but have a "decent" gap on each side to allow for airflow.

In my two cases, the outputs had been on for at least 5 minutes in the first instance, and no idea on the second instance since it happened while I was away. I've also had the unit run very successfully for hours and hours without this happening. :/

Thanks!

Macbeth · « **Reply #446 on:** April 30, 2016, 06:55:29 pm »

In my case its only happened within the first 10 minutes of powering on, even with no load or just a single low amp output. Also it happened before I riglolled up all the options and since. I've upgraded firmwares a few times and fingers crossed it doesn't happen with the latest. I'm usually connected by USB...

McBryce · « **Reply #447 on:** May 02, 2016, 08:10:58 am »

I've had this happen once as well. In my case: Latest Firmware with all options enabled. Nothing connected at all - ie: The power cable was the only cable coming from the unit. No channels were turned on. The PSU had been running for about 3 Minutes at the time from a completely cold start. That was about a 6 Months ago and has never happened since.

McBryce.

alank2 · « **Reply #448 on:** May 06, 2016, 08:56:12 pm »

I ordered a DP832, but it isn't here yet. I noticed that the video above showing an DP832A with a classic display has a regular font instead of the 7 segment style font. Is that something you can switch to on the DP832? The 7 seg are ok, but I like the real font a bit better.

Macbeth · « **Reply #449 on:** May 06, 2016, 09:15:58 pm »

@alank2, no - it's the 7 segment font only.


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

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

Share me