开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
Date
Re: TinySA: Internally generated spurious signals
Above 1GHz RF is like water. It flows? through every hole Hiding with the spur removal does not work as the spur removal removes spurs that do not actually exist but this 48MHz harmonic leakage is an
By Erik Kaashoek · #672 ·
Re: TinySA: Internally generated spurious signals
The TinySA doesn't use the ADF4350, it uses a couple of Si4432's.
By OneOfEleven · #671 ·
Re: TinySA: Internally generated spurious signals
Regarding ADF4351, would the Tninsa perform better with these rather than adf4350? Steve L ? G7PSZ
By Stephen Laurence · #670 ·
Re: TinySA: Internally generated spurious signals
Now the 64,000 dollar question. What could be done to suppress them? Either hide them with software tricks, such as the spur-removal option, but that might leave “holes” in the spectrum, or
By Stephen Laurence · #669 ·
Re: TinySA: Internally generated spurious signals
Yes the unit certainly has limitations, though for the price is not to bad really. Here's a -4dBm carrier from an ADF4351 at 50MHz. The TinySA shows a wide flat top and noise floor of only 45dB down
By OneOfEleven · #668 ·
Re: TinySA: Internally generated spurious signals
Done, The 4.8MHz is indeed present.
By Erik Kaashoek · #667 ·
Re: TinySA: Internally generated spurious signals
Erik, On my tinySA there also appears to be a sub-harmonic of the 48MHz clk at 4.8MHz.? Possibly a divide by 10 output? LOW and HIGH INPUTS terminated in 50ohm loads. Your explanation and an
By hwalker · #666 ·
Re: TinySA: Internally generated spurious signals
These are 48MHz harmonics generated by the MCU. For now all tinySA will show them at 48, 96, 144, 192 and 240 MHz
By Erik Kaashoek · #665 ·
TinySA: Internally generated spurious signals
Have I just been unlucky and got a bad unit, or does everyone suffer spurious signals on their TinySA? I see specific signals at 144.20MHz, 192.15MHz, and 240.19MHz. They are unstable, and wander
By g4jmm2006 · #664 ·
Re: Identifying which serial port the tinySA is attached to
Yes, to be done
By Erik Kaashoek · #663 ·
Re: Identifying which serial port the tinySA is attached to
Very good. Could the firmware not have used the unique CPU serial number to create the device ID ?
By OneOfEleven · #662 ·
Re: Sources of interference
You can measure the field strength of a source in dBuV/m if you change display units to dBuV and use a transducer calibrated in dB/m.? At a single frequency you can enter the tranducer factor (plus
By hwalker · #661 ·
Identifying which serial port the tinySA is attached to
The tinySA uses the same VID/PID as the NanoVNA so if you are writing a script or program to communicate with the tinySA, and both a NanoVNA and tinySA are connected to your computer at the same time,
By hwalker · #660 ·
Re: Sources of interference
I've already used mine for tracking power line noise t 300mhz using a small yagi for that band. With an untuned amplified .3M untuned HF loop I"ve tracked all sorts of items emitting significant
By ajparent1/kb1gmx · #659 ·
Re: Jumping base line
Besides the faster speed and unlimited points, the tinySA 'scanraw ' command transfers corrected data - unlike the similar command on the NanoVNA which transfers raw data and requires you to
By hwalker · #658 ·
Re: Sources of interference
Don't forget to check PC supplies, The worst I found was a PICO supply.
By Erik Kaashoek · #657 ·
Sources of interference
A very useful use of the TinySA is to track down sources of interference. The horrors of today's unfiltered unscreened (and often unsafe - we had one leave burn marks all up our lounge wall after it
By OneOfEleven · #656 ·
Re: Jumping base line
Make sure you use the "scanraw" command i.s.o scan or sweep as scanraw can do unlimited points and sends data in binary, much faster
By Erik Kaashoek · #655 ·
Re: frequency correction #tinysa
I think so.
By Erik Kaashoek · #654 ·
Re: frequency correction #tinysa
Erik, Is that the only change in FW release v1.0-52? - Herb
By hwalker · #653 ·