Products > Test Equipment
Siglent SDS2000X Plus - Bugs / Missing Features / Feature Requests
Martin72:
--- Quote ---Why do you think triggering is related to the issue?
--- End quote ---
I never got the I²C signal from the Batronix demo board to trigger properly.
But when I stopped and scrolled through the table, the data was visible without dropouts.
MathWizard:
Well 1 thing that's going bad, is my new probes that came with the sds2204x+. I really haven't used the scope that much, but already, my green probe gets attenuated maybe 20-30% when sitting in certain positions. It seems to be at the end where the probe meets the coax cable.
Now the same thing happened to my other Siglent probe sets, and similar ones I bought online once. But none as quick as the new problem one. I try to be careful with them, so IDK what's happened.
How hard is it to repair these, do you need some special tools and parts? Maybe it's not worth it, or too hard to do it right.
Any other uses for the cable ? I know it's not regular 50R coax.
tautech:
--- Quote from: Slartibartfast on December 03, 2023, 09:26:14 pm ---Why do you think triggering is related to the issue?
--- End quote ---
The spikes on Ch2 here:
--- Quote ---From my point of view, there are traces that show signals from a specific time window of 200µs at some instance in time. This acquired data is what the decoder has to work on. Now, it is clear that if the traces would start right in the middle of an ongoing transmission, the decoder has nothing to sync on at the beginning of the trace, but even then it should resynchronise when it sees START or STOP conditions. But even that is not the case. The trace starts at a time when the bus is idle, and consequently the decoder start decoding porperly, and then suddenly looses sync. Later in the trace, the decoded information is inconsistent with the traces. This should not happen.
I completely fail to see any connection to the triggering.
--- End quote ---
225us trigger offset is NOT Holdoff !
--- Quote ---Please note I'm not triggering on a bus event, but use normal edge-type triggering.
--- End quote ---
Totally understood and I can see this in the Trigger tab. ;)
Using Holdoff and a Falling Edge for simple decoding illustrations is how I do it too but to trigger on specific bits one must use a decode trigger.
Holdoff is never shown/displayed so set it to a bit longer than a packet and show us the result.
ebastler:
But acquisition is stopped. The data signal is right there with all the bits, and a clean-looking clock too. Why can't it be decoded? I also fail to see how triggering could get in the way.
tautech:
--- Quote from: MathWizard on December 03, 2023, 09:57:06 pm ---Well 1 thing that's going bad, is my new probes that came with the sds2204x+. I really haven't used the scope that much, but already, my green probe gets attenuated maybe 20-30% when sitting in certain positions. It seems to be at the end where the probe meets the coax cable.
Now the same thing happened to my other Siglent probe sets, and similar ones I bought online once. But none as quick as the new problem one. I try to be careful with them, so IDK what's happened.
How hard is it to repair these, do you need some special tools and parts? Maybe it's not worth it, or too hard to do it right.
Any other uses for the cable ? I know it's not regular 50R coax.
--- End quote ---
P215 probes ?
Claim warranty. Probes = 1 year.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version