¿ªÔÆÌåÓý

  1. Tinysa
  2. Topics

TinySA Ultra fails self test 3, 4, 7, 11, 14

 

New to the TinySA, so hoping I'm in the right place to ask support questions, if not please let me know where to ask (thanks in advance). Recent purchase of a TinaSA Ultra, cal and self test worked as advertised. Started using to find transmissions in the 136Mhz to 174Mhz, and was fine. Showed a friend the self test a couple weeks later, and it failed tests 3, 4, 7, 11, and 14. Ran cal, fails to complete. Tried different cables, same result. Any help would be appreciated.

Calibrate fail and self test fail images
 

You may have either blown the internal attenuator or the input switch
Is the tinySA completely deaf? Connect the telescopic antenna and test with and without LNA enabled if you can see any signals
--
For more info on the tinySA go to https://tinysa.org/wiki/
 

Yes, it's displaying transmissions, but also tested from my own radio with LNA enabled and disabled since I live in a remote rural area (not a lot around) to make sure and it spiked up to -20dbm.

Thanks?for the quick response

On Wed, Jan 3, 2024 at 2:27?PM Erik Kaashoek <erik@...> wrote:
You may have either blown the internal attenuator or the input switch
Is the tinySA completely deaf? Connect the telescopic antenna and test with and without LNA enabled if you can see any signals
--
For more info on the tinySA go to

 

Please enable the 30MHz call output and connect to input
What level do you see with and without LNA?
--
For more info on the tinySA go to https://tinysa.org/wiki/
 

it was 64.0dbm with LNA disabled, and 66.4dbm with LNA enabled

thanks
 

If you have a scope you can watch the level of the 30MHz call output, it should be around -35.6dBm.
If the output level is correct then it seems like the input switch is blown. See "The input switch is blown. Where can I find a new switch?" in the tinySA wiki
--
For more info on the tinySA go to https://tinysa.org/wiki/
 

Don't have access to an oscilloscope, so will work on ordering and replacing the input switch and see if that fixes it.

Thanks again for the help.

1 - 7 of 7