First, thank you for you work on this software! It was one of the main reasons I decided to buy 6022BE.

Is your feature request related to a problem? Please describe.
Measuring voltage using "cursor" feature requires taking hands off the whatever stuff you're working on and it's actually quite slow process. A quick glance at the bottom of the screen would be all that's needed to find out Vpp.

Describe the solution you'd like
Add Vpp measurement (option to customise bottom status bar would be a bonus)

Additional context
The lack of Vpp mesurement confused me when I first plugged the oscilloscope. I assumed my Hantek's calibration is way off as the voltage was nowhere near what I was expecting. Only after I read #11 I've realised why the values are different.

When using single trigger, the spike may not be exactly centered. Consequently, if the time/div is expanded, the signal goes out of screen.

A good solution would be a horizontal scroll, option added. Zoom function could tackle the problem, but in this process, another useful feature that could be implemented is a kind of data acquisition menu that allows to specify how much data a user wants to be saved.

.

I have Hantek differential probe which uses X500.
OpenHantek6022 supports only X1 and X10 probe.
It would be very nice if you add X200 , X500, X1000 probe support.
Or maybe user can input factor for his own probe.

Please add option to set up proper probe divider value and show correct signal amplitude.

First of all, thanks a lot for this software. It is much better than original, especially triggering is much more stable.

However, I have problem with "normal" triggering. I am using my Hantek to observe I2C communication on Raspberry Pi. The communication consists of cca. 5us pulses between 0V and 3.3V as shown below

(Please note that two signals are offseted for easier observation.)

The problem is that in 90% of cases I2C communication does not trigger the oscilloscope/program. I don't know if I am doing something wrong or maybe there is some trick I don't know.

• OpenHantek version: 20200110 build 589

• OS: Windows 10

• Device: Hantek 6022BE

• Program top line: OpenHantek6022 (20200110 build 589) - Device DSO-6022BE (FW0204)

• Input signal: square peaks, f ~ 100kHz, Vpp ~ 3.3V

• Probe setting: probe X1

• Number of channels used: 2

• Sample rate: 12MS/s

• USB driver: WinUSB (v6.1.7600.16385)

I don't know if this is a bug or a work-in-progress ... but there in only a pull-down for DC input, no AC input is shown ..

Please move this into "Enhancements" if this is still to do ..

Cheers for the great work .. :)

[ 81%] Building CXX object openhantek/CMakeFiles/OpenHantek.dir/src/usb/uploadFirmware.cpp.o
/home/intellolabs/OpenHantek6022/openhantek/src/usb/uploadFirmware.cpp: In member function ‘bool UploadFirmware::startUpload(USBDevice*)’:
/home/intellolabs/OpenHantek6022/openhantek/src/usb/uploadFirmware.cpp:38:5: error: ‘libusb_set_auto_detach_kernel_driver’ was not declared in this scope
libusb_set_auto_detach_kernel_driver(handle, 1);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/intellolabs/OpenHantek6022/openhantek/src/usb/uploadFirmware.cpp:38:5: note: suggested alternative: ‘libusb_attach_kernel_driver’
libusb_set_auto_detach_kernel_driver(handle, 1);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libusb_attach_kernel_driver
[ 82%] Building CXX object openhantek/CMakeFiles/OpenHantek.dir/src/usb/usbdevice.cpp.o
[ 84%] Building CXX object openhantek/CMakeFiles/OpenHantek.dir/src/utils/printutils.cpp.o
openhantek/CMakeFiles/OpenHantek.dir/build.make:1142: recipe for target 'openhantek/CMakeFiles/OpenHantek.dir/src/usb/uploadFirmware.cpp.o' failed
make[2]: *** [openhantek/CMakeFiles/OpenHantek.dir/src/usb/uploadFirmware.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/intellolabs/OpenHantek6022/openhantek/src/usb/usbdevice.cpp: In static member function ‘static UniqueUSBid USBDevice::computeUSBdeviceID(libusb_device*)’:
/home/intellolabs/OpenHantek6022/openhantek/src/usb/usbdevice.cpp:51:5: *error: ‘libusb_get_port_numbers’ was not declared in this scope
libusb_get_port_numbers(device, (uint8_t )&v, sizeof(v));
^~~~~~~~~~~~~~~~~~~~~~~
/home/intellolabs/OpenHantek6022/openhantek/src/usb/usbdevice.cpp:51:5: note: suggested alternative: ‘libusb_get_bus_number’
libusb_get_port_numbers(device, (uint8_t *)&v, sizeof(v));
^~~~~~~~~~~~~~~~~~~~~~~
libusb_get_bus_number
openhantek/CMakeFiles/OpenHantek.dir/build.make:1166: recipe for target 'openhantek/CMakeFiles/OpenHantek.dir/src/usb/usbdevice.cpp.o' failed
make[2]: *** [openhantek/CMakeFiles/OpenHantek.dir/src/usb/usbdevice.cpp.o] Error 1
CMakeFiles/Makefile2:185: recipe for target 'openhantek/CMakeFiles/OpenHantek.dir/all' failed
make[1]: *** [openhantek/CMakeFiles/OpenHantek.dir/all] Error 2
Makefile:151: recipe for target 'all' failed
make: *** [all] Error 2

I can not understand how to run the program. The file that is as a finished application only opens the Terminal and does something there. I use Mac OS X. Tell me what to do so that everything works right away?

First of all, huge thanks for this piece of software. The original OpenHantek was a bit hard to use with the 6022BE regarding triggers...

Perhaps it is a lack of understanding the feature, perhaps it is a feature that could be implemented differently but my question is as follows:

When i have a signal that's not repeating, (for instance an IR command, measured at the sending IR LED) I can select trigger mode Normal. The program wil wait for a trigger and display the waveform.

However, If I get a repeating signal, for example 1 IR command every 200ms, the trigger mode 'Normal' will be updating every time. This is where trigger mode 'Single' would be used, at least, that's what I expected?

Instead: Single mode always fire's instantaneous when pressing the 'play' button. Whether the trigger condition is met or not (In the upper left corner, you see a nice red TR when the trigger condition was not met). Is this the expected behaviour? And is my use-case invalid for this type of device? Using the Windows Software, it appears 'Single' will wait for a trigger, fill the... buffer? and stop collecting after the buffer is full. This allows to capture an event based on the trigger and analyse after the fact...

Kind regards,

Eric van Zandvoort

Edit: I tried to accomplish what i described but my programming skills are a bit rusty :)
It seems to be working on a basic level :)
single-mode.txt

hey, i just found out something that quite bothering me, if i minimize the window, then hovering my cursor at the taskbar icon of the app, it will show previous menu that i open in the app, although i already close it.

Originally posted by @seraphie21 in #38 (comment)

Hi,

When opening the program, channel 1 probe's scaling is set to 10x, as I left it. But in order to the measures to be correck I have to uncheck and check the box again.

Also, is it possible to use custom attenuation probes? I'm plannig to make some DIY 4:1, 20:1 and 50:1 probes.

Steps to reproduce the behavior:

1. Open the program
2. Check 10x at both channels
3. Close the program and open again
4. See that channel 1 in left lower corner is not corresponding to the scale set in the control panel

• Device Hantek 6022BE

Can you add dummy mode? So users without Hantek hardware can see and may be test interface.

As I think it need only dummy input data generator like calibrating output of 6022 hardware.

When I run progam from command line in linux I see many qglx warnings when switch settings:

qt.glx: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)

Firstly, thank you for this project. It is working better than the stock software and vanilla OpenHantek. Second, Just wanted to confirm that it is working fine on MacOS Mojave 10.14.6. I did have a quick question about the samplerate. It seems that the 48Ms/s option is not available in single channel mode. Was that omitted because of stability? I looked though the commits, and saw a note on the Jun 10 that seemed to indicate that is the reason

This happen then I set Normal mode and move trigger threshold.

Also as I understand "normal" mode in oscilloscopes it should stop refresh data on the screen if trigger not crossed. It is bug too

/usr/include/c++/9/bits/stl_vector.h:1042: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp = std::pair<QOpenGLVertexArrayObject*, int>; _Alloc = std::allocator<std::pair<QOpenGLVertexArrayObject*, int> >; std::vector<_Tp, _Alloc>::reference = std::pair<QOpenGLVertexArrayObject*, int>&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
KCrash: Application 'OpenHantek' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Getting sample data failed:  "Other error"
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::length_error'
  what():  vector::_M_default_append
Unable to start Dr. Konqi

And backtrace from gdb https://paste.fedoraproject.org/paste/L6k6zoKs9lqEUIZnhwhcdw

This report from eevblog tells us:

Have problem with DDS120 and OpenHantek6022 (b188)
I try use my DDS120 again, find new software OpenHantek6022 (b188) and try configure all again.
I see that OpenHantek6022 not read calibration data from DDS120 and zero is not in zero and gain wrong.

Proposed solution: Change these lines:

to:

specification.voltageLimit[0] = { 32 , 80 , 160 , 155 , 170 , 165 , 330 , 820  };
specification.voltageLimit[1] = { 32 , 80 , 160 , 155 , 170 , 165 , 330 , 820  };

Also adapt

double calibration = settings.value( ranges[ iii ], "0.0" ).toDouble();

First thanks for all your hard work, very good project. One small feature if added can greatly advance this rep. when exporting the data via CSV the output is dependent on the time of the export, which as you may conclude is kind of problematic for real time data processing, I am currently exploring your code base, to see if i can create a small modification in which the processed data (before going to the GUI) can be written to a file or linked with another program. Have you considered this ? or if you can point me in the right direction will greatly be appreciated.

I'd like to add a feature to log analyzed data values (rms, vpp...).

I imagined to clone the csv exporter to make a continous logger :

1. Ask for a filename, open a file and write header (columns names),
2. Write into that file the data at fixed interval (1 s for instance) during a specified time or until a mouse clic on the corresponding option menu,
3. Close the file.

I don't understand very well the exporter model.
It seems to process the data, update progress and only at the end ask for a filename to save the processed data.
Is it correct?
So what should be the easiest way to make a logger?

Thanks in advance for your advice.

I've looked through the manual and played with the software (v2.12). Does it have Voltage cursors? If not will this be added?

Also does the SW store samples or only what can be seen?

Please overhaul the front-end of your documentation relating to satisfying installation dependancies, the installation process, and regarding launching the software.
This is what I got after three hours of effort, and I can't even find the launch shortcut for the software after the three hours, so I will TRY to not swear regarding my dissatisfaction:

1. Launching .deb package binary installer fails with a dependency message. It took me a while to realize that you have pre-installation dependency satisfaction instructions. These instructions must belong to first page of your manual. These instructions must also be prominently all over your documentation, project front page, PDF, and within the .deb launcher.

2. You have a bizarre statement on first page of manual, something about forking, yet don't describe the pre-installation requirements. Replace the bizarre statement with useful information!!!

3. In the PDF manual, please explain to user the installation process with a .deb. Not everyone is a developer here, and not everyone has spent a day getting all the pre-requisites!!!

4. After running your suggested command for dependencies, .deb binary is allowed to install but after installation I can't find in any place any way of seeing what and where was installed, and how to launch it. Again, in your manual, please add wording on how I am supposed to launch your software, what its launch names/executables/location/icons/menu entries look like, etc!!!

Thanks!

Describe the bug
Loops on detecting scope. Closing the program and restarting or replugging the scope has no affect.

It says uploading FW, but never gets to that, even if left for a long while.

In the output below the scope is at USB 1.8.*

The permission denied is expected for those other devices, but even when I did give my use RW permissions to it all to see what would happen, still looped, just opening and closing other devices as well.

poll({ 3/POLLIN },1,995)                         = 0 (0x0)
openat(AT_FDCWD,"/dev/usbctl",O_RDONLY,00)       = 15 (0xf)
ioctl(15,USB_READ_DIR,0x7fffffffb8f8)            = 0 (0x0)
openat(AT_FDCWD,"/dev/ugen0.1",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen2.1",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.1",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.2",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen0.2",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.3",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.4",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.5",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.6",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.7",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.8",O_RDWR,00)        = 16 (0x10)
ioctl(16,USB_GET_PLUGTIME,0x7fffffffb8dc)        = 0 (0x0)
ioctl(16,USB_GET_DEVICE_DESC,0x7fffffffb8e0)     = 0 (0x0)
ioctl(16,USB_GET_DEVICEINFO,0x7fffffffbaa0)      = 0 (0x0)
ioctl(16,USB_GET_DEV_PORT_PATH,0x7fffffffba78)   = 0 (0x0)
close(16)                                        = 0 (0x0)
ioctl(15,USB_READ_DIR,0x7fffffffb8f8)            = 0 (0x0)
close(15)                                        = 0 (0x0)
poll({ 3/POLLIN },1,992)                         = 0 (0x0)
openat(AT_FDCWD,"/dev/usbctl",O_RDONLY,00)       = 15 (0xf)
ioctl(15,USB_READ_DIR,0x7fffffffb8f8)            = 0 (0x0)
openat(AT_FDCWD,"/dev/ugen0.1",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen2.1",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.1",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.2",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen0.2",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.3",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.4",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.5",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.6",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.7",O_RDWR,00)        ERR#13 'Permission denied'
openat(AT_FDCWD,"/dev/ugen1.8",O_RDWR,00)        = 16 (0x10)
ioctl(16,USB_GET_PLUGTIME,0x7fffffffb8dc)        = 0 (0x0)
ioctl(16,USB_GET_DEVICE_DESC,0x7fffffffb8e0)     = 0 (0x0)
ioctl(16,USB_GET_DEVICEINFO,0x7fffffffbaa0)      = 0 (0x0)
ioctl(16,USB_GET_DEV_PORT_PATH,0x7fffffffba78)   = 0 (0x0)
close(16)                                        = 0 (0x0)
ioctl(15,USB_READ_DIR,0x7fffffffb8f8)            = 0 (0x0)
close(15)                                        = 0 (0x0)
poll({ 5/POLLIN },1,-1)                          = 1 (0x1)

To Reproduce
IMPORTANT: Always unplug and replug the scope if used before with a different application, e.g. sigrok or the original Hantek software.

Steps to reproduce the behavior:

1. Go to '...'
2. Select '....'
3. See error

Expected behavior
It uploads the FW to the device and starts.

Computer environment (please complete the following information):

• OS: FreeBSD 12-STABLE, r354217
• ports tree: r517355
• OpenHantek version: ccdceeb
• Video hardware: Nvidia
• OpenGL version: (( waiting for the package for mesa-demos to build so I can check glxinfo ))
• Qt version: 5.13.22
• C++ compiler version: Clang 8.0.1

Scope device (please complete the following information):

• Device: Hantek 6022BE
• Program top line: Select device
• Input signal: none
• Probe setting: none

Additional context
Add any other context about the problem here, e.g. the program output if started in a console like xterm.

Started in xterm: qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence: 209, resource id: 0, major code: 140 (Unknown), minor code: 20

After running into issues getting this scope to play nice in this and OpenHantek, I tried pulseview. That worked, although it is not useful for oscopes(unless you really want to use it as a 2channel logic analyzer).

There's a good chance this is a user error but the program doesn't utilise my icon theme which makes buttons harder to see with a dark theme. I've included a screenshot below.

Version: Latest commit (a7c9eb6), built with yay from the AUR
OS: Arch Linux (Kernel 5.4.2)
DE: KDE Plasma 5.17.4 / Qt 5.13.2
Icon theme: La Capitaine

Screenshot

Recent versions run with very high CPU utilization.

To reproduce start OpenHantek and use under Linux
top -p $(pidof OpenHantek)

CPU goes above 200%

I've tracked back the issue and found that it appears after v.2.13 - exactly after commit #94bd5bab476087db293237940980008be7afe807 in file hantekdsocontrol.cpp

After manually revert code:

void HantekDsoControl::updateInterval() {
  // Revert "faster display refresh" 
#if 0
    // after commit  
    // Check the current oscilloscope state everytime 25% of the time
    //  the buffer should be refilled (-> cycleTime in ms)
    cycleTime = (int)( (double)SAMPLESIZE_USED * 250.0 / controlsettings.samplerate.current );
    // Not more often than every 2 ms but at least once every 100 ms
    cycleTime = qBound(2, cycleTime, 100);
#else
    // before commit    
    // Check the current oscilloscope state everytime 25% of the time the buffer
    // should be refilled
    cycleTime = (int)((double)getRecordLength() / controlsettings.samplerate.current * 250);
    // Not more often than every 100 ms though but at least once every second
    cycleTime = qBound(100, cycleTime, 1000);
#endif
    //timestampDebug(QString("cycleTime %1").arg(cycleTime));
}

... now CPU is back to normal ~25%

I hope this helps. Congrats and thank you again for your great work!

hey, i have an error when i tried to install for the first time, it says "connection failed" how can i solve this problem

i had a linux version installed on my VirtualBox on my Lubuntu and it works fine, but it's kinda annoying to use because it takes so long to boot, so i want to try the windows version

thank you for your help : )

I see in the OpenHantek6022 example screenshot a drop-down box with x100 selected. Also cannot select AC option.

I've downloaded v3.0.1 for Debian but i see only a check box for a x10 probe.

how can I use my 100x probe? Years ago I always use my 100x probe for troubleshooting inverters AC 220v output. it works fine with 6022 Original software. please help, thank you.

A lot of people, including me, would like to see a version for RPI in the releases.
Thx!

The cursor measurements yellow or blue box fails to draw.

1. Click Compass tool
2. Select a trace
3. Click and drag to draw box.

No box shows. However, the measurement itself is displayed:

DSO-6022BE FW0204
v 3.0.1 - downloaded binary
Linux Mint 19.2 Cinnamon
Intel Corporation Core Processor Integrated Graphics Controller
OpenGL version string: 2.1 Mesa 19.0.8

terminal output:
$OpenHantek
qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no

I notice quite a bit of Jitter on the edges when the frequency get's higher than about 70khz, is this a hardware limitation or this software ..?

I have tried this on both external signal generator and the internal Calibration output ..

To duplicate just set Cal Out to 100khz ..
Jitter appears to be around 300ns at 100khz ..

I also notice that the max samplerate is only 24Mhz, where on the old software (pre fork) was 48Mhz

I can't set maximum sampling frequency to 48Msps for my 6022BL.
After 24Msps it set only 30Msps in single channel mode.

In two channel mode program can set maximum 16Msps instead of 24Msps.

I use Fedora linux.

This is rather a question.
I can run latest OpenHantek-Win-x64-Release-b127.zip in my Windows 10 PC (1903).
However, I found TortoiseSVN under OpenHantek process. May I know why?

While testing the new openhantek6022 on linux, i noticed that the frequency and voltage readings are not correct in the lower part of the screen.
Frequency is off when the samplerate is too low. e.g; on the calibration squarewave, when you update the timebase, the samplerate automatically reduces to 100kS/s and gives you a frequency of 250Hz. updating the samplerate to 500kS:S shows the correct frequency values.
It would be nice to give the highest possible samplerate when changing the timebase, this would eliminate some interpretation errors.
Also, voltage readings on the last version seems half of what they shoud be. I'm reading 1, 06 V on the ref squarewave, Normally this should read 2Vpp.
on sinewaves, voltages are half of what they are in reality. Older openhantek software gives correct values

Is ist possible to enable the ac/dc coupling without rebuilding the binaries. ex. by an option?

If i set the checkbox only to CH1, the measurement is very noisy.
There is no problem with CH1 and CH2 set together or only set to CH2.
I try the latest repository with the 6022BL.
CH1+CH2:

Only CH1:

Hi,

I want to try to implement some features in this program, and experiment with it. What are the steps to be followed when importing this project to QtCreator(Windows)? Mine wont compile with error:

👎 error: No rule to make target 'all'. Stop.

It is a fresh installation of QtCreator. Never used it. I would appreciate the help.

The program crashes on the MAC OS if the cursor measures the time intervals. I can send a video to the mail.

And here you can see that Normal mode not working as expected:
oh_v_1-2019-05-05_09.34.28.zip

Originally posted by @Vascom in #5 (comment)

Hi there,

are there any approaches in supporting the 6004BD series, especially the Hantek 6204BD in linux?

I just found that the serial communication chip is a CY7C68013A (FX2LP) and that it can be reverse engineered with the Hantek SDK and a Windows in a virtual machine for the 6022BE. rpcope1 has made some progress (https://github.com/rpcope1/Hantek6022API/blob/master/REVERSE_ENGINEERING.md).
Any more tips if i would try to implement it?

Depending on the viewing angle the grid dots are very difficult to see. Can these be made larger using more pixels perhaps with an option in the colour configuration menu?

Windows 10 pro 64b, version 1809, OS build 17763.1039; Intel Core 2, Duo CPU E6550
OpenHantek-Win-x64-Release-b228/OpenHantek.exe

Device Manager Driver Listing: Hantek6022BL\Hantek6022BL DRIVER 2

Error uploading firmware:
"UploadFirmware: Couldn't open device: Operation not supported or unimplemented on this platform"

Note:
Recent Hantek software installation downloaded 20200212.
Drivers provided within the Hantek install package work OK with the Hantek software version 1.06.

Hey!

Thanks for that wonderful software. It was very easy to use and I am glad you released a Mac OS version!

On the first sight, I thought I just have to execute this application and would be able to measure right away. My first try proofed me wrong.

With a little knowledge about software development I figured out quickly, that I need xcode, xcode command line tools, homebrew, qt, libusb and fftw installed. Right after giving away 40 GB of discspace for like 99% unneeded stuff and 1.5 hours later I was able to start openhantek6022.

To be fair, I had no compilation problems happening. Which has been really good!

On the end of the day I wished there had been a simple bundle containing only the things I need. More like 100MB than 40 GB.

QT describes how to do macOS deployment as a bundle...
https://doc.qt.io/qt-5/macos-deployment.html

Could you please create a simple Bundle for Mac? I offer myself as a volunteer for testing ;)

Is it possible to add DSO4104C?
I don't know how i can add this because firmware of DSO is in .upk and i need to add hex file...
Anyone can help me ?
Thanks

I did this to install:

sudo dpgk -i openhan.....

When I try to start the connection window appear, click on connect and then program crash with this message:

qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no
QEGLPlatformContext: eglMakeCurrent failed: 3009
QOpenGLFunctions created with non-current context
Segmentation fault

If i try to build myself, i got this error at launch libopengl0 not found

Regards

Cinosh07

Can you please add option to save more data to file. Not only 20000 samples.
If it can not be save continuously than at least incontinuously.

So user can set multiplier for example 2x20k, 3x20k, etc.

It will be good for postprocessing in other apps like octave.

Hi, I wanna know if there is some kind of support for Hantek 1008c. Tried to find it but I haven't got any information about it.

I'd like to use the device natively on OSX but right now I can't :/

Thanks,
Sebastián.

Hi guys.

Recently I got my hands on a clone of USBee-DX device. This is combined logic analyzer and oscilloscope.
I was hoping to make it working under Linux with Sigrok PulseView software, but unfortunately it supports only analyzer side.
Googling this issue brought me to few articles, with information, that this devices are hardware compatible to Saleae logic analysers and stating that Handek 6022 is basically improved clone of the same USBee-DX...
Indeed, checking the drawings I've found, led me to conclusion that at least general configuration is very similar: both devices are using Cypress FX2 chip (100-pin CY7C68013A-100 in case of Hantek and 56-pin Cypress CY7C68013A-56 in case of USBee-DX clone), which is getting information from ADCs (one dual ADC AD9288 and two single TLC5510 respectively) over B and D ports, and both devices are getting the firmware from PC software.

Winged by this information I started experimenting with different VID/PID values, trying to get USBee-DX clone represent itself as 6022, and even got it detected as Hantek and driver loaded. Unfortunately OpenHantek software shows an error, stating that it cannot load the firmware.

My question is: will it be possible to get a support for USBee-DX compatible oscilloscopes? What can I do from my side? I'm programming a bit (C & C++), but I'm not professional. I do not know, from which side to approach to this issue.

Hi,l. First of all, thanks for this amazing software! It definately runs smoother than any other available. The only thing I miss here is a duty cicle measurement, and other minor measurements such as rise and fall times, etc. Is it possible to implement these? I could not uninstall the original software only because I eventually need those measurements.

Describe the bug
Exporting a zoomed screen with zoom x 1.00 shifts the center of original trace to the left border.
Zoom > x 1.00 crashes the program.
This issue exists already in 3.0.1

It is impossible to set desired Timebase and Samplerate simultaneously.

For example I want 100 ns and 12 Msps but it is always switched to maximum samplerate on lower timebases.

This is a very annoying bug and very bad for user experience.

Release-b106 (v2.15)
Program crashes when initially increase timebase above 20ms on Windows 10. Tested several times, only when timebase is increased very slow and patiently program works fine until restart and start again initial increase of timebase.
On waveform screen appears some peak to peek noise just before crash.

To Reproduce
Start the program on windows 10 and start increasing timebased. On average fast clicking "up" above 2ms program freez and close it self.

On previous version everything works fine.

I am astounded by how good this software is! I am using OpenHantek6022 3.0.1 FW0204 on Windows 10 with a Hantek 6022BL.

Voltage measurements are off by 10%, so I would like to calibrate the display. I have a modelDSO6022.conf file that I can change values in and see a corresponding effect in the display.

I read the calibration notes in:
https://github.com/Ho-Ro/Hantek6022API/blob/master/README.md#create-calibration-values-for-openhantek

This references both examples/cal_zero.py and examples/calibrate.py. I have searched github in both OpenHantek and OpenHantek6022, and eevblog but cannot find these files anywhere.

Would you please provide a pointer to the python programs, or at least hints on how to determine values for the modelDSO6022.conf file?