¿ªÔÆÌåÓý


Re: Black Screen after Update still able to connect

 

Very pleased to say I went to grab a copy of the 175 bin file which was the one thatI had trouble with, and there was the 199 bin file (wasn't there before)which loaded perfectly (using StmCube) with the TinySA Ultra rebooting and happily making squiggly lines after!! So I guess mine is legit lol

Now just have to figure out the how and why again. Havn't touched an spectrum analyzer for 20 years.

Thanks again for all the hints/help.

Dave

On Mon, May 5, 2025 at 5:50?AM Erik Kaashoek via <erik=[email protected]> wrote:
Correct
--
Designer of the tinySA
For more info go to


Locked Re: Spur signals above 2.75 GHz?

 

On Mon, May 5, 2025 at 07:48 AM, Serguei wrote:
But is it possible to change the IF while scanning in the GHz range? This would shift false spur and mirror signals, but leave the normally detected signals in place, right?
I would welcome someone looking at the code and suggesting better ways to remove spurs and mirrors
Shifting the IF is already done.
?
--
Designer of the tinySA
For more info go to


Locked Re: Spur signals above 2.75 GHz?

 

Do any of the readers of this group remember the original Polrad spectrum analyzers?? Those were my introduction to spectrum analyzers.? When you tuned them looking for your signal, there were copious spurs moving both right and left on the screen.? How could you be sure you found what you were searching for?? Switch your apparatus off and on.? Of course, your signal mixed with the LO, so you were never sure!!??

The old HP 141's are still around with their burned CRT, variable persistence, and the BWO.? If the BWO ever went south, one had to realign the entire unit.? I'm glad those days are behind us!!

Dave - W?LEV?


On Mon, May 5, 2025 at 2:48?PM Serguei via <mirsev=[email protected]> wrote:
Did I read it? Oh, yes, but that was the first day I bought this device, was in a hurry to use it, and forgot about it, like about the fine print. My mistake!

After I posted my message, I did a deeper search and found your message here. Maybe I need to look for more information about TinySA Ultra+ and documentation to study how it works... But is it possible to change the IF while scanning in the GHz range? This would shift false spur and mirror signals, but leave the normally detected signals in place, right? Sorry if I'm asking something stupid, perhaps, I have to search some docs and do some research in the code on GitHub, but I would appreciate if someone gives me a hint...



--
Dave - W?LEV



Locked Re: Spur signals above 2.75 GHz?

 

Did I read it? Oh, yes, but that was the first day I bought this device, was in a hurry to use it, and forgot about it, like about the fine print. My mistake!

After I posted my message, I did a deeper search and found your message here. Maybe I need to look for more information about TinySA Ultra+ and documentation to study how it works... But is it possible to change the IF while scanning in the GHz range? This would shift false spur and mirror signals, but leave the normally detected signals in place, right? Sorry if I'm asking something stupid, perhaps, I have to search some docs and do some research in the code on GitHub, but I would appreciate if someone gives me a hint...


Locked Re: Spur signals above 2.75 GHz?

 

John,
Can you explain for those that are less knowledgeable?
--
Designer of the tinySA
For more info go to


Locked Re: Spur signals above 2.75 GHz?

 

High pass filters are your friend when measuring in ultra mode.


Re: Black Screen after Update still able to connect

 

Correct
--
Designer of the tinySA
For more info go to


Re: Black Screen after Update still able to connect

 

So assuming I muffed that first update I should be able to update to that version. If not then I should consider this a clone and work on getting a refund?? Sound about right?

Appreciate the help/patience for newbs lol

Thanks Erik

Dave


On Mon, May 5, 2025, 12:09 a.m. Erik Kaashoek via <erik=[email protected]> wrote:
All FW should be backward compatible for all genuine HW.
Don't know about clones
--
Designer of the tinySA
For more info go to


Re: TinySA Ultra Sig-gen output level

 

Thanks but I am not confident to do this. The self test fails with the message:

Test 3:? Signal level Fail
?
30.000MHz -74.7 dBm
?
The spectrum analyser is working fine.?
?
?


Re: Black Screen after Update still able to connect

 

All FW should be backward compatible for all genuine HW.
Don't know about clones
--
Designer of the tinySA
For more info go to


Re: Auto Save Issues

 

You could use a Raspberry Pi and the cli tool I've written for the tinySA:
?
A simple bash script that loops over a frequency range and exports the traces with capture could look like this:
?
#!/bin/bash
?
# enable max hold on trace 2
tsactl trace 2 --enable --calc=maxh
?
# sweep between 100mhz and 500mhz in 50mhz steps
for freq in $(seq 100 50 500); do
? ? tsactl sweep --center ${freq}mhz --span 50mhz
? ??
? ? sleep 10
?
? ? # save second trace as csv
? ? tsactl save --trace 2 -o sweep_${freq}mhz.csv
?
? ? # save capture
? ? tsactl save --capture -o sweep_${freq}mhz.png
done
?
If you can code, you could also use the golang sdk for the tinySA which is used by the cli tool:
?
Note that both the cli tool and the sdk are in a very early stage, so if you find any bugs, please report them.
And if you need help, just write me an email.
?
Kevin


Re: Black Screen after Update still able to connect

 

As an update to this I downloaded an older file from around the manufacture date and it's back working again making squiggly lines.? So that's a positive.

So if I try to update can I expect it to accept any of the newer bins? Just curious if I had messed the first update up or there are hardware diffs or something preventing the latest and greatest bin being used?


On Sun, May 4, 2025, 2:52 a.m. Dave King via <kingdws=[email protected]> wrote:

Yup was a ultra bin file. I will be paranoid and double check it again though lol.? It is still able to talk to the programmer in dfu mode so am hoping it is something fixable.


On Sat, May 3, 2025, 5:49 p.m. Bill Retzner via <billretzner=[email protected]> wrote:
Did you download the correct binary file to match your tinySA type?

I f you have an Ultra, then get your binary from the SA4 folder and has ¡°SA4¡± in the file name.?


On Sat, May 3, 2025 at 7:27?PM Dave King via <kingdws=[email protected]> wrote:
Hi All

Hopefully someone can help aim me in the right direction. I updated my ultra with the latest code using STMCube. It appeared to update correctly but after rebooting I am no longer getting any display. I tried one suggestion of erasing then reflashing along with verification but no difference. The date on my unit shows Feb 24 mfr date and was supposed to have come from Zeetex(?) .??

Was there a hardware update or change so I need a different bin???
Does this prove it was a fake clone?
Any suggestions??

Dave


Locked Re: Spur signals above 2.75 GHz?

 

As you are using the Ultra mode I assume you have read this page :
?
--
Designer of the tinySA
For more info go to


Re: Has anyone tried connecting Tiny to https://www.gnuradio.org ? Is it possible to extract a clean IQ signal from Tiny ?

 

Not possible as there is no I/Q output
--
Designer of the tinySA
For more info go to


Has anyone tried connecting Tiny to https://www.gnuradio.org ? Is it possible to extract a clean IQ signal from Tiny ?

 

Has anyone tried connecting Tiny to https://www.gnuradio.org ?
Is it possible to extract a clean IQ signal from Tiny ?


Locked Spur signals above 2.75 GHz?

 

Hi. I purchased the SeeSii TinySA Ultra+ ZS406 from Amazon last week. I'm really impressed with its design. It is a wonderful piece of hardware. I updated the firmware to the latest version, ran self test and calibration. Everything was fine...

However, when I scanned the radio frequency range from 100 kHz to 5.5 GHz with the supplied antenna, I found some suspicious patterns on the traces and waterfall. It seems that some signals above 2.75 GHz look like copies of the signals from the lower band. Are they spurious signals? Is there any way to fix it? Or is it a problem with my device? Any idea?
?
The next two screenshots below were taken during separate scans within 1.8-2.8 GHz and 4.0-5.0 GHz screen ranges:
?



The weaker signals around 2.4 GHz are from my router, I think, and the stronger yellow pattern corresponds to the 1.5 minute time interval when the microwave was on.

So it looks like false signals above 2.75 GHz to me. Does anyone have a similar problem?


Re: TinySA Ultra Sig-gen output level

 

Dieter,
?
Follow the first Fault finding with oscilloscope section at the bottom of this page:
?
--
Designer of the tinySA
For more info go to


Re: TinySA Ultra Sig-gen output level

 

I just tried the same with my little TinySA and it seems to be working just fine with -7dBm output level. My RF microwattmeter shows -10 dBm. I guess this can be improved by calibration.


TinySA Ultra Sig-gen output level

 

Hi
Yesterday I tried using the sig gen function of my TinySA Ultra. I notice that the output level is not -18.5 dBm but instead it is around -50 dBm.
I tried the various setting options but all to no avail. Perhaps I am making a mistake somewhere.

The spec analyser function is working very well. However, I have not done any calibration yet.

Any comments & advice are most welcome.
?
Dieter VK3FFB


Re: Auto Save Issues

 

Hi all !? i'm a new here and have an original Tiny SA Ultra+ ZS407 updated,
and i would to use it to record to sdcard without computer, some band of freq (if possible with multi band) like "water fall" with date and time in .CVS file for analyse on computer after the capture.
I would like to record during 8h or 12h before transfert to computer for analyse
?
i read this topic i think i'm at the good place, have you a firmware ready for that or advice?
?
Thank you