Keyboard Shortcuts
Likes
- Tinysa
- Messages
Search
Re: tinysa
Scott hunter
with an external ittenuator what is the maximum input the spectrum annalyzer would handle 1dbm or 2 dbm or even lower any chance could u give me a accurate reading ..also did u design this spectrum annalyzer?thanks for replying .. On Wed, 16 Sep 2020, 12:51 Erik Kaashoek, <erik@...> wrote: The input power of the fundamental should be as low as possible to avoid the tinySA generating internal harmonics. But the fundamental should also be so strong the harmonics do not disappear into the noise. |
Re: tinysa
The input power of the fundamental should be as low as possible to avoid the tinySA generating internal harmonics. But the fundamental should also be so strong the harmonics do not disappear into the noise.
In this example:? you see that keeping the fundamental just below -25dBm (with 0dB attenuation, increase attenuation if you increase the level of the fundamental) gives the largest measurement range of observing harmonics. The first example in this video:? shows the measurement of a signal with harmonics where the fundamental is at -25dBm A practical example of measuring the harmonics from an actual transmitter can be found here:? |
Re: Noise factor measurement: Can someone with knowledge review this wiki page?
On Tue, Sep 15, 2020 at 11:55 PM, Bonzo wrote:
For this method of NF measurement it is important that the noise contribution of the DUT isI will adapt the page to use two amplifiers, just like in the Keysight instructions. With one amplifier I did not see the noise increase (unless I added the input resistive termination) so the calculation is wrong. |
Re: Noise factor measurement: Can someone with knowledge review this wiki page?
Hi Erik,
For this method of NF measurement it is important that the noise contribution of the DUT is dominant over the noise of the S.A. itself. One can easily check this in your example by powering off the amplifier. The measured noise level should then significantly drop. Minimum 10 dB, better 20dB. Otherwise the S.A. adds too much noise in this setup and the calculated result is wrong. So this step should be added in the procedure. |
Re: Thank you! And a couple of questions on PC connectivity and upgrade
On Tue, Sep 15, 2020 at 06:02 PM, Ham Radio wrote:
Bernie, ? v0.3 is the production hardware revision.? The beta hardware revision was v0.2. ?- Herb |
Re: Thank you! And a couple of questions on PC connectivity and upgrade
Erik: On the TinySA flash page, when it boots, it says in bold letters ¡°tinySA v0.3¡± |
Re: Tracing interference with the Tiny SA
#tinysa
On Tue, Sep 15, 2020 at 08:56 AM, Martin wrote:
Data over Power line adaptor Is terrible, my neighbours are using them. I had to put chockes over all the mains electricity cables where they enter my home, including the ground cable. ? |
Re: Thank you! And a couple of questions on PC connectivity and upgrade
Try going into the Device Manager window and under View, select "show hidden devices" Then, have a look for any old STM USB or DFU devices and delete them. Now, connect the SA and let Windows detect and re-install the drivers.
On Tuesday, September 15, 2020, 1:04:06 p.m. EDT, Magicbean <smstone@...> wrote:
I have just found it works fine on my other Windows 10 PC. Same TinySA, same TinySA.exe. Odd.
|
Re: Thank you! And a couple of questions on PC connectivity and upgrade
Have you tried accessing the SA via a terminal, like TeraTerm? Does it work?
On Tuesday, September 15, 2020, 12:40:42 p.m. EDT, Magicbean <smstone@...> wrote:
Thanks for clarifying the build number. It happens to me too! On Tue, Sep 15, 2020 at 10:43 AM, Erik Kaashoek wrote: It may take some seconds (5 seconds per comm port on your computer)? before the port selection box appearsI don't think it's that, I have left it for over 15 minutes and nothing happens. By the way, I don't mean the port selection box isn't populated. I mean nothing happens at all. No program opens, no interface appears or anything. Just a brief 'windows busy' icon for 1/2 a second and then that's all. Should I be doing anything more than downloading TinySA.exe and running it to make something happen? I.e. does it need to be in a particular folder or have any other files present?? |
Re: Thank you! And a couple of questions on PC connectivity and upgrade
Thanks for clarifying the build number. It happens to me too!
toggle quoted message
Show quoted text
On Tue, Sep 15, 2020 at 10:43 AM, Erik Kaashoek wrote: It may take some seconds (5 seconds per comm port on your computer)? before the port selection box appearsI don't think it's that, I have left it for over 15 minutes and nothing happens. By the way, I don't mean the port selection box isn't populated. I mean nothing happens at all. No program opens, no interface appears or anything. Just a brief 'windows busy' icon for 1/2 a second and then that's all. Should I be doing anything more than downloading TinySA.exe and running it to make something happen? I.e. does it need to be in a particular folder or have any other files present?? |
Tracing interference with the Tiny SA
#tinysa
Hi All,
I thought you may be interested to see the Tiny SA in action when trying to trace some RF interference from a Data over Power line adaptor. The Yellow trace shows the peak hold trace with notches in the data signal on Amateur bands clearly visible, the Red trace shows a real time scan, with the strong data bursts peaking >25dB above the ambient noise floor. By connecting the Tiny SA to a small tuned loop antenna and walking around the local streets, I have been able to identify the property that is radiating this noise. The next step is to try and get the Data over Power line adaptor removed. Regards, Martin |
Re: TinySA bug reporting process?
#tinysa
#bug_report
Thank you Erik.
What a great teaching tool using TinySA.exe and a large monitor for teaching students electromagnetic waves, frequencies, FM & AM modulation and where various services reside on the RF spectrum. |
Re: Release 1.0-86: Unexpected Marker Center/Span behavior
Short answer: Yes,?
but it deserves a long answer. I guess you started from power on. At least I can replicated if I start from power on. Then activate the 10MHz cal output and send to low input. Then you see the 10MHz with marker 1 and you click on MARKER OPS/CENTER and you get picture one. Now look carefully at the center frequency. you would hope it to be 10MHz but it is 9.688MHz instead. The reason for this error (which is not an error but a limitation) is the number of measurement points used. The 350MHz range split over 290 points equals 1.2MHz step per point. The accuracy for frequency measurement when in full low range is thus limited and that is why you get 9.688MHZ i.s.of 10MHz (which is 0.3MHz delta) |
Release 1.0-86: Unexpected Marker Center/Span behavior
Erik,
? I noticed the following issue this morning: ? 1. 10MHz calibrator output connected to LOW input. ? 2.? Marker->Center places the 10MHz carrier in the center of the display. ? 3.? Frequency->Span 10MHz.? Expected 10MHz carrier to remain in the center of the display with 5 divisions on either side.? Instead observed the following: ? ? ? ? ? 4.? Another Marker->Center resulted in the expected display. ? ? ? ? ? Is the above actually intentional behavior for the tinySA? ? - Herb |