TinySA Ultra launched

[DaneLaw]

I vote @shapirus reports the bug, he found it, I was just confirming it.

The creator Erik Kaashoeck is a regular user here on EEVblog, and likely quite ajour with this thread.

Erik is user erikka (#130).

[KungFuJosh]

I vote @shapirus reports the bug, he found it, I was just confirming it.

The creator Erik Kaashoeck is a regular user here on EEVblog, and likely quite ajour with this thread.

Erik is user erikka (#130).

Even better! No effort bug reporting. 😉

[shapirus]

I vote @shapirus reports the bug, he found it, I was just confirming it.

Not via google groups, sorry. Not gonna go through the associated setup hassle.

But since the author is registered on this forum, let's mention him.

@erikka , do you consider this one a bug, a glitch, or a feature? :)

[KungFuJosh]

There's an option in the config settings for better accuracy OR cleaner signal. The glitches exist either way.

[KungFuJosh]

bug, a glitch, or a feature?

[erikka]

The tinySA does not do a continuous sweep but sweeps in discrete steps with possible silence in between. Set the scan speed slow and you will see the step

[KungFuJosh]

The tinySA does not do a continuous sweep but sweeps in discrete steps with possible silence in between. Set the scan speed slow and you will see the step

What are the random frequencies that appear between steps?

[erikka]

PLL's locking after the step
I do not mute the output as this would slow down the maximum sweep speed and created larger gaps which you will hear as stronger clicks.
Any stepwise sweep will always have some form of artifacts

Can you explain why these may be a problem?
Or is this just curiosity because of what you saw on the DSO?

[KungFuJosh]

For me, just curiosity.

[shapirus]

More like a cosmetic issue, having all those random waveforms displayed between steps, especially since it's not the primary function of this device.

It would be nice if it could be fixed without compromising other functionality, but otherwise no big deal.