Forums › SM Series Discussions › Meaning of smUncalData error
- This topic has 8 replies, 2 voices, and was last updated 3 years ago by
Andrew.
- AuthorPosts
jmatusiakParticipantAnother random batch of values I used was able to get the SM200C to error out with smUncalData.
I am in FREQSWEEP mode with:
* Auto speed
* 900kHz – 6GHz start/stop
* 30kHz RBW
* 100ms period
* Nuttall windowMy app seems to be setting up the device with these settings fine, but when I try to get an FFT sweep, this is the value I get in return after the very first smFinishSweep call. Any ideas? It seems like I can “ignore” it, but should I be worried?
Also, I am still a little confused on the sweepTime option for the smSetSweepCoupling API call. I am setting the start/stop and RBW, is it safe to just pick a super small sweepTime since the system will just pick the fastest time it can based on the RBW/VBW?
AndrewModerator- This reply was modified 3 years ago by
Andrew.
The API picks the maximum sweep time that ensures all configuration is met. That includes RBW/VBW/sweeptime. Setting a small sweep time ensures the minimum sweep time is chosen based on RBW/VBW.
I would ignore the uncal warning flag for now if it’s being thrown on the first sweep. I suspect it’s being set erroneously. I was able to reproduce this using your settings. The uncal data flag usually indicates network data loss, I’m going to need to investigate further to determine why it’s returning this warning for this configuration.
Andrew
jmatusiakParticipantOK, makes sense on the sweeptime. Thank you.
Maybe it is an issue with my custom RX software, but when I get the uncal data error, I get pretty much garbage samples, so I can’t use it. My problem is that by the time a user has hit go to start receiving samples, the SH has been setup and they think that everything is good, yet I don’t know that I will have a problem until I try to do the very first receive. I am thinking that I might have to figure out some bounds that I don’t let a user work outside of so they don’t get into this state.
AndrewModerator- This reply was modified 3 years ago by
Andrew.
Thanks for the follow up. Can you throw away the first sweep if it gives you this error? Maybe even perform a single sweep after configuration for the purpose of discarding it? Looking into it now.
AndrewModeratorI have been unsuccessful reproducing the issue with the API. Can you potentially put together a short script that reproduces the problem on your end?
I’m also now considering that you are in fact seeing networked data loss, and that could be tied to your specific hardware configuration and/or software.
While I do see the issue in Spike, I only see it ~1 out of 20 or so reconfigures, and the sweep is not corrupted, which led me to believe it was an erroneous warning.
You also have my email if you wish to communicate via email. It is easier to share pictures and code via email moving forward.
Andrew
jmatusiakParticipantIt doesn’t recover even after that first acquisition.
Here is an additional piece of information I just discovered, my two two SM200C are actually acting differently. The one that I referenced above was running firmware v3.3.1. The other one I have (which I just discovered isn’t showing the uncal issue) is running v5.5.3. Maybe that has something to do with it…
I am going to try to update the firmware on them both, but first I need to get a hold of a windows machine since it doesn’t look like you have a linux firmware updater tool.
AndrewModeratorThat’s correct, the FW updater can only be run on Windows. You will need to install the Spike software on the Windows machine to ensure the USB driver is installed. The SM200C must be connected to the PC via USB for the FW update.
Andrew
jmatusiakParticipantOK, the update to 7.7.1 on my “bad” SM200C seems to have fixed the issue. Thanks for the feedback.
AndrewModeratorThanks for the update.
I’m glad this resolved the issue.
- This reply was modified 3 years ago by
- AuthorPosts
You must be logged in to reply to this topic.