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

0 Members and 5 Guests are viewing this topic.

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #350 on: February 21, 2014, 01:00:51 am »
When running the latest OPEN6022BE I find that when both probes are connected to the internal reference output I get two nice square waves, but they shudder and move around regardless of whether on trigger CH1 or CH2.

Works fine here, scope's reference waves are rock solid with Trigger on CH1. Try adjusting the trigger level to the middle of the waveform.

Quote
When I add a reference waveform from the menu button function generator, it displays nicely and the reference waveform sits there solid as a rock.
Now I select AC coupling on CH1 (trigger is also CH1) and the reference wave starts running and CH1 and 2 becomes stable

I found some inconsistencies in respect to Triggers and the Reference Trigger also, should be fixed in next release *Fingers crossed*

Quote
then after a short while the red led comes on and the software  freezes and only a end task in task manager can release it. The same happens when trigger is CH2 and AC Coupling is selected on CH2.

I also found a situation where the application might hang and I fixed it, though I was not able to replicate the hanging under your provided conditions, I am hopeful that they are related and thus your issue will be fixed in the next release.

Thanks for the feedback :)
« Last Edit: February 21, 2014, 01:43:14 am by RichardK »
 

Offline Matchless

  • Regular Contributor
  • *
  • Posts: 120
  • Country: za
Re: Hantek 6022BE 20MHz USB DSO
« Reply #351 on: February 21, 2014, 11:10:53 am »
Thanks RichardK, will check when the next binary is released!

I did not see the "Autoset" function on your todo list.  Are you planning to have it replicate what the OEM software is doing now (i.e. scans for any input signal and then by pushing the Auto button the best display is automatically selected)?

You are doing outstanding work on this! :-+
Regards
Matchless
 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #352 on: February 21, 2014, 03:51:29 pm »
I did not see the "Autoset" function on your todo list.  Are you planning to have it replicate what the OEM software is doing now (i.e. scans for any input signal and then by pushing the Auto button the best display is automatically selected)?

Yes I'll be working on that soon, either the next release or the following.
 

Offline Rick Law

  • Super Contributor
  • ***
  • Posts: 3423
  • Country: us
Re: Hantek 6022BE 20MHz USB DSO
« Reply #353 on: February 21, 2014, 11:46:31 pm »
Latest Binary: http://jmp.sh/2QnHfye

What's New:
-----------------------------------------------------------
1. Various Rendering performance improvements.
2. Added a right click menu to output window to copy measure output to clipboard.
3. Fixed a bug where changing Time Division with Math Channel enabled could cause
   the application to hang.
4. Fixed a bug where changing Time Division would sometimes not update Sample Rate
   display.
5. Fixed a bug where Math & Reference Trigger Leavers would not rescale on form resize.
6. Implemented XY mode.
EDIT: 7. Added a color option for XY mode to the Waveform Color dialog.

...


Hey, RichardK, good piece of work!  All my prior issue reports: math rolling, math causing hang... are all gone.  I found no new issues.  None!  Apart from FFT, I tested all the other features rather thorough.  This is very solid.

I'd notice that it does not trigger on math trace, but since you said not all trigger functions are completed.  I left them out of testing.

Rick

Edit:  Documenting this just for completeness.  The issue I had with remote desktop remains.  Since you determined it is not an issue with your software, I left that out.   It drawing only 1 trace - (the last one to turn on, such as, if you turn on math last, that is the only one seen in RDC).

« Last Edit: February 21, 2014, 11:51:34 pm by Rick Law »
 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #354 on: February 22, 2014, 11:31:53 pm »
Something I noticed, lots of places selling the 6022BE advertise that it has pre-trigger acquisition, and even the Hantek product details states (for the entire 6000 series).

Quote
Pre/Post trigger    0-100%

And if you look at the HTMarch.dll function dsoReadHardData():
Code: [Select]
HTMARCH_API short WINAPI dsoReadHardData(WORD DeviceIndex, short* pCH1Data,
short* pCH2Data, ULONG nReadLen, short* pCalLevel, int nCH1VoltDIV, int nCH2VoltDIV,
short nTrigSweep, short nTrigSrc, short nTrigLevel, short nSlope, int nTimeDIV,
short nHTrigPos, ULONG nDisLen, ULONG* nTrigPoint, short nInsertMode);

You will notice a parameter called nHTrigPos which in the SDK says is the "Horizontal Trigger", and it's range is stated as being 0-100.

Many of you have probably already noticed the lack of a Horizontal Trigger lever in the stock software, it's nowhere to be found. I thought this was odd, as there is no way to set the parameter, and the SDK example sets this at 50, so I assumed that's probably what the stock software is doing also.

Well, after some reverse engineering I discovered that in dsoReadHardData() the parameter for horizontal trigger is, wait for it... NEVER USED.

They don't even use the value passed into it, which tells me they planned on having Pre-Trigger support but never implemented it.

I have added a Horizontal Trigger lever in the next release, but I have left it invisible (disabled) in hopes that Hantek updates their HTMarch.dll someday to include Pre-Trigger like they falsely advertise.
 

Offline sandos

  • Contributor
  • Posts: 14
Re: Hantek 6022BE 20MHz USB DSO
« Reply #355 on: February 23, 2014, 11:46:27 am »
Im lucky you made this software, since I was unable to read the included CD (I only have an old IDE cd-drive, and no IDE ports... no CDs in any laptop either) and their site is so incredibly bad/slow I was unable to download the software zip!

Just wanted to note that sadly its very unstable. It crashed several times during only 15 minutes of experimenting. How do I get a log or any info on why it crashed?
 

Offline sandos

  • Contributor
  • Posts: 14
Re: Hantek 6022BE 20MHz USB DSO
« Reply #356 on: February 23, 2014, 12:56:35 pm »
Well, ok, it seems two threads are stuck when this happens, from Process Hacker 2:

These threads both use 25% cpu/ 1 core.


TID 4780:

Code: [Select]
0, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
1, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x56b
2, wow64.dll!Wow64SystemServiceEx+0x1ce
3, wow64.dll!Wow64LdrpInitialize+0x42b
4, ntdll.dll!RtlUniform+0x6e6
5, ntdll.dll!RtlCreateTagHeap+0xa7
6, ntdll.dll!LdrInitializeThunk+0xe
7, ntdll.dll!NtDelayExecution+0x15
8, KernelBase.dll!Sleep+0xf
9, Open6022BE.exe!PrintdialogFinalize+0x3cc64
10, Open6022BE.exe!ConstantsFinalize+0x3352d
11, Open6022BE.exe!ConstantsFinalize+0x32400
12, Open6022BE.exe!MeasureFinalize+0x6dd27
13, Open6022BE.exe!MeasureFinalize+0x12e1e
14, user32.dll!gapfnScSendMessage+0x332
15, user32.dll!GetThreadDesktop+0xd7
16, user32.dll!CharPrevW+0x138
17, user32.dll!DispatchMessageW+0xf
18, Open6022BE.exe!MeasureFinalize+0x6e4cc
19, Open6022BE.exe!MeasureFinalize+0x6e50f
20, Open6022BE.exe!MeasureFinalize+0x6e83a
21, Open6022BE.exe!WaveformcolordialogFinalize+0x166
22, Open6022BE.exe!Tb2versioninitialization$qqrv+0x15197
23, kernel32.dll!BaseThreadInitThunk+0x12
24, ntdll.dll!RtlInitializeExceptionChain+0x63
25, ntdll.dll!RtlInitializeExceptionChain+0x36


0, KernelBase.dll!IsNLSDefinedString+0x476
1, 0x76548a4876523b6f
2, 0x7652449800000038
3, KernelBase.dll!IsNLSDefinedString+0x476
4, Open6022BE.exe!PrintdialogFinalize+0x3cc64
5, Open6022BE.exe!ConstantsFinalize+0x3352d
6, Open6022BE.exe!ConstantsFinalize+0x32400
7, Open6022BE.exe!MeasureFinalize+0x6dd27
8, Open6022BE.exe!MeasureFinalize+0x12e1e
9, user32.dll!gapfnScSendMessage+0x332
10, user32.dll!GetThreadDesktop+0xd7
11, user32.dll!CharPrevW+0x138
12, user32.dll!DispatchMessageW+0xf
13, Open6022BE.exe!MeasureFinalize+0x6e4cc
14, Open6022BE.exe!MeasureFinalize+0x6e50f
15, Open6022BE.exe!MeasureFinalize+0x6e83a
16, Open6022BE.exe!WaveformcolordialogFinalize+0x166
17, Open6022BE.exe!Tb2versioninitialization$qqrv+0x15197
18, kernel32.dll!BaseThreadInitThunk+0x12
19, ntdll.dll!RtlInitializeExceptionChain+0x63
20, ntdll.dll!RtlInitializeExceptionChain+0x36

0, ntdll.dll!NtDelayExecution+0x15
1, 0x76523bc877e3fd91
2, 0x18fb8800000000
3, 0xb6183fc9
4, 0x24f2c2000000003
5, 0x100000024
6, ntdll.dll!NtDelayExecution+0x15
7, KernelBase.dll!Sleep+0xf
8, Open6022BE.exe!PrintdialogFinalize+0x3cc64
9, Open6022BE.exe!ConstantsFinalize+0x3352d
10, Open6022BE.exe!ConstantsFinalize+0x32400
11, Open6022BE.exe!MeasureFinalize+0x6dd27
12, Open6022BE.exe!MeasureFinalize+0x12e1e
13, user32.dll!gapfnScSendMessage+0x332
14, user32.dll!GetThreadDesktop+0xd7
15, user32.dll!CharPrevW+0x138
16, user32.dll!DispatchMessageW+0xf
17, Open6022BE.exe!MeasureFinalize+0x6e4cc
18, Open6022BE.exe!MeasureFinalize+0x6e50f
19, Open6022BE.exe!MeasureFinalize+0x6e83a
20, Open6022BE.exe!WaveformcolordialogFinalize+0x166
21, Open6022BE.exe!Tb2versioninitialization$qqrv+0x15197
22, kernel32.dll!BaseThreadInitThunk+0x12
23, ntdll.dll!RtlInitializeExceptionChain+0x63
24, ntdll.dll!RtlInitializeExceptionChain+0x36

TID 2956:

Code: [Select]
0, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
1, wow64cpu.dll!TurboDispatchJumpAddressEnd+0x56b
2, wow64.dll!Wow64SystemServiceEx+0x1ce
3, wow64.dll!Wow64LdrpInitialize+0x42b
4, ntdll.dll!RtlIsDosDeviceName_U+0x23a27
5, ntdll.dll!LdrInitializeThunk+0xe
6, ntdll.dll!NtDelayExecution+0x15
7, KernelBase.dll!Sleep+0xf
8, Open6022BE.exe!PrintdialogFinalize+0x3cc64
9, Open6022BE.exe!ScopeFinalize+0x31689
10, Open6022BE.exe!PrintdialogFinalize+0x3db30
11, Open6022BE.exe!DrawFinalize+0x310ae
12, Open6022BE.exe!MeasureFinalize+0x2dd06
13, kernel32.dll!BaseThreadInitThunk+0x12
14, ntdll.dll!RtlInitializeExceptionChain+0x63
15, ntdll.dll!RtlInitializeExceptionChain+0x36

0, wow64cpu.dll!CpuSimulate+0x16e
1, 0x42bff7400000000
2, 0x24f2c20007ffd8a
3, 0x7ffdf102541770
4, 0x80009802541770
5, 0x2541770007ffd60
6, 0x81263102583550
7, 0x81263b042bff58
8, 0x42bff7c042bff74
9, 0x42bff7400812691
10, ntdll.dll!NtDelayExecution+0x15
11, KernelBase.dll!Sleep+0xf
12, Open6022BE.exe!PrintdialogFinalize+0x3cc64
13, Open6022BE.exe!ScopeFinalize+0x31689
14, Open6022BE.exe!PrintdialogFinalize+0x3db30
15, Open6022BE.exe!DrawFinalize+0x310ae
16, Open6022BE.exe!MeasureFinalize+0x2dd06
17, kernel32.dll!BaseThreadInitThunk+0x12
18, ntdll.dll!RtlInitializeExceptionChain+0x63
19, ntdll.dll!RtlInitializeExceptionChain+0x36

0, KernelBase.dll!IsNLSDefinedString+0xca7
1, 0x76523bab042bfecc
2, 0x42bfea8
3, 0x6b22b3aa9
4, 0x24f2c2000000005
5, 0x100000024
6, KernelBase.dll!IsNLSDefinedString+0xca7
7, KernelBase.dll!SleepEx+0x48
8, KernelBase.dll!Sleep+0xf
9, Open6022BE.exe!PrintdialogFinalize+0x3cc64
10, Open6022BE.exe!ScopeFinalize+0x31689
11, Open6022BE.exe!PrintdialogFinalize+0x3db30
12, Open6022BE.exe!DrawFinalize+0x310ae
13, Open6022BE.exe!MeasureFinalize+0x2dd06
14, kernel32.dll!BaseThreadInitThunk+0x12
15, ntdll.dll!RtlInitializeExceptionChain+0x63
16, ntdll.dll!RtlInitializeExceptionChain+0x36

 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #357 on: February 23, 2014, 04:02:30 pm »
Im lucky you made this software, since I was unable to read the included CD (I only have an old IDE cd-drive, and no IDE ports... no CDs in any laptop either) and their site is so incredibly bad/slow I was unable to download the software zip!

Just wanted to note that sadly its very unstable. It crashed several times during only 15 minutes of experimenting. How do I get a log or any info on why it crashed?

I found a hang condition a few days ago and fixed it, and looking at your logs, it's hanging in a Lock() loop (the sleep call is a dead giveaway) so I'm pretty confidant your issue will be gone in the next release.
 

Offline Mark_O

  • Frequent Contributor
  • **
  • Posts: 939
  • Country: us
Re: Hantek 6022BE 20MHz USB DSO
« Reply #358 on: February 23, 2014, 04:24:04 pm »
Something I noticed, lots of places selling the 6022BE advertise that it has pre-trigger acquisition, and even the Hantek product details states (for the entire 6000 series).

Quote
Pre/Post trigger    0-100%

Yep.  Though from Rick Law's early reports of being unable to trigger consistently on any signal, asking it to select a specific point seemed wildly optimistic.

Quote
Well, after some reverse engineering I discovered that in dsoReadHardData() the parameter for horizontal trigger is, wait for it... NEVER USED.

They don't even use the value passed into it, which tells me they planned on having Pre-Trigger support but never implemented it.

Why am I not surprised?  This is the kind of annoyance I find discouraging about Hantek.  Not only does their user-level software not work properly, not only do they not live up to their advertised claims, but they don't even implement the API-layer that they themselves defined.

But it does help to explain, a) why they don't do a better job documenting their API, and b) refuse to answer any questions about it.  All that would accomplish is to expose their amateur-grade quality all the more quickly.  (Actually, my apologies.  I shouldn't insult amateurs by comparing them to Hantek programmers.  :D )

Quote
I have added a Horizontal Trigger lever in the next release, but I have left it invisible (disabled) in hopes that Hantek updates their HTMarch.dll someday to include Pre-Trigger like they falsely advertise.

Hopefully, no one will be holding their breath.  ;)

[Another approach would be to make that control visible, and when an operator tries to use it, pop up a dialog box with contact information for Hantek, and direct them to inquire why a sales feature Hantek advertises is not implemented.  That may accelerate the enhancement process.  Or simply get them to stop advertising capabilities their offering does not provide.  Either would be an improvement.]
 

Offline Mark_O

  • Frequent Contributor
  • **
  • Posts: 939
  • Country: us
Re: Hantek 6022BE 20MHz USB DSO
« Reply #359 on: February 23, 2014, 04:48:44 pm »
I have added a Horizontal Trigger lever in the next release, but I have left it invisible (disabled) in hopes that Hantek updates their HTMarch.dll someday to include Pre-Trigger like they falsely advertise.

[Another approach would be to make that control visible, and when an operator tries to use it, pop up a dialog box with contact information for Hantek, and direct them to inquire why a sales feature Hantek advertises is not implemented.  That may accelerate the enhancement process.  Or simply get them to stop advertising capabilities their offering does not provide.  Either would be an improvement.]

A third approach, even more proactive, would be to actually get in touch with Hantek, show them what you've accomplished with your software (whose availability could be very beneficial to their sales), and ask them if they'd be so kind as to add the pre-trigger functionality to their DLL that they've been falsely advertising, for how many years?

Of course, I wouldn't word it quite that way.   :-DD  Since a new version of the DLL was actually (unexpectedly) released, they evidently still consider it an active product.  So it's at least a possibility.  With greater likelihood if you poke them, rather than just hoping it may happen randomly some day.

Worst case, they could say no, they don't have 'the resources'.  At which point you ask if they'd share the DLL source with you... though that might not as useful as one would hope.  (It could at least save you some time & trouble reverse-engineering!)
« Last Edit: February 23, 2014, 04:50:28 pm by Mark_O »
 

Offline Rasz

  • Super Contributor
  • ***
  • Posts: 2616
  • Country: 00
    • My random blog.
Re: Hantek 6022BE 20MHz USB DSO
« Reply #360 on: February 24, 2014, 12:42:05 am »
RichardK have you considered collaborating with sigrok.org people?
Who logs in to gdm? Not I, said the duck.
My fireplace is on fire, but in all the wrong places.
 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #361 on: February 24, 2014, 04:27:08 am »
RichardK have you considered collaborating with sigrok.org people?

Never heard of them before, and their site is down... What are they, like the DD-WRT of the Oscilloscope world?
 

Offline MrAureliusR

  • Supporter
  • ****
  • Posts: 373
  • Country: ca
Re: Hantek 6022BE 20MHz USB DSO
« Reply #362 on: February 24, 2014, 12:45:05 pm »
@RichardK

I was just thinking...

Back in high school, I programmed some stuff using MIDI to control a robot. I took a basic MIDI controller that had like 8 knobs and some buttons etc, and mapped the MIDI signals to call functions in the process. If I (or someone) were to implement some MIDI plugins, we could theoretically get control of the on-screen knobs etc from a basic MIDI pad.

I'd be willing to try and implement this at some point as I have quite a bit of MIDI stuff lying around (MIDI <-> USB, MIDI keyboard, etc) and the protocol is really simple.

I would just need to look at your source code and somehow write a plugin to enable this feature. I've never written a plugin type program before so I'd be a fish out of water but I'd be happy to try.

Wouldn't that be cool -- to actually have physical knobs etc to control the signals? That could considerably increase the value and usefulness of this scope.

Let me know what you guys think, and maybe I'll try and find some time to start coding. However I must admit my non-microcontroller coding skills have slumped over the past few years. My C is good, but all I do is microcontroller stuff (ARM, AVR, PIC) so I'd have to re-learn some stuff. Are you using Visual Basic for the GUI? Or how are you implementing it?

EDIT: I just had a measurement crash, as outlined earlier. Had measurements up, tried to change timebase, and program locked up.
--------------------------------------
Canadian hacker
 

Offline PioB

  • Regular Contributor
  • *
  • Posts: 84
  • Country: ch
Re: Hantek 6022BE 20MHz USB DSO
« Reply #363 on: February 24, 2014, 03:03:36 pm »
@MrAureliusR: a project like that was recently featured on Hackaday: http://hackaday.com/2014/02/04/a-usb-connected-box-o-encoders/


Sent from my GT-I9300 using Tapatalk

 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #364 on: February 24, 2014, 07:24:39 pm »
Hello everyone, here is an update on progress thus far...

A while back I noticed an odd bug which would cause a Division by Zero exception when viewing a stopped waveform and setting the timebase less than 500ns.

It turns out the bug is in the HTDisplayDLL DrawWaveInYT() method, and there was really no pretty way to work around this, so... I reverse engineered all the HTDisplayDLL methods that I use and totally eliminated the need for the stupid DLL.  :rant:

Here was the bug (disassembled C++ code):

Code: [Select]
double HorzRatio;
if(MemSize >= 1)
HorzRatio = (double)(rc->right - rc->left + 1) / (double)(MemSize - 1);
else
HorzRatio = 0;

See if anyone can figure out what's wrong with the above code... I also found (and fixed) a bunch of Buffer overrun's riddled throughout their drawing code. Silly Hantek developers  :palm:


I'm doing some more testing to make sure everything still works fine, finishing up a few more items then I'll be releasing the latest Binary in the next day or so.
« Last Edit: February 24, 2014, 07:28:34 pm by RichardK »
 

Offline RobertH

  • Contributor
  • Posts: 11
  • Country: de
    • monochromatic
Re: Hantek 6022BE 20MHz USB DSO
« Reply #365 on: February 24, 2014, 07:28:02 pm »
if(MemSize >= 1) ...

Outch ...
Sorry, I'm not a signature, I'm just tidying up this mess ...
 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #366 on: February 24, 2014, 08:45:24 pm »
Are you using Visual Basic for the GUI? Or how are you implementing it?

All the code is C++, using C++ Builder which uses VCL (Visual Component Library).
 

Offline pickle9000

  • Super Contributor
  • ***
  • Posts: 2438
  • Country: ca
Re: Hantek 6022BE 20MHz USB DSO
« Reply #367 on: February 24, 2014, 09:20:46 pm »
Richard,

Is the demo mode your creation or related to Hantek? I ask because I was wondering it could be used in a classroom situation. Not relating to myself it just seems that if you could load waveforms with it then it could be used for that purpose.

I'm really enjoying this thread.
 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #368 on: February 24, 2014, 09:55:09 pm »
Is the demo mode your creation or related to Hantek? I ask because I was wondering it could be used in a classroom situation. Not relating to myself it just seems that if you could load waveforms with it then it could be used for that purpose.

I created it but I got the idea from the Hantek 6052BE software which has a Demo mode when started up and no device connected. The Hantek demo mode however is very basic, it doesn't let you choose frequency (it has a few pre selected frequencies), it doesn't let you choose Wave Function (sine or random only).

I created it mainly for testing purposes, since it was inconvenient to have the 6022BE hardware with me during development, and testing without the hardware is very limited.
« Last Edit: February 24, 2014, 09:57:18 pm by RichardK »
 

Offline Rasz

  • Super Contributor
  • ***
  • Posts: 2616
  • Country: 00
    • My random blog.
Re: Hantek 6022BE 20MHz USB DSO
« Reply #369 on: February 25, 2014, 12:42:17 am »
RichardK have you considered collaborating with sigrok.org people?

Never heard of them before, and their site is down... What are they, like the DD-WRT of the Oscilloscope world?

Its back up again. They are the Openwrt of measurement equipment world :) (DDWRT guys are actually pretty hostile to forking/compiling manually).

Try getting in touch with them, maybe you will get some help, and at the very least you will can look at their code or reuse it (if you like gpl)
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
afaik their Oscilloscope UI is very immature and lacking, and you are doing great job with hantek, It would be great if it could be leveraged in some way to support more hardware. I dont know about their organization structure, but maybe they get contracts/commercial support and could even pay you for code contributions.
Who logs in to gdm? Not I, said the duck.
My fireplace is on fire, but in all the wrong places.
 

Offline Rick Law

  • Super Contributor
  • ***
  • Posts: 3423
  • Country: us
Re: Hantek 6022BE 20MHz USB DSO
« Reply #370 on: February 25, 2014, 05:46:01 pm »
RichardK,

As you know, I have been testing your Open6022BE so I was trying various things that I don't usually do just to exercise the software.  This last weekend for a couple of days I use it as I normally would - just focused on getting my own things done as oppose to checking if the software feature works and how far does it work.

Here my observations from the pure user perspective: This software is very workable and friendly.  A few things get in the way:
1. Lacking ability to adjust V/div for math (and reference)
2. Save and restore the settings (v/div, trigger, color, etc.) upon restart
3. I would dearly love to say click on a few items of the "debug info" and that that few stay on screen.  But this one is the least important - after a while, the eyeball automatically focus on the info I am interested and the brain tuned out the other distractions.

I also needed to switch back to stock software to run remote-desktop so I can keep an eye on it while I munch down my lunch in the kitchen.  I am not sure why under RDC the Open6022BE would draw only the last trace (Ch1+ Ch2+math will draw the last one=math trace only).  I have to do more experimentation there.

This is very good piece of work.  Very user friendly and much much more powerful than the stock software.  Very good work.  Hats off to you.

Thanks, Richard!

Rick
 

Offline Mark_O

  • Frequent Contributor
  • **
  • Posts: 939
  • Country: us
Re: Hantek 6022BE 20MHz USB DSO
« Reply #371 on: February 25, 2014, 06:09:08 pm »
Here my observations from the pure user perspective: This software is very workable and friendly.  A few things get in the way:

2. Save and restore the settings (v/div, trigger, color, etc.) upon restart

I'd definitely have to second this one.  While there aren't a huge number of settings to configure, having them go away when you shut down, and have to manually be reset every time isn't a very good use of computer resources.  I.e., don't make me do it's work for it.  ;)

There are plenty of times where one circuit setup will be worked on over multiple sessions, and having state retention just makes sense.  Having it be a "blank slate" on every start isn't very user-friendly.  As a bonus, being able to Save/Load several different sets of configuration Settings can be helpful when moving back and forth between projects.

This isn't a criticism, just echoing the suggestion Rick made, with a +1.   :-+
 

Offline Matchless

  • Regular Contributor
  • *
  • Posts: 120
  • Country: za
Re: Hantek 6022BE 20MHz USB DSO
« Reply #372 on: February 25, 2014, 06:18:41 pm »
Rick,
      Just wondering, have you tried with any other remote desktop program? Maybe the free Teamviewer?

Richard is really moving on this and I agree with you, your point 2 issue is very irritating, it is on his todo list and I am also hoping he gets that one done soon! I see Mark_O also thinks so.

It would be quite interesting if the early posters would do a review of OPEN6022BE and add the latest findings to the earlier review post as a comparison.

Do you know if anyone has figured out why two drivers are installed (one is hidden)?

Regards
Matchless
 

Offline pickle9000

  • Super Contributor
  • ***
  • Posts: 2438
  • Country: ca
Re: Hantek 6022BE 20MHz USB DSO
« Reply #373 on: February 25, 2014, 07:03:24 pm »
It would be interesting to have two more vertical channels, you could have them populated with math and saved waveform functions. 
 

Offline RichardK

  • Regular Contributor
  • *
  • Posts: 157
Re: Hantek 6022BE 20MHz USB DSO
« Reply #374 on: February 25, 2014, 09:32:16 pm »
1. Lacking ability to adjust V/div for math (and reference)

Not sure what you mean, changing the Voltage Division for Math and Reference works fine here.

Quote
2. Save and restore the settings (v/div, trigger, color, etc.) upon restart

I have this in the Todo List, but saving it for last due to all the changes that are in between and I don't want to have to rewrite it over and over for every new change added between.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf