EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: scopeman on July 11, 2018, 02:13:49 am
-
I have been trying to do a capture/compare of a OOK signal with my SSA3000X. I have the video trigger set at -39dBm and I can capture the signal as Trace "A" and place that in "View" mode. I then selected Trace B in Write mode but when the analyzer triggers it clears the Trace A data display which was "stored" in view mode.
So how do I get the instrument to save the "A" trace whilst storing a trace to compare (or is this a bug?).
Sam
W3OHM
-
Yes it's not entirely intuitive.
The button View could be better named as Save as it stops the sweep and fixes the trace.
Then open another and select the setting you require; Max or Min hold to compare against the saved trace.
Here's a couple of captures as some example.
A on 80 MHz span, 40 MHz CF and captured/frozen
B on 38-42 MHz span.
Video trigger continous running.
-
Try to save both A and B and trigger once and save A then trigger again and save B. You can't do it and max or min hold does not do what I want.
I am trying to capture a 306MHz wireless ceiling fan controller (much like a garage door opener).
As you can see from PNG2 when I trigger from video with trace A in view mode trace B clears trace A even though A was saved in view mode.
If I were to use max or min the pulses would not be shown correctly.
Sam
-
Fairly sure I can do it, I have a 339 MHz garage remote to try it with too but it's the middle of the night so I'll have a go in the morning.
What's important for you on this, code and amplitude ?
-
Yes that is correct. All of the HP analyzers I have worked with save the trace until set to clear write so I think this is a bug and probably an easily squashable one in the firmware!
All the best and thanks for running this down.
Sam
W3OHM
-
While the results I've got don't give the same quality as yours the process of storing an A trace and then capturing a B trace does indeed work.....when you work out now. (never done exactly this before)
The key is working between Trace and Detect UI's after setting Trigger as required.
(https://www.eevblog.com/forum/testgear/siglent-ssa3000x-trace-store-issue-in-video-trigger-mode/?action=dlattach;attach=474146)
My workflow:
Preset to factory default.
Set CF and Span
Set Trigger and Level
View A (capture)
Enable B and set to Detect on B
-
I will have to try this out the next time (soon) when I get back to it.
Thanks,
Sam