-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offset calibration on Windows #83
Comments
This is the typical behaviour without offset calibration. I see 500mV/div with x10 setting -> real range 50 mV/div where 1 digit equates about 4 mV. So the displayed offset of 320 / 520 mV is real 32 / 52 mV, which equates 8 / 13 digits (a not so unusual value, caused by the brain-dead HW design of the scope). Please follow the hints for calibration. |
Thank you very much for your answer! I had to include/change specific paths to some files in the python code for it to work. |
Please provide your changes - this will help other Win users. |
Here are the things I did to get the calibration working. First of all a little disclaimer for any incorrect terminology or strange solutions. First I downloaded the complete Hantek6022API folder here: Also I needed to install libusb1 using pip. For the calibration I used calibrate_6022.py in the examples folder of the API. To this file I added the following at the top of the code: To the file LibUsbScope.py, located in a folder named PyHT6022 I had to add the same code, also right at the top. When I tried to run everything now there still was an error that libusb-1.0.dll could not be found. The solution to this is definitely not a nice one but it worked. After I did this I could run calibrate_6022.py from the windows command prompt without any errors. |
Did you install Hantek6022API? Probably not, I see that this step is missing in the README.md, so I will give you a quick hint (please check if I'm correct, because I do not use Windows and do not have a Windows PC available for testing). |
Installing solved the issues I had earlier. But I'm not certain if this is a general problem if you do this on Windows or if it roots in my lack of experience with python and thus an me-made error with the installation, some directory or whatever. A definitive thing to say is, that when you install Hantek6022API less tweaks are necessary. |
I opened a new issue #8 in the right repo, to concentrate all discussion about the python tools under Windows. |
I use a Hantek 6022BL wit OpenHantek on Windows 10.
On both channels the signals are always offset by some mV, even when the Probes are connected to GND.
The text was updated successfully, but these errors were encountered: