Products > Test Equipment
DG4000 - a firmware investigation
TurboTom:
--- Quote from: Yeson on July 27, 2022, 03:31:03 am ---How do you calibration? Need Powermeter?
--- End quote ---
Rigol clearly specifies in their calibration guide (attched) the required instruments. For high frequency flatness, a power meter is required, and I don't see much chance for a replacement if you need the amplitude accuracy.
A spectrum analyzer may be a makeshift solution to get rid of the major errors you observe, but you'll rarely get better accuracy than +-1dB. Moreover, using an SA requires interconnection cables and probably adapters that all need to be of prime quality, and the input impedance of the SA may also not be accurate enough (though in the relevant frequency range, that's probably no real problem).
I got lucky with my DG4102 since apparently it's been calibrated all the way up to 200MHz in the factory already.
Yeson:
From 20Mhz to 200Mhz。
PA0PBZ:
My 'upgraded' DG4062, trace max hold. Not sure about the few peaks, maybe interference. I did not touch the calibration at all.
TurboTom:
And here's my DG4000's channel 1 that started life as a DG4102 at three signal levels. Ch2 performs equally well.
Kujo:
Thanks to all for their efforts and patience on this topic.
So noting that this thread has been quiet for some time i just wanted to add some USB drive combinations that ended up working out for me.
I initially tried SanDisk Cruzer 16GB usb 2.0 drives. They were recognised by the device in normal operation but would not load a new firmware file. I noticed that someone mentioned that they had used a microSD adapter. Now also remembering that someone else had mentioned that they felt the USB controller implementation at boot was maybe a bit off i grabbed the dodgy microSD adapted that came with my Ender 3D printer. I dropped a 16GB Strontium Nitro sd card (came with a phone i think) formatted to FAT32 with default allocation size and lo and behold. It worked a treat. Interestingly (well to me anyway) when updating the license file i used the original Cruzer stick and that worked fine. So this seems to support the fact that the USB implementation at boot is different from that once up and running. Anyway in case this is helpful to anyone in the future.
Kujo
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version