Products > Test Equipment
Rigol DP832 - Firmware list and bugs
<< < (120/153) > >>
Gandalf_Sr:

--- Quote from: garrettm on March 09, 2020, 12:39:37 pm ---Its alive again!

I've been stuck at home with what might very well be corona virus (or a very bad case of the flu), and finally decided to write the Telnet script in Java. Java sockets made writing the Telnet client a breeze and with TooOldForThis's reverse engineered SCPI commands I was able to recalibrate channel 1 and 2 better than before the manual calibration fiasco. Honestly, I don't see why people avoid using Telnet, its super convenient and avoids messing with drivers, bulky software and hardware adapters. The only hiccup I noticed was that I had to add some latency between sending commands to the Tek DMM4050, otherwise it would start missing commands. Some 50-60 milliseconds seemed to do the trick.

--- End quote ---
Any chance you could come up with an outline of what we need to set up to run your code on a PC?  I have a calibrated Keysight 34461A that would be the obvious meter to use to cal my DP832.

Hope you feel better soon.
garrettm:
@cpposteve after calibration, the read back should be around +-2 counts (when rounding the output to three decimal places). My unit was in a similar state as yours, its last cal date was in 2014, had ancient firmware, and was off by +-20 counts. And now it finally agrees with my benchtop DMM. Though I now question the effort needed to make that happen.

@Gandalf_Sr all you would need to run it is the Java JRE or JDK, a simple Java IDE like BlueJ (to edit, compile and run) or use Notepad++ to edit and Windows PowerShell to compile and then run it. I could turn it into a jar, but you really need the source code to make tweaks as are inevitably needed. Of course being Telnet based, you would need a wired network with a DHCP server, or assign static addresses, and know what device has what address.

To see what its all about I attached a .txt output of the voltage calibration routines for all three channels. It's still a rough draft and may need a few adjustments to work with another DMM, but that wouldn't be hard to do.

Now if only Rigol could improve their quality control regarding firmware bugs and include all the files you actually need when updating...
cpposteve:
Awesome thanks. Although mine is new and manufacturer date of nov 2019.
Is there any reason why people prefer to calibrate it vie scpi rather than through the unit it self? Reading the 16 page document about doing it through the gui it seems pretty strait forward. I really want to get my read back voltage spot on?

Cheers
garrettm:

--- Quote from: cpposteve on March 09, 2020, 05:03:22 pm ---Is there any reason why people prefer to calibrate it vie scpi rather than through the unit it self? Reading the 16 page document about doing it through the gui it seems pretty strait forward.
--- End quote ---

There are two main reasons that I encountered. First it's laborious to do it manually. The DAC-V has 36 entries alone. Second, there are software bugs that might actually screw up the calibration process itself. This is what happened to me. I was perfectly fine slaving away at entering the measured values, but the cal set points weren't outputing the correct voltages for some reason. But I suspect that if you use the SCPI clear all command and then go back and do a manual calibration that it would probably work alright. But, then it is still an effort in patience entering all the values manually.
cpposteve:
ok, so i have calibrated the 832a via the on-board calibrator, all in all it took me 1.5 hours to just calibrate voltage out and read back voltages on all three channels, ignoring the current as these are well within spec and prob only 1ma out across the board. now all three channels read correctly and im very pleased with how its turned out.


steve
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod