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 else 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 three most recent bugs (#14 to #16) which eTobey found over the past two days, and which electronics hobbyist has added in the SDS800X HD bug thread?