Author Topic: Hantek 6022BE 20MHz USB DSO (Read 856275 times)

Seekonk · « **Reply #875 on:** December 17, 2015, 05:32:59 pm »

One thing I wish they would do with the software is turn the section of the trace RED when the A/D converter has reached its limit. Any time I see a nice square top I figure I'm clipping.

borax · « **Reply #876 on:** December 17, 2015, 05:51:58 pm »

Quote

turn the section of the trace RED when the A/D converter has reached its limit.

Good idea!

My problem is solved. It was nearly just too easy

I simply replaced the HTMarch.dll in the Open6022BE package with the (unchanged) version from the DSO2020 installation package and it works

Thanks to RichardK!

piresito · « **Reply #877 on:** December 26, 2015, 04:00:00 pm »

Hi all!
Just received the Hantek 6022 for Christmas and found this thread!
Although I'm not able to use the Open6022BL, it doens't find the scope! The software from Hantek finds it though.
Is there any special instructions to run it? I couldn't find the manual.

Using Windows 10 64bit!

borax · « **Reply #878 on:** January 02, 2016, 11:27:33 pm »

No idea if Windows 10 may be a problem. But I'm also not sure if the Open6022BE software also works for the Hantek 6022BL (6022BL includes the Logic analyzer, the 6022BE is just the scope). You can try to replace the HTMarch.dll in the Open6022BE package with the (unchanged) version from the original Hantek 6022BL package. Maybe this helps.

piresito · « **Reply #879 on:** January 04, 2016, 09:31:40 am »

Quote from: borax on January 02, 2016, 11:27:33 pm

No idea if Windows 10 may be a problem. But I'm also not sure if the Open6022BE software also works for the Hantek 6022BL (6022BL includes the Logic analyzer, the 6022BE is just the scope). You can try to replace the HTMarch.dll in the Open6022BE package with the (unchanged) version from the original Hantek 6022BL package. Maybe this helps.

Hey! Thank you for your reply!
I find the BE and BL designations so confusing that always mess them up! Yes, my version has the logic analizer!

Just got it working on a XP machine by replacing the HTMarch.dll from the original pack form Hantek to this Open6022 package.
Thank you for your tip!

Later today will try it on my Win10 machine!

Soltan · « **Reply #880 on:** January 04, 2016, 04:21:53 pm »

Hi!
First of all, I apologize for knowledge of the English language.
I try to be understood. Ubuntu 14.04. I would like to operate under the oscilloscope.
I got this far based on Github rpcope1 Description:
<code> fazekas@fazekas-ESPRIMO-E3500:~/Letöltések/Hantek6022API-master/PyHT6022/HantekF irmware/custom$ make for a in dscr.a51; do \ cp $a build/; \ cd build && sdas8051 -logs basename $a && cd ..; done for s in fw.c device.c; do \ THISREL=$(basename echo "$s" | sed -e 's/\.c$/\.rel/'); \ sdcc -mmcs51 --code-size 0x3c00 --xram-size 0x0100 --xram-loc 0x3c00 -Wl"-b DSCR_AREA=0x3d00" -Wl"-b INT2JT=0x3f00" -c -I ../fx2lib/include $s -o build/$THISREL ; done fw.c:62: warning 158: overflow in implicit constant conversion sdcc -mmcs51 --code-size 0x3c00 --xram-size 0x0100 --xram-loc 0x3c00 -Wl"-b DSCR_AREA=0x3d00" -Wl"-b INT2JT=0x3f00" -o build/firmware.ihx build/fw.rel build/device.rel build/dscr.rel fx2.lib -L ../fx2lib/lib Multiple definition of _handle_get_descriptor make: *** [build/firmware.ihx] Error 1
<code>
That would be my question is how to continue because it would be very good to use the device under Linux.

MatthewEveritt · « **Reply #881 on:** January 05, 2016, 01:16:16 pm »

Have you made any changes to the code? If not you don't actually need to recompile, there's an up to date binary already in the right place.

Soltan · « **Reply #882 on:** January 05, 2016, 03:56:57 pm »

No change, as I understand it firmware.ihx on the GitHub used any Linux?

MatthewEveritt · « **Reply #883 on:** January 05, 2016, 04:06:33 pm »

firmware.ihx runs on the device itself, so the OS doesn't matter. Everythong else seems to be python, so again shouldn't be a problem,

You should just be able to run

Code: [Select]

sudo python setup.py install and start using it. That worked for me on Debian 8 anyway.

Soltan · « **Reply #884 on:** January 05, 2016, 04:12:13 pm »

Thank you very much, we have two days of struggling with my language skills, unfortunately, very poor and only 50% get the corpses out from the rest descriptions on the fly.

daybyter · « **Reply #885 on:** January 05, 2016, 10:32:53 pm »

You know C?

Soltan · « **Reply #886 on:** January 06, 2016, 08:02:32 am »

Quote from: MatthewEveritt on January 05, 2016, 04:06:33 pm

firmware.ihx runs on the device itself, so the OS doesn't matter. Everythong else seems to be python, so again shouldn't be a problem,

You should just be able to run
Code: [Select]
sudo python setup.py install and start using it. That worked for me on Debian 8 anyway.

The installation was successful.
But how do you run?

MatthewEveritt · « **Reply #887 on:** January 06, 2016, 03:46:39 pm »

Quote from: Soltan on January 06, 2016, 08:02:32 am

The installation was successful.
But how do you run?

There are some python scripts in the examples folder that you can run, but you really need to write a program to do whatever it is you need. There isn't a user-friendly GUI that I know of.

jemzik · « **Reply #888 on:** January 07, 2016, 05:58:11 am »

Hello there
Has anybody had any success with installing driver on win 10 machine ?
Turning off digital signature enforcement did not help for me.
Device recognised as unknown in manager tree.
Manual driver installation prompts that driver was not installed .

MatthewEveritt · « **Reply #889 on:** January 07, 2016, 03:36:27 pm »

I've installed it on a couple of Win 10 machines with no real issues.
I think I might have had to unplug and replug the device, or maybe even reboot, but I don't remember having to do anything more complex than that.

jemzik · « **Reply #890 on:** January 07, 2016, 06:02:41 pm »

Thank you for reply Matthew
I lucky enough to have cd-rom reader on my laptop ( feel like it as obsolete as floppy this days). I used cd that comes with scope to install driver and the process succeed.

daybyter · « **Reply #891 on:** January 12, 2016, 08:27:59 pm »

Question for the coders: if the hantek shows up as ODM HantekDSO6022BE, can I savely assume, that the firmware was correctly flashed on the device and the CPU was restarted? I guess so? But the following

_scope_device_handle = libusb_open_device_with_vid_pid( _context, VENDOR_ID, PRODUCT_ID);

always returns NULL so far.

Is some delay required before the request for the new device handle?

MatthewEveritt · « **Reply #892 on:** January 12, 2016, 09:48:46 pm »

I'm in the office, so I can't check the device label right now, but you can tell if the firmware is loaded as the VID id changes from 0x04B4 to 0x04B5. There will be a slight delay as the device reboots and the system enumerates the new device.

daybyter · « **Reply #893 on:** January 12, 2016, 10:14:42 pm »

Yeah, I tried a delay of 1s, which did not work. But when I stop the app and then restart it, the device is found. Maybe 1s is just not enough. Since the open_device method has no timeout, I'll have to find some reasonable delay time to wait for the scope.

daybyter · « **Reply #894 on:** January 22, 2016, 10:31:51 pm »

Trying to port the rpcope code to C++. Looking for C++ coders to create a QT app for the 6022be, so it could be used under Linux.

Mail me at

arueckert67@t-online.de

if you are interested.

TIA,
Andreas

RichardK · « **Reply #895 on:** January 31, 2016, 03:30:22 am »

Hello everyone, been a while since I have poked in here... I have some free time coming up and I want to hammer away some more Bugs, GUI and Measure in particular...

If anyone would like to compile a list of known Bugs either new or previously mentioned on the last release and how to replicate them it would be helpful

In regards to the Measurement problems, if anyone can get some screenshot comparisons between correct stock software measurement and incorrect Open6022 measurement that would be a great help!

I had to reverse engineer the Measurement code from the original DLL and there might be some data loss in converting between data types...

Also, I was made aware of a GUI/INI bug where changed waveform colors wouldn't be restored after closing and reopening the program, I fixed that today and when I get some more bugs fixed I'll compile a new build for everyone with updated source.

ArekS · « **Reply #896 on:** February 13, 2016, 09:08:35 pm »

Hi,

thanks for the Software and thanks for the manual! Much better than the original.

I have my 6022BE since a few days, so probably I can't help with a complete list of bugs.

I need to analyze a signal of an acceleration sensor at about 70 to 200Hz. Obviously I need FFT. The data sheet of the 6022BE says it can do it, so I bought a Hantek just for this purpose. But what the heck should I do with the curve, when there's no horizontal axes label for the FFT?? What are my frequencies?

I was so happy, when I saw that Open6022BE can do FFT of a math function and the peak frequencies are labeled. Finally a meaningful FFT function! Unfortunately you can't read low frequencies like 100Hz and you can't change the horizontal "time base" or zoom in or do anything about it.

I would be most grateful if you could fix this bug.

olrowdy01 · « **Reply #897 on:** February 13, 2016, 11:52:57 pm »

Quote from: ArekS on Today at 08:08:35 AM

Hi,

I need to analyze a signal of an acceleration sensor at about 70 to 200Hz. Obviously I need FFT. The data sheet of the 6022BE says it can do it, so I bought a Hantek just for this purpose. But what the heck should I do with the curve, when there's no horizontal axes label for the FFT?? What are my frequencies?

>Temporarily, how about coupling a 50 Hz signal (with harmonics) in the circuit you are testing?

ArekS · « **Reply #898 on:** February 15, 2016, 11:36:24 pm »

How would this help? OK, if I had a let's say 50Hz and 100Hz signal I would create my own horizontal axes.

Is it normal, when I put the timebase to 1s/div or slower, I would expect to see a slow line from left to right, to see the signal and it's history. For example, 0V from the source. I put it to 1s/div, the first 10s I don't see anything, it's very laggy, then the whole line is at 0V. I turn the source up to 10V, I still can see 0V, 10s later POW 10V. Sometimes I don't even see the point when the source was turned up.

olrowdy01 · « **Reply #899 on:** February 16, 2016, 03:17:10 am »

Quote from: ArekS on Today at 10:36:24 AM

How would this help? OK, if I had a let's say 50Hz and 100Hz signal I would create my own horizontal axes.

>When using the FFT mode, signals are represented by vertical blips on the display. The horizontal trace represents frequency in the FFT mode. The flat horizontal line is the base line displaying no signal input at the time the sample being displayed was taken (with zero frequency on the left).

If you input a fixed 50Hz and/or 100Hz signal to the DSO you should see those two blips rising above the base (horizontal) line representing the two frequencies.

If you use an input signal combiner you should see those two blips in addition to the FFT representation of your sensor output.

The 50 & 100Hz frequencies on a FFT scope are commonly called "markers". For a starter I would input one or both markers into the DSO and set the DSO to display them.

I don't have the DSO so I run the software in demo mode and it does display demo signals as I would expect. Except for one detail; if I set the marker to be a 1 KHz Sine wave the blip is labeled 10 KHz on the scope. Oops.

You can turn the frequency of the blips ON in the FTT Settings menu. It's called "Show Fundamentals"

Is it normal, when I put the timebase to 1s/div or slower, I would expect to see a slow line from left to right, to see the signal and it's history. For example, 0V from the source.

This is a storage scope that doesn't erase just before where the new sweep is at the time.

I put it to 1s/div, the first 10s I don't see anything, it's very laggy, then the whole line is at 0V. I turn the source up to 10V, I still can see 0V, 10s later POW 10V. Sometimes I don't even see the point when the source was turned up.

I set up the demo mode in the software to display a ramp sweep from 50 to 100 Hz and the signal blip was at the extreme left of the display. In demo mode I couldn't find a way to move the blip from the left side of the display. There doesn't seem to be a Horizontal position control.

My settings were 8v input and 1 sec/div. Higher frequencies do display the blips moved to the right of zero. I would guess this is a limitation of the software.

I would set the scope up to display a known marker at the approximate output frequency & level your sensor is going to output and then adjust the scope settings for the best display.


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Hantek 6022BE 20MHz USB DSO (Read 856275 times)

Share me