Cursor shows wrong value?

[eTobey]

Hi,

I am using the cursors in rollmode on the SDS800X HD, and they dont show the values like I think they should.

I dont know what I am missing, but isnt the cursor supposed to show the time as in the timeline at the bottom?

[wraper]

-620s completely matches with what's on the screen. As of X1, X2 values, they're likely display values related to end of capture.

[eTobey]

As of X1, X2 values, they're likely display values related to end of capture.

X2 has 380s to the one end, and 620s to the other end, but it shows 1270s? X1 has also a value that I cant the the reference of.

Its actually the complete capture.

(Dont ask me how the rollmode worked in this case, since it is buggy.)

Edit:
It just struck me. There is this issue,where the trigger rate drops when using low sample rates (manual). One said, that there might be more memory filled, as you could see on the screen, and thus it cant trigger as you would expect. This could be the case here too, and there might be more in the memory than you can see. And this "end of capture" might be referenced too.
No, that doesnt work. X2 then should have the smaller absolute value.

[eTobey]

Now I know whats going on:
I have the "trigger" reference set to the right border of the screen, to have a the proper times in the horizontal axis. (Something that should be there by default I would say. There is no trigger in rollmode in automode.) Then when changing to a lower horizontal scale, the trigger reference would move outside of the screen (to the right). But the values on the horizontal axis would not align with the reference (but the numbers on the cursors do). By moving the trigger reference, everything comes back into alignment (the reference is put back onto the right border of the screen).

Just another bug.   

[Sensorcat]

The scope stores an offset value in its timebase setting (-> screenshot), in this case -650s. This value is then added to the value in the coordinate system displayed.

X1 = 0s + (-650s) = -650s
X2 = -620s + (-650s) = -1.27ks

[eTobey]

The scope stores an offset value ...

The scope has another bug...