I have another issue:
I set up a qualified trigger, but the edge trigger is not stable.
The deviation gets worse, if i set the trigger level lower.
Has anyone else turned on their SDS800X to find a fixed DC offset (~700 mV) on CH1 and CH1 only?
Pictures! You have to take pictures, because some will never believe you. And you may consider, that some aspects of it a very confusing, so you take your time and try to figure out if its a problem with the setup.
Anyone else seen this?
Has anyone else turned on their SDS800X to find a fixed DC offset (~700 mV) on CH1 and CH1 only?
Anyone else seen this?
Not.
There is mention of offset issues in beta FW release notes but not this exact issue it seems.
It is customary when reporting an issue to state the FW version in use.
Not.
There is mention of offset issues in beta FW release notes but not this exact issue it seems.
It is customary when reporting an issue to state the FW version in use.
Point taken.
Software Version 1.1.3.1
UBOOT-OS Version 2.8.10
FPGA Version 2023-12-29
HW Version 00
Thank you. While the release notes don’t mention offset issues, it does mention "Solve the problem that Bode Plot cannot control sdg1000”. I do have a SDG1062X, so I’m up for a firmware update.
Another thing in the manual that does not add up:
Again...
The X2 is whereever you set it up. So it can also be on the left side. The same problem is with the Y1/2.
Contradictory findings:
Either the manual is wrong or the scope shows wrong values. I can only count like a few dozent of points.
The timebase also does not show all the time 50Mpts if you zoom out its sometimes 20 or 40 Mpts.
Another thing in the manual that does not add up:
Again...
The X2 is whereever you set it up. So it can also be on the left side. The same problem is with the Y1/2.
I take "left (default)" to mean that by default -- i.e. before you set it up differently -- X1 is on the left. Makes sense to me?
Contradictory findings:
Either the manual is wrong or the scope shows wrong values. I can only count like a few dozent of points.
The timebase also does not show all the time 50Mpts if you zoom out its sometimes 20 or 40 Mpts.
Should be exactly 20 points, right? 200 ns total sweep time, 100 MSa/s, so 20 Samples in 200 ns. You can see the individual data points when you switch the display mode to "Dot".
Did you acquire that data with a much slower time base, then stop and zoom in? In that case, the number of number of samples indicated in the info box might be the number of samples acquired in the sweep, rather than the number of samples shown on-screen at the moment? (I don't have access to my scope at the moment.) The manual would be incorrect in that case.
If the above hypothesis is right, I would probably prefer the scope to behave like stated in the manual, i.e. always tell me how many data points are behind the trace I see on-screen at the moment. In which case this would be a bug or improvement request.
Contradictory findings:
Either the manual is wrong or the scope shows wrong values. I can only count like a few dozent of points.
The timebase also does not show all the time 50Mpts if you zoom out its sometimes 20 or 40 Mpts.
It means left as being first on the time axis when doing subtraction. Diff will be X1-X2.
If you set X1 left and x2 right, diff will be 10 ns. If you set them the other way around then it will be 10ns.
X1-X2
It means left as being first on the time axis when doing subtraction. Diff will be X1-X2.
If you set X1 left and x2 right, diff will be 10 ns. If you set them the other way around then it will be -10ns.
X1-X2You are dead wrong! It gives -10ns. Even more, when X1 is sometimes on the left, and sometimes on the right, there is a huge risk of confusion, which really bothers me, as electronics can be confusing enough already.
This is not meant to be rude: but i really get frustrated of people saying things that are wrong with an quite a high assurance (in general). Arent we all interested in having a good product?
And for instance, with 2 ch on as you go through timebases once you reach 50Mpts, it will start alternating between 40 and 50 MPts.
I'm guessing you know why but he doesn't understand that if you multiply time on screen with sampling rate you get what sample numbers are possible....
Off course it is meant to be rude... The hint is in a tone and actual rude words you use...
Read occasionally your own signature...
Hint it was a typo... I wasn't wearing glases and didn't notice there is no minus sign.. Fixed now.
And for instance, with 2 ch on as you go through timebases once you reach 50Mpts, it will start alternating between 40 and 50 MPts.
I'm guessing you know why but he doesn't understand that if you multiply time on screen with sampling rate you get what sample numbers are possible....
I can proove you wrong again:
at 20ms/div i got 20Mpts, but above and below i get 50Mpts... (see attached setup)
Are talking about me not understanding? I might miss some things, as i have a few projects ongoing, but if one is able to explain it, i will quickly grasp it.
Off course it is meant to be rude... The hint is in a tone and actual rude words you use...
Read occasionally your own signature...
Hint it was a typo... I wasn't wearing glases and didn't notice there is no minus sign.. Fixed now.You may have gotten that tone wrong. But what is the actual "rude" word? I just expressed my feelings, and just why its is so.
If you have made a typo, it should be clear, that this sentence does not apply anymore, and there is no need of further discussion...