¿ªÔÆÌåÓý

Date

Re: TinySA Ultra

 

I meant inside tinis ultra.


Re: TinySA Ultra

 

Why can't I use the ad8317 logarithmic amplifier IC for calibration?


Re: #tinysa_TinySA2.8_Red_AM_indication

 

Martin, thanks for the clarification.

Erik, you specified the threshold very precisely.
6.22mVp-p (-40dBm), actually displayed as -39dBm:

Single spikes are visible and indicates a red AM.


5.09mVp-p (-42dBm), actually displayed as -41dBm:

No spikes are visible and there is no red AM.
It works, thanks for the advice!

With best regards,


Re: #tinysa What do you use your TinySA for what applications or purposes? #tinysa

 

I mostly try to use it for Phase Noise measurements of my SHF oscillators.

i2NDT Claudio


Re: #tinysa_TinySA2.8_Red_AM_indication

 

On Sun, Mar 5, 2023 at 12:43 AM, Ctoyan Dombarov wrote:
I hope for advice on what can be done to eliminate spikes in a problematic device.
Try to keep the input signal below -40dBm This may solve the problem with the spikes

?
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: #tinysa_TinySA2.8_Red_AM_indication

 

The Tiny SA is only specified for frequencies >100 kHz.

I notice the sweep is from 3 kHz to 103 kHz.

I'm surprised you have been able to obtain a trace that looks anything as good as the ones you have, when used at that low a frequency.

The differences in traces is probably due to minor hardware variations and internal noise generation, as it is being used well outside of its specified range.

I think you just got lucky with one device performing better than the other, due to a variation in manufacturing tolerances.

Regards,

Martin


Re: #tinysa_TinySA2.8_Red_AM_indication

 

Hello

Erik, you're absolutely right.
I have periodic access to the HP3588A spectrum analyzer, on which I tested my HP3314A function generator.


This 3314A served as a source in previous experiments.

Isidro, the characteristics of the input signal are as follows:
The form is sinusoidal
Amplitude 35.6 mVp-p??????
The frequency sweeps linearly and smoothly from 3 kHz to 103 kHz
The sweep time is 1000 seconds.

I did this to more precisely adjust the frequency correction in the low frequency region.
I didn't expect such different behavior from my two instances of tinySA Basic.
I hope for advice on what can be done to eliminate spikes in a problematic device.

With best regards,


Re: TinySA Ultra

 

pe1hwo
?
?12:30 #10318
?
/g/tinysa/message/8079
?prompted, just missed this topic.
?yes it works, thanks Erik Kaashoek.
9


Re: #tinysa_TinySA2.8_Red_AM_indication

 

He is measuring the maxhold of a frequency sweep to try to see the flatness of the level measurement over frequency
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: TinySA Ultra

 

The correction tables are generic for all same model tinySA and may improve over time. Unless you have created your own correction tables, you should never need to save/restore them over a FW update
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: #tinysa_TinySA2.8_Red_AM_indication

 

What are the characteristics of the input signal?
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: TinySA Ultra

 

Depth error is a warning that with the currently requested output levels there is insufficient headroom to perform the requested AM modulation.
The device is not faulty but you are running into a limitation.
Try to reduce or increase the output level and see if the warning disappears
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: #tinysa_TinySA2.8_Red_AM_indication

 

¿ªÔÆÌåÓý

Hello,

I don't have a clue what you try to measure or demonstrate.

I can't identify any signal.

Can you please tell us what signal you measure and what you expect?


All the Best,

Isidro


Am 04.03.2023 um 23:12 schrieb Ctoyan Dombarov:

The measurements continued. 1 swiping cycle of source took 1000 seconds.
Accumulated 4 cycles:


Re: #tinysa_TinySA2.8_Red_AM_indication

 

The measurements continued. 1 swiping cycle of source took 1000 seconds.
Accumulated 4 cycles:


Re: TinySA Ultra

 

Thank you. I seem to have missed this thread.
There was a question on correction. Is it worth using the previously recorded correction factors in the new firmware?


Re: TinySA Ultra

 


Re: TinySA Ultra

 

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 0 10000 14,2? ? ? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 1 40000 9,5? ? ? ? ? ? ??

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 2 100000 7,6? ? ? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 3 300000 3,8? ? ? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 4 500000 1,5? ? ? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 5 900000 0,1? ? ? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 6 4000000 0,3? ? ? ? ? ??

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 7 6000000 0.0? ? ? ? ? ??

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 8 30000000 0.0? ? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 9 90000000 -0,8? ? ? ? ??

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 10 210000000 0,7? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 11 300000000 0,4? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 12 380000000 1,4? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 13 510000000 1,0? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 14 600000000 0,8? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 15 690000000 0,7? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 16 780000000 2,6? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 17 810000000 5.2? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 18 820000000 6,9? ? ? ? ?

§Ü§à§â§â§Ö§Ü§è§Ú§ñ §ß§Ú§Ù§Ü§Ñ§ñ 19 830000000 9,5? ? ? ? ?
Does it make sense to keep it?
these corrections changed with the latest firmware, I tried to change the correction to the previously saved one, I did not notice any difference in the readings.


Re: #tinysa_TinySA2.8_Red_AM_indication

 

Bit better, but:


TinySA Ultra

 

What means: DEPTH ERROR?
Modulation works but writes this error
this error was at the time of purchase.
you said that the device is calibrated and corrected in production.
but as soon as I received the device, I saved the correction and also made a dump.
here I met a faulty LNA in the topic there the same correction values ??\u200b\u200bthat I had.


Re: #tinysa_TinySA2.8_Red_AM_indication

 

Can you test the tnySA Basic with setting display/sweep accuracy/presice
Hopefully the spikes will be gone
--
For more info on the tinySA go to https://tinysa.org/wiki/