Hantek DSO5202BM: The problem with using cursors Track mode.

Oleg10011001

Now I understand. Thanks for the explanation! I want to note that really is that cursors measure the time located between DOTS and constantly and I do not understand why it made possible? Would not it be more correct to move the cursors only by dots? In addition, if the waveform is drawn in Vectors mode, why not move the cursors to measure voltage on the point vectors that are known? I would also add that I have previously raised the issue that need the ability to adjust the accuracy / speed of moving cursors measure time. At that time I did not have coarse displacement mode because the cursor moves very slowly. This time, I note that I do not have pixel-precise cursor movement. Still, when 2ns scan on the waveform signal digitized at a frequency 1Gs / sec cursor step 5 ns - it's too rough, you need to be able to take a step 1ns move the cursor, just you can move the cursor to any dots on the screen.. I certainly can move the waveform so that was one of the cursors to the desired place, but for the second cursor, this method is not suitable ...

P.S: I would also like to know whether it is possible here to ask not only fix bugs or modify something, but also add new capabilities previously missing? For example, I would like to have trigger catch pulses which differ from the specified values are not only the width (duration), and height (voltage)...

Oleg10011001

Thanks for the explanation!

Moreover, a new error has been added in the latest version of the firmware; in previous versions of the firmware, this error was absent. When using the oscilloscope in a mode with two windows in the upper window (when it is active) began to work badly cursors to measure the voltage in "Track" mode. Once the cursor "S" and / or "E" leave that part of the waveform, which is projected in the lower window, so immediately stops working associated cursor measuring voltage

This bug been fixed

The latest version of the firmware the following new bugs have been seen:
1) After clicking on the "SAVE TO USB" button, in the process of performing this function, for some reason, for a short time, a menu opens, if it has been closed;
2) When the set scan time 2ns sometimes waveform drawn some strange wavy line:



If the capture of oscillograms is stopped, you should perform some action with a waveform, for example just move it, and the view waveform becomes normal:



This bug was first spotted back in the previous version of the firmware and continues until now.

Oleg10011001

I found another bug or maybe a lot of bugs in one place. It is impossible to make cursor measurements of any type on the on-screen reference waveform - when you specify as a source RefA (namely from there taken the reference waveform shown on the screen), cursors simply disappear from the screen and still can not switch between cursors "S" and "E" through F4 keys. Neither indicator is lit next to the control element V0 and its rotation or pressing or has no effect. For exemple:








In addition, when the source is selected RefB (off) appear on the screen cursors, which measure is not clear that, while switching between cursors "S" and "E" are not generally available. For exemple:

Oleg10011001

For wavy line, I do not do anything special. Now perform the following steps:
1) Turn on the oscilloscope, and then reset it to the default;
2) Starting to get the waveform with a USB-connector Arduino Uno, I placed it on the screen so that it takes up most of the screen;
3) During the capture scan waveform changed with time. At this time, I put it on 2ns;
4) By repeatedly pressing the button "SINGLE SEQ" and in one of the still images obtained wavy line:







As you can see, this time not all the waveform drawn by a wavy line. In addition, this time as I did not move the waveform on the screen its appearance has not changed and has not returned to normal. I have wavy line is obtained from the very first attempt (pressing the button "SINGLE SEQ"). However, not every waveform fails to see it. For example, I could not get a wavy line on the waveform obtained from the calibration of the generator built-in oscilloscope. I'm not sure that this bug. Just I saw something seemed strange to me and I show you. You tell yourself bug or not.

Oleg10011001

Well, the latest version of the firmware, I saw the following:
1)

After clicking on the "SAVE TO USB" button, in the process of performing this function, for some reason, for a short time, a menu opens, if it has been closed

This bug been fixed;

2) For the most part solved the problem with the work cursor measurements on the reference waveform. At the same time somehow made inaccessible cursor measurements the type "Track" as the source when the selected reference waveform. And, in doing so, we assumed that the user first selects the type of cursor measurements, and then indicate the source. If you do the opposite, that is, first by selecting the source (for example: RefA), and then the type of cursor measurement the type "Track", we get the following situation:



The cursor "S" and "E" are functioning properly, but the associated cursors measure voltage - do not work. In this situation, you can easily get, if the user uses a different type of cursor measurements on the reference waveform and does not need to modify the source before going to cursor;

3) When fixed scan time 2ns waveform with USB-connector Arduino Uno is still drawn a wavy line.

Oleg10011001

Well, waiting for the long-awaited bug fixing reported finding new bugs (or strange). All of them are related to the work the trigger type "Edge" (Slope: Rising); it is used by default. The only thing I would change in the settings Trigger Mode: Normal (default is Mode: Auto). In general, I wanted to see what kind of transients occur when you turn on the power supply of my laboratory. I connected the oscilloscope to the power supply, set up in the above manner the trigger and turn on the power unit. Here is what I saw on the oscilloscope screen:



It seems to me that, in this case, the center line, dotted line and waveform should intersect at one point? Here we see that the trigger load for 80ms before the signal level has reached the trigger level trigger... Next, I turn off the power supply and the trigger for some reason again is triggered, although the settings specified trigger Slope: Rising, instead Slope: Falling. Here is what I saw on the oscilloscope screen:



Here we do not even see the waveform of the places where the signal level has reached the trigger level trigger... In addition to this, I can not, with the trigger in the specified mode, scroll through the registered waveform horizontally. When you try to do this can happen one of two things:
1) Waveform disappear, as happened in this screenshot:



2) Waveform does not disappear from the screen, but at the same time stands still and does not scroll. I see in this movement only trigger offset marker.

Oleg10011001

Well, after a firmware update, I saw that what I said earlier (Post time 2016-8-6 18:07:33) remains relevant. As for my message yesterday, I seem to figured out what the problem was - it happened fast transients that were not visible at the scan time, which has been established but the trigger on them worked. You only need to deal with the inability to scroll horizontally registered waveform when the oscilloscope is waiting for the next event, which will trip the trigger and update the waveform on the screen. By the way, here's waveform with the transient, who have not seen, but which trigger works when you turn off the power supply. Look, I try to scroll it horizontally, but it goes on, with only shifts the trigger handle:

Oleg10011001

The track cursor doesn't support reference waveform.

Yes, I already knew it, but the reason why it was done I do not understand. I merely pointed out that this case is not brought to an end. It takes more to make inaccessible switch mode cursor measurements type "Track" when the source is selected as the reference waveform (RefA or RefB).

And the wavy line should come from the input signal.

I do not understand how this is possible? When the set time 2ns scan oscilloscope sampling at a rate 1Gs / sec. Thus it appears that one cell of the grid on the screen is necessary on the two points. On wavy lines I see about two waves of one grid cell and thus get one out of two:
1) Existing point somehow connected is not a straight line but an arc;
2) the points themselves for some reason, are drawn in the form of an arc, not a straight line or point.
Between samples, the oscilloscope receives no information about the signal and thus it is not clear how the input signal may affect what an oscilloscope connects two adjacent points on the arc of the screen, rather than direct...

About your new questions, you can use the single trigger "SINGLE SEQ" to get the fast transients signal and move the waveform horizontally.

I understand it. Now there is the question of what is normal if that is not possible to scroll horizontally registered waveform when the oscilloscope waits for the next event, which will trip the trigger and update of the waveform on the screen? When continued capture waveforms stopped scrolling no problem.

Oleg10011001

1. The track cursor doesn't track the ref waveform, please use the time and voltage cursor to measure.

Okay, but is it possible to prevent the entry into the mode that is not supported? When I switch to cursor measurement type "Track" choice as a source of some reference waveform is blocked and it is right. However, if I choose as a source of reference waveform, the ability to switch to cursor measurement type "Track" for some reason are not locked and it is not correct because it allows input mode is not supported. It's not difficult to modify.

2. When the base time is less than or equal to 80ns, the scope enters into interpolation mode. Most of the points are drawn by the interpolation method based on the collected points.

It is clear, thank you for the clarification! However, I believe that when there is a waveform drawing mode using dots, interpolation is not used and you can see the true shape of the signal as it is. It turns out it is not possible here.

3. In normal trigger mode, only when the waveform meets the trigger condition, the scope will scan, the waveform will be displayed, but the waveform will not be saved or stopped.

It is clear, thank you for the clarification!

Earlier, I pointed out even at some moments in the work of the oscilloscope, which seems to have not seen you. In particular, I pointed to the absence in the upper window channel markers in dual view. I also pointed out that immediately after the switch to the Cursor mode type "Track", the voltage measuring cursors are unattached to the waveform. It has so far been no fixes or defined as the correct operation of the oscilloscope.

I will add that I would love to see constantly on the oscilloscope screen, the current sample rate and memory depth is used.

Oleg10011001

Today rechecked it again, how cursors measure voltage work immediately after switching to the "Track" mode. If you switch to the "Track" mode takes place during the continued recording waveform, the cursor is positioned is normal, but the voltage is not calculated correctly:



If you switch to the "Track" mode takes place during the time when the registration of the new waveform is stopped, and the work goes to the stored waveform, the cursor can still be positioned wrong:



Marked are bugs in the cursors measure the voltage and calculate the voltage can only be observed immediately after the switch to the "Track" mode. After the start of movement of the cursor "S" or "E" these bugs disappear and the oscilloscope starts to operate normally. As for the lack of a channel marker in the top window when working with two windows, then this can be seen by looking in the following illustration:



Here you can replace the incorrect drawing of the waveform in the lower window at high magnification.

I will add that I would like to, with the default settings of the oscilloscope, does not change the previously set color scheme and sound mode button presses. If this can not be done, it would be desirable that the default was set that color scheme, which can be seen in the screenshots provided to me; In my opinion, this color scheme is best combined with an external oscilloscope view.