开云体育

Ah,

Unplug the tinySA, wait for the beep, plug in again, wait for the beep and try again.

tinySA.exe may hang in a hidden state waiting in deadlock

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.

Remember you can do DISPLAY/STORAGE/STORE TRACE to save a trace short term and after that you can do a PRESET/STORE/STORE x to save the stored trace to flash so you can recall them any time you want.
You can extract them to a PC using the "frequencies" and "data 1" console commands

?

I have just found it works fine on my other Windows 10 PC. Same TinySA, same TinySA.exe. Odd.

Thanks for clarifying the build number. It happens to me too!

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

Thank you Erik.

You have a truly remarkable product. ?TinySA is a game changer.

Every high school Science ?Department should purchase a TinySA. ?The product maturity is there now,

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.

--
73, Bernie, VE3FWF
(most typos in this message were generated by highly sophisticated auto-correction software)

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)

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

Hi Erik,

That's great.

Love the new graticule calibration, it's now so much easier to quickly work out the frequency spacing between signals :-)

Thanks again.

Martin

On Mon, Sep 14, 2020 at 04:57 PM, Jim Allyn - N7JA wrote:

so hasn't had the chance to fix it on github yet.

Is fixed now

Looks good!? Love how you are constantly working to improve this.
--
73, Michael, KE4EST

Forgot to push the release button
Now its there

New FW release
Version V1.0-86

Changes:?
- Added a frequency per division indicator at the bottom
- Increased the minimum number of frequency grid lines to be shown?

Thanks Erik, all understood no rush, but maybe is good :-)

Regards,

Martin

On Tue, Sep 15, 2020 at 02:37 AM, Martin wrote:

I wondered if at some point it would be possible to add an option to change the frequency graticule scale,

Added to the todo list, this may take some time though (if ever)

On Tue, Sep 15, 2020 at 01:39 AM, Magicbean wrote:

1) I downloaded TinySA.exe to use on Windows 10 64-bit. My device shows up as a COM port but when I run TinySA.exe, there is a brief pause (0.5-1s) and then nothing at all happens. I restarted the computer, turned off anti-virus etc. TinySA is in a folder on my computer (not in Program Files etc. as I am under the impression that this is OK). I assume I have missed something.... any pointers gratefully received.

It may take some seconds (5 seconds per comm port on your computer)? before the port selection box appears

2) I have upgraded the firmware for the first time using dfuse and file tinySA_v1.0-85-ge82e61d.dfu. The software uploaded and verified then I closd dufse and rebooted with the power switch.
The TinySA is working but the front panel shows version 1.0-84 not 1.0-85. Is that just accidentally not updated in the software or is the upgrade not applied? (Sorry, I forgot to look at the number before I did the upgrade!)

I have forgotten (again) to clear the project before building and this messes up the version number displayed. V1.0-85 display V1.0-84. Need to improve my build environment.

I added a wiki page on noise factor measurement but as I am no measurement expert I could make some stupid mistakes.
Can someone with the right knowledge (on how to measure noise of resistors and the NF of an amplifier) please review this wiki page and provide some feedback?