Products > Test Equipment
New Hantek DSO2X1X models?
Geoff from Oz:
Hi DavidAlfa,
I've downloaded the repaired package from your Google Drive, and stored it away safely, in case I ever need it. One again, thank you :-+
I'm presuming that the calibration coefficients problem spotted by Visitorik won't be a problem, since it seems that my scope has them already stored in my EEPROM.
Is there any other difference that I should look out for in the repaired backup, or can I just use the backup safely if/whenever I need to?
Cheers
Geoff from Oz
PS Now I have a working scope again, I've been trying to get the Keysight SCPI connection to work (I'm not knowledgeable enough yet to really need it, but it seems like a useful thing to know how to do). Not having much luck yet though, the IO Connection Expert doesn't detect the scope. I think it's something on my pc though; the driver for the "USB Test and Measurement Device (IVI)" isn't completely happy, it says it needs further installation (whatever that means). I will first do a bit of google research, then try removing the devices and starting again. (or possibly, just park the idea for now, I'm keen to get back to the project I was using the scope to explore when the "frozen" problem happened.)
vistorik:
--- Quote from: Geoff from Oz on December 30, 2022, 01:45:11 am ---I'm presuming that the calibration coefficients problem spotted by Visitorik won't be a problem, since it seems that my scope has them already stored in my EEPROM.
--- End quote ---
Hi Geoff,
you could easily check whether your EEPROM contains the factory calibration coefficients. Run the dso3kb_PT24C02_damp.upk like update from the USB drive. It creates a PT24C02_damp.bin file on this drive. Look at this file in any hex-editor. If you find at the end of this file a string 0.8402679.324291, then your EEPROM has the factory calibration coefficients that correspond to their hex values in the calibration file /cache/dds_calbration.dat.
--- Quote from: Geoff from Oz on December 30, 2022, 01:45:11 am ---PS Now I have a working scope again, I've been trying to get the Keysight SCPI connection to work (I'm not knowledgeable enough yet to really need it, but it seems like a useful thing to know how to do).
--- End quote ---
It is known that Keysight SCPI is not compatible with Windows 11.
DavidAlfa:
--- Quote from: Geoff from Oz on December 30, 2022, 01:45:11 am ---I've downloaded the repaired package from your Google Drive, and stored it away safely, in case I ever need it. One again, thank you :-+
--- End quote ---
Please re-download it, I added your original EEPROM. That would be all. :-+
Geoff from Oz:
All looking good, MANY thanks yet again :-+
--- Quote ---you could easily check whether your EEPROM contains the factory calibration coefficients.
--- End quote ---
Done :-) My EEPROM does have the factory calibration coefficients that correspond to their hex values in the calibration file /cache/dds_calbration.dat.
--- Quote ---It is known that Keysight SCPI is not compatible with Windows 11.
--- End quote ---
Duh! You have saved me from much |O THANKS
--- Quote ---Please re-download it, I added your original EEPROM. That would be all.
--- End quote ---
Done :-) Downloaded and stored away safely.
gritzlaszlo:
Hi!
I have a DSO2D15. After a couple of minutes of use it started to show the following symptoms.
https://drive.google.com/file/d/1ByR_9ueos3tpGteahgUM_qE_qPZ1a33M/view?usp=share_link
I waited the recommended 30 minutes of warmup and then tried to do calibration, but it escaped with error message (at the beginnig of the process).
I did full restore with platform tools. The problem still exists.
I have no idea whether it is a hardware or software problem.
Can anyone help me, what are the steps of the calibration process? It could take me closer to the truth :)
Thanks,
Laszlo
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version