开云体育

Easy to build if you have:
- space
- power
- money
May I suggest you open your tinySA and try to find space for the 3 amplifiers stages required to get some dynamic range?.
And try to find a component configuration that is stable, even with the huge gain of the cascaded amplifiers.
--

If they are so easy to build, I would think it would not be a burden, and everything would be self-contained...
regards
Colin

Hi Martin ,
you might look for a Tesla charging in the vicinity.
I had some HF disturbance of off these in the past.

kind Regards

patrick

I have a tiny SA and a TinySA Ultra, and I have also used them to try and track down noise sources.

In my opinion the Tiny SA does not have sufficient sensitivity, for what you are proposing. As Erik says you could use an external pre-amplifier, or an active antenna, which is pretty much the same thing, but it all gets a bit messy if you wish to carry it around.

If you don't have either version, and are now considering buying one, go for the TinySA Ultra, it is definitely worth the additional cost and I would highly recommend it.

The TinySA Ultra can be used with a short whip antenna <30cm, and I've found it to be adequate to locate noise sources by walking around the neighbourhood. As a guide, it has sufficient sensitivity to be able to hear short and medium wave broadcast stations, just using the short whip, but it's not as good as a dedicated portable radio for that purpose.

Mine also works well with a small handheld tuned loop antenna of <0.5m diameter, that I use for direction finding to locate noise sources at a greater distance.

Regards,

Martin

The NF of the tinySA is 28dB so if you adding a cheap 30dB amplifier will be sufficient
For inspiration:?
The tinySA Ultra has an internal LNA with a 4dB NF
--

Hi all. first post from a new member...

I have an RFI problem which is impacting on several HF bands and I'm trying to track down the source. Functionally, a tinySA looks like the right tool, but I'm worried about the sensitivity. I currently have a Xiegu X6100 - which is not a slouch as a receiver - and I've been experimenting using that to track down the noise, but the results are not great. My main rig is an FTdx101D with a doublet at about 30 feet. My RFI source produces peaks of noise one or two kHz wide which wander from side to side by maybe 1kHz - and several of them are sitting just above the bottom of an amateur band - the worst is on about 14.08MHz. On the FTdx101D with the doublet connected, the noise peak reads just over S9. On the X6100 with the doublet connected, it's similar - perhaps slightly weaker, but still an S8/9 signal and well defined.?

I put an HF whip antenna - about 18 inches long, helically wound - onto the X6100 and it barely registers the noise. Since I know that it is there, I can see it on the waterfall, but if you didn't know it was there, you could easily miss it. Hence my concern about the tinySA - how sensitive is it with the telescopic whip that is supplied with it? I need sufficient gain that this signal will show at a decent amplitude with an antenna that I can realistically carry round to seek out the noise source!?

TIA

Martin (G8FXC)

Wiki part on markers is updated as the text was wrong
--

I understand, it's about a black number on a light background. The question is removed.

Hello,
Here:

I can't understand phrase:
"One marker is active and marked with an inverted number."
I have never seen inverted numbers on a marker. In what modes does this happen?
Or does it mean something like "The active marker is marked with a number in an inverted triangle."?

With best regards,

This problem was related to the regional decimal number formatting. The decimal number separator must be a dot and not a comma. Once I changed it, the frequency axis looked fine.

Thanks to Vitor for pointing me in the right direction.

Dieter

Thanks for quick reply!

Thanks. Good remark. It's indeed maximum 290. But there is an option to select less sweep points
--

Better: " As the number of points displayed is 290, when the RBW is too small to cover...."

Hello,
In the

I read the phrase:
The number of points scanned is minimum 290 but when the is too small to cover the selected frequency range with 290 points additional measurements are done and accumulated into the 290 points.
Is the highlighted word correct? According to the specifications of the tinySA3, the word "maximum" is more appropriate.

With best regards,

Thanks!

If you might wish to learn by doing, here is an excellent application.? It's freeware at:

?

????

?

And an excellent tutorial at:

?

????

?

Thanks for this. Looks like a wealth of information!

On Thu, Jan 26, 2023 at 01:40 AM, Vitor Martins Augusto wrote:

Perhaps Eric could include a START/STOP command, so that external software could switch off the screen of the TinySA and stop it doing its own sweeps while being used remotely. The external software would then either reactivate the screen with START or the user would have to switch teh TinySA off and back on.

You can use the pause and resume command. When in pause mode a big green PAUSED text is shown in the status window
?
--

Also, the TinySA will stop his own sweep, when the raw command is sent through the USB/RS232 protocol. Once the raw command finishes its sweep, the TinySA resumes what it was doing. But since my software constantly sends raw commands, the TinySA ends up showing outdated sweeps, when it does not get time to do its own sweep. Also, the use of the raw command will not change the settings for TinySA's own sweep, so you end up seeing something completely weird.

Perhaps Eric could include a START/STOP command, so that external software could switch off the screen of the TinySA and stop it doing its own sweeps while being used remotely. The external software would then either reactivate the screen with START or the user would have to switch teh TinySA off and back on.

Hello,

Please e-mail me directly with problems regarding my software - this group should be use for the TinySA devices only, as per request from Eric, which I respect.

The mentioned problem results from having "," configured as the decimal symbol. Visual Studio is IMHO not coherent regarding the use of regional settings, some functions respect it, some don't. The fix consists in using "." as the decimal symbol.

I will try to fix this in future versions.

Regards,
Vitor

Dieter, try english as? Windows language.

Toni.