Open borisbme opened 6 years ago
I am also have offset +45mV on both channels with 6022BL.
I also see +100mV offset on Ch1 of my 6022BE with probe connected to GND. In the windows application everything is fine. @borisbme @Vascom were you able to solve this problem? It looks like the official application does some calibration procedure on every startup or applies saved offset corrections?
I have found a simple workaround. I shifted vertical position of channel which has problem with offset and now the same sine wave is seen almost identically on both channels. When you hold Alt key, you can set this position precisely in order to visually compensate the offset error
I know, this is not how offset should be corrected, but still better than nothing.
Unfortunately, the workaround I described above is not quite good, because you need to adjust vertical offset every time you switch between channel voltage ranges (10mV to 5V)
Hi,
Sorry to hear that. Thanks for the effort. It seems that openhantek is abandoned, so this and other issues will never be fixed...
It is not abondoned. It is in maintenance mode as visible on the main readme page. This means no feature development. Only critical bug fixes and pull request reviews.
There are no paid developers on this project. Don't expect anything!
I read about the self-calibration feature in #176, but looks like the topic is abandoned.
Are there any plans to either have auto-calibration or allow for manually defining DC correction values for each channel (e.g. some millivolt integer in the config file or Windows registry)?
Is there/what is currently a recommended way of adjusting the DC error? (except for dragging the zero marker in the UI)
Do you know #277? Please check these hints about calibration of 6022 devices.
I wasn't aware of those calibration hints - thank you for the link! It's been some struggle for me with zero Python experience, but I got it working eventually.
Just in case someone else ever wants to calibrate his/her Hantek 6022BE on a Windows 10 machine, here is what I did:
libusb-1.0.dll
file:
libusb-1.0.dll
from the zip file into {Python install dir}/
(where python.exe
sits) git clone https://github.com/Ho-Ro/Hantek6022API
cd Hantek6022API
pip install .
Hantek6022API\PyHT6022\HantekFirmware
folder to
{Python install dir}\Lib\site-packages\PyHT6022\HantekFirmware
cd examples
calibrate_6022.py -gec
I was then able to calibrate the scope providing the given voltages. All works perfectly fine now and voltage readings are nicely accurate.
Again, many many thanks for your work! :-)
Edit: Since the last update of Hantek6022API, copying the firmware folder is no longer needed. Also, libusb-1.0.dll
can be used from the OpenHantek folder, no need to download anything from sourceforge.
I opened a new issue #8 in the right repo, to concentrate all discussion about the python tools under Windows.
The issue link was broken, it is https://github.com/Ho-Ro/Hantek6022API/issues/8
I just commented there. Everything's working great now. Thank you.
I have the same issue. Not there on Window Hantek app and it's Channe 1 only. Can someone explain what the disparity is and why it just shows on OpenHantek? I ran the self calibration on the Windows version which gives no feedback thinking it might write some values to the EEPROM and then it would be fine on Ubuntu but no such joy.
Are you talking about openhantek or OpenHantek6022? If you are using the latter, please report this problem to the right place as this repo is not maintained, see #277
My apologies - you were right - wrong place.
Hi,
I have a Hantek 6022BE, I moved to linux, and channel 1 has a 100 mV (zero) offset (also present when probe is connected to GND) This shift is not present on windows using the official app.
I'm using arch linux and compiled Openhantek from the source.
https://prnt.sc/ix5ape