Forums › BB Series Discussions › BB60C Overflow
- This topic has 4 replies, 2 voices, and was last updated 6 years, 7 months ago by Justin Crooks.
When I use sweep mode in my application i get a strange reaction to overload.
It looks like result of bbFetchTrace_32f returns the previous value of bbADCOverflow.
I look at spike software and got a similar behavior in manual work mode (‘single’ button on panel).
In FM band I select Gain 2, Att 0 and get overflow.
First time when i select 10 dB att on the spectrum overflow disappears but label of оverflow is still visible.The next time you press the button ‘single’ label of оverflow disappears
Justin CrooksModeratorJustin Crooks July 29, 2016 at 10:22 am
The ADC overflow flag is only cleared immediately after reporting it. When you are doing single sweep, with an overflow condition (e.g. gain 2 atten 0), it reports the overflow, clears the flag, and then immediately sets the flag again (overflow condition still present). You set the attenuator to 10 dB (no more overflow), sweep, and it reports there was an overflow condition since the last time it was reported. But the next sweep reports no overflow.
This is the expected behavior. If this is not what you are seeing, let me know.
Answer the question then.
Does the status of overflow characterizes the data that was calculated spectrum?
I put a delay of one second after setting the attenuator.
However next call bbFetchTrace_32f function still returns the overflow.
And as you write after attenuator you mast twice call bbFetchTrace_32 to find out what went overflow.
By the way, function bbFetchRaw working correctly.
After settings att next call bbFetchRaw returns no overflow.
Justin CrooksModeratorJustin Crooks August 1, 2016 at 1:03 pm
Interesting. It is probably safe to ignore the first overflow flag after a settings change from an overflow condition. Subsequent overflow flags should be treated as valid.
You must be logged in to reply to this topic.