开云体育

Date

Re: Signal level too low #ultra

 

I think (I may be wrong, as a beginner) that the switch is for IN/OUT. If that is the case, I can replicate the 10dB error by doing the reverse: generate a signal with the Ultra and read it on tinySA. At [email protected],?tinySA reads -27dBm. Using the CAL output @10MHz I see -34dBm on tinySA.


Re: Signal level too low #ultra

 

Is it the part market A79? What kind o chip is this?


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

 

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


Re: Signal level too low #ultra

 

I don't even know what the switch is. I do have a hot air station and basic skills (THT).
Which part is the switch on the board?


Re: Signal level too low #ultra

 

This confirms the input switch has too low impedance.
It is possible to replace the switch?
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: Signal level too low #ultra

 

TinySA @-7dB is ~780mVpp measured by the scope (high impedance, direct cable, 1X).
Same is 300mVpp with a 50ohm BNC terminator.
R44: ~80-90mVpp
C98: ~75-85mVpp


Re: Signal level too low #ultra

 

If the input switch acts as a low impedance load the level measured at the input drops
Please measure the output level of the tinySA when set to -7dB.
This should be twice 280mVpp
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: Signal level too low #ultra

 

It is 120mVpp at the entry point too, before anything else, so that is what the scope is measuring. I used that as a "reference".


Re: Signal level too low #ultra

 

My mistake
Input level at -7 dBm should be 280mVpp
Input switch seems broken

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


Re: Signal level too low #ultra

 

Also measure either side of R44, close to the mixer
--
For more info on the tinySA go to https://tinysa.org/wiki/


Re: Signal level too low #ultra

 

The input switch seems ok
Lift the large shield between the two sma connectors?
Set LEVEL/ATTENTION to zero
With same input signal measure the level at either side of C98

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


Re: Signal level too low #ultra

 

Hello, thank you for the response.

At 10MHz@-7dBm?output from tinySA, I get the following data:

- level indicated by Ultra: -17dBm
- input pin ~120mVpp
- C58 ~120mVpp
- C24 ~100mVpp


Re: Signal level too low #ultra

 

Do you have a scope?

If yes, can you input a 10MHz signal between -20dBm and 0dBm (such that it is well visible on your scope), you can use the tinySA to generate such a signal?
Remove carefully the cover close to the RF connector
Switch on the tinySA Ultra in default settings (0-800MHz) and measure the signal level at C58 and C24. (either side of the capacitor is OK)
The levels should be fairly close.
If not, the input switch is not working correctly
--
For more info on the tinySA go to https://tinysa.org/wiki/


Signal level too low #ultra

 

Hello,

I've got a tinySA Ultra in December 2022 and all was good (tests & calibration at least). I also have a tinySA non-ultra.
Yesterday while playing around, I've noticed that the signal level indicated by the Ultra is lower by about 10dB compared to the other.

I tried to do a self-test and level calibration and both failed (pictures attached).

I've cleared configuration and disabled "save config" in "presets" turned off and on (after a while as instructed by the seller) and measured the 30MHz CAL output signal which stays at ~-45dBm compared to the expected -35dBm. Measured the CAL signal with the other tinySA and it is around -35dBm so the output is good. Third picture is the CAL signal as measured by Ultra.
Is there anything else that can be done in terms of software/configuration or something is broken in hardware?
The system itself kinda works, but all signals are lower.



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

 

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?


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

 

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


Re: Linux Mint USB #tinysa

 

开云体育

Are you in the dialout group? The error suggests you haven't got permissions to the device...

Good Luck!

Paul

On 1/17/23 23:14, Ed Vignati wrote:

Thanks Jim, I did that, the program opens but won't connect to the TinySA.

I get this in the terminal window

2023-01-18 02:08:23,923 - TinySASaver.TinySASaver - ERROR - Tried to open /dev/ttyACM0 and failed: [Errno 13] could not open port /dev/ttyACM0: [Errno 13] Permission denied: '/dev/ttyACM0'

For some reason in the TinySA program the USB port is /dev/ttyACM0 but there is no communication with the unit and I did rescan and I get /dev/ttyACM0 again no communication when I press Connect.

I have the TinySA Ultra on the way from RL Electronics and would like for that to work.

Thanks Ed kj4fgi

On Tue, Jan 17, 2023 at 12:30 AM Jim Allyn - N7JA <jim@...> wrote:
I am able to use both my tinySA and my tinySA Ultra with Linux Mint 20.3 Cinnamon and tinySA-saver 0.2.2.? Are you using the latest version of tinySA-saver from github?



I have heard some have had problems connecting with USB3, but USB2 works OK.? If you have problems with one, you might try the other.? Try hitting the rescan button if saver doesn't see your tinySA.

I hadn't used tinySA-saver in some time and just installed the latest version recently when I got the Ultra.? I used

git clone

in a terminal to download, then used cd to switch to the newly created folder and followed the directions for Ubuntu in the README.MD file, except that I just used python3 where the instructions specified python3.7 since Mint 20.3 is using python 3.8.10 and will use that automatically when given the command python3.? Python3 and pip were already installed, so I ignored that part of the instructions to install those.


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

 

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


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

 

开云体育

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.


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

 

开云体育

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.