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.
I haven't had my DP832 powered on and under observation enough to be at all sure, but seeing a random LXI splash message out of the corner of my eye sounds a bit familiar.
I haven't had my DP832 powered on and under observation enough to be at all sure, but seeing a random LXI splash message out of the corner of my eye sounds a bit familiar.I suppose that is good news in that it looks like a software thing then.
I have been pondering changing it for a.n.other 2 or 3 channel PSU to get 0-60v and a high current, might have a look around and see what will fit the bill. Defeats the point of scripting tests if you have to keep stopping to reset the PSU to get the comms back.
I haven't had my DP832 powered on and under observation enough to be at all sure, but seeing a random LXI splash message out of the corner of my eye sounds a bit familiar.I suppose that is good news in that it looks like a software thing then.
I have been pondering changing it for a.n.other 2 or 3 channel PSU to get 0-60v and a high current, might have a look around and see what will fit the bill. Defeats the point of scripting tests if you have to keep stopping to reset the PSU to get the comms back.
I have never seen any issue with my DP832 resetting or getting on/off the network.
Several of us have scripted this PSU, e.g. to analyze the acuracy of the DAC and ADC and have had no issue. In one of my tests, I did a full 1mV sweep of the whole 30V range, which is almost 24hrs of runtime, with no issue.
Obviously, some people have issues with their DP832, but I wouldn't panic and automatically assume this is wide spread and broken on all units. I am not sure what alternative PSU there is that will give you more perceived stability and specs in this price range.
Have you excluded all other possibilities? ie: swapped computers / routers etc to make sure it's not some other part of the setup that's causing the issue?
McBryce.
Have you tried it with USB instead of Ethernet? I'm ashamed to say I haven't even tried the Ethernet option myself, but haven't had issues with USB.
Not a lot of DP832A threads on EEVblog.
I was wondering if these issues have been fixed in the latest PCB/design/firmware revisions?
1. Easy to overload pass mossfet
2. Do people still prefer the DP832 instead of DP832A? Does DP832 have all the updates PCB/design wise?
3. Where's the DP832A hack thread to unlock more resolution? I saw the "Sniffing Rigol's Internal I2C Bus" thread, but that's like >160 pages, not realistic to go through that.
3. Where's the DP832A hack thread to unlock more resolution? I saw the "Sniffing Rigol's Internal I2C Bus" thread, but that's like >160 pages, not realistic to go through that.
Thanks for letting me know. Just out of curiosity - is the firmware between the 832 and 832A the same or different?
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.
Hi Laurent, it looks like you are the creator of the cal script and I appreciate your work and sharing this.
I'm just got a new DP832 that is showing different reading and tolerates, it's said it was calibrated 6 months ago. So I plan to try your script since I have a 3 month old calibrated hp 34401A.
One of the factors for buying this was that I could see the current being used on my DUT without adding burden voltage inline.
So one fothe downfall of most bench meters is the high burden voltage when measuring current draw. I still need to learn more on SCPICOMMNADS and install the computer needed libraries So for calibrating the current side (I) I was wondering if you think it's possible that I could modify the script to read voltage for the current reading. What I'm looking at doing is getting the Agilent current shunt that shows 1mV per 1mA for more accurate measurements with the 34401A. So my thought was to modify the script to pull e mV measurements and apply the difference to the current calibration factors on the DP832.
What are the chances of this working after I do the needed research and learn more on this method of communication to my Equiptment? Are the needed command available for such a change to the script, or would I be waisting my time trying to get this to work?
After reading reviews I expected that even my new unit might be out of calibration to what I'm looking to use it for. So I'm happy to say your script was a big part of my decision in buying the DP832. I like the fact that I can have my 34401A calibrated and then use that to calibrate the DP832 without having to spend on getting a second device calibrated. I'm also banking in the age of the 34401A and that it's done drifting, I'll find out if that's true when I send it out in 8 months for my next yearly calibration and compare the data from the original calibration. If it has stopped drifting then a yearly cal may not be needed for someone like me who is just a hobbiest. If the 34401A starts disagreeing with my Fluke 289 then I will have to figure out what meter went off, but for now as long as they both agree within the tolerance expected then I can trust the meter to use for calibrating other Equiptment like the DP832 and save money not having to pay for calibrations.
Thanks,
ScottLooks 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.
Hi Laurent, it looks like you are the creator of the cal script and I appreciate your work and sharing this.
I'm just got a new DP832 that is showing different reading and tolerates, it's said it was calibrated 6 months ago. So I plan to try your script since I have a 3 month old calibrated hp 34401A.
One of the factors for buying this was that I could see the current being used on my DUT without adding burden voltage inline.
So one fothe downfall of most bench meters is the high burden voltage when measuring current draw. I still need to learn more on SCPICOMMNADS and install the computer needed libraries So for calibrating the current side (I) I was wondering if you think it's possible that I could modify the script to read voltage for the current reading. What I'm looking at doing is getting the Agilent current shunt that shows 1mV per 1mA for more accurate measurements with the 34401A. So my thought was to modify the script to pull e mV measurements and apply the difference to the current calibration factors on the DP832.
What are the chances of this working after I do the needed research and learn more on this method of communication to my Equiptment? Are the needed command available for such a change to the script, or would I be waisting my time trying to get this to work?
After reading reviews I expected that even my new unit might be out of calibration to what I'm looking to use it for. So I'm happy to say your script was a big part of my decision in buying the DP832. I like the fact that I can have my 34401A calibrated and then use that to calibrate the DP832 without having to spend on getting a second device calibrated. I'm also banking in the age of the 34401A and that it's done drifting, I'll find out if that's true when I send it out in 8 months for my next yearly calibration and compare the data from the original calibration. If it has stopped drifting then a yearly cal may not be needed for someone like me who is just a hobbiest. If the 34401A starts disagreeing with my Fluke 289 then I will have to figure out what meter went off, but for now as long as they both agree within the tolerance expected then I can trust the meter to use for calibrating other Equiptment like the DP832 and save money not having to pay for calibrations.
Thanks,
ScottLooks 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.
Scottjd, what you are trying to do is not complicated, and everything you'll need is already in the script, so you'll just need a bit of Matlab editing to get it to work.
* First, you should install Matlab, the Keysight IO Libraries and make sure you can run the script and go through the first IDN calls. I used to have a 34401A and the script ran on it in draft form. Note that I was using the serial port and had all kinds of issues with that setup.
* Second, the current script probably doesn't work out of the box on the 34401A anymore, but it should be easy to make it do so. You just have to recognize the 34401A IDN and skip the is34461A section, which uses 34461A-only commands (temperature, uptime... which are not critical to the test).
* Finally, for the 3.2A reading, you have to modify a bit of code. When you detect that the current step is >3A, do the voltage init and reading as done during the voltage stepping and do the math.
Note that at 3.2A, you are unlikely to blow the fuse and the 34401A should be able to measure it properly. I believe one of the users in this thread has done it.
I don't really have time to experiment at home, but I can try to help if you bump into any issue.
Laurent
Thanks for the responce,
As for blowing a fuse with the > 3.2A current measurement with the 34401A it won't be an issue if I'm using the more acurate current shut, hence the 34401A will be measuring mV, voltage and not amperage.
But yes, I've done short times of 3.2A current measurements with the 34401A, but this is were its the most inaccurate and can apply 2V of burden voltage, it's why I'm looking at using the shut in the voltage side instead for calibration and it more acurate over the 3.2A range.
I won't be using the serial cominication, I have a keysight GBIP to USB adapter so I shouldn't see these cominication errors.
Thanks for the heads up in these potential issues.
Scott
Thanks for the responce,
As for blowing a fuse with the > 3.2A current measurement with the 34401A it won't be an issue if I'm using the more acurate current shut, hence the 34401A will be measuring mV, voltage and not amperage.
But yes, I've done short times of 3.2A current measurements with the 34401A, but this is were its the most inaccurate and can apply 2V of burden voltage, it's why I'm looking at using the shut in the voltage side instead for calibration and it more acurate over the 3.2A range.
I won't be using the serial cominication, I have a keysight GBIP to USB adapter so I shouldn't see these cominication errors.
Thanks for the heads up in these potential issues.
Scott