Products > Test Equipment
Rigol DP832 - Firmware list and bugs
_Wim_:
Thanks for this. Will keep that in mind if I would ever be in need.
mountainman:
Hi.
I've found a bug in the DP832A (00.01.14) VXI-11 stack . The DP832A will only accept the device name 'inst0' on the create_link call. Any other value will result in a device not accessible reply to create_link.
Regards Mountainman
Teuobk:
Noticed a bug with my DP832 today (FW 01.14) while calibrating it. It's possible this has been covered elsewhere, but some searching didn't turn up anything, so I thought I'd share both the problem and the solution.
My output voltage on channel 2 had been about 8 mV low for a while, so I decided to calibrate it today using a modified version of bson's script and my DM3068. Everything was fine until I was checking various voltages after the calibration. That's when I noticed that the DP832 had lost its zero on channel 2, by which I mean it was putting out -86 mV instead of 0 V when it was off. All readings at 100 mV and higher were fine, but once the output setpoint was below about 50 mV, the actual output dropped below 0 V. That's a problem because DP832 channels that are "off" are really just set to "0 V" -- or in my case, -86 mV.
Channels 1 and 3 were -0.5 mV and 0.6 mV, respectively, when they were "off".
I confirmed the problem by wiring my 34401A in parallel with my DM3068. The two meters agreed about all of the readings.
I calibrated again, calibrated a third time, power cycled the DP832, manually calibrated from the front panel, and so on. Nothing helped. The 0 V point remained stubbornly below zero, roughly -60 mV to -100 mV depending on the calibration run.
At that point, I looked through the offsets between the DAC calibration point voltages and the actual voltages. On my DP832, all of the DAC cal points below 5.2 V were off by about 430 mV; said differently, the actual voltages were about 430 mV lower than the nominal cal voltages. The only exception was the 0.2 V cal point, which was only 286 mV low. That made me think: what if I just ignore the actual reading during the 0.2 V cal point measurement and instead tell the DP832 that the measured value was 430 mV low, i.e., -230 mV? So, I patched the cal script to do that, and completed another calibration cycle.
That worked! My channel 2 voltages were accurate to with a mV or two almost everywhere, even with output voltages down in the low tens of mV. Zero was only slightly off: about 4 mV. Close enough!
To recap: I fixed my non-zero output problem on my DP832 by giving the instrument a fake value for the 0.2 V DAC cal point.
vertual:
Very long time error not appear. Just catch it. when tool lost connection with computer and off outputs.
probability of this error depend from fetch frequency. 0.1sec - almost stable along 24 hours. 2 sec error not appear 2 mounts.
:syst:err?
data3 (-113,"Undefined head...) er keyword cannot be found
:syst:err?
data2 (-113,"Undefined head...) er keyword cannot be found
I not know it about computer trying connect to DP832A after fail or it is fail reason
About each 5 minutes request address from DHCP, it problem of 1.14 firmware. 1.09 much more stable.
for fix this problem, i according mac address on the tools assign IP at the router, on the tool set same address but manually.
About prevent off network adapter i will try, but why tool disable outputs if it ethernet problem?
for example if simply cut off ethernet cable and over few minutes put again, measurement session will continue without errors.
computer will wait response from tool. even if instead correct data come error message handle it and resend data request again.
when this problem appear destroyed visa object.
victorb:
Hi everyone, I just wanted to say that I received a DP832 today and the FW is version 1.14 and the trigger option works fine using the code generator input using the GUI in the utility menu. Can someone please confirm this and perhaps remove this from the list of problems in the original post?
--- Quote ---4. Trigger option disabled in firmware 01.08 and 01.09
For DP832, the Trigger option is lost when upgrading to 01.08 or 01.09. This appears to be a firmware bug as the trial for evaluating Trigger is not active on new units. All options can be enabled in firmwares prior to 01.08.
[00.01.03.00.02] [00.01.06.00.00] [00.01.08.00.02] [00.01.09.00.01]
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version