I have setup a qualified trigger that does not trigger at all on a 100mv/div scale. The edge trigger does trigger on this signal down to 5mv. Signal is from ~0 - 2.7V
I start wondering if my scope hase some issues itself, but then many other issues were confirmed by others...
Let's see, analyse and think: ............
Wait for a bit until new FW comes out. Then start first with all the stuff that was reported in release notes that will come with it, then all the stuff that was reported and you don't see them in release notes.
This is my advice to you. You don't have to listen, of course.
What was also confirmed by many others are many false alarms and errors you made and then blamed scope . That is why we say a methodical approach is needed and good detailed explanations are needed.
For instance, you NEVER write what FW you are running at the time you encountered something that is suspicious behaviour or bug.
So in few weeks from now, when stuff is fixed nobody in the world will know if all the stuff you reported is still suspicious or that was some old initial FW that is not relevant anymore.
Like I said before but it fell on deaf ears.
You can stop writing about bugs, looking for them, or investigate them at this moment.
You are wasting your time (and ours if we decide to read).
There is imminent FW release being tested, as we speak.
Wait for a bit until new FW comes out. Then start first with all the stuff that was reported in release notes that will come with it, then all the stuff that was reported and you don't see them in release notes.
This is my advice to you. You don't have to listen, of course.
We are blue in the face from telling such, so much so I think ears must be just painted on.
What was also confirmed by many others are many false alarms and errors you made and then blamed scope . That is why we say a methodical approach is needed and good detailed explanations are needed.
For instance, you NEVER write what FW you are running at the time you encountered something that is suspicious behaviour or bug.
So in few weeks from now, when stuff is fixed nobody in the world will know if all the stuff you reported is still suspicious or that was some old initial FW that is not relevant anymore.
Like I said before but it fell on deaf ears.
You can stop writing about bugs, looking for them, or investigate them at this moment.
You are wasting your time (and ours if we decide to read).
There is imminent FW release being tested, as we speak.
Wait for a bit until new FW comes out. Then start first with all the stuff that was reported in release notes that will come with it, then all the stuff that was reported and you don't see them in release notes.
This is my advice to you. You don't have to listen, of course.
You are too harsh with eTobey, I think. Yes, there have been "false alerts", but a surprising number of actual bug findings too. And this thread is titled "is it me or the scope?", so what's wrong about bringing up potential issues where one is confused and wants to ask others for help to clarify the situation?
Firmware version is 1.1.3.3. throughout -- what elese would it be for mere mortal users? But I do agree with you that a bit more detail about the signals and settings would be helpful in many reports.
Regarding the upcoming firmware, you are quite bullish in your advice that "it's likely to change everything, you can stop looking for bugs for the time being". Have you tried with the two most recent bugs (#14 and #15) which eTobey found over the past two days, and which electronics hobbyist has added in the SDS800X HD bug thread?
530+ posts and 4-5 bugs from him.
Any bugs in old FW found postmortem after new FW is available are either fixed already (sometimes one bug triggers a revision of part of design, that reveals some errors in common parts, so one fix fixes several bugs). Bugs that were not fixed will be discovered in new one anyways.
when triying to use the mask feature on the zoom window, i then was not able to get the zoom window back to the state where it was before setting up the mask (see picture).
when triying to use the mask feature on the zoom window, i then was not able to get the zoom window back to the state where it was before setting up the mask (see picture).
Edit: Did you attach the wrong picture maybe?
when triying to use the mask feature on the zoom window, i then was not able to get the zoom window back to the state where it was before setting up the mask (see picture).
Edit: Did you attach the wrong picture maybe?
Yes it was indeed the wrong picture. Since i had the same issues again with a strong indication, that this is not just an issue, i moved over to the bug topic.
Yes, i have to take a step back and analyse more and not ton confuse others. But at the same time i would like to encourage others to be a bit more playful in trying things out that i wrote. Because some might find what i missed. As 2N3055 might have found nothing wrong, he could have tried other things too, like creating a mask by hand, which is probably the difference with this issue. (This sentence has truely only an objective meaning)
Can I ask why are you multiple posting same issues in several different topics?
when triying to use the mask feature on the zoom window, i then was not able to get the zoom window back to the state where it was before setting up the mask (see picture).
Edit: Did you attach the wrong picture maybe?
Yes it was indeed the wrong picture. Since i had the same issues again with a strong indication, that this is not just an issue, i moved over to the bug topic.
Yes, i have to take a step back and analyse more and not ton confuse others. But at the same time i would like to encourage others to be a bit more playful in trying things out that i wrote. Because some might find what i missed. As 2N3055 might have found nothing wrong, he could have tried other things too, like creating a mask by hand, which is probably the difference with this issue. (This sentence has truely only an objective meaning)
Can I ask why are you multiple posting same issues in several different topics?
You started now double spamming.
And as people already said to you multiple times: I'm not going to put in ANY work because you are too lazy to do proper write up.
With bugs you don't accuse and let other side defend themselves.
It is quite the opposite: Unless you can prove a repeatable method to replicate error and demonstrate it step by step,then probably you made a mistake or misunderstand grossly how things work.
Some hints of proper use of Reference waveforms are here:
https://www.eevblog.com/forum/testgear/probe-into-probes-whats-up/msg4678768/#msg4678768