开云体育

On Thu, Oct 12, 2023 at 10:21 PM, Kimmo wrote:

I need a Python program, in Linux / Ubuntu, that can be used to control tinySA so that I can make continuous sweeps with the tinySA.
I was testing the program tinySA.py, available at
http://athome.kaashoek.com/tinySA/python/

It works fine when using with a command like
> ./tinySA.py -S 50e6 -E 500e6? -o aa.csv?? ? ? ? ? ? (sweeping between 50-500 MHz and saving the data into aa.csv, with 450 scan points)
However, if using a command
> ./tinySA.py -S 50e6 -E 500e6 -N 500? -o aa.csv ? ? (same as above but using 500 scan points)
there is an error message

Traceback (most recent call last):
? File "./tinySA.py", line 306, in <module>
??? nv.writeCSV(s,opt.save)
? File "./tinySA.py", line 239, in writeCSV
??? print("%d, "%self.frequencies[i], "%2.2f"%x[i], file=f)
IndexError: index 500 is out of bounds for axis 0 with size 500

Can somebody tell how to fix this error ?
After that, I can try to modify the program so that it makes continuous sweeps.

Cheers, Kimmo

TinySA Ultra is limited to 450 scan points unless you use the "scanraw" command.? Unfortunately, tinySA.py does not have a switch for invoking the "scanraw" command.

Martin has a python script at? ?? which does use the "scanraw" command for saving a csv file with greater than 450 points.

Herb

On Thu, Oct 12, 2023 at 10:21 PM, Kimmo wrote:

I need a Python program, in Linux / Ubuntu, that can be used to control tinySA so that I can make continuous sweeps with the tinySA.

? Give QtTinySA a try.? It is located at? ?? and is actively supported by the author.

Herb

I need a Python program, in Linux / Ubuntu, that can be used to control tinySA so that I can make continuous sweeps with the tinySA.
I was testing the program tinySA.py, available at
http://athome.kaashoek.com/tinySA/python/

It works fine when using with a command like
> ./tinySA.py -S 50e6 -E 500e6? -o aa.csv?? ? ? ? ? ? (sweeping between 50-500 MHz and saving the data into aa.csv, with 450 scan points)
However, if using a command
> ./tinySA.py -S 50e6 -E 500e6 -N 500? -o aa.csv ? ? (same as above but using 500 scan points)
there is an error message

Traceback (most recent call last):
? File "./tinySA.py", line 306, in <module>
??? nv.writeCSV(s,opt.save)
? File "./tinySA.py", line 239, in writeCSV
??? print("%d, "%self.frequencies[i], "%2.2f"%x[i], file=f)
IndexError: index 500 is out of bounds for axis 0 with size 500

Can somebody tell how to fix this error ?
After that, I can try to modify the program so that it makes continuous sweeps.

Cheers, Kimmo

Thanks Erik.

Yep, I had the wrong info, it was my bad. I got -25dBm from the tinySA. Ultra is -35.6dBm (MODE --> CAL OUTPUT)
I had level adjusted the fundamental (marker) up to -25dBm, which was wrong, and I found that doing another self test it fails many tests with "bad level" messages.

With it back to normal, my 30Mhz cal toggles between -35.6 and -35.7, so I think it's good right there.

I had to it with STM32CubeProgrammer.? At first TinySA exe seemed to work, but when I had to retry, it couldn't connectto NanoSA.

It's in the Wiki.



73

-Jim
NU0C

On Thu, 12 Oct 2023 07:12:22 -0700
"Leif M" <leif.michaelsson@...> wrote:

One? question: How to put SA? Ultra in? a DFU mode. I did not find that info anywhere.

On 12/10/2023 15:12, Leif M wrote:

One? question: How to put SA? Ultra in? a DFU mode. I did not find that info
anywhere.

Depress the jog wheel while switching on.

David
--
SatSignal Software - Quality software for you
Web:
Email: davidtaylor@...
Twitter: @gm8arv

One? question: How to put SA? Ultra in? a DFU mode. I did not find that info anywhere.

The tinySA Ultra uses a much lower level calibration signal (approx -35dBm)
Both global and frequency curve adjustments are available
The adjustment per selected frequency (IN ... CURVE) modifies the internal correction curve (correction versus frequency).
The INPUT LEVEL can be used to do a global level adjustment
See the WiKi

--

Question around calibration tasks.
Self tests are good.
After doing the auto-cal 100kHz-5.43GHz, the 30MHz signal shows up as -32.7dBm.
Is the 7.7dBm diff due to the supplied cable? Leave it as-is, or level adjust it back up to -25dBm ?

And when doing the manual level adjustment, is the adjustment per frequency selected (creating an adjustment map), or does the adjustment simply carry across the unit?

On Wed, Oct 11, 2023 at 02:55 AM, Charlie N2MHS wrote:

Be mindful of that first attenuator's power rating vs what is the source power.

Yes. I forgot to mention that important piece.?

On Sat, Sep 16, 2023 at 07:43 AM, Mike wrote:

Exactly my thoughts Martin - well said. This is really a common sense resolved issue - a good selection of ready to hand attenuators, and always err on the side of caution.

50ohm terminator caps are good, when not in use.

Hi all. I have several tiny devices, SA Ultra is my newest one.

I just wanted to make some notes, perhaps corrections to some previous posts.
G8HUL on page-1 is right. The spec sheet for SA Ultra does says "For best measurements keep input power below -25dBm". That's just 3.162uW.

If power is 1W, you need around 55dB attenuator to get close to -25dBm, thus -60dB is good (1uW).
Anything more than -25dBm and it's outside it's comfort zone.

Someone posted "-20dB with my 1W". That's magnitudes more power than the SA wants to see.

-60dB is easy, just buy a 20 & 40, so now you have three attenuators 20/40/60. Yeah, watch out for insertion losses.

Those things generally use OOK (On/Off Keying) and are rather broadband by nature.? The modulation looks about like I would expect.? The output is variable due to the fact that it is held in your hand and the proximity of your hand to the antenna detunes the antenna.? You might use a non-metallic tweaker (ceramic, if you have one), and tune for greatest signal strength at the distance you usually open the gate.? Or you might use the trial and error method for best range.? Unless you currently have a problem with the range of the device, Sam Reaves' advice to use the "If it's not broken, don't fix it" method might be the best.? I say that having a fair bit of professional experience with handheld and bodyworn RF devices.? You usually wind up doing at least some trial and error.

I seem to use the sig gen function quite a lot with my Ultra.

Today I was toying with my old Wouxun UVD1 on the FM broadcast band.

The broadcast FM RX has always been a bit weird, but usable, but nothing special.

I learnt that I could get exactly -100dbm of MDS out of it before the the rx died, at 108Mhz.

Even 1 db below was unusable, much like the typical sensitivity of other RX's.

But the difference here was the absolute cliff edge when a signal was below -100dbm.

Other rx's are still a cliff edge, but hell the UVD1 was so absolute.

Below that the audio was so terrible as to be awful.

Sent for info only, just appreciating the Ultra's sig gen function.

Messeed around with other HT's in my collection.

For example my Yaesu VX7R on HF was about -100dbm also.

As is my Tecsun PL880. But at least it as some AGC, unlike the VX7R.

I very much appreciate the sig gen function on the Tiny SA Ultra.

73 de Andy