EEVblog Electronics Community Forum

Products => Test Equipment => Topic started by: Fraser on May 27, 2013, 10:12:32 am

Title: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on May 27, 2013, 10:12:32 am
To add to my growing stack of Hantek test gear, I have just ordered their budget DSO, the 6022BE.

I have already purchased the 1025G Function Generator and 4032L Logic Analyser so I thought adding a basic oscilloscope would complete the set  ;) It has two channels, FFT and 48Msps real sampling rate (single shot).

Make no mistake, this will be a very basic USB oscilloscope with only 48msps but it will have its uses none the less. Sadly no external trigger input is provided so one channel will provide the trigger. It does have the x-y mode that I need so that is a bonus. I see that there is an 'OpenHantek' project that may support this DSO in the future. An SDK is provided by Hantek.

Once the unit arrives I will provide internal pictures of it and a run down on the software performance. This DSO is not an alternative to 'real' DSO's with >1Gsps but at GBP49 ($75)delivered, its cheap enough to have in the test equipment inventory and competatively priced in the marketplace.

My unit is coming from 'Goodlucksell'

http://www.ebay.co.uk/itm/Hantek6022BE-PC-Based-2-CH-Oscilloscope-20MHz-48MSa-s-gl-/281110701285?pt=UK_ToysGames_RadioControlled_JN&hash=item417380e4e5 (http://www.ebay.co.uk/itm/Hantek6022BE-PC-Based-2-CH-Oscilloscope-20MHz-48MSa-s-gl-/281110701285?pt=UK_ToysGames_RadioControlled_JN&hash=item417380e4e5)


I expect this two channel unit to be 'cheap and cheerful' but the software quality, or lack there-of
will be the key to its usefulness. There has been a recent software update to fix some issues.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: amyk on May 27, 2013, 11:01:06 am
That 48Msps suggests something very common (http://www.cypress.com/?id=193) inside...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on May 27, 2013, 02:29:40 pm
When you look at what you get for GBP49 it can't be a very expensive chipset inside the unit ?

I will let you know when I get it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on June 13, 2013, 12:23:20 pm
The 6022BE arrived today.

I have quickly whipped its clothes off to see what lives inside.

For GBP49 delivered I did not expect a lot but see what you think.

The key components are as follows:

1. CY7C68013A-100AXC
2. 24LC02 EEPROM
3. Dual Channel ADC with glued on heat-sink. Likely to be a 40MHZ AD device.
4. 2 Analogue input channels. Each contain 74HC4051, 5 pin 'HRA' amplifier, Qty 2 in cascade and a 3 pin 'A7' device.
5. AMS1117 3v3 regulator


There are positions on the PCB for another CY7C68013A-100AXC, 24LC02 and a SMSC USB2512A USB Hub. These would provide a 16 Channel Logic Analayzer function to the unit.

There is also a position for a 5V supply. Interestingly, the only components needed are a socket and a diode. There is no polyfuse in the external supply rail unlike the USB feed.

Pictures to follow.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on June 13, 2013, 12:47:11 pm
Ok here are the pictures.

Nice PCB. It is laid out in a logical manner.

The parts count is relatively low and a CY7C68013 development board costs around $10 from China. But I still don't think I would bother to build one of these using such a board as the additional parts, case, scope probes and my time would make it far more expensive than GBP49. In those terms it is very good value for money. Next test will be to see how the unit performs with the infamous Hantek software package !
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: tinhead on June 13, 2013, 01:00:59 pm
from pinout i would say the ADC is AD9288.

Btw, do have have higher res pictures? PM
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on June 13, 2013, 01:08:24 pm
Yes I have the 8mp pictures that my camera produces but I didn't want to eat Dave storage with them. I will upload a couple of higher resolution pictures of the PCB for you.

I note that another forum member has posted a review of this unit here:

https://www.eevblog.com/forum/testgear/hantek-6022be-will-it-work-for-me/msg232007/#msg232007 (https://www.eevblog.com/forum/testgear/hantek-6022be-will-it-work-for-me/msg232007/#msg232007)

I note that the screening cans have not been fitted to the input amplifiers but the PCB has positions for such. This may explain some of the noise issues that are reported but it could be other factors as well.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Anks on June 13, 2013, 01:49:13 pm
Im sure there is a open source project making  better software for the scopes. Ill look back in my history see if I can find it

http://www.openhantek.org/ (http://www.openhantek.org/)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on June 13, 2013, 02:12:27 pm
Yes I found the open source software but sadly it does not support the 6022 yet. I will keep an eye out for other software that may work as the 6022 is basically a common CY7C68013A based DSO.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on June 13, 2013, 02:17:36 pm
Two slightly higher quality images...... as requested by some members. full Res pictures are 4mb in size and I can email if required
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: tinhead on June 13, 2013, 03:11:58 pm
Yes I have the 8mp pictures

got them, thanks !

I note that the screening cans have not been fitted to the input amplifiers but the PCB has positions for such. This may explain some of the noise issues that are reported but it could be other factors as well.

Sscreening cans, yeah, maybe used in higher bw model only? Savings :P

the noise could come from the DC/DC converter which powers the input stage (not that bad, two J-FET opamps AD8065).
The DC/DC converter, is it, Mornsun A0505S-1W ?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on June 13, 2013, 03:33:18 pm
Mornsun A0505S-2W
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: womai on July 07, 2013, 03:30:10 pm
I recently did a teardown wanted to do a review of the Hantek 6022BE myself but saw that Aurora has already posted a lot of good pictures and description of the instrument's guts - better quality than the cell phone pictures I took. What I can add is a review about the unit's functionality and usability (or lack thereof, as you will see below).

Full disclosure: I designed and am selling my own USB/PC based entry-level oscilloscope (the DPScope, see http://www.dpscope.com (http://www.dpscope.com) if you are interested in the details), so clearly this unit is my competition and there is a possible conflict of interest. So if you want to take any criticism from my side with a grain of salt, be my guest. That said, I will only report my objective observations; if you spot a mistake in my review, or if things change (e.g. new software version that fixes some shortcomings) please contact me and I will update the review. 

I was intrigued by the 6022BE's ultra-low price point (you can get it for around US$70 including free shipping if you shop around a bit), combined with what seems to be quite useful performance specs. Granted, 48 MSa/sec won't give you resonable display for a 20 MHz signal without some excellent sin(x)/x interpolation algorithm - which I did not expect to find here - but it's still a pretty good number. So off I went and got myself such an instrument so I could have a closer look.

Construction quality is actually pretty solid - sturdy extruded aluminum enclosure (many much more expensive models use plastic), the PCB inside is well layed out and soldering is good quality. Springs make sure the enclosure is connected to electrical ground. BNC connectors are metal throughout. So overall the hardware makes a very good impression, especially given the low cost of the instrument. (you can find older reviews of other Hantek scopes that show very shoddy construction so they clearly made a lot of progress in this department over the past few years).

Unfortunately that's already the really good part. Let's go to the mediocre stuff - the software. Functionality here is very basic - at first the GUI looks ok but then you quickly find lots of basic stuff that is missing. Why is there no datalogger mode for slow speed signals? Would be trivial to implement. Why can't you set the horizontal position? As others noted, there is no way to zoom in or scroll through the (supposedly 1M long) waveform except with hundreds of mouse drags; in other words, useless. Also this is the first scope GUI where you have to scroll the controls panel to have access to all controls (horizontal, vertical, trigger) - just make the controls a bit close together. There is no averaging mode to get rid of noise on the waveform (again, would have been trivial to implement in the software, so I fail to see why they didn't bother).

Now to functionality. This is where it really gets bad, especially if you initially believe the banner specs. I tested on two different computers (a laptop and a desktop, both fairly recent models, and both running Windows 7 64-bit home edition) but the results were identical on both.


So what's my overall verdict? Promising hardware and good build quality, but the software that comes with it is disappointingly shoddy, but far surpassed in terms of disappointment by the unit's real-world performance. As it is (broken acquisition at 5 us/div and beyond) even basic use is only possible for signals of around 200 kHz or less. That's a full 1% of the advertized range!! Even where you CAN see the signal and trigger on it, triggering is unstable. Overall performance is downright horrible compared to what Hantek claims it can do. So I would strongly recommend to stay away from it and get yourself something else for a few bucks more.

It may be possible that some of the problems can be fixed either in software or in firmware. Please let me know if anyone hears or sees something in this respect. Most importantly, the faster timebase settings, followed by trigger stability. After that, averaging, datalogger (roll) mode, cleaner GUI layout. Not sure I am getting my hopes up too high, given the lack of software progress of the Hantek software for other models - hardly any changes/improvements for years.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on July 07, 2013, 05:03:06 pm
Womai,

Thank you for this excellent insight into the limitations of this cheap DSO.

Mine is currently sat, still boxed, in a pile with the other Hantek kit I bought, awaiting use.

I own several DSO's including the Rigol DS1052E and a Tektronix THS720A so I will not shed any tears over this unit if it is total rubbish. It is a great pity that what looked to be decent hardware performs so poorly in the real world. There is no excuse for the odd behaviour that you noted.

I purchased my 6022BE as an accessory to my Hantek Logic analyser and function as it completed my little 'set' of portable test tools for use on my laptop. It was a 'whim' purchase, but at least it was cheap  :)

I also have a neat little ELAN USBscope50 50MS/s DSO which is little bigger than a USB memory stick. That unit is an isolated USB DSO that actually works so I will use that in my laptop kit for checking power rails for noise etc.

http://www.saelig.com/product/PSPCEL004.htm (http://www.saelig.com/product/PSPCEL004.htm)

I will fire up my 6022BE and test its behaviour. Not that I doubt your review content, but potentially you could have a duff unit ?

A classic case of "you get what you pay for"  :-BROKE
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: womai on July 07, 2013, 05:47:02 pm
You're welcome to double-check my results. As I mention, I find it hard to believe that such gross malfunction as I observe could be missed at even the most cursory quality checkout. So there are two possibilities:

- They could not get triggering etc. to work in time (or because of some hard limitation of the design) and decided to drop whatever they had onto the unsuspecting customer, hoping most beginners won't notice.

or

- Something in my setup does not work well with the scope. Something broken in my Windows installation, some hardware detail, etc. Although the fact that two quite different PCs show exactly the same makes me less hopeful in this respect.

I am very curious to see what you find on your side.

At least that applies to the behavior at faster sample rates. Misbehavior at 5 us/div, noisy trigger, short records at 2us/div and faster, noise spikes have been noted by others before so I guess they are there by design...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on July 07, 2013, 06:45:45 pm
Ok after a quick and dirty test on my lounge floor I have feedback on my unit.

I am driving the 6022be with a Sony Netbook running Win7 Home. The signal source is a Digimess FG100 20MHz function generator with its output set to 1V. 50R through-termination and decent test lead used.

1. I set the FG to 100kHz Sine and pressed the 'Auto' button for the 6022BE. Sine wave displayed perfectly with some trigger jitter but nothing more than I have seen on other cheap DSO's.
2. Set FG to 1MHz Sine and again used 'Auto' feature on 6022BE. Display showed a perfect Sine wave with good triggering.
3. Set FG to 1MHz Square and used 'Auto'. Square wave was represented well with good square tops and a little ringing on the leading edge. Triggering jittered a little then settled down.
4. Set FG to 10MHz Sine. Auto produced a perfect sine wave with stable trigger.
5. Set FG to 20MHz Sine. Auto produced a very respectable sine wave with good triggering.
6. Noise level with no input checked. on 20mV div range only 5-10mV noise and impulses could be seen.
7.Tried the scrolling of the waveform......... it only appeared to work for lower frequencies (slower time-bases). At higher frequencies only one screen of captured signal data was available to see. This 'function' really isn't much use at all.
8. During the displaying of the waveforms on the screen I noted that even after an AUTO setting the last half of a sine wave at the right hand side was flickering and you could stop the capture and have part of the waveform missing ! Most odd and no idea why this happens.

My view.... my unit does produce accurate renditions of the test sine wave all the way to 20MHz so its maths is working pretty well. The trigger is definitely stable enough on my unit to capture and view a live signal at all frequencies up to 20MHz. Stopping the capture produces a clean waveform.
The capture does have an odd flickering end to it on the right of the screen. This did not present a problem as AUTO sets the TB to show several cycles of the waveform. It could be a pain though if the flickering section contained the glitch that was being hunted for ! The memory is a mystery to me. The scrolling through a waveform is severely limited and practically useless. The noise on my waveforms was not invasive and was less than 10mV on my tests.

In summary. This DSO  will meet my needs for checking computer power rails for noise but it is not useful in trying to find a glitch in a large capture of signals. Not junk though. I am pleasantly surprised.

Basic ? Very !
Good software ? NO ! The hardware quality far exceeds that of the software.
Accurate ? It appears to be accurate enough for most basic tasks.
Trigger ? Satisfactory.
Noise ? 5-10mV.
Memory ? Virtually unuseable
Value for money ? You decide. It can be purchased for around US$70.

What this thing needs is to be supported in the Open Source software that has been developed for Hantek's more expensive DSO's.

http://www.openhantek.org/ (http://www.openhantek.org/)

http://hantekdso.sourceforge.net/ (http://hantekdso.sourceforge.net/)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on July 07, 2013, 07:16:53 pm
Yes I have the 8mp pictures that my camera produces but I didn't want to eat Dave storage with them. I will upload a couple of higher resolution pictures of the PCB for you.

I note that another forum member has posted a review of this unit here:

https://www.eevblog.com/forum/testgear/hantek-6022be-will-it-work-for-me/msg232007/#msg232007 (https://www.eevblog.com/forum/testgear/hantek-6022be-will-it-work-for-me/msg232007/#msg232007)

I note that the screening cans have not been fitted to the input amplifiers but the PCB has positions for such. This may explain some of the noise issues that are reported but it could be other factors as well.

What I posted then was more personal experience with this scope than I formal review.  I so much wanted to see some review but this thread didn't exist then, so I shared some of my views and experience with others.

(Thanks, Womai pointed out this thread).  Now I can add my 2 cents in....


Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: womai on July 07, 2013, 07:52:34 pm
Hmmmm, based on Auroras feedback I went back and gave it another try. Here's what I found:

It seems I have to use autoset at least once at some higher timebase. Then it will trigger even at faster timebase settings. (I work a lot with scopes and don't use autoset too often, that's why I didn't try autosetting after initially checking that it does work at some slow frequency). If I just start the software and try to set some fast timebase manually the triggering will not work, as noted in my initial post. After the autoset I can manually change the timebase and it still works. Bug in the software?

I also observe the flickering waveform. It seems the scope can't really start the capturing at a precise moment relative to the trigger so there is an uncertainty of ~1 signal period where the record really lies with respect to the trigger. The software seems to align the waveform correctly (at least after auto setup) but it means some variable portion of the waveform at the beginning and/or the end is missing - different at each capture. Basically only the center portion of the acquired record is consistently usable. You can see similar flickering at the record start when you scroll to the beginning of the waveform.

That said, 5 us/div still does not work at all. Even with autoset there is never a stable display. Aurora, maybe you could try that? (set frequency to around 30 kHz to make autoset go to 5 us/div).

Still have problems with somewhat unstable triggering at slower timebase settings. I use a Rigol DS1022A signal generator which from previous experience I know produces a very clean signal with very little noise. My other scopes have not problem whatsoever to cleanly trigger on its output signal.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on July 07, 2013, 08:26:26 pm
...Now to functionality. This is where it really gets bad, especially if you initially believe the banner specs. I tested on two different computers (a laptop and a desktop, both fairly recent models, and both running Windows 7 64-bit home edition) but the results were identical on both....

Actually, the software may be more XP friendly than Win7 then.  I use XP and the software ran well (no lags, smooth and snappy) on even a very slow but very small 1GHz laptop I often use for space reasons.

The software is portable (don't need to install - just copy the installed folder.  You do need to install the driver).  I just copy the folder over and without fuss the software is running.  (Without having to run install means I am having less junk clogging up the system and adding junk to the registry.  I like software that just copy-and-go.)


Yeah, I hate that too.  I have a couple of capacitors at hand just because of that.


Not to confuse others, it adds two devices via one usb connection - one for each channel.  So, one single USB cable does it.


This one confused me a bit at the start too.  Until I read the manual that both channel need to be grounded.  It does execute but no feedback.  My volt readout is still high (by about 2-5%) but not as much over as before I ran the self calibration (by about 5-7%).


After using it for a while, I got the trick worked out now:
- pause the display
- kill the cursor (otherwise, mouse click sets cursor)
- now point at wave form, press mouse button, and drag the wave from left to right
Then you can see the part of the wave before the trigger.  Problem is, the amount of info before the trigger is random.  What I guess is this: The software appear to treat the memory buffer as a ring.  The data just get written in and once it gets to the end, it returns to the start but clears the entire buffer.  So, when the trigger occurs when the WRITE pointer is near the end, you captured lots of pre-trigger but little post trigger wave form when the buffer is plotted start to finish linearly.  However, when the WRITE pointer is near the start of the buffer, you captured darn little pre-trigger info.


No kidding here.  The noise is awful and it does cause trigger to hit.  It is very annoying but at least is is still useable.  I was able to find the 50mV resonance wave to measure an inductor's inductance.  I do find a reboot sometimes helps.  So it could be picking up the noise from other connected devices.

I think I was caught with this same confusion too, but here is what I found out:
At 2us or below is when it captures at 48msps and at merely 1060 datapoints.  At 5us or slower, it goes to over 100K datapoints at 16msps.  The slower the more datapoints.
BUT...
When you freeze
the display and zoom in/out (say capture at 5us and zoom to view at 100ns), the display does not show your capture frequency (5us=100,000+ samples) and instead it shows what it would be at 100ns (1060 samples at 100ns).  After I realized that, I can see that it works.  Of course, the noise still make that difficult.


I agree with you 100% here...  Only 8 bit resolution to +- 5Volts, so it is about 40mV per ADC bits.  I am not sure if they have a way (such as lowering their reference voltage) to get the lower readings.

At best sampling rate (48msps), it is about 21ns between samples.  With a 10mhz wave, you have 100ns per period, 50ns high and 50ns low.  Best case is 2 samples during wave-high, and 2 samples during wave-low with PERHAPS another sample somewhere in the middle.  Can't measure rise time with that.


Overall though, I am please with the scope.  For merely $70, it does more than I expect.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on July 07, 2013, 08:30:05 pm
I should have mentioned that I also experienced the failure to trigger unless Auto was used initially. Thanks for pointing that out. It is strange that the trigger appears totally non functional until Auto is initiated. Software bug likely. I have put the unit back in the lab. I will try the 5uS range and let you know the result.

I only went down to 100kHz so will repeat the test at lower frequencies to see how the trigger behaves.

Thank you for reviewing this unit, it gives me the incentive to test my unit  :)

I think we are seeing that US$70 buys a DSO with flaws, hence why I purchased the DS1052E after seeing Dave's review...its a real DSO that does not leave you fed up because of 'niggles' in firmware/software.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on July 07, 2013, 09:08:39 pm
Hmmmm, based on Auroras feedback I went back and gave it another try. Here's what I found:

It seems I have to use autoset at least once at some higher timebase. Then it will trigger even at faster timebase settings. (I work a lot with scopes and don't use autoset too often, that's why I didn't try autosetting after initially checking that it does work at some slow frequency). If I just start the software and try to set some fast timebase manually the triggering will not work, as noted in my initial post. After the autoset I can manually change the timebase and it still works. Bug in the software?

I also observe the flickering waveform. It seems the scope can't really start the capturing at a precise moment relative to the trigger so there is an uncertainty of ~1 signal period where the record really lies with respect to the trigger. The software seems to align the waveform correctly (at least after auto setup) but it means some variable portion of the waveform at the beginning and/or the end is missing - different at each capture. Basically only the center portion of the acquired record is consistently usable. You can see similar flickering at the record start when you scroll to the beginning of the waveform.

That said, 5 us/div still does not work at all. Even with autoset there is never a stable display. Aurora, maybe you could try that? (set frequency to around 30 kHz to make autoset go to 5 us/div).

Still have problems with somewhat unstable triggering at slower timebase settings. I use a Rigol DS1022A signal generator which from previous experience I know produces a very clean signal with very little noise. My other scopes have not problem whatsoever to cleanly trigger on its output signal.

Womai ,

Do you mean 5ns or 5us?

I have encounter no problem triggering at 5us at all.  It gets crazier as it gets lower.  At 2ns and 5ns it gets really crazy.

It captures only about 1 screen wide worth (10 division) of data for display - at 5ns, that would be merely 50ns worth of display or 2 samples at 48mhz (20.8ns/sample).    So I can see any slight shift in trigger causing the display major jitter.

Attach a screen capture of triggering at 100ns to capture a 2mhz square wave - 100ns is 50 times faster than 5us.  Works just fine with very slight jitter.

(EDIT - typo -- it was 1us, not 100ns, replaced paragraph above)
Attach a screen capture of triggering at 1us to capture a 2mhz square wave - 1us is 5 times faster than 5us.  Works just fine with very slight jitter.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on July 07, 2013, 10:03:21 pm
It captures only about 1 screen wide worth (10 division) of data for display - at 5ns, that would be merely 50ns worth of display or 2 samples at 48mhz (20.8ns/sample).    So I can see any slight shift in trigger causing the display major jitter.

By the way, having used it for a couple of months...  I learn to deal with it: If I am looking at fast things, I have to use capture and view.

I capture at 2us/div however fast the signal.  At 2us/div, it captures at the max speed of 48msps and a screenful of data is 10 division = 20us worth.  I have 20us of data to zoom in on - that is 1000 points.   Probably it is a bit more than a screenful since saving the data would save 1060 points.

Anything faster just reduces my data points.  Capturing too much faster doesn't work mathematically - For example, at the timebase of 5ns to capture, I have only 1 screenful which is 50ns worth of data.  50ns is 2 data points of data since 48msps=21ns/sample.   Everything is a straight line with only 2 real data points captured in the duration.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: womai on July 07, 2013, 10:14:15 pm
I really mean 5 us (microseconds), not ns (nanoseconds). Slower than that and it works pretty well except for the glitchy trigger. Faster than that (2 us and up) we have the issue of the truncated waveform but at least triggering is stable after autoset. (I guess you are right that the small record size at that speed just makes the trigger-to-data alignment issue more visible, it's probably just the same for slower timebase settings but there the buffer is large and the flaky area at the beginning and the end is far outside the default display area).

I would say from the hardware side the unit has potential. But firmware/software would need a through scrub for it to show. Fix the trigger instability either by adding hysteresis (assuming trigger is done in hardware) or by simply discarding "wrong" captures in the software. (although one would need to know more about the actual design internals to be able to tell if a good, solid fix is possible at all). Add averaging. Definitely add a slider and a numerical display for the horizontal position. Add indication of the trigger position on the time axis.

Right now I must say I'm glad this is just a toy to play around for me and I am not dependent on it to do real work...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: womai on July 07, 2013, 10:19:00 pm
>Attach a screen capture of triggering at 1us to capture a 2mhz square wave -
> 1us is 5 times faster than 5us.  Works just fine with very slight jitter.

1us/div works fine or me as well (after doing at least one autoset, that is), as does anything slower or faster than 5us/div. 5us/div is the only timebase setting that just won't trigger and produces garbage data (lots of partial waveforms stitched together).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on July 07, 2013, 11:13:14 pm
>Attach a screen capture of triggering at 1us to capture a 2mhz square wave -
> 1us is 5 times faster than 5us.  Works just fine with very slight jitter.

1us/div works fine or me as well (after doing at least one autoset, that is), as does anything slower or faster than 5us/div. 5us/div is the only timebase setting that just won't trigger and produces garbage data (lots of partial waveforms stitched together).

Interesting...  I had the program still running so I switched to a 1Mhz wave at 5us and after about a minute, I switch to 10us trigger with the same 1Mhz square wave oscillator.  It showed for 20 seconds and the program did an abnormal termination.  Whether it is program bug with Hantek or with other programs, I am not sure. 

I rebooted it again, ran it for 5 minutes so far... 5us trigger with a 1mhz square wave.  No problem aside from small noise jitter.  I placed the cursor at the rise and fall point and for 5 minutes the wave stay within the cursor except for once.  The frequency measurement window shows 1mhz on the dot.

After 5-7 minutes, I switch to 10us trigger with the same 1 mhz square wave.  It is jittering a bit more since they are now narrower.  But it triggers just fine.  The measurement shows 1mhz on the dot.

The 1mhz oscillator I have is too fast for 10us trigger.  The wave is too narrow to see details.  Too bad I do not have a good stable signal source below 1mhz.  I guess I will wait and see with you to see what Aurora comes up with.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: amyk on July 08, 2013, 05:17:26 am
It might help to state what USB (host) controller you're using, and what else is plugged into it, if anything. Other devices using the bus can cause all sorts of weird issues in a realtime application like this.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on July 08, 2013, 10:55:43 am
I have read many times that a real time data acquisition product should not share the USB bus with any other item. My Win7 Netbook is no powerhouse PC as it is a 1.83GHz Atom but it copes well with the program. I used only the 6022BE on its USB bus so there were no contention issues  :)

Your point is very valid where test equipment is concerned. Bearing in mind that I was going to hook up the 6022BE DSO, 1025G FG and 4032L LA on one DellX300 Win XP laptop computer....that no longer looks like a good idea ! Maybe that is the reason why we have not seen the mystical Hantek USBXI multi unit docking station ? Bus contention may have made the units misbehave. This is the downside of the symbiotic nature of PC test equipment.
Fortunately I have at least six Dell X300's so I could even dedicate one to each piece of test kit   ;D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: djcristi on August 12, 2013, 08:54:01 pm
i received this 6022be scope 1 week ago, done some basic testing, as many other said, ok hardware but bad software (crappy actually). the most annoying thing is the scroll on the a single shot. for eg. i set it to 500ms/div, it records the signal, you zoom in after, and you want to center the segment you want to see more details, this is where it gets ugly,  cause you have to drag with the mouse left/right, and most of the times it refuses to do that. maybe it's my windows (7 64bit) or my monitor 1440p resolution, but i find the software to be useless anyway....

i am using it to trace an kwp2000 signal (~10kbps) so for this use it's enough 40msps , actually it's 1msps on longer timebase...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 13, 2013, 05:31:27 am
i received this 6022be scope 1 week ago, done some basic testing, as many other said, ok hardware but bad software (crappy actually). the most annoying thing is the scroll on the a single shot. for eg. i set it to 500ms/div, it records the signal, you zoom in after, and you want to center the segment you want to see more details, this is where it gets ugly,  cause you have to drag with the mouse left/right, and most of the times it refuses to do that. maybe it's my windows (7 64bit) or my monitor 1440p resolution, but i find the software to be useless anyway....

i am using it to trace an kwp2000 signal (~10kbps) so for this use it's enough 40msps , actually it's 1msps on longer timebase...

Did you turn your cursor off first?  The dragging left/right works a lot better with the cursor off.

I had a lot of problem trying to move the wave left/right until I tried turning off the cursor first (1600x1200).  It drags without problem but it is still a problem finding the wave form.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: djcristi on August 13, 2013, 08:05:36 am
i received this 6022be scope 1 week ago, done some basic testing, as many other said, ok hardware but bad software (crappy actually). the most annoying thing is the scroll on the a single shot. for eg. i set it to 500ms/div, it records the signal, you zoom in after, and you want to center the segment you want to see more details, this is where it gets ugly,  cause you have to drag with the mouse left/right, and most of the times it refuses to do that. maybe it's my windows (7 64bit) or my monitor 1440p resolution, but i find the software to be useless anyway....

i am using it to trace an kwp2000 signal (~10kbps) so for this use it's enough 40msps , actually it's 1msps on longer timebase...

Did you turn your cursor off first?  The dragging left/right works a lot better with the cursor off.

I had a lot of problem trying to move the wave left/right until I tried turning off the cursor first (1600x1200).  It drags without problem but it is still a problem finding the wave form.


i think you mean to click the "none cursor" button. yes. i always do that first, but when i try to drag the part that i want to the center (to be able to zoom it later) , it won't move, or it moves a little then jumps back where it was :((


l.e. : i've found out if you use autoset first, the scroll will work after, what a shitty software
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roboBOT on August 14, 2013, 05:16:28 pm
Hello, I'm new here and just purchased a Hantek 6022BE v 1.0.3. If I'm butting in here and should not be, please ignore or have the moderator remove.  Do not want to ruin a thread.

To begin, this is my first oscilloscope, purchased more to learn than anything else.  I'm using WIN XP Prof. on a dated Lenova laptop. There is one problem (or maybe not).  The software loaded correctly, and the driver (6022BEAMD642) seems to have installed correctly.  However, when I run the initial setup test, I can get a square waveform only on CH1.  CH2 shows mostly noise, and no distinguishable waveform.  So question:  should I be getting a square waveform on CH2 self-test?  I note in my Hardware that it lists only DRIVER 2  Should there be a DRIVER 1?  I have tried reinstalling, but same thing.

TIA
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 14, 2013, 07:33:22 pm
Hello, I'm new here and just purchased a Hantek 6022BE v 1.0.3. If I'm butting in here and should not be, please ignore or have the moderator remove.  Do not want to ruin a thread.

To begin, this is my first oscilloscope, purchased more to learn than anything else.  I'm using WIN XP Prof. on a dated Lenova laptop. There is one problem (or maybe not).  The software loaded correctly, and the driver (6022BEAMD642) seems to have installed correctly.  However, when I run the initial setup test, I can get a square waveform only on CH1.  CH2 shows mostly noise, and no distinguishable waveform.  So question:  should I be getting a square waveform on CH2 self-test?  I note in my Hardware that it lists only DRIVER 2  Should there be a DRIVER 1?  I have tried reinstalling, but same thing.

TIA

First answer to your last question:  I too see only driver 2 while both my channels are working.  I did a registry search and don't find DRIVE1 or DRIVER2 in the registry either.  Perhaps DRIVER1 is a mini-port driver and DRIVER2 connects to the mini-port (like the IDE/ATA driver and then a driver for the disk itself).

Second, may be obvious but since this is your first scope, may be you missed this:  Did you check-mark Ch2 to turn it on?  See on the attached jpg ithe green checkmark close to the big round "knob".

(https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/?action=dlattach;attach=57610;image)

Good luck! Hope this helps.
Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roboBOT on August 15, 2013, 03:42:19 am
Thanks Rick, for the feedback.  Yep, the newbie thingy about sums it up.  The problem was me! :-//  I thought the probes must be connected to separate test points.  Worked perfectly when I connected the probes to the same input, and a ground to the other.  Daaaa!  Should prove to be fun.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 15, 2013, 04:07:52 am
Thanks Rick, for the feedback.  Yep, the newbie thingy about sums it up.  The problem was me! :-//  I thought the probes must be connected to separate test points.  Worked perfectly when I connected the probes to the same input, and a ground to the other.  Daaaa!  Should prove to be fun.
This forum is full of experience and most folks here are very kind and helpful to newbies.

I too am kind of new.  I am a newbie on second-tour.  (I did a little electronics long time ago in college because it was required, and I just recently return to do it for fun.)  I forgot the stuff I learned eons ago and I am learning them anew.

With USB scope, remember one very important thing:
Your scope shares a ground with USB which means the share the ground with your computer, which means the monitor, which means... well, your dish washer, your refrigerator...

Perhaps for the first week or so until you get more used to operating this scope, may I suggest: To ensure isolation, use a laptop on battery, NO external monitor and NO wired network.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roboBOT on August 15, 2013, 05:45:39 am
Thanks Rick.  I have it on an old Lenovo Pent IV, XP running on battery power except to recharge.  Not physically connected, but on wireless.  So if it blows the system, no big deal.

Gord
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: MrAureliusR on August 15, 2013, 06:17:55 am
I know this scope isn't the greatest, but you can certainly have some fun with it ...  :-DD  :-DMM

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roboBOT on August 17, 2013, 03:04:28 am
Good one.  :-DD

Getting serious, Re: Driver 1 & 2 .... Strange, today my system did not recognize the Hantek, and had to reinstall driver(s).  This time it loaded both 1 & 2.  Everything seems good.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 17, 2013, 04:36:34 am
Good one.  :-DD

Getting serious, Re: Driver 1 & 2 .... Strange, today my system did not recognize the Hantek, and had to reinstall driver(s).  This time it loaded both 1 & 2.  Everything seems good.

You probably switched to a different USB port so it has to load the drivers for that USB port. 

Re: loaded 1&2 - mine installed with both 1&2 also.  Let's compare notes: Check your device driver list and see if you have both listed.  I am curious as to if it list Driver1&2.  (I suspect not, but curious still.)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roboBOT on August 18, 2013, 10:27:55 pm
Only Driver 2 shows.  My system slowed down to a crawl.  Ran Alvira and found I had a virus.  No indications of one a week ago.  Loaded two software programs, one for the oscilloscope, and a SuperAntiSpyware program.  Have not used the laptop for internet, except when on vacation in July.  So could possibly be a delayed reaction to something picked up over a hotel wireless network.

Anyways, Alvira seems to have taken care of it.

When I use the Hantek for some actual work, will post the results.  It would be nice to have a waveform generator.  Guess could test a battery operated radio???



Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on August 18, 2013, 11:49:07 pm
Ummm.."supper anti spyware program" ?????

Is it from a well known vendor and from their own website ? A common malware exploit is to provide a utility that appears to be legit and worthwhile loading onto your PC. Freebies especially risky. You actually permit the installation of the malware as part of the installation process :scared:

Also be aware that most decent malware attacks will defeat the anti-virus program that is installed and make it appear that the AV has cured the problem when in fact it has not. Be careful what you do on your PC and I suggest you run some other AV programs to see what they find, if anything.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: MrAureliusR on August 19, 2013, 01:20:18 am
Avast! Is a good free one. Ad-Aware is CRAP now used to be great. I use Malwarebytes Anti-Malware alongside avast and my PC has always run great.

I heard that each cable was for a separate channel - however mine only shipped with one probe (not two as advertised) but when I touch the channel 2 input I can get a 60Hz mains wave so its clearly working with just the black plug.

Typed using Hacker's Keyboard for Android

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 19, 2013, 03:35:59 am
...I heard that each cable was for a separate channel - however mine only shipped with one probe (not two as advertised) but when I touch the channel 2 input I can get a 60Hz mains wave so its clearly working with just the black plug...

The 6022BE is suppose to include 2 probes with two sets of all the trimmings (ie: 2 plastic screw drivers, 2 probe-manual, 2 sets of color rings).  1x/10x probes with reasonable quality given the low price ($70) of the scope.

If you got only one probe, perhaps you should contact the seller or Hantek.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: MrAureliusR on August 19, 2013, 03:37:55 am
Oh believe me, I contacted the seller, lol. Because someone else paid for it, I had to get their eBay info, which I did... and anyway, I've still heard nothing back, not for lack of trying.

Because it was through eBay and it's someone else's account not a lot I can do...  |O Oh well. I'll have more probes soon anyway.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roboBOT on August 19, 2013, 05:44:06 pm
Ummm.."supper anti spyware program" ?????

Is it from a well known vendor and from their own website ? A common malware exploit is to provide a utility that appears to be legit and worthwhile loading onto your PC. Freebies especially risky. You actually permit the installation of the malware as part of the installation process :scared:

Also be aware that most decent malware attacks will defeat the anti-virus program that is installed and make it appear that the AV has cured the problem when in fact it has not. Be careful what you do on your PC and I suggest you run some other AV programs to see what they find, if anything.

Pretty certain it was infected prior to the antivirus software download.  The system had become extremely slow, almost unresponsive in search mode.  When I downloaded/ran Avira and quarantined  the EXP/2012-0507.BC.4 virus, the system returned to normal.

The spyware program is well-known http://superantispyware.com/ (http://superantispyware.com/)

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roboBOT on August 19, 2013, 05:47:33 pm
Question:  my USB patch cord has two connections, one black, one red.  As both channels work off the black connector, can I assume the red one is for recording/saving screenshots?  There is no mention of it in the manual.

TIA
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: baljemmett on August 19, 2013, 06:30:45 pm
Question:  my USB patch cord has two connections, one black, one red.  As both channels work off the black connector, can I assume the red one is for recording/saving screenshots?  There is no mention of it in the manual.

Usually that sort of arrangement is for devices that might need to draw two USB ports' worth of power - e.g. I have a cable that came with one of my external hard drives, with a mini-USB for the hard drive and two full USB plugs, one marked with a thunderbolt to mean 'power only'.  If the port the 'normal' connector is plugged into doesn't give enough grunt to power the device, the 'power only' connector is supposed to be plugged in as well.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 20, 2013, 12:36:59 am
Question:  my USB patch cord has two connections, one black, one red.  As both channels work off the black connector, can I assume the red one is for recording/saving screenshots?  There is no mention of it in the manual.

TIA

I think that is their device extension port.  This from their website on 6022BE features:
"Standard USBXI(TM) interface, easily inserts into USBXI(TM) housing to make up a combination instrument."

Rick
Title: Re: Re: Hantek 6022BE 20MHz USB DSO
Post by: MrAureliusR on August 20, 2013, 01:52:01 am
Question:  my USB patch cord has two connections, one black, one red.  As both channels work off the black connector, can I assume the red one is for recording/saving screenshots?  There is no mention of it in the manual.

TIA

I think that is their device extension port.  This from their website on 6022BE features:
"Standard USBXI(TM) interface, easily inserts into USBXI(TM) housing to make up a combination instrument."

Rick

nope, that's the card connector on the back of the device. As has been mentioned multiple times, red for extra power (not always needed) black for data. Simple as that. I bet if you opened up the cable the red one would simply have +5 and GND connected into the black cables' respective lines.

Typed using Hacker's Keyboard for Android

Title: Re: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 20, 2013, 05:31:51 pm
Question:  my USB patch cord has two connections, one black, one red.  As both channels work off the black connector, can I assume the red one is for recording/saving screenshots?  There is no mention of it in the manual.

TIA

I think that is their device extension port.  This from their website on 6022BE features:
"Standard USBXI(TM) interface, easily inserts into USBXI(TM) housing to make up a combination instrument."

Rick

nope, that's the card connector on the back of the device. As has been mentioned multiple times, red for extra power (not always needed) black for data. Simple as that. I bet if you opened up the cable the red one would simply have +5 and GND connected into the black cables' respective lines.

Typed using Hacker's Keyboard for Android

Oops, I missed that.  Good to know.  I stand corrected.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marm496 on October 05, 2013, 07:52:23 pm
from pinout i would say the ADC is AD9288.

Btw, do have have higher res pictures? PM

It's a AD9288BSTZ-40 analog to digital converter.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marm496 on October 05, 2013, 08:19:49 pm
I've been reading the spec sheet of the  AD9288, this same integrated circuit comes in 3 different flavors, 40, 80 and 100 MSPS, it seems that according to this data sheet we may replace 40 MSPS  AD9288 IC with a 100 MSPS AD9288 one, so that we could increase  6022BE's bandwidth to 100 MSPS.
It could be just great.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on October 05, 2013, 10:43:17 pm
I've been reading the spec sheet of the  AD9288, this same integrated circuit comes in 3 different flavors, 40, 80 and 100 MSPS, it seems that according to this data sheet we may replace 40 MSPS  AD9288 IC with a 100 MSPS AD9288 one, so that we could increase  6022BE's bandwidth to 100 MSPS.
It could be just great.

Hey thanks for the datasheet.  I found it very interesting.  It would be interesting if it does work.  If I am reading the sheet right, looks like +-15mV is about their typical conversion accuracy (volt match).

Anyone tried voltage calibration?  There is the VR1 sitting there looking like it is for voltage calibration.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on October 06, 2013, 12:00:11 pm
The 6022BE hardware so is so 'simple' as to almost be a development board for experimentation and improvement. Sadly that hardware is very reliant upon the appropriate firmware and software to exploit such improvements. Increasing the ADC clock would be needed to increase the sample rate. I have no idea what changes would then be required to the firmware to accept a higher sample rate, but I doubt it is a trivial task, especially for anyone not very familiar with the processor used. I bought one of these for a simple task and half hoped that this little DSO would become a popular 'project' in the development and hacking community so that better software would become available. That has no happened yet.

As has been said before. Decent hardware, pity about the firmware and software.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marm496 on October 09, 2013, 07:07:17 am
I already bought my cypress Usb microcontroller and I am been trying to get the usb hub chip to make the logic analyzer with my HANTEK 6022BE oscilloscope, I  found a company call  RS Components Ltd that is selling this chip(right now this chip is obsolete),well I ordered one at RS web site but they are asking me for call them with my credit card info ,I don't think I want to give this information  by phone to someone in UK,you can call me paranoid but I prefer to buy it somewhere else online ,although , get this IC doesn't seem to be an easy task, now a days,I will keep looking.
Increase this oscilloscope bandwidth it's not a trivial task, I agree but I think that it's worth trying. I have to learn to program the 8051 microcontroller but someday I am going to try to decipher this firmwere, somehow,it's just matter of time,well I can't promise anything but I am going to try.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on October 09, 2013, 09:22:41 am
Radio Spares aka RS Components is like Farnell / Element14, Digikey or Mouser. They are a huge component supplier to inducstry and Government organisations. RS are a very much respected company that has been around many decades. They can be expensive but they are a convenient parts source. I can state with absolute confidence that they are not a dodgy organisation  ;)

I have bought rare ICs from UTSource in Hong Kong. Cheap shipping, reliable and no problems to date. They accept PayPal.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marm496 on October 09, 2013, 09:41:11 am
Thanks Aurora,I  feel more confident now.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: tinhead on October 09, 2013, 10:37:30 am
Increasing the ADC clock would be needed to increase the sample rate.

Increase this oscilloscope bandwidth it's not a trivial task, I agree but I think that it's worth trying.

check the PCB, it looks like the second CY7C68013A can clock the second ADC (180° phase shifted) when you solder it. Of course you will need to solder R7 as well, remove i think R37 (or R35 - you have to check this first which of them is connecting together both ADC clock inputs). With two CY7C68013A the USB hub ic need to be soldered as well, and R75/R76 removed (but then R122/R12 soldered).

The missing VID/PID you will find in device driver.

So that's so far for higher sample rate, the analog bandwidth could be easy as well. There is low pass filter, R20/C25 and for second channel R25/C30. That's are 49R9 resistors and some pF caps. This need to be however evaluated for best result.
The ADC itself have 2pF on input pin, so add this as well for calculations.

Typically Hantek was using CD4051 for input att/mux, however here is aready NXP 74HC4051D, with good frequency response, so no need to change anything here.

Regards the CY7C68013A, watch out the I2C, there seems to be more than one combination (one EEPROM, two on same bus, separate chip per CY7C68013A), you will have to evaluate this as well.

And finally don't forget t check current consumption.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marm496 on October 12, 2013, 06:58:20 am
After all I bought the USB 2512B,instead of USB2512A,footprint it's the same and this is a direct replacement of USB2512A, I ordered it from microchipdirect as sample for 7.5 dollars for two pieces,well I couldn't pay 50 dollars for shipping(low budget). I have been looking around 6022 pcb,locating all  resitences and paths you mentioned,I am doing it slow and carefully ,so it's taking time to finish.
When I have results, I will post them here. Do you know that Rigol is using five AD9288-40 to perform 1GSPS in their scopes?
Thanks, Aurora and Tinhead for your answers and advices. ;D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marm496 on October 12, 2013, 07:47:37 am
Talking about EEPROM 24LC02B on the second uC,it seems  to be connected  directly to SDA pin and SCL pin on uC,it's just needed a pair of 2.2K pullup resistors and a 0.1u cap as far I could see. But it's necesary  check the address pins of the 24LCxx for proper usb configuration. This memory configure uC VID&PID values at boot time as well as boot code loading. LC02B is not the only eeprom type allowed,We could use any of this:

24LC00    16    Bytes
24LC01    128  Bytes
24LC32     4K   Bytes   
24LC64     8K  Bytes
24LC128   16K Bytes

To use another memory type  we just need to adjust A0, A1, A2  values according to CY7C68013A-100AXC datasheet.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 20, 2013, 03:42:31 am
At 2us or below is when it captures at 48msps and at merely 1060 datapoints.  At 5us or slower, it goes to over 100K datapoints at 16msps.  The slower the more datapoints.

Rick, did you notice at what point it acquires the full rated 1M samples?  And is that split between the two channels?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on November 21, 2013, 08:27:35 am
At 2us or below is when it captures at 48msps and at merely 1060 datapoints.  At 5us or slower, it goes to over 100K datapoints at 16msps.  The slower the more datapoints.

Rick, did you notice at what point it acquires the full rated 1M samples?  And is that split between the two channels?

Mark,

At 50ms (1Mhz) it starts acquiring at full 1M samples (1,047,552 for each channel total 2x1047552)
At 20ms (1Mhz) it is at 523264 samples each Channel
At 10ms (1Mhz)= 523264
At 5ms (1Mhz)= 523264
At 1ms (1MHz) = 130048
At 100us (1Mhz) = 130048
At 20us (4Mhz) = 130048
At 10us (8Mhz) = 130048
At 5us (16Mhz) = 130048
At 2us (48Mhz) = 1016

Anything faster than 2us, it is still at 48MHz at 1016 samples each channel (2032 total)

Rick

Edit:
Adding this:  My 1060 earlier was wrong and was probably trans-positioning the number in my mind.
Ten-sixty (1060) is incorrect.  Ten-sixteen (1016) is the right one.


Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 21, 2013, 09:46:24 am
At 50ms (1Mhz) it starts acquiring at full 1M samples (1,047,552 for each channel total 2x1047552)
At 20ms (1Mhz) it is at 523264 samples each Channel
At 10ms (1Mhz)= 523264
At 5ms (1Mhz)= 523264
At 1ms (1MHz) = 130048
At 100us (1Mhz) = 130048
At 20us (4Mhz) = 130048
At 10us (8Mhz) = 130048
At 5us (16Mhz) = 130048
At 2us (48Mhz) = 1016

Anything faster than 2us, it is still at 48MHz at 1016 samples each channel (2032 total).

Thanks a lot, Rick.  I really appreciate the info, and have made a note of it. 

Surprisingly, not only does Hantek not document this info, you can't even get it on request.  Though with 2M of sample RAM, I'd think they'd want to brag about it.  Apparently, they don't know.  :) 

EDIT:  Turns out I was wrong.  They do know, there's 2K of sample RAM (not 2M), and there's nothing to brag about.   :-[
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rpcope1 on November 25, 2013, 06:59:43 pm
  Hello everyone,

I've been watching this thread for a while, and I just wanted to say thanks for putting up all the cool information. I bought this scope a few months ago, thinking I'd do like what Aurora was talking about and mod it out. I've been writing a Python front-end for the API Hantek provides (I'm not huge on the provided scope software), and was thinking about doing the same in C++. I saw the OpenHantek project but it doesn't look like it supports the 6022BE scope. Is this something you all might be interested in? My big issue with the scope right now is the noise level. In reading this, I thought I read that a DC/DC converter was causing the roughly 10 mV noise seen in the channels? Do you all think it's possible to clean up the noise and get slightly better resolution as far as the signal goes, or is that asking too much from this scope? Maybe I just need to pony up and buy a dedicated spectrum analyzer (that's what I was hoping to accomplish). :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on November 25, 2013, 07:31:48 pm
rpcope1,

Thanks for you post. I would certainly be interested in any alternative software as I really do not get on with that supplied with the unit. The DC-DC converter was raised as a likely source of noise and the channels are not well screened. The 6022 would be a good basis for developing a cheap DSO for the masses  :)

I look forward to hearing how you get on with a better GUI for this well made little DSO. It has much potential and is a real pity that Hantek appear to have no interest in improving their software.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 25, 2013, 11:39:29 pm
Welcome to the Forum, rpcope.

I've been writing a Python front-end for the API Hantek provides...

Good luck with that.  From their (poor) SDK documentation, it's not even clear what some of the parameters are for, or how the functions actually behave.  I looked at it, and there were a few things I couldn't figure out.  It only took 3 emails to Hantek "Tech Support" :-DD over about a month, to net the response that "it's an inexpensive device", and "please read the SDK document" (which is what I was asking about in the 1st place).   |O

And yes, I'm stating publicly that Hantek tech support is a joke.

Quote
(I'm not huge on the provided scope software),

In that regard, you're now a member of the 100% 99.9% Club, since 100% 99.9% of owners/users find the software to be a piece of crap.   :--

[post-edit:  modified for fairness, since Rick says, "It's not that bad".]

Quote
My big issue with the scope right now is the noise level. In reading this, I thought I read that a DC/DC converter was causing the roughly 10 mV noise seen in the channels? Do you all think it's possible to clean up the noise...

Sure.  Though how much reduction you can achieve, for effort expended, remains to be seen.  You could be very successful, since no one AFAIK has taken the time to try.  You'd be exploring new territory.  Which is always fun.  :)  The first step would be to localize the source of the current internal noise (which would most easily be accomplished with a high sensitivity, low noise scope... though simple trial & error would work too!).

Quote
and get slightly better resolution as far as the signal goes, or is that asking too much from this scope?

I'm less certain on the resolution.  I vaguely recall someone reporting that both the 20 mS and 50 mV/div ranges were "fake" (zoomed), and the highest real sensitivity was only 100 mV/div(?).  I'm not sure you could increase that, and until you rectify the noise issue, there's no reason to try.

I'd encourage you to continue with your project.  Let us know what you come up with, and any questions you run into along the way.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on November 26, 2013, 01:05:52 am
I sure would not mind a better software.  Truth be told, the native software is not that bad.  It has some annoying things but it is usable.

It is a useful one now; it could be a great one with just a few improvement:  If we can reduce the noise, implement a better trigger (which would probably improve greatly by removing noise alone), fix a few minor annoying thing with the software, add AC coupling, this would be a great low cost scope.

If it just fix these two things with the software, I would love it:

(1) Missing a better way to move around saved data:

The worst (in my view) is to hunting for the wave form.  For example (my recent use), I captured a 100ns burst that I want to look at more closely.  At the setting I captured, when zoom all the way out, I have about 42.5ms of data.  To find that 100ns requires a lot of dragging.  Worst is, one mistake (by rolling over some active buttons) and you are reset back to the end (or start) of the capture depending on where your mouse is.  Now you have to drag and drag and drag to find that noise burst again.  Great fix will be an option for a zoomed-out display of the entire captured data you click on the part you want to center/zoom.

(2) While it captures 2M data points, it is hardly useful:

The other annoying thing is related to the above but this one is probably in the firmware and not the PC side: what part of the wave it captures (after trigger) and it's relationship to the memory buffer is not controllable.  Say if you are capturing at 1016 points.  It is pure luck what the buffer pointer is at when you triggered.  It could be at (say) point 6 and you capture 1010 points after trigger.  But it could as easily be at point 1010 and you captured 6 points after trigger so you missed your entire waveform except the start.

I tried to capture something simple like a capacitor discharge.  I kept getting just a small portion of it when the whole discharge would have fit into merely a 1/2 to 1/3 the captured memory space.

A great solution would be if it treats the buffer as a ring buffer with indirect access: wrap the buffer array index back to zero so the trigger point is always at the center or a settable number.  So, you can set X to say 40, you get 40 points before trigger and 1016-40=616 points after trigger.  Simple arithmetic: display datapoint[Y] is really buffer[remainder((Y+x)/1016)].

Without this fix, you have to be really luck to capture the entire useful part of the wave form.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 26, 2013, 03:14:09 am
I sure would not mind a better software.  Truth be told, the native software is not that bad.  It has some annoying things but it is usable.

You're a more patient man than I, Gunga Din.  :)

Quote
A great solution would be if it treats the buffer as a ring buffer with indirect access: wrap the buffer array index back to zero so the trigger point is always at the center or a settable number.

That one may be a hardware constraint, not solvable at the SDK level.  :(  It's unclear from their docos what control you have over that, if any.  But you spec a few parameters, then tell it to go off and capture.  Wait for it to finish, then pull the data out of the buffer you gave it a link to.

If you want me to pull up my notes sometime, and we can discuss it here, I doubt anyone else would mind.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: tehmeme on November 26, 2013, 03:18:03 am
  Hello everyone,

I've been watching this thread for a while, and I just wanted to say thanks for putting up all the cool information. I bought this scope a few months ago, thinking I'd do like what Aurora was talking about and mod it out. I've been writing a Python front-end for the API Hantek provides (I'm not huge on the provided scope software), and was thinking about doing the same in C++. I saw the OpenHantek project but it doesn't look like it supports the 6022BE scope. Is this something you all might be interested in?

why not implement support for the 6022BE in the already existing openhantek instead of creating something from scratch and all the issues involved with that?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 26, 2013, 05:01:40 am
why not implement support for the 6022BE in the already existing openhantek instead of creating something from scratch and all the issues involved with that?

Does OpenHantek run on Windows?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on November 26, 2013, 05:23:20 am
I sure would not mind a better software.  Truth be told, the native software is not that bad.  It has some annoying things but it is usable.

You're a more patient man than I, Gunga Din.  :)


Nope, I just had no choice.  This is the only scope I have, so I accept the way it works and work around it.  I did help me found the problem I was looking for.

A great solution would be if it treats the buffer as a ring buffer with indirect access: wrap the buffer array index back to zero so the trigger point is always at the center or a settable number.

That one may be a hardware constraint, not solvable at the SDK level.  :(  It's unclear from their docos what control you have over that, if any.  But you spec a few parameters, then tell it to go off and capture.  Wait for it to finish, then pull the data out of the buffer you gave it a link to.

If you want me to pull up my notes sometime, and we can discuss it here, I doubt anyone else would mind.


You don't need to dig up your notes in the SDK.  I too think it is not at the SDK level.

You can't really link the data post capture.  To work with the data, you have to save it.  No one can click fast enough to do two consecutive trigger+save when working with even millisecond waves.  Even USB transfer with the SDK would not be able to handle 48MHz data transfer.  So if this is done, it has to be done inside the Hantek box itself.

I think that may be able to implement at the firmware level instead of hardware.  At capture of mere 48Mhz, there should be enough time to do an extra add, divide to calculate the memory address then access the memory for writing.

That one "little" change would make the captured memory so much more flexible.  As it is, capturing say a 100us burst by capturing 200us means you only have 50/50 chance of seeing the whole wave form.  So, to have a one in 10 chance of seeing the whole thing, I have to capture 10x the duration --- and then all that scrolling extra scrolling to find the darn burst...  That is damn annoying to use.  One really has to really really want to see it to go through that.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: uboot on November 27, 2013, 06:14:46 pm
Ok here are the pictures.

Nice PCB. It is laid out in a logical manner.

The parts count is relatively low and a CY7C68013 development board costs around $10 from China. But I still don't think I would bother to build one of these using such a board as the additional parts, case, scope probes and my time would make it far more expensive than GBP49. In those terms it is very good value for money. Next test will be to see how the unit performs with the infamous Hantek software package !

Looking at the PCB pictures I wonder if the 6022BE can be upgraded with an external trigger like 6052BE and 6082BE have...

http://hantek.com/en/ProductDetail_2_31.html (http://hantek.com/en/ProductDetail_2_31.html)

Might require new firmware, I'm afraid...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 27, 2013, 11:26:31 pm
Looking at the PCB pictures I wonder if the 6022BE can be upgraded with an external trigger like 6052BE and 6082BE have...

http://hantek.com/en/ProductDetail_2_31.html (http://hantek.com/en/ProductDetail_2_31.html)

Might require new firmware, I'm afraid...

The hardware is there and the traces run into the pin one side of the USB Micro, all you need is a BNC, C62 and R13 and then it's all firmware from then on.

You would have to extract the firmware from the other model drivers and do some reverse engineering on the OP code to figure out what part is responsible and find a way to hack it into the 6022BE driver (which contains the firmware).

After all that, you still need to modify the software and the software used by the other models is vastly different from the software used on the 6022BE, just look at the SDK headers.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 27, 2013, 11:30:20 pm
I just acquired one of these DSOs and I am going to be modifying it a bit, adding extra bypass capacitors, shielding the DC-DC and adding screening cans to both front ends and I will be posting my results here.

Also, I have been tinkering around with the crappy SDK provided by Hantek and I managed to get some framework code written in C++ Builder and I even managed to get some undocumented functions from both DLLs (HTDisplayDll and HTMarch) working, though I had to use IDA Pro to figure out what the function arguments were.

Anyway, will be back later with more.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 28, 2013, 01:07:29 am
I just acquired one of these DSOs and I am going to be modifying it a bit, adding extra bypass capacitors, shielding the DC-DC and adding screening cans to both front ends and I will be posting my results here.

Sounds good.  We'll be looking forward to it.

Quote
Also, I have been tinkering around with the crappy SDK provided by Hantek and I managed to get some framework code written in C++ Builder and I even managed to get some undocumented functions from both DLLs (HTDisplayDll and HTMarch) working, though I had to use IDA Pro to figure out what the function arguments were.

That's interesting.  I did have some documentation on the args to HTMarch, but still wasn't clear what they were all supposed to do.  I made the mistake of asking Hantek "tech support", instead of just doing some black-box testing.  Never did get an answer to any question, and never got back to it again.

If you feel like sharing your findings on the args, that would be helpful.  Or I could just PM you with the info I had on some, and the couple I couldn't figure out.  I'm sure that would be much more productive than the month I spent exchanging emails with Hantek for nothing.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 28, 2013, 03:05:08 am
Here are some of the DisplayDll undocumented functions:

Code: [Select]
//Unducumented Functions
DLL_API int WINAPI HTDrawAcquireMode(HDC hdc, int x, int y, COLORREF h, __int16);
DLL_API int WINAPI HTDrawBottomPentagon(HDC hdc, int, int, COLORREF color);
DLL_API int WINAPI HTDrawCouplingImage(HDC hdc, int, int, COLORREF color, __int16);
DLL_API int WINAPI HTDrawCursorLine(HDC hdc, int, int y, int x, int, int, int, HGDIOBJ ho, int, int);
DLL_API int WINAPI HTDrawCursorTraceLine(HDC h, int x, int, int, int, int, int);
DLL_API int WINAPI HTDrawDefineText(HDC hdc, int, LPCWSTR pszFaceName, int mode, LPCWSTR lpString, int c, int x, int y);
DLL_API int WINAPI HTDrawEdgeSlope(HDC h, int, int, COLORREF hbr, __int16);
DLL_API int WINAPI HTDrawGeneratorRect(HDC hdc, int, int, int, int);
DLL_API int WINAPI HTDrawGridARB(HDC hdc, int, int, int, int, int, int, int, __int16);
DLL_API int WINAPI HTDrawGridBorder(HDC hdc, int, int, int, int);
DLL_API int WINAPI HTDrawGridLA(HDC hdc, int, int, int, int, int, int, int, int);
DLL_API int WINAPI HTDrawGridNew(HDC hdc, int, int, int, int, int, int, int, __int16);
DLL_API int WINAPI HTDrawGroupGridLA(HDC h, int, int, int, int, int, int, int, int);
DLL_API int WINAPI HTDrawKnob(HDC h, int, COLORREF color, int);
DLL_API int WINAPI HTDrawLABusSignal(HDC hdc, int, int Memory, int, int, int x, double, int, __int16, __int16);
DLL_API int WINAPI HTDrawLASquareSignal(HDC h, int, COLORREF color, int, int, int, double, int);
DLL_API int WINAPI HTDrawLATrigLine(HDC hdc, HGDIOBJ h, int, int, HGDIOBJ ho, COLORREF color);
DLL_API int WINAPI HTDrawLeftPentagon(HDC hdc, int, int, COLORREF color);
DLL_API int WINAPI HTDrawLevel(HDC hdc, int, int, COLORREF h, int y);
DLL_API int WINAPI HTDrawMeasLine(HDC h, int, int, int, int, int x, int y, HBRUSH ho);
DLL_API int WINAPI HTDrawPrintGrid(HDC hdc, HGDIOBJ h, HGDIOBJ ho, int, int, int, int, int, __int16);
DLL_API int WINAPI HTDrawPrintGridBorder(HDC hdc, HGDIOBJ ho, int, int, int, HGDIOBJ h);
DLL_API int WINAPI HTDrawPulseWidth(HDC hdc, int, int, COLORREF h, __int16);
DLL_API int WINAPI HTDrawRightPentagon(HDC hdc, int, int, COLORREF color);
DLL_API int WINAPI HTDrawSquareWaveInYT(HDC hdc, int, int, int, int, COLORREF ho, HGDIOBJ h, int, int, int, int, int, double, double, int, int);
DLL_API int WINAPI HTDrawTopPentagon(HDC hdc, int, int, COLORREF color);
DLL_API int WINAPI HTDrawWaveInXY(HDC hdc, void *Memory, int, int, int, int, int, int, int, int, COLORREF color);
DLL_API int WINAPI HTDrawWaveInXYNew(HDC hdc, void *Memory, int, int, int, int, int, int, int, int, COLORREF color);
DLL_API int WINAPI HTDrawWaveInYTNew(HDC hdc, int, int, int, int, COLORREF color, int, int, int, int, __int64, int, double, double, int, int);
DLL_API int WINAPI UserRound(double);

and some for HTMarch.dll that I have not got arguments for yet:
Code: [Select]
HTMARCH_API short WINAPI _dsoCloseFlashLight();
HTMARCH_API DWORD WINAPI _dsoGetPackageSize();
HTMARCH_API short WINAPI _dsoOpenFlashLight();
HTMARCH_API short WINAPI _dsoReadPackageData();
HTMARCH_API short WINAPI dsoSetSquareFreq();
HTMARCH_API short WINAPI _dsoStartDeviceCollect();

The rest of the documented functions are in the PDFs in the "Manual" directory that comes with the "SDK", with some chinglish but decipherable.

The comments in there mostly told me what arguments for the documented functions are and the integer range for some as well as the different options and modes. I turned most of them into enums for easier reading in the code and made a wrapper class for the DLL functions and it's still boiler plate at this point but when I get some more time after the holidays I'll try and get something more functional and put the code up here for anyone who wants to tinker with it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 28, 2013, 08:41:24 am
Thanks for sharing, Richard.  And oh, BTW, Welcome to the forum.

I'll dig up my notes on the SDK and post them as well, after I get some sleep, some food, and the turkey-induced coma eases up.   ;D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: uboot on November 28, 2013, 08:21:13 pm
According to Openhantek, the DSO2090, 2150 and 2250 had their firmware reside within the USB drivers:

http://www.openhantek.org/w/p/installation/#10 (http://www.openhantek.org/w/p/installation/#10)

I read this like "firmware is downloaded to the device by the driver during initialization".

If that's true and provided that it hasn't changed for the 60x2BE series, there might be chances for easy firmware hacks...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 28, 2013, 09:36:08 pm
I have reverse engineered the Front End if anyone is interested:

The A7 device is just a fast switching rectifier, it breaks down at 100V and it's being used to clamp the signal to -5V and +5V.

Also take note that the instead of your usual 1M ohm resistor and trimmer capacitor in parallel connected from input signal to ground we have the input signal going through a 909K resistor with the trimmer capacitor in parallel with it, then shunted to ground through a 100K resistor and an SMD capacitor in parallel. To the input, it looks like a 1M resistor to ground, but the signal is being tapped between 909K and 100K, then going to the first Op Amp. I'm not sure a 5V input signal in 1x mode is going to give a 5V signal at the node between the 909K and 100K, but more like 500mv. This would mean the probe in 1x mode is going to be safe all the way up to 50V and 500V in 10x.

Also, the outside of my unit shows a label between the BNC connecors that says "35vpk max" which I am not sure if they mean for 1x or 10x?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 28, 2013, 10:44:00 pm
According to Openhantek, the DSO2090, 2150 and 2250 had their firmware reside within the USB drivers:

http://www.openhantek.org/w/p/installation/#10 (http://www.openhantek.org/w/p/installation/#10)

I read this like "firmware is downloaded to the device by the driver during initialization".

If that's true and provided that it hasn't changed for the 60x2BE series, there might be chances for easy firmware hacks...

I'm pretty sure all the simple CY7C68013A models are doing it this way, they don't have any on-board flash and the I2C doesn't have firmware in it just model information for USB device detection.

So the .sys driver has the firmware image embedded inside it, and the folks at openhantek.org have a tool to extract it. When the device is plugged in, the driver loads the firmware into the CY7C68013A's 16KB internal memory, and the 4K FIFO is used to store the ADC output.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 29, 2013, 03:03:13 am
I have reverse engineered the Front End if anyone is interested:

Thanks, Richard.

Quote
I'm not sure a 5V input signal in 1x mode is going to give a 5V signal at the node between the 909K and 100K, but more like 500mv.

500 mV is correct.

Quote
This would mean the probe in 1x mode is going to be safe all the way up to 50V and 500V in 10x.

Yes.

Quote
Also, the outside of my unit shows a label between the BNC connectors that says "35vpk max" which I am not sure if they mean for 1x or 10x?

They mean for 1x.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 29, 2013, 03:11:37 am
I'm pretty sure all the simple CY7C68013A models are doing it this way, they don't have any on-board flash and the I2C doesn't have firmware in it just model information for USB device detection.

Correct.

Quote
So the .sys driver has the firmware image embedded inside it, and the folks at openhantek.org have a tool to extract it. When the device is plugged in, the driver loads the firmware into the CY7C68013A's 16KB internal memory, and the 4K FIFO is used to store the ADC output.

Almost.  The 4K FIFO is used to buffer the USB data transfers.  The ADC output should be fed to a 16Mbit chip (2 channels, with 1 MByte each), though I didn't see one on the board.  If they were funneling the data directly from the ADC through the FIFO to USB, it wouldn't be able to keep up with the 48 MHz sample rate of the device.  And it's not limited to 4K of samples, so...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 29, 2013, 05:32:53 am
I'm pretty sure all the simple CY7C68013A models are doing it this way, they don't have any on-board flash and the I2C doesn't have firmware in it just model information for USB device detection.

Correct.

Quote
So the .sys driver has the firmware image embedded inside it, and the folks at openhantek.org have a tool to extract it. When the device is plugged in, the driver loads the firmware into the CY7C68013A's 16KB internal memory, and the 4K FIFO is used to store the ADC output.

Almost.  The 4K FIFO is used to buffer the USB data transfers.  The ADC output should be fed to a 16Mbit chip (2 channels, with 1 MByte each), though I didn't see one on the board.  If they were funneling the data directly from the ADC through the FIFO to USB, it wouldn't be able to keep up with the 48 MHz sample rate of the device.  And it's not limited to 4K of samples, so...

The ADC output traces go directly to the CY7C68013A's Multiplexed input pins (specifically "bidirectional FIFO/GPIF data bus") which can switch between GPIF and FIFO. There is no 1MByte of ram anywhere on the board, or in any of the ICs. The FIFO has a 96 mega byte per second burst rate, so it's highly unlikely they are using the GPIF which would have to go through the address bus just to get to the FIFO.

My guess is they are dumping the 8-bit data from the ADC in real time into the FIFO, and then through firmware they are periodically sampling it via USB possibly using the computer's ram to store the raw data.

Both the CY7C68013A and the ADC can clock at 48Mhz so there is no problem with the full data rate from the ADC getting to the FIFO, and the FIFO doesn't need 1MB of RAM to hold a real time value. If they use 2K of FIFO per channel, they can store 2000 samples of data in FIFO for each channel. All the firmware inside the CY7C68013A has to do is buffer 2000 samples continuously, starting over and overwriting when it reaches 2000 samples.

Since the FIFO is connected directly to the USB Engine (circumventing the Address Bus), this means the PC has high speed access to the FIFO buffer and all the PC has to do is wait for the FIFO to fill up, then read the entire FIFO buffer to PC RAM, and either display it immediately or wait for the FIFO to fill up again, then read it and store in PC RAM until desired sample length is reached.

Since the PC doesn't read the FIFO until it's filled, that means the USB transfer is effectively 4KBs every 24Khz (48Mhz/2000 samples equals 24Khz).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 29, 2013, 06:31:54 am
Thanks for the analysis, Richard.  I don't necessarily disagree with any of it, but I'd like to discuss a few points a bit more.

The ADC  output traces go directly to the CY7C68013A's Multiplexed input pins (specifically "bidirectional FIFO/GPIF data bus") which can switch between GPIF and FIFO. There is no 1MByte of ram anywhere on the board, or in any of the ICs.

I never saw any either, but assumed it must be there somewhere.  :D  Reason being the Hantek claim that unlike the other models in the 6000-series, with only 16K of buffer RAM, the 6022 boasted 1M-samples per channel.  Thus I assumed it must have 1MB of RAM per channel, on the board.  (That's actually one of the reasons I bought that particular model, quite some time ago.)  I never opened it up, or even looked that closely at the PCB shots here that Aurora was kind enough to provide.

Quote
The FIFO has a 96 mega byte per second burst rate, so it's highly unlikely they are using the GPIF which would have to go through the address bus just to get to the FIFO.

My guess is they are dumping the 8-bit data from the ADC in real time into the FIFO, and then through firmware they are periodically sampling it via USB possibly using the computer's ram to store the raw data.

That would be the only plausible explanation.  My concern is the ability to continuously maintain a USB transfer, to transfer 500 FIFO buffers worth of data, without any breaks.  More on that below.

Quote
Both the CY7C68013A and the ADC can clock at 48Mhz so there is no problem with the full data rate from the ADC getting to the FIFO, and the FIFO doesn't need 1MB of RAM to hold a real time value.

Yes, that part is pretty straightforward.

Quote
If they use 2K of FIFO per channel, they can store 2000 samples of data in FIFO for each channel. All the firmware inside the CY7C68013A has to do is buffer 2000 samples continuously, starting over and overwriting when it reaches 2000 samples.

Well, there needs to be some bit of synchronization, between the Producer side you're describing, and the Consumer side to USB, so that neither outruns the other.  But yes.  Normally this is done with double-buffering, but chase-mode would work as well, if you have dual-ported memory with DMA.

Quote
Since the FIFO is connected directly to the USB Engine (circumventing the Address Bus), this means the PC has high speed access to the FIFO buffer...

I'm with you up to here.

Quote
...and all the PC has to do is wait for the FIFO to fill up, then read the entire FIFO buffer to PC RAM,

Too late!  If it waits until the FIFO is full, it can't possibly read it out without an overrun condition, and lose the continuous data stream.

Quote
and either display it immediately or wait for the FIFO to fill up again, then read it and store in PC RAM until desired sample length is reached.

The thing is, the way you're describing it makes it sound like the PC can just grab a 2,000 byte chunk of data over USB instantaneously.  And it can't.  Even running USB in synch-transfer mode, it takes time.

Quote
Since the PC doesn't read the FIFO until it's filled, that means it's effectively sampling it at 48Mhz/2000 samples which equals 24Khz.

Well, OK, though I'm not sure describing it as "sampling" at 24 kHz is really meaningful.  The USB data still gets serialized, and can only be clocked out at something less than 60 MB/sec.  Depending on the system, usually much less than 60.  Most rarely attempt more than 24 MB/sec, and some even fail at that.  (See all the inexpensive USB-logic analyzers.)  I'm wondering just how successful the continuous 48 MB/sec you've described would actually be?

Or are you suggesting that Hantek isn't actually performing a 1M-sample acquisition at 48 MHz, but rather just grabbing discontiguous chunks of 2K of data?  I agree, that would be very easy to do.  But in that case, Hantek would be dangerously close to fraud in their claims, and most certainly deceptive.  However, that would help understand their reluctance to explain any of those issues to me when I asked.

I just don't see how it would be practical to sustain a 48 MB/sec USB transfer rate, even for the 21 msec required to acquire 1M samples of data.  Sure, they can sample that, but they can't get it to the PC.  That's why I assumed they must have a large local buffer.  But maybe I'm missing something.

NB:  And, as it turned out, I was.  See below.

[Thanks for the interesting discussion!]
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: uboot on November 29, 2013, 06:36:43 am
Here is a tear down / analysis of the 2090 series: http://fabiobaltieri.com/2013/07/10/inside-a-hantek-dso-2090-usb-oscilloscope/ (http://fabiobaltieri.com/2013/07/10/inside-a-hantek-dso-2090-usb-oscilloscope/)

There's SRAM and dedicated analog trigger circuitry.


Does the 60x2BE do triggering in software?



EDIT: just saw your last post - at 48M the 6022BE is said to have only 2k sample buffer and in an earlier post it is stated that there's trouble with proper signal readout: https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg258586/#msg258586 (https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg258586/#msg258586)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 29, 2013, 06:51:48 am
Does the 60x2BE do triggering in software?

From numerous comments made here by owners, the 6022BE seems to lack any ability to select a trigger point at a specific spot in an acquisition.  E.g., Rick has described how a capture has the trigger point occurring essentially randomly within the sample, making it very difficult to acquire the desired part of the waveform.  So you might want to look at 90% post-trigger data, but wind up with all of your data to view being pre-trigger.  I.e., a crap shoot.

So software triggering sounds more than plausible.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 29, 2013, 07:08:30 am
EDIT: just saw your last post - at 48M the 6022BE is said to have only 2k sample buffer and in an earlier post it is stated that there's trouble with proper signal readout: https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg258586/#msg258586 (https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg258586/#msg258586)
Yes, Rick documented how at high speed (48 MHz), the module was capturing only 1,016 samples of data.  It wasn't until you dropped back to 16 MSa/sec that you got anything bigger (jumped to 128k), and you couldn't get 1M at all, until you dropped the sampling to 1 MSa/sec or less.  These were his findings:

Code: [Select]
At 50ms (1Mhz) it starts acquiring at full 1M samples (1,047,552 for each channel total 2x1047552)

At 20ms (1Mhz) it is at 523264 samples each Channel
At 10ms (1Mhz)= 523264
At 5ms (1Mhz)= 523264

At 1ms (1MHz) = 130048
At 100us (1Mhz) = 130048
At 20us (4Mhz) = 130048
At 10us (8Mhz) = 130048
At 5us (16Mhz) = 130048

At 2us (48Mhz) = 1016
Anything faster than 2us, it is still at 48MHz at 1016 samples each channel (2032 total)

I think I'm finally starting to get a picture of what the 6022BE can really do.  And why.   :(  That explains what RichardK was trying to tell me, and I wasn't quite getting.  On one end, it can capture at 48 MSa/sec... for a very short period of time (~20 usec).  With 2-channels, of a whopping 1K each.  Because, like I noted, it can't get the data to the PC fast enough.  But if you sample slowly enough, the "sample buffer" is essentially infinite (PC RAM).  This certainly isn't the way they present the product capabilities.

To call this a 20 MHz bandwidth scope, with a 1M buffer is really deceptive.  Because with 1M sampling, the bandwidth is actually about 400 kHz.  (That's with the Hantek software.  It should be possible to do better than that.)  And the 1M buffer is actually in your PC.   :o
Title: AW: Hantek 6022BE 20MHz USB DSO
Post by: uboot on November 29, 2013, 08:50:39 am
You saved my day! I really was considering the 6022BE, but now I'm tending more to the older DSO2xxx series with smaller but onboard SRAM buffer and dedicated analog trigger...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on November 29, 2013, 11:11:20 am
Oh well, the 6022 appears to prove that you get exactly what you pay for...... in this case, not a great deal. Its a real pity though as the hardware looked so promising and build quality was good.

My 6022 just became a bookend....its more useful in that role  ;D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: R_G_B_ on November 29, 2013, 01:01:59 pm
Here is a tear down / analysis of the 2090 series: http://fabiobaltieri.com/2013/07/10/inside-a-hantek-dso-2090-usb-oscilloscope/ (http://fabiobaltieri.com/2013/07/10/inside-a-hantek-dso-2090-usb-oscilloscope/)


interesting to see that he managed to increase his sampling bandwidth by increasing the crystal frequency and maybe changing the ADC.

I tried this with an UT81B with no success so I am not sure how he managed to get more sampling bandwidth doing the above.
timing in the CPLD is more straight forward than an FPGA i guess.

so guess up sampling the clock frequency is just changing the CPLD clock factor for which everything in its path is changed by the  same amount is this correct?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 29, 2013, 03:39:34 pm
The thing is, the way you're describing it makes it sound like the PC can just grab a 2,000 byte chunk of data over USB instantaneously.  And it can't.  Even running USB in synch-transfer mode, it takes time.

It's probably set up so once the buffer is full it stops sampling, calls an interrupt to USB and once the PC grabs the data it starts sampling again.

This would explain the pseudo randomness of the device at times, because how long it has to wait to sample new data depends on how long it takes the USB and PC software to do it's part.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 29, 2013, 07:27:06 pm
If anyone was wondering what the unpopulated components opposite the front end were for, they are an alternate isolated supply for the front end. They are using an LTC3440 Buck regulator for the +5V and a classic 7660 Charge Pump for the -5V supply.

The question remains, why is it there if they already have an isolated DC-DC supply (specifically a Mornsun A0505S-2W)?

Take a quick look at the datasheet for the Mornsun DC-DC under Applications and you'll see why:

3) Regulated and low ripple noise is not required. Such as: digital circuits, low frequency analog circuits, and IGBT power device driving circuits.

Doesn't sound like something you'd use to power an Analog Oscilloscope Front End does it?

Clearly this was a cost cutting, not performance decision and this Mornsun DC-DC doesn't cut it in the higher end models, so I wouldn't be surprised if those boards had the DC-DC unpopulated and the Charge Pump + Buck Regulator populated instead.

In the datasheet for the DC-DC it specifies that the switching frequency is 75KHz but it doesn't specify what kind of input or output capacitors are used, or if there are inductors or even if the inside is shielded. 

Looking at the Applications notation, specifically the part where they say "Regulated and low ripple noise is not required" makes me think that if there is any input/output capacitors inside, it's bare minimum and highly unlikely that there is any sort of inductor in there other than the transformer, and forget about shielding.

I plan on adding copper foil shielding around the DC-DC package, ground strapping the ADC heatsink, and canning both Front Ends as well as adding extra SMD capacitors before and after the DC-DC, at the bypass capacitors near the ADC and USB Micro.

Later on I'll order some parts and populate the alternate DC-DC supply and remove the Mornsun DC-DC and see how it works.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 29, 2013, 10:08:16 pm
If anyone was wondering what the unpopulated components opposite the front end were for, they are an alternate isolated supply for the front end. They are using an LTC3440 Buck regulator for the +5V and a classic 7660 Charge Pump for the -5V supply.

Good catch.

Quote
I plan on adding copper foil shielding around the DC-DC package, ground strapping the ADC heatsink, and canning both Front Ends as well as adding extra SMD capacitors before and after the DC-DC, at the bypass capacitors near the ADC and USB Micro.

Later on I'll order some parts and populate the alternate DC-DC supply and remove the Mornsun DC-DC and see how it works.

Sounds like a good plan.  My guess is your initial efforts will be effective in reducing noise in small doses... perhaps cutting it in half.  The big win though will be eliminating the Mornsun, and you may be able to get noise down into the 1-2 mV range.  (Or maybe even a bit less, since this isn't a wideband device... it's not quite as susceptible as most scopes would be to high-freq noise.)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 29, 2013, 10:30:29 pm
It's probably set up so once the buffer is full it stops sampling, calls an interrupt to USB and once the PC grabs the data it starts sampling again.

This would explain the pseudo randomness of the device at times, because how long it has to wait to sample new data depends on how long it takes the USB and PC software to do it's part.

I agree about the pseudo-randomness.  Especially so if it just sends whatever is in the buffer as soon as it sees a trigger condition in that pass, when sampling at high speed.  I.e., it's constantly refilling the 1k buffer, and if the trigger fired any time during that chunk, it sends that block to the PC.  If not, it discards and keeps collecting.

[Note that the reports of randomness were at high speed, where the chunk size is small (very small).  At slower speeds, where it can collect larger data sets, it can afford to throw some of the head away to align things.]

However, I'm not sure about the first part.  Based on Rick Law's report, it can't be stopping and starting like that.  The crossover point seems to be at 5us/div (16Mhz), where it returns 127k of data per channel (instead of 1kB -8B).  If they were doing so in discontiguous chunks, then something as simple as a sine wave would be broken, and have 127 discontinuities as you scrolled though it.  I've never heard any reports of that.  (Rick?)

So that would have to be the data rate it can maintain continuously.  To do so, it must be double buffering, and sending one full block of data over USB, while acquiring the next block.  With no pauses to dump while not sampling.  If it's doing so on both channels, then it's pumping an aggregate 32 MB/sec over USB, which is very good performance.  If it's only managing one channel at that rate, then the 16 MB/sec that represents would be fairly normal and uneventful.  But I think Rick indicated both channels were active.
Title: Re: Hantek 6022BE 20MHz USB DSO (SDK examination)
Post by: Mark_O on November 30, 2013, 12:21:59 am
Hantek has an SDK manual for the Display DLL, and one for the acquisition DLL (HTMarch).  I concentrated on the later.

There are a set of support functions, which mostly make sense.  Other than the fact that some of them are worthless (redundant), since the data they set gets overridden whenever you actually do a Read call.  Here's my summary, and notes:

Code: [Select]
--Documented HTMARCH acquisition support functions  [Mark_O, Oct'13]:


// just checks to see if a device is present.  usually only Dev=0 is true.

HTMARCH_API short WIN_API dsoOpenDevice(unsigned short DeviceIndex);


// cals are 32B of 'proofreading' data.  short the inputs to Ground, then run dsoCalibrate and retrieve data.
// presumably, the cal sets (16B/channel) are dependent on timePerDiv and voltsPerDiv, which means that
// dsoCalibrate would need to be run in multiple passes (64 combos).  it also suggests that dsoSetCalLevel
// must be run every time either is changed.  what dsoGetCalLevel is good for is unknown.
// cal data also needs to be reloaded on every power-on, since theres no NVMEM.  [not really.  it says it
// sends the Cal data to the device, but it doesn't.  The SDK uses it to adjust the data before returning it.]

// [it looks like dsoSetCalLevel/dsoGetCalLevel are also worthless, for the same reasons as SetTime/Volts (below).]

HTMARCH_API short WIN_API  dsoCalibrate(unsigned short nDeviceIndex,int nTimeDIV,int nCH1VoltDIV,int nCH2VoltDIV,short* pCalLevel);
HTMARCH_API unsigned short dsoSetCalLevel(unsigned short DeviceIndex,short* level,short nLen);
HTMARCH_API unsigned short WIN_API dsoGetCalLevel(unsigned short DeviceIndex,short* level,short nLen);


// worthless functions, because there's no way to get any data after setting them, w/o running a dsoReadHardData, which overrides them!
// however, they do serve to document the needed index values.  (perhaps there are undocumented Read functions that were dropped.)

HTMARCH_API short WIN_API dsoSetVoltDIV(unsigned short DeviceIndex,int nCH,int nVoltDIV);
HTMARCH_API short WIN_API dsoSetTimeDIV(unsigned short DeviceIndex,int nTimeDIV);

// nVoltDIV (0-7):  n20mV, n50mV; n100mV, n200mV, n500mV; n1V, n2V, n5V

// nTimeDIV (0-27): n48Msa(0-10); n16MSa, n8MSa, n4MSa, n1MSa(14-24), n500KSa, n200Ksa, n100KSa

What is interesting there is the CalLevels, since they claim you send the data to the device, but I suspect you do NOT.  I doubt any correction is ever applied in the module, but rather in the SDK interface routine, which applies a cal correction after a Read and before it passes the data back.  I wonder how significant the args are for selecting channel sensitivity and sample rates, because in the worst case there are 8 sensitivities for each of Chan 1 and 2, and 8 sample rates, for a total of 512 combinations!  They appear to combine the CalLevels for both channels into one block, of 32B.

The actual data reading is more interesting, since it appears to wrap up everything into one call.  I guess you need to spawn this in a thread, so you can kill it later if the trigger condition never occurs, since there's no defined timeout.  And you'd hang, otherwise.

Code: [Select]
--ONE call to Config AND Acquire, AND Retrieve (and Correct) sample data.  [Mark_O, Oct'13]
--returns 0 for failure and non-0 for success.
 

HTMARCH_API short WIN_API dsoReadHardData(

unsigned short DeviceIndex,    // access more than one module

short* pCH1Data, // ptrs to 2 storage buffers
short* pCH2Data,
unsigned long nReadLen, // length of 'reading data'

short* pCalLevel, // ** ptr to calibrationLevel vector (see dsoSetCalLevel); input?

int nCH1VoltDIV, // sensitivity settings (0-7=20mV-5V)
int nCH2VoltDIV,

short nTrigSweep, // sweepMode: 0=Auto, 1=Normal ??, 2=single
short nTrigSrc, // 0=chan1, 1=chan2
short nTrigLevel, // level=0-255
short nSlope, // 0=rise, 1=fall

int nTimeDIV, // sampleRate (0-27=48MSa-100KSa/s, see dsoSetTime)
short nHTrigPos, // pre-TriggerData: 0-100% (control pre/post buffering)

unsigned long nDisLen, // ** length of DisplayData (huh?)
unsigned long * nTrigPoint, // index of returned triggerPoint

short nInsertMode // ** D-value Mode: 0=Step, 1=Line, 2=SinX/X (huh?)
);

There are a number of not well-defined things here, but two that stand out as puzzling.  The biggest is what a DisplayLength and D-value Mode are doing in the acquisition routine?  They're both relating to Display, which is (and should be) separate.  And the second is what the purpose of having a SweepMode of Normal is for? 

Auto means just trigger immediately (ignoring the sh!tload of trigger parameters), and Single waits for one trigger hit to capture and return a sample set.  But Normal implies there is a continuous sampling process occurring.  And since there's no callback function or any other mechanism to allow that, I wonder if it's just that Normal=Single here, or if they partition the one block of data that's allocated into slices, and fill it with multiple samples in Normal mode?  (I'd guess not, since that's far too sophisticated for them.  So Single probably means nothing at all.)

I'd be interested in thoughts anyone may have as to the purpose of the Display params in the dsoRead, though.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 30, 2013, 01:50:19 am
I know the DisplayLength has a meaning in the DrawWave function, it's just used to clip the data and only display a portion of it, what it's being used for in GetRaw I'm not sure... perhaps it's clipping the data also?

D-Value mode is how the data is interpolated when you are at 2us or lower, the options are as follows:
1. Step - Interpolate in right angle steps
2. Line - Interpolate in obtuse angles
3. SinX - Interpolate in sine

The reason the Get Raw data function asks for these arguments is because it's doing the interpolation.

As for the Calibration functions, the firmware might be storing the cal data in the I2C IC.

I have been tinkering with the code today and I got the grid displaying and both channels, but so far I have not added any manual controls, just displaying hard coded settings.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 30, 2013, 02:18:34 am
Thanks for the feedback, Richard.

I know the DisplayLength has a meaning in the DrawWave function, it's just used to clip the data and only display a portion of it, what it's being used for in GetRaw I'm not sure... perhaps it's clipping the data also?

Maybe.  Not sure why it would though.

Quote
D-Value mode is how the data is interpolated when you are at 2us or lower, the options are as follows:
1. Step - Interpolate in right angle steps
2. Line - Interpolate in obtuse angles
3. SinX - Interpolate in sine

Right.  That part I know.  :)

NB:  Whoops!  I need to slown down & read more carefully.  I missed your "at 2 us or lower".  Even then, it shouldn't have to interpolate anything until Display time though.

Quote
The reason the Get Raw data function asks for these arguments is because it's doing the interpolation.

Huh?  What interpolation?  I ask it to collect N samples at a certain rate.  It does so and returns them to me.  What is here for it to interpolate?  It would only do so if it was sampling fewer points than the # I requested.  And needed to create the missing intermediate values.  Are you suggesting that's what it's doing?  [I suppose it could be.  :(   :-//]

[BTW, I expect if I ask a device to sample at, say, 8M Sa/s, that it actually does so.  Not sample at some lower rate, then generate fake points to make it look like it was running properly.  If that's what it's actually doing, my interest in it just dropped to 0.  The speed is already disappointingly low, but still quite usable for certain things.  If it's even slower than that, it's worthless to me.  I have no use for a device that provides me with 8M of "data", with 7M of it filler, and 1M actual samples.   >:(  I hope this is not what is happening.]

Quote
As for the Calibration functions, the firmware might be storing the cal data in the I2C IC.

Well, it could store the data anywhere it wanted to.  But I don't see what value that would have?  It has to be used in some way to adjust the raw data values provided by the ADC, and I don't see it having either the time or the horsepower to do so on the fly.  That should be being done on the PC.

Quote
I have been tinkering with the code today and I got the grid displaying and both channels, but so far I have not added any manual controls, just displaying hard coded settings.

Good to hear.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 30, 2013, 02:25:56 am
Quote
Huh?  What interpolation?  I ask it to collect N samples at a certain rate.  It does so and returns them to me.  What is here for it to interpolate?  It would only do so if it was sampling fewer points than the # I requested.  And needed to create the missing intermediate values.  Are you suggesting that's what it's doing?  [It could be.  :(   :-//]

I don't think the device supports sampling at lower than 2us, so they are hacking support by interpolating. Why would they do this? Maybe there is too much noise? Not sure. The interpolation doesn't take effect at timebases above 2us, and if you look at the stock software the interpolation buttons are disabled above 2us presumably because they don't do anything above 2us.

Quote
Well, it could store the data anywhere it wanted to.  But I don't see what value that would have?  It has to be used in some way to adjust the raw data values provided by the ADC, and I don't see it having either the time or the horsepower to do so.  That should be being done on the PC.

It's a USB scope, so you might not be using the same PC to utilize it, thus storing the cal data in the I2C would be convenient, and I don't think the firmware is touching the cal data, it's just stored there and the calibration offsetting happens in the PC software, thus the need for the GetCalLevel function.

If they store it on the PC, you have to recalibrate every time you use a different PC,
If they store it in USB Micro's 16KB RAM you have to recalibrate every time you plug it in,
If they store it in the I2C you only have to calibrate it when it needs it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 30, 2013, 02:54:16 am
Thanks for the clarifications.

I don't think the device supports sampling at lower than 2us, so they are hacking support by interpolating.

You are correct.  Once it hits 2 uS (that's perDIV), it's sampling at its max 48 MHz, and it goes no faster than that.  At that rate, they're acquiring 96 samples/div, and as they drop below that (or zoom in), they need a method to "connect the dots".

Quote
Why would they do this? Maybe there is too much noise? Not sure.

Could be.  In my mind, it just seems like Capture and Display should be independent.  If this only kicks in at 48 MHz, I'm less concerned though.

Quote
The interpolation doesn't take effect at timebases above 2us, and if you look at the stock software the interpolation buttons are disabled above 2us.

That's a relief!   :phew:  :)

Quote
Quote
Well, it could store the data anywhere it wanted to.  But I don't see what value that would have?  It has to be used in some way to adjust the raw data values provided by the ADC, and I don't see it having either the time or the horsepower to do so.  That should be being done on the PC.

It's a USB scope, so you might not be using the same PC to utilize it, thus storing the cal data in the I2C would be convenient.

Oh, you mean, as a temporary cache?  Thus needing the dsoGetCal, to pull it into the SDK.  Yeah, could be.  That would save time and avoid needing a recal just because you switched from your desktop to a laptop PC.  If they have enough room for all of it, in EEPROM. 

(I'm still not sure how many sets of 32B they need to characterize the entire range for the scope... but the Calibrate function does have sampleRate, and channelSensitivity (for _2_ channels) as input args.  I was assuming that a Cal process would not be a single call to that function, but ramp through all the possibilities.  But even though they complicate it by wedding Chan1&2 in a Cal set, that doesn't mean they need to redundantly store all those combos.  You'd just need one 16B Cal per channel for each Sensitivity & Sample rate pair.  So 64 per channel = 2 KB total.  Doable.)

That would also explain why they have the "useless" Set functions for sampleRate and chanSensitivity.  These values get overridden in the dsoRead, but you can't access a specific set of CalLevels w/o first setting the TB and mvPerDIV.  So you'd use the two Set routines to cycle through, and perform a GetCalLevels for each.  Then you'd be able to provide them to the SDK on a dsoRead, and not have to do a full Cal to regen the values between PC.  Makes sense.   You're knocking down some of the unknowns.  :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on November 30, 2013, 03:02:13 am
It's a USB scope, so you might not be using the same PC to utilize it, thus storing the cal data in the I2C would be convenient, and I don't think the firmware is touching the cal data, it's just stored there and the calibration offsetting happens in the PC software, thus the need for the GetCalLevel function.

If they store it on the PC, you have to recalibrate every time you use a different PC,
If they store it in USB Micro's 16KB RAM you have to recalibrate every time you plug it in,
If they store it in the I2C you only have to calibrate it when it needs it.

Yep.  100% agreement.   :-+  You've explained why they needed the 4 "redundant" functions.  Thanks. 

(Well, they're not storing it IN the I2C.  That's a comm channel.  But yeah, the EE accessed thru the I2C.  Yes, I know I'm being pedantic.  :))
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on November 30, 2013, 03:08:02 am
(Well, they're not storing it IN the I2C.  That's a comm channel.  But yeah, the EE accessed thru the I2C.  Yes, I know I'm being pedantic.  :))

Bad habit of mine, sort of like calling a hard drive a SATA.
Title: Re: AW: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on November 30, 2013, 04:54:52 am
You saved my day! I really was considering the 6022BE, but now I'm tending more to the older DSO2xxx series with smaller but onboard SRAM buffer and dedicated analog trigger...

uboot,

Look before you jump.

This is from memory, so I could be remembering the brand wrong.

From year old memory when I was looking, I found many of the other scope in the low end (100MHz and below, dual channel) including Rigol, Atten, etc do the same thing - smaller sample at higher speed and only full memory at slower speed.  I think Owon was the exception.

(Please do correct me if I have the brand/facts wrong)  Either way, do research before buy and don't assume.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: uboot on November 30, 2013, 10:46:22 am
It's not sample depth that distracts me, it is triggering. I want reliable triggering with pre-trigger aquisition. Want to use the DSO for slow digital (CMOS) circuits. 1MHz clock max, but I won't regret having bandwidth / sampling speed for up to 20MHz clock.

Meanwhile, I discovered the new Owon VDS series - looks superior to Hantek 2xxx / better bang for the buck. 10M sample depth for the full speed range. The only thing I'm missing right now is in-depth reviews...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 03, 2013, 11:03:37 pm
Hello again everyone, got some more details to provide about the SDK...

A question was asked earlier about the ReadHardData and DrawWave functions, specifically the "nReadLen" and "nDisLen" for the ReadHardData function and the "nSrcDataLen" and "nDisDataLen" for the DrawWave functions.

When I was implementing GUI controls for Vertical and Horizontal I noticed that my application wasn't behaving exactly the same way as the stock 6022BE software, more specifically the Horizontal scaling was way off.

I had a hunch as to what was causing it, but no idea how to solve it... It turns out the "Read Length" and "Display Length" properties were the culprit as I had used the default values provided in the "SDK" and "Manual" PDF file.

The problem is, these values are highly dependent on what timebase you are in, and there is no documentation on what values to use on which timebases, and there is only one example in the SDK and PDF of it's use, but not enough to figure out what the rest should be.

The first problem I had to tackle was what "Read Length" values to use for each of the 39 different timebases in the original software, and an earlier post in this thread got me close, but no cigar.

I ended up having to write a redirection dll for the HTDisplayDll.dll which is simply a DLL to use between the original software and the real HTDisplayDll.dll file so I can snoop around and see what is being passed into the DLL function calls. This process was VERY tedious and time consuming but I got it working and here is what I came up with.

Below is a snippet of code, an enum I use in my software to describe the 39 different timebases used by the two DLLs. The index values for each enum is in the same order as the Timebase drop-down list in the original software and not surprisingly the same values used by the DLLs. Each enum is grouped by "Read Length" (see samples comments) and followed by a comment which shows the "Display Length", "Horizontal Scaling" and "Vertical Scaling" "Zoom" arguments used in the DrawWave function, and it turned out they were all 1:1 ratio but never the less good to know.

Code: [Select]
//Time Division
enum THantekTimeDivision
{
 //1016 samples
 HTTimeDiv48MS_1NS=0, //960, 1, 1
 HTTimeDiv48MS_2NS=1, //960, 1, 1
 HTTimeDiv48MS_5NS=2, //960, 1, 1
 HTTimeDiv48MS_10NS=3, //960, 1, 1
 HTTimeDiv48MS_20NS=4, //960, 1, 1
 HTTimeDiv48MS_50NS=5, //960, 1, 1
 HTTimeDiv48MS_100NS=6, //960, 1, 1
 HTTimeDiv48MS_200NS=7, //960, 1, 1
 HTTimeDiv48MS_500NS=8, //960, 1, 1
 HTTimeDiv48MS_1US=9, //960, 1, 1
 HTTimeDiv48MS_2US=10, //960, 1, 1

 //130048 samples
 HTTimeDiv16MS_5US=11, //800, 1, 1
 HTTimeDiv8MS_10US=12, //800, 1, 1
 HTTimeDiv4MS_20US=13, //800. 1, 1
 HTTimeDiv1MS_50US=14, //500, 1, 1
 HTTimeDiv1MS_100US=15, //1000, 1, 1
 HTTimeDiv1MS_200US=16, //2000, 1, 1
 HTTimeDiv1MS_500US=17, //5000, 1, 1
 HTTimeDiv1MS_1MS=18, //10000, 1, 1
 HTTimeDiv1MS_2MS=19, //20000, 1, 1

 //523264 samples
 HTTimeDiv1MS_5MS=20, //50000, 1, 1
 HTTimeDiv1MS_10MS=21, //100000, 1, 1
 HTTimeDiv1MS_20MS=22, //200000, 1, 1

 //1047552 samples
 HTTimeDiv1MS_50MS=23, //500000, 1, 1
 HTTimeDiv1MS_100MS=24, //1000000, 1, 1
 HTTimeDiv500K_200MS=25,//1000000, 1, 1
 HTTimeDiv200K_500MS=26,//1000000, 1, 1
 HTTimeDiv100K_1S=27, //1000000, 1, 1
 HTTimeDiv100K_2S=28, //2000000, 1, 1
 HTTimeDiv100K_5S=29, //5000000, 1, 1
 HTTimeDiv100K_10S=30, //10000000,1,1
 HTTimeDiv100K_20S=31, //20000000,1,1
 HTTimeDiv100K_50S=32, //50000000,1,1
 HTTimeDiv100K_100S=33, //100000000,1,1
 HTTimeDiv100K_200S=34, //200000000,1,1
 HTTimeDiv100K_500S=35, //500000000,1,1
 HTTimeDiv100K_1000S=36,//1000000000,1,1
 HTTimeDiv100K_2000S=37,//2000000000,1,1
 HTTimeDiv100K_5000S=38,//-1,1,1
};

As you can see, to scale the waveforms properly the "Display Length" is not the same as the "Read Length" and in some cases it's larger than the former.

Needless to say, my application now behaves exactly like the stock software and later on I'll post my DLL Hooking code that I used to reverse engineer the timebase argument convention.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 03, 2013, 11:55:20 pm
Here is the DLL Hooking code I wrote to obtain the proper "Read Length" and "Display Length" values... It is a CodeGear RAD Studio C++ Builder project but most of the relevant code is written in standard C++ using windows API calls and should compile with few changes in any windows compiler.

This is the code I used to print the relevant information in the scope (see screenshot)... As you can see we are hijacking the original function to display some information, then handing control back to the original DLL function. To the original software this is completely transparent, it cannot tell that our DLL sits between it and the real DLL.

Code: [Select]
extern "C" __declspec(dllexport) void WINAPI HTDrawWaveInYT(HDC hDC, RECT Rect,
COLORREF clrRGB, USHORT nDisType, short* pSrcData, ULONG nSrcDataLen,
ULONG nDisDataLen, ULONG nCenterData, USHORT nDisLeverPos, double dbHorizontal,
double dbVertical, USHORT nYTFormat, ULONG nScanLen)
{
//Convert SrcDataLen, DisDataLen, dbHorizontal and dbVertical to a string
std::string CallData = AnsiString("DataLen: "+IntToStr((int)nSrcDataLen)+
" - DisLen: "+IntToStr((int)nDisDataLen)+
" - dbHorizontal: "+FloatToStr(dbHorizontal)+
" - dbVertical: "+FloatToStr(dbVertical)).c_str();

//Set the text color to the waveform color (otherwise our text will be black on black!)
SetTextColor(hDC, clrRGB);

//Display the text inside the waveform area
TextOut(hDC, Rect.left, Rect.top, CallData.c_str(), CallData.length());

//Call the original DLL function
lib_HTDrawWaveInYT(hDC, Rect, clrRGB, nDisType, pSrcData, nSrcDataLen, nDisDataLen,
nCenterData, nDisLeverPos, dbHorizontal, dbVertical, nYTFormat, nScanLen);
}

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on December 04, 2013, 05:22:20 am
Good going, Mark and Richard!

The information you two unearth is going to be vary valuable for anyone who wants to dig into the code.  Very informative and interesting.

Thanks, guys - I will continue to learn from you two.

Rick

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on December 04, 2013, 12:26:51 pm
The problem is, these values are highly dependent on what timebase you are in, and there is no documentation on what values to use on which timebases, and there is only one example in the SDK and PDF of it's use, but not enough to figure out what the rest should be.

The first problem I had to tackle was what "Read Length" values to use for each of the 39 different timebases in the original software, and an earlier post in this thread got me close, but no cigar.

I ended up having to write a redirection dll for the HTDisplayDll.dll...

Thanks, Richard, for taking the time to dig out this information.  Personally, I think it's pretty sad that Hantek doesn't simply publish it, rather than making customers jump through hoops.  It's not as if they don't know those numbers, and that without them, the data can't be displayed properly.

Quote
As you can see, to scale the waveforms properly the "Display Length" is not the same as the "Read Length" and in some cases it's larger than the former.

I probably need to come back when I have a bit more time to read this, but I still don't understand how a parameter in an acquisition function affects the raw captured data.  Unless the ReadData is NOT returning the actual sample data captured, but some expansion/interpolation thereof.  (Beyond the short 1016 captures you already explained previously.)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 04, 2013, 06:07:47 pm
I probably need to come back when I have a bit more time to read this, but I still don't understand how a parameter in an acquisition function affects the raw captured data.  Unless the ReadData is NOT returning the actual sample data captured, but some expansion/interpolation thereof.  (Beyond the short 1016 captures you already explained previously.)

I hooked the GetHardData and fed the "nReadLen" and "nDisLen" to a file and played around with the time bases and this is what I got:

Code: [Select]
nReadLen: 130048 - nDisLen: 800
nReadLen: 130048 - nDisLen: 500
nReadLen: 1016 - nDisLen: 960
nReadLen: 130048 - nDisLen: 800
nReadLen: 130048 - nDisLen: 1000
nReadLen: 523264 - nDisLen: 50000
nReadLen: 1047552 - nDisLen: 2000000000
nReadLen: 1047552 - nDisLen: -1

So it's essentially the same as the DrawWave, but as to why they need the display length in there, no idea... But I'm going to find out when I modify what they are sending the ReadHardData function  >:D

Edit: I modified the hook to change the nDisLen to 1000 then to 0 and I noticed no changes in application behavior, so it's entirely possible the parameter is redundant/unused.

Code: [Select]
extern "C" __declspec(dllexport) 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)
{
/*
//Stringify needed arguments
std::string Info = AnsiString("nReadLen: "+IntToStr((int)nReadLen)+" - nDisLen: "+IntToStr((int)nDisLen)).c_str();

//
std::ofstream OutFile("C:\\Program Files\\Hantek6022BE\\ReadHardData.txt", fstream::app);
OutFile << Info << std::endl;
OutFile.close();
*/

//Change Display Length >:)
nDisLen = 0;

return lib_dsoReadHardData(DeviceIndex, pCH1Data, pCH2Data, nReadLen, pCalLevel,
nCH1VoltDIV, nCH2VoltDIV, nTrigSweep, nTrigSrc, nTrigLevel, nSlope, nTimeDIV,
nHTrigPos, nDisLen, nTrigPoint, nInsertMode);
}
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 05, 2013, 06:48:47 am
Yet again, some more undocumented information... Not surprisingly the Hantek "SDK" or "Manual" doesn't mention this, but in order for triggering to work and display a stable waveform, you have to use the Trigger Point Index value (set by the ReadHardData function) inside the DrawWave function, specifically the nCenterData argument.

Now, the provided example code in the "SDK" shows this nCenterData argument being supplied with simply half of the ReadLength (of the raw data buffer).

However if you use this method you will find your waveforms bouncing all over the place and your Trigger Level having no effect what so ever...

Here is what you have to do... Supply the nCenterData argument with the value of the Trigger Point Index (index relative to raw data where triggered) + Raw Read Length divided by 2 (half of the entire raw data).

Again I had to use my Hooking code to find out what the hell was going on with the DrawWave function and I noticed that in the original software the nCenterData value wasn't exactly half of the RawDataLength and furthermore it was changing rapidly, which clued me to the possibility they were using the Trigger Point Index to offset it somehow.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rpcope1 on December 09, 2013, 07:28:22 am
I have reverse engineered the Front End if anyone is interested:

The A7 device is just a fast switching rectifier, it breaks down at 100V and it's being used to clamp the signal to -5V and +5V.

Also take note that the instead of your usual 1M ohm resistor and trimmer capacitor in parallel connected from input signal to ground we have the input signal going through a 909K resistor with the trimmer capacitor in parallel with it, then shunted to ground through a 100K resistor and an SMD capacitor in parallel. To the input, it looks like a 1M resistor to ground, but the signal is being tapped between 909K and 100K, then going to the first Op Amp. I'm not sure a 5V input signal in 1x mode is going to give a 5V signal at the node between the 909K and 100K, but more like 500mv. This would mean the probe in 1x mode is going to be safe all the way up to 50V and 500V in 10x.

Also, the outside of my unit shows a label between the BNC connecors that says "35vpk max" which I am not sure if they mean for 1x or 10x?

  Richard,

I would be very interested in what you've done with the front end. I wrapped the SDK into Python via ctypes, thinking I would use this scope for data acquisition and possibly doing some spectrum analysis. To you and anyone else that might be interested, I uploaded my Python wrapper to https://github.com/rpcope1/Hantek6022API . I hope someone can get something useful out of it.

Also to you and everyone else, I saw someone mentioned changing or fixing the DC-DC converter. I can see where the Mornsun DC-DC convert is soldered in (and I agree, it's a terrible choice for this application). I think the first thing I'm going to attempt to do is solder some big electrolytic caps onto between both the V+ and V- and the 0V reference coming out of the converter. Does this sound reasonable thing to do to reduce noise on the traces? I'm also open to changing the DC-DC converter here if anyone has some suggestions as to how to do, and reporting how it worked. I think this will make an interesting experiment.

  Also, I'm interested in any other experimentation you all are thinking about (including possibly hacking the firmware?).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 09, 2013, 04:40:41 pm
Quote
I would be very interested in what you've done with the front end

I added 100uF 16V electrolytics in parallel with the large SMD capacitors after the +5V USB branch and after the +3.3V Regulator.

I also stacked (in a very bodgy fashion) SMD capacitors on top of ALL the bypassing capacitors for the USB Micro and ADC.

Then I stacked SMD Capacitors on the larger of the three SMDs before the DC-DC (C103 & C105) and I stacked the SMD Capacitors on the other side, specifically the large ones going between +5 and -5 and the ones going from +5 to GND and -5 to GND, both before and after the Inductors.

Then I made a very rudimentary screening can out of copper foil shielding over clear PETE plastic, to which I measured and scored the PETE and folded it into a can shape, then soldered tinned copper wire to various places around the side, aligned with where the solder holes for the can were positioned. I made two of these so each channel had it's own can.

I then used copper foil tape to shield the holes on both aluminum end caps which were only covered with the sticky label on the other side, the largest of the holes is where the Logic Analyzer header would mount.

I used copper foil tape around the DC-DC and grounded it with a braided copper strap (Solder wick). Also, my unit did not come with a heatsink on the ADC (though my board revision is 1.00.2, not 1.00.1) so I added a flat TO220 heatsink mounted with Arctic Silver thermal adhesive and ground strapped with copper braid again.

Figures though, stupid me forgot to aquire some waveforms pre-modification to compare, but from memory I was getting 10-15mv noise and post modification it's down to 3-5mv.

I'll take pictures of the interior later and post them here, as well as some screenshots of the noise floor.

Quote
I think the first thing I'm going to attempt to do is solder some big electrolytic caps onto between both the V+ and V- and the 0V reference coming out of the converter. Does this sound reasonable thing to do to reduce noise on the traces? I'm also open to changing the DC-DC converter here if anyone has some suggestions as to how to do, and reporting how it worked. I think this will make an interesting experiment.

The DC-DC datasheet specifies a maximum capacitive load of 100uF so be careful what you add there, and I also plan on populating the Buck & Charge Pump section to see what happens.

Edit: Here is a high-res PNG legend of my changes using Aurora's high res PCB image (hope he doesn't mind): http://img198.imageshack.us/img198/3733/7ljo.png (http://img198.imageshack.us/img198/3733/7ljo.png)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 09, 2013, 07:01:22 pm
Here are the inside pictures, using a cell phone camera at the moment so they are not very bright or crisp...

As you can see, I have already started populating the alternative DC-DC section with SMD Capacitors, and I noticed some Hantek equipment has the Crystal can grounded so I did that as well, probably doesn't change much but it didn't hurt it either.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 09, 2013, 07:02:20 pm
And the front and back panels with copper foil over the gaping holes, held on with Kapton tape.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on December 10, 2013, 06:12:14 am
Awsome!  Richard.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rexnanet on December 12, 2013, 03:23:39 pm
Great "hack" :D

I've just ordered one and as soon as I get it I'm going to do the same!

Next step would be shorting some points to GND to see what's the main point of noise collection, going from the ADC input to the BNC connector. Despite this, 3-5mV seems more acceptable :)

Yep, photos from the noise floor from before the mod would be nice for comparison. I'll try to post some when I get mine.

I was plannig to build one myself... but time is not the most available product around here, so this one seemed a nice "low-cost starter kit" :)

P.S. Hello World! LOL
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on December 12, 2013, 04:03:03 pm
...forgot to aquire some waveforms pre-modification to compare, but from memory I was getting 10-15mv noise and post modification it's down to 3-5mv.

We're more interested in the after, than the before, but 10-15 mVpp noise is about average from all the reports here, and elsewhere.  Worst case I've seen reported was 20 mV, and that was probably an outlier.  And as bad as that sounds, it's not really unusual.  I.e., the max sensitivity of the 6022BE is 20mV/div, so you were seeing ~1/2-3/4 div of noise.  That's similar to many more expensive scopes.  Though they have much higher sensitivities, the relative noise levels are about the same.

While Vpp noise is good to know, also helpful could be using the FFT function, to get the spectral distribution of the noise components.

Lastly, you enumerated 6 tweaks you made to the board, though I thought I counted more like 8.  But in any event, it would be helpful to know the relative contribution of each, to maximize 'bang for the buck'.  Not necessarily to minimize cost, but perhaps time.  I suspect, and it's highly probably, that some tweaks will have very minimal influence.  And omitting them really wouldn't matter. 

Of course, to conduct such a study would require stopping to evaluate after each mod was installed.  I realize that's asking a bit much.  But just a thought for those following in your footsteps, if they'd like to make their own contributions.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rpcope1 on December 13, 2013, 03:13:22 am
Here are the inside pictures, using a cell phone camera at the moment so they are not very bright or crisp...

As you can see, I have already started populating the alternative DC-DC section with SMD Capacitors, and I noticed some Hantek equipment has the Crystal can grounded so I did that as well, probably doesn't change much but it didn't hurt it either.

Wow! This looks pretty good. I'm going to try to do the same for mine. Thanks so much for posting your pictures and keeping us updated!  :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 13, 2013, 07:24:08 pm
No problem guys, my pleasure.

Lastly, you enumerated 6 tweaks you made to the board, though I thought I counted more like 8.  But in any event, it would be helpful to know the relative contribution of each, to maximize 'bang for the buck'.  Not necessarily to minimize cost, but perhaps time.  I suspect, and it's highly probably, that some tweaks will have very minimal influence.  And omitting them really wouldn't matter. 

Of course, to conduct such a study would require stopping to evaluate after each mod was installed.  I realize that's asking a bit much.  But just a thought for those following in your footsteps, if they'd like to make their own contributions.

I don't want to hog all the fun :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: sneasle on December 19, 2013, 10:52:21 pm
Just ordered myself one of these to give myself a little extra capability until I move again next year and hopefully have enough room to add a true DSO.

That said, I appreciate the efforts you guys are putting into this thing, I look forward to implementing some of these changes on mine.


That said, I was wondering if anyone knew if any of the other software tools support this model yet?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 20, 2013, 02:12:04 am
That said, I was wondering if anyone knew if any of the other software tools support this model yet?

I am not aware of any, other than Open Hantek, which currently doesn't support the 6022BE however someone in their forums is attempting to add support for it.

I am in the process of making my own Open Source version using the Hantek "SDK", and my goal is to at least match the functionality of the original software which should be enough for anyone to start from in adding to it. It's being written in C++ using Code Gear's RAD Studio (C++ Builder, formally by Borland).

It's pretty far off from being done, or even usable but here is a screenshot of my progress thus far (see attachment):
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rpcope1 on December 23, 2013, 02:13:05 am
  Hey guys,

Just to build on RichardK's work, I got around modifying the hardware on my 6022BE this weekend. I added the 100 uF capacitors to the +5V USB rail and the +3.3V rail, and made an aluminum foil shield for the DC-DC converter, which was soldered to ground. I also added film 1 uF capacitors between +V0 and 0V and between -V0 and 0V. These capacitors hopefully don't push the DC-DC converter too far as capacitive load goes. It looks like I'm down to some sporadic 2-3 mV noise, which given how much I've got in this, isn't bad. RichardK, I really like your new GUI; I think C++ is a much better choice for this than Python, if nothing else for the speed. Thanks again for your hard work. :)

Edit: Spelling error.
No problem guys, my pleasure.

Lastly, you enumerated 6 tweaks you made to the board, though I thought I counted more like 8.  But in any event, it would be helpful to know the relative contribution of each, to maximize 'bang for the buck'.  Not necessarily to minimize cost, but perhaps time.  I suspect, and it's highly probably, that some tweaks will have very minimal influence.  And omitting them really wouldn't matter. 

Of course, to conduct such a study would require stopping to evaluate after each mod was installed.  I realize that's asking a bit much.  But just a thought for those following in your footsteps, if they'd like to make their own contributions.

I don't want to hog all the fun :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rpcope1 on December 23, 2013, 02:43:41 am
I attached a background noise power spectrum for my now modified 6022BE, which I think is pretty revealing. This scope is attached to my old laptop. When I remove the charger cable, the noise seems to grow slightly. I guess this thing doesn't have sufficient enough shielding or whatever else to reject all of the regular EMI at this level. Still I get flickers of noise at 3.8 mV; I suspect this only a single bit on the DAC, and I'm not sure we're going to do much better for noise reduction on this device. Still I'd be open to ideas to reducing it. :D

Here are the inside pictures, using a cell phone camera at the moment so they are not very bright or crisp...

As you can see, I have already started populating the alternative DC-DC section with SMD Capacitors, and I noticed some Hantek equipment has the Crystal can grounded so I did that as well, probably doesn't change much but it didn't hurt it either.

Wow! This looks pretty good. I'm going to try to do the same for mine. Thanks so much for posting your pictures and keeping us updated!  :)

Edit: Clarified what the power spectrum was referring to.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on December 30, 2013, 06:27:46 am
Little bit more progress on the software side (see attachment)...

I have implemented two different cursor modes, one exactly like the cursor mode in the original software (Cross, Horizontal, Vertical) and one I call Interactive, where two cursors labeled 1 & 2 in little circles are drawn with the waveform and you can interact with them by dragging them across the waveform, and they will follow the wave's y axis.

By the way, ignore the ugly toolbar button glyphs, those will not be in the final version as I am going to make my own graphics for the toolbar but those are placeholders until I am done.

Anyway, lots more work to do on it, but thought I'd share my progress thus far for those who are interested, thanks :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rpcope1 on December 31, 2013, 11:44:43 pm
Little bit more progress on the software side (see attachment)...

I have implemented two different cursor modes, one exactly like the cursor mode in the original software (Cross, Horizontal, Vertical) and one I call Interactive, where two cursors labeled 1 & 2 in little circles are drawn with the waveform and you can interact with them by dragging them across the waveform, and they will follow the wave's y axis.

By the way, ignore the ugly toolbar button glyphs, those will not be in the final version as I am going to make my own graphics for the toolbar but those are placeholders until I am done.

Anyway, lots more work to do on it, but thought I'd share my progress thus far for those who are interested, thanks :)

Richard, this looks awesome. Thanks for sharing! :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on January 01, 2014, 12:28:39 pm
Better software would be a Godsend to this hardware . Thank you your efforts to provide such  :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 02, 2014, 08:48:02 pm
Little bit more progress on the software side (see attachment)...

I have implemented two different cursor modes, one exactly like the cursor mode in the original software (Cross, Horizontal, Vertical) and one I call Interactive, where two cursors labeled 1 & 2 in little circles are drawn with the waveform and you can interact with them by dragging them across the waveform, and they will follow the wave's y axis.

By the way, ignore the ugly toolbar button glyphs, those will not be in the final version as I am going to make my own graphics for the toolbar but those are placeholders until I am done.

Anyway, lots more work to do on it, but thought I'd share my progress thus far for those who are interested, thanks :)

Richard, do you have executable/binary you can share?  I don't have a C++ compiler newer than Microsoft VC5.

Thanks
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 02, 2014, 09:16:03 pm
Richard, do you have executable/binary you can share?  I don't have a C++ compiler newer than Microsoft VC5.

Thanks

I'll be releasing binaries & source in conjunction with each other, and I'll make a source forge project for it when it's reached a usable stage.

It's lacking some key functionality right at the moment, like Triggering, which is at a bare minimum, auto trigger, I have not implemented start and stop acquire, xy mode.

Also, other areas like toolbar glyphs, buttons, main menu items and some display elements are incomplete, and utility features like importing and exporting, saving and restoring GUI settings at shutdown and startup of program, reference waveform channel... All are non functional or incomplete.

I'll compile a release build in a little bit and upload it here if you want to give it a whirl.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 02, 2014, 10:57:28 pm
Alright, here is the latest binary for those who want to tinker with it... http://jmp.sh/b/wOS6BUC9tp3Cels8JWf3 (http://jmp.sh/b/wOS6BUC9tp3Cels8JWf3)

Note: This is an unfinished pre-release build!

Limitations:
-----------------------------------------------------------
1. Trigger only works in Auto.
2. Horizontal mode limited to YT only.
3. Cannot Stop & Start Waveform (Acquire controls non-functional)
4. No Importing & Exporting waveforms or waveform images (not implemented).
5. Reference channel non functional (due to no importing)
6. Toolbar Buttons & Features incomplete.
7. Some Main Menu items incomplete or non functional.
8. GUI Control settings not saved on application close or restored on startup.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 03, 2014, 04:12:07 am
Alright, here is the latest binary for those who want to tinker with it... http://jmp.sh/b/wOS6BUC9tp3Cels8JWf3 (http://jmp.sh/b/wOS6BUC9tp3Cels8JWf3)

Note: This is an unfinished pre-release build!
....

Thanks, Richard K.  Just grabbed the zip and as soon as I can, I will give it a go.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 03, 2014, 02:10:03 pm
Hi,

Very informative thread and thanks to all who contributed!

I was looking for a simple (non soundcard) based scope and from link to link I got here.
I need a scope for measurements in the audio range 10Hz - 20kHz (occasionally 100Khz for SMPS) which as I understand this particular scope is fully capable of. I'm a tube amp hobbyst (but scope newbie) and I need a scope capable of measuring at least 50V AC and 500V DC. I'm OK of modding the unit so my question are:
1/ What mods would you suggest for enabling this scope to measure such voltages
2/ I didn't get if I can measure spectrum with this one
3/ How to isolate it from ground

Thanks in advance.


Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 03, 2014, 03:54:33 pm
1/ What mods would you suggest for enabling this scope to measure such voltages

Well, using a 1x probe you are safe up to 50V, using the 10x switch on the probes that come with the 6022BE you are safe up to 500V, and with a 100x probe up to 1000V etc...

2/ I didn't get if I can measure spectrum with this one

Possibly with FFT.

3/ How to isolate it from ground

1. Use a laptop on battery (Not connected to AC adapter)
2. Use a laptop and AC adapter with isolated ground (Ground lead not connected to secondary ground)
3. Use a USB isolator (it has opto isolators for data and an isolated DC-DC for power)
4. Use a mains isolation transformer to power computer/laptop.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 03, 2014, 04:54:22 pm
Thanks for your help.

I'll be using it on a desktop so I guess an USB isolator will do the job.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 03, 2014, 05:02:19 pm
Just a quick question on this scope,
In x1, any signals over 5v and under -5v get clipped, is that normal?

Also, that software looks great Richard, thanks  :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 03, 2014, 05:11:41 pm
Just a quick question on this scope,
In x1, any signals over 5v and under -5v get clipped, is that normal?

Not quite, the front end has the signal coming in through a capacitor and a 909k resistor then from there another 100k resistor and capacitor to ground (see attachment).

In this configuration, the clamping diodes D3/D2 will only see 10 percent of the input signal, so if in 1x mode it won't start clamping to +5 and -5 until the input signal goes over +- 50V.



Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 03, 2014, 06:07:05 pm
That's what I thought...
Is it likely that I've got a faulty unit then? Anything over 5v just becomes a perfect straight line at 5v, so maybe there's something wrong with it?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 03, 2014, 06:10:48 pm
That's what I thought...
Is it likely that I've got a faulty unit then? Anything over 5v just becomes a perfect straight line at 5v, so maybe there's something wrong with it?

Possibly, you should definitely open it up and see if you possibly have a different revision?

Edit: Actually it might be software, if you are on 5V per division (the highest it goes in software in 1x mode) then the software will clip the signal.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 03, 2014, 06:29:52 pm
That's probably what it is then... Why is it clipping the signal?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 03, 2014, 06:38:02 pm
That's probably what it is then... Why is it clipping the signal?

It's the dsoReadHardData function from the HTMarch.DLL, two of the arguments passed to it are the Voltage Per Division for both channels...

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);

As you can see, they are both Integers and they are not voltages, but selection box indexes, I.E.

Code: [Select]
//Voltage Division
enum THantekVoltDivision
{
 HTVoltDiv20mv=0,
 HTVoltDiv50mv=1,
 HTVoltDiv100mv=2,
 HTVoltDiv200mv=3,
 HTVoltDiv500mv=4,
 HTVoltDiv1V=5,
 HTVoltDiv2V=6,
 HTVoltDiv5V=7,
}

That function needs to scale the data it gets to match the vertical divisions of the grid, and they don't accept anything other than those hard coded values, so it's scaling what it reads to -5V to +5V, even if it's higher.

Either the function has to be modified or an alternative written in order to hack in additional Voltages for 1x.

In the mean time, if you want to measure higher than 5V, put the probe in 1x 10x and set the software probe setting to 10x and then select a voltage higher, say 10V or 20V.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 03, 2014, 06:43:47 pm
Understood, thanks for the help  :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 03, 2014, 07:13:30 pm
Actually, sorry you will still need your probe in 10x and software in 10x to measure higher than 5V.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 03, 2014, 07:37:24 pm
Seems a bit strange... Why is the max input voltage given as 35v then?  ???
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 03, 2014, 07:43:51 pm
Seems a bit strange... Why is the max input voltage given as 35v then?  ???

That's the derated hardware limit, which is actually 50V.... The hardware is capable, but the software is limited.

As of now I am hacking in a 10V mode for 1x, with software 10x attenuation but it won't solve the clipping issues, anything above 5V will get clipped by Hantek's data acquisition function.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 03, 2014, 08:03:22 pm
Well that's bloody annoying, this scope is a bit of a letdown...
At least I know what it is now though, thank you :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 03, 2014, 08:34:39 pm
...
3/ How to isolate it from ground

1. Use a laptop on battery (Not connected to AC adapter)
2. Use a laptop and AC adapter with isolated ground (Ground lead not connected to secondary ground)
3. Use a USB isolator (it has opto isolators for data and an isolated DC-DC for power)
4. Use a mains isolation transformer to power computer/laptop.

Let me also add one that caught me off-guard.

When trying to isolate your laptop from ground, do not use a KVM or external monitor with your laptop.  KVM creates a common ground between all connected machines even if they are OFF and that could be your ground path even if your laptop is on battery.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 03, 2014, 08:36:52 pm
...
3/ How to isolate it from ground

1. Use a laptop on battery (Not connected to AC adapter)
2. Use a laptop and AC adapter with isolated ground (Ground lead not connected to secondary ground)
3. Use a USB isolator (it has opto isolators for data and an isolated DC-DC for power)
4. Use a mains isolation transformer to power computer/laptop.

Let me also add one that caught me off-guard.

When trying to isolate your laptop from ground, do not use a KVM, external monitor, or wired-network with your laptop.  KVM creates a common ground between all connected machines even if they are OFF and that could be your ground path even if your laptop is on battery.  Wired network to a hub or another machine also possibly creates ground path.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 04, 2014, 12:27:26 pm
Quote
...do not use a KVM, external monitor, or wired-network with your laptop.

In my case it's just a desktop PC and nothing else.
How about cutting the USB power supply lines from PC to the unit and using a regulated bipolar power supply (wallwart adapter, ground isolated) to power it?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 04, 2014, 12:46:01 pm
Quote
...do not use a KVM, external monitor, or wired-network with your laptop.

In my case it's just a desktop PC and nothing else.
How about cutting the USB power supply lines from PC to the unit and using a regulated bipolar power supply (wallwart adapter, ground isolated) to power it?

You'd still need a common ground for the data, you could buy a USB isolator?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on January 04, 2014, 01:31:34 pm
480mbps USB2.0 Isolators can be very expensive  :(
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 04, 2014, 01:34:42 pm
480mbps USB2.0 Isolators can be very expensive  :(

Sadly I don't think there's another way around it, you might be able to build your own and bring the price down a bit?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 04, 2014, 03:11:12 pm
Wouldn't something like this do the job:

http://www.ebay.com/itm/USB-protection-ADUM4160-Evaluation-Board-USB-Isolator-/231092186962?pt=LH_DefaultDomain_0&hash=item35ce2aef52 (http://www.ebay.com/itm/USB-protection-ADUM4160-Evaluation-Board-USB-Isolator-/231092186962?pt=LH_DefaultDomain_0&hash=item35ce2aef52)

Project:

http://hackaday.com/2009/09/18/usb-isolation/ (http://hackaday.com/2009/09/18/usb-isolation/)

There are kits on sale:

http://www.circuitsathome.com/products-page/usb-interfaces (http://www.circuitsathome.com/products-page/usb-interfaces)

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on January 04, 2014, 03:30:11 pm
I believe those boards are all low and full speed USB isolators. For USB2.0 High Speed (480mbps) you would need something better. That is why I commented on price. IMHO a 480mbps USB isolator would likely cost more than the 6022BE and you would be better off looking for a different DSO.

Update...

This may be of interest.... a possible High Speed USB isolator ?

http://www.elektor-labs.com/project/high-speed-usb-20-isolator.12435.html (http://www.elektor-labs.com/project/high-speed-usb-20-isolator.12435.html)

Also this is interesting:

http://www.bb-elec.com/Learning-Center/All-White-Papers/USB/USB-Isolation/USB-Isolation.pdf (http://www.bb-elec.com/Learning-Center/All-White-Papers/USB/USB-Isolation/USB-Isolation.pdf)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 04, 2014, 03:31:56 pm
There may even be noise from the DC-DC in the isolator, so I would suggest using a Mains Isolation Transformer to run the PC, they can be had for pretty cheap if you know where to get them.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on January 04, 2014, 04:20:32 pm
I just found this EEVBlog thread that discussed High Speed USB Isolation.

I would personally be looking at input isolation to the DSO rather than trying to isolate the data output. I use a pair of Pico differential active probes when isolation is needed. The down side is the cost of these probes. For their cost you can buy a decent isolated portable DSO.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 05, 2014, 12:04:19 pm
I don't think differential probes are the solution, especially with a £50 USB DSO. A good set cost way too much to make it worthwhile.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on January 05, 2014, 02:19:07 pm
My point exactly. A better DSO, more suited to the task would be a better choice  ;)

The 6022BE is a compromise device built down to a price and may not be the 'right tool for the job'.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 05, 2014, 03:31:27 pm
My point exactly. A better DSO, more suited to the task would be a better choice  ;)

The 6022BE is a compromise device built down to a price and may not be the 'right tool for the job'.

Agreed. It's a budget tool, and you get what you pay for. And anyway, almost all scopes are earth referenced so why would you expect isolation with this thing? Just use it with a laptop if you really need it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 05, 2014, 04:20:40 pm
Latest Binary for anyone interested: http://jmp.sh/v/8koyiaueYLtxZfdq5MRj (http://jmp.sh/v/8koyiaueYLtxZfdq5MRj)

Changes:
1. Importing & Exporting now functional (Reference channel now functional)
      . Import saved .txt waveforms from original 6022BE software
      . Export & Import to custom binary format
      . Export to Bitmap & JPEG Images, visible or entire waveform, with render options to tweak + export preview
2. Hacked 10V/DIV option for 1X with Software Attenuation
3. Hacked AC Coupling (software filtering)
4. Various bug fixes and other minor changes

Interface Notes:
1. You can "drag" the waveform in view three different ways
     1a. Click and drag the "Waveform Context" area above the waveform (fastest way to drag, very course)
     2a. Click and drag the Waveform (slower, less course)
     3a. Use Left and Right arrow keys (slowest, fine control)

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 05, 2014, 04:29:54 pm
Quote
The 6022BE is a compromise device built down to a price and may not be the 'right tool for the job'.

I'm aware that it's a budget tool and I need one for measurements mainly in the audio range. It looks like a mains isolation transformer for the device under test is the way to go. Luckily I have a variable transformer by hand.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 05, 2014, 04:34:02 pm
Quote
The 6022BE is a compromise device built down to a price and may not be the 'right tool for the job'.
It looks like a mains isolation transformer for the device under test is the way to go. Luckily I have a variable transformer by hand.

Make sure your Auto transformer is isolated, most are not.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 05, 2014, 04:36:32 pm
Latest Binary for anyone interested: http://jmp.sh/v/NbdJxdvV1l35qIRE3DmP (http://jmp.sh/v/NbdJxdvV1l35qIRE3DmP)

Changes:
1. Importing & Exporting now functional (Reference channel now functional)
      . Import saved .txt waveforms from original 6022BE software
      . Export & Import to custom binary format
      . Export to Bitmap & JPEG Images, visible or entire waveform, with render options to tweak + export preview
2. Hacked 10V/DIV option for 1X with Software Attenuation
3. Hacked AC Coupling (software filtering)
4. Various bug fixes and other minor changes

Interface Notes:
1. You can "drag" the waveform in view three different ways
     1a. Click and drag the "Waveform Context" area above the waveform (fastest way to drag, very course)
     2a. Click and drag the Waveform (slower, less course)
     3a. Use Left and Right arrow keys (slowest, fine control)

Not working for me on Windows 8.1, I think it's connected to the scope but no waveform is being shown, not even a line. Maybe it's just something wrong with my setup, thanks anyway for all the hard work, looks great so far :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 05, 2014, 04:40:16 pm
Not working for me on Windows 8.1, I think it's connected to the scope but no waveform is being shown, not even a line. Maybe it's just something wrong with my setup, thanks anyway for all the hard work, looks great so far :)

Hmm... Did the previous binary work? (assuming you tried that one)... And when the scope is connected, is the light on the scope Red and blinking, or green and solid?

Edit: Also, I am correct in assuming the stock software works for you under Windows 8? And if you could, start the software without the scope connected and enter Demo mode, do the various waveforms in the demo mode show up? And another thing, if the software is in demo mode, it won't capture from scope until you exit demo mode.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 05, 2014, 05:08:46 pm
Previous binary had the same problem, when the scope is connected I'm getting a green blinking light. The stock software works fine, and I tried the demo mode but I couldn't get any waveform to appear, same as before with no line on the screen...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 05, 2014, 05:26:22 pm
Previous binary had the same problem, when the scope is connected I'm getting a green blinking light. The stock software works fine, and I tried the demo mode but I couldn't get any waveform to appear, same as before with no line on the screen...

Hmm thanks, I'll try and figure out why, it sounds like a problem with HTDrawWaveInYT()... Question: Do you see a grid, or is that missing too?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 05, 2014, 05:37:29 pm
Grid's there, everything else except the waveform. I wish I could be of more help, but I haven't done proper programming in years...
Thanks again for all this, it's going to be great to have alternative software :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 05, 2014, 05:47:47 pm
Grid's there, everything else except the waveform. I wish I could be of more help, but I haven't done proper programming in years...
Thanks again for all this, it's going to be great to have alternative software :)

Quick test if you could: Start it up in Demo Mode, put a sine wave in CH1 and go to export, then click the "Image Preview" tab...

Do you see a waveform in the preview? Thanks :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 05, 2014, 06:34:57 pm
I might have found the problem and a possible workaround (though I don't have a Windows 8 machine to test it on atm)... There is apparently an issue with the Windows AlphaBlend() function on 64bit machines, and I use the AlphaBlend function to set the waveform brightness, since the Hantek SDK provides no ability to set it in the draw wave function, the draw grid function provided by the SDK does have a brightness argument so I don't need to use AlphaBlend() there, so that might also explain why the grid draws but not waveforms.

Here is the new binary: http://jmp.sh/v/MWcYkfQZ5t1qRzXBWIZD (http://jmp.sh/v/MWcYkfQZ5t1qRzXBWIZD)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on January 07, 2014, 02:34:51 am
Quote
Here is the new binary: http://jmp.sh/v/8koyiaueYLtxZfdq5MRj (http://jmp.sh/v/8koyiaueYLtxZfdq5MRj)

Thanks RichardK for your hard work.

 Let me introduce myself and my short story with this scope, I'm a mechanic teacher and we used to use "picoscope" oscilloscope with our student. Due to budget, we had 3 "pico" for 80 students so when I saw these low price 6022be scope I decide to give it a shot and see if we could maybe get more scope for our students for the same budget. I got the first unit last week to test it and played a little bit today with the official software. Let me say I’m a little bit disappointed with some functionality such as the lack of a zoom function and the printing which print the yellow and green waveform with a b/w printer in a pale grey that's almost invisible.

So after some googling I came to this forum and saw you project.
I tried your beta and saw that you plan to take care of these 2 issues by letting the user change the default yellow and green colour for waveform which should result in a darker printed wave, once switch to darker colour and in the acquire tab, you seem to plan a zoom function.

So I want to encourage you to continue your great work that will surely be of great use for many people!

thanks a million times
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 07, 2014, 05:31:33 am
Thanks RichardK for your hard work.

No problem, I actually enjoy improving hardware & software that has promise but is lacking in features or specifications, and if others find my work useful to them, even better :)

Btw, changing the waveform colors is already implemented and the next binary should have zooming implemented, but take note that a zoomed waveform is no longer in scale with the grid (or as Dave would say, out of calibration) and thus voltage and time measurements will be disabled to prevent measurement errors!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 07, 2014, 06:58:54 am
I might have found the problem and a possible workaround (though I don't have a Windows 8 machine to test it on atm)... There is apparently an issue with the Windows AlphaBlend() function on 64bit machines, and I use the AlphaBlend function to set the waveform brightness, since the Hantek SDK provides no ability to set it in the draw wave function, the draw grid function provided by the SDK does have a brightness argument so I don't need to use AlphaBlend() there, so that might also explain why the grid draws but not waveforms.

Here is the new binary: http://jmp.sh/v/8koyiaueYLtxZfdq5MRj (http://jmp.sh/v/8koyiaueYLtxZfdq5MRj)

Awesome, working perfectly now  :-+ Thanks.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on January 07, 2014, 12:05:48 pm
Quote
zoomed waveform is no longer in scale with the grid

Would it be possible to have dôme sort of measurement like on the pico software? Or is it limited by the hardware?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 07, 2014, 03:18:22 pm
Quote
zoomed waveform is no longer in scale with the grid

Would it be possible to have dôme sort of measurement like on the pico software? Or is it limited by the hardware?

I have never used picoscope before, so I'm not familiar with that type of measurement.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jon86 on January 07, 2014, 05:56:27 pm
This software's looking really good, already feels much nicer than the stock software.
Is there a possibility of waveform averaging and intensity grading in the future? That would make this scope so, so much better.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on January 07, 2014, 06:03:02 pm
Quote
zoomed waveform is no longer in scale with the grid

Would it be possible to have dôme sort of measurement like on the pico software? Or is it limited by the hardware?

I have never used picoscope before, so I'm not familiar with that type of measurement.

Well, let's say that you want to zoom deeper into your signal (for us in mechanic it's usefull to analyse the spark in an ignition system) it lets you zoom and mesure a specific point (V or time)  into that zoomed image.  I'm not sure if that's made by zooming the grid  at the same time than the waveform itself. Or maybe it's a math thing.... like maybe.. you zoom 10x, our cursor is on the 2.3V level on the unzoomed grid -> so 2.3V / 10x = 0.23V . something like that... I don't know how to explain this the proper way... so here's a screenshot of the pico "zoom" fonction.

in the small windows up this is the actual waveform I took from an ignition spark. the main window is the zoom part of it where I mesure one point of the wave.


Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 07, 2014, 06:20:18 pm
This software's looking really good, already feels much nicer than the stock software.
Is there a possibility of waveform averaging and intensity grading in the future? That would make this scope so, so much better.

Possibly, I had planned on adding effects like that later on, but right now I'm focusing on getting it more complete as a whole, and usable...

In fact, while messing around with Alpha blending when implementing the waveform intensity code I accidentally ended up with a simple form of waveform averaging which looked very analog-ish.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 07, 2014, 06:23:12 pm
Well, let's say that you want to zoom deeper into your signal (for us in mechanic it's usefull to analyse the spark in an ignition system) it lets you zoom and mesure a specific point (V or time)  into that zoomed image.  I'm not sure if that's made by zooming the grid  at the same time than the waveform itself. Or maybe it's a math thing.... like maybe.. you zoom 10x, our cursor is on the 2.3V level on the unzoomed grid -> so 2.3V / 10x = 0.23V . something like that... I don't know how to explain this the proper way... so here's a screenshot of the pico "zoom" fonction.

in the small windows up this is the actual waveform I took from an ignition spark. the main window is the zoom part of it where I mesure one point of the wave.

I would have to implement my own draw grid function, as the provided Hantek "SDK" function for drawing the grid does not allow zooming the grid to match the waveform.

Maybe after I have finished all the major work left to do on this, I'll try and whip up a "blown up" view dialog with a scaled grid.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on January 07, 2014, 06:49:15 pm
Quote
Maybe after I have finished all the major work left to do on this, I'll try and whip up a "blown up" view dialog with a scaled grid.

There's no hurry on this. Considering the fact that you are already doing a lot on your own. I just think that it would be useful for a many peoples.

keep on the good work.

thanks!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 08, 2014, 04:13:05 am
Richard,

The Open 6022 front end you wrote is quite an accomplishment.  It has a nice feel to it.  Allow me to point out a few things where I found trying:

1. The start up seems to have a bit of delay.  A few times, I re-clicked and ended up starting multiple instances.

2. The interactive measurement is quite nice.  It however escapes me on how to catch the peak, min, or max – points that I cannot exactly put a cursor on.

3. Wave form for Ch2 is weird.  I have Ch1 on a TTL square wave and Ch2 on the output part of the circuit which transform the TTL square wave transformed to Sine wave.  The two waves are same frequency and phase.  With the native software, the two wave forms are locked together as they should (since one is input and one is output of the same wave source).  With Open6022 however, the Ch2 wave keeps rolling left/right as if it is not related to the Ch1 wave.  I tried from low KHz to 4MHz using the UB1308S function generator.

4. I was confused for a while as only one set of vertical control is visible only.  Until I found the drop down to change from Ch1 to Ch2, I was for a moment very confused by not able to deal with Ch2.  It was rather inconvenient to drop down to switch to control “the other channel” and back again.  I think keeping both Ch1 and Ch2 vertical control knobs visible would be nice.  Perhaps use the same check box: when wave for Ch? Is shown, the vertical controls are also shown.

I particularly like these new abilities you provided:
1. AC couple via software, love this.  Too many circuits at “points of interest”, I had an extra capacitor to no where merely to provide a hook up point for the scope so as I can see how things are working.  With this AC coupling, it makes taping into any point less cumbersome.
2. Change color – something so simple yet it can make the software seem so much more friendly.
3. Looks like the top “mini wave window” shows what part of the captured data is being displayed as I drag the wave forms left and right.  I like that.  It does not seem fully functional yet since the T like pointer doesn’t seem to move consistently with my dragging.  If my gut feel is right and that it is suppose to point at what part of the captured wave is being displayed, it would add so much and make the software so much more “user friendly.”

Thanks, Richard.  Thanks for your hard work – we are benefited by it.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 08, 2014, 05:36:28 am
1. The start up seems to have a bit of delay.  A few times, I re-clicked and ended up starting multiple instances.

Fixed (I hope) in latest binary (see below)...

Quote
2. The interactive measurement is quite nice.  It however escapes me on how to catch the peak, min, or max – points that I cannot exactly put a cursor on.

It's harder to get it exactly when at lower resolutions (many waveforms in view), the original cursor measurement feature is probably better for finer measurements.

Quote
3. Wave form for Ch2 is weird.  I have Ch1 on a TTL square wave and Ch2 on the output part of the circuit which transform the TTL square wave transformed to Sine wave.  The two waves are same frequency and phase.  With the native software, the two wave forms are locked together as they should (since one is input and one is output of the same wave source).  With Open6022 however, the Ch2 wave keeps rolling left/right as if it is not related to the Ch1 wave.  I tried from low KHz to 4MHz using the UB1308S function generator.

Fixed in latest binary (see below)...

Quote
4. I was confused for a while as only one set of vertical control is visible only.  Until I found the drop down to change from Ch1 to Ch2, I was for a moment very confused by not able to deal with Ch2.  It was rather inconvenient to drop down to switch to control “the other channel” and back again.  I think keeping both Ch1 and Ch2 vertical control knobs visible would be nice.  Perhaps use the same check box: when wave for Ch? Is shown, the vertical controls are also shown.

The reason I did this was because I felt the original software interface was too busy, and I was sick of scrolling down to modify CH2, so I figured using the arrow key to select channels would be a little better than trying to cram them all in. I'll look into making it easier to interact with CH1 & CH2 without using the drop down list.

Quote
It does not seem fully functional yet since the T like pointer doesn’t seem to move consistently with my dragging.  If my gut feel is right and that it is suppose to point at what part of the captured wave is being displayed, it would add so much and make the software so much more “user friendly.”

I think you are using an older binary, because I optimized the wave context movement recently, it's smooth as butter now even in a debug build... Here is the very latest binary: http://jmp.sh/v/MWcYkfQZ5t1qRzXBWIZD (http://jmp.sh/v/MWcYkfQZ5t1qRzXBWIZD)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 09, 2014, 04:57:10 am
1. The start up seems to have a bit of delay.  A few times, I re-clicked and ended up starting multiple instances.

Fixed (I hope) in latest binary (see below)...


Fix confirmed!  The new binary starts right the way.

2. The interactive measurement is quite nice.  It however escapes me on how to catch the peak, min, or max – points that I cannot exactly put a cursor on.

It's harder to get it exactly when at lower resolutions (many waveforms in view), the original cursor measurement feature is probably better for finer measurements.


Yeah, I think the non-cursor measurement window needs to come back as well.  Otherwise, it would be hard to measure something that is not always there to put a cusor on - such as trying to catch the peak of an unknown/irregular pulse that is not on the current trace.

3. Wave form for Ch2 is weird.  I have Ch1 on a TTL square wave and Ch2 on the output part of the circuit which transform the TTL square wave transformed to Sine wave.  The two waves are same frequency and phase.  With the native software, the two wave forms are locked together as they should (since one is input and one is output of the same wave source).  With Open6022 however, the Ch2 wave keeps rolling left/right as if it is not related to the Ch1 wave.  I tried from low KHz to 4MHz using the UB1308S function generator.

Fixed in latest binary (see below)...


Fix confirmed!  I used the same wave and Ch2 is plotted exactly like Ch1.  I put Ch2 into a frequency that is a multiple of Ch1 and the wave appears exactly as expected.  Two cycles with Ch2 lined up with the single cycle on Ch1.  Ch2 is no longer rolling wild.

4. I was confused for a while as only one set of vertical control is visible only.  Until I found the drop down to change from Ch1 to Ch2, I was for a moment very confused by not able to deal with Ch2.  It was rather inconvenient to drop down to switch to control “the other channel” and back again.  I think keeping both Ch1 and Ch2 vertical control knobs visible would be nice.  Perhaps use the same check box: when wave for Ch? Is shown, the vertical controls are also shown.

The reason I did this was because I felt the original software interface was too busy, and I was sick of scrolling down to modify CH2, so I figured using the arrow key to select channels would be a little better than trying to cram them all in. I'll look into making it easier to interact with CH1 & CH2 without using the drop down list.


I understand - I agree with the "too busy look" and agree with your logic.  Perhaps make it shows only when a channel is enabled.  Or may be forget the "knobs" to change scale but just use drop down menus?

It does not seem fully functional yet since the T like pointer doesn’t seem to move consistently with my dragging.  If my gut feel is right and that it is suppose to point at what part of the captured wave is being displayed, it would add so much and make the software so much more “user friendly.”
I think you are using an older binary, because I optimized the wave context movement recently, it's smooth as butter now even in a debug build... Here is the very latest binary: http://jmp.sh/v/MWcYkfQZ5t1qRzXBWIZD (http://jmp.sh/v/MWcYkfQZ5t1qRzXBWIZD)

Fix confirmed!  The dragging you provided is really a joy to use - whereas the stock software, using the stock software's dragging is really a drag.

Once you get "Normal" and "Single Shot" working, I can see using this to catch a whole wave form and then find it easily.

***
And now for something completely different.  I got an Abort testing Interactive Cursor. Probably a divide by zero or unexpected values in a calculation.
(see attached Access Violation error screen print.)
I am able to reproduce it with these steps:
- I had both channels connected.
- I had both on 100KHz, Ch1 Sine wave, Ch2 Square wave.
- Time base is 20uS/division
- (EDITED: adding info on the vertical:)
  Vertical is 1V/division.
  Ch1 (sine) max and min are 1.82V, 3.64V peak to peak according to stock version measurement window
  Ch2 (square) max 816mV, min -753mV, 1.57V peak to peak
- Interactive cursor measurement is turned on
  The cursor positions likely is important. I am not sure this what other settings will trigger it, but the settings below is a sure way of making it happen:
  Ch1 measurement point is point #2 is about 2 divisions right of point #1 and about 1 division below point #1.
  Ch2 measurement points are left as default.
- I changed Ch2 to 0Hz
- I changed Ch1 to 0Hz
- I changed Ch1 to 0.1Hz
 (So far so good...next step cause error)
- I changed timebase to 5 seconds
 The system pauses for a brief moment waiting for the trigger, then the program aborts.
***

Hey, Richard.  Thank you so much for your hard work.  I think I speak for the rest of us: "We appreciate it!"

Rick
(re-edited for typo and format error and typo)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 10, 2014, 12:51:49 am
And now for something completely different.  I got an Abort testing Interactive Cursor. Probably a divide by zero or unexpected values in a calculation.
(see attached Access Violation error screen print.)
I am able to reproduce it with these steps:
- I had both channels connected.
- I had both on 100KHz, Ch1 Sine wave, Ch2 Square wave.
- Time base is 20uS/division
- (EDITED: adding info on the vertical:)
  Vertical is 1V/division.
  Ch1 (sine) max and min are 1.82V, 3.64V peak to peak according to stock version measurement window
  Ch2 (square) max 816mV, min -753mV, 1.57V peak to peak
- Interactive cursor measurement is turned on
  The cursor positions likely is important. I am not sure this what other settings will trigger it, but the settings below is a sure way of making it happen:
  Ch1 measurement point is point #2 is about 2 divisions right of point #1 and about 1 division below point #1.
  Ch2 measurement points are left as default.
- I changed Ch2 to 0Hz
- I changed Ch1 to 0Hz
- I changed Ch1 to 0.1Hz
 (So far so good...next step cause error)
- I changed timebase to 5 seconds
 The system pauses for a brief moment waiting for the trigger, then the program aborts.
***

Thanks for detailing this bug, I fixed it and will upload the latest binary later on... The problem was a little more complicated than a divide by zero, it was a small oversight in some calculations I do to scale mouse cursor positions from the scope image to data array indexes and vice-versa.

The mistake was when writing the scaling code, I had made the assumption that the Raw Read Length (the length of the waveform data array) would always be larger than the Raw Draw Length (the length of the raw data to draw to the screen)...

Well as it turns out (and I knew this but it didn't pop into my head when writing that part of the code) that when the Timebase is 2 seconds or higher, the Raw Draw Length is actually higher than the Raw Read Length and you can tell, because the waveform becomes shrunken inside the scope view.

The fix was to get the ratio between the Raw Draw Length and Raw Read Length and use this in the scaling calculations, otherwise they would be invalid from 2S/DIV upward!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 10, 2014, 04:23:34 am
Here is the very latest binary: http://jmp.sh/v/UPtQLGTWm7zJrftGiad2 (http://jmp.sh/v/UPtQLGTWm7zJrftGiad2)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 10, 2014, 06:21:13 pm
Here is the very latest binary: http://jmp.sh/v/lNrJZjN58d1SpM42tz8O (http://jmp.sh/v/lNrJZjN58d1SpM42tz8O)
RichardK,

Sorry!  This fix doesn't work.  The cursor just jump around and I cannot grab/set it at any point  to do testing.  The cursor is not even on the trace.  See attached short video at about 38 seconds in and you will see what I mean.

Short Video showing jumping cursor (https://www.youtube.com/watch?v=jhSaOwSdmDM#)

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 10, 2014, 06:55:08 pm
Here is the very latest binary: http://jmp.sh/v/lNrJZjN58d1SpM42tz8O (http://jmp.sh/v/lNrJZjN58d1SpM42tz8O)
RichardK,

Sorry!  This fix doesn't work.  The cursor just jump around and I cannot grab/set it at any point  to do testing.  The cursor is not even on the trace.  See attached short video at about 38 seconds in and you will see what I mean.

Short Video showing jumping cursor (https://www.youtube.com/watch?v=jhSaOwSdmDM#)

Rick

Opps sorry about that, I forgot to update a piece of code... Should be fixed now: http://jmp.sh/v/UPtQLGTWm7zJrftGiad2 (http://jmp.sh/v/UPtQLGTWm7zJrftGiad2) NOTE: Same zip filename as before, make sure you remove the old one!

Also in that new binary the waveform dragging (dragging the scope, not the waveform context area above) and the scrolling with left and right arrow keys is now scaled to TimeDIV so the waveforms will move the same regardless of Timebase.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on January 10, 2014, 08:12:10 pm
@RichardK,

I just wanted to send you a big THANK YOU for your work on this software. You are very generous with you time and skills. My 6022BE has not been used since discovering the poor performance of the supplied software. I will have to dig it out in preparation for its first exposure to decent coding  :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 10, 2014, 08:19:15 pm
@RichardK,

I just wanted to send you a big THANK YOU for your work on this software. You are very generous with you time and skills. My 6022BE has not been used since discovering the poor performance of the supplied software. I will have to dig it out in preparation for its first exposure to decent coding  :)

You're welcome, I'm just glad other people are finding my work useful to them somehow, even if it's purely a spare time project and I am grateful for all the various feedback and suggestions :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 10, 2014, 08:20:32 pm
Here is the very latest binary: http://jmp.sh/v/lNrJZjN58d1SpM42tz8O (http://jmp.sh/v/lNrJZjN58d1SpM42tz8O)
RichardK,

Sorry!  This fix doesn't work.  The cursor just jump around and I cannot grab/set it at any point  to do testing.  The cursor is not even on the trace.  See attached short video at about 38 seconds in and you will see what I mean.

Short Video showing jumping cursor (https://www.youtube.com/watch?v=jhSaOwSdmDM#)

Rick

Opps sorry about that, I forgot to update a piece of code... Should be fixed now: http://jmp.sh/v/UPtQLGTWm7zJrftGiad2 (http://jmp.sh/v/UPtQLGTWm7zJrftGiad2) NOTE: Same zip filename as before, make sure you remove the old one!

Also in that new binary the waveform dragging (dragging the scope, not the waveform context area above) and the scrolling with left and right arrow keys is now scaled to TimeDIV so the waveforms will move the same regardless of Timebase.

Fix Confirmed!  That problem is history.

Thanks for the hard work.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on January 11, 2014, 12:50:01 pm
@RichardK:
I just ordered the 6022BE because of your improved software.
Thank you for all the time & energy that you put into this software.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: callito on January 15, 2014, 12:44:07 pm
@RichardK

Wow, god dam this is awesome! Just a few questions.
you hacked the SW for 1x to 10V,... so if I use the 10x probe it goes to 100V up??

and is it possible to hack this SW, so it goes up to 35V at 1x??? and 350V at 10x probe?

that would be unbelievable!! I normally want to use this scope for 3-16V at 10-100Hz, so it would be great if I can use 1x probe up to 35V instead of the factory-set 10x probe at 50V .

By the way,.. I did't order this 6022BE yet,.. just saw this thread today and since you do something with the SW, I wanna have this scope!


Thank you very, very much for your hard work!!!

Greetings, and sorry for my bad english.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: womai on January 15, 2014, 01:07:30 pm
But even with the new software the scope has a lot of issues (see the first few pages of this thread...) - as they say, you can put lipstick on a pig but it will still be a pig :=)

The +/-5V is a limitation in the hardware, so software won't be able to get around this restriction.

I would definitely NOT recommend this scope in its current state.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 15, 2014, 03:58:43 pm
But even with the new software the scope has a lot of issues (see the first few pages of this thread...) - as they say, you can put lipstick on a pig but it will still be a pig :=)

The +/-5V is a limitation in the hardware, so software won't be able to get around this restriction.

I would definitely NOT recommend this scope in its current state.

The +/-5V is a limitation in 1x mode, it's not like you can't measure any signal over +/-5V period, in fact the limitation is not hardware, as you can see from the front end, after the 900K & 100K resistor, the input signal is 1/10th lower, so it's NOT being clipped by those protection diodes.

The signal is being clipped either in the firmware, or the acquire DLL, hopefully the latter as that will be easier to hack.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 15, 2014, 04:02:58 pm
@RichardK

Wow, god dam this is awesome! Just a few questions.
you hacked the SW for 1x to 10V,... so if I use the 10x probe it goes to 100V up??

and is it possible to hack this SW, so it goes up to 35V at 1x??? and 350V at 10x probe?

that would be unbelievable!! I normally want to use this scope for 3-16V at 10-100Hz, so it would be great if I can use 1x probe up to 35V instead of the factory-set 10x probe at 50V .

By the way,.. I did't order this 6022BE yet,.. just saw this thread today and since you do something with the SW, I wanna have this scope!


Thank you very, very much for your hard work!!!

Greetings, and sorry for my bad english.

It's a software hack of 10V/DIV @ 10x but with software attenuation, so you lose some resolution. It's just a placeholder for now as I plan on trying to hack either the driver or the DLL to get access to the real raw data, not the tweaked data provided by the SDK.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: callito on January 15, 2014, 04:51:13 pm
Quote
It's a software hack of 10V/DIV @ 10x

Ahhhh.. ok I understand.... i thought it would be @ 1x ... but still very cool and usable!

If you are realy gonna hack the driver or dll's.. wow,... but i think it is very hard to do so...
...it would be dubble the price, if they will find out.

Good luck, so, I'm "staying tuned"


Greetings

 
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on January 15, 2014, 05:10:57 pm
I did notify today that the printing option is not available,
Am I doing something wrong or you just haven't reach this point yet?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 15, 2014, 05:19:58 pm
I did notify today that the printing option is not available,
Am I doing something wrong or you just haven't reach this point yet?

Printing is not implemented yet, but will be soon... Typically, if you notice anything in the interface that doesn't appear to do anything, it's not implemented yet. Exceptions being of course, things that worked in previous builds, as this may be a bug!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Prana on January 15, 2014, 06:52:11 pm
@RichardK
Hi, is it possible to use your software with Hantek 6052BE (50 Mhz version of this scope) ??
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 15, 2014, 09:46:45 pm
@RichardK
Hi, is it possible to use your software with Hantek 6052BE (50 Mhz version of this scope) ??

It does not, however that model might work with OpenHantek for reasons stated below...

That model uses vastly different hardware and thus a vastly different software architecture than the 6022BE, in fact I have looked at all the SDKs for all USB scopes & Logic Analyzers and most of them use the same architecture as the 6052BE, and the 6022BE software architecture is unique, I have not encountered it's design in any of the other SDKs.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on January 15, 2014, 11:35:07 pm
I did notify today that the printing option is not available,
Am I doing something wrong or you just haven't reach this point yet?

Printing is not implemented yet, but will be soon... Typically, if you notice anything in the interface that doesn't appear to do anything, it's not implemented yet. Exceptions being of course, things that worked in previous builds, as this may be a bug!

Not that anyone has been complaining, but there's been a fair amount of "this or that doesn't seem to be working?".  It's good to keep in mind that RK is an outsider (doesn't work for Hantek, and is uncompensated), with no internals info other than what he's managed to figure out for himself, working part-time, for a couple weeks.  And even with all those constraints, he's managed to out-do the full-time Hantek programmer(s) with full access to all the internals, and other resources, for the past ?? years! 

Let's let him proceed at his own pace, without any pressure.  The capabilities and limitations of previous beta releases have been documented, and I suspect he'll continue to document improvements as he announces new versions.

Richard,

one thing that might help minimize confusion is if in your ReadMe you had a simple list of the major Features, broken into Implemented and Not-Implemented Yet lists.  Then just move one line between the 2 lists as their status changes.  That's about as simple a project-management & status tracking technique as I can think of.

You could even have a 3rd list (Not-Planned), if folks start requesting things that aren't possible, or you don't plan on doing.  That would forestall repeated requests (and explanations), since it's fairly obvious that folks aren't going back through and reading the thread postings.

[Oh, and thanks for all your efforts.  You're doing a great job!]
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 15, 2014, 11:52:54 pm
one thing that might help minimize confusion is if in your ReadMe you had a simple list of the major Features, broken into Implemented and Not-Implemented Yet lists.  Then just move one line between the 2 lists as their status changes.  That's about as simple a project-management & status tracking technique as I can think of.

You could even have a 3rd list (Not-Planned), if folks start requesting things that aren't possible, or you don't plan on doing.  That would forestall repeated requests (and explanations), since it's fairly obvious that folks aren't going back through and reading the thread postings.

I was thinking about doing that for the next binary, since I was not originally going to periodically release binaries for a functionally incomplete project (I assumed nobody would want to use a partially functional program).

I will release the next binary soon, I know it's been a while between releases it's just that I have a methodology of "Get it working first, optimize it later" and I have to do more testing due to a switch from Borland's TTimer to true multi-threading for Capture & Drawing, and as you would expect with multi-threading you have to track down race conditions and I think I nailed them all, but I'm just being extra cautious.

The latest binary will have better performance (due to the multiple threads) and almost fully functional triggering, as well as initial support for FFT (which is already partially implemented in the last binary, but who's feature is hidden in the GUI) ;)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on January 16, 2014, 07:53:03 am
I was not originally going to periodically release binaries for a functionally incomplete project (I assumed nobody would want to use a partially functional program).

Yeah, but what you overlooked is that's what everyone with a 6022BE has always been doing, so far.  ;)  Whether they wanted to or not.  You're raising the bar.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 16, 2014, 10:48:11 am
Richard, I've seen in the past people developing software for big companies' products which despite their big names released products with mediocre software to say the least and then offering fully functional software against small charge and/or donations.
Or maybe you can contact and make some deal with Hantek against some of their higher quality product/s or something so they can give you the software source as they will profit from it as well?

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 19, 2014, 04:37:16 pm
Hi I joined this forum after reading this great thread. I have also bought the Hantek 6022be for all the reasons already mentioned.  The software RichardK is busy with just made it more promising. I still need to understand how to use this DSO properly, as this is all new to me.

I will try to post the noise shown on both my channels when connected to the internal square wave. It interesting to see that channel 2 is nearly clean compared to channel 1.
Both probes were set to X10.
Any comments please?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 20, 2014, 02:19:22 am
Latest Binary: http://jmp.sh/v/NptVTtzwQwZwLEnbZwFe (http://jmp.sh/v/NptVTtzwQwZwLEnbZwFe)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 20, 2014, 09:14:26 am
RichardK I ran your latest binary to compare my unmodified Hantel 6022be noise level on the Hantek software and yours. I still find my channel 1 very clean with only the odd noise spike now and then on the OEM software. The exact same settings on your software gives corresponding noise levels on both channels.
I have attached two screen shots:
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 20, 2014, 03:23:05 pm
No idea, I get the data the same way the stock software does...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rpcope1 on January 20, 2014, 04:32:31 pm
Hi I joined this forum after reading this great thread. I have also bought the Hantek 6022be for all the reasons already mentioned.  The software RichardK is busy with just made it more promising. I still need to understand how to use this DSO properly, as this is all new to me.

I will try to post the noise shown on both my channels when connected to the internal square wave. It interesting to see that channel 2 is nearly clean compared to channel 1.
Both probes were set to X10.
Any comments please?

  Matchless,
Have you added any shielding internal to the oscilloscope? I followed some of RichardK's instructions (thanks again so much dude), and added a couple extra caps and some shielding to the DC/DC converter, this should reduce a lot of the noise you're seeing. I also ran a power spectrum on the base level noise coming out of the oscilloscope after the fact (if you look back a couple pages) and found that most of my noise now was 60 Hz noise, which just means the whole thing needs better shielding (the oscilloscope is plugged into a laptop, so I was pretty sure that probably isn't a noise source). I wouldn't be totally surprised a stock oscilloscope was more noisy on channel 1 than 2, maybe if nothing else because of channel 1's proximity to the DC/DC converter, which really according to it's spec sheet is a little to noisy to normally be used in a scope. Can you build a power spectrum from that signal (and crop out the 10 kHz and harmonics), and show us what the noise looks like? I can certainly say from experience if you add the shielding and caps RichardK graciously posted about you should be able to get the noise about as low as it's going to go for this device. Also, I can post the python script I use to generate power spectrums from the Hantek wave output files if that would help.


  RichardK,
I started to use your binary. Though I can tell it's still a work in progress, this looks so much better. Thanks for your hard work! :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 20, 2014, 08:19:59 pm
rpcope1,
            This was exactly my intention to follow Richardk's guide. I have just received the DSO and checked the noise and to my surprise channel 2 had no significant noise at the same settings using the Hantek software. I suspected faulty equipment and changed out probes, nothing changed. Then ran it up on Richards software and then both channels showed similar noise levels except that the noise is inverted. Tried the Hantek software and channel 1 only is noisy measuring about 4mV as per the settings in the pictures I posted. This has me stumped.
My settings are; both probes connected to the ground tag on the front panel, both probes on x1, time/Div on 50uS, both channels on 20mV. Channel 1 has noise of about 4mV and channel 2 has an occasional positive going spike of about 4mS. Channel 1 also has an occasional positive going spike, but has continuous noise as in the picture negative going.

On RichardK's software both my channels have the same continuous noise but where channel 1 is negative going, it seems as if channel 2 is positive going.

I can switch to and fro between the programs and nothing changes. The hardware is always the same......?

If anyone else can check this or even post a picture of their screen at the same settings it may help. I was prepared for noise, but with the same result for both channels.

Much appreciated.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 21, 2014, 03:32:46 am
I just did a similar measurement, the results were the same on the latest binary and stock software... It started out with less noise on CH1, but then a few minutes later the noise evened out between channels (both my version and stock software).

Considering my scope was near a window and it's 2F outside, I think it's safe to say it's thermally related and once the scope warmed up, both channels had pretty much the same noise.

Edit: The keen-eyed observer might notice something in the next build that Rick Law was asking for a few pages back ;)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 21, 2014, 07:47:10 am
I just did a similar measurement, the results were the same on the latest binary and stock software... It started out with less noise on CH1, but then a few minutes later the noise evened out between channels (both my version and stock software).

Considering my scope was near a window and it's 2F outside, I think it's safe to say it's thermally related and once the scope warmed up, both channels had pretty much the same noise.

Edit: The keen-eyed observer might notice something in the next build that Rick Law was asking for a few pages back ;)

I see it!  I see it!

Thanks Richard!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 21, 2014, 07:05:01 pm
RichardK thanks again for  this new improved version you are working on! Thanks for posting the screenshot of your noise, your Ch2 looks just like my Ch1 on the Hantek program version 1.0.3 and like both Ch1 & 2 on your binary

I can see a slight increase in noise on my Ch1 after switch on from cold (ambient temp here is 28 C today). After about 30 seconds no more increase in noise.

The interesting part with my 6022be running on the Hantek program with both probes grounded; only channel 1 is noisy, channel 2 is shows no significant noise at all, just a blip every 3 to 4 seconds.
When closing the Hantek program and opening your binary, both channels show the same noise except that they seem inverted in comparison.

My logical assumption is that this must be tied to the software in some way, as the hardware is not even changed in the slightest, I do not even switch off anything or disconnect anything. I just toggle between the two programs and the result stays the same very time. I am running both on Windows 8.

Could it be that my Channel 2 has some hardware anomaly that matches it to the software differently and thus producing an improved signal display quality erroneously or correctly?
If the two programs are doing exactly the same thing, why should there be two differing results? Channel 2 seems to be working properly, as is Channel 1 except for the noise difference.

All I recall doing since powering it up was to try and run the Calibration function and its just accepted it with no further indication at all.

Maybe I have found the holy grail! If this improvement or anomaly is  pinpointed maybe the noise problem on these could be a thing of the past! Just wishful thinking from my side!

Any inputs here will be appreciated.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 21, 2014, 09:04:43 pm

...

The interesting part with my 6022be running on the Hantek program with both probes grounded; only channel 1 is noisy, channel 2 is shows no significant noise at all, just a blip every 3 to 4 seconds.
...

Any inputs here will be appreciated.
Hi, Matchless,

Let me add some clues to this puzzle.  I have similar problem except it swaps Ch occasionally.  Often, my Ch1 has much less noise to Ch2.  Not quite down to occasional blip, just Ch1 about 1/3 to 2/3 the constant noise of Ch2.  Then, occasionally, without probe swapping, without disconnection, I turned it back on to continue prior work (ie:it is connecting back to the same circuit at the same point.), the "noise channel" reverse and Ch2 is 1/3 cleaner than Ch1.

My guess is, it is software artifact but not real.  I think packets were dropped.  Something unknown affects which channel has lower priority (got processed second? got less package?) and the trace was smoothed out rather than it being less noise.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: limpid on January 22, 2014, 08:44:38 am
Hello, anyone know bandwidth and div/v relationship for DSO6022BE?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 22, 2014, 03:38:15 pm
Hello, anyone know bandwidth and div/v relationship for DSO6022BE?

These are the sample rates for corresponding Time Divisions:
Note: They are in the exact same order as the Time/DIV Drop-down list of the stock software.

Code: [Select]
//Time Division
enum THantekTimeDivision
{
 //1016 samples
 HTTimeDiv48MS_1NS=0, //960, 1, 1
 HTTimeDiv48MS_2NS=1, //960, 1, 1
 HTTimeDiv48MS_5NS=2, //960, 1, 1
 HTTimeDiv48MS_10NS=3, //960, 1, 1
 HTTimeDiv48MS_20NS=4, //960, 1, 1
 HTTimeDiv48MS_50NS=5, //960, 1, 1
 HTTimeDiv48MS_100NS=6, //960, 1, 1
 HTTimeDiv48MS_200NS=7, //960, 1, 1
 HTTimeDiv48MS_500NS=8, //960, 1, 1
 HTTimeDiv48MS_1US=9, //960, 1, 1
 HTTimeDiv48MS_2US=10, //960, 1, 1

 //130048 samples
 HTTimeDiv16MS_5US=11, //800, 1, 1
 HTTimeDiv8MS_10US=12, //800, 1, 1
 HTTimeDiv4MS_20US=13, //800. 1, 1
 HTTimeDiv1MS_50US=14, //500, 1, 1
 HTTimeDiv1MS_100US=15, //1000, 1, 1
 HTTimeDiv1MS_200US=16, //2000, 1, 1
 HTTimeDiv1MS_500US=17, //5000, 1, 1
 HTTimeDiv1MS_1MS=18, //10000, 1, 1
 HTTimeDiv1MS_2MS=19, //20000, 1, 1

 //523264 samples
 HTTimeDiv1MS_5MS=20, //50000, 1, 1
 HTTimeDiv1MS_10MS=21, //100000, 1, 1
 HTTimeDiv1MS_20MS=22, //200000, 1, 1

 //1047552 samples
 HTTimeDiv1MS_50MS=23, //500000, 1, 1
 HTTimeDiv1MS_100MS=24, //1000000, 1, 1
 HTTimeDiv500K_200MS=25,//1000000, 1, 1
 HTTimeDiv200K_500MS=26,//1000000, 1, 1
 HTTimeDiv100K_1S=27, //1000000, 1, 1
 HTTimeDiv100K_2S=28, //2000000, 1, 1
 HTTimeDiv100K_5S=29, //5000000, 1, 1
 HTTimeDiv100K_10S=30, //10000000,1,1
 HTTimeDiv100K_20S=31, //20000000,1,1
 HTTimeDiv100K_50S=32, //50000000,1,1
 HTTimeDiv100K_100S=33, //100000000,1,1
 HTTimeDiv100K_200S=34, //200000000,1,1
 HTTimeDiv100K_500S=35, //500000000,1,1
 HTTimeDiv100K_1000S=36,//1000000000,1,1
 HTTimeDiv100K_2000S=37,//2000000000,1,1
 HTTimeDiv100K_5000S=38,//-1,1,1
};


Not sure what you mean for Voltage Divisions in respect to bandwidth, all I can tell you is the vertical resolution is limited to 256 bytes (even though the SDK uses a short).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 22, 2014, 05:00:35 pm
Hello, anyone know bandwidth and div/v relationship for DSO6022BE?

I listed them on another tread when someone else asked the exact same question:
------------------
At 50ms (1Mhz) it starts acquiring at full 1M samples (1,047,552 for each channel total 2x1047552)

At 20ms (1Mhz) it is at 523264 samples each Channel
At 10ms (1Mhz)= 523264
At 5ms (1Mhz)= 523264

At 1ms (1MHz) = 130048
At 100us (1Mhz) = 130048
At 20us (4Mhz) = 130048
At 10us (8Mhz) = 130048
At 5us (16Mhz) = 130048

At 2us (48Mhz) = 1016
Anything faster than 2us, it is still at 48MHz at 1016 samples each channel (2032 total)
------------------
Additional info since that post - only starting thinking about it recently when RichardK's program made it less painful to go slow division and find the trace (thanks, Richard):  The slowest is 100KHz.  At 1meg memory, you have max a bit over 10 seconds worth of data.  So, if you set your scope to 10sec/division, your trace will fill only a bit over 1 division and the rest of the trace-screen is blank.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: fery13013 on January 22, 2014, 11:49:15 pm
HI for everybody,

could you perhaps help me?
I have this equipment, used it with my desktop pc.It was fine.
Then I connected it to my other desktop, I checked the reference signal and it was not 1 kHz, but about 1,9 kHz ( T= 540 microsec).
Where is the problem?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 23, 2014, 04:30:07 am
HI for everybody,

could you perhaps help me?
I have this equipment, used it with my desktop pc.It was fine.
Then I connected it to my other desktop, I checked the reference signal and it was not 1 kHz, but about 1,9 kHz ( T= 540 microsec).
Where is the problem?

Repeat the whole thing first with your two PC's.  If you get the same result, try a third PC.  That will help determine what is faulty.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: fery13013 on January 23, 2014, 08:26:28 am
I repeated it and I checked both of them with a second signal, with an exact frequent also. My second pc shows me a wrong frequent.  The question is why?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: limpid on January 23, 2014, 01:42:35 pm
thanks, I ask them, they tell me below data, this is correct?

1.
V/div and bandwidth relationship for you reference as below?

Volt/div
   

Bandwidth

20mV, 50mV, 100mV
   

10MHz

200mV
   

12MHz

500mV, 1V, 2V, 5V
   

20MHz
 
2.
No attenuation, cut off voltage -+5V, attenuation 10X, -+50V.

Looks question1, it is not correct, how about with question2?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on January 23, 2014, 02:56:01 pm
thanks, I ask them, they tell me below data, this is correct?

1.  V/div and bandwidth relationship for you reference as below:

Volt/div                             Bandwidth

20mV, 50mV, 100mV         10MHz

200mV                             12MHz

500mV, 1V, 2V, 5V            20MHz
 
2.  No attenuation, cut off voltage -+5V, attenuation 10X, -+50V.

Looks question1, it is not correct, how about with question2?

Why do you think that Answer 1 is not correct?  It's fairly normal for the effective BW to drop at higher sensitivity settings.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 24, 2014, 03:13:19 pm

Let me add some clues to this puzzle.  I have similar problem except it swaps Ch occasionally.  Often, my Ch1 has much less noise to Ch2.  Not quite down to occasional blip, just Ch1 about 1/3 to 2/3 the constant noise of Ch2.  Then, occasionally, without probe swapping, without disconnection, I turned it back on to continue prior work (ie:it is connecting back to the same circuit at the same point.), the "noise channel" reverse and Ch2 is 1/3 cleaner than Ch1.

My guess is, it is software artifact but not real.  I think packets were dropped.  Something unknown affects which channel has lower priority (got processed second? got less package?) and the trace was smoothed out rather than it being less noise.

Rick

Thanks Rick, I am just going to sit tight and follow this thread. With RichardK's improved software seeing the light, I expect a lot is going to happen here over time. Many thanks for your input. Maybe soon, I will have both channels properly noisy or a miracle and both channels without noise!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 27, 2014, 07:55:17 am
Quote
The keen-eyed observer might notice something in the next build that Rick Law was asking for a few pages back ;)

I actually also prefer both channels with separate controls as in the picture of your latest PR8 version! Will check it out as soon as you make it available!
Thanks again for doing all this!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 28, 2014, 06:56:33 pm
Latest Binary: http://jmp.sh/v/GxYh8cys9Rbbf3HAlLqG (http://jmp.sh/v/GxYh8cys9Rbbf3HAlLqG)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: A_L_E_X on January 28, 2014, 07:22:37 pm
Hantek released an update of the software (1.0.4), but i haven't noticed any changes to the GUI. They must have corrected some bugs.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 28, 2014, 08:06:50 pm
Hantek released an update of the software (1.0.4), but i haven't noticed any changes to the GUI. They must have corrected some bugs.

The HTDisplayDll.dll has been updated, HTMarch.dll has not changed... I'm comparing the two Display dll's disassembled right now to see what has changed and will test the new DLL with the latest binary.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 28, 2014, 11:38:37 pm
Hantek released an update of the software (1.0.4), but i haven't noticed any changes to the GUI. They must have corrected some bugs.

The HTDisplayDll.dll has been updated, HTMarch.dll has not changed... I'm comparing the two Display dll's disassembled right now to see what has changed and will test the new DLL with the latest binary.

Alex, thanks for letting us know.

Richard, I will be loading your PR8 and test.  Thanks for your effort.

In prep for testing Richard's new release, I decided to first install Hantek's V104 so I can use it with the latest driver.  Running V104 for a brief time, these are my observations:

1. All the hardware drivers are date 1/13/2014, they are new with V104, as to whether anything is changed within, time will tell.

2. The software looks the same as v103.  But for the window's title, you would not know anything changed - most noticeable change with the UI is the splash screen's modified picture.

3. The software seem more responsive.  The trigger point on a trace seem to be more stable so jittering with the displayed trace seem less.  This is not a scientific measurement but merely by "feel".  Any improvement here is small - small enough that it could be just a low-noise day for me because I turned off something (whatever thing) that might have created lots of electrical noise.

4. RMS measurement on 103 will hang the program after a while, so far, I have not hung it yet but in that similar duration, typically, RMS would have jammed on v103.  A more extensive test will be needed before I suggest that it really had been fixed.

5. I had an unknown hung.  Not sure why. 

6. Worthy of upgrade?  Yes, it just feel more solid with the trigger.  I am not sure why because I am not sure how to quantify trigger stability yet.  The trace that used to wonder (due to changing trigger point) seem to be triggering better.

So, now that I have the new device drivers loaded, let me check out RichardK's stuff first.  RichardK's stuff is far more interesting and far more important to me than this update from Hantek so far...

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 29, 2014, 02:06:56 am
RichardK,

Thanks, this new PR8 works pretty nice.  I went from 0.01Hz to 8Mhz with random stops every decade or so.  When randomly stopped, I make the channel different frequencies or change wave shape.  I explored various options at that random stop (such as changing line-to-dot interpolation, measurement cursor, so on.  Then I go back to Ch1&Ch2 at equal frequency and move up 10x with possibly another random stop before 10x.

I noticed a few issues - but only issue 1 is a bug.  The other issues are refinements:

Issue 1:

At certain settings, Ch2 will use Ch1's position.  Look at the attached video, you will see the Ch2 trace is on top of Ch1 for a brief time, then disappear, then come back.  But looking carefully: Ch2 trace actually returned to where it should be at the bottom part of the screen.  It will stay there for a flash then go back to where Ch1 is.  The hopping around is non-stop once you get it started.
https://www.youtube.com/watch?v=9l1oj9mdqfQ&feature=youtu.be# (https://www.youtube.com/watch?v=9l1oj9mdqfQ&feature=youtu.be#)

Settings to get that issue going:
Ch1: 110KHz, triangle, +2.76v to -2.76v
Ch2: 110KHz, square, +2.00 to -2.00v
TimeScale 5uS/division
Trigger: Edge, Auto, Ch1, Rising

To Start:
The hopping around does not happen all the time.  To get it going, set it to 5uS then switch between FULL Screen and windowed partial screen, resize the screen, full screen again.  After a few tries, the hopping around will start.

To Stop:
Switch to 10uS and then back to 5uS a few times, the hopping will stop.  (Sometimes it will stop at first switching)

Also:
At 10uS, I can get the hopping going also.  At much slower speed, I can't get it to hop around.

Issue 2:

Using the scope's built-in 1KHz reference wave and with the AC coupling turned on, you see the AC-filtered wave jittering up and down a bit too much.  I think the noise is affecting the evaluated DC offset.  With the offset changing, the trace is moving up and down too much.

If I can suggest, perhaps the evaluated DC offset should be dampen a bit.  Perhaps keeping DC offset unchange unless/until the evaluated new DC offset is at least abs(X%) greater than current DC offset and minimum delta of at least 10mV.  That should make it rock solid if in fact the noise is the cause of the problem.

Issue 3:

I notice that once paused, changing the time-scale doesn't redraw the trace at the new time-scale.  Actually, I found and using time-scale changing to zoom in is easier for me.  If you think so as well, perhaps don't waste time on zooming.

Issue 4:

I miss the regular measurement window.  I can get the current peak/max/min regardless of where in the trace it would occur.  The interactive cursor measurement is very nice, I like it, but it can't do that job.

If I don't have the peak on the visible trace, I can't put the cursor there and I can't measure it.  Same for the unknown-position max and min.  If I can't put the cursor there (unknown-position), I can't measure it.

The standard measurement window does that.  Where ever it may be on the trace, I get the peak/min/max for that duration.

I hope we can keep the interactive cursor along with the old measurement window.

Lastly,

Thanks RichardK!
  This is a good release with very nice improvement...   I think Hantek should contact you and give you some add'l info or help.  Or may be even a free sets of probe or something just to show a token of appreciation.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 29, 2014, 02:34:50 am
Issue 1:

At certain settings, Ch2 will use Ch1's position.  Look at the attached video, you will see the Ch2 trace is on top of Ch1 for a brief time, then disappear, then come back.  But looking carefully: Ch2 trace actually returned to where it should be at the bottom part of the screen.  It will stay there for a flash then go back to where Ch1 is.  The hopping around is non-stop once you get it started.
https://www.youtube.com/watch?v=9l1oj9mdqfQ&feature=youtu.be# (https://www.youtube.com/watch?v=9l1oj9mdqfQ&feature=youtu.be#)

Settings to get that issue going:
Ch1: 110KHz, triangle, +2.76v to -2.76v
Ch2: 110KHz, square, +2.00 to -2.00v
TimeScale 5uS/division
Trigger: Edge, Auto, Ch1, Rising

To Start:
The hopping around does not happen all the time.  To get it going, set it to 5uS then switch between FULL Screen and windowed partial screen, resize the screen, full screen again.  After a few tries, the hopping around will start.

To Stop:
Switch to 10uS and then back to 5uS a few times, the hopping will stop.  (Sometimes it will stop at first switching)

Also:
At 10uS, I can get the hopping going also.  At much slower speed, I can't get it to hop around.

I'm aware of this issue, not sure what's causing it yet, but I'll fix it eventually :)

Quote
Issue 2:

Using the scope's built-in 1KHz reference wave and with the AC coupling turned on, you see the AC-filtered wave jittering up and down a bit too much.  I think the noise is affecting the evaluated DC offset.  With the offset changing, the trace is moving up and down too much.

If I can suggest, perhaps the evaluated DC offset should be dampen a bit.  Perhaps keeping DC offset unchange unless/until the evaluated new DC offset is at least abs(X%) greater than current DC offset and minimum delta of at least 10mV.  That should make it rock solid if in fact the noise is the cause of the problem.

Also aware of this, I think it has to do with the AC coupling taking time to take effect and the wave being drawn before it's done.

Quote
Issue 3:

I notice that once paused, changing the time-scale doesn't redraw the trace at the new time-scale.  Actually, I found and using time-scale changing to zoom in is easier for me.  If you think so as well, perhaps don't waste time on zooming.

Probably due to incomplete nature of the code, but will look into it to verify it's not a bug.

Quote
Issue 4:

I miss the regular measurement window.  I can get the current peak/max/min regardless of where in the trace it would occur.  The interactive cursor measurement is very nice, I like it, but it can't do that job.

If I don't have the peak on the visible trace, I can't put the cursor there and I can't measure it.  Same for the unknown-position max and min.  If I can't put the cursor there (unknown-position), I can't measure it.

The standard measurement window does that.  Where ever it may be on the trace, I get the peak/min/max for that duration.

I hope we can keep the interactive cursor along with the old measurement window.

I plan on having measurement capabilities (similar to the stock feature) but have not implemented it yet, so eventually all of them will available.

Thanks for the feedback :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 29, 2014, 07:15:19 am
Latest Binary: http://jmp.sh/v/GxYh8cys9Rbbf3HAlLqG (http://jmp.sh/v/GxYh8cys9Rbbf3HAlLqG)

What's New:
-----------------------------------------------------------
1. Fixed a bug where channel's might "jump" up and down at random.
2. Fixed a bug where AC Coupled or Inverted channels would jump around, especially when
   dragging waveforms.
3. Fixed a bug where waveforms would sometimes not update when changing Timebases.
4. Fixed a crash on close when Cursors enabled.
5. Fixed a bug where the Wave Context would sometimes not update properly when changing
   Timebases.
6. Included Latest Hantek SDK DLL: HTDisplayDLL.dll

Edit: Rick, hopefully this fixes most of the issues you brought up earlier.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 29, 2014, 03:21:27 pm
RichardK, thanks for this. Unfortunately I could not compare with the latest Hantek 1.0.4 as their website is down.
Just some feedback that may help on your project:
My issue with no noise on channel two on the Hantek software and the usual noise on both channels on your software is still there. If I run the Calibration utility on yours it reminds me to ground the probes and then fails, and then the noise on my channel 2 goes away! Channel 1 stays the same. Now my result looks the same as on the Hantek software.
Running the calibration on the Hantec does not come back with either a failure or a complete and nothing changes. I assume the calibration feature is not working there.

Thanks again.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 29, 2014, 06:26:06 pm
RichardK,
Thank!  I will give it a go later today.



RichardK, thanks for this. Unfortunately I could not compare with the latest Hantek 1.0.4 as their website is down.
Just some feedback that may help on your project:
My issue with no noise on channel two on the Hantek software and the usual noise on both channels on your software is still there. If I run the Calibration utility on yours it reminds me to ground the probes and then fails, and then the noise on my channel 2 goes away! Channel 1 stays the same. Now my result looks the same as on the Hantek software.
Running the calibration on the Hantec does not come back with either a failure or a complete and nothing changes. I assume the calibration feature is not working there.

Thanks again.
Matchless,

As I posted earlier, I have that problem occasionally at a lesser degree.  One channel being noticeably less noise than the other - and mine swaps.  I believe it to be a software artifact instead of real.  It is practically impossible for any signal to be totally noise free.  If you are seeing NO noise on Ch2 at all, I think you have a problem not related to RichardK's software.

If noise shows with RichardK's software, and the stock doesn't, it make me think may be the display setting.  The stock software restore last setting on start up - so if the last setting is wrong, it stays wrong.  RichardK's software doesn't restore last setting, so you are forced to change and that just may get it to the right setting.

Check and see if you make the same mistake I made often when I was new with the scope: Volt/div and probe 1x/10x setting.  The mistake was setting the V/div too low and/or not matching that of 1x/10x problem.

Example of setting mistake:
using the scope's reference wave - Square +2V @ 1KHz.
1ms/div, Ch1 at 1V and Ch2 at 500mV.

Ch1 at 1V will show with noise
Ch2 (top part) will show little or no noise

Photo 1 - shows no noise on Ch2 when square wave is high

(https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/?action=dlattach;attach=79058;image)
That is because at 500mV, it cuts off before when the trace when it reaches +-4 divisions = +-2V.   With the reference wave square high part being 2V, anything above 2V is clipped and the scope trace flat-lined.

Due to parts' tolerance, 2V is not exactly 2V.  You see 2.02V in the photo.  In any case, with anything over 2V clipped, positive noise is clipped.  So it would appear as if it is much less noise.

One can imagine, for a square wave @ +-2V (instead of just +2V), both high volt and low volt noises are gone so it looks as if Ch2 has no noise at all.

Photo 2 - Proper setting for both

(https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/?action=dlattach;attach=79060;image)
If I set Ch2 at 1V/division (as with Ch1), now it wont clip and Ch2 noise is shown in full.  In fact, Ch2 has more noise than Ch1 when settings allow it to show instead of clipping it off.

These two photo was taken back-to-back, so practically at the same time.  With the stock software, it restores the last setting on open, so until I notice it and change it, it would always looks as if Ch2 has less noise than Ch1 in this scenario - but in fact Ch2 is more noise than Ch1 when proper setting is chosen.

Hope this helps...

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 30, 2014, 12:23:28 am
Latest Binary: http://jmp.sh/v/GxYh8cys9Rbbf3HAlLqG (http://jmp.sh/v/GxYh8cys9Rbbf3HAlLqG)

What's New:
-----------------------------------------------------------
1. Fixed a bug where channel's might "jump" up and down at random.
2. Fixed a bug where AC Coupled or Inverted channels would jump around, especially when
   dragging waveforms.
3. Fixed a bug where waveforms would sometimes not update when changing Timebases.
4. Fixed a crash on close when Cursors enabled.
5. Fixed a bug where the Wave Context would sometimes not update properly when changing
   Timebases.
6. Included Latest Hantek SDK DLL: HTDisplayDLL.dll

Edit: Rick, hopefully this fixes most of the issues you brought up earlier.

RichardK,

First, I hope I am not acting in a way that appears to be "just being critical".  I am unable to contribute by helping with programming, so I am trying to contribute by do doing testing to hope to lighten your load.

So, if I sound critical, tell me to bug-off...

I did a run down on the latest PR9.  I can confirm all 4 issues I brought up are addressed and resolved.

On "issue #2" (trace jitters using software AC coupling), I can see there was great improvement.  There is still some slight jitters, but the blinking (trace disappear momentary) is largely gone.  The "gone dark" is much shorten when it does happen.  (The time when the blink, that brief duration of the momentary screen-with-trace.  Both the frequency of blink and duration of blink are improved.  It is not disruptive anymore as it was with PR8.

I think the AC coupling is one of the best features of your software.  It may be worthwhile to make this the show-piece.  The "gone dark" is so short it is barely noticeable.  The slight up/down jitter that is left, if it can be slow down a bit more, this is the show piece.

New Bug:
When in AC coupling mode, interactive cursor doesn't work (not on the trace).
To reproduce:
Use the scope's references 1KHz wave
Ch1 & Ch2 are both 2V/div
time scale at 500uS
Ch1 on AC coupling
Turn on cursor - Ch1 cursor riding on air (not on trace) where as Ch2 (not AC coupling) is on the trace.  Both seem to measures fine.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 30, 2014, 02:51:34 am
First, I hope I am not acting in a way that appears to be "just being critical".  I am unable to contribute by helping with programming, so I am trying to contribute by do doing testing to hope to lighten your load.

So, if I sound critical, tell me to bug-off...

Absolutely not, while I don't look forward to hearing about bugs, it's important that they be known so they can be fixed, and I am very appreciative of all feedback, even feedback that is critical or reveals bugs. Thanks for helping out with testing, it's hard enough finding the time to work on it with my busy life, so testing tends to take a back seat to coding.

Quote
I did a run down on the latest PR9.  I can confirm all 4 issues I brought up are addressed and resolved.

On "issue #2" (trace jitters using software AC coupling), I can see there was great improvement.  There is still some slight jitters, but the blinking (trace disappear momentary) is largely gone.  The "gone dark" is much shorten when it does happen.  (The time when the blink, that brief duration of the momentary screen-with-trace.  Both the frequency of blink and duration of blink are improved.  It is not disruptive anymore as it was with PR8.

I think the AC coupling is one of the best features of your software.  It may be worthwhile to make this the show-piece.  The "gone dark" is so short it is barely noticeable.  The slight up/down jitter that is left, if it can be slow down a bit more, this is the show piece.

I ended up having to use double buffering due to race conditions between the render and acquire threads, and I also still get the odd wobble now and then and I am perplexed as to what is causing it, I thought the double buffering would be the final nail in the coffin, apparently I have to bury the casket as well  :-\

Quote
New Bug:
When in AC coupling mode, interactive cursor doesn't work (not on the trace).
To reproduce:
Use the scope's references 1KHz wave
Ch1 & Ch2 are both 2V/div
time scale at 500uS
Ch1 on AC coupling
Turn on cursor - Ch1 cursor riding on air (not on trace) where as Ch2 (not AC coupling) is on the trace.  Both seem to measures fine.

Whoops, that's Mybad, I forgot to move some code back down to where it belongs while testing a previous fix... Easy fix, will be gone in the next binary.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 30, 2014, 10:42:47 am
According to scope's specs the max input voltage in x10 probe mode is 350V. If I want to double that can I just insert another 9-10MOhm resistor between the probe and scope's input and should I compensate it with an adjustable capacitor?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 30, 2014, 05:01:33 pm
Hi Rick,
           Thanks for the detailed reply and examples. I really appreciate the effort you are putting in to help me.
I have had the settings on both channels the same as that alerted me to this discrepancy, as I would expect both channels to be just about similar on the same test and settings.
My test was for base noise with both probes on X1 and connected to the ground tag of the 6022.
I have added some screen shots to compare the Hantek 1.0.3 program with RichardK's latest binary. To me both results should be the similar.
You can clearly see the settings in each screenshot:
The pictures marked 1, 2, 3 are on the Hantek SW and marked 1R, 2R, 3R are on RichardKs SW.
Only capture1 shows the noise missing on channel 2 :-//
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on January 30, 2014, 07:22:53 pm
I have had the settings on both channels the same as that alerted me to this discrepancy, as I would expect both channels to be just about similar on the same test and settings.
My test was for base noise with both probes on X1 and connected to the ground tag of the 6022.
I have added some screen shots to compare the Hantek 1.0.3 program with RichardK's latest binary. To me both results should be the similar.
You can clearly see the settings in each screenshot:
The pictures marked 1, 2, 3 are on the Hantek SW and marked 1R, 2R, 3R are on RichardKs SW.
Only capture1 shows the noise missing on channel 2 :-//

Good job on the 3 comparisons.  I think they show the problem very clearly.

That said, IMO you're asking the wrong person for an explanation.  Your Hantek 2 & 3 shots show there's definitely noise on Chan2.  Yet when you zoom in by selecting a more sensitive vertical setting, instead of seeing that noise in more detail, it completely disappears!  Since Richard's software is working, and Hantek's software is obviously NOT working properly, you should be asking Hantek why their software is broken. 

Asking Richard to explain why someone else's software doesn't work is a waste of everyone's time.  Your efforts have isolated the problem to one range of Hantek's software.  File a bug report with them.  See if you get a fix in 1 day, as Richard has been regularly doing.  ;)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 30, 2014, 09:05:00 pm
Mark_O,
             Thanks for your reply. A logical deduction is that it cannot really be a hardware issue, as then it would show up on RichardK's software as well. Another logical deduction is, if it is a software issue it should show up on other peoples 6022be's as well. The fact is that it is happening in the same way every time and is not intermittent. Thus to reproduce this behaviour, I think I was not clear enough in my original post. Hopefully more people will try it now and come back.
I will gladly file a bug report with Hantek once I can confirm this is a problem experienced on more 6022's than mine.

From what I have seen and read to date, I have more faith in RichardK putting together a better software solution than in Hantek solving issues like this on the 6022be! As such I did not intend RichardK to find a solution for mine (as he already has in his binary), but just in case this helps him with his project.
This not a real problem for me, but more a peculiarity that must have some definite explanation or reason.

I really appreciate the time you have taken to look at my issue and replying to it. I also apologize if my posts on this is a waste of everyone's time.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on January 30, 2014, 10:30:45 pm
A logical deduction is that it cannot really be a hardware issue, as then it would show up on RichardK's software as well. Another logical deduction is, if it is a software issue it should show up on other peoples 6022be's as well. The fact is that it is happening in the same way every time and is not intermittent. Thus to reproduce this behaviour, I think I was not clear enough in my original post. Hopefully more people will try it now and come back.

Yes, that would be good.

Quote
I also apologize if my posts on this is a waste of everyone's time.

Well, my apologies to you, if this came off harsher than I intended.   :-[  It's always worth the time to point out problems, anomalies, and misbehavior.  Everyone benefits from that.  At some point though, diminishing returns kick in.  I felt that had been achieved, and the issue had been sufficiently identified.  And it was your posted tests that accomplished that.  So I appreciate your taking the time to make those contributions.
Title: Re: Re: Hantek 6022BE 20MHz USB DSO
Post by: larry42 on January 30, 2014, 10:40:16 pm
According to scope's specs the max input voltage in x10 probe mode is 350V. If I want to double that can I just insert another 9-10MOhm resistor between the probe and scope's input and should I compensate it with an adjustable capacitor?

If you're asking that question then maybe you shouldn't be measuring above 350V... :) NB most resistors are not rated above 500 volts breakdown voltage and SMD ones are rated at much lower voltages...

Sent from my One S using Tapatalk

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on January 30, 2014, 10:46:05 pm
The fact is that it is happening in the same way every time and is not intermittent. Thus to reproduce this behaviour, I think I was not clear enough in my original post.

BTW, one other thing you could try, if you were interested in exploring the Hantek problem a bit, would be to take a low amplitude sine source and split it, thus feeding the same signal into both inputs.  Using the Hantek software, on the 20mV/div range.

Slowly raise the sine amplitude from ~1mV to ~20mV.  I.e., starting below the noise threshold.  And see at what point you get a reasonable reading on each channel.  And when you hit 1div on the "good" channel, do you also on the "abnormal" channel.  That way you could tell if signals below a certain threshold were being clamped, or if it's just being level shifted down, to the point where it's not visible.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 31, 2014, 03:22:39 am
Matchless,

First, you are welcome.  I received so much help is it only fair I return a favor on the few things that I know.

I agree with Mark_O.  The screen print you posted shows a clear software problem with your hantek software.

With the Hantek software screen prints, when you look closely at your 1V/div (and other except the 20mV), you can clearly see Ch2 wiggling just like Ch1.  That means that Ch2 is reading noise or otherwise it would have been a flat line.

As to why it fails to show at 20mV, I think it is your install rather than the software (edit) a combination of what you have and the Hantek stuff (end of reedit).  The Hantek software is prone to all kinds of issues, but your install so far is the only one reporting that.  So it could be something you have that Hantek software doesn't like.

With V104 already out, why not try a clean install.  If you want to chase down a problem, at least do it with the latest version.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 31, 2014, 06:34:04 am
Mark_O and Rick,
                           Thanks for your replies and advice to date. Unfortunately the Hantek website has been down for 3 days now and will most likely only be up again after the Chinese new year celebrations it seems. My next test is to try this with their latest 1.0.4 version once I can download it. Hopefully the driver is also new. By the way I am running these on Windows 8. I can also try running on Windows 7.

I am leaning towards the suggestion that it may be a combination of my installation and the software and have reinstalled it a couple of times, but nothing has changed. More tests here need to be done yet.

I will be away for a couple of days and on return will try the newer version, Mark_O's suggestion and install on Win7 as well.

Could I possibly ask anyone else to post their results and mention which OS their PC's are running?

Just a thanks again for the interest and inputs from your side.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on January 31, 2014, 07:20:38 am
                           Thanks for your replies and advice to date. Unfortunately the Hantek website has been down for 3 days now and will most likely only be up again after the Chinese new year celebrations it seems. My next test is to try this with their latest 1.0.4 version once I can download it. Hopefully the driver is also new. By the way I am running these on Windows 8. I can also try running on Windows 7.

I already downloaded the latest version from their website before it went down (Probably due to excessive traffic) and uploaded it to my Jumpshare account.

http://jmp.sh/v/xhBbrWPkvVEsYQomHCzs (http://jmp.sh/v/xhBbrWPkvVEsYQomHCzs)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on January 31, 2014, 07:47:47 am
Mark_O and Rick,
                           Thanks for your replies and advice to date. Unfortunately the Hantek website has been down for 3 days now and will most likely only be up again after the Chinese new year celebrations it seems. My next test is to try this with their latest 1.0.4 version once I can download it. Hopefully the driver is also new. By the way I am running these on Windows 8. I can also try running on Windows 7.

I am leaning towards the suggestion that it may be a combination of my installation and the software and have reinstalled it a couple of times, but nothing has changed. More tests here need to be done yet.

I will be away for a couple of days and on return will try the newer version, Mark_O's suggestion and install on Win7 as well.

Could I possibly ask anyone else to post their results and mention which OS their PC's are running?

Just a thanks again for the interest and inputs from your side.

Matchless,

I could have swore I wrote and saved this reply 20 minutes ago...   Anyhow here goes again:

The drivers in V104 are all dated this year, so I assume they are new builds.  As to what changed if any, only Hantek knows.

I use the scope software on multiple machines.  They are all WinXP, two with SP3 and one with SP2.  Hantek's 6022be software works well on all three machines.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on January 31, 2014, 10:17:12 am
Quote
If you're asking that question then maybe you shouldn't be measuring above 350V... :) NB most resistors are not rated above 500 volts breakdown voltage and SMD ones are rated at much lower voltages...

Getting high voltage high value resistors is not a problem. The question is whether my "concept" for doubling the input voltage is right or I'm missing something? I was planning of building a simple BNC to BNC adapter with the additional resistor and eventually capacitor inside.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on January 31, 2014, 07:15:41 pm

I already downloaded the latest version from their website before it went down (Probably due to excessive traffic) and uploaded it to my Jumpshare account.

http://jmp.sh/v/xhBbrWPkvVEsYQomHCzs (http://jmp.sh/v/xhBbrWPkvVEsYQomHCzs)

Thanks Richard. I had a quick look at it, will play with it a bit when I am back home next week. I think its Chinese new year there and nothing will happen until the festivities are over!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on February 01, 2014, 11:35:50 am
Couple of screenshots comparing Hantek and OpenHantek software:

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 02, 2014, 02:55:37 am
Couple of screenshots comparing Hantek and OpenHantek software:

Merlyn, look at Chan2 on the Hantek software.  It's 20mV/div, and clearly the Vpp on screen is 1/5 of a div, or 4 mV.  Yet in the Status area below (Output window), claims the Vpp is 8.16 mV.  ???  That's some mighty fine software there.

The noise density is much higher on Chan2, but that doesn't (shouldn't) affect the Vpp at all.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on February 02, 2014, 09:45:41 am
Yeah, I noticed that too. Maybe it will produce wrong readings at the noise level. I'll try with higher amplitude signals and see what's going on.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 02, 2014, 05:14:03 pm
Couple of screenshots comparing Hantek and OpenHantek software:

Merlyn, look at Chan2 on the Hantek software.  It's 20mV/div, and clearly the Vpp on screen is 1/5 of a div, or 4 mV.  Yet in the Status area below (Output window), claims the Vpp is 8.16 mV.  ???  That's some mighty fine software there.

The noise density is much higher on Chan2, but that doesn't (shouldn't) affect the Vpp at all.

Yeah, I noticed that too. Maybe it will produce wrong readings at the noise level. I'll try with higher amplitude signals and see what's going on.


Mark_O, Merlyn,

re: ...Yet in the Status area below (Output window), claims the Vpp is 8.16 mV.  ??? That's some mighty fine software there....

I am not sure I agree that it is a software problem for this one.  At 50uS, the scope is collecting at 1Mhz (1uS/datapoint) for 130048 datapoints.  That is 130milliSecond worth of data.

But the display is 50uS/division which equals 500uS per screen full of data.  The 130048 data points (130.048mS) equals 260 screenfull of data.  So somewhere in the not-on-screen but collected data may be the higher 8.16 mV peak.

Often, I have to scroll my screen left or right to find the peak that is not on the current screen display.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 02, 2014, 09:17:00 pm
I am not sure I agree that it is a software problem for this one.  At 50uS, the scope is collecting at 1Mhz (1uS/datapoint) for 130048 datapoints.  That is 130milliSecond worth of data.

But the display is 50uS/division which equals 500uS per screen full of data.  The 130048 data points (130.048mS) equals 260 screenfull of data.  So somewhere in the not-on-screen but collected data may be the higher 8.16 mV peak.

Often, I have to scroll my screen left or right to find the peak that is not on the current screen display.

Rick, thanks for pointing this out!  I agree that it's certainly possible the Vpp  captured could have been the 8mV reported, if there are 260 screens worth of data acquired.

OTOH, I think if we're only seeing <0.4% of the data (a very tiny drop in the bucket), there should be some indication of that, on-screen.  Not to mention the (already discussed) painful process of trying to scroll through those 260 screenfuls of data.

And not only is there no such indication, once one does start scrolling, I see absolutely no way to know where one is in that 130,000 sample acquisition.  So if you did eventually stumble across that 8mV peak (before you died of old age while scrolling), you'd have no idea where (in time) it occurred.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 03, 2014, 03:54:20 am
I am not sure I agree that it is a software problem for this one.  At 50uS, the scope is collecting at 1Mhz (1uS/datapoint) for 130048 datapoints.  That is 130milliSecond worth of data.

But the display is 50uS/division which equals 500uS per screen full of data.  The 130048 data points (130.048mS) equals 260 screenfull of data.  So somewhere in the not-on-screen but collected data may be the higher 8.16 mV peak.

Often, I have to scroll my screen left or right to find the peak that is not on the current screen display.

Rick, thanks for pointing this out!  I agree that it's certainly possible the Vpp  captured could have been the 8mV reported, if there are 260 screens worth of data acquired.

OTOH, I think if we're only seeing <0.4% of the data (a very tiny drop in the bucket), there should be some indication of that, on-screen.  Not to mention the (already discussed) painful process of trying to scroll through those 260 screenfuls of data.

And not only is there no such indication, once one does start scrolling, I see absolutely no way to know where one is in that 130,000 sample acquisition.  So if you did eventually stumble across that 8mV peak (before you died of old age while scrolling), you'd have no idea where (in time) it occurred.

re: (the bold text part)

That is exactly where I think RichardK's program shines.  He has that mini wave form (the saw tooth at the top and middle of the screen), the T  above the mini-wave allows you to scroll and points at the present position relative to the start of the collected datapoints.

Second thing is, I am not sure (plain just forgot) if it does now, but it could show with part of the mini-wave in different color representing where the current screen is relative to the whole set of collected data.

Richard's program allows rapid scrolling to specific areas.  Finding the right area to look at will still be a human task.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 03, 2014, 04:06:24 am
Second thing is, I am not sure (plain just forgot) if it does now, but it could show with part of the mini-wave in different color representing where the current screen is relative to the whole set of collected data.

Stock software doesn't do this, however the other models stock software does have this feature (which is where I got the idea from and improved upon it).

Btw, I'll be uploading the latest binary in the next day or so which does away with the Zoom warning because I have implemented proper scaling of Interactive and Line cursors when zoomed in or out, and also when looking at stopped waveforms on timebases that are different from the stopped timebase. I noticed that Hantek uses the Horizontal Zoom parameter of the Draw Wave SDK function to simulate different Timebases on Stopped waveforms without reacquiring raw data (which wouldn't be proper anyway).

So the next binary should have dramatic improvements in Zooming (active waveforms or stopped waveforms).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 04, 2014, 12:24:35 am
Latest Binary: http://jmp.sh/v/TpJwJVuWFtNDFZJMovL8 (http://jmp.sh/v/TpJwJVuWFtNDFZJMovL8)

What's New:
-----------------------------------------------------------
1. Fixed a bug where Interactive Cursors out of sync with AC Coupled waveforms.
2. Full support for viewing stopped waveforms at different timebases and voltage divisions.
3. Cursors now work on Zoomed waveforms .
4. Removed Scale warning for zoomed waveforms (Proper scaling now implemented).
5. Added Reset Zoom menu item and Toolbar Button.
6. Added Fullscreen, Hide Toolbar and Hide Sidebar buttons to Toolbar.
7. Moved Start & Stop acquire buttons closer to the left side of the Toolbar.
8. Various other bugs fixed, performance improvements, code cleanup.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Plummerman on February 04, 2014, 02:16:46 am
Hello Rick,

      I just joined this forum and see that folks are evidently writing software for the HANTEK PC Oscilloscope...  this is encouraging.

      I have a HANTEK 6022BE and want to download the trace data.  So far, I've been successful (sort of) at getting the comma separated variable file... the problem is that there's so much data that it overwhelms my spreadsheet (Open Office Calc).  It appears that every sample is exported.... I've used network analyzers, spectrum analyzers, and other scopes with similarly high sample rates; however the downloaded data is much, much less, like 3K data points instead of 500K - some models have allowed me to set the number of data points (AGILENT for example).  Another problem is that the corresponding x-axis data (time scale) is not exported.  Furthermore, the trace data appears all in the same columns (making extremely long columns) rather than appearing in sequential columns.  I could move this around... except the spreadsheet program tends to choke on the large data set... so forget using a formula to calculate the time base...  This is a problem for me, because I've retired an no longer have access to all the wonderfully expensive equipment I once did.  So... have any of my issues been addressed with software, OEM, or after-market?  Where could I find more information on it?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 04, 2014, 04:10:25 am
Latest Binary: http://jmp.sh/v/TpJwJVuWFtNDFZJMovL8 (http://jmp.sh/v/TpJwJVuWFtNDFZJMovL8)

What's New:
-----------------------------------------------------------
1. Fixed a bug where Interactive Cursors out of sync with AC Coupled waveforms.
2. Full support for viewing stopped waveforms at different timebases and voltage divisions.
3. Cursors now work on Zoomed waveforms .
4. Removed Scale warning for zoomed waveforms (Proper scaling now implemented).
5. Added Reset Zoom menu item and Toolbar Button.
6. Added Fullscreen, Hide Toolbar and Hide Sidebar buttons to Toolbar.
7. Moved Start & Stop acquire buttons closer to the left side of the Toolbar.
8. Various other bugs fixed, performance improvements, code cleanup.

Thanks RichardK!  I will look forward to testing it tomorrow.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 04, 2014, 04:48:16 am
Hello Rick,

      I just joined this forum and see that folks are evidently writing software for the HANTEK PC Oscilloscope...  this is encouraging.

      I have a HANTEK 6022BE and want to download the trace data.  So far, I've been successful (sort of) at getting the comma separated variable file... the problem is that there's so much data that it overwhelms my spreadsheet (Open Office Calc).  It appears that every sample is exported.... I've used network analyzers, spectrum analyzers, and other scopes with similarly high sample rates; however the downloaded data is much, much less, like 3K data points instead of 500K - some models have allowed me to set the number of data points (AGILENT for example).  Another problem is that the corresponding x-axis data (time scale) is not exported.  Furthermore, the trace data appears all in the same columns (making extremely long columns) rather than appearing in sequential columns.  I could move this around... except the spreadsheet program tends to choke on the large data set... so forget using a formula to calculate the time base...  This is a problem for me, because I've retired an no longer have access to all the wonderfully expensive equipment I once did.  So... have any of my issues been addressed with software, OEM, or after-market?  Where could I find more information on it?

Plummerman,

The number of data points collected is entirely controlled by time per division.  Once you set time per division (say 10nS/div), that setting alone will dictate the sampling speed and number of data points collected.

Look at a few pages, you will see a reply containing time/div verses data points and sample speed that I posted.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Plummerman on February 04, 2014, 08:27:42 am
Hello Rick,

     Thanks for the prompt reply.  My application is for calibrating small wind turbines (< 3kW) output characteristics.  BTW, I have X100 probes because the output voltage in the operating regions is 50V to 300V.  At any rate, the time per division is on the order of milliseconds, which at a 48MSa/sec would yield 1 million samples or more for 10 divisions (1 screen).  As I recall on my first test runs,  I was capturing something less than this (130k data points or more), so it would seem the scope software was adjusting the sample rate somehow.... but that's still way, way, too much (way over-sampled).  Does the OpenHantek software have a more intelligent control over the sample rate than the OEM software?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 04, 2014, 11:27:09 am
RichardK, you are doing outstanding work on this!
I played with that Zoom function a bit and it is really looking very nice.

Please just ignore these questions if they are irrelevant:

Do you intend activating the Calibration function at a later stage?
Is it possible to change the 3 large rotary knobs to a better HD that looks more "quality" in line with your software?
Is it possible or bad practice to allow for clicking on the relevant rotary knob to activate the mouse scroll wheel, where at the moment one has to click the drop down box voltage?

Thanks again for what you are doing! :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on February 04, 2014, 11:51:12 am
Richard is doing amazing work with the code so I suggest that we do the modified UI elements so he won't have to.
If you send me some photos of desired buttons I can draw them in Inkscape and upload here.
So Richard would only have to replace the original files...

I have already found one nice button (the big one on the top):
(http://cdn7.us.yokogawa.com/uploaded/DL9000_press_high_res_LG.jpg)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on February 04, 2014, 11:53:53 am
I have now noticed that the buttons in the software are not images but coded graphic elements (circles, dots) so change to rotating image would not be so trivial...
IMHO it's best to wait with UI changes (or requests) until the software is completely done...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 04, 2014, 12:44:09 pm
Hi frenky,
              I agree that cosmetics are low on the list for sure, but once the software is complete and working,  that will definitely also make it look good as well!
Unfortunately that is not my field at all, so there is not much that I can contribute to this except some ideas.
I hope I am not breaking any rule, but here is a PCscope with a very good looking GUI and this sort of caused me to ask about the rotary knobs:
xxx.zeitnitz.de/Christian/scope_en   (xxx = www)
Thanks for your offer!

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 04, 2014, 05:44:58 pm
Hello Rick,

     Thanks for the prompt reply.  My application is for calibrating small wind turbines (< 3kW) output characteristics.  BTW, I have X100 probes because the output voltage in the operating regions is 50V to 300V.  At any rate, the time per division is on the order of milliseconds, which at a 48MSa/sec would yield 1 million samples or more for 10 divisions (1 screen).  As I recall on my first test runs,  I was capturing something less than this (130k data points or more), so it would seem the scope software was adjusting the sample rate somehow.... but that's still way, way, too much (way over-sampled).  Does the OpenHantek software have a more intelligent control over the sample rate than the OEM software?
Plummerman,

Hantek software (and perhaps hardware) for 6022 capture rates and capture size are automatically set by your time-per-division.  It has not other way of controlling it.

If you want 48MHz capture rate, the most you are going to capture is 1016 data points.
For 1M data points, you have to slow down to 50ms/div. See this table that I put together:
------------------
At 50ms (1Mhz) it starts acquiring at full 1M samples (1,047,552 for each channel total 2x1047552)

At 20ms (1Mhz) it is at 523264 samples each Channel
At 10ms (1Mhz)= 523264
At 5ms (1Mhz)= 523264

At 1ms (1MHz) = 130048
At 100us (1Mhz) = 130048
At 20us (4Mhz) = 130048
At 10us (8Mhz) = 130048
At 5us (16Mhz) = 130048

At 2us (48Mhz) = 1016
Anything faster than 2us, it is still at 48MHz at 1016 samples each channel (2032 total)
------------------

So, your signal determines what minimum capture rate you need.  You said your signal is in the 50-500v range, but that doesn't say how fast you want/need to observe it.

Since you are setting it "in the order of mS/division", I assume that is the range you are observing the characteristic you want to see.  In that range, you are pretty much 130048 points.  You can adjust the sampling rate (see table above) but not the length until you go down to 2uS for 1016 points.

However, if at that time-per-division is fast enough but you capture more than you need, you can trim the data with a quick and dirty program.  If you need more capture data than the scope is capable of (at your needed minimum capture rate), than it would be time for another scope.

Hope this helps.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 04, 2014, 06:15:55 pm
Do you intend activating the Calibration function at a later stage?

It has been implemented for quite some time.

Quote
Is it possible to change the 3 large rotary knobs to a better HD that looks more "quality" in line with your software?

Anything is possible, but right now I'm focusing on getting core features implemented. I don't see it being very hard to replace the generic knobs with color coded graphical ones, but at a later date.

Quote
Is it possible or bad practice to allow for clicking on the relevant rotary knob to activate the mouse scroll wheel, where at the moment one has to click the drop down box voltage?

I'll look into this, but it's low priority for the moment as I'm trying to get Measurements implemented now... Thanks for the suggestions though, all are appreciated.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 04, 2014, 06:55:23 pm
RichardK,
              Thanks, I must have missed that. At the moment if I run Calibration on the Hantek software it executes with no further feedback at all. If I run it on Open 6022be it executes and then gives Cannot calibrate: Calibration failed.
I may have missed something. Is there any specific steps to follow, except having it on for a while and having the probes connected to ground?
Thanks
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 04, 2014, 07:36:25 pm
RichardK,
              Thanks, I must have missed that. At the moment if I run Calibration on the Hantek software it executes with no further feedback at all. If I run it on Open 6022be it executes and then gives Cannot calibrate: Calibration failed.
I may have missed something. Is there any specific steps to follow, except having it on for a while and having the probes connected to ground?
Thanks

I followed the SDK on Calibration, but the SDK documentation might be wrong or there could be a bug in my code, I'll check it out.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 04, 2014, 09:58:01 pm
RichardK,
              Thanks, I must have missed that. At the moment if I run Calibration on the Hantek software it executes with no further feedback at all. If I run it on Open 6022be it executes and then gives Cannot calibrate: Calibration failed.
I may have missed something. Is there any specific steps to follow, except having it on for a while and having the probes connected to ground?
Thanks

Matchless ,

I cannot reproduce your issue -- I think you might have forgot to ground the probes first.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 05, 2014, 12:11:05 am
Latest Binary: http://jmp.sh/v/TpJwJVuWFtNDFZJMovL8 (http://jmp.sh/v/TpJwJVuWFtNDFZJMovL8)

What's New:
-----------------------------------------------------------
1. Fixed a bug where Interactive Cursors out of sync with AC Coupled waveforms.
2. Full support for viewing stopped waveforms at different timebases and voltage divisions.
3. Cursors now work on Zoomed waveforms .
4. Removed Scale warning for zoomed waveforms (Proper scaling now implemented).
5. Added Reset Zoom menu item and Toolbar Button.
6. Added Fullscreen, Hide Toolbar and Hide Sidebar buttons to Toolbar.
7. Moved Start & Stop acquire buttons closer to the left side of the Toolbar.
8. Various other bugs fixed, performance improvements, code cleanup.

RichardK,

All the above fixed were tested without problem.  Three minor issue plus a suggestion:

Issue 1: When trigger is not triggered, confusing wave form...

This bug is on NORMAL trigger and doesn't show in automatic trigger.   In earlier release, you said only automatic trigger is working. I'm not sure that NORMAL trigger is "done" or work in progress.  Anyhow, you want to know this anyway.

When trigger point is not within wave-range, the waves are still shown but deformed.  The volt displayed is inaccurate.  (Stock software draws nothing when trigger point is not within wave-range, so it would not be misleading or confusing.)

It may be best to remove the visible trace so as it would not be confusing when normal trigger is not triggered.

To see the confusing trace:
1 use scope’s build-in reference
2 time=1ms/div
3 volt ch1 2v/div
4 volt ch2 1v/div
5 Trigger Edge/Normal/Ch1/+
6 DC coupling for both
7 Trigger point at about 1v/div
Now drag the trigger point up and down a bit to just above the wave form, you can see the wave form CH2 is shown and jumps around, but volt is not accurate.
8 Now set CH1 to AC coupling, both wave forms are shown with inaccurate volts.

Issue 2: Zoom...
Zoom works really nice - particularly the reset zoom.  It lacks just one thing.  One doesn't know how much is zoomed, and reading the screen can easily confuse one into reading a wrong number.

You need either some magnification indicator (1X, 2.3X) somewhere on screen, and/or resize the grid.  With the grid unchanged but zoomed, one can easily be confused and it is hard to discern the true value of the Horizontal or Vertical.

Issue 3: Full Screen
This works nice too!.  It took me a bit of trying to realize that right-mouse button give me the option to re-window it.  Perhaps you should put a tiny icon at the corner to re-window.  First few times, I close the app and restart to regain window-ed mode.  After a few tries, I want to see if there is a way and I tried all kinds of keys - eventually got to trying the other mouse button.

A small icon in the corner would be a nice touch.


Suggestion:
Earlier point Mark_O made about when one screen of 260 screens of data is shown, it is hard to see where the visible screen is relative to the start of data.  I pointed out that your mini-wave at top-middle of screen and the T points at exactly the start position of data.

A further improvement would make it even more informative - may be on the left of the mini-wave, show x/130048 where x is the data point the screen trace begin and 130048 is however many data points is collected or available for scrolling.  Is that possible?

(Not a request, just blue-skying)  For super-super showoff, you can even have an "auto-advance" and a fast/slow button as well.  So when auto-advance is engaged, the wave start scrolling from start of saved data forward so the Wave moves right to left (like a movie moving in time).  Pressing the fast/slow button increase/decrease the play speed.  That would be super super awesome way of inspecting the saved data points.

Hey Richard, this is great work!  Thanks!

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 05, 2014, 03:06:09 am
Issue 1: When trigger is not triggered, confusing wave form...

This bug is on NORMAL trigger and doesn't show in automatic trigger.   In earlier release, you said only automatic trigger is working. I'm not sure that NORMAL trigger is "done" or work in progress.  Anyhow, you want to know this anyway.

When trigger point is not within wave-range, the waves are still shown but deformed.  The volt displayed is inaccurate.  (Stock software draws nothing when trigger point is not within wave-range, so it would not be misleading or confusing.)

It may be best to remove the visible trace so as it would not be confusing when normal trigger is not triggered.

To see the confusing trace:
1 use scope’s build-in reference
2 time=1ms/div
3 volt ch1 2v/div
4 volt ch2 1v/div
5 Trigger Edge/Normal/Ch1/+
6 DC coupling for both
7 Trigger point at about 1v/div
Now drag the trigger point up and down a bit to just above the wave form, you can see the wave form CH2 is shown and jumps around, but volt is not accurate.
8 Now set CH1 to AC coupling, both wave forms are shown with inaccurate volts.

Yeah some graphical aspects of triggering are not finished, like what you brought up, how the waveform should not be updating when the trigger is outside wave range.

Quote
Issue 2: Zoom...
Zoom works really nice - particularly the reset zoom.  It lacks just one thing.  One doesn't know how much is zoomed, and reading the screen can easily confuse one into reading a wrong number.

You need either some magnification indicator (1X, 2.3X) somewhere on screen, and/or resize the grid.  With the grid unchanged but zoomed, one can easily be confused and it is hard to discern the true value of the Horizontal or Vertical.

There is a zoom indication in the Main form Caption when zoomed in or out, as for zooming the grid, the SDK DrawGrid doesn't support zooming the grid so I would have to make my own DrawGrid function or reverse engineer theirs.

Quote
Issue 3: Full Screen
This works nice too!.  It took me a bit of trying to realize that right-mouse button give me the option to re-window it.  Perhaps you should put a tiny icon at the corner to re-window.  First few times, I close the app and restart to regain window-ed mode.  After a few tries, I want to see if there is a way and I tried all kinds of keys - eventually got to trying the other mouse button.

A small icon in the corner would be a nice touch.

That's not too hard, and I was thinking maybe binding the escape key to return to windowed mode also.

Quote
Suggestion:
Earlier point Mark_O made about when one screen of 260 screens of data is shown, it is hard to see where the visible screen is relative to the start of data.  I pointed out that your mini-wave at top-middle of screen and the T points at exactly the start position of data.

The 'T' actually points to the center of view, and the green area exactly represents the visible area (the waveform in view) in respect to the rest of the data.

Also, check out View->Debug Information... Is that similar to what you are talking about?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 05, 2014, 04:31:34 am
...
Issue 2: Zoom...
Zoom works really nice - particularly the reset zoom.  It lacks just one thing.  One doesn't know how much is zoomed, and reading the screen can easily confuse one into reading a wrong number.

You need either some magnification indicator (1X, 2.3X) somewhere on screen, and/or resize the grid.  With the grid unchanged but zoomed, one can easily be confused and it is hard to discern the true value of the Horizontal or Vertical.

There is a zoom indication in the Main form Caption when zoomed in or out, as for zooming the grid, the SDK DrawGrid doesn't support zooming the grid so I would have to make my own DrawGrid function or reverse engineer theirs.

Ah...  I totally missed the window frame name changed to have the word zoom and actual scale following - and - the second 1/2 of the 3rd line has the information I am looking for.  If that is on screen, I think it would help prevent misreading the scale.

I don't think the grid needs to be redraw - just some indication that the wave is zoomed.  The window frame is easy to miss.  Perhaps the 1/2 of the 3rd line in debug window can be brought to the wave area?  Or something more "in your face" to make it hard to miss.


...
Suggestion:
Earlier point Mark_O made about when one screen of 260 screens of data is shown, it is hard to see where the visible screen is relative to the start of data.  I pointed out that your mini-wave at top-middle of screen and the T points at exactly the start position of data.

The 'T' actually points to the center of view, and the green area exactly represents the visible area (the waveform in view) in respect to the rest of the data.

Also, check out View->Debug Information... Is that similar to what you are talking about?

The first number of debug line 1 (DataSize) and the first two numbers of debug info line 3 (ViewStart and ViewSize).  That 3 numbers shown as [ ViewSize @ ViewStart/DataSize] to the left or the right of the mini-wave would be great.  If it can't always be shown, I suppose once scrolling starts (ie: no longer at "default view") or when trigger is paused would be good too.  Then as one scroll left or right, one knows exactly where one is relative to the the exported data.   I think this is exactly what would address Mark_O's issue and a feature I would love too!

With the stock software, I can do a little of that by saving the wave form as a reference and as a TXT - To find things with stock, I have to look at the reference graphically and look at the exported text to hunt.  But that is so difficult to use and so troublesome to scroll.  This is so much more superior.

Hey, thanks, Richard.  This is getting nicer and nicer.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 05, 2014, 07:06:00 am
RichardK,
              Thanks, I must have missed that. At the moment if I run Calibration on the Hantek software it executes with no further feedback at all. If I run it on Open 6022be it executes and then gives Cannot calibrate: Calibration failed.
I may have missed something. Is there any specific steps to follow, except having it on for a while and having the probes connected to ground?
Thanks

Matchless ,

I cannot reproduce your issue -- I think you might have forgot to ground the probes first.

Rick

Rick,
      They were grounded as the Calibration software calls for on the screen. I also removed them completely as the Help calls for. Neither method works.
This is quite peculiar I must say!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 05, 2014, 07:15:04 am
Quote

   
Quote
Issue 3: Full Screen
    This works nice too!.  It took me a bit of trying to realize that right-mouse button give me the option to re-window it.  Perhaps you should put a tiny icon at the corner to re-window.  First few times, I close the app and restart to regain window-ed mode.  After a few tries, I want to see if there is a way and I tried all kinds of keys - eventually got to trying the other mouse button.

 A small icon in the corner would be a nice touch.


Quote
That's not too hard, and I was thinking maybe binding the escape key to return to windowed mode also.


I vote for the Esc key! Its a fairly accepted way.
Thanks!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 05, 2014, 06:45:00 pm
RichardK,
              Thanks, I must have missed that. At the moment if I run Calibration on the Hantek software it executes with no further feedback at all. If I run it on Open 6022be it executes and then gives Cannot calibrate: Calibration failed.
I may have missed something. Is there any specific steps to follow, except having it on for a while and having the probes connected to ground?
Thanks

Matchless ,

I cannot reproduce your issue -- I think you might have forgot to ground the probes first.

Rick

Rick,
      They were grounded as the Calibration software calls for on the screen. I also removed them completely as the Help calls for. Neither method works.
This is quite peculiar I must say!

Geeze - RichardK, you are right.  I totally missed that on Matchless' post.  Sorry, Matchless.

Time to consider an upgrade to my reading glasses.  (Gotta blame it on something else.)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 05, 2014, 08:02:16 pm
Quote
Geeze - RichardK, you are right.  I totally missed that on Matchless' post.  Sorry, Matchless.

Time to consider an upgrade to my reading glasses.  (Gotta blame it on something else.)

No problem Rick!  :)

Hopefully my comments/thoughts are useful to Richard in some way. I think I will just leave my noise concern on the back burner for a while, so as not to distract from the project which is more important to us anyway.
It's quite fascinating to watch this roll out!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Plummerman on February 05, 2014, 10:28:06 pm


However, if at that time-per-division is fast enough but you capture more than you need, you can trim the data with a quick and dirty program.  If you need more capture data than the scope is capable of (at your needed minimum capture rate), than it would be time for another scope.

Hope this helps.

Rick
Hello Rick,

     Thanks again for taking the time to respond.  Since I'm looking at some pretty low frequency stuff (alternating current of a wind turbine), my time scales will be in the milliseconds range.  I don't know of a spreadsheet program that won't simply choke on 130K to 500K (or more) data points.  As for a "quick and dirty program", I'm not much of a code guru, and attempts at using a formula to lookup and extract a smaller data set simply sent Open Office into la-la land.  What about the screen memory/display manipulations in the HANTEK and/or OpenHANTEK software?  Is every data point being shown in the display, or is there some extrapolation from the sampled data set?  I'm sure hoping there is some way to get a more manageable data chunk out of this thing..., or perhaps, as folks reading this forum are working on the Open HANTEK code, they will think about and implement ways to export manageable data sets? 
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 06, 2014, 12:30:38 am
I don't know of a spreadsheet program that won't simply choke on 130K to 500K (or more) data points.  As for a "quick and dirty program", I'm not much of a code guru, and attempts at using a formula to lookup and extract a smaller data set simply sent Open Office into la-la land.

I get the impression you're looking at CSV files?  If so, and you can use a text-editor, just open the file, select a few thousand lines (up to 60k should be fine), and save them out.  No code guru (or programming) required.

Quote
perhaps, as folks reading this forum are working on the Open HANTEK code, they will think about and implement ways to export manageable data sets?

Good suggestion.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 06, 2014, 03:53:39 am


However, if at that time-per-division is fast enough but you capture more than you need, you can trim the data with a quick and dirty program.  If you need more capture data than the scope is capable of (at your needed minimum capture rate), than it would be time for another scope.

Hope this helps.

Rick
Hello Rick,

     Thanks again for taking the time to respond.  Since I'm looking at some pretty low frequency stuff (alternating current of a wind turbine), my time scales will be in the milliseconds range.  I don't know of a spreadsheet program that won't simply choke on 130K to 500K (or more) data points.  As for a "quick and dirty program", I'm not much of a code guru, and attempts at using a formula to lookup and extract a smaller data set simply sent Open Office into la-la land.  What about the screen memory/display manipulations in the HANTEK and/or OpenHANTEK software?  Is every data point being shown in the display, or is there some extrapolation from the sampled data set?  I'm sure hoping there is some way to get a more manageable data chunk out of this thing..., or perhaps, as folks reading this forum are working on the Open HANTEK code, they will think about and implement ways to export manageable data sets?

Plummerman,

They (scope manufacturers) are more likely to work on exporting larger and larger sets instead of smaller data sets.  Deep-memory is a selling point.

130,000 points is not that many.  You could use Microsoft Word to slides the file into 2 or three, and go from there.  Microsoft Word has the capability to go to specific line of text if I remember right, so you can get to 100,000th line or whatever point you want to slice the file.

If you can get a buddie to write you a script or a macro for the word processor you use, you could speed that up.  A macro (recordable bunch of keystroke) can "delete a line, move forward N lines, repeat".  With such a macro, you can just let it run for a while and it will trim down to 1/N of the original size.

Good Luck!
Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Plummerman on February 07, 2014, 06:49:53 am


However, if at that time-per-division is fast enough but you capture more than you need, you can trim the data with a quick and dirty program.  If you need more capture data than the scope is capable of (at your needed minimum capture rate), than it would be time for another scope.

Hope this helps.


Rick
Hello Rick,

     Thanks again for taking the time to respond.  Since I'm looking at some pretty low frequency stuff (alternating current of a wind turbine), my time scales will be in the milliseconds range.  I don't know of a spreadsheet program that won't simply choke on 130K to 500K (or more) data points.  As for a "quick and dirty program", I'm not much of a code guru, and attempts at using a formula to lookup and extract a smaller data set simply sent Open Office into la-la land.  What about the screen memory/display manipulations in the HANTEK and/or OpenHANTEK software?  Is every data point being shown in the display, or is there some extrapolation from the sampled data set?  I'm sure hoping there is some way to get a more manageable data chunk out of this thing..., or perhaps, as folks reading this forum are working on the Open HANTEK code, they will think about and implement ways to export manageable data sets?

Plummerman,

They (scope manufacturers) are more likely to work on exporting larger and larger sets instead of smaller data sets.  Deep-memory is a selling point.

130,000 points is not that many.  You could use Microsoft Word to slides the file into 2 or three, and go from there.  Microsoft Word has the capability to go to specific line of text if I remember right, so you can get to 100,000th line or whatever point you want to slice the file.

If you can get a buddie to write you a script or a macro for the word processor you use, you could speed that up.  A macro (recordable bunch of keystroke) can "delete a line, move forward N lines, repeat".  With such a macro, you can just let it run for a while and it will trim down to 1/N of the original size.

Good Luck!
Rick

Hello Rick,

     I can see a desire for "deep data" in order to catch high speed transients, glitches, and the like; however, an FFT of the trace would yield the highest frequency component.  From there, the Nyquist criteria can be used to determine a maximum useful sample rate, above which, nothing useful is added to having "more data".  A problem with doing this is the resulting variable number of samples with each capture.  My desire is to do repetitive data captures of side by side data in a single file in performing a series of tests for later analysis - rather than having a host of files to deal with.  Excel and OpenOffice Calc choke on just two data channels of 130K data points- and that doesn't even include generating the x-axis data (time of each sample).  Handling a file of 20 or 30, or more such traces would be, well, unthinkable.  I know what a macro is - at one time I wrote quite a few of them in Excel VBA, but that required a "functioning" application...  The Excel  VBA macro recorder helped a lot with my weaknesses at scripting.  As yet, I'm unfamiliar with the Open Office VBA equivalent.

     AGILENT spectrum analyzers employ a user selectable number of data points per trace which may be irrespective of the instrument's sample rate.  This of course, affects the displayed results because of the bandwidth represented for each data point - thus requiring more knowledge and experience on the part of the user for accurate data representations.

      At any rate, I may be able to solve my individual problem with much head banging  |O, but that doesn't do much for the next guy.  Perhaps young blokes that live to write applications with neat features will benefit from this discussion.  I'm still thinking a bit about some technical stuff - but that's almost from a bygone life now.  The older I get, the less time I want to spend in front of a computer.

Thanks again,

Plummerman
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rasz on February 07, 2014, 07:11:49 am
Excel and OpenOffice Calc choke on just two data channels of 130K data points- and that doesn't even include generating the x-axis data (time of each sample).  Handling a file of 20 or 30, or more such traces would be, well, unthinkable.  I know what a macro is - at one time I wrote quite a few of them in Excel VBA, but that required a "functioning" application...  The Excel  VBA macro recorder helped a lot with my weaknesses at scripting.  As yet, I'm unfamiliar with the Open Office VBA equivalent.

learn Octave
https://www.gnu.org/software/octave/ (https://www.gnu.org/software/octave/)
or R
http://www.r-project.org/ (http://www.r-project.org/)

they are "like excel", but without clicking :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 07, 2014, 05:04:09 pm
Hello Rick,

     I can see a desire for "deep data" in order to catch high speed transients, glitches, and the like; ...  My desire is to do repetitive data captures of side by side data in a single file in performing a series of tests for later analysis ... Excel and OpenOffice Calc choke on just two data channels of 130K data points- and that doesn't even include generating the x-axis data (time of each sample) ...
Thanks again,

Plummerman

RichardK's program allow you rapid and easy scrolling.  So you could just use that to scroll to start and view the first couple of screens.  Save it as a reference wave and you can reload it to view anytime you like.

If however you need to export to do numerical analysis, you will need some better tool than merely a spread sheet.  Trimming is solvable easily even by only a text editor.  If you are doing over and over again, why not just import it into Access and have SQL the access database like using:
"select * into XXX where ID < NNNN".
I know on Server200X (not sure about later), you can define a text database and use ODBC to do SQL.  Using that, you don't even need importing or trimming.  I did that (a subsystem auto text export at night, SQL select next day into another subsystem).  You can work out a access report to SELECT the right range of data.  That will be quite a bit of work however.

Try RichardK's program first.  See if just viewing the start-of-wave is doing you any good, and how many datapoints fit your need best.  Then you can go from there.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: MrAureliusR on February 08, 2014, 07:17:07 am
@RichardK :clap: :clap: :clap:

I've owned this scope for a while but because I have an HP bench scope I rarely use it. Especially because the software is so crap.

But then... wow. I knew it was only a matter of time before someone pulled something awesome off like this. The amazing points:

-the triggering. just, wow. The Hantek software could rarely hold a stable trigger. Yours is rock solid.
-the FFT options. Dude. Wow. Way to freakin' go.
-THE SCROLLING. Obviously you also suffered with the 1 data point per scroll before. I just can't say enough!

Really, truly, amazing work. The only bug I've noticed is that mine won't calibrate. It just says that it failed calibrating and doesn't give anything more specific. the official software succeeds, though.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 08, 2014, 12:46:26 pm
With RichardK rolling on the software, I was wondering if the 6022 user manual could also do with a facelift by updating it to what OPEN6022BE can do. I have spent some time on it and now have the old manual in an editable word format. I have moved some parts around and fixed some of the funny Chinese English stuff. Also set up an active table of contents
Unfortunately I am not skilled enough to actually properly rewrite or add any functions, but I am quite prepared to do any editing, adding or changes suggested or sent to me by anyone.
I still have to find a way to easily manage any updates or changes while still sharing the document.
Any thoughts on whether this will be a worthwhile exercise and if anyone can/will help with the rewriting or writing of new guides to add?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: A_L_E_X on February 08, 2014, 01:24:51 pm
I got a response from Hantek regarding the software update.

Greeting from Hantek. We have improved the performance for the device to make two devices work on one computer. Have a nice day.

Looks like they improved the performance of the software. Maybe it has to do with the modified HTDisplay.dll and the new drivers.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 08, 2014, 03:27:11 pm
Hello everyone, I think I figured out the Calibration problem... In the SDK it says:

Quote
7. Function declaration:
HTMARCH_API unsigned short dsoSetCalLevel(unsigned short DeviceIndex,short* level,short
nLen);
Return value: return zero (0) for success and non-zero for failure.

Sure, that makes sense, it returns non-zero for failure... So, in my code (as you would expect) I did (in bold):
Quote
//Calibration error state
   bool CalibrateError=false;

   //Attempt to calibrate device
   if(!Scope->Calibrate())
   {
       //Attempt to Store Calibration Data to device
       if(Scope->SetCalLevel())
       {
         //Set Error Flag
         CalibrateError = true;
       }
   }
   //Otherwise there was an error
   else
   {
       //Reset Calibration Data
       Scope->GetCalLevel();

       //Set Error Flag
       CalibrateError = true;
   }

This is what's triggering the failure messages, it appears the dsoSetCalLevel function is failing... However if you look at what the stock software is doing with Calibration (via disassembly):
Quote
__int16 __usercall sub_41AE50<ax>(int a1<esi>)
{
  __int16 v1; // bx@1
  __int16 result; // ax@2
  __int16 *v3; // [sp-1Ch] [bp-24h]@1

  //Calibrate, set v1 to success/fail
  v1 = dsoCalibrate(
         *(_WORD *)(a1 + 48),                   // DeviceIndex
         *(_WORD *)(a1 + 56),                   // nTimeDIV
         *(_WORD *)(a1 + 8),                    // CH1VoltDIV
         *(_WORD *)(a1 + 32),                   // CH2VoltDIV
         (__int16 *)(a1 + 110));                // pCalLevel
  v3 = (__int16 *)(a1 + 110);

  //Failure
  if ( v1 )
  {
    dsoGetCalLevel(*(_WORD *)(a1 + 48), v3, 32);
    result = v1;
  }
  //Success
  else
  {
    dsoSetCalLevel(*(_WORD *)(a1 + 48), v3, 32);
    result = 0;
  }

  //Return status
  return result;
}

As you can see from the bold line above, they don't even use the return value from dsoSetCalLevel(), and from what I can tell, it returns a failure code regardless of success or not, either that or it's returning a 1 for success and 0 for failure.

So, I'm modifying my code to ignore the return value, if Hantek developers don't even trust it, why should I? I'm pretty sure it's causing the Calibration failure messages, even though the Calibrate succeeded and successfully stored it to the device.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 08, 2014, 04:00:52 pm
Quote
Hello everyone, I think I figured out the Calibration problem...

RichardK,
              Excellent! Will check it out on your next binary! :clap:
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 09, 2014, 08:53:35 pm
Latest Binary: http://jmp.sh/v/QN9DEKEgv4YQEW056ASq (http://jmp.sh/v/QN9DEKEgv4YQEW056ASq)

What's New:
-----------------------------------------------------------
1. Fixed a bug where you would always receive a Calibration error when Calibrating.
2. Added Math & Reference channels to Cursor Lines source menus.
3. Binded Escape Key to exit Full Screen mode.
4. Added Restore button to upper lefthand corner when in Full Screen mode.
5. Fixed a bug where changing VoltDIV on Stopped Waveforms would cause incorrect
   Interactive cursor measurements.
6. Fixed a bug where Reference Waveforms would not rescale when changing Voltage
   Divisons.
7. Fixed a bug in Text Waveform Format: Added Voltage Division information for proper scaling,
   Caveat: Files created with older versions will not load unless a #VDIV= entry is added
   under the #CLOCK entry.
8. Implemented printing of FFT.
9. Removed FFT from Channel Controls and added Voltage Division option to FFT Dialog with more
   voltage division options.
10. Added Vertical Position slider to FFT Dialog which allows positioning the FFT along the
   vertical axis.
11. Implemented Measure Option (View->Measure or Measure Button on Toolbar)

Edit: Also, there was some confusion a few pages back about the stock software's measurement feature in respect to VPP values being out of view.. My Measurement lets you choose to measure the entire wave or the visible part, hopefully that helps.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 10, 2014, 07:51:59 am
RichardK,
              It's looking better every time! Just some low level observations from this side:

The calibration utility is running correctly now, but if one runs it while erroneously connected to the internal reference output, the amplitude of the waveform doubles and then it fails and gives an error. I would expect it to fail, but not affect any settings?

If one loads a reference waveform from the R menu, there is no way to disable it again, except closing and restarting the program. Maybe a Close option would be helpful.

The full screen option with the Esc button works well, but the small icon on the left, using restore, removes the full screen, but then its without the menus.

Are you planning to include the "AUTOSET" feature that is used when probe compensation is done?

Hope this is of help.
Regards
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 10, 2014, 03:45:17 pm
The calibration utility is running correctly now, but if one runs it while erroneously connected to the internal reference output, the amplitude of the waveform doubles and then it fails and gives an error. I would expect it to fail, but not affect any settings?

When you calibrate, it's saying that whatever you see on the input is now zero, so if you see 2V on the input when you calibrate, it's going to think every signal needs to be offset by 2V. This is why the probes have to be grounded during calibration, and any settings effected by calibrating while connected to some signal above ground is only temporary because the Calibration function modifies the Calibration data in PC memory, however it doesn't store the incorrect data to the Scope.

Quote
If one loads a reference waveform from the R menu, there is no way to disable it again, except closing and restarting the program. Maybe a Close option would be helpful.

There are several different ways to turn a channel off:
1. Right click the left-hand lever and click "Hide"
2. Channel->Reference->Turn Off
3. Select the Reference channel from one of the Drop-down lists on the right-hand side and uncheck the "Enable" checkbox.

If you are talking about clearing the channel data (resetting to zero) I can add that option for the next release.

Quote
The full screen option with the Esc button works well, but the small icon on the left, using restore, removes the full screen, but then its without the menus.

I'm not sure what you mean? It's working properly for me. Also, the Right Click menu, Escape Key and Restore button are all calling the same exact function to restore to windowed mode. There is no difference between them, functionally.

Quote
Are you planning to include the "AUTOSET" feature that is used when probe compensation is done?

Again, not sure what you mean? Can you explain in more detail?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 10, 2014, 05:39:07 pm
Thanks for the response RichardK. I will try and clarify my poor explanations:

Calibration issue: I understand what you are saying, was only wondering why the display changes on an error. It would be more user friendly if the error message comes up and the waveforms stay as they were or revert back.

Reference waveform: Sorted, I did not know where to look. Sorry! :palm:

Full screen option:
The Esc key and the Right click menu takes me back to the window mode correctly, but the small icon definitely takes me back to a window mode, but with the difference that only the graticule with grid and wave form shows, no upper toolbar or right hand knobs etc. are displayed then.

Autoset feature: The Hantek software has an Auto setup blue button in the toolbar, 4th from the right. The help shows this:

Quote
Probe Compensation

Perform this function to match the characteristics of the probe and the channel input. This should be performed whenever attaching a probe to any input channel at the first time.

? From the “Probe” menu, select attenuation to 1:10. Set the switch to “X10” on the probe and connect it to CH1 of the oscilloscope. When using the probe hook-tip, insert the tip onto the probe firmly to ensure a proper connection.

? Attach the probe tip to the Probe Compensator and the reference lead to the ground connector, select CH1, and then press the “AUTOSET“ button into the menu or the toolbar.

? Check the shape of the displayed waveform.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 10, 2014, 06:35:26 pm
The Esc key and the Right click menu takes me back to the window mode correctly, but the small icon definitely takes me back to a window mode, but with the difference that only the graticule with grid and wave form shows, no upper toolbar or right hand knobs etc. are displayed then.

It shouldn't be doing that, and I cannot replicate that here at all... The corner icon calls the same exact function that the other methods call, literally there is no difference between them other than one is a Main menu item, one a right click menu item, one a key bind and the one in question a physical button, all calling the same method.

Quote
Autoset feature: The Hantek software has an Auto setup blue button in the toolbar, 4th from the right.

Alright so I examined the stock software "Auto" button to see what it does, and it appears to do the following:
1. Sets Time Division to 50us
2. Sets Display Format to YT
3. Sets both channel's Voltage Division to lowest setting (Ignores Probe Attenuation)
4. Sets Trigger Sweep to Auto
5. Sets Trigger Source to CH1
6. Sets Trigger Slope to Rising Edge (+)
7. Undoes any Invert settings

Not sure why this would be useful, except to bring the GUI back to a sort-of default configuration suitable for adjusting the Probe's variable capacitor with the provided screwdriver?

It doesn't appear to be changing the data in any way, so I think it's just a "dumb button" so to speak?

Edit: It's functioning differently with the Scope plugged in, it seems to be scanning different Voltage Divisions, then Time Divisions... Not sure exactly what it's doing, so no idea how to replicate it's functionality.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 10, 2014, 09:11:59 pm
RichardK, my understanding of this was that it was used to take the scope easily (one click) to a "default" setting that allows for the best probe compensation adjustment.
Having a special tool button for it is a bit overkill I think and it would fit in better under the Menu item Utility.
Autoset = Yes is even shown in Appendix A as a feature in the manual. Both the V1.0.3 manual and the Help button instructs you to use it when doing probe compensation adjustment for optimum wave form.

It seems to work with the probes connected to the reference waveform output. It also gives a non useful result if run with the probes disconnected instead of an error warning.

That full screen back to window mode from the small icon, is definitely different on my PC. Maybe some others can report back on theirs as well? As you say you cannot reproduce it on yours....

Hope this is useful.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 11, 2014, 07:37:31 am
RichardK,

I am having some PC issues at home.  The fixed-list looks impressive.  I am looking forward to trying out your new binary once I get my PC fixed...

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 11, 2014, 08:13:38 pm
Latest Binary: http://jmp.sh/v/QN9DEKEgv4YQEW056ASq (http://jmp.sh/v/QN9DEKEgv4YQEW056ASq)
....

Great Work! RichardK!

Summary First:

I checked all 11 points you listed.  They all work well.  I have some scaling questions/issues.  Apart from that, this is working very smooth.  Great Work! RichardK!  You've outdone yourself.  This is really almost ready to wrap up as Version 1.  (I am assuming you have not yet finish Normal Trigger, otherwise, I would say this is good for wrap up.)

+ The capability you added to Reference is really really nice.  Your implementation of Reference is so much more useful than stock software.  Now it is actually useful.
+ I like the fix with calibration!
+ The Esc button out of full screen mode is great! Very intuitive.
+ The waveform text file is good.  Until some scaling issue (see #1 below) is solved, editing that will serve a good scaling adjustment.
+ Your added feature with FFT is also great.
+ I particularly like being able to do math against the reference wave.  So the math can be delta and serve as reference and math again to get delta-of-delta or any other math-fun to do.

Some issues and suggestions

Issue 1:
I have problem getting either Math or Reference to scale.  Can you share with us how it is suppose to be scaling?  I am seeing very inconsistent scaling and even with many experiments, I can't even determine what might be the scaling logic with math. (Follow Ch1?  Follow Ch2?  Average Ch1+CH2? Follow Ch1 by a multiplier factor? etc...)
Suggestion 1 - why not make it manually scalable?  A lot more flexible if user can select scaling base on what is being investigated.  At the wave-position pointer, the right-mouse click drop down to hide the Ref/Math trace could have another entry to open a pop-up to get scaling info.

Issue 2:
Deteching toolbar causes display to be erratic.  It is certainly not a big issue unless it points to a larger problem (since trace-drawing seem to slow down after a few times of doing that).  It was hard to reproduce, but I mapped out a sure way to see it:
1. Reboot (if not rebooted, it may not show after a while but seem to slow down trace drawing)
2. Hook up to scope's reference wave
3. Start Open6022BE
4. Set trigger to get stable trace (I set it to ~500mv)
5. Resize window to a bit longer than the tool bar and a bit wider (It may not happen unless both width and height are changed)
6. Drag toolbar outside the window you will see the traces for both channel blinking.
7. Resizing the window again, the traces now draws normal - you can move toolbar anywhere without blink except the default position (below main window's drap down menus).  If you move it back to the default position it will blink again.
8. It will repeat: Resize window again and blink stop, move toolbar out and it starts...  It seems to plot slower after a while, but it may just seem to do that instead of for real.  Mind may play trick after looking at the same thing for a long time.

Issue 3:
Interestingly, when I Remote Desk Top into the machine running the scope with both Ch1 and Ch2, only Ch2 is showing.  The grid and Ch1 do not show at all.  When I have both Math and Reference wave on, grid,Ch1,Ch2,Math are absent but Reference wave is visible.

Suggestion 2:
Would it be feasible to implement scroll bar in the control area?  I use a small machine with 1024x768 resolution to fit my work area.  When measurement windows are open, Ch2 controls are no longer visible.

Suggestion 3:
For measurement windown, would it be feasible to split the screen horizontal instead of vertical?  Displaying Ch2 data below Ch1 takes too much screen real-estate and the measurement data display is not wide.  If Ch1 and Ch2 are spilt horizontally, it will not take up so much screen.


Really RichardK, this is great work and thanks!
Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 11, 2014, 10:38:50 pm
Issue 1:
I have problem getting either Math or Reference to scale.  Can you share with us how it is suppose to be scaling?  I am seeing very inconsistent scaling and even with many experiments, I can't even determine what might be the scaling logic with math. (Follow Ch1?  Follow Ch2?  Average Ch1+CH2? Follow Ch1 by a multiplier factor? etc...)
Suggestion 1 - why not make it manually scalable?  A lot more flexible if user can select scaling base on what is being investigated.  At the wave-position pointer, the right-mouse click drop down to hide the Ref/Math trace could have another entry to open a pop-up to get scaling info.

It has to do with there being two different Voltage Divisions for each channel, one that reflects the channel setting and one for Stopped waveforms (So they can scale from acquired voltage division to set voltage division). Problem was, in some parts of the code I was using the current voltage division instead of the acquire division (Oops!). Should be fixed in next release.

Quote
Issue 2:
Detaching toolbar causes display to be erratic.  It is certainly not a big issue unless it points to a larger problem (since trace-drawing seem to slow down after a few times of doing that).  It was hard to reproduce, but I mapped out a sure way to see it:
1. Reboot (if not rebooted, it may not show after a while but seem to slow down trace drawing)
2. Hook up to scope's reference wave
3. Start Open6022BE
4. Set trigger to get stable trace (I set it to ~500mv)
5. Resize window to a bit longer than the tool bar and a bit wider (It may not happen unless both width and height are changed)
6. Drag toolbar outside the window you will see the traces for both channel blinking.
7. Resizing the window again, the traces now draws normal - you can move toolbar anywhere without blink except the default position (below main window's drop down menus).  If you move it back to the default position it will blink again.
8. It will repeat: Resize window again and blink stop, move toolbar out and it starts...  It seems to plot slower after a while, but it may just seem to do that instead of for real.  Mind may play trick after looking at the same thing for a long time.

Sorry about that, a minor oversight... When the form's dimensions change I have to manually update the scope's canvas dimensions (otherwise you get flickering). I have a routine for doing this for which I call whenever I perceive the form's dimensions have changed, however I forgot to think about the toolbar un-docking (which would cause the form's vertical dimension to increase). Should be fixed in the next binary.

Quote
Issue 3:
Interestingly, when I Remote Desk Top into the machine running the scope with both Ch1 and Ch2, only Ch2 is showing.  The grid and Ch1 do not show at all.  When I have both Math and Reference wave on, grid,Ch1,Ch2,Math are absent but Reference wave is visible.

I have no idea what would be causing that... I have tested with VNC Viewer and it appears fine, so it's probably an issue with the software you are using... Perhaps some kind of setting for reducing unnecessary traffic?  :-//

Quote
Suggestion 2:
Would it be feasible to implement scroll bar in the control area?  I use a small machine with 1024x768 resolution to fit my work area.  When measurement windows are open, Ch2 controls are no longer visible.

I'll see what I can do, but at the moment it looks like it might be a more complicated feat than one would imagine...

Quote
Suggestion 3:
For measurement window, would it be feasible to split the screen horizontal instead of vertical?  Displaying Ch2 data below Ch1 takes too much screen real-estate and the measurement data display is not wide.  If Ch1 and Ch2 are split horizontally, it will not take up so much screen.

I was thinking the same thing and I have already implemented for the next release a segmented view (see attachment) using four TreeView controls (one for each measure source) side by side. The way the stock software does it is a massive waste of space, and it just looks wrong.

Btw, if anyone was wondering, if you double click the measurement list it will invert the current selections, so if nothing is selected, it will select all items.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 12, 2014, 12:37:20 am
First of all: you're doing a great job, Richard, thanks! :-+ :-+

As far as I could test your work so far, it's way better than the mfg's piece of code ...

One additional bug:

The V/Div setting for both channels have a glitch (regardless of other settings as far as i have tested it):

V/Div (set)  V/Div (active)
10/V            10V
5V                5V
2V                2V
1V                1V
500mV         1V
200mV         1V
100mV         1V
50mV           500mV
20mv           200mV

(values for x1, x10 etc. show the same behaviour)

Another thing: IIRC someone had a problem with the calibration signal on differnent PCs (frequency almost doubled). This appears to be a driver issue (or something messing up the intermal time-base in the 6022BE). This can be reproduced by running Open6022BE and the original software simultaneously (an easy way to mess things up  ;D )

I'm waiting to see the next version of Open6022BE - that really is something worth waiting for!


Regards

Robert
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 12, 2014, 12:44:55 am
One additional bug:

The V/Div setting for both channels have a glitch (regardless of other settings as far as i have tested it):

V/Div (set)  V/Div (active)
10/V            10V
5V                5V
2V                2V
1V                1V
500mV         1V
200mV         1V
100mV         1V
50mV           500mV
20mv           200mV

I'm not able to reproduce this here, and nobody else has mentioned such an obvious bug... Are you using the latest binary (http://jmp.sh/v/pgnwMU9slvz6OIK8YhKr)? Can you provide details to reproduce it? Because the channel voltage division controls are working fine for me.

Also, make sure you have the latest drivers installed from the recent update at Hantek Website: http://www.hantek.com.cn/en/ProductDetail_31.html (http://www.hantek.com.cn/en/ProductDetail_31.html)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 12, 2014, 03:38:10 am
I'm using the latestest version of your Software and the drivers.

You'll get so screen shots this evening (4:30am right now, got to go to work, sorry).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 12, 2014, 08:43:14 am
Issue 3:
Interestingly, when I Remote Desk Top into the machine running the scope with both Ch1 and Ch2, only Ch2 is showing.  The grid and Ch1 do not show at all.  When I have both Math and Reference wave on, grid,Ch1,Ch2,Math are absent but Reference wave is visible.

I have no idea what would be causing that... I have tested with VNC Viewer and it appears fine, so it's probably an issue with the software you are using... Perhaps some kind of setting for reducing unnecessary traffic?  :-//


Interesting.  I thought of possible data compression when I first ran into this and I immediately tried it with setting display to max, that did not do any good.  Must be some of Hantek's DLL must failed to follow certain windows rules.

Anyone care to see if they run into this as well?  I use WinXP-Sp2 for scope and WinXp SP2 and SP3 for RDC into the scope machine.  I will switch over to an Sp3 machine to see if that makes any difference.


Suggestion 2:
Would it be feasible to implement scroll bar in the control area?  I use a small machine with 1024x768 resolution to fit my work area.  When measurement windows are open, Ch2 controls are no longer visible.

I'll see what I can do, but at the moment it looks like it might be a more complicated feat than one would imagine...


Arrgh, not critical, but would be nice.



Suggestion 3:
For measurement window, would it be feasible to split the screen horizontal instead of vertical?  Displaying Ch2 data below Ch1 takes too much screen real-estate and the measurement data display is not wide.  If Ch1 and Ch2 are split horizontally, it will not take up so much screen.

I was thinking the same thing and I have already implemented for the next release a segmented view (see attachment) using four TreeView controls (one for each measure source) side by side. The way the stock software does it is a massive waste of space, and it just looks wrong.

Btw, if anyone was wondering, if you double click the measurement list it will invert the current selections, so if nothing is selected, it will select all items.

What can I say, great minds think alike!  I like how your screen print looks with the new measurement result windows!

I do look forward to your next binary, and thanks again.

Rick
 
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 12, 2014, 03:04:56 pm
Arrgh, not critical, but would be nice.

Actually, I implemented it last night... It was a pain in the butt, but it's done... lol
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 12, 2014, 06:11:16 pm
Here are the promised screen shots ...

OS: Win7Pro 64bit

Open6022BE: R11

Drivers: as downloaded from mfg's site two days ago.

Signal: 1V@1kHz (cal output)

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on February 12, 2014, 06:29:47 pm
Just to let you know that you hard work is beeing appreciated. ;)

I'm working on tutorial on how to reverse engineer multiplexed lcd signal back into characters/numbers and your software is really helpful.
On the image below is muliplexed signal put trough 74HC4050 HEX Buffer...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 12, 2014, 06:55:48 pm
Due to the rather strage behaviour of the V/DIV-setting on my PC I'll ask before putting it on the wish list:

With slower settings (i.e. 500ms/DIV) I get an updated screen every 5 seconds. Is that the standard output?

If yes: I'd love to have a "continuous drawing mode" - either real-time samples on the right edge of the scope and the plot moving to the left of, if more feasible, continuous drawing of samples from left to right with "overwriting" on the next pass.

That would ease finding bursts on 100kHz max signals a lot ...

Regards Robert

P.S.: yeah, I know ... coming up with strange (individual) bugs and having extra wishes is a horrible combination  ;D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 12, 2014, 07:46:45 pm
Latest Binary: http://jmp.sh/v/pgnwMU9slvz6OIK8YhKr (http://jmp.sh/v/pgnwMU9slvz6OIK8YhKr)


What's New:
-----------------------------------------------------------
1. Added the ability to Import & Export Calibration data to file (Utility->Zero Offset Calibration)
2. Added Clear option to all Channel sub-menus which allows you to clear the data on that
   channel to zero.
3. Added Scroll Bars to Vertical Controls when they are out of view.
4. Fixed a bug when undocking-redocking the Toolbar which would cause Scope display to flicker,
   and or reduced performance.
5. Fixed a bug where Math and Reference Cursor Measurements would be incorrect in certain
   situations.
6. Fixed several form resizing flicker issues.
7. Modified the Measure Output window to have a horizontal layout (Separate Tree View for each
   Measurement Channel) which better utilizes the available horizontal space.
8. Added preliminary support for a Probe Compensation Auto Setup (See Auto Button on Toolbar).
9. Fixed a few minor Measurement bugs.
10. Renamed some Measurement items in the Measurement Window (Positive/Negative now in parentheses
   after the Measurement name).
11. Swapped positions of "Toggle Controls" & "Toggle Measure" buttons on the Toolbar
12. Added little 'X' buttons to Measure, Output and Control Windows which hides them when clicked.
13. Fixed a bug where resizing the form would not rescale the Channel Waveform Position Levers.
14. Made Zooming In and Out more granular (Halved zoom-rate)
15. Fixed a bug where Voltage Division might not properly set for CH1 & CH2 in certain situations.

RobertH: Hopefully #15 fixes your issues.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 12, 2014, 11:03:44 pm
Wow, that's a fast response  :-+

It solves the problem to some extend:

Down to 500mV/DIV things are working properly ... with 200mV/DIV and 100mv/DIV actual resolution is 400mv/DIV (that's strange!), 50mV/DIV gives you 200mV/DIV and 20mV/DIV appears to be working correctly again ...

The peak-peak readout is somewhat erratic too:

To make things even worse: when switching to x10 (only the probe, thus reducing the signal to 10%) all results are as they are supposed to be ...

While summing the above things up I did some additional testing. The main result: disregard all after good morning!

Your update fixed my issues! I've reproduced the R11's flaws on two other computers, so there might be some changes in hardware, which led to this behaviour.

The rest seems to be a clipping issue, as there are several clipping conditions (@x1):

a) Vin exceeding 500mV
b) Vin exceeding 5*V/DIV (if Vin is above 500mV)
c) Vin exceeding 5V (due to hardware limitations: internal /10 & 500mV max for a/d converter)

So clipping occurs at the following settings vs. voltages:

V/DIV    Vclip (x1) Vclip(x10) Vclip (x100)
20mV    500mV    n/a            n/a
50mV    500mV    n/a            n/a
100mV  500mV    n/a            n/a
200mV  1V          5V              n/a
500mV  2.5V       5V              n/a
1V         5V          5V              n/a
2V         5V*        10V            50V
5V         5V*        25V            50V
10V       5V*        50V            50V
20V       n/a         50V*         100V
50V       n/a         50V*         250V
100V     n/a         50V*         500V
200V     n/a         n/a            500V*
500V     n/a         n/a            500V*
1kV       n/a         n/a            500V*
(values marked with * are running into hardware limitation)

So, as a conclusion: all settings above 1V times probe attenuation run into the hardware limit and all settings above 100mV times probe attenuation will hit the software limit (assuming it is in fact a software limit).

For AC sources the software limit (again, if it isn't, please correct me!) is quite reasonable, as it exceeds the 8 DIVs on the scope. For DC sources this limit is somewhat low, as it leaves up to 3 DIVs unusable ...

So, as a conclusion: the three highest settings are to some extend obsolete, as they will run into the hardware limit of 5V max @ BNC. If (I know, too many if's) the 5*V/DIV setting is a software limit (with some doubts, as this applies to the mfg's software too), I'd suggest removing it, at least for DC measurement ...

My 6022BE is now decorated with a big sticker: "Max usable range: 5V * probe attenuation"

Best regards and, once again, thanks for the fast respone

Robert
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 13, 2014, 03:50:54 am
Latest Binary: http://jmp.sh/v/pgnwMU9slvz6OIK8YhKr (http://jmp.sh/v/pgnwMU9slvz6OIK8YhKr)
....

RichardK, great work, I owe you a few.  See below.  Also, there are two new issues - likely just one as they look related.

+1. Added the ability to Import & Export Calibration data to file (Utility->Zero Offset Calibration)
>>   I assume the export/input is to allow zero-reset without having to wait for the system warm up and recal it to what the normal zero-offset would be.   Do you plan to re-import settings at start up?

+2. Added Clear option to all Channel sub-menus which allows you to clear the data on that
   channel to zero.
>> Tested AOK

+3. Added Scroll Bars to Vertical Controls when they are out of view.
for (i=0;i<=1000000;i++ ) { say: This is wonderful!  Works beautifully!  I owe you one.}   In other words, thanks a million plus one!

+4. Fixed a bug when undocking-redocking the Toolbar which would cause Scope display to flicker,  and or reduced performance.
>> Fixed work, I can no longer trigger that flicker playing around with toolbar.

+5. Fixed a bug where Math and Reference Cursor Measurements would be incorrect in certain
   situations.
>> Math cursor is very stable, tested under different volts and freq.  See two other issues below with math trace.

6. Fixed several form resizing flicker issues.
>> Rock stable!

7. Modified the Measure Output window to have a horizontal layout (Separate Tree View for each   Measurement Channel) which better utilizes the available horizontal space.
for (i=1;i<=1000000;i++ ) { say: Wonderful!  This is sweet.}

8. Added preliminary support for a Probe Compensation Auto Setup (See Auto Button on Toolbar).
>> not tested, can't find the silly little screw driver

9. Fixed a few minor Measurement bugs.
>> So far, so good, I have not seen any issues.

10. Renamed some Measurement items in the Measurement Window (Positive/Negative now in parentheses
   after the Measurement name).
>> Works, no issue

11. Swapped positions of "Toggle Controls" & "Toggle Measure" buttons on the Toolbar
>> Wonderful

12. Added little 'X' buttons to Measure, Output and Control Windows which hides them when clicked.
>> very nice touch

13. Fixed a bug where resizing the form would not rescale the Channel Waveform Position Levers.

14. Made Zooming In and Out more granular (Halved zoom-rate)
>> Tested AOK.

15. Fixed a bug where Voltage Division might not properly set for CH1 & CH2 in certain situations.

RobertH: Hopefully #15 fixes your issues.
....

New Issues 1:
1. Math is changing where it should not be (setting dependent, described below).

When both Ch1 and Ch2 are measuring the same thing, the two waves match as expected.  Math trace (A+B) should look exactly like  Ch1 and Ch2 with exact same frequency, different ampltitue, and same 0 crossing.  By window resize and mouse movement describe below, it could get into a mode where it shifts left/right a little (that is what caught my attention).  The math trace begin rolling left and right and keep rolling.  Once that starts, it can get to a point the rolling worsens to like an untriggered wave form. 

Settings:
Both Ch1 and Ch2 hooked to the same spot, 100KHz, Square,  +-3.5V peak to peak, math=A+B
Set to default 2V/div, 5uS.  Leave trigger at program start up default.
Note:Square, Sine, doesn't matter, v/div doesn't matter, just frequency and time/div matters.  I know I don't get it at the low 1KHz reference wave. I am not sure at what frequency it starts. At 100KHz (or 90KHz), I know the bug will hit.

Steps to trigger the uncontrolled scrolling of math waveform:  (Next issue related to this, don't change a thing yet after you reproduce this bug)
1. I started with fresh reboot, signal all set up (100KHz, Square, +-3.5v)
2. Start the program, change time/div to 5uS, math A+B
3. Size the window smallest (both verticle and horizontal) and move it to top left for sreen-space.  LET GO of the button before next step.
4. Enlarge the window both verticle and horizontal about 1.5x size
5. Start the mouse in the trace-drawing area and move the mouse left and right very very rapidly about 10 times.(mouse movement within trace area, moved perhaps 1/2 trace area width)
6. It may start after a few (<5) such rapid mouse movement left and right, if not go back to step 3.  I can usually get the trace scrolling  going back to step 3 less than 5 times.
7. Once you get it to roll, move moment appears irrelevant.  Sizing window smaller stops the roll, sizing it big starts it again.  It became uncontrollable after a few small-large cycle..
8. Do not change a thing yet.  Look at the next issue.

New Issues 2: probably related to Issue 1

(Once you hit issue 1) Trigger is default setting.  Top right display of trigger voltage update delayed (by > 5 sec) Moving the update trigger above wave, the trigger voltage should update.  The new display of trigger voltage you added on lower left updates immediately. The trigger voltage on top right (stock software trigger voltage display) does not update immediately.  The more you go "resize-small (Vert&Horiz), release button, size big (V&H)," the slower the the update gets.  I have waited for >10 seconds for it to update.  (The trigger voltage change can be within or beyond wave-voltage.  I used the trigger pointer tab to change trigger voltage in case there is another way I don't know)

With your added display on lower right already showing it immediately, the delayed stock-display of trigger voltage will merely confuse the user.  If this is difficult to fix, perhaps just don't display the stock trigger voltage update.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 13, 2014, 04:02:45 am
Wow, that's a fast response  :-+

It solves the problem to some extend:

Down to 500mV/DIV things are working properly ... with 200mV/DIV and 100mv/DIV actual resolution is 400mv/DIV (that's strange!), 50mV/DIV gives you 200mV/DIV and 20mV/DIV appears to be working correctly again ...

The peak-peak readout is somewhat erratic too:
...
Robert

Robert, I will give it a try to reproduce your issue, see if I can somehow get it to replicate on my system the next couple of days.  I will keep you posted.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 13, 2014, 05:42:14 am
With slower settings (i.e. 500ms/DIV) I get an updated screen every 5 seconds. Is that the standard output?

Hi, Robert.

If you multiply it out, 500ms/div x 10 divs = 5 sec.  It has to capture the data, before it can display it.  ;)

Quote
If yes: I'd love to have a "continuous drawing mode" - either real-time samples on the right edge of the scope and the plot moving to the left of, if more feasible, continuous drawing of samples from left to right with "overwriting" on the next pass.

I can see where that would be handy.  However, it would be difficult to do.  The reason being that the interface with the Hantek DLL sets up the acquisition parameters, then the driver funnels the data directly to the memory buffers.  There's no incremental interactivity (query/response, or periodic notify callbacks).

The reason I say difficult, and not the expected impossible, is because it would be possible to prefill the buffer (say, with FF's).  And have a second task running that monitored the high-water mark (as the FF's got overridden by incoming data).  Then update the display incrementally.  I'm not sure that's something Richard would want to tackle at this stage of the development.

Of the two display methods you suggested, the fill-then-overwrite would be lower overhead, than trying to blit a chunk of screen space while scrolling the whole area (on top of the grid pattern).  Some or all of this may be completely impossible, using the DisplayDLL that Hantek has provided.  I'm not familiar with it's constraints, but I doubt it's overly fancy.  So it may effectively be wishful thinking.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 13, 2014, 07:24:38 am
What an improvement!!!

RichardK, just one small thing I picked up when running the Autoset for scope compensation adjustment, the V/Div goes to 100mV on the OEM Hantek and Open6022be goes to 1.00V.

Saying you are doing excellent work is an understatement!!!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 13, 2014, 09:38:21 am
Wow, that's a fast response  :-+

It solves the problem to some extend:

Down to 500mV/DIV things are working properly ... with 200mV/DIV and 100mv/DIV actual resolution is 400mv/DIV (that's strange!), 50mV/DIV gives you 200mV/DIV and 20mV/DIV appears to be working correctly again ...

The peak-peak readout is somewhat erratic too:
...
Robert

Robert, I will give it a try to reproduce your issue, see if I can somehow get it to replicate on my system the next couple of days.  I will keep you posted.

Rick

Rick,

don't waste the time - that was clipping that hit me  |O

Robert
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 13, 2014, 04:25:52 pm
Wow, that's a fast response  :-+

It solves the problem to some extend:

Down to 500mV/DIV things are working properly ... with 200mV/DIV and 100mv/DIV actual resolution is 400mv/DIV (that's strange!), 50mV/DIV gives you 200mV/DIV and 20mV/DIV appears to be working correctly again ...

The peak-peak readout is somewhat erratic too:
...
Robert

Robert, I will give it a try to reproduce your issue, see if I can somehow get it to replicate on my system the next couple of days.  I will keep you posted.

Rick

Rick,

don't waste the time - that was clipping that hit me  |O

Robert

OK, good you found the problem.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 13, 2014, 05:01:45 pm
What an improvement!!!

RichardK, just one small thing I picked up when running the Autoset for scope compensation adjustment, the V/Div goes to 100mV on the OEM Hantek and Open6022be goes to 1.00V.

Saying you are doing excellent work is an understatement!!!

It varies from scope to scope because the stock software is scanning horizontal and vertical scale and looking for some condition that it finds suitable. I'm not quite sure what exactly that condition is yet, so the Auto button is "dumb" right now and when I am able to figure out what it is exactly they are doing I'll make it do the same.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 13, 2014, 05:16:07 pm

+1. Added the ability to Import & Export Calibration data to file (Utility->Zero Offset Calibration)
>>   I assume the export/input is to allow zero-reset without having to wait for the system warm up and recall it to what the normal zero-offset would be.   Do you plan to re-import settings at start up?

It was easy to implement and I figured someone might find a use for it so why not... I don't plan on adding any start-up import, I am already grabbing the stored calibration data from the scope at start-up, so I'll leave the usage of this feature to the imagination of the end-user.

Quote
New Issues 1:
1. Math is changing where it should not be (setting dependent, described below).

When both Ch1 and Ch2 are measuring the same thing, the two waves match as expected.  Math trace (A+B) should look exactly like  Ch1 and Ch2 with exact same frequency, different ampltitue, and same 0 crossing.  By window resize and mouse movement describe below, it could get into a mode where it shifts left/right a little (that is what caught my attention).  The math trace begin rolling left and right and keep rolling.  Once that starts, it can get to a point the rolling worsens to like an untriggered wave form.

Not sure what could be causing this but I'll be investigating it today.

Quote
New Issues 2: probably related to Issue 1

(Once you hit issue 1) Trigger is default setting.  Top right display of trigger voltage update delayed (by > 5 sec) Moving the update trigger above wave, the trigger voltage should update.  The new display of trigger voltage you added on lower left updates immediately. The trigger voltage on top right (stock software trigger voltage display) does not update immediately.  The more you go "resize-small (Vert&Horiz), release button, size big (V&H)," the slower the the update gets.  I have waited for >10 seconds for it to update.  (The trigger voltage change can be within or beyond wave-voltage.  I used the trigger pointer tab to change trigger voltage in case there is another way I don't know)

Was able to slightly reproduce this and it might have been caused by that portion's draw event having a much lower priority and when the draw queue is choked full of draw wave events (which take some time) it tends to sit on the back burner for a while. Since rendering the trigger level takes very little time I gave that particular draw event a higher priority than draw wave events and it's much more snappy now.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 14, 2014, 04:42:17 am
I was going to skip the 13th build, but it's the 13th of February and I fixed a few issues, so I might as well get it out of the way... Lucky Build #13: http://jmp.sh/r4BjH8a (http://jmp.sh/r4BjH8a)

What's New:
-----------------------------------------------------------
1. Various Performance enhancements.
2. Reduced tendency for Math channel to roll.
3. Implemented FFT Fundamental frequency rendering.
4. Fixed a glitch in FFT Rendering.

Not a whole lot changed, but this should clear up the latest issues and get #13 out of the way *knock on wood*.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 14, 2014, 05:01:42 am
I was going to skip the 13th build, but it's the 13th of February and I fixed a few issues, so I might as well get it out of the way... Lucky Build #13: http://jmp.sh/JEjvatW (http://jmp.sh/JEjvatW)

Hmm.  "File Not Found."  That string looks suspiciously short?  Maybe it's just me.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 14, 2014, 05:12:25 am
I was going to skip the 13th build, but it's the 13th of February and I fixed a few issues, so I might as well get it out of the way... Lucky Build #13: http://jmp.sh/JEjvatW (http://jmp.sh/JEjvatW)

Hmm.  "File Not Found."  That string looks suspiciously short?  Maybe it's just me.

I think perhaps it is a site problem.  I saw this PR13 post from RichardK a few hours ago on my laptop.  Approx 1 hr ago,  I got on my PC to download - and I did not find this PR13 post from RichardK.  I was beginning to wonder if I was imagining it or perhaps he changed his mind and removed it somehow.  I came back to my laptop after having some snack, this post from RichardK reappeared.

I was really wondering what was in my dinner that caused such imagination.  I am glad I see your post.  That tells me there must be something wrong on the site or Google Chrome cache is not working right showing me an old page.

Well, I am sure Richard K will post a new link again shortly.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 14, 2014, 02:16:30 pm
Sorry about that guys, Jumpshare gave me the wrong URL...  :-//

http://jmp.sh/r4BjH8a (http://jmp.sh/r4BjH8a)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 14, 2014, 02:22:21 pm
I think perhaps it is a site problem.  I saw this PR13 post from RichardK a few hours ago on my laptop.  Approx 1 hr ago,  I got on my PC to download - and I did not find this PR13 post from RichardK.  I was beginning to wonder if I was imagining it or perhaps he changed his mind and removed it somehow.  I came back to my laptop after having some snack, this post from RichardK reappeared.

I was really wondering what was in my dinner that caused such imagination.  I am glad I see your post.  That tells me there must be something wrong on the site or Google Chrome cache is not working right showing me an old page.

Both, I found another issue and noticed nobody had Downloaded it yet so I removed it and rebuilt it, reuploaded with new fix and one other new feature...

But... Lucky #13 strikes back and Jumpshare gives me a dud URL (it was /invalid or something) when I'm making the post, so I copy it again and finally get a normal looking one (but I didn't test it, DOH!) and of course it's a DUD too  :palm:

Well time to un-bury my house, friggen snow  :rant:
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 15, 2014, 02:25:05 am
I was going to skip the 13th build, but it's the 13th of February and I fixed a few issues, so I might as well get it out of the way... Lucky Build #13: http://jmp.sh/r4BjH8a (http://jmp.sh/r4BjH8a)

What's New:
-----------------------------------------------------------
1. Various Performance enhancements.
2. Reduced tendency for Math channel to roll.
3. Implemented FFT Fundamental frequency rendering.
4. Fixed a glitch in FFT Rendering.

Not a whole lot changed, but this should clear up the latest issues and get #13 out of the way *knock on wood*.

1. Various Performance enhancements.
It does seem more responsive now

2. Reduced tendency for Math channel to roll.
Not fully fixed.  Issue#1 (recap below) still triggers a roll.  When I posted originally, I said 100KHz down to 90 KHz I can get it to roll.  I experimented more and I get it to roll at 10KHz at 5uS/division.  (A,B at the same spot on signal gen, Square wave, +- 2 to 2.5V).  The rolling stop at slower time/division.  At 50uS, I did not get it to roll.
Even as slow as 5KHz, I can also see rolling.  But 5KHz at 5uS/div, so little of the wave is visible determining rolling (or not) becomes difficult.
Unrelated Suggestion
Doing tests makes me switch time/div a lot and I notice the drop down shows just a few choices (7+current selection), so I ended up scrolling around a lot.  This may be an inconvenience during normal use as well.   Since that drop down is so high up on the screen, offering more choices will not impact screen real-estate.  Can you make the drop down a little longer so it show more time/div choices?  Only if it is easy - this one is polishing.  Offer more choices for this drop down menu may make it more user-friendly.  It would also look more polished to get rid of some of the digits after the decimal since they are always zero anyway.

3. Implemented FFT Fundamental frequency rendering.
4. Fixed a glitch in FFT Rendering.
Not sure how to test 3&4.  So I did not test these two much.

Issue#2 is certainly fixed.  The stock trigger voltage display now updates immediately.  The conflicting trigger-voltage display no longer exist to confuse the user.

Recap of Issue #1 so you don't have to hunt down the original post down reproduction info:
New Issues 1:
1. Math is changing where it should not be (setting dependent, described below).

When both Ch1 and Ch2 are measuring the same thing, the two waves match as expected.  Math trace (A+B) should look exactly like  Ch1 and Ch2 with exact same frequency, different ampltitue, and same 0 crossing.  By window resize and mouse movement describe below, it could get into a mode where it shifts left/right a little (that is what caught my attention).  The math trace begin rolling left and right and keep rolling.  Once that starts, it can get to a point the rolling worsens to like an untriggered wave form. 

Settings:
Both Ch1 and Ch2 hooked to the same spot, 100KHz, Square,  +-3.5V peak to peak, math=A+B
Set to default 2V/div, 5uS.  Leave trigger at program start up default.
Note:Square, Sine, doesn't matter, v/div doesn't matter, just frequency and time/div matters.  I know I don't get it at the low 1KHz reference wave. I am not sure at what frequency it starts. At 100KHz (or 90KHz), I know the bug will hit.

Steps to trigger the uncontrolled scrolling of math waveform:  (Next issue related to this, don't change a thing yet after you reproduce this bug)
1. I started with fresh reboot, signal all set up (100KHz, Square, +-3.5v)
2. Start the program, change time/div to 5uS, math A+B
3. Size the window smallest (both verticle and horizontal) and move it to top left for sreen-space.  LET GO of the button before next step.
4. Enlarge the window both verticle and horizontal about 1.5x size
5. Start the mouse in the trace-drawing area and move the mouse left and right very very rapidly about 10 times.(mouse movement within trace area, moved perhaps 1/2 trace area width)
6. It may start after a few (<5) such rapid mouse movement left and right, if not go back to step 3.  I can usually get the trace scrolling  going back to step 3 less than 5 times.
7. Once you get it to roll, move moment appears irrelevant.  Sizing window smaller stops the roll, sizing it big starts it again.  It became uncontrollable after a few small-large cycle..
8. Do not change a thing yet.  Look at the next issue.

New Issues 2: probably related to Issue 1

(Once you hit issue 1) Trigger is default setting.  Top right display of trigger voltage update delayed (by > 5 sec) Moving the update trigger above wave, the trigger voltage should update. 

Thanks again!
Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 15, 2014, 03:14:05 am
2. Reduced tendency for Math channel to roll.
Not fully fixed.  Issue#1 (recap below) still triggers a roll.  When I posted originally, I said 100KHz down to 90 KHz I can get it to roll.  I experimented more and I get it to roll at 10KHz at 5uS/division.  (A,B at the same spot on signal gen, Square wave, +- 2 to 2.5V).  The rolling stop at slower time/division.  At 50uS, I did not get it to roll.
Even as slow as 5KHz, I can also see rolling.  But 5KHz at 5uS/div, so little of the wave is visible determining rolling (or not) becomes difficult.

I think the rolling is caused by the fact that the Math function takes some time to execute and by the time it's rendered the source waveforms are at a slightly different time, and with the noise the trigger could be in another location, thus causing the offset.

I optimized it as much as I can, so I think in order to squash this issue I'll have to find another approach, possibly compute the math as soon as possible after the raw data is acquired, although I am already doing it pretty much right after CH1 & CH2 are acquired.

Quote
Unrelated Suggestion
Doing tests makes me switch time/div a lot and I notice the drop down shows just a few choices (7+current selection), so I ended up scrolling around a lot.  This may be an inconvenience during normal use as well.   Since that drop down is so high up on the screen, offering more choices will not impact screen real-estate.  Can you make the drop down a little longer so it show more time/div choices?  Only if it is easy - this one is polishing.  Offer more choices for this drop down menu may make it more user-friendly.  It would also look more polished to get rid of some of the digits after the decimal since they are always zero anyway.

Good idea, will be in the next release.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 15, 2014, 03:39:20 am
2. Reduced tendency for Math channel to roll.
Not fully fixed.  Issue#1 (recap below) still triggers a roll.  When I posted originally, I said 100KHz down to 90 KHz I can get it to roll.  I experimented more and I get it to roll at 10KHz at 5uS/division.  (A,B at the same spot on signal gen, Square wave, +- 2 to 2.5V).  The rolling stop at slower time/division.  At 50uS, I did not get it to roll.
Even as slow as 5KHz, I can also see rolling.  But 5KHz at 5uS/div, so little of the wave is visible determining rolling (or not) becomes difficult.

I think the rolling is caused by the fact that the Math function takes some time to execute and by the time it's rendered the source waveforms are at a slightly different time, and with the noise the trigger could be in another location, thus causing the offset.

I optimized it as much as I can, so I think in order to squash this issue I'll have to find another approach, possibly compute the math as soon as possible after the raw data is acquired, although I am already doing it pretty much right after CH1 & CH2 are acquired.


I think this is a minor issue - not one that should hold up release since your release represents so many important improvements.  It could be documented in the release write-up that a fast CPU is needed for proper rendering of math function @ faster than 5uS/division.  But of course, it is your call.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 15, 2014, 04:22:24 am
2. Reduced tendency for Math channel to roll.
Not fully fixed.  Issue#1 (recap below) still triggers a roll.  When I posted originally, I said 100KHz down to 90 KHz I can get it to roll.  I experimented more and I get it to roll at 10KHz at 5uS/division.  (A,B at the same spot on signal gen, Square wave, +- 2 to 2.5V).  The rolling stop at slower time/division.  At 50uS, I did not get it to roll.
Even as slow as 5KHz, I can also see rolling.  But 5KHz at 5uS/div, so little of the wave is visible determining rolling (or not) becomes difficult.

I think the rolling is caused by the fact that the Math function takes some time to execute and by the time it's rendered the source waveforms are at a slightly different time, and with the noise the trigger could be in another location, thus causing the offset.

I optimized it as much as I can, so I think in order to squash this issue I'll have to find another approach, possibly compute the math as soon as possible after the raw data is acquired, although I am already doing it pretty much right after CH1 & CH2 are acquired.


I think this is a minor issue - not one that should hold up release since your release represents so many important improvements.  It could be documented in the release write-up that a fast CPU is needed for proper rendering of math function @ faster than 5uS/division.  But of course, it is your call.

Now that I have looked at the code some more, it might also be caused by the fact that Data Capture is in one thread and Wave Drawing in another, and when the CH1 & CH2 waves are being drawn, a new Data Capture may have occurred in the other thread, BUT before the latest Math has been calculated. So when Math Channel is finally rendered, it's old Math data rendered with new Channel data, and if the new channel data has a different trigger position... Well you know what happens :)

In the next release I'll have a change in the trigger code that won't affect any situation where Channel Data and Math Data are in sync, BUT if they are not in sync it should correct it. 

I also noticed the Interactive Cursors bouncing off the Math trace, and I have just fixed this also.

Edit: Think I found a solution that works! I just had to create a boolean that would delay a raw data capture until the Math channel was rendered... The Math Channel will still shudder when dragging, but that's due to extra Draw Wave events being generated... But if you are just observing, even down to 5uS/DIV the Math channel is lock-step with CH1 & CH2.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 15, 2014, 08:57:11 am
RichardK,
               I found a slightly more descriptive note on the function of the Autoset button in the DSO1000 series user manual:
It seems as if its primary function is to scan all the inputs and then automatically adjust the settings for the best display on the screen when the button is pressed. I could get this to work like this on the Hantek6022be 1.0.4 software.

The same function is then just used to properly display the built in 2V P-P wave when used to adjust the probe compensation.

Open6022be does not do this at present as I think you did mention.

Extract from user manual below:


Quote
To compensate probes
Perform this adjustment to match the characteristics of the probe and the channel input. This should be performed whenever attaching a probe to any input channel the first time.
1. From CH1 menu, set the probe attenuation to 10X (press CH1?Probe?10X).
Set the switch to X10 on the probe and connect it to CH1 of the oscilloscope.
When using the probe hook-tip, insert the tip onto the probe firmly to ensure proper connection.
Attach the probe tip to the probe compensator connector and the reference lead to the ground pin, Select CH1, and then press AUTO.
2. Check the shape of the displayed waveform
3. If necessary, use a non-metallic tool to adjust the trimmer capacitor of the probe for the flattest square wave being displayed on the oscilloscope.
4. Repeat if necessary.
WARNNING: To avoid electric shock while using the probe, be sure the perfection of the insulated cable, and do not touch the metallic portions of the probe head while it is connected with a voltage source

To display a signal automatically
The oscilloscope has an Auto feature that automatically sets up the Oscilloscope to best display the input signal. Using Auto requires signals with a frequency greater than or equal to 50 Hz and a duty cycle greater than 1%. Press the AUTO button, the oscilloscope turns on and scales all channels that have signals applied, and it selects a time base range based on the trigger source.
The trigger source selected is the lowest numbered input that has a signal applied. The oscilloscope has two-channels input. Connect a signal to the CH1 input.
1.Connect a signal to the oscilloscope.
2.Press AUTO. The oscilloscope may change the current setting to display the signal. It will automatically adjust the vertical and horizontal scaling, the trigger coupling, type, position, slope, level, and mode settings.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 15, 2014, 04:48:23 pm
Finally sat down and started editing the user manual in readiness for all the changes and improvements Richardk is adding. This is basically the original user manual with the changes:

Edit taken down: It was not showing a virus from this side, but others were getting warnings! See new post about 9 posts further on and Jumpshare new link.

I have just done a first edit up to page 12. Mostly this can really only be done when the software is complete, but starting now may be useful to somebody. If anyone wants to help with this please just enter in red or PM me the new text or upload somewhere and I will update the master as we go on.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on February 15, 2014, 05:40:33 pm
Warning !

That download site just tried to infect my PC with a Trojan. I have rebuilt my PC today and the first download was this one. Be careful. I will attach a screen shot from MS Secuirty Essentials.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 15, 2014, 05:44:12 pm
Warning ![/size

That download site just tried to infect my PC with a Trojan. I have rebuilt my PC today and teh first download was this one. Be careful. I will attach a screen shot from MS Secuirty Essentials.

That's Media Fire for you, they will let anyone advertise on their site and they don't screen for malicious advertisements.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 15, 2014, 05:46:17 pm
Warning ![/size

That download site just tried to infect my PC with a Trojan. I have rebuilt my PC today and teh first download was this one. Be careful. I will attach a screen shot from MS Secuirty Essentials.

Please clarify - are you are referring to the Document Mr. Matchless put on mediafire.com? or are you referring to the RichardK's binary download site?

My desktop also gone to hell (hung during Windows start up) this morning and I had a hard time getting on.  I plan to restore my machine after lunch too.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 15, 2014, 05:47:25 pm
My desktop also gone to hell (hung during Windows start up) this morning and I had a hard time getting on.  I plan to restore my machine after lunch too.

Sounds like a job for CCleaner.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on February 15, 2014, 05:53:31 pm
To be clear, the SITE that matchless has uploaded the edited manual to is the one with Virus issues.

I selected the manual download and it gave a file not found error and my AV went off saying that it was defending against an attack. The manual file never got downloaded, so the virus Payload came from the site when I pressed the 'Download' button (next to the manual details). NOT an advert or one of those cr*p bogus download buttons often found on sites.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 15, 2014, 05:59:30 pm
I am very sorry, I have taken it down immediately. :palm:  Can anyone suggest a safe way of doing this please?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 15, 2014, 06:00:08 pm
I am very sorry, I have taken it down immediately. :palm:  Can anyone suggest a safe way of doing this please?

jumpshare.com
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on February 15, 2014, 06:13:45 pm
No worries Matchless, not your fault and no damage done  :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 15, 2014, 07:22:14 pm
OK, thanks RichardK. Here is the manual roughly updated to page 12


http://jmp.sh/8f7hBHD (http://jmp.sh/8f7hBHD)

Hope this one works properly!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 16, 2014, 01:12:46 am
I am very sorry, I have taken it down immediately. :palm:  Can anyone suggest a safe way of doing this please?

No harm done here either.  I have a system "Ghost" image.  I regularly restore it and flush the junk off my system.  It was about time to do it anyhow.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on February 16, 2014, 01:22:30 am
Hi, I'm new to this site.  Please forgive me if I get some names wrong, or mention things that are already known.  I downloaded the PR13 build of the binary and tried it.  Here are my thoughts as an outsider:

1) Just having the horizontal scroll control on the top of the display makes this program infinitely more valuable than the stock Hantek software.  (I'd put the Clapping emoticon here if I could figure out how to insert it...)  All the rest is gravy.  RichardK, are you the only author?  I would like to send a small token of my appreciation to the contributors.

2) When I first ran the program on my laptop, I had the scope disconnected, so got the Device Not Found warning.  I clicked Yes to attempt Demo mode, and got a warning about No Default Printer being present.  The program then exited.  Ideally, it would be better for that to be a warning than a fatal error.  When I set a default printer to some dummy device, the program came up in Demo.  Seemed to work fine.  Glad that you have the Random waveform.  The others are so regular, it's hard to know where I'm scrolling.

3) I connected the scope, and started up the program for real.  Captured a one-shot waveform, and used the horizontal scroll bar to look at it.  I noticed that the Zoom function is like a display zoom; it magnifies in both the x- and y-dimensions.  I think that what I really want most of the time is horizontal zoom, with vertical zoom being a distant second, and both at once an even more distant third.

4) After scrolling to a part of the waveform other than the default center part, I changed the volts/div on CH1.  The display remained centered on the section of interest, but changed the vertical gain as expected.

5) I then tried changing the time/div.  Every time I did this, the display reset to center the trace.  Ideally, I would want it to stay centered on whatever I was viewing, just like changing the volts/div above.  Then if I wanted to gradually zoom in on an interesting part of the waveform, I could zoom partway in, re-center, and zoom in again.

6) The ultimate would be zoom in and out to a rectangle that I get to sweep out with my mouse.  I know that's asking for a lot, but ideally, if I did a zoom in by cursor select, the software would put the middle of the region I select at the center of the screen, and select "reasonable" units for timescale.  Like if I chose a region that translated into 7 uS per division, the software would show the trace to me at 10 uS per division, always favoring showing a little more when there is a choice.  Same thing with volts per division.  I dare to dream!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 16, 2014, 02:26:17 am
2) When I first ran the program on my laptop, I had the scope disconnected, so got the Device Not Found warning.  I clicked Yes to attempt Demo mode, and got a warning about No Default Printer being present.  The program then exited.  Ideally, it would be better for that to be a warning than a fatal error.  When I set a default printer to some dummy device, the program came up in Demo.  Seemed to work fine.  Glad that you have the Random waveform.  The others are so regular, it's hard to know where I'm scrolling.

That's not my error, and I wasn't even aware it existed until now... I looked around and it's the bane of just about every C++ Builder developer's existence.

Apparently, if a TPrintDialog component is placed *anywhere* in the project and the "Copies" property is set to anything above 0, when run on a Computer without a printer installed you will get a big fat Exception and ungraceful program termination.

I have set Copies to 0 by default, and in Print dialog Constructor if printers are found, I set it to 1 (as it's currently set to). Hopefully this resolves the issue.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 16, 2014, 07:19:42 pm
Latest Binary: http://jmp.sh/aqaEw5c (http://jmp.sh/aqaEw5c)

What's New:
-----------------------------------------------------------
1. Fixed a random crash/hang bug when using FFT.
2. FFT's now update properly on stopped waveforms.
3. Fixed an FFT Fundamental Negative Frequency bug.
4. Fixed a bug where zooming stopped waveforms would cause
   interactive cursors to go off trace.
5. Increased Time and Voltage division drop-down lengths.
6. Fixed a bug where Math Interactive Cursors would go off trace.
7. Fixed the Math Channel roll issue.
8. Disable AC Couple & Invert options when Acquire Stopped.
9. Fixed a crash on start up if no Printer is installed.
10. Fixed a bug where Measurements would not update on stopped waveforms.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 17, 2014, 11:57:44 pm
Latest Binary: http://jmp.sh/aqaEw5c (http://jmp.sh/aqaEw5c)

What's New:
-----------------------------------------------------------
1. Fixed a random crash/hang bug when using FFT.
2. FFT's now update properly on stopped waveforms.
3. Fixed an FFT Fundamental Negative Frequency bug.
4. Fixed a bug where zooming stopped waveforms would cause
   interactive cursors to go off trace.
5. Increased Time and Voltage division drop-down lengths.
6. Fixed a bug where Math Interactive Cursors would go off trace.
7. Fixed the Math Channel roll issue.
8. Disable AC Couple & Invert options when Acquire Stopped.
9. Fixed a crash on start up if no Printer is installed.
10. Fixed a bug where Measurements would not update on stopped waveforms.

5. Increased Time and Voltage division drop-down lengths.
Works nice!  A lot less scrolling needed now.  By the way, do you still plan to trim the zero's after the decimal?

7. Fixed the Math Channel roll issue.
b]Works very nice!  On Ch1 trigger, I can't get it to roll anymore.[/b]    I am not sure if Ch2 trigger and Normal trigger is done yet.  I can get it to roll if I change to Ch2 trigger (Ch2/Normal/Rise) with the same method as described before on 110KHz, 5uS/div, +-3V square wave.

New Issue - System hung (with Math):
1. Set Signal to 2.11MHz, 0 to 3V Square wave.
2. Have both Ch1 and Ch2 connected to the same signal source
3. Start PR14
4. Adjust trigger level to about mid-way of the square wave, I did that on both Ch1 and Ch2 planning to shortly switch triggering channel.  But the bug hit before I change anything with trigger.
5. Start MATH and just use the default "ADD"
6. At this point V/div, time/div, and trigger settings are still startup default
7. Change time/div to 2uS
8. Switch time/div to 5uS - now PR14 application is hung

This bug only hit when Math is on.  Once you hit the bug, X'out of the app doesn't totally return to normal.  I have a hard time restarting the system with Control-Alt-Delete. 

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 18, 2014, 12:17:37 am
New Issue - System hung (with Math):
1. Set Signal to 2.11MHz, 0 to 3V Square wave.
2. Have both Ch1 and Ch2 connected to the same signal source
3. Start PR14
4. Adjust trigger level to about mid-way of the square wave, I did that on both Ch1 and Ch2 planning to shortly switch triggering channel.  But the bug hit before I change anything with trigger.
5. Start MATH and just use the default "ADD"
6. At this point V/div, time/div, and trigger settings are still startup default
7. Change time/div to 2uS
8. Switch time/div to 5uS - now PR14 application is hung

This bug only hit when Math is on.  Once you hit the bug, X'out of the app doesn't totally return to normal.  I have a hard time restarting the system with Control-Alt-Delete.

Not able to replicate it yet, but I'll keep investigating.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 18, 2014, 07:22:17 am
New Issue - System hung (with Math):
1. Set Signal to 2.11MHz, 0 to 3V Square wave.
2. Have both Ch1 and Ch2 connected to the same signal source
3. Start PR14
4. Adjust trigger level to about mid-way of the square wave, I did that on both Ch1 and Ch2 planning to shortly switch triggering channel.  But the bug hit before I change anything with trigger.
5. Start MATH and just use the default "ADD"
6. At this point V/div, time/div, and trigger settings are still startup default
7. Change time/div to 2uS
8. Switch time/div to 5uS - now PR14 application is hung

This bug only hit when Math is on.  Once you hit the bug, X'out of the app doesn't totally return to normal.  I have a hard time restarting the system with Control-Alt-Delete.

Not able to replicate it yet, but I'll keep investigating.

Interesting!  Prior to reporting it, I was able to hit that even right after reboot.  I tried at least 5 times to make sure and get the "reproduce" steps log properly.

I will do another verification tomorrow, and this time, make sure I didn't do anything in between that I deem inconsequential and didn't log that.  If nothing new come up, I will try it with a different machine.  Stay tune, I will report back.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 18, 2014, 07:25:37 pm
Interesting!  Prior to reporting it, I was able to hit that even right after reboot.  I tried at least 5 times to make sure and get the "reproduce" steps log properly.

I will do another verification tomorrow, and this time, make sure I didn't do anything in between that I deem inconsequential and didn't log that.  If nothing new come up, I will try it with a different machine.  Stay tune, I will report back.

Rick

No worries, I think I fixed it :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on February 18, 2014, 07:36:26 pm
I recently saw a clone of the 6022BE for sale on e*ay and took a look at the 'manufacturers' web site. Instrustar is the name on the units. Take a look here:

http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506 (http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506)

There is also software available to download.

http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506 (http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506)

http://www.instrustar.com/download_detail.asp?nid=1536 (http://www.instrustar.com/download_detail.asp?nid=1536)

Manual is here:

http://20121015114.web47.ckuai.com/upload/user%20guide/ISDS205A%20User%20Guide.pdf (http://20121015114.web47.ckuai.com/upload/user%20guide/ISDS205A%20User%20Guide.pdf)

I have not tried the software on a 6022BE but thought this information may be of some interest ?

UPDATE: Having looked into this DSO, sadly it appears that the unit looks similar but is likely not the same as the 6022BE. Oh well, it was a thought.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 18, 2014, 07:56:00 pm
I recently saw a clone of the 6022BE for sale on e*ay and took a look at the 'manufacturers' web site. Instrustar is the name on the units. Take a look here:

http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506 (http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506)

There is also software available to download.

http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506 (http://translate.google.co.uk/translate?hl=en&sl=zh-CN&u=http://www.instrustar.com/product_detail.asp%3Fnid%3D1595&prev=/search%3Fq%3Disds205a%2Bsoftware%26biw%3D1024%26bih%3D506)

http://www.instrustar.com/download_detail.asp?nid=1536 (http://www.instrustar.com/download_detail.asp?nid=1536)

Manual is here:

http://20121015114.web47.ckuai.com/upload/user%20guide/ISDS205A%20User%20Guide.pdf (http://20121015114.web47.ckuai.com/upload/user%20guide/ISDS205A%20User%20Guide.pdf)

I have not tried the software on a 6022BE but thought this information may be of some interest ?

I seen this before also... Thanks for the links, downloading the English Version and the SDK for a look-over :)

Edit: I looked at the software (no it doesn't work with 6022BE hardware, shocker lol) and the SDK, and it's completely different from Hantek's stuff, so it wouldn't surprise me if the outside was the only thing in common with the 6022BE, I.E. totally different hardware.

Would be interesting none the less to have a peak inside one of these clones...

Also, their software package seems to be a One for All approach, instead of having a unique Application for each DSO model, they created one Application that works with several different models, so some features in software would not work on less capable models.

Also, they do not render their FFT inside the scope, it appears they just have a "Spectrum Analyzer" mode (in a separate tab) which makes the Scope look like a Spectrum Analyzer by doing a Fourier transform on the channel data.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 18, 2014, 09:00:47 pm
Interesting!  Prior to reporting it, I was able to hit that even right after reboot.  I tried at least 5 times to make sure and get the "reproduce" steps log properly.

I will do another verification tomorrow, and this time, make sure I didn't do anything in between that I deem inconsequential and didn't log that.  If nothing new come up, I will try it with a different machine.  Stay tune, I will report back.

Rick

No worries, I think I fixed it :)

Great!  I look forward to trying.

I also tested it a bit more.  Even the stock software has problem switching between 2uS (48Mhz) and anything <48MHz (5uS and up) when Math is on.  I hit this problem with 2 different machines.

I have a simpler "get to the problem" process now if you like to verify before building PR15:
1. Reboot
2. Hook up to scope's reference on both Ch.
3. Start Open6022 or stock, 2v/div, 500uS/div
4. Set trigger to about 1V (available only with Open6022BE) but leave trigger conditions unchanged (Ch1/Auto/Rising)
5. Start Math (A+B default is fine)
6. Switch to 2uS - program hangs

Alternative route - this one switch from 48MHz
5A. Before starting Math, Switch first to 2uS
6A. Start Math (A+B)
7A. It does not hang, switch to dot/vector and it draws fine...
8A. Switch to 5uS (away from 48MHz to 16MHz)
9A. Hung.

Both Stock and Open6022BE hits this problem.  It is to and from 48Mhz that it doesn't seem to like.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: MrAureliusR on February 18, 2014, 11:16:15 pm
WOW! RichardK -- you are amazing! I've been forgetting to check in on this thread over the last couple weeks (I've been busy with work) but man! The software is amazing now! This scope might actually get some use from me.

I'm upgrading to a Rigol DS2072 soon, and I already have an HP 54645D, but for quick measurements with my PC this software actually makes this thing worth having around.

RichardK, do you have a 'tip jar' PayPal set up or anything? I'd love to support your development! Or if there's any other way I can help (software/hardware) let me know! My C is alright, but I don't know what language you're using to develop this.... any way I can help just ask!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 19, 2014, 12:04:22 am
RichardK, do you have a 'tip jar' PayPal set up or anything? I'd love to support your development! Or if there's any other way I can help (software/hardware) let me know! My C is alright, but I don't know what language you're using to develop this.... any way I can help just ask!

Nah I have nothing like that set up, and it's being written in C++, specifically using CodeGear's RAD Studio (formally Borland C++ Builder)...

Once I have the major parts done I'm going to run through the code and clean it up, because this whole project has been a learn as you go, trial and error, and in some cases, reverse engineer the hell out of the stock software (simply because of the giant lack of information on the SDK)... Actually, I'm currently reverse engineering the stock software to figure out how the hell to use the HTDisplayDLL's HTDrawWaveInXY() for XY support.

As a result, the code is a bit messy and needs to be cleaned up and commented, and some parts rewritten (now that relevant information has been obtained).

After the code is cleaned up and properly documented with comments, I'll be uploading the whole thing to it's own source forge page, for anyone to modify it to their hearts content.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on February 19, 2014, 02:21:16 am
RichardK, You are a true Gentleman and Scholar  :-+

Thank you

Aurora
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 19, 2014, 03:16:50 am
Latest Binary: http://jmp.sh/2QnHfye (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.

Some information about XY Mode, in the stock software, X is hard coded to CH1 and Y is hard coded to CH2 and it renders off the entire
capture buffer.

I have provided two XY modes, one that renders off the entire capture buffer (like stock software) and a new mode that renders off the data in view (the part that would be visible in YT mode).

I must also note that the XY mode is a bit CPU intensive and the interface can get sluggish when the data capture is large, this is why I implemented an XY Visible mode, it will use a smaller data set while not bogging down the interface as much.

Also, instead of having hard coded X and Y sources, the X Channel Source is whatever Vertical Control A (the first control) is set to and the Y Channel Source is whatever Vertical Control B (the second control under Control A) is set to.

And for anyone who is interested, the SDK documentation for HTDisplayDLL doesn't provide any information at all on the DrawWaveInXY methods, so here is my reverse engineered function declarations for those interested in using them.

Code: [Select]
//Draw Wave in XY (C++)
DLL_API int WINAPI HTDrawWaveInXY(
HDC hdc,
int Left,
int Top,
int Right,
int Bottom,
short* ptrCH1RawData,
short* ptrCH2RawData,
short CH1Lever,
short CH2Lever,
unsigned long DataSize,
COLORREF color);

//Draw Wave in XY (New)
DLL_API int WINAPI HTDrawWaveInXYNew(
HDC hdc,
int Left,
int Top,
int Right,
int Bottom,
short* ptrCH1RawData,
short* ptrCH2RawData,
short CH1Lever,
short CH2Lever,
unsigned long DataSize,
COLORREF color);

Enjoy :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on February 19, 2014, 05:31:30 am
Great job!  I haven't been checking this forum every day, but just tried version PR15.  I confirm, the "no default printer" issue is fixed!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on February 19, 2014, 09:08:55 am
@RichardK:
Now that most of the stuff is working great could you please add one small improvement? ;)

It would be great if you could add onClick event on rotary buttons so that when you click on the button the dropdown next to it is selected.
This way it will be really easy to quickly change Volt/DIV and Time/DIV values up and down with mouse wheel.

Tnx for all the effort.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 19, 2014, 02:36:27 pm
@RichardK:
Now that most of the stuff is working great could you please add one small improvement? ;)

It would be great if you could add onClick event on rotary buttons so that when you click on the button the dropdown next to it is selected.
This way it will be really easy to quickly change Volt/DIV and Time/DIV values up and down with mouse wheel.

Tnx for all the effort.

Done.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on February 19, 2014, 02:52:42 pm
Tnx. Can't wait for the next release. :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 20, 2014, 12:02:34 am
@ RichardK: with every release of your work using the 6022BE gets more and more confortable! Great work!

Robert
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 20, 2014, 06:48:43 pm
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.
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, 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.

If I select Reference as trigger source CH1 and CH2 still jump around (with no AC coupling) the software also freezes after a short while and has to be cleared in task manager. Selecting AC coupling (before the program freezes) agitates the CH1 and CH2 channels more and the program freezes after a short while as well.

Hope my explanation is not too jumbled!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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 :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless 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! :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 21, 2014, 11:46:31 pm
Latest Binary: http://jmp.sh/2QnHfye (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).

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: sandos 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?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: sandos 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

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O 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.]
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O 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!)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rasz on February 24, 2014, 12:42:05 am
RichardK have you considered collaborating with sigrok.org people?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: MrAureliusR 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PioB 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

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on February 24, 2014, 07:28:02 pm
if(MemSize >= 1) ...

Outch ...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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 (http://www.embarcadero.com/products/cbuilder) which uses VCL (http://en.wikipedia.org/wiki/Visual_Component_Library) (Visual Component Library).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rasz 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law 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
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O 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.   :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless 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)?

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 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. 
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK 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.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 25, 2014, 09:35:09 pm
Do you know if anyone has figured out why two drivers are installed (one is hidden)?

One quietly loads the firmware into the device (it has no internal storage for the firmware, so it's stored in one of the device drivers).

The second driver is for communicating with the active device (now loaded with firmware) and it acts as a communication proxy between the device and HTMarch.dll.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 26, 2014, 03:27:30 am
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.
...

I must have been too preoccupied hunting for the "rolling trace".  I totally missed the v/div adjustment for math.

I have to check that out again.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on February 26, 2014, 03:32:27 am
Rick,
      Just wondering, have you tried with any other remote desktop program? Maybe the free Teamviewer?
...

No, I have not tried Teamviewer.  Time has not allowed me to dig into this RDC issue much yet.  Thanks for pointing that out - I should give that a try.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 26, 2014, 05:51:20 am
Do you know if anyone has figured out why two drivers are installed (one is hidden)?

One quietly loads the firmware into the device (it has no internal storage for the firmware, so it's stored in one of the device drivers).

The second driver is for communicating with the active device (now loaded with firmware) and it acts as a communication proxy between the device and HTMarch.dll.

Ah! Thanks Richard, I recalll someone said the firmware is in the driver, so thats it!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 26, 2014, 06:49:15 pm
Latest Binary: http://jmp.sh/CxPNMVk (http://jmp.sh/CxPNMVk)

What's New:
-----------------------------------------------------------
1. Clicking on Vertical Control Knobs will now select the Vertical Control lists.
2. Fixed a random hang bug.
3. Fixed some Trigger issues.
4. Added an option in Reference Function Generator to select which channel to trigger
   Reference waveforms off of.
5. Added a Digital Phosphor/Persistence effect to Display->Waveform->Render menu.
6. Fixed a Lever selection/dragging bug.
7. Implemented FFT Scale in dB option.
8. Fixed an FFT Rendering bug where the generated FFT Image would not stretch to fit
   the entire Scope width.
9. Fixed an FFT crash while changing Frequency Bins.
10. Implemented Default Settings Menu Item & Toolbar Button.
11. Renamed some Menu Items and moved a few things around.
12. Implemented the Auto Setup feature (Menu & Toolbar Buttons available).
13. Removed dependance on HTDisplayDll.dll (file no longer required to run).

Notes:
1. The Digital Phosphor mode has a "Phosphor Persistence" adjustment which you can adjust in conjunction with the Waveform brightness which will give you more control over the effect. This effect (as well as waveform brightness adjustment) does not work on 64bit Windows sorry, this is due to a Microsoft oversight in their AlphaBlend() API function. Some day I might do my own AlphaBlend function, but not any time soon.
2. The Auto Setup feature is implemented but may not behave exactly like stock software's Auto Setup and it might not do what you expect in certain situations as I have not fully tested it yet.
3. The HTDisplayDll DLL is no longer required to run Open6022BE due to hours of reverse engineering.  :-/O

Enjoy :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: sandos on February 26, 2014, 08:29:18 pm
For some reason, this version is virtually unusuable for me, it hangs almost at once. Well, it doesnt hang as much as it just stops drawing anything. Btw what does "Debug Information" do, anyway?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on February 26, 2014, 08:42:24 pm
It works fine on my pc. (Win7 32bit)

I specialy like clickable knobs and Digital Phosphor.

Tnx Richard. :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 26, 2014, 08:47:52 pm
RichardK,
              Running Windows 8 (32bit) and the latest version crashes after about 6 seconds....
 Hope this is just a small glitch and itching to see it in action with all those improvements you listed!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 26, 2014, 09:01:40 pm
RichardK,
              Running Windows 8 (32bit) and the latest version crashes after about 6 seconds....
 Hope this is just a small glitch and itching to see it in action with all those improvements you listed!

Can you detail the crash more? What kind? Hang? or Access Violation, etc...? If it hangs, can you move the form, or interact with controls?

Does it crash even if you don't change any settings?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 26, 2014, 09:03:23 pm
For some reason, this version is virtually unusuable for me, it hangs almost at once. Well, it doesnt hang as much as it just stops drawing anything. Btw what does "Debug Information" do, anyway?

Working fine on all my machines here... Very odd.

I'm making a new build shortly with Timeouts in my Lock() methods... Hopefully this addresses the issue as it seems to be some race condition which happens to some people but not all...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 26, 2014, 09:16:27 pm
Richardk,
              I tried it on Windows 7 and the same failure. The program stops running and the flashing green led flashes red. The waveforms disappear and if I click on the v/div button I cannot turn it, but the voltage in the window changes properly.
If I manage to "turn" the button from the default 2V to say anything under 1V before it fails,  it will then stay up and running until I "turn" the button over 1V or 2V then it fails again. Its hard to sort of catch it in time to reproduce the fault.
Hope this little info helps.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 26, 2014, 09:32:24 pm
Reuploaded: http://jmp.sh/6iXvKER (http://jmp.sh/6iXvKER)

Hopefully this corrects the issues because I'm running out of ideas lol...  |O
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 27, 2014, 07:20:08 am
RichardK,
            It seems as if you nailed it. It seems stable now. I will do some more testing later today.
Unfortunately it still does it, but takes a bit longer before it fails!

Thanks, you are doing great work!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 27, 2014, 12:13:54 pm
RichardK,
              The traces disappearing of the screen is still happening. They disappear after 3 to 4 seconds mostly and sometime a little bit longer. I am on Win8 and have both probes to the reference output tag, then I run OPEN6022BE:
1) If I can grab the Ch1 V/Div black spot on the yellow button in time and turn it to something below 2V it seems to stay stable and run properly.
2) If I can drag the Trigger pointer away from the bottom of the wave on Ch1 in time then the programs seems stable. Any length of time thereafter if I drag the trigger pointer to the lower part of the wave, where the noise is, the failure occurs again.
3) At times trying to do above the GUI freezes and the yellow and blue knobs disappear and I have to end task in task manager.

I can try to help as far as I can, but you will have to advise me on what to do and how to do it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 27, 2014, 05:01:16 pm
Hopefully this build does the trick: http://jmp.sh/CxPNMVk (http://jmp.sh/CxPNMVk)

 :-BROKE
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 27, 2014, 05:29:56 pm
RichardK, I am happy to report that I do not experience this on either win7 or Win8 any more! :clap:

Click and using the mouse scroll wheel is really very nice!

On the original software one could click the mouse cursor at the position you wanted the button to turn. This obviously does not work on OPEN6022BE, but for some reason it sometimes attempts to work when you click the button. The black dot may or may not move fully or partially to the cursor position. Its hard to reproduce.

Thanks again!!!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 27, 2014, 05:45:00 pm
RichardK, I am happy to report that I do not experience this on either win7 or Win8 any more! :clap:

Good to hear  :phew:

Quote
On the original software one could click the mouse cursor at the position you wanted the button to turn. This obviously does not work on OPEN6022BE, but for some reason it sometimes attempts to work when you click the button. The black dot may or may not move fully or partially to the cursor position. Its hard to reproduce.

I just implemented clicking to reposition knob, so for the next release it will operate as it does in the stock software. Thanks for the suggestion :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on February 27, 2014, 06:00:20 pm
I must add, setting the Phosphor Persistence brings about another dimension when zooming in on a waveform!! I really like that!

I can just repeat myself - Excellent work!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PedroDaGr8 on February 27, 2014, 06:36:07 pm
I decided to try this out even though I dont have a scope. Just because it seems like you are making huge headway RichardK. I must say this thing is super fluid and I can see this device being SUPER useful for a variety of people now. It makes what was a buggy budget scope into a usable entry-level device.

A couple things I noticed in demo-mode.

 The first relate to the noise functions:
1) Horizontal noise doesn't work with the square wave
2) Vertical noise seems to be dependent on the value of the points. For example, a square wave from 0-2V will have loads of noise at the top but zero noise in the valley.

Now these both may have be functioning as intended but they just seemed a bit "off" to me. If it was the way you intended keep them as is because clearly you know what you are oding.

The others deal with DPO mode, it would be nice to have a clear screen button. Otherwise its very easy to get displays that look like this:
(http://i.imgur.com/mjAmg2j.png) (http://imgur.com/mjAmg2j)
 ;D

Also, turning off a channel and/or clearing it should remove the wave. it looks like it turns off the channel but doesn't remove the DPO left-overs.


I have to say, after playing with yoru software I'm REALLY considering picking one of these up. These have turned into a hidden gem of a device thanks to your software and hardwork. Huge props for what you have done.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: xxzzyzx on February 27, 2014, 06:49:41 pm
Had to register just to Chip in...

Received my 6022BE today! Having installed the stock software, I quickly decided it wasn't very good, and a potentially crippling limitation to these natty bits of kit. I was looking for a Linux solution (which there doesn't seem to be one, FWIW) when I stumbled upon this thread and was happy to see that it was active.

RichardK, your Open6022BE is a fantastic piece of software, many times better than the one Hantek supply.  I just wanted to echo the others in saying good work, and thanks for your hard work. Bravo.

I shall be putting it through it's paces in the coming days, so if I can chip in bug finding / feature ideas etc. I will!

Thanks again,
JamesR
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on February 27, 2014, 07:07:17 pm
While I was googling around I found what appears to be the official Hantek help forum. It looks fairly active.

http://www.hantek.org/asken/ (http://www.hantek.org/asken/)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 27, 2014, 07:38:01 pm
While I was googling around I found what appears to be the official Hantek help forum. It looks fairly active.

http://www.hantek.org/asken/ (http://www.hantek.org/asken/)

Good find, I'm not able to reply to any of the 6022BE related questions though... The reply button doesn't appear to do anything...

I did add a loaded question though about the pre-trigger acquisition  >:D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on February 27, 2014, 07:47:59 pm
Be nice if they sent you some samples to play with.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 27, 2014, 07:59:32 pm
Had to register just to Chip in...

Received my 6022BE today! Having installed the stock software, I quickly decided it wasn't very good, and a potentially crippling limitation to these natty bits of kit. I was looking for a Linux solution (which there doesn't seem to be one, FWIW) when I stumbled upon this thread and was happy to see that it was active.

RichardK, your Open6022BE is a fantastic piece of software, many times better than the one Hantek supply.  I just wanted to echo the others in saying good work, and thanks for your hard work. Bravo.

I shall be putting it through it's paces in the coming days, so if I can chip in bug finding / feature ideas etc. I will!

Thanks again,
JamesR

Thanks and welcome to the forums :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on February 27, 2014, 08:05:20 pm
1) Horizontal noise doesn't work with the square wave

Yeah that's a limitation of the way I'm generating them, so I'm thinking about having two types, a pure square wave which will work like other functions because it will be derived from a sine wave, but the caveat being no ability to change duty cycle, and the square wave already implemented which is not derived from a sine wave and will have duty cycle adjustments but no horizontal noise.

Quote
2) Vertical noise seems to be dependent on the value of the points. For example, a square wave from 0-2V will have loads of noise at the top but zero noise in the valley.

I have noticed this also, it seems to be some quirk in the Hantek draw wave function, the noise will appear but at a much higher level (just keep ticking the noise up and it will eventually appear).

Quote
The others deal with DPO mode, it would be nice to have a clear screen button. Otherwise its very easy to get displays that look like this:
(http://i.imgur.com/mjAmg2j.png) (http://imgur.com/mjAmg2j)
 ;D

Also, turning off a channel and/or clearing it should remove the wave. it looks like it turns off the channel but doesn't remove the DPO left-overs.

I have added a clear display option in the next release, thanks for the feedback :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on February 27, 2014, 09:19:53 pm
@RichardK,

I have thanked you for your efforts previously but wanted to say thank you again for the amazing progres you have been making. I am no coder, so have no idea how much work is involved in producing your software application, but I feel sure it will be a lot ! Your superb efforts, and the speed with which you have developed this software are greatly appreciated.

Cheers

Aurora
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: jun on February 28, 2014, 01:09:24 am
Hello, I am new to electronics, and wanted a cheap oscilloscope so I can see if this is a field I want to invest in. However after receiving it today I found out that the software that came with it doesn't work with my computer. So I would like to thank you for your work on this software (and for enabling me to debug my circuits!) So far it works fantastically and if I happen to find any bugs I will let you know.

Thanks again,
     -Jun
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: DarrenS on February 28, 2014, 12:37:36 pm
@RichardK

I just wanted to add my thanks to everyone else's for the work you've done on this software so far.

I'm just getting into the hardware side of things (my day job is software engineering specialising in UI development for financial markets which I've been doing for the last 20+ years) and I wanted a cheap entry level scope. I was initially put off the 6022BE because of the rubbish stock software until I came across this thread and the work you've been doing. As a direct consequence of your Open6022BE software I bought the hardware :)

Keep up the good work and I look forward to seeing the project on sourceforge/github if all goes to plan.

Thanks,
Darren
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: sandos on February 28, 2014, 07:23:21 pm
It now works very well for me too!

There is one thing which is worse compared to the stock software: triggers go crazy at 48Mhz, and this I know, but with stock it always start working again at 16Mhz. In your software I have to slow down a lot for triggering to be reliable again.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: sandos on February 28, 2014, 07:45:01 pm
Also, surely this should behave a lot more like the logic analyzers based on ez-usb, ie. once below the USB speed threshold you have an "infinite" buffer on the PC end, and that should mean 24Mhz.

I wonder if the http://sigrok.org/wiki/Fx2lafw (http://sigrok.org/wiki/Fx2lafw) firmware could be made to run on this? I understand the chip is in the same family...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 28, 2014, 10:03:25 pm
I did add a loaded question though about the pre-trigger acquisition  >:D

Are you sure?  I searched for 6022BE issues, and didn't see it.  Just someone trying to find drivers.

I did register there, but wasn't able to submit my application.  I had to 'sumbit' it.  ;)  1+1 = 10.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on February 28, 2014, 10:06:41 pm
It's there

http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937 (http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 28, 2014, 10:12:22 pm
As a direct consequence of your Open6022BE software I bought the hardware :)

I am quite sure you won't be the last to say that.  As the word spreads, I'm confident Hantek will sell a lot more of these units than they were in the past.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 28, 2014, 10:15:04 pm
It's there

http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937 (http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937)

Thanks, pickle!  I see that Hantek's web software works about as well as their DSO software.  ;)

http://www.hantek.org/asken/iasksearch.aspx?word=6022BE&submit=Search (http://www.hantek.org/asken/iasksearch.aspx?word=6022BE&submit=Search) does NOT find it. 

Though it can be plainly seen if you navigate to the "DSO-5200 USB" Section.  Gee, why didn't I think of that?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 28, 2014, 10:19:55 pm
Also, surely this should behave a lot more like the logic analyzers based on ez-usb, ie. once below the USB speed threshold you have an "infinite" buffer on the PC end, and that should mean 24Mhz.

The units you're referring to are single-channel.  (Two channel units do NOT run at 24MHz.)  Remember, the 6022BE is running two channels, so 16MSa/sec sampling is at 32 MB/sec.  (Also, there is no 24 MHz option in the Hantek DLL.  It goes directly from 48MHz to 16.)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 28, 2014, 10:27:11 pm
There is one thing which is worse compared to the stock software: triggers go crazy at 48Mhz, and this I know, but with stock it always start working again at 16Mhz. In your software I have to slow down a lot for triggering to be reliable again.

How far do you have to slow down?  (And is it really the slowing down that stabilizes it?  Or just that some time has passed, and the buffers have had time to flush?  Probably not related, but thought I'd ask.)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: sandos on February 28, 2014, 10:38:38 pm
Also, surely this should behave a lot more like the logic analyzers based on ez-usb, ie. once below the USB speed threshold you have an "infinite" buffer on the PC end, and that should mean 24Mhz.

The units you're referring to are single-channel.  (Two channel units do NOT run at 24MHz.)  Remember, the 6022BE is running two channels, so 16MSa/sec sampling is at 32 MB/sec.  (Also, there is no 24 MHz option in the Hantek DLL.  It goes directly from 48MHz to 16.)

I am aware, but does disabling a channel on the 6022 not mean its single-channel, or is the USB part unaffected maybe?

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on February 28, 2014, 10:58:51 pm
The units you're referring to are single-channel.  (Two channel units do NOT run at 24MHz.)  Remember, the 6022BE is running two channels, so 16MSa/sec sampling is at 32 MB/sec.  (Also, there is no 24 MHz option in the Hantek DLL.  It goes directly from 48MHz to 16.)

I am aware, but does disabling a channel on the 6022 not mean its single-channel, or is the USB part unaffected maybe?

No, disabling a channel on the 6022 UI doesn't make it single-channel (unfortunately).  AFAICT (from my reading some time back), the Hantek DLL has no option to disable either channel, so, as you say, the USB part is unaffected.  It would be nice if you could double the speed by turning off one channel.  But the driver that gets loaded into the 6022BE would also have to support that transfer mode.

Perhaps I missed something, and Richard will tell me I'm FOS.  :D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 01, 2014, 02:11:40 am
The units you're referring to are single-channel.  (Two channel units do NOT run at 24MHz.)  Remember, the 6022BE is running two channels, so 16MSa/sec sampling is at 32 MB/sec.  (Also, there is no 24 MHz option in the Hantek DLL.  It goes directly from 48MHz to 16.)

I am aware, but does disabling a channel on the 6022 not mean its single-channel, or is the USB part unaffected maybe?

No, disabling a channel on the 6022 UI doesn't make it single-channel (unfortunately).  AFAICT (from my reading some time back), the Hantek DLL has no option to disable either channel, so, as you say, the USB part is unaffected.  It would be nice if you could double the speed by turning off one channel.  But the driver that gets loaded into the 6022BE would also have to support that transfer mode.

Perhaps I missed something, and Richard will tell me I'm FOS.  :D

The software acquires both channel data at the same time, from the application, to the HTMarch.dll all the way down to the driver... Trust me, I went down the rabbit hole and almost didn't make it back out  :scared:

When you "disable" a channel, all you are doing is simply not rendering the data anymore... The software is still acquiring it and storing it into memory, it's just not calling the Draw Wave function until you enable the channel again.

As far as I know, down to the driver level, it's not possible to get only one channel's worth of data, they come bundled.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: KindleFlame on March 03, 2014, 02:28:53 am
Another thanks to RichardK from a newcomer, I guess. I'm an international ece student needing a cheap portable scope, and this scope might just be on the edge of measuring SPI traces.

And honestly, I'm buying it only because of your contributions to the software, making it usable. Thanks! Tell me if I can buy you a beer somewhere.

On something more helpful and the only contributions I can make, minor typo.  :D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 03, 2014, 03:56:49 am
I noticed that the Voltcraft DSO-2020 is the exact same thing as the 6022BE, and the software looks identical, however due to code like below:

Code: [Select]
HANDLE GetDeviceHandle(WORD DeviceIndex)
{
 char Src[63];
 char FileName[63];
 memset(&Src, 0, 63u);
 memset(&FileName, 0, 63u);

 //Create Device Identifier
 sprintf(Src, "d6022-%d", DeviceIndex);
 strcat(FileName, "\\\\.\\");
 strcat(FileName, Src);

 HANDLE Hnd = CreateFileA(FileName, GENERIC_WRITE, FILE_SHARE_WRITE, NULL, OPEN_EXISTING, NULL, NULL);
 if(Hnd != (HANDLE)-1 && Hnd)
 {
CloseHandle(Hnd);
return NULL;
 }

 //Return Handle
 return Hnd;
}

Even though the hardware, firmware and software are pretty much identical, the code used to get the device handle for a 6022BE will fail when it's looking for a DSO2020 due to the different hardware IDs.

If I ever get the HTMarch.dll fully reversed engineered (I have partially reversed it so far) then I can make Open6022BE support the re-branded hardware as well.

I downloaded the Voltcraft DSO-2020 software and all the files ironically have the same names, HTDisplayDll, HTMarch, etc... however the HTMarch.dll has the different Hardware ID: "d2200-%d"
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on March 03, 2014, 07:56:15 am
Hi.

Perhaps this will help... Cypress usb chip reads VID/PID from EEPROM chip.
It's easy to read and change this VID/PID values: http://www.jwandrews.co.uk/2011/12/saleae-logic-analyser-clone-teardown-and-reprogramming/ (http://www.jwandrews.co.uk/2011/12/saleae-logic-analyser-clone-teardown-and-reprogramming/)

I've done it successfully on my usb scope Hantek 5200A (because it stopped working) and it has the same usb chip & eeprom setup, just different values.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 03, 2014, 11:53:39 am
RichardK,
              I have a list of some little funnies I have noted to date. I am running Win8 and your latest binary. Some are just typos, some are issues that I have had from start, but have listed all as they still seem to be a problem:

1) If full screen is selected the GUI does not display the menu, tool bar and button bar.
Pressing the Esc button returns correctly to smaller display with toolbars and controls panel.
Clicking the small top left hand icon and selecting Restore the display is smaller, but no toolbars or controls are shown,
you have to right click on the display and select Windows Mode to get your toolbar and controls back.

2) Noise issue on base noise with probes grounded still exist:
  Settings: Both probes grounded to front ground lug, set to X1, 500uS, both channels 20mV set Zoom to level 19
                 Ch1                     Ch2
   20mV     Noise              No Noise
   50mV     Noise              No Noise
  100mV    Noise              No Noise
  200mV    Noise spikes   Noise spikes
  500mV    Noise              Noise
      1V       Noise              Noise
      5V       No Noise         No Noise
    10V       No Noise         No Noise
 
3) Autoset is not taking one to best settings option, always to 2.000uS only (I think you are aware of this)

4) Trigger Mode Dropdown box has only one selection. Why have a dropdown then?

5) Corporation is mistyped in About

6) Trigger Sweep One shot freezes waveform display, shows "Stop" and red led flashes on device. Unable to resume if setting is changed back
to Normal or Automatic, but resumes if Factory default is pressed after changing back to Normal or automatic. Pressing Autoset also restarts
the program after freezing.

8) When placing a cross, vertical or horizontal cursor line without Enabled, the cursors are placed, but needs two clicks on None to remove.
The automatic placing of cursors seem a bit funny with "Enabled".

9) Auto Setup (Toolbar menu) and Auto Settings (Icon) are the two different names for the same thing.

10) Waveform type is called Vector in the toolbar menu and Line in the icon button menu for the same thing.

11) Print preview screen underlines the words when typing in Notes, can the underline be removed?

12) Can colors be changed in Print Preview just for the printout?

13) When loading Factory settings the window asks to confirm and "wan't" is mistyped in this window.(already reported by OP)

Hoping this feedback helps you.

Thanks again for what you are doing!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 03, 2014, 04:39:32 pm
1) If full screen is selected the GUI does not display the menu, tool bar and button bar.
Pressing the Esc button returns correctly to smaller display with toolbars and controls panel.
Clicking the small top left hand icon and selecting Restore the display is smaller, but no toolbars or controls are shown,
you have to right click on the display and select Windows Mode to get your toolbar and controls back.

Not able to replicate.

Quote
2) Noise issue on base noise with probes grounded still exist:
  Settings: Both probes grounded to front ground lug, set to X1, 500uS, both channels 20mV set Zoom to level 19
                 Ch1                     Ch2
   20mV     Noise              No Noise
   50mV     Noise              No Noise
  100mV    Noise              No Noise
  200mV    Noise spikes   Noise spikes
  500mV    Noise              Noise
      1V       Noise              Noise
      5V       No Noise         No Noise
    10V       No Noise         No Noise

No idea why the stock software is behaving differently.

Quote

3) Autoset is not taking one to best settings option, always to 2.000uS only (I think you are aware of this)

I am aware, the Autoset is going to need to be tweaked at some point, it's very quirky right now.

Quote
4) Trigger Mode Dropdown box has only one selection. Why have a dropdown then?

I am just mirroring the stock software, for thoroughness... Maybe Hantek plans on implementing other trigger modes some day? Hopefully along with pre-trigger Acquisition.

Quote
5) Corporation is mistyped in About

Fixed.

Quote
6) Trigger Sweep One shot freezes waveform display, shows "Stop" and red led flashes on device. Unable to resume if setting is changed back
to Normal or Automatic, but resumes if Factory default is pressed after changing back to Normal or automatic. Pressing Autoset also restarts
the program after freezing.

Not sure, have to investigate this further.

Quote
8) When placing a cross, vertical or horizontal cursor line without Enabled, the cursors are placed, but needs two clicks on None to remove.
The automatic placing of cursors seem a bit funny with "Enabled".

Unable to reproduce this issue... Not able to place any line-style cursors without Enabled, and when line-style cursors are Enabled, clicking None once removes them.

Quote
9) Auto Setup (Toolbar menu) and Auto Settings (Icon) are the two different names for the same thing.

Fixed.

Quote
10) Waveform type is called Vector in the toolbar menu and Line in the icon button menu for the same thing.

Fixed.

Quote
11) Print preview screen underlines the words when typing in Notes, can the underline be removed?

Just mirroring stock software, will add an option to remove underline.

Quote
12) Can colors be changed in Print Preview just for the printout?

Not yet, perhaps soon :)

Quote
13) When loading Factory settings the window asks to confirm and "wan't" is mistyped in this window.(already reported by OP)

Fixed.

Thanks for the feedback :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 03, 2014, 05:24:27 pm
Thanks,  I will try those that you cannot reproduce on another PC when an opportunity comes along. That full screen really has me puzzled.
Thanks my list is much shorter now :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 03, 2014, 08:58:42 pm
RichardK,
               I had a look at the cursors again and hopefully I have described the issue a bit better.

When placing a cross, vertical or horizontal cursor line without clicking "Enabled", the cursors are placed, but needs two clicks on None to remove.
Cross does not place a cursor without clicking “Enabled” the first time, but if you try a second time it places a cursor
Both horizontal and vertical place a cursor first try without clicking “Enabled” These cursors do not go away when you click “None”, but if you try clicking “None” a second time the cursors are removed.
The automatic placing of cursors seem a bit funny with "Enabled".

If you only click "Enabled" you get a Cross cursor without selecting Cross, Horizontal or Vertical?

Hope this helps you to reproduce this.

Thanks!




Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 03, 2014, 10:20:34 pm
RichardK,
               I had a look at the cursors again and hopefully I have described the issue a bit better.

When placing a cross, vertical or horizontal cursor line without clicking "Enabled", the cursors are placed, but needs two clicks on None to remove.
Cross does not place a cursor without clicking “Enabled” the first time, but if you try a second time it places a cursor
Both horizontal and vertical place a cursor first try without clicking “Enabled” These cursors do not go away when you click “None”, but if you try clicking “None” a second time the cursors are removed.
The automatic placing of cursors seem a bit funny with "Enabled".

If you only click "Enabled" you get a Cross cursor without selecting Cross, Horizontal or Vertical?

Hope this helps you to reproduce this.

Thanks!

I just made some changes to that code so when you click Cross, Horizontal or Vertical and the Line mode isn't enabled, it will enable it for you.

This should clear up any issues. *fingers crossed*

I also made some changes to the fullscreen/restore code to sleep for a bit (to let threads catch up) and to let the main thread process any unhandled messages... This is the only thing I can think might correct it, but it's hard to tell if it's going to work or not because I am not able to replicate it here.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 04, 2014, 06:43:26 am
Thanks, I will test when the next binary is available!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 04, 2014, 07:11:56 am
Has anyone checked out the actual screen update rate and blanking time? I know it will vary. I'm not sure if the term "blanking time" is correct for a usb scope. I mean the minimum amount of time between captures.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 07, 2014, 05:23:20 pm
I have tried to do some further work on the user manual for RichardK's OPEN6022BE. This is only the part that describes the use of the menu items. There are some items I am not clear on, due to my limited and very rusty experience with oscilloscopes. Those are in red and I will appreciate any feedback, especially some help with describing those functions still pending.
The Document is in .docx format.

Thanks in advance.

Download: http://jmp.sh/q0RHv19 (http://jmp.sh/q0RHv19)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PedroDaGr8 on March 07, 2014, 09:54:00 pm
I have tried to do some further work on the user manual for RichardK's OPEN6022BE. This is only the part that describes the use of the menu items. There are some items I am not clear on, due to my limited and very rusty experience with oscilloscopes. Those are in red and I will appreciate any feedback, especially some help with describing those functions still pending.
The Document is in .docx format.

Thanks in advance.

Download: http://jmp.sh/q0RHv19 (http://jmp.sh/q0RHv19)

Nice work so far. If I have time this weekend I will import some pictures and do a bit of editing on of my own.

As for the clear function see my post here:
https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg396515/#msg396515 (https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg396515/#msg396515)

I requested the clear function.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 08, 2014, 07:50:08 am
PedroDaGr8,
                    Thanks! That will help me a lot. I was intending to do the user manual in 3 parts and them merge them into one document when completed. I have
already have semi-revised the introductory part for the user manual. The final part will consist of actual step by step guides to do certain tests with the 6022BE.
Much appreciated

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: effbiae on March 08, 2014, 03:22:22 pm
Hi Everyone,

I'm expecting delivery of my 6022 early next week - and I'm even more excited now, reading this thread.  I knew what I was getting into with the 6022 - I did my research - for the money, this scope is value.  I'm looking at audio frequency (maybe a little higher), so the hardware should do the job.

I started down the soundcard oscilloscope road, but I don't recommend that (even though you would think it would be ideal for the audio range).

Thanks to those modding the hardware and hacking on software.  I'm mostly a software developer, so RichardK, let me know if you'd like any help. 

Thanks,
Jack.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 08, 2014, 06:26:34 pm
Latest Binary: http://jmp.sh/h2xSceX (http://jmp.sh/h2xSceX)

What's New:
-----------------------------------------------------------
1. Fixed a race condition which might cause random hangs.
2. Fixed a bug in the grid brightness dialog which caused part of the slider range to have no
   effect on brightness.
3. Made Horizontal and Vertical Knobs "position-clickable" (click to set position).
4. Implemented loop timeouts to prevent infinite loops in Multithread Lock code (Hang prevention).
5. Fixed a bug where disabling the Math Channel could cause a hang.
6. Added detailed Calibration Failure error messages.
7. Made waves continuously draw in Phosphor mode when Acquire stopped (To prevent smearing).
8. Added a Clear option to the Display menu which will clear the screen (good for Phosphor mode).
9. Added a Reset Interactive option to the Cursors Menu which reset the Interactive Cursor positions
   to their default locations.
10. Overhauled Rendering code, much easier to read and performance increased.
11. Fixed a few Dialog typos.
12. Fixed some Menu/Toolbar label inconsistencies.
13. Fixed some Trigger issues.
14. Trigger Single Shot mode now shows last captured waveforms while waiting for trigger, instead of
   not showing any waveforms at all.
15. Changed rendering so only Waveform's and FFT are effected by Digital Phosphor mode (Not cursors,
   text, etc...).
16. Fixed some Menu/Toolbar checkbox issues.
17. Made selecting either of the three different Line Cursor Modes enable Line Cursors if Line Cursors
   are not already enabled.
18. Added Pure Square waves (Generated from Sine Waves) to Demo Mode & Function Generator.
19. Disabled Horizontal noise for Artificial Square Waves (it's not supported).
20. Improved FFT performance when using a Window Function (precalculated window functions).
21. Added Sweep Controls to Demo Mode (sweep any demo mode property).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 09, 2014, 03:09:27 am
Latest Binary: http://jmp.sh/h2xSceX (http://jmp.sh/h2xSceX)

What's New:

Wow!  That's a pretty massive update.  Excellent!

Quote
14. Trigger Single Shot mode now shows last captured waveforms while waiting for trigger, instead of
   not showing any waveforms at all.

While in general I think that this 'preserve until replaced' strategy is superior, I can think of some cases where this may not be the preferred choice.  Just a thought.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 09, 2014, 03:19:37 am
Wow!  That's a pretty massive update.  Excellent!

I'm tying up all the loose ends and fixing minor things here and there, so the changelog tends to get bloated at this stage.

Quote
While in general I think that this 'preserve until replaced' strategy is superior, I can think of some cases where this may not be the preferred choice.  Just a thought.

I'm mirroring the stock software for now, later on I'll look at some alternative ideas.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 09, 2014, 03:53:06 am
@RichardK

When clicking on the measurement checkboxes it would be nice if the pane that shows the actual measurement opened up far enough to see the first measurement and perhaps half of the second. That would give the user a visual indication that he may have to adjust the pane to see all the measurements selected selected.

It's really looking good, congrats. I honestly have no need for one of these but ordered one just so I could see how it works with the software. Who knows, maybe I'll use it all the time.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 09, 2014, 04:03:48 am
@RichardK

When clicking on the measurement checkboxes it would be nice if the pane that shows the actual measurement opened up far enough to see the first measurement and perhaps half of the second. That would give the user a visual indication that he may have to adjust the pane to see all the measurements selected selected.

Done.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on March 09, 2014, 04:15:17 am
Latest Binary: http://jmp.sh/h2xSceX (http://jmp.sh/h2xSceX)

What's New:
-----------------------------------------------------------
1. Fixed a race condition which might cause random hangs.
2.
...

Wow, quite a list of bug fix and enhancements.  I look forward to trying it.  I have some problem at my house, I cannot get to my bench and my PC is down...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 09, 2014, 05:21:10 am
Problem, part of waveform remaining after change in sig gen (demo mode). It's repeatable on my pc.

Here is what I did.

Demo mode sig gen
Sine on ch1 Square on Ch 2

Exported ch1 txt (no prob)
Exported ch2 txt (no prob)

Exported ch1 and ch2 (I assume this is incomplete/ in progress because there isn't any info in the txt file identifying ch2)

I changed ch2 on the sig gen to a flat line.

--- This is the issue ---
Exported ch2 and found the remainder of the previous square wave at the end (see screenshot) was in the exported txt as well.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 09, 2014, 08:58:40 am
RichardK,
              Wow! You have really done a lot since the last release! Excellent!

The cursor line performance seems to be working very well now!

The clickable knobs are also working well.

The Scale item you added to the Display grid menu earlier, is that to enable or disable the grid or is it meant to open a scaling (size) menu for the grid?

The default window size when opening the program hides the CH2 controls and needs to be pulled down every time to see them. The OEM does not do this. It can be a bit irritating at times.

I assume Autoset is still on your pending list, just noticed that Autoset on the OEM also sets the trigger pointer to the middle of the waveform amplitude in addition to selecting best Volt/Div and best Time/Div for input. If you use the Autoset on OPEN6022BE a few times after each other you get a different Volt/Div setting every time for the same waveform.

The Zoom feature is excellent and I can step it in and out very nicely.
When zooming in the display disappears after step 19. If I keep on zooming in more than 19 times the counter can be incremented indefinitely (I took it over 100) without any further displays being shown.
When zooming out I can carry on indefinitely (I went up to step 200). Display was there all along.
Would it be possible to add a visual horizontal left and right scroll line with 100% in the centre to replace the zoom counter next to the program name. Present clicking  then remains for fine zoom and scroll line can be used to drag zoom point which will be a bit coarser? Maybe place above controls? The counter next to the program name is a funny place for a counter IMHO.

You are doing an outstanding job!


Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on March 09, 2014, 06:33:31 pm
RichardK,

I can't think of a unique way to add to the mountain of thanks posted here for your work, so I'll simply say :clapping: again.

One thing I noticed in release beta17 was that if I change from a 1x to 10x probe in the GUI on the right, then look at the dropdown menu, the 1x is still checked in the dropdown.  In fact, if I change from 1x to 10x in the dropdown, the check remains on the 1x entry when I return to that menu, and there is no effect on the GUI value.  Ideally, the GUI and dropdown would be linked so that a change in one affects the other.

I also noticed that if I change the probe value while an autotrigger trace is presently running, there is no effect on the trace until I stop and restart the trace.  It's not terribly important, as I wouldn't plan to swap probes in real life while a trace is running, but note the inconsistency, as updating either time or volts per division while a trace is running does have an immediate effect.

I only tried CH1 for the above, but maybe CH2 would be affected, too?

The "export image to BMP" is a feature I use often.  If I could add to the wish list, I would want the exported image to show the text also, like the stock software does.  The most important part is the time/DIV and volts/DIV, but if everything was exported, never know what would be useful to someone.  This is not a high priority, as I can actually do a screen capture from Windows itself if necessary.

In dragging the horizontal line cursor, I noticed that the voltage difference is always displayed as a positive value.  This could actually be a good thing, because as a user, I can tell from observation which is the higher and lower voltage, and there is no need to put a minus sign in front of a negative value.

Matchless,

Thanks for doing the documentation!  Sooner or later, every one of us looks up things in the documentation, so it's important.  I'm not finished reading through the whole thing, but here are a few observations.

1) I'm guessing that your English is British English, so a word like "colour" would be correct.  Possibly "curser" is correct, also, but to me (I live in the USA) that's a person who uses crass language.  "cursor" would be my spelling.

2) There is a section 6.c.c describing the behavior of the cross cursor.  That sounds great.  But just after that, 6.c.d says that the vertical line cursor displays "time, frequency, and voltage," when in fact, it only displays time and frequency.  Similarly in 6.c.e, the horizontal line cursor only displays voltage, not all three.

3) In 7.a.i.1, I would suggest using the term "Phosphor Persistence" to be consistent with the naming in 7.a.i.2 immediately following.

Best Regards,
  Roderick.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 09, 2014, 07:15:33 pm
@RichardK

The waveform markers would be a good place to allow voltage adjustment via the scrollwheel when you mouseover them. That would allow the imported and math traces to be adjusted without going through the menus. The tooltip that shows CH1, CH2, reference, math could also show the voltage setting.

The main use would be adjustment while in full screen and import/math setup.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 09, 2014, 07:51:42 pm
Quote
Matchless,

Thanks for doing the documentation!  Sooner or later, every one of us looks up things in the documentation, so it's important.  I'm not finished reading through the whole thing, but here are a few observations.

1) I'm guessing that your English is British English, so a word like "colour" would be correct.  Possibly "curser" is correct, also, but to me (I live in the USA) that's a person who uses crass language.  "cursor" would be my spelling.

2) There is a section 6.c.c describing the behavior of the cross cursor.  That sounds great.  But just after that, 6.c.d says that the vertical line cursor displays "time, frequency, and voltage," when in fact, it only displays time and frequency.  Similarly in 6.c.e, the horizontal line cursor only displays voltage, not all three.

3) In 7.a.i.1, I would suggest using the term "Phosphor Persistence" to be consistent with the naming in 7.a.i.2 immediately following.

Best Regards,
  Roderick.

Roderick,
             Thanks for the feedback, I have done the corrections. Changed to USA English for color and fixed the spelling of cursor (curser is probably someone who curses a lot!)
Fixed up the behavior measurements of the cursor.

The Render Phosphor is as the menu is at the moment. If RichardK reads this and changes "Phosphor" to "Phosphor Persistence" after clicking on Render I can change that as well. Good suggestion thanks!

Please pass on any further feedback. I have broken the manual up into 5 parts and as a part is as complete as my limited knowledge allows, I will post it and hope for some input from the users such as yourself for corrections additions and suggestions.
Thanks again.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 09, 2014, 10:05:31 pm
One thing I noticed in release beta17 was that if I change from a 1x to 10x probe in the GUI on the right, then look at the dropdown menu, the 1x is still checked in the dropdown.  In fact, if I change from 1x to 10x in the dropdown, the check remains on the 1x entry when I return to that menu, and there is no effect on the GUI value.  Ideally, the GUI and dropdown would be linked so that a change in one affects the other.

Yikes apparently I never implemented those and nobody noticed until now... Just implemented that now so will be fixed in next release.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 09, 2014, 10:39:02 pm
@RichardK

Import / Export, having the ability to change the txt exported/imported data acquisition rate would make the waveforms much more compatible with other gear.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 10, 2014, 12:13:32 am
Problem, part of waveform remaining after change in sig gen (demo mode). It's repeatable on my pc.

Here is what I did.

Demo mode sig gen
Sine on ch1 Square on Ch 2

Exported ch1 txt (no prob)
Exported ch2 txt (no prob)

Exported ch1 and ch2 (I assume this is incomplete/ in progress because there isn't any info in the txt file identifying ch2)

I changed ch2 on the sig gen to a flat line.

--- This is the issue ---
Exported ch2 and found the remainder of the previous square wave at the end (see screenshot) was in the exported txt as well.

So far, exporting only works on the first selected source... Except for images.

As for the channel's not clearing all the way, should be fixed in next release.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 10, 2014, 12:16:31 am
@RichardK

Import / Export, having the ability to change the txt exported/imported data acquisition rate would make the waveforms much more compatible with other gear.

Not sure I follow, what do you mean by changing the acquisition rate? It cannot be changed after it's already exported without heavy interpolation, as for changing it before it's exported, just change the timebase before you export.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 10, 2014, 08:27:19 pm
I have tried to display the Lissajous pattern in demo mode and setting the phase offset to O degrees on one channel in XY mode shows correctly as well as the 45 degrees offset, but the 90 degrees offset does not seem to be correct, looks more like 135 degrees to me?
Waveform 1 marker also stays horizontal, but in the OEM software it jumps to the top of the graticule to show vertical when XY mode is selected.
Am I doing something wrong here?


Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 10, 2014, 08:41:21 pm
I have tried to display the Lissajous pattern in demo mode and setting the phase offset to O degrees on one channel in XY mode shows correctly as well as the 45 degrees offset, but the 90 degrees offset does not seem to be correct, looks more like 135 degrees to me?
Waveform 1 marker also stays horizontal, but in the OEM software it jumps to the top of the graticule to show vertical when XY mode is selected.
Am I doing something wrong here?

The offset units are not in degrees (they are in radians, but I'll be changing them later to degrees) and ill be moving the other lever to the top in a future release.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 11, 2014, 05:22:19 pm
Thanks RichardK!
If people use radians, maybe an option, radians or degrees?

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 12, 2014, 07:55:32 am
@richardk

Hey Richard, Sorry I wasn't ignoring you. I'm retired, but an old customer talked me in to helping him out for a few days.

Anyway here is some info you may find interesting, or may already know?

Most bench DSO's support csv's directly. The format varies widely but basically you will have the following.

Headers will often include date time instrument settings and sample width or samples per second and total number of samples. In real life this varies greatly.

Body format single trace. Most scopes have the ability to output acquisition time and number information but it's not always clear how to accomplish it.

acquisition time, voltage
acquisition number, voltage
voltage

Body format multiple trace.

acquisition time, voltage, acquisition time, voltage (acquisition time will vary depends on channel sharing)
acquisition number, voltage, voltage
voltage, voltage

So here are a couple of scenarios for csv's

- Exporting a csv for use in excel. Acquisition time is very useful. If number is used then duration of the sample should be in the header.
- Exporting a csv for use in a bench DSO. This relies heavily on header information and the record length of the body. My routine was to used an existing header, paste in a body then count the number of records. I would never attempt to add that type of functionality. Way too much grief.
- Importing a waveform from a DSO. If you have two columns the second will be the voltage. If the first is time you could load accordingly. If the first is a sample/record number then you will need to know what amount of time each datapoint represents. That could be included in the header but I'd suggest asking the user. If there are not enough records just fill with zeros and leave at that. If there are too many records just load what you can. Although you could interpolate datapoints while loading I do not think it would be an issue to use the last record value until you arrive at a change or to skip / average multiple points.
- Importing a waveform from a program. Ltspice output (for example) is acquisition time voltage and on and on (I didn't check the separator). You could load in the same way as a DSO or read through the body to calculate the time that each datapoint covers. Ideally you would be able to time shift this type waveform after it has been loaded. In any case this would probably be the most used feature. Being able match simulated waveforms with a realworld design kinda neat.

My thoughts csv would be

Multi trace output in any format you like.
Single trace reference load which skips the header if not Hantek and asks or has a place to input the datapoint duration.
Possibly allow the user to select the voltage column
 
I'm not sure about multi trace load but would probably not allow it unless the header math information matches the Hantek. Mainly that is because the math trace needs the math information to be displayed correctly. This is supported in the native save.

If the csv has more than 1 column then column 2 is probably voltage

I've added a few csv's for you to look at. The siglent is to show you variants from the same scope.

Please feel free to discard anything I say.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rexnanet on March 14, 2014, 01:38:38 pm
Mine just arrived!!!!! :D
Let the modding begin!! (when there's some time for it.. :S )

My first impression: horrible (or non existing at all) trigger...
I plugged both channels to the internal square wave generator to calibrate the probes and in both cases it can't trigger properly!
Is it due to the low voltage wave letting the noise mess with the trigger? Some say that it triggers ok... I'll have to check with some other signal source. But not very pleased with this... :(

Quote
While in general I think that this 'preserve until replaced' strategy is superior, I can think of some cases where this may not be the preferred choice.  Just a thought.

I'm mirroring the stock software for now, later on I'll look at some alternative ideas.

I have some Agilent high end DSO's at my work and in this case they don't display the last capture. This allows us to know if there was a new trigger or not... Although it can be more of a preference issue. Maybe there could be an option somewhere to choose between both aproaches...


By the way, again:
Excelent work! :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 15, 2014, 08:34:05 am
Here is the latest basic user manual for Open6022be:
http://jmp.sh/f8DTgQZ (http://jmp.sh/f8DTgQZ)

It still needs a lot of work and some pictures to be added. If anyone has any inputs, corrections etc please pass on to me and I can update it.
It is in .docx format and if you enable View of the Navigation pane you will have a nice Table of contents on the left side for jumping around.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 15, 2014, 10:34:52 am
If anyone has any inputs, corrections etc please pass on to me and I can update it.

The title page says "Soware", and I suspect you meant Software?

EDIT:  There are also misspellings of application, specification, calibration, functions, etc. so I'm wondering if some characters just aren't rendering properly for me?  Software is showing as soware everywhere, and I doubt you got that wrong more than once.  ;)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on March 15, 2014, 11:34:35 am
@Mark_O

MS Word 2010 does not show the detailed spelling errors, so it looks like your software is messing with the document.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on March 15, 2014, 03:17:26 pm
There are also misspellings of application, specification, calibration, functions, etc. so I'm wondering if some characters just aren't rendering properly for me?

Just an FYI, the spellings seem to be okay on my screen.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 15, 2014, 04:05:29 pm
MS Word 2010 does not show the detailed spelling errors, so it looks like your software is messing with the document.

Quote from: roderick
Just an FYI, the spellings seem to be okay on my screen.

Thanks, guys.  I'll see if I can track down the problem on my end.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 15, 2014, 04:56:53 pm
Would anyone prefer that I rather post a pdf or keep to the docx?

I will really appreciate some inputs, especially enhancements and obviously corrections!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on March 15, 2014, 05:19:22 pm
docx makes it customisable for users  :) Both docx and PDF may be an option ?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on March 15, 2014, 06:08:28 pm
Jumpshare's docx-viewer creates those "typos" - I can't see errors after opening the document in Word.

@Matchless: docx is fine for me!  :-+

Regards Robert
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on March 15, 2014, 06:19:21 pm
For review, either docx or pdf will work fine for me.  My opinion is that pdf is better for the final document.

I went through the first part of this version of the documentation, but did not get to the Examples part.  Here are my thoughts:

I think it would be very helpful to mention somewhere in the manual that the 6022BE hardware is limited to measuring a +- 5.0 volt signal.  That is, with a 1x probe, signals from -5 to +5 volts can be displayed; with a 10x probe, -50 to +50 volts, and so forth.  Maybe that should be a note in the Volts/DIV section, a warning that even if the display is set to 10 volts per division, the trace will clamp at 5 volts.  True, the input voltage limits are mentioned in the specs in the appendix, but that's really obscure.

15.2.f full screen

This looks like a 3-step process, when in fact, 15.2.f.1 is all that is needed to restore the normal screen.  Perhaps it should read,

1.  Push the ESC key on your keyboard, OR

2.  Right click on the display and select Window Mode.

15.2.f.3 choosing Restore from the system menu.

I would leave this out entirely, as it adds nothing beyond point (2.) above.  If someone knows Windows, they will know how to un-maximize their Window.  Also, on using Restore works as your text describes on (soon to be unsupported by Microsoft) Windows XP, but also, there is a restore button at the upper RIGHT of the title bar, too.  Other versions of Windows may do this differently.

3.a.ii.  Volts/DIV

These values are scaled by the probe attenuation.  For example, with an x10 probe, the smallest value is 200 mV, and the largest is 100 V.  It might be simpler to just omit the actual values in the documentation, but keep

"Select the voltage/division range for the displayed waveform."

Someone who has purchased an oscilloscope should already be quite familiar with what this does.

Of course, any comments on the menu items here could be similarly applied to the toolbar items.  I won't bog down the feedback by mentioning things twice.

3.a.iii probe

the 10000X setting is mentioned twice.

3.b.ii, 3.b.iii - same suggestions as above

4.b.i I'm not sure if this is exactly how auto trigger works.  I -think- that what happens is that this is the same as a normal trigger, except that if the input does not generate a trigger for a while, then a trigger will automatically be generated.  Notice that even in AUTO trigger mode, you can get a stable trace, if your input signal is stable.

4.b.ii Normal trigger
I would change the last word "drawn" to "drawn or redrawn", since the previous trace will stay on the screen until the next one is drawn.

7.a.i, 7.a.ii

Whichever term you choose, "Render Phosphor" or "Phospor Persistence," I still suggest using the same term in both occurrences, otherwise is sounds like you're talking about two different things.  Bottom line is that the first menu item switches it off, and the second switches it on.

7.a.v.  Phosphor Persistence

Suggest adding a note that this only applies when "Render Phosphor" is selected above.  It would seem that the UI could be simplified further by eliminating the "Render Normal/Phosphor" menu pick entirely, and having the "Phosphor Persistence" item always available.  Dragging the Persistence all the way to the left (zero) would be equivalent to Normal.  That would match a traditional old scope, where there is just one knob for persistence, no extra button to turn it on and off.  But that's for RichardK to decide.

8.a Acquire

Start acquiring and displaying the signal, according to the trigger conditions previously set.

8.b Stop

Stop acquiring.  This is useful for "freezing" the most recently displayed signal on the screen.

16.6 FFT

I note that this is only on the toolbar, not in any menu pick as far as I can see.  For the explanation, I'd suggest

"The Fast Fourier Transform (FFT) can be used to display the component frequencies in a signal.  Consult the internet for more information on this subject."

and just leave it at that.  Presently, the FFT does not show a labled scale, so it's only qualitatively useful, and the simple explanation above should suffice.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 15, 2014, 09:00:53 pm
Would anyone prefer that I rather post a pdf or keep to the docx?

I think a docx makes the most sense, for now.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: C on March 15, 2014, 10:39:18 pm

Matchless

I would break the Specifications in to two parts
One part for the software and one for the data collection unit the Hantek 6022BE

then for the Hantek 6022BE

I would start with the most important limitations first so they would be seen and not missed.

Input protection 35Vpk (DC + peak AC < 10kHz)
Max. Input +/- 5V(Without external attenuation)
Max. sample rate burst mode,  size of burst & how long until you can get an additional burst of samples
Max. sample rate continuous

then for the vertical section use the actual hardware limits. From a quick read it looks like you might have 8 gain settings. At those gain settings what are the actual limits. This separates the software function from the data collection hardware.
In place of a string of numbers for common probes use a table with one column for each hardware gain setting and a row for each common probe.
Use volts and not volt/Div as volts/div is really a software function. Depending on how the software is written, it could be easy for the software to allow use of a custom probe like a 2x or 3x.
 
Use the same idea for the same with the hardware timebase section.
This would make it easy to know the foundation that the software has to use. And if the software starts using a different hardware data collection system, this part will stay correct.
And as the software changes you also just have one section to update.

Just an idea
C

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on March 15, 2014, 11:05:11 pm
...
Input protection 35Vpk (DC + peak AC < 10kHz)
Max. Input +/- 5V(Without external attenuation)
Max. sample rate burst mode,  size of burst & how long until you can get an additional burst of samples
Max. sample rate continuous

then for the vertical section use the actual hardware limits. From a quick read it looks like you might have 8 gain settings. At those gain settings what are the actual limits. This separates the software function from the data collection hardware
....

I ran into some kind of software limit a few weeks ago. As I didn't keep that in focus I'll re-test that issue next week.

One problem was the max Vin beeing clipped at 500mv (if V/div set to 100mV/div or lower) and clipping occurring at 5 times V/div - until you start to hit the hardware limit.

Maybe this problem only exists due to "personal practice" - as I'm rarely ever using settings that will give me less than two divs signal height on the scope ...


Robert
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 16, 2014, 09:49:43 am
I have managed to incorporate most of your suggestions. The items in red are still incomplete or dependent on RichardK's software updates. In some cases I need some help with better formulating of a description. Once it's more complete I will post links for the docx and pdf.
I have also added a section for listing some limitations to be aware of.

Your suggestions have helped a lot!

Note: Rather download the file as opening it in Jumpshare does not function properly it seems.

Here is the latest docx: http://jmp.sh/iNgCCck (http://jmp.sh/iNgCCck)
Here is the latest pdf: http://jmp.sh/wushfT3 (http://jmp.sh/wushfT3)

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on March 18, 2014, 03:02:24 pm
Latest Binary: http://jmp.sh/h2xSceX (http://jmp.sh/h2xSceX)

What's New:
-----------------------------------------------------------
1. Fixed a race condition which might cause random hangs.
2. Fixed a bug in the grid brightness dialog which caused part of the slider range to have no
   effect on brightness.
3. Made Horizontal and Vertical Knobs "position-clickable" (click to set position).
4. Implemented loop timeouts to prevent infinite loops in Multithread Lock code (Hang prevention).
5. Fixed a bug where disabling the Math Channel could cause a hang.
6. Added detailed Calibration Failure error messages.
7. Made waves continuously draw in Phosphor mode when Acquire stopped (To prevent smearing).
8. Added a Clear option to the Display menu which will clear the screen (good for Phosphor mode).
9. Added a Reset Interactive option to the Cursors Menu which reset the Interactive Cursor positions
   to their default locations.
10. Overhauled Rendering code, much easier to read and performance increased.
11. Fixed a few Dialog typos.
12. Fixed some Menu/Toolbar label inconsistencies.
13. Fixed some Trigger issues.
14. Trigger Single Shot mode now shows last captured waveforms while waiting for trigger, instead of
   not showing any waveforms at all.
15. Changed rendering so only Waveform's and FFT are effected by Digital Phosphor mode (Not cursors,
   text, etc...).
16. Fixed some Menu/Toolbar checkbox issues.
17. Made selecting either of the three different Line Cursor Modes enable Line Cursors if Line Cursors
   are not already enabled.
18. Added Pure Square waves (Generated from Sine Waves) to Demo Mode & Function Generator.
19. Disabled Horizontal noise for Artificial Square Waves (it's not supported).
20. Improved FFT performance when using a Window Function (precalculated window functions).
21. Added Sweep Controls to Demo Mode (sweep any demo mode property).

RichardK, usually, I try to find issues with your release to help you with debugging.  This release, I can't find any issue at all.  Great job!  The trigger and display are much more stable than before.  The UI is more polished.  This is a great release.

1 Question and 1 non-bug issue:

Issue not related to bug- when I download this, Chrome blocked it as malicious.  See attached screen print.  I am on Chrome version 33.0.1750.154 m, and it up-to-date according to Chrome's update screen.

Question- I must be missing something obvious.  You said the math and reference wave form has v/div adjustment.  I can't find it...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on March 18, 2014, 03:34:50 pm
Just stumbled on a site detailing overheating in the 6022 DC-DC converter:

http://pididu.com/wordpress/blog/i-dropped-an-oscilloscope-on-my-foot-hantek-6022be/ (http://pididu.com/wordpress/blog/i-dropped-an-oscilloscope-on-my-foot-hantek-6022be/)


EDIT:

Misread web page....6022BE was being used to DIAGNOSE an overheat issue, it was not the subject of the investigation....thats the perils of speed reading for you  :-[
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 18, 2014, 03:36:51 pm
Issue not related to bug- when I download this, Chrome blocked it as malicious.  See attached screen print.  I am on Chrome version 33.0.1750.154 m, and it up-to-date according to Chrome's update screen.

No idea why chrome is deeming this malicious... I don't use Chrome, I use Firefox and Avast AV, so far no heuristic false positives.

Quote
Question- I must be missing something obvious.  You said the math and reference wave form has v/div adjustment.  I can't find it...

The voltage divisions for Math and Reference channels can be changed from the Main Menu -> Channel as well as setting Channel Control A or B to Math or Reference and setting the Voltage Division from the respective Drop Down menu for that Channel Control.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 18, 2014, 03:39:35 pm
Just stumbled on a site detasiling overheating in the 6022 DC-DC converter:

http://pididu.com/wordpress/blog/i-dropped-an-oscilloscope-on-my-foot-hantek-6022be/ (http://pididu.com/wordpress/blog/i-dropped-an-oscilloscope-on-my-foot-hantek-6022be/)

He is not talking about the DC-DC inside the 6022BE, he is talking about a seperate DC-DC converter that was overheating and how his first use of the 6022BE was in diagnosing the over heating of this separate DC-DC.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PedroDaGr8 on March 18, 2014, 03:42:57 pm
Issue not related to bug- when I download this, Chrome blocked it as malicious.  See attached screen print.  I am on Chrome version 33.0.1750.154 m, and it up-to-date according to Chrome's update screen.

No idea why chrome is deeming this malicious... I don't use Chrome, I use Firefox and Avast AV, so far no heuristic false positives.

Quote
Question- I must be missing something obvious.  You said the math and reference wave form has v/div adjustment.  I can't find it...

Definitely chrome issue.

Not a single virus vendor flags this file:
https://www.virustotal.com/en/file/b5d906fa4d2c2b555831f98fa2ce3d28458696d051c12e9492da4f6bc8da1bf2/analysis/1395157292/ (https://www.virustotal.com/en/file/b5d906fa4d2c2b555831f98fa2ce3d28458696d051c12e9492da4f6bc8da1bf2/analysis/1395157292/)

0/50  ;D

The voltage divisions for Math and Reference channels can be changed from the Main Menu -> Channel as well as setting Channel Control A or B to Math or Reference and setting the Voltage Division from the respective Drop Down menu for that Channel Control.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on March 18, 2014, 03:46:17 pm
@RichardK, 

Yes, I realised too late and after posting  :-[  I was speed reading and missed the context of the tests he was doing. Oooooops ! I edited my previous Post.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 18, 2014, 03:48:29 pm
@RichardK, 

Yes, I realised too late and after posting  :-[  I was speed reading and missed the context of the tests he was doing. Oooooops ! I edited my previous Post.

No worries, happens to everyone :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: DarrenS on March 19, 2014, 09:06:00 am
I don't know if anyone else has noticed this... quite often when I click and drag on the vertical channel markers to move the waveform up and down, the pointer changes to the double arrow as if the marker will be moved, but the marker and waveform don't actually move even though the mouse pointer does. If I release the click and try it again, it works as expected. The same also happens with the trigger markers.

Does anyone else see this behaviour?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 19, 2014, 10:37:11 am
I don't know if anyone else has noticed this... quite often when I click and drag on the vertical channel markers to move the waveform up and down, the pointer changes to the double arrow as if the marker will be moved, but the marker and waveform don't actually move even though the mouse pointer does. If I release the click and try it again, it works as expected. The same also happens with the trigger markers.

Does anyone else see this behaviour?

No do not get this, but why are you clicking on it?
As soon as the mouse cursor hovers over the marker the cursor changes to an down/up arrow and you just push and hold the mouse button to drag it up or down.
I am using the latest v17 and it is running on Win8.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: DarrenS on March 19, 2014, 10:49:29 am
I'm clicking as part of the drag operation ;-) To be more accurate then I "press" the mouse button (as opposed to a click which is a press and a release). All I'm doing is a standard drag action.

To be very specific:
I move the pointer over the marker and the pointer changes to the double arrow
I press the left mouse button
I move the pointer up or down
Frequently, the pointer moves but the channel or trigger marker does not

I'm running the latest PR17 version on Win7 64bit but I have also noticed this with previous versions.

It's not a showstopper by any means, but it is slightly annoying and unnecessary.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 19, 2014, 11:40:27 am
DarrenS,
 
Normal drag does not do it on my PC, but if the trigger sweep  is set to "Normal" then I get a delay before the waveform moves to the pointer position.

I tested with the program on Default settings and the probes connected to the front output lug on the 6022. Not sure what settings you were using.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: DarrenS on March 19, 2014, 01:38:50 pm
I'm using the program with default settings too.

I can't find any pattern to when it happens for me - it just happens, maybe, 1 out of every 7 or 8 repeated attempts, although it quite often seems to happen on the first attempt during typical usage (i.e. not just trying to reproduce the issue).

Maybe it's only me that's affected (although I can't imagine what it is about my environment/usage that causes it) but I'd be very interested to know if anyone else has ever experienced this.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on March 19, 2014, 04:20:29 pm
Issue not related to bug- when I download this, Chrome blocked it as malicious.  See attached screen print.  I am on Chrome version 33.0.1750.154 m, and it up-to-date according to Chrome's update screen.

Just as a data point, I can download the jumpshare file for version 17 from Chrome without complaint, both on Linux, and Windows XP.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 19, 2014, 04:22:37 pm
I'm using the program with default settings too.

I can't find any pattern to when it happens for me - it just happens, maybe, 1 out of every 7 or 8 repeated attempts, although it quite often seems to happen on the first attempt during typical usage (i.e. not just trying to reproduce the issue).

Maybe it's only me that's affected (although I can't imagine what it is about my environment/usage that causes it) but I'd be very interested to know if anyone else has ever experienced this.

I found the problem and have fixed it, will not be a problem in the next release... A better way to reproduce it is to slowly move the cursor toward a lever until the cursor changes, then attempt to drag (it won't drag)... This was due to a slight difference in the coordinate conversion in the part of the code that determines if you are over a lever and the part of the code that moves it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 19, 2014, 04:42:37 pm
DarrenS,  if I follow RichardK's explanation I have the same problem! As he said it is already fixed in the next version.
Good catch on that one!
Thanks RichardK.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: DarrenS on March 19, 2014, 05:05:43 pm
Woo hoo! Thanks guys - you have restored my faith in my sanity!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: C on March 19, 2014, 05:23:54 pm
RichardK,

I am not seeing the most important reason to get a Hantek 6022BE fixed with this software.

Look at all the reviews that dave has done on stand alone DSO's. When you connect one of them to a PC. Only two modes are really possible, Video mode or Data Collection mode.

Video Mode:
For this mode the stand alone DSO acts like a video camera source. A cheap DSO would just send the picture frame data over the USB buss. To get higher resolution &/or a higher frame rate the DSO would have to do video compression. The Hantek 6022BE can not do this.

Data Collection mode:
For this mode the stand alone DSO acts like a analog data capture source. Here the  stand alone DSO would capture a block of samples. In addition to the actual ADC data samples the DSO would need to inform the PC of what format the data samples are being sent over the USB. Some of the extra information would be how many channels, Sample rate for a channel, The real time that this block of data samples started and how many samples the data block contains, The analog settings used to collect the samples. In this mode there would be blocks of data with time gaps between the blocks. The time gaps would only become 0 when the sample rate became slow enough that the PC side could keep up with the incoming data. Because the rate could change it would be important to know when a time gap did happen. The Hantek 6022BE while poor is a analog data capture device. As some of the above is set by the firmware loaded into the Hantek 6022BE I see the PC data collection software needing to add the additional information to the information that travels over the USB buss so that the viewer will then have the needed information to properly display the data.

The software first needs to turn the Hantek 6022BE into the best analog data capture device it can be. This is where the Hantek 6022BE could be better than the stand alone DSO. Unlike the DSO the PC could use a lot of buffers, You could buffer samples to ram &/or buffer samples to disk. And while the data collection is happening you could then look at the captured data. Where a DSO would have to use a One shot mode to acquire data the Hantek 6022BE could switch from continuous to disk sample speed with no time gaps to one of many burst speeds where the samples would have time gaps.
The analog data capture software could do some auto ranging by looking at the sample data. To make this really nice and usable there would need to be a lot of easy to use settings.
With the low cost of the Hantek 6022BE, the software should allow for adding an additional USB interface card to the computer so that many Hantek 6022BE's could be used at high speeds.
Even as poor as the Hantek 6022BE is it could be very nice to have the ability to look back at what happened.

The existing software is a start of a data viewer and has parts of the data capture side needed.
If the data capture side was done well it should be possible to run many viewers. Someone that has many displays connected to there PC could have one viewer showing the real time data collection while using an additional display to look back through the collected data on a second display.

So RichardK,
How far do you want to go with this software? With a good software foundation it could become more than just a little better than what Hantek supplied. As a separate data collection program that talks to a data viewer program it could become the thing to use with any DSO on a PC.

C

       




Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 19, 2014, 05:32:15 pm
RichardK,

I am not seeing the most important reason to get a Hantek 6022BE fixed with this software.

Look at all the reviews that dave has done on stand alone DSO's. When you connect one of them to a PC. Only two modes are really possible, Video mode or Data Collection mode.

Video Mode:
For this mode the stand alone DSO acts like a video camera source. A cheap DSO would just send the picture frame data over the USB buss. To get higher resolution &/or a higher frame rate the DSO would have to do video compression. The Hantek 6022BE can not do this.

Data Collection mode:
For this mode the stand alone DSO acts like a analog data capture source. Here the  stand alone DSO would capture a block of samples. In addition to the actual ADC data samples the DSO would need to inform the PC of what format the data samples are being sent over the USB. Some of the extra information would be how many channels, Sample rate for a channel, The real time that this block of data samples started and how many samples the data block contains, The analog settings used to collect the samples. In this mode there would be blocks of data with time gaps between the blocks. The time gaps would only become 0 when the sample rate became slow enough that the PC side could keep up with the incoming data. Because the rate could change it would be important to know when a time gap did happen. The Hantek 6022BE while poor is a analog data capture device. As some of the above is set by the firmware loaded into the Hantek 6022BE I see the PC data collection software needing to add the additional information to the information that travels over the USB buss so that the viewer will then have the needed information to properly display the data.

The software first needs to turn the Hantek 6022BE into the best analog data capture device it can be. This is where the Hantek 6022BE could be better than the stand alone DSO. Unlike the DSO the PC could use a lot of buffers, You could buffer samples to ram &/or buffer samples to disk. And while the data collection is happening you could then look at the captured data. Where a DSO would have to use a One shot mode to acquire data the Hantek 6022BE could switch from continuous to disk sample speed with no time gaps to one of many burst speeds where the samples would have time gaps.
The analog data capture software could do some auto ranging by looking at the sample data. To make this really nice and usable there would need to be a lot of easy to use settings.
With the low cost of the Hantek 6022BE, the software should allow for adding an additional USB interface card to the computer so that many Hantek 6022BE's could be used at high speeds.
Even as poor as the Hantek 6022BE is it could be very nice to have the ability to look back at what happened.

The existing software is a start of a data viewer and has parts of the data capture side needed.
If the data capture side was done well it should be possible to run many viewers. Someone that has many displays connected to there PC could have one viewer showing the real time data collection while using an additional display to look back through the collected data on a second display.

So RichardK,
How far do you want to go with this software? With a good software foundation it could become more than just a little better than what Hantek supplied. As a separate data collection program that talks to a data viewer program it could become the thing to use with any DSO on a PC.

C

     

The scope is limited but useful, and it seems like you are making the assumption that I am trying to turn a $75 20Mhz USB scope into a thousand dollar 200+ Mhz scope and I am not... I am only correcting the flaws in the stock software and providing features that should have been in the stock software.

It is pointless to try and turn this scope into something it is not, and after I am done doing my work on the code and release the source, if someone else wants to give it a try, that's up to them.

As for the software, this is what the software does (stock and my version):

1. A worker thread takes periodic samples from the hardware into PC memory and checks it for trigger criteria, setting the trigger index (relative to the raw data array) for any trigger event found in that particular capture (so it can render it later on without rolling or jidder), it also does interpolation if needed.

2. Another worker thread renders the captured data in PC RAM onto the screen, where the user can interact with it, perform measurements on it. etc...

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: C on March 19, 2014, 07:11:21 pm
The scope is limited but useful, and it seems like you are making the assumption that I am trying to turn a $75 20Mhz USB scope into a thousand dollar 200+ Mhz scope and I am not... I am only correcting the flaws in the stock software and providing features that should have been in the stock software.

Is it really a $75 scope? When your software is running would it not be fair to include part of the PC's cost in the result?
For all the limits imposed by the $75 hardware this could be very powerful due to the attached PC
For some uses a 20Mhz scope is a lot more than what is needed.

Quote
I am only correcting the flaws in the stock software and providing features that should have been in the stock software.
I guess that you and I just looking at things differently. I am looking at a great stand alone DSO and asking the question what has to change due to the  $75 hardware used & what improvements can be made to that great stand alone DSO because a PC is being used.

C
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 19, 2014, 11:26:49 pm
The scope is limited but useful, and it seems like you are making the assumption that I am trying to turn a $75 20Mhz USB scope into a thousand dollar 200+ Mhz scope and I am not... I am only correcting the flaws in the stock software and providing features that should have been in the stock software.

Is it really a $75 scope? When your software is running would it not be fair to include part of the PC's cost in the result?
For all the limits imposed by the $75 hardware this could be very powerful due to the attached PC
For some uses a 20Mhz scope is a lot more than what is needed.

Quote
I am only correcting the flaws in the stock software and providing features that should have been in the stock software.
I guess that you and I just looking at things differently. I am looking at a great stand alone DSO and asking the question what has to change due to the  $75 hardware used & what improvements can be made to that great stand alone DSO because a PC is being used.

C

The possibilities of the scope are not limited by me,  but by the community using it. Like I said before, if people want to improve it more than I have, they can put as much work into my code as they want, that was my second goal of this project, giving others a good launching pad to start from.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on March 20, 2014, 03:44:50 am
The scope is limited but useful, and it seems like you are making the assumption that I am trying to turn a $75 20Mhz USB scope into a thousand dollar 200+ Mhz scope and I am not... I am only correcting the flaws in the stock software and providing features that should have been in the stock software.

Is it really a $75 scope? When your software is running would it not be fair to include part of the PC's cost in the result?
For all the limits imposed by the $75 hardware this could be very powerful due to the attached PC
For some uses a 20Mhz scope is a lot more than what is needed.

Quote
I am only correcting the flaws in the stock software and providing features that should have been in the stock software.
I guess that you and I just looking at things differently. I am looking at a great stand alone DSO and asking the question what has to change due to the  $75 hardware used & what improvements can be made to that great stand alone DSO because a PC is being used.

C

Mr. C,

I don't think you quite understand what is being done here.  Some of us find a stand alone DSO to be the way to go, some of us find otherwise.  Still, some of us may want to go for a stand-alone but for one reason or another, went with the a USB based scope.

So, those of us with this USB DSO are trying to get as much out of it as we can.  With RichardK's help, we are getting more out of our limited hardware.  So, we are all appreciative of Mr. RichardK for that.

It is true that the $75 scope is not $75 if you include the cost of the PC.  Then again, the $500 standalone DSO is not $500 if you include the cost of bringing electricity from the substation into the house to run that DSO.

Value is what one places on the item.  Suitability is application and cost dependent.  If all I need is a push cart, I am foolish to buy a forklift; if all one can budget for is a townhouse, one is foolish to say a mansion or nothing.

You said you are going to buy a stand alone DSO, good for you.  You have the need for it and you can justify it.  So it is right for you.  I am far from saying: "Forgot your prescription glasses? No problem; use mine - my prescription glasses allow me to see clearly therefore you should see as clearly through my prescription glasses as well."

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on March 20, 2014, 10:46:51 am
I am fortunate enough to own bench, portable and USB DSO's. Each has its own benefits and compromises. So why did I buy the 6022BE ?  It matched my Hantek Logic analyser and my Hantek Arb Function Generator  ;D But seriously I already had the LA and AFG and thought a simple DSO would be useful for use with them as part of a Laptop PC based mobile test setup. The DSO was so cheap that it was hard ot resist.

I was pleased with the 6022BE hardware, but unimpressed with the poorly produced software that drives it. Good hardware with poor software basically made the 6022BE a paperweight for my purposes. RichardK has done what I could not.....created a software package that enables me to use the 6022BE as part of my PC test kit and it is now a useable DSO thanks to his very generous efforts and those who have been doing the Beta testing.

There is an old saying in the UK...... you can't make a silk purse out of a Sows ear. In this case RichardK has made the unit useable but there seems little point in expending many hours trying to make the 6022BE anything more than it was designed to be..... a 20MHz basic DSO. For the 'Ultimate' USB DSO a better hardware platform would be advised.

My sincere thanks to RichardK for turning my 6022BE paperweight into a useful little DSO.

It is such a pity that Hantek do not seem to place adequate importance on the software elements of their products as their hardware design is quite respectable.

Aurora 
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 20, 2014, 11:42:10 am
The possibilities of the scope are not limited by me,  but by the community using it. Like I said before, if people want to improve it more than I have, they can put as much work into my code as they want, that was my second goal of this project, giving others a good launching pad to start from.

I think you're doing a really excellent job meeting that objective!  Thanks.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 20, 2014, 12:09:57 pm
RichardK,
              This thread is my most favourite and My Hantek 6022be is next to my PC waiting for the next updated binary! You are definitely meeting my requirements and doing a most outstanding job!
Thank you sir!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 21, 2014, 10:00:44 am
I have updated some more sections in the Open6022be user manual. I have also included some of the findings by members in this forum thread. I hope it is in order with you that I did that.
There are a few items in red font, that are sort of related to RichardK's software, if you have any comments on those.

Here is the latest pdf: http://jmp.sh/fZAhsOY (http://jmp.sh/fZAhsOY)
Here is the latest docx: http://jmp.sh/VrNJmBq (http://jmp.sh/VrNJmBq)

All feedback, changes, additions, criticisms are appreciated!

Edit:See new post further on with updates
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on March 23, 2014, 08:24:58 am
I have updated some more sections in the Open6022be user manual. I have also included some of the findings by members in this forum thread. I hope it is in order with you that I did that.
...
Section 14 on "Limitations and Things to be Aware of" is wonderful!  It distills the essential information that the public has learned that would be of useful to an engineer.  Only in an open-source manual can we find this sort of information.  Great job!

In Section 13, "Self-Calibration," there is a picture of the probe, and an enlargement of the x10 / x1 switch.  I don't know about other people's probes, but the ones that came stock with my 6022BE have the "x1" setting forward, and the "x10" setting back, the opposite of the picture.  Not a major deal.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 23, 2014, 12:49:23 pm
roderick, thanks for the feedback! Picture is fixed now!
I have progressed a little further with the updates to the document. The parts in red are either software related or require some more detail.

Here are the latest versions b9:
Note: The Jumpshare viewer seems to result in spelling mistakes on the docx, rather download it to read properly. I have notified them.

Docx: http://jmp.sh/jksZHSB (http://jmp.sh/jksZHSB)
Pdf: http://jmp.sh/dKax03Q (http://jmp.sh/dKax03Q)

Hopefully I get more feedback from the forum crowd!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 23, 2014, 05:35:35 pm
Hopefully I get more feedback from the forum crowd!

Well, you asked for feedback, so I'll give you some.  :)

I haven't had time to read the entire manual in detail yet, but I'm very impressed with what I have seen.  You've done a very good job, especially tying explanations to screen captures of displays and menus.  This isn't only better than Hantek's docs, or any Chinglish docs, it's also superior to many US manufs. professionally produced documents.  Very well presented, informational, and educational.  Excellent for a product of this type.

I did note a couple questions in red, on Page 39.  Here's the info you requested:

- the max sample rate in Burst Mode is 48 MSa/s
- the max sample rate in continuous mode is 16 MSa/s


I see now that the "Hantek strategy" has paid off handsomely.  Aka, "reverse outsourcing".  We started it by outsourcing our electronics knowledge and manufacturing expertise, years ago, to get cheap hardware.  Hantek has provided that.  And by not investing any time or money in decent software or documentation, Hantek has now outsourced them back to the US, and obtained both, free of charge.   :-DD
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on March 23, 2014, 05:52:30 pm
...
I see now that the "Hantek strategy" has paid off handsomely.  Aka, "reverse outsourcing".  We started it by outsourcing our electronics knowledge and manufacturing expertise, years ago, to get cheap hardware.  Hantek has provided that.  And by not investing any time or money in decent software or documentation, Hantek has now outsourced them back to the US, and obtained both, free of charge.   :-DD

It is not a bad idea really.  We (users and manufacturer) both benefited.

This is similar to the "self-checkout" at Walmart and other stores.  When you use the self-checkout, Walmart just outsourced the work to you.

Whereas, at places like Walmart the benefit is far more limited, and they have to balance the numbers between lost (shop-lifting) and gain (labor saved), this "Hantek outsource" doesn't have that drawback and the benefit (by value) is far more significant.

Thanks to RichardK, we all benefited.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 23, 2014, 06:21:44 pm
I haven't had time to read the entire manual in detail yet, but I'm very impressed with what I have seen.  You've done a very good job, especially tying explanations to screen captures of displays and menus.  This isn't only better than Hantek's docs, or any Chinglish docs, it's also superior to many US manufs. professionally produced documents.  Very well presented, informational, and educational.  Excellent for a product of this type.

I did note a couple questions in red, on Page 39.  Here's the info you requested:

- the max sample rate in Burst Mode is 48 MSa/s
- the max sample rate in continuous mode is 16 MSa/s

Thanks for the feedback and the specs. Its slowly coming together, but there is still a lot to do. Every bit of input is appreciated and I know how hard it is to read a manual. Most people including myself only use the manual as a last resort or even then maybe not!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Bocks on March 24, 2014, 01:19:13 am
I tried to use Open6022BE on my laptop and everything works except the waveform doesn't render. If I have the scope connected to a signal I see triggering indicated. If I do a print preview I see a waveform. If I put the software in XY mode I can see a trace. Just no trace in YT. Grid, cursors, zero and trigger level gadgets all show fine. I have Hantek's 1.04 version installed and it runs normally, and I've tried Open6022BE on a netbook and it works great there. This laptop is running Windows 7 Pro 32 bit and it has both nVidia 310M and Intel onboard video, which it defaults to. I tried running it off the nVidia side and no difference(the laptop is able to switch video chipsets on the fly). That was the only thing I could think of that's out of the ordinary. I am using the PR17 version and have not tried anything earlier. I also tried moving the copy of msvcr100.dll that came with it so it would use the one already in the computer. If you have any insights please let me know. Thanks!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 24, 2014, 01:42:08 am
I tried to use Open6022BE on my laptop and everything works except the waveform doesn't render. If I have the scope connected to a signal I see triggering indicated. If I do a print preview I see a waveform. If I put the software in XY mode I can see a trace. Just no trace in YT. Grid, cursors, zero and trigger level gadgets all show fine. I have Hantek's 1.04 version installed and it runs normally, and I've tried Open6022BE on a netbook and it works great there. This laptop is running Windows 7 Pro 32 bit and it has both nVidia 310M and Intel onboard video, which it defaults to. I tried running it off the nVidia side and no difference(the laptop is able to switch video chipsets on the fly). That was the only thing I could think of that's out of the ordinary. I am using the PR17 version and have not tried anything earlier. I also tried moving the copy of msvcr100.dll that came with it so it would use the one already in the computer. If you have any insights please let me know. Thanks!

I have no clue really... The only thing that is different between XY and YT (other than the obvious) is brightness doesn't effect XY, so it could be related but I'll have to look at the code.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on March 24, 2014, 04:31:47 pm
I tried to use Open6022BE on my laptop and everything works except the waveform doesn't render. If I have the scope connected to a signal I see triggering indicated. If I do a print preview I see a waveform. If I put the software in XY mode I can see a trace. Just no trace in YT. Grid, cursors, zero and trigger level gadgets all show fine. I have Hantek's 1.04 version installed and it runs normally, and I've tried Open6022BE on a netbook and it works great there. This laptop is running Windows 7 Pro 32 bit and it has both nVidia 310M and Intel onboard video, which it defaults to. I tried running it off the nVidia side and no difference(the laptop is able to switch video chipsets on the fly). That was the only thing I could think of that's out of the ordinary. I am using the PR17 version and have not tried anything earlier. I also tried moving the copy of msvcr100.dll that came with it so it would use the one already in the computer. If you have any insights please let me know. Thanks!

Bock, this rendering failure seems similar to what I see when I run remote desktop.  (I see all traces plotted normal except when I run RDC).

Try this (to get more clues): immediately after power-up, connect both CH1 and CH2 to the scope's reference wave, turn on both CH1 and CH2, then turn on math, you may see the math trace.  If so, they may be related.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: DarrenS on March 24, 2014, 09:24:53 pm
I don't know if I've just discovered another small bug...

I just tried exporting waveforms for both Channel 1 and Channel 2 but I don't see any evidence of Channel 2 in the exported file. I first tried this using the .bewf format but when I only saw one channel appear on import I tried the .txt format export so I could view the contents... and there is no reference to CH2 in the file.

I've not tried including any of the other elements in the export  file (Math, Reference, FFT) so don't know if they are missing too.

Is this a known problem?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 24, 2014, 09:28:32 pm
I don't know if I've just discovered another small bug...

I just tried exporting waveforms for both Channel 1 and Channel 2 but I don't see any evidence of Channel 2 in the exported file. I first tried this using the .bewf format but when I only saw one channel appear on import I tried the .txt format export so I could view the contents... and there is no reference to CH2 in the file.

I've not tried including any of the other elements in the export  file (Math, Reference, FFT) so don't know if they are missing too.

Is this a known problem?

Exporting more than one channel (or source) is only supported for Image exports currently, I'll have to modify the data formats for exporting more than one source (I will eventually). Right now you have to export them separately.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: DarrenS on March 24, 2014, 09:51:19 pm
Exporting more than one channel (or source) is only supported for Image exports currently, I'll have to modify the data formats for exporting more than one source (I will eventually). Right now you have to export them separately.

Noted - thanks for the quick reply Richard.

One other thing I forgot to mention before, totally unrelated to exporting!... I've noticed problems at times with the "waveform context area" above the waveform view. I can't say what conditions this occurs under but at times the T appears way over to the right of the context area and clicking and dragging only brings it back so far. The waveform view scrolls as you drag but it's not clear where exactly in the timeline you are. Again, is this a known problem?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 24, 2014, 09:55:31 pm
Exporting more than one channel (or source) is only supported for Image exports currently, I'll have to modify the data formats for exporting more than one source (I will eventually). Right now you have to export them separately.

Noted - thanks for the quick reply Richard.

One other thing I forgot to mention before, totally unrelated to exporting!... I've noticed problems at times with the "waveform context area" above the waveform view. I can't say what conditions this occurs under but at times the T appears way over to the right of the context area and clicking and dragging only brings it back so far. The waveform view scrolls as you drag but it's not clear where exactly in the timeline you are. Again, is this a known problem?

The 'T' is the location of the trigger, so sometimes the waveform context can be rendered before the waveform itself is rendered (which is centered with trigger position).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Bocks on March 25, 2014, 02:32:18 am
Rick and Richard, thanks for the replies. I tried math right after powerup and got no trace there either, but thinking about the remote desktop prompted me to think about my monitor configuration. I have an external monitor plugged in(HDMI) using dual view mode. Switching out of dual view to either single monitor or laptop display, or to cloned display on both screens made the traces appear instantly! So at least I know how to make it work and perhaps it will be repeatable on another computer. I'll try it on another computer if I can. I can't try it on my netbook because it runs Windows 7 Starter edition which only allows cloned display externally, not dual view.

Thanks again for your help.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 25, 2014, 02:41:04 am
Rick and Richard, thanks for the replies. I tried math right after powerup and got no trace there either, but thinking about the remote desktop prompted me to think about my monitor configuration. I have an external monitor plugged in(HDMI) using dual view mode. Switching out of dual view to either single monitor or laptop display, or to cloned display on both screens made the traces appear instantly! So at least I know how to make it work and perhaps it will be repeatable on another computer. I'll try it on another computer if I can. I can't try it on my netbook because it runs Windows 7 Starter edition which only allows cloned display externally, not dual view.

Thanks again for your help.

The windows GDI function AlphaBlend has issues when rendering on multiple displays, I have modified the code to use an alternative method if it fails (things will render differently but at least it will be visible!).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: alex.forencich on March 25, 2014, 04:26:57 pm
One is for data, the other is for extra power. Each USB port is only rated to 500 mA. This sort of setup is common for external hard drives as well.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 25, 2014, 05:34:59 pm
RichardK,  I have listed some issues. I was holding back as some of these may already have been solved in your coming binary. If you have a look at the User Manual I posted here http://jmp.sh/dKax03Q (http://jmp.sh/dKax03Q) there are some parts in red that are not mentioned below that are easier explained in that way.
I know its always a pain in the backside to get these when busy with a project, I thus apologize in advance! Hope this helps you sort out some glitches a bit easier!

1.   If full screen is selected the GUI does not display the menu, tool bar and button bar, only the full graticule and program name area.
Pressing the ESC button returns correctly to smaller display with toolbars and controls panel in view.
Clicking the small top left hand icon and selecting Restore the display is smaller, but no toolbars or controls are shown, you have to right click on the display and select Windows Mode to get your toolbar and controls back.
This happens exactly the same on both Win7 and Win8 on same PC and on another PC running Win7.
Richard is aware of this, but cannot reproduce on his PC.
If anyone else can please test this and report back on this it will help.

2.    Autoset is not taking one to best settings option, on every run it changes the Volt/Div to a different value. On the OEM program the Trigger marker is also set to the middle of the Waveform amplitude. Richard was working on this.

3.      Trigger Sweep One shot freezes waveform display, shows "Stop" and red led flashes on device. Unable to resume if setting is changed back to Normal or Automatic, but resumes if Factory default is pressed after changing back to Normal or automatic. Pressing Autoset actually also restarts the program after freezing. Richard was looking at this.

4.   Print preview screen underlines the words when typing in Notes. Can the underline be removed? Richard was looking at this.
   
5.     Can colors be changed in Print Preview just for the printout?

6.   The zoom function cuts off after 19 steps, but the counter can be clicked up into the hundreds without any further response after 19.
   
7.     The XY mode Lissajous pattern offset is in radians, will be changed to degrees and the second pointer which stays horizontal (incorrectly) now will be moved to vertical top. (In hand with Richard)

8.   The Horizontal Time/Div ranges from dropdown menu does not compare to the values in the dropdown in the control panel S (seconds) is also after minute instead of before and 5000 sec is max in control dropdown while 500.0S is max in menu dropdown.

9.   The OPEN6022BE does not go back to previous settings used when starting it. This is working in the OEM software  (Richard has this on his pending list)

10.   Display Ch1, CH2 and reference as the square wave from the output lug and Function generator. With Ch1 & Ch2 as source, enable Maths and use A/B and you will get noise pulses of 1V. Now change one of the Sources A or B to Reference wave and see what happens to the Maths channel. Is this correct? Unable to “lock” the Maths wave now it moves around. Reference trigger position has no effect. Select Reference as trigger and all the waves except reference start moving – unable to lock.

11.   When displaying a Reference waveform and then selecting Reference as trigger, the trigger name and voltage shows right hand top. Voltage is off the screen if more than 3 numericals at the right top. E.g if the value is Reference 1.36V the “V” is off the screen, this is also present in the OEM software.

12.   The OEM software had the date and time displayed at right hand bottom corner, as well as the ”Running” in the left bottom corner. Not displayed in OPEN6022BE.

13.   If you Turn off CH1 or 2 it still shows the CH1 =xxxV and TR1= xxxV in bottom left corner. Neither clear nor reset removes this or changes it to 0V, the measurement showed before turning off remains there. OEM software removes these indications completely from the bottom line when turning channel off.

14.   OEM software has an Autohide feature for the control panel. Not provided in OPEN6022be yet.

15.   On OEM software only the trigger selected and active shows as a trigger marker, the non-active trigger does not show, but OPEN6022BE shows all the triggers whether active or not.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: tpgates on March 26, 2014, 12:58:09 pm
I just purchased this 6022BE, have not touched a storage scope in 20 years, Tektronix last used. I immediately threw it on the output of my bench supply to view the ripple. The scope would not respond to any increase above 5VDC. I thought I was missing something in the setup. I cannot find any means to increase that 5vdc limit.

I thought that I would try a blog before returning it.

I appreciate any and all advice. I need 0 - 35vdc minimum and 115vac would be nice.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 26, 2014, 12:59:35 pm
I just purchased this 6022BE, have not touched a storage scope in 20 years, Tektronix last used. I immediately threw it on the output of my bench supply to view the ripple. The scope would not respond to any increase above 5VDC. I thought I was missing something in the setup. I cannot find any means to increase that 5vdc limit.

I thought that I would try a blog before returning it.

I appreciate any and all advice. I need 0 - 35vdc minimum and 115vac would be nice.

The driver or firmware clip everything at 5V, if you want to measure higher than that you need to set the probe & the software to 10x or higher.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 26, 2014, 02:17:45 pm
Hantek sells 100x probes as well as automotive ignition probes.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Bocks on March 26, 2014, 05:45:19 pm
I appreciate any and all advice. I need 0 - 35vdc minimum and 115vac would be nice.

Like any scope, the 6022BE is not isolated. If you need to look at an AC wall socket you will need a differential probe. Floating your computer by running it on battery, although it separates your computer and the 6022BE from ground, it's still dangerous to then connect your probe to a wall socket.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on March 26, 2014, 05:52:26 pm
I appreciate any and all advice. I need 0 - 35vdc minimum and 115vac would be nice.

Like any scope, the 6022BE is not isolated. If you need to look at an AC wall socket you will need a differential probe. Floating your computer by running it on battery, although it separates your computer and the 6022BE from ground, it's still dangerous to then connect your probe to a wall socket.

Then again, using a general purpose oscilloscope to probe high potential mains is probably not a good idea to begin with.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 28, 2014, 05:08:35 pm
Here are the latest updated copies of the OPEN6022BE User Manual.
Note: Do not use the Jumpshare viewer for the docx, it has problems, rather download it.

The docx: http://jmp.sh/bjUPzDS (http://jmp.sh/bjUPzDS)
The pdf: http://jmp.sh/rGGbLAc (http://jmp.sh/rGGbLAc)

Again any feedback, suggestions, corrections etc. are welcomed! There are parts in red that are in hand with RichardK and I will update those when his next binary version is released.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on March 28, 2014, 05:48:19 pm
I just purchased this 6022BE, have not touched a storage scope in 20 years, Tektronix last used. I immediately threw it on the output of my bench supply to view the ripple. The scope would not respond to any increase above 5VDC. I thought I was missing something in the setup. I cannot find any means to increase that 5vdc limit.

I thought that I would try a blog before returning it.

I appreciate any and all advice. I need 0 - 35vdc minimum and 115vac would be nice.

The driver or firmware clip everything at 5V, if you want to measure higher than that you need to set the probe & the software to 10x or higher.

Hello Richard, Thanks for all your work here
I guess the hardware clips : AD9288 A/D Converter
 Input Voltage Range (with Respect to AIN) ±512 mV p-p (excerpted from Analog Device data sheet)

Attached an extension of your 6022BE_Front_End.png
There, according to me,  we can see that due to analog mux the user can select 4 input range : 5Vpp, 2.5V, 1V, 0.5V
Do you agree with that ? and if yes, could you tell us which software position is related to hardware range

to Matchless
, OPEN6022BE User Manual :
14. Limitations and things to be aware of:
    xiii. ... " I'm not sure a 5V input signal in 1x mode is going to give a 5V signal at the node
between the 909K and 100K, but more like 500mv. This would mean the
probe in 1x mode is going to be safe all the way up to 50V and 500V in 10x "

a 5V input signal in 1x mode is going to give a 500mv signal at the node
between the 909K and 100K and at the ADC input. Anything more will be clipped by the ADC ( I'm not sure it's the safe way ! )

The A7 diodes protect the HRA input amplifier but this 5V protection is related to a 50V input.

Eric
(I'm French :-DD, not so rude :phew:, let me know what's wrong about my english, I will improve !!!  :-//)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 28, 2014, 06:36:38 pm
Eric,
       Thanks for your input. Do you have a high resolution copy of that schematic you posted? Would you have any issue if I put it in the manual sometime in the future?

Much appreciated!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marpolsdofer on March 29, 2014, 09:59:13 am
can some one help me with a minor problem I am having. Does the original hantek software do RMS in watts? It not necessary but it would be great to see what the amps are putting out and can adjust each channel accordingly with out calculating it and for other channels that may require lower power.

Also what is this I was reading about a new software? What makes it better? Where can I actually find it?

Thanks
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on March 29, 2014, 10:04:54 am
Matchless
Here are three versions of the schematic
pdf : http://jmp.sh/KDVL21k (http://jmp.sh/KDVL21k)
bmp zipped : http://jmp.sh/gQ9MADv (http://jmp.sh/gQ9MADv)
source : http://jmp.sh/DYYGEhr (http://jmp.sh/DYYGEhr)

I used "DesignSpark PCB" to edit the source : free download from http://www.rs-online.com/designspark/electronics/ (http://www.rs-online.com/designspark/electronics/)
Probably not the best tool for your purpose.

No problem for me if you  use and modify this files. This is an Hantek's design.
For convenience, I used absolute values : Vin range is [+5V, -5V]

Feel free to ask for modifications

Eric

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 29, 2014, 02:59:56 pm
Eric,
      Thanks, now I can see the blue labels a bit better. I think this will give some of the people who want to know these things a better insight into the front end.
For the manual I need to have it in A4, preferably portrait and need to move the labels for clarity. I will try SPlan which is very good for this kind of diagrams.
Much appreciated!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PedroDaGr8 on March 29, 2014, 03:09:49 pm
can some one help me with a minor problem I am having. Does the original hantek software do RMS in watts? It not necessary but it would be great to see what the amps are putting out and can adjust each channel accordingly with out calculating it and for other channels that may require lower power.

Also what is this I was reading about a new software? What makes it better? Where can I actually find it?

Thanks

To do that you need a current probe or a shunt resistor. Without having one of these, it's impossible to measure wattage alone. You need two of the three ( volts, current, resistance) to get watts. If you know the resistance of your load you can calculate watts. That being said if your load is dynamic (like a speaker) then the above methods are the only way to do it properly and get a real result. In summary, no it doesn't do watts because it's a voltage only device.

RichardK is writing the new software this thread deals with. Go back a few pages to find the latest post where he posts a build.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 29, 2014, 07:53:21 pm
Matchless
Here are three versions of the schematic
pdf : http://jmp.sh/KDVL21k (http://jmp.sh/KDVL21k)
bmp zipped : http://jmp.sh/gQ9MADv (http://jmp.sh/gQ9MADv)
source : http://jmp.sh/DYYGEhr (http://jmp.sh/DYYGEhr)

Eric, thanks a lot for providing those.  Interestingly, a PNG version of that BMP is smaller than the BMP zipped.  :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marpolsdofer on March 29, 2014, 09:10:53 pm
can some one help me with a minor problem I am having. Does the original hantek software do RMS in watts? It not necessary but it would be great to see what the amps are putting out and can adjust each channel accordingly with out calculating it and for other channels that may require lower power.

Also what is this I was reading about a new software? What makes it better? Where can I actually find it?

Thanks

To do that you need a current probe or a shunt resistor. Without having one of these, it's impossible to measure wattage alone. You need two of the three ( volts, current, resistance) to get watts. If you know the resistance of your load you can calculate watts. That being said if your load is dynamic (like a speaker) then the above methods are the only way to do it properly and get a real result. In summary, no it doesn't do watts because it's a voltage only device.

RichardK is writing the new software this thread deals with. Go back a few pages to find the latest post where he posts a build.

I have them just most of the scopes I have seen have a RMS wattage display and rather not calculate . All you do is play the test tone's, set it to below clipping with the scope and done but the RMS watts will give you a idea of what you are putting out. If the amp is CEA 2006 compliant it will out out what it says but if its not you might not even get 2/3 of what is say or that may be the draw.

 My amp and sub are I have no problems becaues my amp is 500 under the 1500 RMS load. My amp and speakers are the problem. The Amp at 4 Ohm is 50x4. Well my front are rated for 45 but they should be able to handle 50, but the amp can put actually put out 10 over rated for each channel so now its 60. I do not want to go more then 50 of the fronts so I would need to calculate or have a scope that shows watt RMS witch most scopes used do show. The rears can handle 100 so want the amp to push as much as I can there or get some 2 Ohm speakers and match the 2 Ohm rating.

I do have a clamp type multimeter to look at amps but its a chepo so I don't trust it. I will have to use my good one and do at the measurements  to double check from the scope and get all the other data needed to calculate.
I just rather have to use just the scope. Every scope I seen allows you to add loads and what not and give you watt RMS.

Well they read Vrms but they are displaying watts.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 29, 2014, 09:24:01 pm
I have them just most of the scopes I have seen have a RMS wattage display...

I would need to calculate or have a scope that shows watt RMS witch most scopes used do show...

Every scope I seen allows you to add loads and what not and give you watt RMS.

Well they read Vrms but they are displaying watts.

I've seen hundreds of different scopes over the last 30-some years, and I can't recall a single general-purpose scope that displays Watts.

Can you give us a few examples of what "every scope you've seen" are?  I'm really curious.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marpolsdofer on March 29, 2014, 11:33:42 pm
Well mostly all of them say Vrms and then what ever the number is. However, amps are rated in watt RMS and the number next to Vrms is showing the number corresponding to the rating in watts so it seams.
or am I missing something.

If you watch the video here you will see what I mean. 
https://www.youtube.com/watch?v=D1AYZL72PTY (https://www.youtube.com/watch?v=D1AYZL72PTY)

If some one can shine light on the subject that would be great.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PedroDaGr8 on March 30, 2014, 12:28:57 am
Well mostly all of them say Vrms and then what ever the number is. However, amps are rated in watt RMS and the number next to Vrms is showing the number corresponding to the rating in watts so it seams.
or am I missing something.

If you watch the video here you will see what I mean. 
https://www.youtube.com/watch?v=D1AYZL72PTY (https://www.youtube.com/watch?v=D1AYZL72PTY)

If some one can shine light on the subject that would be great.
Based on what I see, the issue is that guy doesn't know how to use an oscilloscope. If you read the display it's clearly reading AC Vrms. So unless he a secondary test rig feeding that oscilloscope his number is wrong. First off it looks like he's directly wired from the amp into the oscilloscope. Then he set the probe divider to 1:10. With no divider, he's getting voltage readings 10x too high. Unless there's something else going on that's NOT watts. In fact if you divide his voltage by 10 to get 30V. Then apply ohms law, assuming a constant 2 ohm load (not a good assumption with a speaker) you get 450W. Not 300W like he says.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 30, 2014, 12:52:10 am
Well mostly all of them say Vrms and then what ever the number is. However, amps are rated in watt RMS and the number next to Vrms is showing the number corresponding to the rating in watts so it seams.
or am I missing something.

If you watch the video here you will see what I mean. 
https://www.youtube.com/watch?v=D1AYZL72PTY (https://www.youtube.com/watch?v=D1AYZL72PTY)

If some one can shine light on the subject that would be great.

Well I can honestly say I have never seen this before (in a scope), check out 9:32 into the video below. Any opinions?

https://www.youtube.com/watch?v=QSzt9ZrQqJ0 (https://www.youtube.com/watch?v=QSzt9ZrQqJ0)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 30, 2014, 01:01:24 am
Well mostly all of them say Vrms and then what ever the number is. However, amps are rated in watt RMS and the number next to Vrms is showing the number corresponding to the rating in watts so it seams.
or am I missing something.

Yes, you are.  But it's not all your fault.  He's missing something too.  Putting the RMS units after an AC Voltage reading doesn't turn it into Watts.  Sorry.

Quote
If you watch the video here you will see what I mean. 
https://www.youtube.com/watch?v=D1AYZL72PTY (https://www.youtube.com/watch?v=D1AYZL72PTY)

If some one can shine light on the subject that would be great.

Thanks for the link.  The instrument he is using is a Fluke 105B Scopemeter (Series II), that goes for about a grand.  It can display a large DMM readout, along with a signal trace.  Which is handy.  And like I suspected, it's not reading out Wattage... it says Vrms plain as day. 

That said, there has to be something else going on,  because there's no way he was pumping >300 VAC into a 2-ohm speaker.  :)  He has something else tied into the circuit (a watt-to-volt converter?), and whatever that device is would also work on other scopes.  Why don't you ask him?

[Also, if the 2-ohm speaker was the only load he had on that amp, driving it at those levels at 40 Hz would be WAY louder than anything in that video.  He's got to have a large dummy load of some kind.]
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 30, 2014, 01:45:09 am
Well I can honestly say I have never seen this before (in a scope), check out 9:32 into the video. Any opinions?

https://www.youtube.com/watch?v=QSzt9ZrQqJ0 (https://www.youtube.com/watch?v=QSzt9ZrQqJ0)

Thanks for the additional video link, Pickle.  Looks like a $200 Velleman also has a similar capability as the Fluke.  However, it actually labels the units properly in Watts, which Fluke doesn't. 

Since these are both combo scope+DMMs, they have a few special features not ordinarily found on general-purpose scopes.  Doing the calculations to display Vrms as Watts isn't difficult, as long as you know the resistance you're pumping in to.  This is an input setting the User must supply.  And on the Velleman, he actually showed that selection process.  But on Page 3-7 of the Measurements section on the Fluke, it says, "WATT AC METER: Measure the AC audio watts from the signal in Meter mode. This is done with DC-coupled input. You can choose 1, 2, 4, 8, 16, or 50? as reference impedance.".

You can do the same type of thing on any of the newer DSOs with advanced Math capabilities.  You just need V^2/R, but most don't have a Sqr() function, so you'd need to tie both channels to the same test point, and use CH1*CH2/ohms.

To the OP, I'd suggest you could grab one of the Vellemans that support this specialized Measurement function (HPS50?).  The Velleman is only a single channel, and maybe 12 MHz bandwidth, but you don't need much for audio work. 

Or just get the reading in Vrms at clipping, and do the calculation to see the wattage value (V*V/2, or 4, or 8 ).  You don't really need a continuous readout directly in Watts to be able to detect the max output threshold.  I suspect you can get a pocket calculator for less than a Fluke scopemeter, or even a Velleman.  ;)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marpolsdofer on March 30, 2014, 01:54:42 am
I just more or less wanted a watt reading with out calculating it. Then I would set my front to a safe RMS and the rear well just need to not clip.
I don't know about the humming but in the other vids they say the subs are disconnected, maybe he had something else hooked up and that could explain that . I can call them and ask they seem friendly and knowledgeable last I order from them.

I figure I ask here first since people here know about this scope.

Anyways I have 2 Kicker 12" CVX's 2 Ohm to pair with my old zx 1000.1. All I need to worry there is to prevent clipping.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 30, 2014, 02:13:00 am
Once richard gets the basic software done to his satisfaction it may be an idea to remind him of this watt calculation. It's a novelty but still interesting.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 30, 2014, 02:34:47 am
I just more or less wanted a watt reading with out calculating it.

Ah, a lazy son of a... gun.  :D

Quote
I don't know about the humming but in the other vids they say the subs are disconnected, maybe he had something else hooked up and that could explain that . I can call them and ask they seem friendly and knowledgeable last I order from them.

That's OK.  We've got it all figured out now, and explained above.  They're using a resistive dummy load, and a meter with a special calculation function built in.

Quote
I figure I ask here first since people here know about this scope.

Well, neither the stock Hantek software, nor the improved version that RichardK is working on, has the capability you're asking for.  So if you really want the Wattage readout, you'll have to look elsewhere.  That was actually explained some posts back.  It doesn't do it.

And this special function is not as widely available as you've suggested... even on scopemeters.  I actually own a ~$600 handheld scopemeter that's just a few years old (3-4), and it has no such functionality.

Quote
Anyways I have 2 Kicker 12" CVX's 2 Ohm to pair with my old zx 1000.1. All I need to worry there is to prevent clipping.

If you just want to see where it occurs, so you can back off and set a maximum there, you could do that with the 6022BE and even the stock software.  Use the 10x setting on the probe.


There's one other thing worth keeping in mind.  While it's fun and easy to make power output measurements into dummy loads, they have their limitations.  For example, while an amp may not start clipping until 300W into a resistor, you can't listen to a resistor.  Speakers are reactive devices (mostly inductive) and one rated at 4-ohm (for example) may cause an amp to work harder at some frequencies, and thus start clipping, even when it's "not supposed to".
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PedroDaGr8 on March 30, 2014, 03:18:59 am
This is what I was saying earlier. Speakers are inherently non-linear devices. A speaker rated at 2ohms can go as high as 20 ohms depending on the frequency. Plus stability at one frequency does not inherently guarantee stability at all. To ensure that you need to do a sweep and look for clipping at all relevant frequencies.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 30, 2014, 04:11:27 am
This is what I was saying earlier. Speakers are inherently non-linear devices. A speaker rated at 2ohms can go as high as 20 ohms depending on the frequency. Plus stability at one frequency does not inherently guarantee stability at all. To ensure that you need to do a sweep and look for clipping at all relevant frequencies.

Completely correct!  However, if the OP (and those in the videos linked to) cared about when clipping really started, they would be looking for distortion products (spurious harmonic components) in the frequency domain, and not for visible deformation of the sinusoidal waveshape. 

At one point in the Velleman video, the author said something like, "There, that looks clean... so XX watts".  When in fact, there must have been at least 5% distortion in the waveshape at that point.  And in the first video, the demonstrator cranked the amplitude up so it was clipping so hard it looked like a square wave (at 400W!).  I was cringing, thinking how if an actual speaker had been hooked up, he would have blown the cone right off it.   :scared:

This is just a rough metric, but it apparently has some value in certain contexts, since the claimed ratings are apparently bogus in many situations.  I.e., advertising hyperbole.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on March 30, 2014, 05:08:41 am
To be honest I was only interested in the math being performed in the scope.

As for audio related discussions online... no comment.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: marpolsdofer on March 30, 2014, 08:19:31 am
I do have a CD to preform all needed frequency and test them each, at least what everyone seems to use.

As for distortion detectors like the SMD DD-1 I did not discover it until the day I got the scope.

I don't plan on being at more then half level much if at all so I think this will do, besides it does have other uses. I could have used this a few other times.

Thanks for you help guys.

I don't run across many people talking bout dummy load when seating up the amp. This video as hiding on youtube but this actually stuff better then most people. 
https://www.youtube.com/watch?v=QSzt9ZrQqJ0 (https://www.youtube.com/watch?v=QSzt9ZrQqJ0)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 30, 2014, 09:05:20 am
 Eric,
       I have redrawn your schematic to make it easier to fit a page in the manual. I also made some small changes. Would you be so kind as to check it over. I usually make mistakes!
Thanks.

Here it is: http://jmp.sh/bEsySoI (http://jmp.sh/bEsySoI)

Thanks

Edit updated picture
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on March 30, 2014, 03:57:58 pm
Your probe schematic looks a bit odd with X1/X10 and X100 next to it. I only see a X1/X10 probe.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 30, 2014, 04:21:12 pm
You are right, I meant to add x100 as well, changed my mind and did not remove that.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on March 30, 2014, 06:00:46 pm
Matchless :
at Mux output, R5 is 1k Ohm (R5, R6 R7 refer to R18 R19 R22 on the PCB)
Please suppress the diodes reference (2N000) in the AD9288, it's a dummy reference inserted by my software.

About 6022's design
The diagram is not complete. The ADC measures the signal between pin 2 and pin 3 (respectively 11 and 10 for channel B)
I don't see where pin 10 or 3 are connected on the PCB. What sounds strange for me is that there is no offset at ADC input.

So I suppose the complementary input to be grounded

AD9288 data sheet : The nominal input range is 1.024 V p-p centered at VD × 0.3
Hantek's design seems to be centered at 0V

applying -5V referred to ground  at the box input (Vin) roughly means -0,5V at ADC input. The ADC data sheet lists -0,5V as max rating for the Analog inputs.
Big stress if you exceed the -5V..
I hope something is wrong in the diagram. The only ADC protection are the diodes shown in the Equivalent Analog Circuit of AD9288.
The A7 diodes protect the input of HRA but with this protection, -5V could be applied to the AD9288 input (100mA in the diode, reduced to 90 thanks to the HRA short-circuit output limitation).

The answer may be in the AD9288 data sheet : Special care was taken in the design of the analog input stage of the AD9288 to prevent damage and corruption of data when the input is overdriven.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on March 30, 2014, 06:17:24 pm
If the members agree with the fact that the complementary input is grounded, the diagram would be modified as attached
http://jmp.sh/PSIBOEv (http://jmp.sh/PSIBOEv)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 30, 2014, 06:38:12 pm
Eric, thanks I have updated the schematic.
I will add the ADC change also after hearing what the others have to say about it.
Did you see the 6022be manual states that the input protection is 35V p-p?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on March 30, 2014, 08:19:37 pm
OK, page 58, 35V pp -> ADC input=  -1.75V -> I diode = 25mA, that's better. Still above Absolute Maximum Ratings
Rather than Input Protection, I would say "max input without damage"
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 31, 2014, 05:29:36 am
Here are three versions of the schematic
pdf : http://jmp.sh/KDVL21k (http://jmp.sh/KDVL21k)
bmp zipped : http://jmp.sh/gQ9MADv (http://jmp.sh/gQ9MADv)

No problem for me if you  use and modify this files. This is an Hantek's design.
Once nice thing about a schematic like this is it makes plain the fact that the 6022BE, unlike most scopes that have 3 or 4 decades of Sensitivity settings, has only one decade.  I.e., 100mV/div to 1V/div.  That's one area they saved money by compromising on (along with the limited sample rates, and no real triggering). [Normally, you see anywhere from 10 mV-5V/div, to 1 mV-10V/div.]

The settings below 100mV/div are just zoomed (e.g., like an Agilent with 4 mV/div claims 1 mV/div, by zooming).  Since at that level, the FS range of the ADC is 1,024 mV, and it's 8-bits (256 levels), that means the LSB is 4 mV.  So it's not surprising to see "noise" on the 20 mV/div setting, since in addition to real noise (that shielding and proper grounding can help minimize), the uncertainty present in the LSB will result in jitter of +/-4 mV, all by itself.  Which becomes more visible the farther in you zoom.

Not knocking it... just thinking out loud.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on March 31, 2014, 03:22:28 pm
Mark_O,
             I hope you don't mind if I add your last observations to the User Manual.

Thanks!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on March 31, 2014, 03:50:42 pm
Mark_O,
             I hope you don't mind if I add your last observations to the User Manual.
Thanks!

Not at all.  Every instrument has some limitations.  The key is being aware of them, and understanding how they're still useful, and can provide valuable results. 

Hantek makes all this really opaque, which doesn't help (us) at all.  Ranging from claiming the device has 1M/channel, when it doesn't (the 1M is in your PC, and the device has only 1K/channel), to selectable sensitivity ranges that truncate well below a full-screen level, to pre/post-trigger point selection (in the specs) that flat-out don't exist.  Etc.  For someone to use the 6022BE effectively, they need not only quality software (which RichardK is providing), but also an understanding of the scope's true capabilities.  Many people here have helped contribute to that understanding.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 01, 2014, 05:58:55 am
Mark_O, thanks I have done so. I will post the latest copy of the user manual soon and if you do not mind please see if it looks correct, as I am sort of out of my comfort zone already!
I am waiting for RichardK's next update which should help me clear some of the parts in the manual in red at the moment.

Thanks again!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on April 02, 2014, 06:31:24 pm
Sorry about the delay between releases, been super busy of late.... Here is the latest binary... Not too many ground breaking changes, mostly just tying up loose ends and other bug fixes.

PR18 Download: http://jmp.sh/k0tTgXg (http://jmp.sh/k0tTgXg)

What's New:
-----------------------------------------------------------
1. Fixed a bug where not able to turn grid off in Phosphor mode.
2. Implemented simple waveform brightness support for 64bit operating systems.
3. Increased Output Window height so first measurement item is visible.
4. Implemented the Probe main menu items for CH1, CH2 and Math Channel.
5. Fixed a bug where a channel might not fully clear when changing to None in
   Demo Mode.
6. Changed Phase Offset units from Radians to Degrees.
7. Fixed an inconsistency in cursor over levers and dragging levers witch might
   cause a situation where a lever won't move even when the cursor changes
   suggesting you can.
8. Added an alternative rendering option in case AlphaBlend() fails, some 32 bit
   systems don't work well with AlphaBlend() apparently, especially in systems
   with multiple display configurations.
9. Reordered some Time Division menu items.
10. Added Dynamic option to Reference Channel's Function Generator (works like Demo Mode).
11. Implemented initial support of saving/restoring GUI settings on close/restart.
12. Increased Trigger Information render width to prevent voltages from rendering off
   screen.
13. Implemented hiding of Bottom Pane voltage labels when respective channel is hidden.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on April 02, 2014, 06:38:24 pm
No need for "Sorry".

Personally I am grateful for updates as and when you find any spare time to release such. We all have lives outside this forum and I understand that this is JUST a hobby project.

You have alreday put Hantek's original coders and ongoing software support team to shame !

Fraser
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on April 03, 2014, 12:10:09 am
No need for "Sorry".

Personally I am grateful for updates as and when you find any spare time to release such. We all have lives outside this forum and I understand that this is JUST a hobby project.

You have already put Hantek's original coders and ongoing software support team to shame !

No kidding!  I'd be surprised if, over the years this product has been available, there has been more than 1 or 2 updates a year.  And those coming with little or no clue as to what had changed.

This is a really nice set of improvements.  Thanks.

Off the subject a bit:  One thing I'm not clear on, since I've never had to deal with it as a programmer, is how the screen draws vary between OS's, and 32/64-bit systems.  You've commented several times about AlphaBlend variations, and I don't really have a good picture of what's going on there?  I wouldn't expect you to write a book on it (that's probably already been done!), but a few line summary/overview might be helpful.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on April 03, 2014, 12:31:32 am
No need for "Sorry".

Personally I am grateful for updates as and when you find any spare time to release such. We all have lives outside this forum and I understand that this is JUST a hobby project.

You have already put Hantek's original coders and ongoing software support team to shame !

No kidding!  I'd be surprised if, over the years this product has been available, there has been more than 1 or 2 updates a year.  And those coming with little or no clue as to what had changed.

This is a really nice set of improvements.  Thanks.

Off the subject a bit:  One thing I'm not clear on, since I've never had to deal with it as a programmer, is how the screen draws vary between OS's, and 32/64-bit systems.  You've commented several times about AlphaBlend variations, and I don't really have a good picture of what's going on there?  I wouldn't expect you to write a book on it (that's probably already been done!), but a few line summary/overview might be helpful.

AlphaBlend() is a windows GDI function that uses graphics hardware to do alpha channel blending (Transparencies and such), and a while back when XP first came out (And GDI AlphaBlend also came out) it wasn't too uncommon to come across hardware that didn't support Hardware Alpha Blending, but pretty much every graphics processing unit made today supports it, so you might think it would be odd for modern day systems to have issues with it, but alas they do.

It's not the hardware, it's Microsoft's AlphaBlend GDI function and it has all sorts of issues with 64 bit versions of Windows and other systems (32 or 64bit) that have non standard display configurations (Like dual displays)... Apparently Microsoft has been aware of these issues since Windows 7, and has officially stated that there is a bug, but have not fixed the issue or even addressed when a possible fix may be issued.  |O

I wasn't aware of all the fiasco's involved when I started using it for brightness effects (and eventually Phosphor mode)... You learn something new everyday I guess...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on April 03, 2014, 12:51:30 am
Hey Richard, remember this?

http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937 (http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on April 03, 2014, 03:05:48 am
Hey Richard, remember this?

http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937 (http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937)

Yeah... what about it? ... I see no replies *shocker*
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: pickle9000 on April 03, 2014, 03:37:58 am
Only,  25 days 16 hours 9 ministes 15 seconds to go!!

I love the spelling "ministes", it would be fantastic if they come up with an answer. Unfortunately the answer will probably be that the manual was incorrect and this feature does not exist. 
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on April 03, 2014, 03:49:42 am
AlphaBlend() is a windows GDI function that uses graphics hardware to do alpha channel blending (Transparencies and such), and a while back when XP first came out (And GDI AlphaBlend also came out) it wasn't too uncommon to come across hardware that didn't support Hardware Alpha Blending, but pretty much every graphics processing unit made today supports it, so you might think it would be odd for modern day systems to have issues with it, but alas they do.

It's not the hardware, it's Microsoft's AlphaBlend GDI function and it has all sorts of issues with 64 bit versions of Windows and other systems (32 or 64bit) that have non standard display configurations (Like dual displays)... Apparently Microsoft has been aware of these issues since Windows 7, and has officially stated that there is a bug, but have not fixed the issue or even addressed when a possible fix may be issued.  |O

I wasn't aware of all the fiasco's involved when I started using it for brightness effects (and eventually Phosphor mode)... You learn something new everyday I guess...

Thanks for the education, Richard.  Yes, any of us who've had to deal with MS API's over the years can feel the pain.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on April 03, 2014, 03:54:02 am
Hey Richard, remember this?

http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937 (http://www.hantek.org/asken/iaskdetail.aspx?id=2014022803412937)

Yeah... what about it? ... I see no replies *shocker*

Well, in fairness to them, the title IS "Go Ask Hantek".  No claim is made that they will bother to answer.   :-[
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Bocks on April 03, 2014, 03:59:26 am
8. Added an alternative rendering option in case AlphaBlend() fails, some 32 bit
   systems don't work well with AlphaBlend() apparently, especially in systems
   with multiple display configurations.

Works great on my dual monitor setup. Thanks!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 03, 2014, 05:02:30 pm
RichardK, excellent progress! Its quite amazing, what you are doing! Just from my side thanks again. Its like a  series on TV, I cannot wait until the next one arrives!.

I have had a quick look and have listed some issues. Some are in hand with you already and some may be just my own ignorance. These are just to help you sort out any bugs. If anyone else can confirm the issues that would maybe help you more:

1.    Autoset is not taking one to best settings option, on every run it changes the Volt/Div to a different value. On the OEM program the Trigger marker is also  set to the middle of the Waveform amplitude. Richard was working on this.
2.   Print preview screen underlines the words when typing in Notes. Can the underline be removed? Richard was adding this function.
3.   OEM software has an Autohide feature for the control panel. Not provided in OPEN6022be yet. Not sure if this is needed or useful to anyone.
4.   The OEM software had the date and time displayed at right hand bottom corner, as well as the ”Running” in the left bottom corner. Not displayed in OPEN6022BE.
5.   On OEM software only the active trigger marker shows, the non-active trigger does not show, but OPEN6022BE shows all the triggers whether active or not. Not sure if this is intentional or not.
6.   Does not keep GUI settings yet, if you close and reopen later. Not sure if it should, but also does not stay in Demo mode if you shut down and restart, but the settings part seem to work now! When closing down while rendering Phosphor persistence, it restarts in Phosphor mode correctly, but then incorrectly indicates that it is in Normal mode.
7.   The zoom function cuts off after 19 steps, but the counter can be clicked up into the hundreds.
8.   In XY mode the second source pointer which stays horizontal (incorrectly) still needs to be moved to vertical top when in XY mode. (In hand with Richard)
9.   Display Ch1 Ch2 and Reference wave as square wave. Select Trigger sweep Normal. Move reference wave trigger position marker to the lower part of the reference waveform. Ch1 and Ch2 suddenly goes off the screen to the top.
10.   Reference wave was out of phase with internal 1k waveform, now nearly in phase, but square wave shows it is still out by a small margin.
11.   Can select Reference as trigger even if Reference waveform is off. Reference shows 500mV while Math selected as trigger when off shows 0V.
12.   Right click on waveform marker and a pop up Hide box comes up and if cursor is over marker it switches the channel off. But Hide can be right clicked anywhere in this left margin still displays popup, which does nothing obviously.
13.   Left clicking mouse cursor anywhere on screen gives Ch1 and Ch2 voltage readings in a small box which corresponds to whatever position the mouse cursor is. Not sure if this is intentional or what it is supposed to be doing?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on April 04, 2014, 01:23:33 am
1.    Autoset is not taking one to best settings option, on every run it changes the Volt/Div to a different value. On the OEM program the Trigger marker is also  set to the middle of the Waveform amplitude. Richard was working on this.

On the Todo, I'll get around to fixing it eventually but lower priority at the moment.

Quote
2.   Print preview screen underlines the words when typing in Notes. Can the underline be removed? Richard was adding this function.

Also on the Todo, probably be done in next release.

Quote
3.   OEM software has an Autohide feature for the control panel. Not provided in OPEN6022be yet. Not sure if this is needed or useful to anyone.

I never used the Autohide personally.

Quote
4.   The OEM software had the date and time displayed at right hand bottom corner, as well as the ”Running” in the left bottom corner. Not displayed in OPEN6022BE.

On the Todo, should be done in next release.

Quote
5.   On OEM software only the active trigger marker shows, the non-active trigger does not show, but OPEN6022BE shows all the triggers whether active or not. Not sure if this is intentional or not.

I intentionally did it this way because sometimes I like to adjust both triggers then toggle between them, it's just a pain to have to change trigger sources just to adjust the trigger level.

Quote
6.   Does not keep GUI settings yet, if you close and reopen later. Not sure if it should, but also does not stay in Demo mode if you shut down and restart, but the settings part seem to work now! When closing down while rendering Phosphor persistence, it restarts in Phosphor mode correctly, but then incorrectly indicates that it is in Normal mode.

Demo mode is enabled automatically if no device detected, you can manually enter the mode from the Acquire menu. About the Phosphor mode bug, will be fixed in next release.

Quote
7.   The zoom function cuts off after 19 steps, but the counter can be clicked up into the hundreds.

The cutoff point varies... It depending on the timebase, it has to do with the DrawWaveInYT function. Hantek's implementation has limits on zooming past certain points... I'll think of something more ideal eventually :)

Quote
8.   In XY mode the second source pointer which stays horizontal (incorrectly) still needs to be moved to vertical top when in XY mode. (In hand with Richard)

Also on the Todo, it's not as trivial as it sounds to implement it, but if not next release should be done by the following... I just want to implement it in a way that isn't hackish as I never intended there to be levers on the Top Pane (doh).

Quote
9.   Display Ch1 Ch2 and Reference wave as square wave. Select Trigger sweep Normal. Move reference wave trigger position marker to the lower part of the reference waveform. Ch1 and Ch2 suddenly goes off the screen to the top.

Will look into this.

Quote
10.   Reference wave was out of phase with internal 1k waveform, now nearly in phase, but square wave shows it is still out by a small margin.

Internal waveform has offset due to noise causing premature triggering, Reference wave & Demo Mode waves are pure, so they trigger exactly on wave edge.

Quote
11.   Can select Reference as trigger even if Reference waveform is off. Reference shows 500mV while Math selected as trigger when off shows 0V.

Will check this out also.

Quote
12.   Right click on waveform marker and a pop up Hide box comes up and if cursor is over marker it switches the channel off. But Hide can be right clicked anywhere in this left margin still displays popup, which does nothing obviously.

I'll make the option grayed out if there isn't a Lever under the cursor.

Quote
13.   Left clicking mouse cursor anywhere on screen gives Ch1 and Ch2 voltage readings in a small box which corresponds to whatever position the mouse cursor is. Not sure if this is intentional or what it is supposed to be doing?

It's not actually on left click, it's a popup hint that usually triggers on left clicks, but it's just a quick and dirty measurement (similar to Cross cursors).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 04, 2014, 05:12:46 pm
RichardK,
              Thanks for all the feedback. The following issue you replied on (see below), just does not make sense to me or else I am having an Alzheimer moment! The popup box with Ch1 & Ch2 voltages shown are related to the position of the mouse pointer and the popup box appears after a moment of delay as you move the mouse pointer onto the graticule area from outside of it, then goes off after a short period of display. Now if you keep the mouse pointer on the graticule area and just move it to any position and left click the mouse, then the box pops up again with different voltages related to that point you moved it to and the waveforms. Why would one want to see Ch1 &Ch2 voltages related to the mouse pointer clicks so far away from the waveform?
I just cannot see what this could be used for or it is performing differently to what you intended? Most likely it is just my ignorance at play here......

Quote
    13.   Left clicking mouse cursor anywhere on screen gives Ch1 and Ch2 voltage readings in a small box which corresponds to whatever position the mouse cursor is. Not sure if this is intentional or what it is supposed to be doing?


It's not actually on left click, it's a popup hint that usually triggers on left clicks, but it's just a quick and dirty measurement (similar to Cross cursors).


I have picked up another small glitch, if you use Zoom and then click the Default Settings it does not reset Zoom to zero.

And just another thanks for the time and effort you are putting into this! It is much appreciated.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: nyt on April 05, 2014, 11:32:06 pm
I'd just like to say excellent work on this.

I'm also curious if it would be possible to include a THD operation in the mathematics functions.

Cheers.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 06, 2014, 04:23:43 pm
I have updated some things in the User Manual.

Do not use the Jumpshare viewer as it is broken and I have reported it, but it is still the same.

Here is docx: http://jmp.sh/Eyesdan (http://jmp.sh/Eyesdan)
Here is pdf: http://jmp.sh/PDdz9CD (http://jmp.sh/PDdz9CD)

Again please give feedback, mistakes, corrections etc!

Edit: Fixed link
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on April 06, 2014, 04:38:58 pm
Hi Matchless,

Great work.

Not that it matters much but your file links are both the same and are for the PDF format file  ;)

Aurora
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 06, 2014, 06:02:03 pm
Thanks Aurora, have fixed it!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: arhi on April 08, 2014, 03:07:45 am
great work guy's

saleae logic uses the same cypress chip and they are getting 24MHz LA stream directly from the chip to the pc; now from what I understand Richard is writing this open6022be software as a frontend using SDK so the driver sends firmware to the cy, and then SDK talk to cy and gets data the same way original crappy app does. what I find interesting is maybe ditching the whole hantek driver and rewriting the firmware completely.... if saleae can stream 24MHz from the cy (that's half of what this scope can sample) maybe adding a functionality to stream 24MHz from the adc and then do everything else in the software? triggering, fft, logging ? was anyone thinking about something like that?

I went quickly trough the pictures but I didn't see if anyone reverse engineered the link between cy and the analog part so that we can properly configure it from custom firmware

@richardK, any reason for not pushing this on sourceforge/github?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on April 08, 2014, 08:45:42 am
if saleae can stream 24MHz from the cy (that's half of what this scope can sample) maybe adding a functionality to stream 24MHz from the adc and then do everything else in the software? triggering, fft, logging ? was anyone thinking about something like that?

That's already being done.  The Hantek samples two channels simultaneously, at up to16 MSa/s (which is 32 MB/s), streaming them directly to a buffer in the PC (software dependent size, currently up to a meg).  Even though the Hantek says they support triggering (and even claims 0-100% pre/post trigger acquisitions, which is baloney), it's very crude

In its High-Speed 48MSa mode, it will detect the presence of a trigger condition _somewhere_ in the the current on-chip buffer (1 or 2 kB, I forget).  And on each small sample burst sent over, that trigger position within it will be different.  I.e., there's no circular buffering going on at all.  It's 'wipe and restart' on every cycle.

Exactly how triggering is done in the slower streaming mode is a question for RickardK.  But I'd guess it uses a similar technique to detect a start, then just dumps until the buffer is full.  Since the buffer is so much bigger, the fact that the trigger point is constantly shifting +/-0.1% from the head of the buffer is something the software can hide from the user. 
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: arhi on April 08, 2014, 10:43:37 pm
Well I understand hantek's original firmware is doing that but "we" (actually RichardK) are fetching data trough SDK functions. I don't see a way to get a 32 MHz stream from hantek with USB buffer size I select, or I'm missing some pages of the SDK? I'm actually more interested in 32 MHz from a single channel then 2x16 MHz but I guess it's not a big difference in sw.

I see that front end before ADC is being reverse engineered, any chance someone did the same for the MCU connections? I'm personally not too interested in 6022BE as oscilloscope but more as a nice ADC platform with CY on board :D and for that I need to work on CY firmware and not on hantek SDK (taking into account that I have two CY boards now and still haven't written a blink led for CY due to serious lack of time this is just a theoretical talk until I get some free time on my hand, and even then I have few things that are more important)

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on April 09, 2014, 02:50:09 am
Well I understand hantek's original firmware is doing that but "we" (actually RichardK) are fetching data trough SDK functions.

So?

Quote
I don't see a way to get a 32 MHz stream from hantek with USB buffer size I select, or I'm missing some pages of the SDK?
 
You just allocate a buffer of the appropriate size, and give the SDK a pointer and size spec, with a timebase setting slow enough for it to provide a stream (rather than tiny 2k chunks).

Quote
I'm actually more interested in 32 MHz from a single channel then 2x16 MHz but I guess it's not a big difference in sw.

Sorry, you're SOL on that.  As previously discussed here, the device and SDK always run and ship both channels.  So it actually is a big difference, but has to be done at the firmware level, inside the Cypress chip.  Then it would need to be propagated thru the SDK, and into the Application layer.

Quote
I see that front end before ADC is being reverse engineered, any chance someone did the same for the MCU connections? I'm personally not too interested in 6022BE as oscilloscope but more as a nice ADC platform with CY on board :D and for that I need to work on CY firmware and not on hantek SDK

Have at it!  :)  We'd love to see what you come up with.

Quote
(taking into account that I have two CY boards now and still haven't written a blink led for CY due to serious lack of time this is just a theoretical talk until I get some free time on my hand, and even then I have few things that are more important)

Ah!  You'd like someone else to do the work for you.  A common enough dilemma.   ::)   ;D
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: arhi on April 10, 2014, 12:55:27 am
Ah!  You'd like someone else to do the work for you.  A common enough dilemma.   ::)   ;D

 :-[ nope, just don't want to do work someone else already spent time doing so trying to figure out what's already being done. The RichardK app works just fine for the scope itself (without any changes I see some 8.128mV p2p noise btw), I did not unpack the source (appears to be pass protected and looks like I skipped the post where pass is revealed) but taking into account original fw always sends both channels it looks like "must write new firmware from scratch" so it goes to the list of projects to do (attm second on the list so should be on desk really soon)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 14, 2014, 06:49:48 am
Hi,
    While waiting for the next updated binary, I want to try and tidy up some bits in the User Manual and get rid of the part 3 in italics,
I would be grateful if some people could just test the full screen function with reference to the part in italics and give some feedback. Basically I need to verify whether you get the toolbars and controls back automatically or need to do it by selecting Windows Mode.
Thanks in advance:

Quote
Click to enable Full Screen display without any toolbars, controls, measure display or measure output. There are 3 ways to go back to the normal display:
1.   Push the ESC key on your keyboard or
2.   right click on the display and select Window Mode or
3.   left click on the small icon in the left top corner and select Restore.
Note:  Step 3 will return display to normal size, but without any toolbars or controls. Right click on the display and select Window Mode to get the toolbars and controls back. Mine does this, but RichardK  says his comes back in this way with toolbars and controls showing.
If anyone else cares to test this please come back to me so that I can lay this one to rest!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: LETARTARE on April 15, 2014, 03:01:16 pm
Hello,
Congratulations for this great software I used for one week to measure control signals on an Arduino board and I am very happy.
@Matchless
Your documentation is very well top.
Quote
If anyone else cares to test this please come back to me so that I can lay this one to rest!
I use VISTA Pro Pack2, and it works exactly as you describe.

Sincerely.

This text is translated by google.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: quantumvolt on April 15, 2014, 05:20:02 pm
I just ordered this from eBay. I found a copy of a manual but I found little information about 'File, Save Data' Ctrl+S. I suppose the file is saved on PC disk, but which format? There were no mention/picture of file extension or menu for multiple saved files.

Also I read that there is no time stamp. I will only use 1 channel for single captures on booth/shutdown on 'slow' changing PSU's and voltage references (maybe 1 mS to a few minutes). Since the scope always samples both channels, I plan to use the other channel as an analogue 'clock' (uC generated rising stepped 'event-signature' voltage). Will I be able to save the two channels in a format that  I can read with other software to study further?

Thanks.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: LETARTARE on April 15, 2014, 05:41:31 pm
@quantumvolt,
Hello,
With "Open6022BE V1.0 beta PR18"
File->Export->ExportSetting->Export type = *.txt
File->Export->Image Preview and Export ...

Sincerely
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 15, 2014, 05:49:33 pm
Hello,
Congratulations for this great software I used for one week to measure control signals on an Arduino board and I am very happy.
@Matchless
Your documentation is very well top.
Quote
If anyone else cares to test this please come back to me so that I can lay this one to rest!
I use VISTA Pro Pack2, and it works exactly as you describe.

Thanks for the feedback. That helps a lot.

I hope someone on XP will also come back on this!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 15, 2014, 05:54:53 pm
Here is the latest version of the Open6022be User Manual.
Do not open the docx with Jumpshare viewer it gives spelling mistakes, rather download and open.

PDF: http://jmp.sh/ZkC2JXk (http://jmp.sh/ZkC2JXk)
Docx: http://jmp.sh/fOg8uRl (http://jmp.sh/fOg8uRl)

Again any suggestions, corrections, additions etc. are welcome.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: quantumvolt on April 15, 2014, 06:05:57 pm
Thanks for the .txt fomat.

I looked at the .pdf manual over - I understand that in the open SW, the two channels must be exported separately to different files? But the original SW stores both channels parallel in one file?

Thanks.
(I run old XP, but the box hasn't left China yet (ordered it today)).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 15, 2014, 08:47:29 pm
I looked at the .pdf manual over - I understand that in the open SW, the two channels must be exported separately to different files? But the original SW stores both channels parallel in one file?

Thanks.
(I run old XP, but the box hasn't left China yet (ordered it today)).

RichardK is still developing the new OPEN6022BE software and has indicated that he is aware that the txt files only support single channel exporting.
As far as I know the original 1.0.4 version only supports one channel on txt even if you select "All".

You most probably know it, but can do just about everything in Demo Mode without the box connected to your PC!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: quantumvolt on April 16, 2014, 05:40:50 am
Thanks again. I will look at both the original and the open software here. After a search I also found some other links to 'open' stuff and the SDK. Also I read the review in the other eevblog thread. YT also has videos.

I guess I start to make a little program that scrolls the 2 channels w/ timestamp based on abcd_CH1.txt, abcd_CH2.txt, and the time base stored as abcd_TB.txt (must be saved from Notepad or similar). This way I can hook the used time base to the data for future reference.

I guess decent time markers can be calculated from this-observation's-number and total-number-of-observations with quite high accuracy as long as I use channel 1 as a monotonic increasing 'pulse train' ^clock^).

Anyway, no haste. They say 30-45 days with China post ...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on April 16, 2014, 02:48:18 pm
After a search I also found some other links to 'open' stuff and the SDK.

Could you share those?  I wasn't aware of any other Open projects using the SDK for this device. 

Other Hantek's, sure.  Sigrok has done work with several of them.  But the 6022BE is incompatible with all that.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: quantumvolt on April 17, 2014, 08:19:25 am
Sorry, false alarm. I just noted the:

OpenHantek category topic Work in progress on support of hantek 6022be.
http://www.openhantek.org/forum/topic/3/13/ (http://www.openhantek.org/forum/topic/3/13/)

and bookmarked it. But now I see that one of the posters is 'RichardK' and the post links  to here - i.e. to this thread.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on April 17, 2014, 02:42:32 pm
... But the original SW stores both channels parallel in one file?...
Yes, if you export to Excel in the bundled software, what you really get is a text file, with first the channel 1 data, then all the channel 2 data.  I wish it would have exported the data side-by-side, because then I could use Excel's (or OpenOffice Calc's) built-in Chart to display the data.  A warning too - with the original software, I noticed that what was in the export file did not match the screen.  I measured a power supply that properly showed 5.2 volts on the screen, but the export file said 6.3 volts for some reason.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 23, 2014, 03:55:21 pm
Here is the latest version of the user manual for the Open6022be. Just some cosmetic changes done.

Pdf: http://jmp.sh/OgzM1DM (http://jmp.sh/OgzM1DM)

Avoid using the Jumpshare viewer for the docx, as it corrupts some spelling and formatting. Rather download to your PC or use the pdf. I have reported it, but they have not fixed it.
Docx: http://jmp.sh/SaBSG64 (http://jmp.sh/SaBSG64)

I just need to get rid of the parts in red, if anyone can help I will be grateful!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: LETARTARE on April 25, 2014, 05:40:57 pm
@Matchless
Hello,
I'm reading your documentation, and if I find anomalies I warn you.
Thank you again for a great job. :-+ :-+

Sincerely
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 25, 2014, 07:00:37 pm
Thanks LETARTARE, I appreciate  that!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on April 25, 2014, 07:36:48 pm
I am seeing an increased frequency of my system hanging with PR18.  I am not sure if it is my other applications or PR18.

Anyone experiencing the PC hanging win PR18 running?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RobertH on April 27, 2014, 09:13:12 pm
I assumed the problem to originate from USB 3.0 or my hub ... as I have these hangs with Hantek's software too, but on switching back to R17 - these problems were gone. So I can confirm it ... or - if you're working with 3.0 too - that might be a source of this behaviour.

Best regards

Robert
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on April 28, 2014, 12:06:12 am
I assumed the problem to originate from USB 3.0 or my hub ... as I have these hangs with Hantek's software too, but on switching back to R17 - these problems were gone. So I can confirm it ... or - if you're working with 3.0 too - that might be a source of this behaviour.

Best regards

Robert

Thanks for the feedback, Robert!

I am not using USB3.0.  I do have a lone USB1 in the mix that I on rare occasion plug in.  I may try to take that out of the equation and use just USB2 on my next system reload.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on April 29, 2014, 02:43:13 pm
Here is the latest version of the user manual for the Open6022be. Just some cosmetic changes done.

...

This is very minor, as the meaning is unambiguous, and few people actually check system requirements, anyway, but on page 7, I'd suggest

4. PC System Requirements:

Minimum PC System Requirements

Laptop or Desktop PC with USB port
Operating System - Windows XP/Vista/7/8
Processor - 1 GHz
Memory - 128 MB
Disk Space - 500 MB disk free space
Screen resolution - 800 x 600

---
Changed "Gb" on Processor to "GHz", removed "or faster," since this section already says "Minimum" at the top
Memory changed from "128M" to "128 MB"
Similar change to disk space...
Thanks for your work on the manual, Matchless.  The circuit diagrams are invaluable.  It's the kind of thing that wouldn't be included in a manufacturer's manual.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on April 29, 2014, 04:37:42 pm
Hi Roderick,
Thanks for that feedback. I have fixed that for the next version.
I can't tell you how many times I have glanced over the document without noticing those glaring errors!

Thanks again, I appreciate any feedback, as it helps getting the document user friendly and useful.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 01, 2014, 06:06:51 am
Hi everyone!

First I'd like to congratulate the members for the excellent work improving the 6022BE's software and documentation! :-+

I don't own one of these scopes yet. However, after reading this thread and using the open software's Demo mode, I think that one of this devices can probably fulfill my specific needs. I already own several Tek CROs and an Owon SDS7102 DSO, but I have an application where I think a low cost PC based scope would be the best choice.

Basically, I would almost exclusively use the 6022BE in XY mode along with a curve tracer. Currently I'm using a dedicated CRO for this purpose, but is bulky, there is no simple way of storing the images in the PC besides taking a photo, and I could put the desk space to better use. The Owon is a better choice, but it's usually in use for something else when I need to use the curve tracer, so it's a pain to move it back and forth. I tried a sound card based PC scope using free software but it can't be calibrated accurately, so I gave up on that idea.

I uploaded some images to illustrate what I want to do and to illustrate the limited testing I did with the Demo mode in an attempt to evaluate how well the 6022BE may be able to do this job.

The first 3 images were obtained with the Owon, first is a sample of the IV curves I normally get from the curve tracer when analyzing a semiconductor, next are the curve tracer's output signals used to calibrate the scope for XY mode use, and last, the XY mode screen produced by these signals when the scope is properly calibrated.

The next 4 images is what I got with the Demo mode as I attempted to simulate the curve tracer's output signals via its options. First are the options I used, the closest thing to the 6 step waveform was a sawtooth. Next is the resulting YT display, here I notice that the waveforms have a negative component even though the minimum voltage was set to 0V. Don't think this will be a problem in my case, I suspect this is just a peculiarity of the way Demo mode is implemented. Next is the XY display after calibrating the 6022's controls for a proper display. Of course, instead of dots there is just the slanted line because the input waveforms don't have steps. The last image is just illustrating a peculiarity I noticed in the 6022BE XY mode when the time base is changed. You would think that the time base wouldn't have any effect on the XY display, but as can be seen here, changing from 10ms to 2ms affects the display quite significantly.

Anyway, I'll appreciate any feedback or insight anyone of you can offer! :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on May 03, 2014, 05:55:42 pm
Here is latest version of the Open6022be User manual. I have only provided the link to the pdf copy, if anyone wants the docx let me know.

http://jmp.sh/56yQNdr (http://jmp.sh/56yQNdr)

Again any changes, corrections, additions etc are welcome!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: jomor on May 05, 2014, 06:28:03 am
Hello,

can someone explain what the led indications mean?

I have red blinking while not running either Hantek's nor Richard's software. I get green blinking which often turns temporarily red blinking while running any of the software, but I never get constant green. The weirdest is that while having the software in running mode (not paused) I often get red blinks. I use Hantek v1.0.4 and Richard's PR18.

Any ideas?

( I also have many issues with PR18 which I will post later in detail)

Congratulations and many thanks to everyone contributing on this useful project of 6022's software development.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 05, 2014, 01:24:34 pm
Hello,

can someone explain what the led indications mean?

I have red blinking while not running either Hantek's nor Richard's software. I get green blinking which often turns temporarily red blinking while running any of the software, but I never get constant green. The weirdest is that while having the software in running mode (not paused) I often get red blinks. I use Hantek v1.0.4 and Richard's PR18.

Any ideas?

( I also have many issues with PR18 which I will post later in detail)

Congratulations and many thanks to everyone contributing on this useful project of 6022's software development.
Look at Matchless latest Open6022BE manual, it explains the LEDs on page 8.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: jomor on May 05, 2014, 06:20:33 pm
I have already checked the manual, it is not clear to me if the led is always blinking or gets steady also, thats why I asked. In my case it often gets blinking red while having the program running. Thank you for the reply
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on May 05, 2014, 07:50:01 pm
Hi jomor,
             I replied to you earlier, but coming back now my post was not showing. I do not have much on the leds and Hantek does not give away much either. I will update the next version of the manual to make it a bit clearer. Here is the update:

Quote
On the front panel you will see a red/green bi-color led, two BNC connectors and two hook lugs:
1.   The bi-color led always flashes, either red or green.
No Indication:
        If no drivers are installed on PC, the led stays unlit when connected to USB port.
Red flashing: (DSO and PC not communicating)
     a.   If drivers are already installed on the PC and DSO is connected to USB port, but program is not running or
     b.   when the program fails, due to timebase settings out of limit or
     c.   when program shows Red STOP in left top corner.
Green flashing: (DSO & PC is communicating)
    a.   When the DSO is connected and program is running or
    b.   when program shows Green WAIT in top left corner or
    c.   when program shows Green AUTO in top left corner.
2.   The two BNC connectors are for the Channel 1 & 2 probes.
3.   The hook lug marked 1 KHz 2VP-P provides a fixed reference square wave for adjusting probe compensation.
4.   The hook lug marked with the ground symbol is the common ground of the DSO, used to connect the ground clips to when adjusting probe compensation.

Hope this helps a bit.

Edit: Above is an extract from the latest User Manual and the functions of the drivers are mentioned in the Drivers part.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on May 06, 2014, 07:07:20 am
In the past I've done some research on this matter...

Led starts to blink red after successful firmware load into Cypress FX2LP.
Green blinking is indication of receiving data.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on May 06, 2014, 08:12:52 am
Thanks frenky, I have updated the next User manual now and its a bit clearer I hope
Driver 1 loads the firmware and Driver 2 does the communication - I have updated the previous post as to the LED indications only.
Thanks again.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on May 06, 2014, 12:42:16 pm
Thank you, for investing your free time into this user manual. :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: miso156 on May 07, 2014, 06:46:10 am
Hi,

please can someone upload PR18 binary to some another file-server? The link provided does not work for me.

Thanks
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: jomor on May 07, 2014, 07:45:56 am
I tried the device to my laptop ( I was trying it to my desktop pc until now) and I did not get red blinking while the program was running, which means there is a problem with my desktop's usb connection, I only used the front panel's usb ports though. Thanks for the clarifications.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on May 09, 2014, 06:06:34 am
Hi,

please can someone upload PR18 binary to some another file-server? The link provided does not work for me.

Thanks

I put it here, but don't expect it to be a fast download.  Also, no guarantee that I'll keep any past or future binary at this location.  ftp://pididu.com/OpenHantek/
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 09, 2014, 11:15:58 pm
Just received my 6022BE. I'm using Win7 and the installation seems to be a little different than what is described.

First, before I could load the CD windows found the drivers and installed them, I presume off the internet. Just to be sure I clicked update driver from Dev Mgr and directed it to the appropriate folder. However, the new driver seems to be the same as the one originally installed automatically by windows, I think this is the case because it didn't offer me the option to revert to the old driver.

Second, Dev Mgr only shows Driver 2, checking the option to view hidden devices doesn't make any difference as far as this driver is concerned. I know, however, that Driver 1 is installed because I can see it via Sys Info.

Other than the above, everything seems to be working as expected. I haven't tried the XY mode with my curve tracer yet, I'll post about that later. The attached images illustrate what I saw with Dev Mgr and Sys Info. Also, it shows what I get after adjusting the probes while scoping the Cal signal.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: York on May 10, 2014, 05:49:34 am
I bought lots of Hantek products?Especially their USB products. Recently ON China's largest e-commerce sites TaoBao product Hantek6022BL is very hot,
http://item.taobao.com/item.htm?_u=mb4mc243bc3&id=38085913724 (http://item.taobao.com/item.htm?_u=mb4mc243bc3&id=38085913724)
I know Hantek6022BE,But never hear of Hantek6022BL.
 
Through the introduction , It contains Hantek6022BE’s all functions?Addition with 16CH logic analyzer functions, Compatible with Saleae logic analyzer.So Hantek6022BL=Hantek6022BE+16CH logic analyzer + Saleae. A more cost-effective products than Hantek6022BE. An SDK is provided by Hantek.
Saleae Download address?
https://www.saleae.com/downloads (https://www.saleae.com/downloads)

Near the Hantek6022BL’s USB port has a button, press the button support Hantek’s software, and Bounce off the button support Saleae logic analysis software
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on May 11, 2014, 03:39:19 pm
I don't remember if this was mentioned before but it looks like the OpenHantek can't take measurements properly.
I'm using the scope for audio amplifiers mainly so I need to observe the onset of clipping and the corresponding signal amlpitude.
As seen from the pics below The Hantek software produces 19.9V RMS/59VPtP. The OpenHantek PtP reading is close but the RMS is something strange. In the same time my DMM reads 18.9V  ??? It's an 80Hz sine wave.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on May 11, 2014, 04:12:00 pm
I don't remember if this was mentioned before but it looks like the OpenHantek can't take measurements properly.
I'm using the scope for audio amplifiers mainly so I need to observe the onset of clipping and the corresponding signal amlpitude.
As seen from the pics below The Hantek software produces 19.9V RMS/59VPtP. The OpenHantek PtP reading is close but the RMS is something strange. In the same time my DMM reads 18.9V  ??? It's an 80Hz sine wave.

Yeah, on multiple occasions and they turned out to be user error (such as setting V/div too low and thus clipping occurred)

Your wave looks more like rounded triangle than sine to me, so how it is calculated, the sample rate, etc will all affect the "real value". 

When it comes to AC voltage, accuracy of DMM or the Hantek is not that good.  Do you know for sure your DMM is true RMS?  Your quoted numbers (19.9/18.9) looks to me like an RMS/TRMS issue and within expected value ranges.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Merlyn on May 11, 2014, 04:55:10 pm
You can see my settings from the pics. The probe is set to x10. There's no clipping. Obviously it's not a triangle wave either.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on May 11, 2014, 10:08:30 pm
You can see my settings from the pics. The probe is set to x10. There's no clipping. Obviously it's not a triangle wave either.

I know it is not a triangle wave.  But it appears to me it has very linear rise and fall.  So linear that it looks more like a rounded-angle triangle wave.

With it looking so different than an ideal sine wave, the algorithm to calculate sine wave RMS will not work well.  Slightly differences in the algorithm may yield very different results.  When you are measuring it with two different devices, the two devices may be making different assumptions and used different algorithms.

Why not do a data capture with the Hantek, export the data to excel, and do a real RMS calculation.  We don't know your wave, but we do know the specs for the hantek.  With the specs you can eval the exact error range also.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: quantumvolt on May 11, 2014, 11:32:17 pm
@ Merlyn, Rick

With a P-P voltage of some 58 volt (or somewhere there) and a 'triangular tendency sine-like' shape, it is OK to use a crest-factor 1.5 (appr. SQRT(2)). This gives an RMS voltage around 58/(2x1.5)= 19.3 volt.

Acordingly - the DMM and the Hantek SW shows sound results. The quoted OpenHantek value of some 6 volt is a SW bug (maybe division by some 3-like number 2 times  ::)  :-//  :scared: (6.5x3x3=58.5)).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on May 12, 2014, 05:15:36 am
@ Merlyn, Rick

With a P-P voltage of some 58 volt (or somewhere there) and a 'triangular tendency sine-like' shape, it is OK to use a crest-factor 1.5 (appr. SQRT(2)). This gives an RMS voltage around 58/(2x1.5)= 19.3 volt.

Acordingly - the DMM and the Hantek SW shows sound results. The quoted OpenHantek value of some 6 volt is a SW bug (maybe division by some 3-like number 2 times  ::)  :-//  :scared: (6.5x3x3=58.5)).

Good to know.  I would have wasted time really calculated the root mean square a data point at a time if I exported the data - of course, that would still be an estimate since the data points are discrete whereas the voltage change is continuous.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 13, 2014, 05:00:23 am
I just got done setting up my 6022BE for use with my curve tracer. The definition of the XY images is not as good as I hoped. I think part of the reason is noise interference and most of the reason is the DPI used to draw the images. I was able to improve the noise situation by using ferrites on the cables interfacing the curve tracer to the scope and constructing the adjustable voltage dividers used to calibrate the curve tracer's output on a very small PC board. I don't know if it's possible to alter the DPI used to draw the images by recoding something in the software, maybe RichardK can answer that!

The attached images illustrate the results I got. The first two images show the calibration screen, one of them is from my Owon SDS7102 to illustrate the difference in definition and DPI. The next image shows the IV curve for an UF4007 rectifier I obtained with the 6022BE. Here the Curve tracer is set to 0.1V/Div Horizontal and 20mA/Div Vertical. The curve shows that the Fwd Voltage reaches 1V at about 120mA. The last two images show a sample set of IV curves for an NPN transistor. here again one of the images is from my Owon SDS7102 to illustrate the difference in definition and DPI.

In the end, although I think the 6022BE is usable for this purpose, the quality of the images it produces is well below what I can get with other equipment I already own. So I no longer plan to replace the dedicated CRO I've been using for this purpose with it. On the other hand, I plan to use the 6022BE as a quick way of capturing an image if the Owon is not available.

Next I plan to explore other capabilities and limitations of the 6022BE in more detail. So, in the hope that it may be helpful for the software and documentation development effort, I'll be posting my findings as I go along.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 16, 2014, 03:25:16 am
Today I was trying to determine the 6022BE's limits associated with low level high frequency signals. With a maximum sampling rate of 48MS/s (1 sample every 20ns), I didn't expect faithful reproduction of 20MHz signals (2.5 samples per cycle). Hoped for mediocre reproduction of 10MHz signals (5 samples per cycle), and fairly good reproduction of 5MHz signals (10 samples per cycle). The scope performed reasonably close to these expectations depending on the setting of the time base.

One unexpected peculiarity is that at settings faster than 2us/div the scope adds additional data points next to the real time samples. It seems that this mechanism is designed to enhance the display of high frequency logic signals (rectangular signals). Unfortunately, it also has the effect of distorting, for example, sine waves, and making them appear as step waves. I tried to illustrate this behavior with the attachments.

The attached images were obtained using an RF signal generator set to 10MHz 33mVpp with a sine wave output signal. To get a viable display I had to set the probe to X1 and the scope to 20mV/Div. Since the probe's bandwidth at X1 is 6MHz, the signals displayed are considerably less than 33mVpp:

 #1 through #1c - Here I captured the 10MHz signal with the time base set to 2us/div and with the scope stopped I changed the time base to 50ns/div. Since the measured values on all of these images are mostly way off, I used the cursors to show the frequency and amplitude. The reason I used the stock software for these images is that the PR18 cursors don't yield the correct frequency (see #1b). Note that on #1c the expected number of samples (about 5 per cycle) are present.

 #2 through #2b - Here I captured the 10MHz signal with the time base set to 1us/div and with the scope stopped I changed the time base to 50ns/div. Note on #2a that the sine wave is starting to look like a step wave. Also note on #2b the extra data points, the total appears to be about 10 per cycle.

 #3 - Here I captured the 10MHz signal with the time base set to 500ns/div and with the scope stopped I changed the time base to 50ns/div. Note that even more data points are present now.

 #4 through #4a - Here I captured the 10MHz signal with the time base set to 200ns/div and with the scope stopped I changed the time base to 50ns/div. Note that even more data points are present now. Also note on #4a the appearance of the signal, now definitely looks like a step wave.

So it seems to me that for the most faithful reproduction when viewing signals other than rectangular waves, it would be better to capture the signal with the time base set to 2us/div or slower.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on May 16, 2014, 05:44:24 am
Hello TomC
The input level is too low.
2 LSB max !  The scope will only display 5 values : 0, 4mV, 8mV, -4mV -8mV.
If you reduce the input to 1LSB ( roughly 4mV), you will get pure square wave...
See the diagram on page 16 of the OpenHantek UM.

You could get an optimum display using a 500mV input (1V pp).
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 16, 2014, 01:30:52 pm
Hello TomC
The input level is too low.
2 LSB max !  The scope will only display 5 values : 0, 4mV, 8mV, -4mV -8mV.
If you reduce the input to 1LSB ( roughly 4mV), you will get pure square wave...
See the diagram on page 16 of the OpenHantek UM.

You could get an optimum display using a 500mV input (1V pp).
Thanks a lot for your response,

My RF generator doesn't produce larger signals, however, using my audio generator, which can produce about 4Vpp, I saw pretty much the same effect at around 100KHz. Next I'm going to try my function generator which goes up to 2MHz with both sine and square waves. I hope that shows whether the effect still holds true for larger signals! :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 17, 2014, 04:44:08 am
This is a follow up to post #603. As pointed out by lapeyroua, the input level at the BNC has an influence on the effect of the additional data points generated when the time base is set to faster than 2us. Unfortunately, I don't have an RF generator capable of 1Vpp at 10MHz, so I can't make a direct comparison to the images on post #603. Instead I'm using a function generator at its maximum frequency of about 2.2MHz. For the attached images the output is set to 1Vpp and the function to sine wave.

To get 1Vpp at the BNC the probe is set to X1 on the images so identified by the filename. For reference, the probe is set to X10 on the last few images (as indicated by the filename), note that in this case the input level at the BNC is only 100mVpp.

 #1 through #1b - were obtained with my Owon SDS7102 just to show how the signal appears, first captured at 1GS/s and subsequently at 50MS/s which is close to the 6022BE's max of 48MS/s.

 #2 through #5a - were obtained with the probe set to X10 (1Vpp at the BNC) and were captured at various time base settings as indicated by the filenames. With the scope stopped the time base was then changed to 50ns/div. Although I still see some distortion in waveforms captured at faster than 2us/div, the effect is nowhere nearly as bad as with the low level signals on post #603.

Note that I did try input levels at the BNC of up to 11Vpp, at which point there is clipping by the protection circuit in the scope's front end. However, at a level just below 10Vpp, where there is no clipping, the distortion caused by the additional data points is hardly noticeable at 50ns/div.

 #6 through #7a - were obtained with the probe set to X10 (100mVpp at the BNC) to show the difference in the level of distortion with a low level signal. The first two images were captured at 2us/div and with the scope stopped the time base was then changed to 50ns/div to show how the signal looks without the additional data points. The last two images were captured at 50ns/div and as can be seen the distortion caused by the additional data points results in a very noticeable step wave.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on May 17, 2014, 06:08:37 am
To TOMC #606
Could you use the RichardK's OpenHantek software ? I'm really more confident in his version than the Hantek's one.

Looking at picture #7a, I would say : not too bad for this low price hardware. (taking into account the noise and distorsion) :
As each dot is visualised as a line, the picture is confusing. But if you consider the start of each small horizontal line as the real dot, the curve is better and you will no more see additional data points.

A good way to determine weither distorsion comes from harware or software would be to visualize the signal close to the AD9288, with the Owon...



Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: jomor on May 17, 2014, 01:51:21 pm
OpenHantek does not work on my laptop (Toshiba U300,windows 7), it is very very slow and it crashes with access violation messages when i try to select what to show on the measuring window.

Hantek's software works well, except for the noise and inaccurate readings issue: I measure the output of a 5V voltage regulator (which I verify at 4.99V with a high accuracy voltmeter) and it shows 5.17Volts. One or two times I managed to get the exact reading of 4.99Volts with hantek's software and that time the line was completely clear straight line at 4.99Volts with no noise at all!!!! Then I touch the probe on another point of the circuit where it has 9V ac and I hit the Auto button and the noise comes back on the 9v sinewave, I put the probe back to the 5v dc point and it shows again 5.17Volts with noise.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 17, 2014, 04:17:21 pm
To TOMC #606
Could you use the RichardK's OpenHantek software ? I'm really more confident in his version than the Hantek's one.

Looking at picture #7a, I would say : not too bad for this low price hardware. (taking into account the noise and distorsion) :
As each dot is visualised as a line, the picture is confusing. But if you consider the start of each small horizontal line as the real dot, the curve is better and you will no more see additional data points.

A good way to determine weither distorsion comes from harware or software would be to visualize the signal close to the AD9288, with the Owon...
Hi lapeyroua,

I agree that the 6022BE is a pretty good deal considering the price! :)

I did use both software versions for many of the tests and the images were the same. For this particular series of tests the stock software was more convenient because the options I was using most often were just a click away. Also, the stock software cursor function for frequency is more accurate on X1 than PR18 and the measure functions seem to be a little more accurate at times. Later today I'll try to repeat #6 through #7a with the open software and post them.

I suspect that the mechanism for adding extra data points is in the firmware. I also suspect that it is there due to the fact that this scope seems to be basically the same as the 6022BL except for the missing components in the circuit board. So it would stand to reason that it would be designed to enhance the display of logic signals.

I haven't taken apart my unit yet, but let me know specifically what you have in mind as far as scoping inside of it with the Owon and I'll see what I can do in the next few days!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 18, 2014, 04:09:59 am
The attachments to this post are a repeat of the images #6 through #7a on post #606. However, these new images were rendered using the Open Software PR18. The test equipment was setup just as described on post #606. While comparing these images to the ones rendered with the stock software, it seems to me that these new images exhibit slightly more distortion.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 18, 2014, 05:40:31 am
Today I was exploring in more detail what happens at maximum and minimum input signals.

First I wanted to see what happens when you drive the input with a signal greater than 10Vpp. For this test I set the function generator to 2.2MHz at 11.5Vpp and sine function. The results can be seen on attachments #1 and #1a. Notice that the signal is clipped to around 10.3Vpp.

Next I wanted to see how the signal appeared at a level just below clipping. For this test I lowered the generator's output to 9.8Vpp. The results can be seen on attachments #1b and #1c. Notice that on this high level signal, although it was captured at 50ns/div, the distortion caused by the extra data points is barely perceptible.

The rest of the tests illustrate what happens with either a 50 ohm terminator or nothing connected to the BNC. On this scope the Base Line Noise seems to be the same in either case. To check if the BLN displayed by the 6022BE was actually present at the BNC, I connected the Owon to it. In every case the signal displayed by the Owon didn't resemble what the 6022BE was displaying and the amplitude of the noise displayed was way less than what was displayed by the 6022BE.

I performed this test on all the time base settings, but I'm only posting images of the area where I found some unexpected peculiarities.

 #2 through #2b - This was captured at 5us/div, then with the scope stopped the time base was changed to 200ns/div to show the image in more detail. The third image is what the Owon was seeing at the BNC while I was performing the capture. Note that the BLN has both positive and negative pulses. Although not shown in this capture, once in a while there is a double positive pulse. Also note that the expanded images look trapezoidal. These characteristics are similar at lower time base settings. However, the frequency of the signal seems to be lower as the sample rate decreases.

 #3 through #3b - This was captured at 2us/div, then with the scope stopped the time base was changed to 200ns/div to show the image in more detail. The third image is what the Owon was seeing at the BNC while I was performing the capture. Note that the BLN has only positive pulses, this is the only time base setting where I observed this peculiarity. Also note the double positive pulse, as in the previous case this happens infrequently, but for this capture I set the trigger higher to make sure I caught it. Also note that in the expanded image some of the pulses have a flat top.

 #4 through #4b - This was captured at 1us/div, then with the scope stopped the time base was changed to 100ns/div to show the image in more detail. The third image is what the Owon was seeing at the BNC while I was performing the capture. The positive part of this image is similar to the previous example, but here again we also have negative pulses as in the time base settings below 2us/div. Also note that the frequency of the signal is higher although the sample rate is the same as for the 2us/div time base setting. I suspect that this may have something to do with the fact that at 1us/div additional data points are generated. These characteristics are similar at higher time base settings. However, the frequency of the signal continues to increase at higher time base settings apparently in proportion with the increase in extra data points generated.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on May 18, 2014, 10:01:31 am
Is Richardk still around? Hope he is just busy!

Anyone have the Hantek 6022BL software yet?

TomC, do you mind if I use one of your pictures in the user manual to show the clipping at > 10V p-p?

I will post the next version of the user manual this within the next few days.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 18, 2014, 03:10:59 pm
Is Richardk still around? Hope he is just busy!

Anyone have the Hantek 6022BL software yet?

TomC, do you mind if I use one of your pictures in the user manual to show the clipping at > 10V p-p?

I will post the next version of the user manual this within the next few days.
Not at all! :)
Use whatever you need, and let me know if there is something else I can do to help!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on May 18, 2014, 03:51:55 pm
Quote
Not at all! :)
Use whatever you need, and let me know if there is something else I can do to help!

Thanks TomC. Have used a photo of the voltage clipping. If you have the time, any help with the manual will be appreciated.

Here is the latest version of the user manual.
Pdf: http://jmp.sh/Zd3ymXt (http://jmp.sh/Zd3ymXt)
Docx: http://jmp.sh/Ywoj7r4 (http://jmp.sh/Ywoj7r4)

Again any corrections, additions, changes etc. are welcome. Some stuff in red is still pending as well.

Edit: The Jumpshare  docx viewer has been fixed!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 19, 2014, 03:52:51 am
Thanks TomC. Have used a photo of the voltage clipping. If you have the time, any help with the manual will be appreciated.

Here is the latest version of the user manual.
Pdf: http://jmp.sh/Zd3ymXt (http://jmp.sh/Zd3ymXt)
Docx: http://jmp.sh/Ywoj7r4 (http://jmp.sh/Ywoj7r4)

Again any corrections, additions, changes etc. are welcome. Some stuff in red is still pending as well.

Edit: The Jumpshare  docx viewer has been fixed!
Hi Matchless,
Here are a couple of suggested corrections for the first paragraph on page 6 and some comments on the text next to the first bullet on the same page. I didn't suggest a correction for this last part, just offering my opinion on this issue, see if you can use any of it to improve the text. :)

Page 6 – first paragraph:
Some contents are extracts are from the original Hantek manual as well as inputs from forum members on the www.eeblog.com (http://www.eeblog.com) website and other general Internet sources.

Page 6 – first bullet:
I'm having trouble with the terminology “common ground to the mains power”. As I understand it, there shouldn't be any problem connecting the ground lead to equipment that uses a protective earth ground, that's usually equipment that uses a three prong AC plug, for example, my Function Generator. Also, as I understand it, there shouldn't be any problem with equipment that uses a true floating return, also known as floating ground. This type of equipment may use a two or three prong AC plug and also feature some internal means, such as a transformer, to isolate the mains from the return. On the other hand, as I understand it, equipment that uses a live return, also known as a live ground, will cause current to flow through the ground lead if it is connected to it and something will burn to stop the flow. This type of equipment typically uses a two prong AC plug and derives the return from the mains neutral lead, for example, older TV sets (1990's).

When in doubt, I believe it should be possible to determine if it's safe to connect the ground lead to the return as follows. Connect a 10k resistor between the equipment's return and protective earth ground (ground lug of a three prong receptacle). If current flows through the resistor indicating a live return you should be able to read a voltage across it with your VOM or DMM.

Page 6 – asterisk note below the first bullet:
There may be a danger associated with connecting a scope isolated from protective earth ground to another piece of equipment. If for example, the ground lead is connected to a live return or chassis, this potential will be present on any exposed metallic parts of the scope presenting a shock danger for the operator. Even if the operator is very careful, unless there is absolutely no connection to the mains (battery operated), a high enough potential on the scope's ground can lead to stress and or failure of internal components not designed for this purpose.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on May 24, 2014, 04:17:42 am
Today, since I couldn't find it in the specs,  I wanted to get some idea of the risetime of the 6022BE. To perform the tests I used my scope calibrator which has a risetime of <4ns. The fast risetime output has an amplitude of about 250mV and the frequency was set to 1MHz. For reference, the risetime of my Owon SDS7102, a 100MHz DSO, is rated at <3.5ns. In contrast, the risetime of my 15MHz Tektronix CRO is rated at <23ns.

 #1 through #1b - The first image is from the Owon captured at 200ns/div. Next is a Hantek 6022BE image captured at 2us/div and with the scope stopped changed to 200ns/div. Finally we have a Hantek 6022BE image captured at 200ns/div. It seems that as far as the risetime is concerned, the image captured at 200ns/div shows a faster risetime. So it seems that the additional data points help portray fast risetime pulses a little better.

 #2 through #2b - This series shows the rise of the pulse at a faster sweep setting. The first image is from the Owon captured at 2ns/div. Next is a Hantek 6022BE image captured at 2us/div and with the scope stopped changed to 20ns/div. Finally we have a Hantek 6022BE image captured at 20ns/div. It didn't make sense to use a 2ns/div for the Hantek because the scope's risetime is to slow to show the full excursion on one screen. Here again, as far as the risetime is concerned, the image captured at 20ns/div shows a faster risetime, about 20ns shorter. Again, I think that the additional data points help portray fast risetime pulses a little better.

 #2 through #3b - This series is similar to the previous one but shows the fall of the pulse instead of the rise.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on May 25, 2014, 04:10:01 pm
Quote
Hi Matchless,
Here are a couple of suggested corrections for the first paragraph on page 6 and some comments on the text next to the first bullet on the same page. I didn't suggest a correction for this last part, just offering my opinion on this issue, see if you can use any of it to improve the text. :)


Hi TomC,
             Thanks for the input. Your suggestions were excellent. I have now revised that part and hope it is more meaningful. I am not an expert and this is way beyond my comfort zone so all input is appreciated!
Thanks again!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Prana on May 26, 2014, 10:34:02 pm
Hi Matchless,
Have you any news from Richardk ?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on May 27, 2014, 06:53:34 am
Hi Matchless,
Have you any news from Richardk ?

Hi Prana,
His last post here was on 4 April 2014.....
He was doing exceptional work on the program up until the beta18 version!
Hopefully he is still around and OK, but just busy with other things.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on June 05, 2014, 03:24:34 pm
I'm alive, just had zero time to do anything on the program... I'm keeping an eye in here and writing down new bugs/feature ideas etc...

When I have ample time again I'll resume work on it, sorry guys but real work takes president over hobbies :)

Btw thanks to everyone helping test and ideas and Matchless for the documentation :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on June 05, 2014, 11:39:03 pm
I'm alive, just had zero time to do anything on the program... I'm keeping an eye in here and writing down new bugs/feature ideas etc...

When I have ample time again I'll resume work on it, sorry guys but real work takes president over hobbies :)

Btw thanks to everyone helping test and ideas and Matchless for the documentation :)

Thank goodness!  https://www.eevblog.com/forum/Smileys/default/clap.gif (https://www.eevblog.com/forum/Smileys/default/clap.gif) At my age, if someone is out of touch, it's a reasonable possibility to consider that they might be gravely ill or have passed away.  Glad you're fine, and absolutely, real work must come first.  Not to be morbid about it, but it may be worth considering putting your source in escrow with a trusted friend or relative, in case the worst happens.  At least until you can get some version up on a place like SourceForge.  Yes, your program is that valuable.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on June 06, 2014, 07:19:35 am
Ditto on what roderick said! Glad to hear you are still around!  I have noticed that you have quite a following on this thread, due to what you are doing!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mustafakerb on June 20, 2014, 11:07:46 pm
I've read whole topic but didn't find answer for simple question: It is possible to add AC-coupling somewhere inside case? probably with switch on front like on proper scope?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: vbs on July 01, 2014, 11:26:30 am
Sorry for chiming in but would RichardK's software also work with the Hantek 6022BL?
Thank you.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on July 05, 2014, 10:02:44 am
Sorry for chiming in but would RichardK's software also work with the Hantek 6022BL?
Thank you.

I think not as it is at the moment. I do not have a 6022BL to test on, but I downloaded the 6022BL software and installed on my laptop and connected the 6022BE DSO. It opens a window with 2 icons. One for the scope and the other for the function generator.  Clicking the scope icon opens up Version 1.0.4, but it does not find the device. I think there may be differences in the firmware and in the software. RichardK is the guru and could comment on this, but I think that Open6022BE may need to be adapted to do this.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: SoloTek on July 07, 2014, 05:24:43 pm
Hello everybody, I stumbled over this discussion, also because I was looking for the difference between BE and BL. I just ordered the BE, since I got the impression that a BL is actually 2 devices in one, a BE Scope and a Saleae clone Logic16. The bad part: they are not usable together at the same time! You have to decide, analog XOR digital,  no mixed mode.   :--

Regards.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: tkrmona on July 16, 2014, 06:14:36 pm
Sorry for chiming in but would RichardK's software also work with the Hantek 6022BL?
Thank you.

Sadly I'm an 6022BL owner and it´s not working with the current Open6022BE version. I hope there's an easy way to adapt the software. RichardK's if you can add support to the 6022BL version, I will apreciate that a lot!!!  :-+ :-+ :-+ :-+
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on July 16, 2014, 06:27:42 pm
Sorry for chiming in but would RichardK's software also work with the Hantek 6022BL?
Thank you.

Sadly I'm an 6022BL owner and it´s not working with the current Open6022BE version. I hope there's an easy way to adapt the software. RichardK's if you can add support to the 6022BL version, I will apreciate that a lot!!!  :-+ :-+ :-+ :-+

The 6022BL has the same SDK as the 6022BE, so any incompatibility might be as trivial as a file name or hardware ID... And it seems the 6022BL is the 6022BE with the Logic Analyzer components populated...

Edit:

Did some preliminary decompiling on the 6022BL's HTMarch.dll and it has a different hardware ID "d602a-%d" as opposed to the 6022BE's "d6022-%d" and the library functions appear to be the same...

It might work with Open6022BE if you use the 6022BL's HTMarch.dll instead of the 6022BE's HTMarch.dll... So simply delete the HTMarch.dll file included with Open6022BE and replace it with the HTMarch.dll that comes with the 6022BL Software.

The 6022BL's HTMarch.dll has a new function called:

Code: [Select]
dsoChooseDevice(unsigned short DeviceIndex, short nType);
And this is used to specify which device to use (they cannot be used at the same time I suppose)...

The parameter nType is 0 for 6022BL's Logic Analyzer and 1 for 6022BE Scope... If this is required to get the 6022BE functioning I might have to make a call to this function to get the 6022BL to work with Open6022BE.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: tkrmona on July 16, 2014, 07:12:45 pm
Sorry for chiming in but would RichardK's software also work with the Hantek 6022BL?
Thank you.

Sadly I'm an 6022BL owner and it´s not working with the current Open6022BE version. I hope there's an easy way to adapt the software. RichardK's if you can add support to the 6022BL version, I will apreciate that a lot!!!  :-+ :-+ :-+ :-+


The 6022BL has the same SDK as the 6022BE, so any incompatibility might be as trivial as a file name or hardware ID... And it seems the 6022BL is the 6022BE with the Logic Analyzer components populated...

Edit:

Did some preliminary decompiling on the 6022BL's HTMarch.dll and it has a different hardware ID "d602a-%d" as opposed to the 6022BE's "d6022-%d" and the library functions appear to be the same...

It might work with Open6022BE if you use the 6022BL's HTMarch.dll instead of the 6022BE's HTMarch.dll... So simply delete the HTMarch.dll file included with Open6022BE and replace it with the HTMarch.dll that comes with the 6022BL Software.

The 6022BL's HTMarch.dll has a new function called:

Code: [Select]
dsoChooseDevice(unsigned short DeviceIndex, short nType);
And this is used to specify which device to use (they cannot be used at the same time I suppose)...

The parameter nType is 0 for 6022BL's Logic Analyzer and 1 for 6022BE Scope... If this is required to get the 6022BE functioning I might have to make a call to this function to get the 6022BL to work with Open6022BE.

Yeah!! It works!!!! I only change the HTMArch.dll It's looks like everything is working fine. If i found a new bug, I will let you know. Thank You for the quick reply!!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RichardK on July 16, 2014, 07:15:40 pm
Sorry for chiming in but would RichardK's software also work with the Hantek 6022BL?
Thank you.

Sadly I'm an 6022BL owner and it´s not working with the current Open6022BE version. I hope there's an easy way to adapt the software. RichardK's if you can add support to the 6022BL version, I will apreciate that a lot!!!  :-+ :-+ :-+ :-+


The 6022BL has the same SDK as the 6022BE, so any incompatibility might be as trivial as a file name or hardware ID... And it seems the 6022BL is the 6022BE with the Logic Analyzer components populated...

Edit:

Did some preliminary decompiling on the 6022BL's HTMarch.dll and it has a different hardware ID "d602a-%d" as opposed to the 6022BE's "d6022-%d" and the library functions appear to be the same...

It might work with Open6022BE if you use the 6022BL's HTMarch.dll instead of the 6022BE's HTMarch.dll... So simply delete the HTMarch.dll file included with Open6022BE and replace it with the HTMarch.dll that comes with the 6022BL Software.

The 6022BL's HTMarch.dll has a new function called:

Code: [Select]
dsoChooseDevice(unsigned short DeviceIndex, short nType);
And this is used to specify which device to use (they cannot be used at the same time I suppose)...

The parameter nType is 0 for 6022BL's Logic Analyzer and 1 for 6022BE Scope... If this is required to get the 6022BE functioning I might have to make a call to this function to get the 6022BL to work with Open6022BE.

Yeah!! It works!!!! I only change the HTMArch.dll It's looks like everything is working fine. If i found a new bug, I will let you know. Thank You for the quick reply!!

I'm working on a quick solution that should make it easier to work with both.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on July 16, 2014, 10:14:27 pm
Mr. RichardK,

Your contribution to the 6022BE (L) community here is immeasurable.  Anywhere you go, chances are, there is a 6022 user within 100 miles who would buy you a beer.

(Thanks!)
Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: frenky on July 17, 2014, 08:49:01 am
What do you guys think about taking this scope to another level?
https://www.eevblog.com/forum/oshw/opensource-oscilloscope-with-tabletphone-display-based-on-hantek-6022be/ (https://www.eevblog.com/forum/oshw/opensource-oscilloscope-with-tabletphone-display-based-on-hantek-6022be/)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Keptenkurk on August 12, 2014, 05:31:26 pm
Received my Hantek 6022BE with two probes included from banggood.com (http://banggood.com) today (currently at USD 68,99 shipping included, delivered within 2 weeks to the Netherlands).
Didn't even bother to install the supplied SW from Hantek (except for the driver) and went straight for the Open6022 version of RichardK on Win7. No HW modifications done yet.
Works like a charm and i'm sure this will be a valuable tool.

Thanks Richard!!  :-+ Keep up the good work!!

EDIT: ...and Rick Law is right about the beer!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: whitrzac on August 12, 2014, 08:54:25 pm
Mine just got here from fleebay. I tried the included software and it locked 5 times in 10 min  :rant:

Another big thanks for open6022be.


Would it be possible to add a THD measurement(for amplifiers/etc)?

I 2nd the Watt/RMS reading. It's easy enough to calculate, but having it done automatically would be awesome
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: whitrzac on August 17, 2014, 05:04:07 am
Is there a way to set the FFT range?

I want 0hz to ~30khz range. As of right now its all in the 1st division, anything less than 5k is impossible to read.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rosasharn on August 19, 2014, 07:25:01 am
The software is very simple.
It seems no function to do setting on FFT range. :-//
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rick Law on August 19, 2014, 05:14:59 pm
Mine just got here from fleebay. I tried the included software and it locked 5 times in 10 min  :rant:

Another big thanks for open6022be.


Would it be possible to add a THD measurement(for amplifiers/etc)?

I 2nd the Watt/RMS reading. It's easy enough to calculate, but having it done automatically would be awesome

I think your setup may have a problem.  The included software is not great, but I use it often (since it is Remote Desktop friendly).  It hangs, but rarely.  If it hangs on you so often, check you USB voltage, hubs, and whatever else.  You must have a hidden issue somewhere.

Rick
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 21, 2014, 07:14:29 am
The file Open6022BE_1_0_BetaPR18_Binary.zip keeps saying its a malicious file in Google Chrome and blocks it. The file Open6022BE_1_0_BetaPR17_Binary.zip downloads just fine however. Is there something wrong with the PR18 file that I should be concerned about?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: olrowdy01 on August 21, 2014, 02:14:05 pm
Quote from: AznGothic on Today at 05:14:29 PM (https://www.eevblog.com/forum/index.php?topic=17278.msg499475#msg499475)
The file Open6022BE_1_0_BetaPR18_Binary.zip keeps saying its a malicious file in Google Chrome and blocks it. The file Open6022BE_1_0_BetaPR17_Binary.zip downloads just fine however. Is there something wrong with the PR18 file that I should be concerned about?

PR18 downloaded, unzipped, installed and runs fine in demo mode on my Windows 7, 32 bit machine.  I'm using Firefox V27 and Comodo ISP V7.03xxxx.  Probably Chrome or your virus protection is set a little too sensitive.  Try scanning the zip file with another program for viruses.

I just test downloaded PR18 from
ftp://pididu.com/OpenHantek/ (http://ftp://pididu.com/OpenHantek/) then scanned it with Comodo and it's clean.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rosasharn on August 22, 2014, 01:29:18 am
I couldn’t agree more with olrowdy01’s statement.

Many browsers clashed with PR18.
While, actually it's clean and seems no harm to my computer.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 23, 2014, 12:15:01 pm
Awesome. Thank you for checking into that for me. I was a bit nervous when I saw a big red box pop up saying MALICIOUS! in google chrome. I just downloaded the previous release instead and have been playing around with that but I'll grab the newer one now.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: whitrzac on August 24, 2014, 02:25:29 pm
I had a bad usb cable...

The Vrms measure doesn't seem to be working properly.

I have a 400hz, 85v pk-pk, signal, 100x probe
my Vrms measure is 700kv :-//
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 24, 2014, 10:02:10 pm
Ok, so I downloaded the newer PR18 binary at the link RichardK posted http://jmp.sh/k0tTgXg (http://jmp.sh/k0tTgXg). After doing this, my 6022BE became unresponsive. The light is a blinking red light that will turn green for a split second and back to a blinking red light. I tried the PR17 software and stock software again to get the same results. The download link above is the link that google chrome also tells me is a malicious download. I tried the FTP link olrowdy01 posted but the link kept returning "server not found." So I took the 6022BE over to my girl friends computer and installed the stock software to find everything worked fine. I went back to my computer, opened up device manager, selected the 6022BE Driver 2 and clicked uninstall. When I disconnect the USB cable and reconnect it, Windows automatically reinstalls the driver which in turn still has the same issue. So how do I uninstall and reinstall this properly so that I can get it working again? Also I'm wondering if the files at the FTP link are different from the files at the HTTP link and could have caused this?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Dave_S on August 25, 2014, 04:50:56 am
I do not know how much help this will be, but I just ran a diff on the file at at your link and the file that I am using with no apparent problems and the result was no difference.  Could a glitch have caused some kind of defect in the copy that you have?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: SteveB on August 25, 2014, 11:30:51 pm
my first post  ;)

With the 6022BE unplugged, go to device manager and uninstall the drivers. Then reinstall from the CD-ROM (or download from Hantek). Then plug in the scope.

Steve.

Please post if it works for you.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 26, 2014, 12:01:48 am
With the 6022be unplugged, the device doesn't show up in device manager. Is there a trick to showing unplugged devices?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: SteveB on August 26, 2014, 05:15:52 am
Good point ! Of course it won't be there . Uninstall with the device plugged in and then unplug it for the reinstall. My main point was supposed to be that the device shouldn't be plugged *back in* before the drivers were manually reinstalled.

I wasn't that clear in my reply.

Steve.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on August 26, 2014, 05:44:14 am
I noticed back there that someone was having trouble, and running Windows 7.  Not to insult anyone's intelligence, but I noticed there were no Windows 7 drivers on the CD included with my scope.  Those had to be downloaded from the Hantek site.  I'm not exactly sure what Windows 7 will do trying to run the XP driver in compatibility mode.  Perhaps later shipments have remedied that, and the Win7 driver is on the CD...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 26, 2014, 12:17:16 pm
I didn't use the disc supplied with the 6022be. Regardless of anything I buy or what computer I'm using I always download drivers to ensure I have the latest driver version. In this cause though, I downloaded the driver because I don't have an optical drive in my computer. I also already tried going to the device manager, uninstalling the driver, unplug the 6022be, plug the 6022be back in and it auto installed the driver. Still the same issue. So I tried going to device manager, uninstall the driver, unplug the 6022be, open programs & features to uninstall the hantek software, reinstall the software, plug the 6022be back in. Still the same issue. I also clicked on update driver, clicked browse for drivers, navigated to the hantek download and clicked ok to update. It said the driver was updated. Still the same problem. That's when I started thinking there was a problem with my 6022be. I took it to my girl friends computer, installed the software, plugged in the 6022be.....everything works fine. I could have sworn I saw someone was having a similar issue and someone typed or linked instructions on how to uninstall the 6022be drivers to fully clean them out and start new but I can't find it now. Perhaps I was dreaming about seeing that. I am running Win7 Ultimate 64bit.

Sorry for the misunderstanding with your post on uninstalling the drivers.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on August 26, 2014, 02:32:23 pm
Hi AznGothic,

A few things that I don't know if you have tried:

- A different USB port

- Connecting both ends of the USB cable for extra power.

- Disconnecting all other USB devices from your computer and leaving only the 6022

- Exiting/stopping all other programs while using the 6022

Good luck! :)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 27, 2014, 04:50:10 pm
Hi AznGothic,

A few things that I don't know if you have tried:

- A different USB port

- Connecting both ends of the USB cable for extra power.

- Disconnecting all other USB devices from your computer and leaving only the 6022

- Exiting/stopping all other programs while using the 6022

Good luck! :)

I have 4 front usb ports. Two of them are USB 2.0 and two of them are USB 3.0. So the USB 3.0 should be on a different controller (from my understanding). I tried it on all 4 with the same results and I also tried using both plugs. I did not try disconnecting other USB devices since the 3.0 should be running on its own controller anyways. I also did not try stopping other programs. I'll try both of those today.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jetfixxxer on August 27, 2014, 08:36:32 pm
Has anyone had an issue installing on 8.1?  I'm able to find the computer, but errors out because it's not finding the driver signature.  I've downloaded the latest from the Hantek website as well.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 27, 2014, 09:45:16 pm
Has anyone had an issue installing on 8.1?  I'm able to find the computer, but errors out because it's not finding the driver signature.  I've downloaded the latest from the Hantek website as well.

The driver isn't a signed driver. You have to disable the driver signature requirement in windows 8 to install it.


As for my issue. Still having the same issue. The only other usb devices I have is my mouse, keyboard and external hard drive. I disconnected the external hard drive with no luck. The keyboard and mouse should not be causing any conflicts and if I unplugged them I wouldn't be able to click around to do anything. I did a fresh boot and closed everything that starts up with my computer but still no luck. When you initially plug in the 6022be it states that it installed DRIVER 1 and DRIVER 2. But when you look in the device manager you only see DRIVER 2. I'm wondering if perhaps the issue is DRIVER 1? Does anyone know how I would be able to uninstall it when it doesn't even show up?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Jetfixxxer on August 27, 2014, 11:21:40 pm
Has anyone had an issue installing on 8.1?  I'm able to find the computer, but errors out because it's not finding the driver signature.  I've downloaded the latest from the Hantek website as well.

The driver isn't a signed driver. You have to disable the driver signature requirement in windows 8 to install it.



Thought about that after I posted. 

Thanks

Have you selected "show hidden" devices?  Under device manager "view, show hidden devices".
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mikewardlow on August 28, 2014, 12:54:21 am
Could somebody with the resources [ie] pic etc perform a small test ...

Send a repeating sequence of 2 pulses and 8 second delay...  [ probably use .2ms time base]

Pulse 1=100 us,  delay 100 us,  pulse 2=100 us, delay 8 seconds..........I..I.....................\\.....I..I................

Does the trigger properly,  does single sweep work correctly.
when single sweep and capture does the display change properly when you change the time base....

I just got a DDS120 and it cannot do this correctly.....
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 28, 2014, 02:52:18 am
Has anyone had an issue installing on 8.1?  I'm able to find the computer, but errors out because it's not finding the driver signature.  I've downloaded the latest from the Hantek website as well.

The driver isn't a signed driver. You have to disable the driver signature requirement in windows 8 to install it.



Thought about that after I posted. 

Thanks

Have you selected "show hidden" devices?  Under device manager "view, show hidden devices".

Yes I did. It's not a hidden device unless it has a different name from the one that was shown when the two drivers installed.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on August 28, 2014, 03:03:44 am
When you initially plug in the 6022be it states that it installed DRIVER 1 and DRIVER 2. But when you look in the device manager you only see DRIVER 2. I'm wondering if perhaps the issue is DRIVER 1? Does anyone know how I would be able to uninstall it when it doesn't even show up?

Sorry that you are still having problems!

When I installed my 6022 I also noticed that DRIVER 1 doesn't show up in device manager, but I was able to see it if I ran System Information. See an image of this in the following post:

https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg441478/#msg441478 (https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg441478/#msg441478)

I have the drivers installed on a desktop and on a laptop. On the desktop I installed the application software first and then just connected the 6022 to an USB port. In this case, Windows automatically found the driver, I presume off the internet, and installed it. This worked fine. On the laptop I connected the 6022 to a USB port before installing the application software, in this case Windows wasn't able to successfully install the drivers automatically, so I installed it manually. I can't remember if I used the CD or a downloaded file. In any case, there were no issues with this installation either.

If you uninstall DRIVER 2 again, you could try to use System Information to see if DRIVER 1 is also uninstalled. If it isn't, then it may be worthwhile to try and figure out a way to uninstall it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: AznGothic on August 28, 2014, 03:46:16 am
When you initially plug in the 6022be it states that it installed DRIVER 1 and DRIVER 2. But when you look in the device manager you only see DRIVER 2. I'm wondering if perhaps the issue is DRIVER 1? Does anyone know how I would be able to uninstall it when it doesn't even show up?

Sorry that you are still having problems!

When I installed my 6022 I also noticed that DRIVER 1 doesn't show up in device manager, but I was able to see it if I ran System Information. See an image of this in the following post:

https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg441478/#msg441478 (https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg441478/#msg441478)

I have the drivers installed on a desktop and on a laptop. On the desktop I installed the application software first and then just connected the 6022 to an USB port. In this case, Windows automatically found the driver, I presume off the internet, and installed it. This worked fine. On the laptop I connected the 6022 to a USB port before installing the application software, in this case Windows wasn't able to successfully install the drivers automatically, so I installed it manually. I can't remember if I used the CD or a downloaded file. In any case, there were no issues with this installation either.

If you uninstall DRIVER 2 again, you could try to use System Information to see if DRIVER 1 is also uninstalled. If it isn't, then it may be worthwhile to try and figure out a way to uninstall it.

Thank God! It finally works again!! Thank you so much TomC. Your info put me on the right track to figure this thing out.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on August 29, 2014, 04:01:48 pm
Here is the latest beta 17 copy of the user manual for Open6022BE:

http://jmp.sh/hhrhnkw (http://jmp.sh/hhrhnkw)

Any additions, changes or corrections to the content will be appreciated.

Updated download.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: danielr82 on August 29, 2014, 04:36:20 pm
Hello everybody, I stumbled over this discussion, also because I was looking for the difference between BE and BL. I just ordered the BE, since I got the impression that a BL is actually 2 devices in one, a BE Scope and a Saleae clone Logic16. The bad part: they are not usable together at the same time! You have to decide, analog XOR digital,  no mixed mode.   :--

Regards.
Faced with the choice of

6022BE - £38 (~$63 USD) and free delivery
Saleae clone on it's own - £6

(complete "test set" price £43 including delivery)

or 6022BL - £53, I went with the much simpler option of buying two tools that I could use at the same time if I wanted!


This thread is pretty cool, and spurred me on to actually get the cheap scope knowing that there is decent software for it :)

Much Gratitude to Richard,

Now just waiting for the thing to get here!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: olrowdy01 on August 29, 2014, 05:44:40 pm
Quote from: Matchless on Today at 02:01:48 AM (https://www.eevblog.com/forum/index.php?topic=17278.msg504031#msg504031)
Here is the latest beta 17 copy of the user manual for Open6022BE:

>http://jmp.sh/bvK6pDM (http://jmp.sh/bvK6pDM)

Any additions, changes or corrections to the content will be appreciated.

Excellent looking manual.  Only problem is the link doesn't allow you to download or save it.  I guess you have to login but I have enough logins already.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on August 29, 2014, 07:07:00 pm
Quote
Excellent looking manual.  Only problem is the link doesn't allow you to download or save it.  I guess you have to login but I have enough logins already.

Try the blue download button in the top right hand corner  ;)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on August 29, 2014, 07:25:44 pm
HI, I hope someone could help me solve my problem.

I've been using my 6022 with this open6022be software for a few months now.
I use this scope for automotive diagnostic. Everything was working until this afternoon. I still have a visual of the waveforms I'm looking for but what should be 12V now display (an mesure) as 5V.

Can someone point me to the right direction please?!?

thanks
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on August 29, 2014, 07:49:14 pm
Hi mrphil,

Make sure the probe is set to X10. If it's set to X1 the scope is limited to + or - 5V.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on August 29, 2014, 07:58:19 pm
Here is the latest beta 17 copy of the user manual for Open6022BE:

http://jmp.sh/bvK6pDM (http://jmp.sh/bvK6pDM)

Any additions, changes or corrections to the content will be appreciated.
Hi Machtless,
 I'm wondering if you uploaded the wrong version by mistake. This seems to be the same beta 16 manual you previously published!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on August 29, 2014, 08:03:45 pm
oh.. I always used this for rotation signal (engine speed , wheel speed sensor.....) and these signal are often below 5v... I didn't know it was limited to 5v.

by the way i'm not using the original probe (since these are not appropriate for automotive testing) I'm simple probe without the x10 switch attached to it. So if I put the software in x10 mode , i'm not getting the right voltage either.....

any solution ?
I could always mod the original probes that come with the scope.. is this the best I can do ?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on August 29, 2014, 08:13:29 pm
oh.. I always used this for rotation signal (engine speed , wheel speed sensor.....) and these signal are often below 5v... I didn't know it was limited to 5v.

by the way i'm not using the original probe (since these are not appropriate for automotive testing) I'm simple probe without the x10 switch attached to it. So if I put the software in x10 mode , i'm not getting the right voltage either.....

any solution ?
I could always mod the original probes that come with the scope.. is this the best I can do ?
Yeah, the software in X10 will just multiply the value of the input voltage by 10, but the input voltage value is clipped at + or -5V, so you'll still get the wrong voltage. You need to have a X10 probe to see signals >+-5V, so probably modifying the original probes is your best bet.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on August 29, 2014, 08:17:21 pm
thanks!

I found an old fluke 10:1 reducer in my toolbox, so for now I attached it to the probe I now have my 12v which I should have...

I guess these are the downs of not having a 700$ picoscope ...  |O

thanks a lot. you saved my day
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on August 29, 2014, 09:15:08 pm
ohh... I forgot one last thing

I don't know if RichardK is still working on this but I could really use a x20 fonction ... I got many x20 reducer
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: olrowdy01 on August 29, 2014, 09:28:56 pm
Quote from: Matchless on Today at 05:07:00 AM (https://www.eevblog.com/forum/index.php?topic=17278.msg504120#msg504120)
Quote
Excellent looking manual.  Only problem is the link doesn't allow you to download or save it.  I guess you have to login but I have enough logins already.

Try the blue download button in the top right hand corner  ;)

>
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: danielr82 on August 29, 2014, 10:15:48 pm
oh.. I always used this for rotation signal (engine speed , wheel speed sensor.....) and these signal are often below 5v... I didn't know it was limited to 5v.

by the way i'm not using the original probe (since these are not appropriate for automotive testing) I'm simple probe without the x10 switch attached to it. So if I put the software in x10 mode , i'm not getting the right voltage either.....

any solution ?
I could always mod the original probes that come with the scope.. is this the best I can do ?
Yeah, the software in X10 will just multiply the value of the input voltage by 10, but the input voltage value is clipped at + or -5V, so you'll still get the wrong voltage. You need to have a X10 probe to see signals >+-5V, so probably modifying the original probes is your best bet.

Might be a stupid question, but what makes the probes unsuitable for automotive work?

is it just that alligator clips are better?

how is the scope for automotive work?
are there enough channels for everything that you'd want to measure?


Hantek appear to do another scope (1008C) that has a bit better resolution (12bit) and more channels (8 instead of 2), but a much lower sampling rate - 2.4MS/s rather than 48Ms/s, which (I think) gives it about a 1MHz bandwidth...

I've been considering getting that (1008C) scope with more channels to go alongside this one (6022BE), mainly for doing audio stuff, but would use if for automotive work in the future...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on August 30, 2014, 07:10:07 am
Quote
Hi Matchless,
 I'm wondering if you uploaded the wrong version by mistake. This seems to be the same beta 16 manual you previously published!

TomC, thanks for pointing that out. I have not worked on it lately and the last small changes were only in the docx. I usually change the name of the last pdf in preparation of an over write, which I never did. I have updated the link, here it is again. Sorry! Mostly the same things are still pending in red waiting for your winter to arrive and Richardk's next release!

http://jmp.sh/hhrhnkw (http://jmp.sh/hhrhnkw)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on August 30, 2014, 07:16:13 am
oh.. I always used this for rotation signal (engine speed , wheel speed sensor.....) and these signal are often below 5v... I didn't know it was limited to 5v.

by the way i'm not using the original probe (since these are not appropriate for automotive testing) I'm simple probe without the x10 switch attached to it. So if I put the software in x10 mode , i'm not getting the right voltage either.....

any solution ?
I could always mod the original probes that come with the scope.. is this the best I can do ?

mrphil, have a look at the manual I posted. I have tried to incorporate a bit on the probes and the voltage which should hopefully make it clearer. I use mine on small motorcycle ignitions as well. I still need to order the HT probe for the plug lead as shown in the manual
Here is the link to the manual:
http://jmp.sh/hhrhnkw (http://jmp.sh/hhrhnkw)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: whitrzac on August 30, 2014, 02:36:02 pm
Is there a way to set the FFT range?

I want 0hz to ~30khz range. As of right now its all in the 1st division, anything less than 5k is impossible to read.

Anyone?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Keptenkurk on August 30, 2014, 08:09:10 pm
Thanks Matchless for the time and effort you've put in the manual!
/paul
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on August 31, 2014, 12:10:57 am
oh.. I always used this for rotation signal (engine speed , wheel speed sensor.....) and these signal are often below 5v... I didn't know it was limited to 5v.

by the way i'm not using the original probe (since these are not appropriate for automotive testing) I'm simple probe without the x10 switch attached to it. So if I put the software in x10 mode , i'm not getting the right voltage either.....

any solution ?
I could always mod the original probes that come with the scope.. is this the best I can do ?
Yeah, the software in X10 will just multiply the value of the input voltage by 10, but the input voltage value is clipped at + or -5V, so you'll still get the wrong voltage. You need to have a X10 probe to see signals >+-5V, so probably modifying the original probes is your best bet.

Might be a stupid question, but what makes the probes unsuitable for automotive work?

is it just that alligator clips are better?

how is the scope for automotive work?
are there enough channels for everything that you'd want to measure?


Hantek appear to do another scope (1008C) that has a bit better resolution (12bit) and more channels (8 instead of 2), but a much lower sampling rate - 2.4MS/s rather than 48Ms/s, which (I think) gives it about a 1MHz bandwidth...

I've been considering getting that (1008C) scope with more channels to go alongside this one (6022BE), mainly for doing audio stuff, but would use if for automotive work in the future...

Well I must admit I've used better scopes. I'm a mecanic teacher and the school o work for own 3 automotive picoscope which are amazing but expensive. 700$ each (unit only) & 1200$ each with all the accessories. The 6022be is way far behind these picoscope but for less than 100$ they can do most of the job I need a scope for.

If you compare this 6022 to the picoscope you'll be disappointed but if you can live with the fact that it's slower, the software is ( no harm to Richardk . he has done a wonderful job ) way behond what the picoscope software, it worth the 100$ you'll spend.

Like I said, I use it often for rotation signal. ( engine speed , abs sensor...) These signal are pretty much always below 5volt so it works right of the box. When you get to ignition & injection, you'll need a 10x reducer for injection as youll reach peak ay 40v or so. And even a 100x for ignition as you get peaks at +/- 300volts.

The software of the 1008c is more "automotive" ready as they integrate preset such as amp clamp for starting, charging, compression check , injection & ignition ramp.
The 6022 software only have voltage measurement preset so you'll have to do the convertion by yourself. But in the end you'll get to the point.

For the probes, in automotive diargnostinc we usually use voltmeter type probe with back probes (needles to get between the wire and the plastic connector).
Also the ground clamp need to be bigger and have a longer wire.


Anyhow, I guess you get with you pay for and the 6022 worth every $ if  you are ready to work a little harder.

I haven't try the 1008c , I only used the demo mode on the software. I plan to buy one in the next months.

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on September 02, 2014, 04:37:20 pm
mrphil,
          I would love to add a chapter to the use manual on using the 6022BE for doing the tests you can/have used it for! I know it asking g a lot, but if you ever have the time to spare it would be much appreciated. I know too little about that field to even attempt writing a guide!!!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on September 02, 2014, 07:47:25 pm
mrphil,
          I would love to add a chapter to the use manual on using the 6022BE for doing the tests you can/have used it for! I know it asking g a lot, but if you ever have the time to spare it would be much appreciated. I know too little about that field to even attempt writing a guide!!!

What would you need ?

for eample if I write something like:

Code: [Select]
Automotive tests
categorie INITION,
sub categorie : primary circuit (for a simple 2 wire coil)
testing procedure for firing voltage
 + test lead on control wire,  (neg (-) of coil)
 - test lead on body ground
using 100:1 reducer
setting x100 in software
voltage scale 50V / div
time scale 500 us / div
all this with a picture explaining what means what on the result of that scope

is this the kind of info you would need ?
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on September 02, 2014, 08:18:45 pm
Quote
What would you need ?

for eample if I write something like:

Code: [Select]

Automotive tests
categorie INITION,
sub categorie : primary circuit (for a simple 2 wire coil)
testing procedure for firing voltage
 + test lead on control wire,  (neg (-) of coil)
 - test lead on body ground
using 100:1 reducer
setting x100 in software
voltage scale 50V / div
time scale 500 us / div

all this with a picture explaining what means what on the result of that scope

is this the kind of info you would need ?

Hi mrphyl,
Basically I need to have it in the sort of same format as the present user manual.
A description of the test, assuming the person reading it has not done such a test before, and maybe why the test is done.
Then how to go about doing the test and the settings used on the 6022BE
Then a screen capture of the result, if applicable showing the waveform as well as the measure results.
As you suggested the chapter can be called Automotive tests and measurements.

This sort of measurements will even be useful to someone building or configuring ignitions for miniature engines or just DIY fault proving on your own car...?
This will be great information to add and the RC, motorcycle, car and other hobbyists will be able to see if this cheap DSO can do what they want it for.
I have had a closer look at the 1008 on ebay and it would be interesting to hear your findings once you have one.
Thanks for responding to this, your input is very much appreciated!


Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: mrphil on September 02, 2014, 09:10:34 pm
The only thing that I don't like with this 6022be is when I need to capture a slow signal. Today I had to check a potentiometer with a slow movement.  I set up the time scale to 1sec/ div and I was disappointed to see how slow the scope display the result. Is there any.way to speed that up?

For your manual. What I can.do is each time i write something for my classes (new test procedure) I will translate(I teach in french) and provide detailed picture w/ explanations.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on September 03, 2014, 08:05:32 pm
mrphil, sorry I have no idea, but richardk may have some ideas on this.
Thanks for you offer and looking forward to it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: lapeyroua on September 04, 2014, 07:50:28 am
Hello mrphil
Due to the design, Data are not displayed in real time.
"It has to capture the data, before it can display it."
look at this message https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg386643/#msg386643 (https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg386643/#msg386643) from Mark_O
Bonne journée
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: woodbird on September 04, 2014, 10:04:45 am
I did some interesting testing with another Library:
 I was able to read 50MSamples (could be even more) from both channels at the full sample rate of 24MHz.
Actually this gave me 2 Seconds of raw samples @ 24MHz (50MB/sec).
Combining this functionality with RichardK's software could become a very interesting result...
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: roderick on September 05, 2014, 12:34:49 am
Is there a way to set the FFT range?

I want 0hz to ~30khz range. As of right now its all in the 1st division, anything less than 5k is impossible to read.

Anyone?
Last I checked, there were no adjustments possible in the FFT function.  It seems to still be under development, with the axes not even labeled.  I hold out hope that one day, RichardK will have the time to get the code in a state where he feels comfortable releasing it to sourceforge.  Then there can be many more people working on details like this.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on September 05, 2014, 01:27:33 pm
I did some interesting testing with another Library:

Which library was that?

Quote
I was able to read 50MSamples (could be even more) from both channels at the full sample rate of 24MHz.
Actually this gave me 2 Seconds of raw samples @ 24MHz (50MB/sec).

Are you sure about that?  I ask because while 24 MB/sec is quite reasonable for a USB2 channel, twice that would be very difficult to achieve.  I'm not saying you're wrong, just that it seems unlikely, when the max theoretical USB2 capacity is <60 MB/sec, even if both sides of the exchange were running at 100% (which almost never happens).

That would be a pretty slick trick to achieve.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: woodbird on September 07, 2014, 10:08:21 am
I used this driver for testing on a Linux machine running Ubuntu 12.4:   https://github.com/rpm2003rpm
I extended the driver to read up to 48MB of raw data from each channel @24MHz and modified the main program acordingly.
The USB bus was totally reserved for this task. No other device was attached.
I used the inBuilt 1kHz square wave of the BE6022 as testsignal.
To verify the transfer I checked the received data at different positions. The result was always correct: about 12000 Samples for a half cycle of the squarewave.
(24M / 1kHz / 2 = 12.000) It took - as expected - 2 Sec. to get the whole Bulk data.
I also tested the same scenario at other sample rates (down to 100kHz). The results were always as expected. And of course it took the necessary time.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on September 08, 2014, 06:22:26 am
I used this driver for testing on a Linux machine running Ubuntu 12.4:   https://github.com/rpm2003rpm
I extended the driver to read up to 48MB of raw data from each channel @24MHz and modified the main program acordingly.
The USB bus was totally reserved for this task. No other device was attached.
I used the inBuilt 1kHz square wave of the BE6022 as testsignal.
To verify the transfer I checked the received data at different positions. The result was always correct: about 12000 Samples for a half cycle of the squarewave.
(24M / 1kHz / 2 = 12.000) It took - as expected - 2 Sec. to get the whole Bulk data.
I also tested the same scenario at other sample rates (down to 100kHz). The results were always as expected. And of course it took the necessary time.

Thanks, woodbird!  Both for the link, and the info.  I see you already verified your transfers, which is good.  One limitation of the device is it can't send just a single channel, so if you did only need one, you'd be limited to half the potential speed.  But as a result of that, most systems can't handle the continuous streaming rate that the 6022BE can apparently provide.  Good to know that a linux-based system can do so.   :-+   None of the Win-based systems I've used could ever manage that.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rasz on September 08, 2014, 10:36:59 am
I did some interesting testing with another Library:

Which library was that?

Quote
I was able to read 50MSamples (could be even more) from both channels at the full sample rate of 24MHz.
Actually this gave me 2 Seconds of raw samples @ 24MHz (50MB/sec).

Are you sure about that?  I ask because while 24 MB/sec is quite reasonable for a USB2 channel, twice that would be very difficult to achieve.  I'm not saying you're wrong, just that it seems unlikely, when the max theoretical USB2 capacity is <60 MB/sec, even if both sides of the exchange were running at 100% (which almost never happens).

That would be a pretty slick trick to achieve.

here is the magic dust that lets you push almost 50MB/s over usb 2.0

Code: [Select]
    HT6022_1MB   = 0x00100000  /*!< 1048576 Bytes */
}HT6022_DataSizeTypeDef;

there are 'Turbo' mass storage drivers that do the same, they aggregate SCSI commands into big 2MB chunks instead of transferring sector at a time

http://media.bestofmicro.com/I/M/340222/original/sequentialturbo.png (http://media.bestofmicro.com/I/M/340222/original/sequentialturbo.png)
slowest one on the graph is USB2.0
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: rosasharn on September 13, 2014, 08:21:08 am
Many thanks for this helpful data :-+, Rasz.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: jomor on September 24, 2014, 12:31:46 pm
apologies if this has been answered before, but has the noise issue been suppressed? i am reading back older posts but i can't figure out if it is software artifacts or hardware interference. I tried some of the suggested shielding tricks one by one but neither helped. Adding 100uF capacitors before the ams1117 regulator, shielding the dc-dc converter and grounding the other chip's heatsink did not help at all. I haven't tried shielding the input stages or adding the extra bypass ceramic capacitors yet though.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Fraser on September 24, 2014, 03:08:44 pm
The noise of a system is often set by the 'front end' amplification stages. A DSO is little different. If the power supply to the channel amplifiers is noisy, it will degrade the noise figure of the whole system. Screening of an input amplifier stage is best practice as that helps to reduce spatial interference ingress to the amplifier chain. You should fit the channel amplifier shielding as part of any effort to reduce the noise level of the scope. Like many such issues, it is often a case of curing more than one problem and small improvements in several places can often add up to a significant overall performance increase. At least this DSO PCB is easy to work on and simple to open so you can experiment with different noise reduction approaches. In a perfect world, all analogue stages would be supplied by a well decoupled analogue regulator and not a switching regulator with its associated bad habits of creating noise spikes on the output (at least in this design anyway). The input channels would then receive a nice clean supply rail from which to operate. The analogue stages should also be well screened, both above and below the PCB. The screens may be made from thin copper or tin plate....  at a push, even an old baked bean tin that has been flattened work suffice ! The screens should be in contact with the PCB but any PCB tracks should be protected against the screens influence by making small cut-outs on the screen sides so that it passes over them with some clearance. Sadly screening an amplifier can be a little more complex than just adding an overall screen. Sometimes you need inter-stage screening as well but the little 6022 probably does not have the gain to need such measures provided there is no digital electronics 'trapped' inside the screening can along side the analogue stages. And remember...you can never have too much RFI decoupling on a supply rail to analogue amplification stages !

The location of the screening for the input amplifiers is obvious from the PCB marking and the presence of the holes for the screening can locator pins. Hantek were penny pinching when they removed the two screening cans from the BoM and used a relatively noisy switching regulator with poor decoupling. Positioning the RFI prone switching regulator close to the unscreened input channels was just adding insult to injury.

Aurora
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: jomor on September 24, 2014, 08:39:22 pm
thank you for your reply

then the next step after shielding the input channels, is to replace the switching regulator with a low noise analog one. Replacing the 1117 is also worth trying. I haven't done any measurements yet, but i asume the 1117 is for 5v-->3.3v regulation. What about the switching regulator? Is it a step up regulator, has anyone measured its output? If this is the case, perhaps a clean, separate power supply instead of usb 5v could solve the problem.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Hernexto on September 25, 2014, 12:01:57 pm
Ooooook, so... after some days I finally manage to read the whooole thread!  ;D

I bought my 6022B*L* before the summer, knowing software is crap but I saw there were some open projects.

I trusted on open projects and I bought the unit anyway, but... now I see the unit with logic capabilities is not so 'accepted'.

I can change the .DLL file and use the open software (enough good for me from some months ago) so I'm happy and after so goooood job by RichardK I'm wondering if he managed to make the software easily work with my unit.

Is the beta18 the last one? (older links doesn't exist anymore, not sure if they are deleted manually or automatically. But his work without being on sourceforge/... it can be lost if RichardK dissappears or is being kidnapped.

PD: If you travel to Spain you will also have a some many beer 4 free!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: chemary on September 27, 2014, 05:01:44 pm
Lots of thanks to RichardK, I bought one Hantek 6022BE only because I saw that a software alternative exists and after trying it, is very good.

I have found some visual problems maybe it's my computer configuration (Win 8.1 with AMD A10-7800 APU):
- Render Phospor leaves the trace static and very dim, if I resize the window the trace persistence appears but in two places (original and where it will be placed when resized). It seems like if image is being updated in a back buffer but not updated to screen.
- If I click on Render Phospor two times and then on normal mode, the trace brighness remains at 50% instead of returning to 100% as expected.
- If I close the program in when in Render Phospor when I open it again is in normal mode but screen is freezed (it may be in Render Phospor incorrectly checked the button of normal mode). I have to select Render Phospor and normal again to solve this problem.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Andydb on September 28, 2014, 01:06:07 pm
Hi,
first I want to thank with RichardK for the nice and useful software that make our scope usable.

I've a very small issue to report, its connected to the waveform colors.
When you change colors (I've tested the second channel, I want it to mach the Hantek light blue channel color) it work correctly. When you reopen the application the color is not reloaded on the waveform but it is correctly displayed in the "waveform colors" (check attached image)

Here it is an extract from ini file after reopening the application:
Code: [Select]
[Colors]
CH1=65535
CH2=16776960
Math=8388736
Reference=15780518
XY=15780518

Hope this help

Andy
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: chemary on September 28, 2014, 05:32:18 pm
Some aditional issues:
- When I set 2V Volt/DIV (10x probe and display) and the input signal is a +12V ATX voltage I see a perfect straigh line at 10V, if I set 5V Volt/DIV y can see the 12V correctly with it's fluctuations.
- When I use Measure and I set "Entire Capture" the values I get are totally incorrect, but setting "Visible Capture" shows the correct values.
- When I try to save on Windows 8.1 I always get "'1.0' is not a valid floating point value".
- When Time/DIV is > 50.00ms the interface becomes quite unresponsible and I get access violation errors when I try to display some measures.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: kxdn on October 03, 2014, 06:24:52 am
This thread shows why we need open source software!
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Dave_S on October 03, 2014, 07:17:25 am
This thread shows why we need open source software!

If you want open source just get sigrok and wait until they are ready to support this particular device.
http://sigrok.org/wiki/Supported_hardware#Oscilloscopes (http://sigrok.org/wiki/Supported_hardware#Oscilloscopes)
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: PedroDaGr8 on October 09, 2014, 02:13:39 am
This thread shows why we need open source software!

If you read, RichardK said he would open-source it when he is done developing. He didn't want to release a half-baked product to the open-source community.

Sent from my LGLS990 using Tapatalk

Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on October 09, 2014, 08:24:30 am
This thread shows why we need open source software!

There's nothing stopping you from writing some, and sharing it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: SideshowBob on October 10, 2014, 02:29:32 pm
Hi, new here and found this great forum, blog and youtube channel after searching for info on the 6022BE, I have one on order.  Kudos to Richard K for his hard work & generosity in creating Open6022BE, I have been playing with 1.0 Pre Beta 18 in demo mode.  I find that the V RMS measure for a square wave (Artificial) is incorrect even with a duty cycle of 100 % (a straight DC signal): for 0 - 5 V I get RMS calculated as 5.69543 V (p-p & mean both 5.01961 V).  Is this a fault just with demo mode?  With the scope attached would this value come from the scope or be calculated by the software?

Great job by RichardK, just a small thing: I would love to see the measured output taking up less vertical space (esp when has several values) and would humbly suggest putting it below the "Measure" list panel.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on October 11, 2014, 04:09:23 am
Hi, Bob.  Welcome to the group.

Hi, new here and found this great forum, blog and youtube channel after searching for info on the 6022BE, I have one on order.  Kudos to Richard K for his hard work & generosity in creating Open6022BE, I have been playing with 1.0 Pre Beta 18 in demo mode.  I find that the V RMS measure for a square wave (Artificial) is incorrect even with a duty cycle of 100 % (a straight DC signal): for 0 - 5 V I get RMS calculated as 5.69543 V (p-p & mean both 5.01961 V).  Is this a fault just with demo mode?  With the scope attached would this value come from the scope or be calculated by the software?

I doubt it's restricted to Demo mode.  It's probably the same when Live.  The value certainly doesn't come from the scope module.  However, I'm not sure to what extent Richard is relying on DLL functions for this.  There is an error in the software, but it could be Richard's code or Hantek's.

Quote
Great job by RichardK, just a small thing: I would love to see the measured output taking up less vertical space (esp when has several values) and would humbly suggest putting it below the "Measure" list panel.

I can see why you'd suggest that.  And looking only at that screen, it seems quite reasonable.  However, as new Outputs are added, I'm pretty sure they populate horizontally, in that (now) mostly empty space.  There's very little room left under the Measure panel, and what do you do when there's more than just the 1?  Better just to have a collapsable Outputs panel.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: SideshowBob on October 11, 2014, 11:19:58 am
Hi, Bob.  Welcome to the group.

Hi, new here and found this great forum, blog and youtube channel after searching for info on the 6022BE, I have one on order.  Kudos to Richard K for his hard work & generosity in creating Open6022BE, I have been playing with 1.0 Pre Beta 18 in demo mode.  I find that the V RMS measure for a square wave (Artificial) is incorrect even with a duty cycle of 100 % (a straight DC signal): for 0 - 5 V I get RMS calculated as 5.69543 V (p-p & mean both 5.01961 V).  Is this a fault just with demo mode?  With the scope attached would this value come from the scope or be calculated by the software?

I doubt it's restricted to Demo mode.  It's probably the same when Live.  The value certainly doesn't come from the scope module.  However, I'm not sure to what extent Richard is relying on DLL functions for this.  There is an error in the software, but it could be Richard's code or Hantek's.
Thanks for the welcome and the quick answer, after I posted I did download the API and have a look for a RMS function when I get a chance.

Quote
Great job by RichardK, just a small thing: I would love to see the measured output taking up less vertical space (esp when has several values) and would humbly suggest putting it below the "Measure" list panel.

I can see why you'd suggest that.  And looking only at that screen, it seems quite reasonable.  However, as new Outputs are added, I'm pretty sure they populate horizontally, in that (now) mostly empty space.  There's very little room left under the Measure panel, and what do you do when there's more than just the 1?  Better just to have a collapsable Outputs panel.
In full screen (maximised not fs mods) there is plenty of room under the measure list (YMMV I have a largish screen) on the lhs and having 3 active measurements at the bottom vertically compresses the scope screen distorting the xy ratio.  Just an optimisation tweak for larger screens, a floating measurement window would be another way to achieve the same thing or stacking the measurement results horizontally then vertically.  Not a big issue at all.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: SideshowBob on October 11, 2014, 12:59:01 pm
I had a quick look at the very sparse SDK API and looks like all measurements are in the software.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RedOctobyr on October 11, 2014, 02:54:05 pm
Hi all. I have been looking for a low-cost option for getting a basic oscilloscope. Mainly for learning more about some electrical issues in a hobby of mine, not for use as an EE or anything :) I wanted something that could capture data, for review later.

I just ordered a 6022BE. Out of the different USB options, this seemed the most viable for me, while still being under $100.

Ironically, a thread that describes the drawbacks of the product (especially the software) actually inspired me to buy it, as a result of the amazing work that Richard K has done. Thank you Richard!! I hope that Hantek is paying attention.

I do have a question. I want to look at voltage dips/spikes in a 6V source. That's too high for the probes in x1. If I go to x10, will I lose a lot of voltage resolution? 8 bits of resolution, across a 100V total range (+/- 50V), implies ~0.4V steps? That would make the steps quite coarse, for looking at just a 6V signal. My apologies if this isn't actually how it works.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Mark_O on October 11, 2014, 09:54:09 pm
In full screen (maximised not fs mods) there is plenty of room under the measure list (YMMV I have a largish screen) on the lhs and having 3 active measurements at the bottom vertically compresses the scope screen distorting the xy ratio.  Just an optimisation tweak for larger screens, a floating measurement window would be another way to achieve the same thing or stacking the measurement results horizontally then vertically.  Not a big issue at all.

Good points.  Maybe that's something Richard could make configurable, once he reaches the optimization phase of his implementation.  Maximizing the space for signal traces is certainly a worthwhile objective.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on October 11, 2014, 10:15:50 pm
Hi all. I have been looking for a low-cost option for getting a basic oscilloscope. Mainly for learning more about some electrical issues in a hobby of mine, not for use as an EE or anything :) I wanted something that could capture data, for review later.

I just ordered a 6022BE. Out of the different USB options, this seemed the most viable for me, while still being under $100.

Ironically, a thread that describes the drawbacks of the product (especially the software) actually inspired me to buy it, as a result of the amazing work that Richard K has done. Thank you Richard!! I hope that Hantek is paying attention.

I do have a question. I want to look at voltage dips/spikes in a 6V source. That's too high for the probes in x1. If I go to x10, will I lose a lot of voltage resolution? 8 bits of resolution, across a 100V total range (+/- 50V), implies ~0.4V steps? That would make the steps quite coarse, for looking at just a 6V signal. My apologies if this isn't actually how it works.
You are right that the resolution for 8 bits is about 0.4% of total range, that equals about 0.4V steps for a 100V total range as you said. However, the way I see it, you wouldn't have to use 100V total range with the probe set to x10. For a +6V signal with a 1Vpp ripple the range must cover about 14V total (+7/-7). So it seems to me that you could use 2V/Div with a total range of 20V (+10/-10). Beware that even with the probe set to x10, if you use 1V/Div, it will clip anything above +5V.

Edit: The original post calculated the total range based on 8 vertical graticule divisions, it was corrected to 10 graticule divisions since although only 8 are visible the ADC provides data for 10.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on October 12, 2014, 03:00:16 am
Here are a couple captures related to the above. The subject is the output of a wall wart rated at 7.5VDC, but in reality it's output is closer to 8VDC. The trigger is set to single shot at a level of about 9.5V. With the probe attached I suddenly connect a 7.5 ohm resistor across the output, if the transients reach 9.5V the scope triggers and captures the transients. Note on #1 that the transients try to extend above +10V but get clipped off. This is due to the 6022's input protection circuit. Since the setting is 2V/Div the total range is -8V/+8V but there is a little leeway and you can get away with up to +10V signals. #2 shows the left hand side of the signal at 200ns/div to get a better look at the clipped signal.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: RedOctobyr on October 13, 2014, 01:44:33 am
Ahh, I see. Thank you, TomC. The screenshots from actual use, at 8V, using x10, are very helpful, BTW.

I had assumed that the 8-bit resolution was always applied across the whole +/-5V actual input range to the scope (whether using x1 or x10 probes). This was apparently a bad assumption. I'm guessing the 8-bit resolution is actually applied maybe to just the available range, based on the volts/div setting you're using. Which is great news.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on October 13, 2014, 03:35:08 am
Ahh, I see. Thank you, TomC. The screenshots from actual use, at 8V, using x10, are very helpful, BTW.

I had assumed that the 8-bit resolution was always applied across the whole +/-5V actual input range to the scope (whether using x1 or x10 probes). This was apparently a bad assumption. I'm guessing the 8-bit resolution is actually applied maybe to just the available range, based on the volts/div setting you're using. Which is great news.
Yes, that's right, on the setup of the screenshots (2V/Div), the range is 20V (-10V/+10V). So the resolution is 0.4% of 20V which comes to 80mV steps. However, these scopes don't use a true attenuator for all the range settings. For example, on x10, only the 1, 2, 5, & 10V/Div range settings are obtained via the attenuator circuit which consists of an operational amplifier with 4 switchable gain resistors. The range settings below 1V/Div and above 10V/Div are obtained by zooming the image in or out. For example, the 100V/Div range setting is obtained by setting the gain to 10V/Div and zooming out by x10. So as far as what the ADC is seeing, the resolution, and the maximum swing that you can see before clipping, the 100V/Div range setting is the same as the 10V/Div range setting. The only difference is that the signal takes less room on the display.

Edit: The original post calculated the total range based on 8 vertical graticule divisions, it was corrected to 10 graticule divisions since although only 8 are visible the ADC provides data for 10.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on October 20, 2014, 05:41:13 am
For the last few days I've been exploring some 6022 peculiarities related to the way that it displays signals that should span the full height of the graticule. The results depend on the V/Div setting and the baseline setting. What happens, in my opinion, is not always intuitive. So I decided to write down my explanation of this effects and to take screenshots of some of my experiments.

The attached PDF, "Some 6022 Peculiarities", is my attempt at explaining what happens and why. This isn't all new material and many of you may already be familiar with it, but I found it helpful to have it all together in the 3 PDF pages. The attached screenshots are experimental results obtained by scoping the output of my Function Generator. They are intended to help support the write-up. Note that the "Measurement Output" provided by the 6022 is incorrect in some of these screenshots, specifically #1, #2, #8, #9, #10. So pay attention to the file names, the actual scope settings, and read the displayed signal values yourself.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Matchless on October 20, 2014, 11:51:29 am
Hi TomC,
             This info will be very helpful to some people! I would gladly include it in the user manual if you agree. :-+
I will also put your name to this if you can let me have the pdf in maybe a docx format. If you do not want your name to it, can I use your forum handle?
Thanks.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: TomC on October 20, 2014, 03:35:00 pm
Hi TomC,
             This info will be very helpful to some people! I would gladly include it in the user manual if you agree. :-+
I will also put your name to this if you can let me have the pdf in maybe a docx format. If you do not want your name to it, can I use your forum handle?
Thanks.
Hi Matchless,

Here is the PDF in odt format, I don't have word, but you should be able to open odt in the later word versions. I don't know if the page format will be completely accurate, but it should be close. I normally just use my forum handle for anything I publish. You are welcome to use any or all of this info and/or edit it if you wish!
Title: Comprehensibility enhancement suggestion (ease understanding)
Post by: Mark_O on October 20, 2014, 11:57:54 pm
Hi TomC,
             This info will be very helpful to some people! I would gladly include it in the user manual if you agree. :-+

I too thought Tom's explanations were well done, and did a good job of capturing the important limitations within which the 6022BE works (along with the reasons why).

I couldn't help thinking though, as I was looking at his clipped screen shot on Page 2, where he wrote:  "...will appear clipped. Although this is normal, it may be confusing to the user, since, in general, it would be reasonable to expect an 11.5Vpp signal to display properly within a 16Vpp full screen range." that he was certainly right about it being confusing to the user.  Especially so for newbies, who may be using this as their first scope.  But even old-timers, who have to constantly stop and think, as they're adjusting gains and offsets, "Hmm, baseValue x scaling + offsets >+limit, or <-limit?  Ah yes, THAT's why it's truncated."  Or perhaps it really IS truncated at some level, and you're wondering, "is that because of the front-end limitations?" even when it's not.

When one is using a scope, they expect to be shown what's actually there (a visualization tool), not silently (invisibly) bump into the measurement limitations, and shown something not reflecting reality.  That's why I've always thought that as the ranges get changed, and the offsets get shifted, the display screen should dynamically make those boundaries instantly obvious, without requiring any mental gymnastics.  I.e., red band regions at top and/or bottom, or a cross-hatched region for same, that clearly and immediately delineates where the scope input can never display valid output. 

I was saving that as an enhancement suggestion for Richard, since obviously Hantek would never want to do something so user-friendly, which would call attention to the device's inherent limitations.  But I think that would go a long way toward minimizing confusion from stumbling into the invisible boundary conditions on the 6022BE.  Make them visible, and half the problems go away (the 'not being sure where they are at the moment' part).  Then at least you can adjust to (partly) avoid them.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: JonnyVolts on October 26, 2014, 02:04:01 am
Just my 2 cents as a novice with a little over a year into my E.E. degree and now putting in a year of some hands on while I get my business up and running before pursuing more school.
I've only had the unit for 2 days but most people researching the unit just want to know, should I buy one for basic analysis?

I was told whatever I do, absolutely do not, under any circumstances, do not buy a Hantek or Sainsmart USB oscilloscope.
I'm glad I found this forum.

For general audio circuits, fancy light circuits and general low speed analog devices that aren't on the cutting edge of technology, this unit is perfectly acceptable.
I'm just designing musical instrument preamps, oscillators, delays, synthesizers, microphone preamps, simple light effects and maybe the occasional hobby ESC or sensor on the car.

I will be the guy who suggests the same 10 dictators appearing on every forum someone asks about buying a cheap scope have something to gain by blacklisting these and pushing Rigol unrelentingly.
If you're not trying to repair satellites, work for the cable company, repair ultrasonic visualizers and other pieces of equipment costing tens of thousands of dollars or at least very high speed devices, what's the harm in starting off with a $60 USB scope?
Nothing unless you're the guys selling $350 bench scopes that are only a few steps up in performance and quality but the way you pay for your winter vacation.

Of course it may very well just be gear snobbery which is a despicable trend in consumerism culture.
My point is I'm happy with the purchase and in another year, yes I'll probably buy a 100mhz bench scope but for most of us dealing with common analog circuits well below the bar of cutting edge technology, this is a reliable tool.
If you're not an engineer or equivalent through hands on industry employment, odds are you're just a hobbyist building RC gadgets or a guy running a car stereo installation business.
A $65 scope is more tool than you will ever actually need for such work.

I won't call it a "hack" but if you set the software to 50Mhz, screen capture with a decent program and then playback in slow motion...guess what??
It's not fancy.
It's not direct perfect.
It is however a useful tool as opposed to the "toy" most gear snobs have labeled it.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: Rasz on October 26, 2014, 03:13:04 am
snobs? dude, you just agreed this toy is ok for audio frequencies only
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: JonnyVolts on October 27, 2014, 02:06:32 pm
snobs? dude, you just agreed this toy is ok for audio frequencies only

I didn't use the word only so next time you think you have the power and right to speak for me, you should message me first and not rely on computer armor to pull that kind of crap.

The unit is an absolute champ on my laptop but this beta software is a disaster.
On my desktop the OEM won't even install, the beta development does but it runs like crap with an absurd amount of latency.
My desktop is 10x the machine my laptop is but it's also about 5 years old.

Feel free to read what I said again and if necessary, message me since English clearly isn't your first language or civility and basic human decency are qualities you like most people online do not possess.

The scope runs great on the right computer which tells me everyone pushing Rigol has a personal agenda.
Title: Re: Hantek 6022BE 20MHz USB DSO
Post by: olrowdy01 on October 27, 2014, 03:00:59 pm
Quote from: JonnyVolts on Today at 01:06:32 AM (https://www.eevblog.com/forum/index.php?topic=17278.msg538472#msg538472)>Quote from: Rasz on October 26, 2014, 02:13:04 PM (https://www.eevblog.com/forum/index.php?topic=17278.msg537422#msg537422)
snobs? dude, you just agreed this toy is ok for audio frequencies only

I didn't use the word only so next time you think you have the power and right to speak for me, you should message me first and not rely on computer armor to pull that kind of crap.

This is an open forum and you'll have to get used to comments by others.

Nor did you call the Hantek a toy. Rasz put that title on it in his post.  But ...... YOU could have been more diplomatic in your response.

The unit is an absolute champ on my laptop but this beta software is a disaster.

On my desktop the OEM won't even install, the beta development does but it runs like crap with an absurd amount of latency.
My desktop is 10x the machine my laptop is but it's also about 5 years old.

All programs don't run perfectly on all computers.

Feel free to write your version of the software. RK has made a great improvement over the original OEM software that runs fine (such that it is) on my old and newer computers.
[snip]

The scope runs great on the right computer whi