Latest Binary: 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.
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?
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?
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?
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
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
Latest Binary: 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.
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.
...
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.
...
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?
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
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.
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.)
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
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.
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?
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.
RickHello 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?
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.
RickHello 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