- This topic has 3 replies, 4 voices, and was last updated 9 years, 2 months ago by
.
- Posts
Background File: Was wondering if there are any plans to create this feature to allow for creating a baseline of the spectrum (BB60C) with the ability to recall it later and have it displayed on the screen during an ongoing sweep to compare changes from a previous sweep? This would also allow the user to see the additions of new signals from full and any span.
Difference File: Would also be nice to subtract two Background Files to determine what signals are new and what signals have disappeared.
vr
Mike
USSOCOMHi Mike,
We don’t have any immediate plans to implement baseline logging or trace math functionality, but we are aware of the need for it, and believe we will address these points in the future. We appreciate you providing feedback. We keep track of all customer requests.
Currently with the functionality we offer today, depending on your needs, you could use additional trace slots in combination with the max hold functionality to create a baseline, and then disable the update of that trace, creating a sort of background trace. Changing settings will clear the trace though, so it will only work for one setup. Once you have a baseline max held signal, you could then export the trace, and any future traces to do some minor trace math in excel or other similar applications. I realize this is not be the exact functionality you are looking for, but might assist your measurements.
Regards,
A.J.Interesting, I was just about to ask a very similar question. We use external test labs for full EMC chamber testing on our products. We do not have an anechoic chamber in house.
We do have a BB60C and Spike and it would be nice to be able to use it when trying to mitigate problem frequencies that were identified in the outside EMC test lab where we are not paying lots of money per hour.
Say we have an issue at 60 MHz for example. It would be nice to save a trace of the average of the environment in a narrow band around 60 MHz while the DUT of powered off. Then this “quiet” average trace can be set to be subtracted from the real time trace when the DUT is powered on to see how much the DUT is adding. Or another method would be to save an average sweep with the DUT powered on with no mitigations, then subtract that from the real time trace. This would make it really easy to see whether wiring mitigations / ferrites / etc. are helping or not.
Thanks,
-RandyHi Mike/Randy,
For EMC debugging I use average (set to 64 counts) and max hold traces.
I take an ambient capture, then a DUT on, then an ‘improved DUT on’ sweep. There are 6 available traces so this works out quite well.
As AJ has suggested…You’ll find EMC lab’s receivers, with their preselection filters, specific RBWs and defined QuasiPeak, Average and Peak detectors, that you wont reproduce EMC receiver results with a spectrum analyser.
However the BB60C is more than up to the task of EMC debugging.
Feel free to email me directly with some more specifics at
apollyon25 at hotmail dot comI’m more than happy to give you a few things to look at.
What other bits and bobs do you have for EMC?Jared
You must be logged in to reply to this topic.