Forum Replies Created
- Posts
1) It depends on your setup. Since you mentioned using LTE, there isn’t a real LTE EVM measurement like there is for WLAN or a standard signal carrier modulated signal. LTE does a quick EVM analysis on the MIB and PSS, but these are subcarriers in a very narrow band, and not representative of the full signal bandwidth EVM.
If you wanted to provide a picture of your setup and help making a good EVM measurement, I would recommend reaching out to support@signalhound.com.
2) Not while running LTE. Only in sweep mode. You would have to go back and forth between measurements.
3) There are a number of built in masks, (lower right hand corner in the control panel), but we don’t include any LTE masks. You would have to build your own.
We do not have a generic OFDM demodulation mode in Spike. A common workaround would be to transmit an 802.11a signal with the VSG60 and then demodulate that with the WLAN demod mode in Spike. No licenses required, and it will simulate a 20MHz BW OFDM signal for your amplifier test.
Do you think this would be sufficient?
Thanks for sharing Jason! Cool stuff.
The picture does not seem to be attached/included. Are you able to email us at support?
support@signalhound.com for technical support and inquiries.
sales@signalhound.com for purchasing/quotes/sales.
Regards
Yes the Spike software can be installed on any number of PCs.
Hopefully you can provide more description of what you mean when you say “then the Spike SW does not run on another computer”, that would be helpful. Such as what error messages are you getting? And am I to understand that where the software was working, simply installing the same software on a totally separate PC causes the software to stop working? That doesn’t make much sense to me. Hopefully you can clarify and provide some additional details.
Thanks for calling in today. It was nice talking with you. If you have follow up questions, please email support@signalhound.com or give us a call again.
Andrew
This issue is usually related to graphics drivers. We utilize the GPU to render our application. Updating to the newest version of available graphics drivers typically fixes this issue.
To find the newest driver, you want to either go to the manufacturers drivers page for your specific model number PC, of if you built the PC yourself, find the driver page for your model number GPU. We can also suggest drivers, but you will need to provide the make/model of the PC you are using. If you prefer, you can send that information to us via email at support@signalhound.com.
We look forward to your results/response.
It seems like you are talking about the noise floor of the measurement? If yes, then you can change the noise floor via 2 main ways. You can adjust the RBW. If you change the RBW to 10kHz, that will lower your noise floor by 20dB to 0dBuV. You can also change the sensitivity of the BB60C. If you lower the max input by another 5 dB to 55dBuV it will lower the noise floor by another 5 dBm. Unfortunately at 55dBuV you are at the maximum sensitivity of the BB60C, and won’t be able to lower it more via the max input control. You will need to rely on RBW again.
Can you provide additional clarification? I’m not sure what you mean by “mt db in y axis automatically goes to 20dBuV”.
Hello,
Unfortunately it is not possible to set gain/atten directly in the EMC precompliance mode as you can in the sweep mode, but only indirectly through the “max input” control, which has similar behavior to reference level in sweep mode.
I apologize for the inconvenience.
Hello,
Unfortunately it is not possible to set gain/atten directly in the EMC precompliance mode as you can in the sweep mode, but only indirectly through the “max input” control, which has similar behavior to reference level in sweep mode.
I apologize for the inconvenience.
Thank you for the feature request! I have added it to our customer request log. I will update this thread when we release a version with this feature.
Regards
Michael,
You also emailed us this same question. We have responded via email.
Hi Scott,
I’m sorry I didn’t realize you were also the same person we have been emailing.
I just sent a follow up email mentioning that based on my most recent understanding I don’t think there is an issue with the processing. I think the reason you see the “peak” or “corrupted data” at the 5MS/s rate is that you are centered at 100kHz, and the 0Hz (DC) feedthrough is coming into your spectrum. The filtering in the API is not sharp enough at that sample rate to filter out the 0Hz response. I recommend a post processing filter if you want to remove the 0Hz response, or reducing the sample rate to 2.5MS/s or below such that additional filtering helps remove the 0Hz feedthrough.
Does this sound like an accurate take on the information you have provided? If yes, then I believe the API is likely working nominally on your system.
I look forward to your response.
sreeder,
Have you tested them in your configurations and verified they would not work? I have customers reporting success on the RPi5 under Ubuntu when using the Nvidia aarch64 builds. Both PiOS and Debian are similar enough I would expect them to work.
Hi Miran,
I can reproduce. It looks like this issue was introduced in the most recent version. I already have a fix and it should go out in a release next week. I apologize for the inconvenience.
Here’s a link to the previous version if you want a version that should not contain this bug. You will need to uninstall the newer version manually before installing.
https://signalhound.com/sigdownloads/Spike/Spike(x64)_4_0_12.zip
Thanks as always.
There is now a BB60 Mac ARM API build in the latest SDK release here,
https://signalhound.com/software/signal-hound-software-development-kit-sdk/
Please review the README in the macos_arm folder to understand it’s limitations (same as the Ubuntu aarch64 build).
Zitro,
The device can only be interfaced by one application at a time. Attempting to connect to the device from 2 applications/users simultaneously will cause undefined behavior. I apologize for the inconvenience.
