Rigol DP832 - Firmware list and bugs

[Macbeth]

Ok. It didn't work. Pretty obvious on first sight the code only supports the 3068, so some quick hacks to KeysightTrueVoltDmm.py
Line no, before, after:

Code: [Select]

17 known_list = ["34461A", "34465A", "34470A", "DM3068"]
known_list = ["34461A", "34465A", "34470A", "DM3068", "DM3058", "DM3058E"]

18 init_cmds = { 'DM3068' : 'CMDSet AGILENT' }
init_cmds = { 'DM3068' : 'CMDSet AGILENT', 'DM3058' : 'CMDSet AGILENT', 'DM3058E' : 'CMDSet AGILENT' } # (Yuck!)
Now the DM3058E fails the self check. It seems the Keysight/Agilent has a plus sign in its return code? - another change:

Code: [Select]

44 if r != '+0':
if r not in ['+0', '0']:
Oh dear, now it fails on the uptime query. The Rigol doesn't support this along with the internal temperature status. Insert a couple of lines to wrap around it:

Code: [Select]

57 insert if self.model() in self.have_temp_check:
61 insert return [None, None, None, None]

... ahh, now thats better, getting somewhere... things seem to be working

or maybe not...

[LaurentR]

... ahh, now thats better, getting somewhere... things seem to be working

or maybe not...

To answer your original question, no the Rigol mode had never been tested on the original Matlab script

[Macbeth]

The only issue I had with your code was that early on, you check for the presence of ":" in the device Visa addresses, but Visa supports aliases , which typically don't have ":" in the name. For instance, my 2 devices are aliased (rather imaginatively) "DP832" and "34461A".

I wondered why I couldn't use my aliases, as you can see from my last run... My devices are aliased "DP832" and "DM3058E". I'm kinda Bohemian like that
Anyway:

D:\Python27\DP832>python calib.py USB0::0x1AB1::0x0E11::DP8C161350000::INSTR USB0::0x1AB1::0x09C4::DM3R161750000::INSTR
Using:
  DMM   : Rigol Technologies DM3058E (FW 01.01.00.02.02.00) @ USB0::0x1AB1::0x09C4::DM3R161750000::INSTR
  DP832 : RIGOL TECHNOLOGIES DP832 (FW 00.01.13) @ USB0::0x1AB1::0x0E11::DP8C161350000::INSTR

Calibration data will NOT be updated -- this is only a check

Remove all leads to perform self test
Press enter to continue

Running DP832 board self-test...
DP832 self-test passed
DP832 internal temp: 30.98C (87.764F)

Running DM3058E board self-test...
DM3058E self-test passed
DM3058E uptime: 0d 00:00:00

Starting calibration of channel 1

Connect the DM3058E VOLTAGE inputs to the DP832 channel 1
Press enter to continue

Running DAC-V for channel 1
Shutting off PSU outputs
ERROR: could not convert string to float: #9000000016 -7.24861231e-02
Calibration failed. Terminating.

eh? I used the NI MAX test panel, and sure enough the Rigol returns

1: Write Operation (READ?)

Return Count: 5 bytes

2: Read Operation
Return Count: 28 bytes
#9000000016\s-2.68880151e-01\n

So much for Rigols supposed Agilent 34401A compatability mode! What is #9000000016\s supposed to be? A timestamp? or a bug?

[bson]

Ah, neat.  I should just put this on github...

If you run it with -t it'll print a trace of all commands and responses; should make it easier to figure out what's happening and why it fails to parse the measurement... That "#9000000016" looks weird though.  Is that a serial or something?

It should really also issue a SYST:LOC at the end to return the DP832 to local (from remote) use, would eliminate the need to press "back" key.  Probably a reset also, though I'm not sure that's enough - it seems to really need a power cycle to reinstall the calibration tables.

[Stupid Beard]

Oh cool, had no idea such a thing existed!

Edit: it doesn't seem to know how to calibrate or do much of anything else device specific...

Meh. Sorry, I guess I should have looked at it in more detail.

[EEVblog]

I get about 30uA and 30V AC between output and earth.
I don't see the issue, you'll get this with almost any supply, capacitive coupling between output and mains earth is quite normal.
My BK Precision 1697 is 30V and 110uA
If for some reason this is an issue with your system, mains output reference your supply, that is what the earth terminal is on the front panel for.

[SimonD]

Is there anyone who have try this new update ( Version:00.01.02.00  -  2015-03-16 ) of software ?
http://www.rigol.com/prodserv/DC%20Power%20Supplies/software/

Works well on DP832 ?
If yes, can anyone post some screenshots ?
Thank you!

[kjdotts]

I've just found this by case. Small unboxing of DP832 on chines website. Nothing special except... full color display on non-A model. It looks like some early firmware.
Color display is not a big deal but I'm curious if you know something about this ?



Source:
http://www.hkepc.com/forum/viewthread.php?tid=1953803

FYI: No firmware update needed for that multicolor look. The below display settings should reproduce the above colors...

Brightness: 50%
Contrast: 85%
RGB Lum: 45%
Disp Mode: Waveform
Theme: Orange (Transitions to yellow as above settings are input...)

-Kris

[kjdotts]

Here is a list of Rigol DP832 firmware versions and summary of known firmware bugs and hardware issues...

If anyone discovers additional bugs, or has corrections to the summary above, please post in the thread and I'll try to keep this post updated.

I've discovered a CH3 OCP firmware related bug. OCP functions as expected on CH1/CH2 and OVP functions as expected on CH1/CH2/CH3.

Particulars for my Rigol DP832 unit:


NOTE: My unit is equipped with TopBoard_V02.20 / BottomBoard_V02.20.

Recreating firmware bug:

CH3 in CC mode set to 100mA. My Fluke 87V confirms output is bang on at 100.1mA. Readback is 2mA low but well within tolerance.

I increase CH3 set current until it exceeds set/enabled OCP limit of 110mA. However, CH3 remains ON. I continue increasing set current to 1A. My Fluke 87V confirms output stops increasing after I pass 110mA on set current and remains at a max of 110.1mA. Readback is again 2mA low but confirms actual output is at the set OCP limit.

I turn CH3 OCP OFF. V/A/W readback remains unchanged and again, my Fluke 87V confirms an actual output of 110.1mA.

I increase CH3 set current by 1mA to 1.001A. My Fluke 87V immediately registers an output current increase to 1.0011A. V/A/W readback immediately updates to correctly reflect the new output level.

I turn CH3 OCP ON. CH3 immediately registers an OCP event, displays a popup warning window and turns CH3 OFF.

I turn CH3 ON. CH3 remains ON regardless of the set current level which exceeds OCP limit. My Fluke 87V confirms an output of 110.1mA. Readback is again 2mA low but confirms actual output is at the set OCP limit.

NOTE: The 110mA CH3 OCP limit I chose to demonstrate this bug at doesn't matter. I've recreated this bug with CH3 OCP limit set to 10mA, 510mA, 1.010A, 1.510A, 2.010A and 2.510A.

-Kris

[kjdotts]

Here is a list of Rigol DP832 firmware versions and summary of known firmware bugs and hardware issues...

If anyone discovers additional bugs, or has corrections to the summary above, please post in the thread and I'll try to keep this post updated.

I've discovered a ManualCal/Key Lock Password firmware related bug. The factory default password is "2012". If you successfully modify the password, ManualCal recognizes the new password. If you have Key Lock enabled (Utility>>System>>Key Lock) and lock the front panel, the new password is recognized when you unlock the front panel. However, power-cycle the unit and the password reverts back to the factory default "2012".

Particulars for my Rigol DP832 unit:


NOTE: My unit is equipped with TopBoard_V02.20 / BottomBoard_V02.20.

-Kris

[wertyq]

I believe there is something missing from your post.

[McBryce]

So I went to the bother of ordering a 3.8mm drill bit as suggested by Rigol (as far as I know) to repair the positive posts that don't take a standard 4mm banana plug. The bit slides effortlessly into the Earth and GND posts with some play, but it also slides (if somewhat slightly tighter) into the positive posts. So is 3.8mm the wrong size? How big should these holes really be? The positive post holes are definitely 3.8mm, but a banana plug doesn't fit into them. Should they be actually 3.9mm?

McBryce.

[thm_w]

So I went to the bother of ordering a 3.8mm drill bit as suggested by Rigol (as far as I know) to repair the positive posts that don't take a standard 4mm banana plug. The bit slides effortlessly into the Earth and GND posts with some play, but it also slides (if somewhat slightly tighter) into the positive posts. So is 3.8mm the wrong size? How big should these holes really be? The positive post holes are definitely 3.8mm, but a banana plug doesn't fit into them. Should they be actually 3.9mm?

McBryce.

0.166 inch or 4.22mm
according to these manufacturers:
https://cinchconnectivity.com/OA_MEDIA/drawings/dr-1080902001.pdf
http://muellerelectric.com/wp-content/uploads/BU-P2854-2.pdf

[LaurentR]

I've discovered ...
-Kris

Did you report these to Rigol?

[kjdotts]

I've discovered ...
-Kris

Did you report these to Rigol?

I plan to in the near future. I was going to give it a few days to see what type of response/insight/confirmation I might receive from my postings.

-Kris

[Sparky]

I've discovered ...
-Kris

Did you report these to Rigol?

I plan to in the near future. I was going to give it a few days to see what type of response/insight/confirmation I might receive from my postings.

-Kris

Hi Kris,

Thanks for your contribution regarding bug(s) with DP800 series!  That's just the kind of news relevant to this thread!  The detail and screenshots to illustrate and reproduce the problem are great. 

I'm on travel as of tomorrow so busy right now, but let's see how this plays out (has anyone reproduced the errors?) and I will add it to the bugs list (post #1) when I am back (end of the month).

Best,
Sparky

[kjdotts]

Hi Kris,

Thanks for your contribution regarding bug(s) with DP800 series!  That's just the kind of news relevant to this thread!  The detail and screenshots to illustrate and reproduce the problem area great.

I'm on travel as of tomorrow so busy right now, but let's see how this plays out (has anyone reproduced the errors?) and I will add it to the bugs list (post #1) when I am back (end of the month).

Best,
Sparky

Thanks for the positive feedback. Your plan for adding the bugs to post #1 at the end of the month sounds good. I'm waiting to report the bugs to Rigol until I get some responses/insight/confirmation with my posts here.

-Kris

[McBryce]

So I went to the bother of ordering a 3.8mm drill bit as suggested by Rigol (as far as I know) to repair the positive posts that don't take a standard 4mm banana plug. The bit slides effortlessly into the Earth and GND posts with some play, but it also slides (if somewhat slightly tighter) into the positive posts. So is 3.8mm the wrong size? How big should these holes really be? The positive post holes are definitely 3.8mm, but a banana plug doesn't fit into them. Should they be actually 3.9mm?

McBryce.

0.166 inch or 4.22mm
according to these manufacturers:
https://cinchconnectivity.com/OA_MEDIA/drawings/dr-1080902001.pdf
http://muellerelectric.com/wp-content/uploads/BU-P2854-2.pdf

So I went for it and drilled out the positive posts last night. They definitely couldn't be 4.22mm as that would leave no steel at all in the post. A used a 3.8mm drill which allowed me to get banana plugs into the posts, but they were still very tight, so I widened the holes slightly more by "jiggling" the drill a little. Ideally a 3.9mm bit should do the job properly. I used a variable speed drill and used a "snails-pace" speed. The bit cut through the surface quite easily without putting any major strain on the post. So my conclusion, this is something that can be easily done without fear of damaging the device. The end result is about 3.9mm and the banana plugs go in as you would expect them to. I considered using a 4mm drill, but it doesn't fit into the posts that were working properly, so I decided it was too big.
One further point. It seems that the tightness is due to a lip/burr at the very start of the hole. Once the drill had passed the first 1mm into the hole, the rest of the terminal seems to be the correct dimension. Either the plating process was a bit over generous or the stamping machine was a bit too heafty.

McBryce.

[Armxnian]

I can't get the firmware update to work (DP832). I got the files from rigol (1.13). I have boot version 1.09 and firmware version 1.11 . I tried two different flash drives. One is USB 2.0, 2gb, and I formatted it as fat32 using disk part and rufus. The other is a 16gb USB 3. Both are recognized by the unit in normal mode. When I boot it up and press help, it says please insert usb stick with the file on it. I do it but it just stays there.

Any help?

[kjdotts]

I can't get the firmware update to work (DP832). I got the files from rigol (1.13). I have boot version 1.09 and firmware version 1.11 . I tried two different flash drives. One is USB 2.0, 2gb, and I formatted it as fat32 using disk part and rufus. The other is a 16gb USB 3. Both are recognized by the unit in normal mode. When I boot it up and press help, it says please insert usb stick with the file on it. I do it but it just stays there.

Any help?

You're good to go on the bootloader (no need to update) so just place "DP800Update.GEL" from "DP800(Software)Update(Normal)_00.01.13.00.01\" on to your FAT32 formatted USB flash drive root directory.

Complete instructions are attached to post #1 of this thread (DP832 Firmware Upgrade 00.01.13.pdf).

-Kris

[kjdotts]

I can't get the firmware update to work (DP832). I got the files from rigol (1.13). I have boot version 1.09 and firmware version 1.11 . I tried two different flash drives. One is USB 2.0, 2gb, and I formatted it as fat32 using disk part and rufus. The other is a 16gb USB 3. Both are recognized by the unit in normal mode. When I boot it up and press help, it says please insert usb stick with the file on it. I do it but it just stays there.

Any help?

BTW: Don't forget to update analog boards 1 & 2. People sometimes forget this step since it's separate from the main firmware update.

-Kris

[Armxnian]

I can't get the firmware update to work (DP832). I got the files from rigol (1.13). I have boot version 1.09 and firmware version 1.11 . I tried two different flash drives. One is USB 2.0, 2gb, and I formatted it as fat32 using disk part and rufus. The other is a 16gb USB 3. Both are recognized by the unit in normal mode. When I boot it up and press help, it says please insert usb stick with the file on it. I do it but it just stays there.

Any help?

You're good to go on the bootloader (no need to update) so just place "DP800Update.GEL" from "DP800(Software)Update(Normal)_00.01.13.00.01\" on to your FAT32 formatted USB flash drive root directory.

Complete instructions are attached to post #1 of this thread (DP832 Firmware Upgrade 00.01.13.pdf).

-Kris

I can't get the firmware update to work (DP832). I got the files from rigol (1.13). I have boot version 1.09 and firmware version 1.11 . I tried two different flash drives. One is USB 2.0, 2gb, and I formatted it as fat32 using disk part and rufus. The other is a 16gb USB 3. Both are recognized by the unit in normal mode. When I boot it up and press help, it says please insert usb stick with the file on it. I do it but it just stays there.

Any help?

BTW: Don't forget to update analog boards 1 & 2. People sometimes forget this step since it's separate from the main firmware update.

-Kris

Yup that worked, thanks  . My Analog Version is 02.02.03.02.02.03 instead of 01.02.03.01.02.03 like on the guide. To anyone wondering, a 16GB USB 3.0 flash drive works for updating the firmware.

______________________________________________________________________________________________________

Just to add to the discussion, my Pomona banana to alligator cables fit nicely. It was a tight fit at first but they loosened up after a few uses.

[kjdotts]

Yup that worked, thanks  . My Analog Version is 02.02.03.02.02.03 instead of 01.02.03.01.02.03 like on the guide. To anyone wondering, a 16GB USB 3.0 flash drive works for updating the firmware.

Excellent! More than happy to help. Analog Version: 02.02.03.02.02.03 should indicate your unit is equipped with the new TopBoard_V02.20 (as pictured here) and new BottomBoard_V02.20 (my unit also has both new revisions).

Just to add to the discussion, my Pomona banana to alligator cables fit nicely. It was a tight fit at first but they loosened up after a few uses.

Glad to see your binding posts are trouble free. My red binding posts are a tight fit with banana plug connections but not too tight. The black and green are a looser fit but still form a trustworthy connection.

-Kris

[broderp]

There doesn't seem to be much information floating around this thread regarding changes in the recent DP800-firmwares. As Rigol unfortunately quite often doesn't seem to provide release notes with firmware updates, maybe some excerpts from the most recent v1.11 release notes will help others to decide, whether to upgrade or not:

Version:00.01.11.00.00   Date:2014-7-8

• Add the traditional language menu.
• Expand the point of recorder to 614400.
• The display mode will not be changed by setting preset.

Version:00.01.10.00.03   Date:2014-5-09

• Fixed the bug of the display of high resolution option.
• Add internal ovp/ocp function.

Cut short for ease of viewing

What has changed with the 00.01.13.00 update?  Any news on this?  Worth the update from 00.01.11??

[kjdotts]

What has changed with the 00.01.13.00 update?  Any news on this?  Worth the update from 00.01.11??

I wondered the same thing and my online research yielded nothing. I wish Rigol would provide release notes so one would know if a firmware update was worth the time, effort and risks. I've never bricked anything updating firmware, nothing but positive experiences. I'm very OCD so I like to keep my firmware updated as a general rule. Over time, firmware updates usually offer continual improvements, however, sometimes new issues are introduced. With the Rigol DP832, firmware updates have resolved several bugs and introduced a few. I've actually reported two new firmware bugs here in this thread which I hope are resolved in a future firmware release (I plan to report them to Rigol in the near future).

-Kris