¿ªÔÆÌåÓý

"CALIBRATE above 5.34GHz" throws a "Signal level too low or not on frequency" error #bug_report


 

I just purchased a tinySA from one of the vendors listed at tinysa.org. When running the "CALIBRATE above 5.34GHz", the test throws a "Signal level too low or not on frequency" error.
?
"CALIBRATE 100kHz to 5.34GHz" passes.
?
Did Config/Clear Config/Config/calibration several times using both provided leads, resulting in same error when calibrating above 5.34GHz.
?
Version: tinySA4_v1.4-40-g2f63e1c
Build Time: Jan 13 2023 - 17:56:59
HW Version: V0.4.5.1 (167)
?
Any ideas on how to proceed prior to returning it to the vendor?


 

Did you input a 5.34GHz signal between -50 and -10dBm when calibrating above 5.34GHz?
--
For more info on the tinySA go to https://tinysa.org/wiki/


 
Edited

Forgot to mention this wiki entry that explains how calibration above 5.34GHz is done:?
--
For more info on the tinySA go to https://tinysa.org/wiki/


 

Hi Erik

On a similar theme; I do not have a 5,4GHz source, so is there a way of manually entering a cal value so as to smooth out the step at 5.4GHz?
I realise that the calibration would not be accurate, but I suspect that it would be closer than with the step, particularly around the transition point.

73
Jeff g8HUL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Erik Kaashoek
Sent: 18 January 2023 06:33
To: [email protected]
Subject: Re: [tinysa] "CALIBRATE above 5.34GHz" throws a "Signal level too low or not on frequency" error #bug_report

Forgot to mention this wiki entry that explains how calibration above 5.34GHz is done:
--

For more info on the tinySA go to


 

There is already a default value set to minimize the step when transitioning to harmonic mode but due to manufacturing tolerances this step is not equal for all tinySA Ultra.
The uncertainty is expected to be below +/- 5dB
If you have done a normal level calibration and you have a calibrated or known source above 5.34 GHz you can manually do the calibration by measuring the know source and changing the value of?
leveloffset harmonic
until the measured value is equal to the known output power of the source.

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


 

Thanks Erik

I assume that leveloffset harmonic is accessible from the console commands?

73
Jeff G8HUL

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Erik Kaashoek
Sent: 18 January 2023 09:19
To: [email protected]
Subject: Re: [tinysa] "CALIBRATE above 5.34GHz" throws a "Signal level too low or not on frequency" error #bug_report

There is already a default value set to minimize the step when transitioning to harmonic mode but due to manufacturing tolerances this step is not equal for all tinySA Ultra.
The uncertainty is expected to be below +/- 5dB If you have done a normal level calibration and you have a calibrated or known source above 5.34 GHz you can manually do the calibration by measuring the know source and changing the value of leveloffset harmonic until the measured value is equal to the known output power of the source.

--

For more info on the tinySA go to


 

Hi Erik.

How accurate must? the frequency? be?

I inject a 5.3420 (that's what my source steps manages) and abt.-20 dbm, and still get the 'Signal level too low or not on frequency'.


TIA??? Joe.


 

Unfortunately it has to be very accurate, within 1 kHz,
See?
Let me see if there is a possibility to relax this requirement.
--
For more info on the tinySA go to https://tinysa.org/wiki/


 

On Wed, Jan 18, 2023 at 01:21 AM, G8HUL wrote:
I assume that leveloffset harmonic is accessible from the console commands?
Yes
?
--
For more info on the tinySA go to https://tinysa.org/wiki/


 

Thanks Erik

Jeff

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Erik Kaashoek
Sent: 18 January 2023 12:12
To: [email protected]
Subject: Re: [tinysa] "CALIBRATE above 5.34GHz" throws a "Signal level too low or not on frequency" error #bug_report

On Wed, Jan 18, 2023 at 01:21 AM, G8HUL wrote:


I assume that leveloffset harmonic is accessible from the console commands?

Yes

--

For more info on the tinySA go to


 

Hi Erik,

I missed that one part in the tinysa.org wiki. Thanks. Unfortunately, I don't have an accurate 5.34GHz source. I can work with just the initial calibration and lower frequencies available.

I appreciate the information. Thanks again.


 

I've updated this page:?
to include a manual method to calibrate the harmonic jump in case you have a generator at 5.34GHz with lesser frequency resolution.
Can you check if the described steps make sense?
--
For more info on the tinySA go to https://tinysa.org/wiki/


 

¿ªÔÆÌåÓý

Hi Joe

You already got an answer from Eric, as the frequency must be 5.34GHz within 1KHz. However, the predefined harmonic offset is after a firmware update set to 10.5 and is not far away to what is created during the calibration above 5.34GHz, so is not essential except you want to measure above 5.35GHz with best possible accuracy.
It has no impact on measurements below 5.34GHz. For my two TinySA Ultra the harmonic offset is 9.1 for the unit (my master unit) I used for creating the correction table embedded in the latest firmware 1.4-40, and for the other unit 9.4 leading to an error of 1.4dB for the one with 9.1 and 1.1dB for the unit with 9.4. It also requires that the frequency adjustment is made to obtain the TinySA ULTRA can measure with said 1KHz accuracy.

However, there is a simple work around as if you enable ultra mode as choose center frequency 5.34GHz and span 100MHz. Then you apply a signal from a signal generator on one half or one third frequency, and tune the signal frequency so you see a signal 10MHz lower=5.33GHz and 10MHz higher 5.35GHz. The levels shall be equal on either side of 5.35GHz and if not the tune the leveloffset harmonic via a terminal command e.g. change the leveloffset harmonic from 10.5 to 10 as a start, and see if that was in the right direct for the level at 5.35GHz. The level at 5.33GHz does not change.
Keep the signal generator level low so you have about 20dB from noise floor to marker level above at 5.35GHz not to provide too high an input signal. ?Remember to issue the terminal command saveconfig when done and you are satisfied.
This procedure is not requiring to find the frequency correction figure, it just mean that the marker frequency is not 100% exact with respect to frequency.
I just updated both my units to firmware 1.4-40 and the master unit deviated +0.2dB between 5.33 and 5.35GHz and the other by +0.3dB so the leveloffset harmonic figure could be reduced from 9.1 to 8,9 and the other from 9.4 to 9.1.
But I will not do so because such small deviations are not relevant as what is 0.2dB amongst friend
?

Kind regards Kurt ???????

?

Fra: [email protected] <[email protected]> P? vegne af josephlevy via groups.io
Sendt: 18. januar 2023 12:36
Til: [email protected]
Emne: Re: [tinysa] "CALIBRATE above 5.34GHz" throws a "Signal level too low or not on frequency" error #bug_report

?

Hi Erik.

How accurate must? the frequency? be?

I inject a 5.3420 (that's what my source steps manages) and abt.-20 dbm, and still get the 'Signal level too low or not on frequency'.


TIA??? Joe.


 

¿ªÔÆÌåÓý

Hi Joe

One detail I forgot to mention. In config set repeat to X10 to stabilized the marker level fluctuation

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af josephlevy via groups.io
Sendt: 18. januar 2023 12:36
Til: [email protected]
Emne: Re: [tinysa] "CALIBRATE above 5.34GHz" throws a "Signal level too low or not on frequency" error #bug_report

?

Hi Erik.

How accurate must? the frequency? be?

I inject a 5.3420 (that's what my source steps manages) and abt.-20 dbm, and still get the 'Signal level too low or not on frequency'.


TIA??? Joe.


 

Hi Erik and Kurt
Thanks for the more 'manual' level calib.
Certainly brings back memories of 'old time...'
Will try it (ie.? play with) tomorrow.
???? Be safe???? Joe


 

Using the 10Mhz cal output and one of the cheap Chinese MAX2870 PLL's sold at the different places (Amazon link only to show the model) modified to accept an external clock of 10Mhz gives me a 5.34Ghz signal with a frequency offset over a GPS of 430hz after a 20 min warm up of both, the generator and the TinySA ultra
I had to amplify the 10Mhz signal by 35db since the PLL needs between 0 and 10dbm clock but gain is cheap. So, if someone has one of those, it can easy be done even without having a GPS for accuracy. In order for it to accept the external input the internal oscillator has to be disabled (removal of a 0 ohm resistor on mine). I use it with an external GPS signal but wanted to see if it could be done using the cal output.

https://www.amazon.com/Generator-Stability-Frequency-MAX2870-23-5%E2%80%916000M/dp/B08YD2F8FF/ref=sr_1_54?crid=3T3X8OPI0FNI6&keywords=max+2871+signal&qid=1674069883&sprefix=max+2871+signal%2Caps%2C83&sr=8-54&ufe=app_do%3Aamzn1.fos.18630bbb-fcbb-42f8-9767-857e17e03685


 

John,

Thanks for the idea for that inexpensive signal generator. I saw Tony Albus demo one last year, but thought it wouldn't be accurate enough. You'd mentioned getting rid of that 0 ohm resistor. Turns out, Tony has a video for doing that to accept a 10 or 25Mhz input from a GPS reference. I have a Leo Bodnar GPS that will inject either frequency, so should be good to go with that.

I'm surprised the PLL required 35db additional gain over what the GPS provided. What did you use to boost the reference input to make the PLL happy?


 

Good morning,
The 35db gain is needed when using the calibrator output of the TinySA as the reverence clock. The calibrator output is around -36dbm and needs to be boosted to a level acceptable for the clock input of the PLL if used that way. Both of my TinySA ultra cal outputs are accurate enough to produce a 5.34Ghz signal that is less than 500hz of frequency. That was the gist of the test to find out if the Tiny can be used instead of a GPS. I wanted to give those that do not have a GPS a solution to generate the required signal. I used a MAR-6 followed by a MAV11 with a 75 ohm pot at the output for level adjustment, Its just 10Mhz, close to DC so it is not that critical and the IC can easy handle the slight mismatch. Of course any combination of MMIC or transistors can be use to amplify the signal. Btw, I installed a switch in my PLL case so it can be switched between internal and external clock. The PLL is accurate over all but there are some division ratios it has problems with and the output frequency is off. I have not experimented how the choice of the clock frequency influences this but, for 5.34Ghz with a 10Mhz GPS clock is is spot on showing 0hz deviation on my HP microwave counter.?

John


 

Thanks John. I appreciate the information.


 

Kurt, thanks for your detailed information. Given what you've said, I'm good with not doing a CAL above 5.34GHz for the time being. Thanks much.