Products > Test Equipment

Rigol DP832 - Firmware list and bugs

<< < (68/153) > >>

Macbeth:

--- Quote from: Omikron on May 06, 2015, 05:17:20 pm ---Update: They tried the same command with a DM3068 running the same firmware version and it provided the expected +0 response.  We are now trying to figure out if this is a bad unit or if it's a firmware bug.

What is particularly troubling is the fact that the self-test passes when started from the Utility menu, but fails via *TST?.

--- End quote ---
Omikron, I've been there, seen it, done it. The Rigol is returning the correct response of '0' to *TST?. The calib.py script expects a '+0' which I can only assume the Agilent returns. Or else it is a typo in the code. Anyway, it's an easy one to fix, but there are plenty more to come  :palm:

I kind of gave up on calib.py when I did find a proper firmware bug on the DM3058 in Agilent mode which renders the Agilent mode utterly useless  |O I reported this one to Rigol and left the ball in their court (though I did hack a workaround, it is not something to be proud of). However, the DM3068 does not have this bug as far as I am aware.

So, you can call your attack dogs off Rigol re: *TST? but I would appreciate it if you give them a kick up the arse for me. See here.

I did have calib.py sort of working, at least on its dry runs, but am still waiting for Rigol to sort out the DM3058 bug. Actually I've been meaning to write my own calibrator in C#.NET instead and use the Rigol command set rather than try and emulate an Agilent.

Omikron:

--- Quote from: Macbeth on May 08, 2015, 12:10:24 am ---
--- Quote from: Omikron on May 06, 2015, 05:17:20 pm ---Update: They tried the same command with a DM3068 running the same firmware version and it provided the expected +0 response.  We are now trying to figure out if this is a bad unit or if it's a firmware bug.

What is particularly troubling is the fact that the self-test passes when started from the Utility menu, but fails via *TST?.

--- End quote ---
Omikron, I've been there, seen it, done it. The Rigol is returning the correct response of '0' to *TST?. The calib.py script expects a '+0' which I can only assume the Agilent returns. Or else it is a typo in the code. Anyway, it's an easy one to fix, but there are plenty more to come  :palm:

I kind of gave up on calib.py when I did find a proper firmware bug on the DM3058 in Agilent mode which renders the Agilent mode utterly useless  |O I reported this one to Rigol and left the ball in their court (though I did hack a workaround, it is not something to be proud of). However, the DM3068 does not have this bug as far as I am aware.

So, you can call your attack dogs off Rigol re: *TST? but I would appreciate it if you give them a kick up the arse for me. See here.

I did have calib.py sort of working, at least on its dry runs, but am still waiting for Rigol to sort out the DM3058 bug. Actually I've been meaning to write my own calibrator in C#.NET instead and use the Rigol command set rather than try and emulate an Agilent.

--- End quote ---

So actually, in this case, the *TST? is actually *failing* when issued via SCPI, but only sometimes.  When it does fail, I always get "+1" response and checking the error codes shows the following two codes:


--- Code: ---* Connected to: TCPIP::10.10.10.23::INSTR
-> SYST:ERR?
<- (Return Count:53)
-330,"Self-test failed; 604 - OHM Common Drive Test"

-> SYST:ERR?
<- (Return Count:53)
-330,"Self-test failed; 605 - DCV Common Drive Test"

-> SYST:ERR?
<- (Return Count:13)
0,"No error"

--- End code ---

vovets:

--- Quote from: kjdotts on April 15, 2015, 09:36:06 am ---
--- Quote from: Sparky on January 05, 2014, 10:04:05 pm ---
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.

--- End quote ---

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

--- End quote ---

Hi! Just wanted to confirm this bug on my new DP832 received recently from batronix.com with firmware 1.13. Firmware 1.14 seem to fix this at least for me.

Regards, Vlad.

kjdotts:

--- Quote from: vovets on May 25, 2015, 12:33:42 pm ---
--- Quote from: kjdotts on April 15, 2015, 09:36:06 am ---
--- Quote from: Sparky on January 05, 2014, 10:04:05 pm ---
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.

--- End quote ---

I've discovered a CH3 OCP firmware related bug...

-Kris

--- End quote ---

Hi! Just wanted to confirm this bug on my new DP832 received recently from batronix.com with firmware 1.13. Firmware 1.14 seem to fix this at least for me.

Regards, Vlad.

--- End quote ---

It's good to receive confirmation of the bug and I'm hopeful firmware v1.14 does in fact resolve the bug on my unit.

Thank you for taking the time to post and welcome to the EEVblog forum!

-Kris

shrek:
Has anyone tried to hack the DP832's ANALOG board? Any luck with JTAG and full memory dump of the controller?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod