¿ªÔÆÌåÓý

New FW release: Improved spur avoidance


 

New FW release
Version v1.0-67

Changes:
- Updated spur avoidance table

After receiving some feedback about possible spurs I made an update of the spur avoidance table
This update could make the scanning a little bit slower.


 

On Fri, Sep 4, 2020 at 04:06 AM, Erik Kaashoek wrote:
New FW release
Version v1.0-67

Changes:
- Updated spur avoidance table

After receiving some feedback about possible spurs I made an update of the spur avoidance table
This update could make the scanning a little bit slower.
1. The new build is showing up in the status panel and version screen as 1.0-66.? The version screen shows the correct build date.?

2. If an actual signal is measured that is in the spur avoidance table, does avoidance get cancelled if the level is above a predetermined level for the spur?

3. I assume the MCU clock related signals are not considered spurs as I didn't see any change from the previous version.

- Herb


 

On Fri, Sep 4, 2020 at 05:25 AM, hwalker wrote:
1. The new build is showing up in the status panel and version screen as 1.0-66.? The version screen shows the correct build date.?
Argh... Forgot to clean the project before building
2. If an actual signal is measured that is in the spur avoidance table, does avoidance get cancelled if the level is above a predetermined level for the spur?
The avoidance algorithm knows when certain combinations of internal frequencies can lead to spurs and choses alternate combination to avoid the otherwise substantial spur. This mechanism is totally transparent and has (should have) no impact on the measurement performance. So it does NOT mask small signals at certain frequencies. It avoid spurs are created.
3. I assume the MCU clock related signals are not considered spurs as I didn't see any change from the previous version.
Indeed, no real signal are impacted in any way, so also not the MCU related signals.