¿ªÔÆÌåÓý

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 exploded) chinese switched mode regulators/supplies, they have literally destroyed today's HF (and now slowly moving up into VHF/UHF) communications for many people around the globe :( This is just one example - a baofeng walkie-talkie charger.

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, you need to perform extra steps to automatically identify which port the tinySA is connected to. 1. The most reliable way is to query a connected port using the 'info' console command. >info tinySA v0.3 2019-2020 Copyright @Erik Kaashoek 2016-2020 Copyright @edy555 SW licensed under GPL. See: https://github.com/erikkaashoek/tinySA Version: tinySA_v1.0-49-ga63df47 Build Time: Aug 4 2020 - 17:52:05 Kernel: 4.0.0 Compiler: GCC 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204] Architecture: ARMv6-M Core Variant: Cortex-M0 Port Info: Preemption through NMI Platform: STM32F072xB Entry Level Medium Density devices If 'tinySA' is contained in the response you have found the serial port the tinySA is connected to. 2. If you happen to have two tinySA's connected to the same computer, perhaps for automated frequency response measurements, then I've found the best way to uniquely identify each tinySA is by using the 'deviceid' command. Each tinySA is serialized at the factory with an 8-digit serial number. The serial number is not written in the tinySA firmware, but Erik has included a 'deviceid ' console command that allows the user to set and query a deviceid. If no deviceid has been set, or after a 'clearconfig 1234' console command, then querying the deviceid returns the following: > deviceid returns 0000 I always set my deviceid to my factory serial number (20070007): > deviceid 2007007 > saveconfig 1234 > deviceid returns 20007007 Always perform a 'saveconfig 1234' after setting a deviceid so that the id will be retained in flash memory. Now your program or script can uniquely identify which tinySA is connected to a port by querying its deviceid number. This works well, but only if the user has assigned a unique deviceid to each tinySA. - Herb

DSL dropped off my TinySA yesterday. A quick check with my Sig Gen shows it works. Now to read the manual !! One thing I need is the PC Software. I looked at the Wiki, saw some pictures, but I didn't see a link to the software. Perhaps I missed something. Can someone send me a link to the PC Control Software ? Thanks, Dick, W1KSZ

Dear community enthusiasts, we have manufactured a small amount of tinySA for sale and now sell it through the Alibaba store. If the community feedback is good, we will make more. The current logistics speed is slow, and the logistics cost for sending to some areas may be higher. If you don¡¯t wait to test it, you can wait for us to manufacture it in large quantities and distribute it to overseas distributors. Purchase to save logistics costs. https://www.alibaba.com/product-detail/Hand-held-tiny-Spectrum-analyzer-TinySA_1600085564565.html Many thanks to Erik for creating the tinySA project and implementing it. Many thanks to the tinySA test group enthusiasts for providing great feedbacks. hugen 2020-07-23

Erik, One of my fellow ham club members asked me about the data 0 command while trying to use the output mask of the scan command. Looking through my notes, I remember you replying the following regarding data 0. "data 2 is the "live" data, only different from data 0 when doing a calculation (max hold, averaging, etc...)" data 0 now seems to have been depreciated and always returns an array of zero values regardless of live or stored trace values. What I currently see is the following: data 0: always returns an empty array data 1: returns stored trace data 2: returns live trace Is this correct or have I missed something in my testing? Are you reserving data 0 for a future feature like a second stored trace? Herb

A word of warning for those that want to measure the spectral purity of their transmitter. As the tinySA is specced to accept +10dBm without attenuation and +30dBm for some seconds with maximum attenuation you may be tempted to connect the output of the transmitter to the tinySA, set the tinySA to max hold and transmit for a short time, long enough for one sweep. Even when your transmitter stays below +30dBm you risk making a wrong measurement, or even worse, if you have attenuation on automatic, destroy the tinySA as the tinySA will only adjust (e.g. increase) the attenuation for the next sweep. The spur free dynamic range of the tinySA is a bit above 70dB with an RBW of 300kHz. This means that any signal that is more than 70dB above the noise floor will cause internally generated harmonics. Let's take an example: Without attenuation and with an RBW of 300kHz the noise floor is at -95dBm. With an input signal of 0dBm you are 25dB above the spur free dynamic range so there will be internally generated harmonics. For a good measurement you should apply 25dB of attenuation Make sure to update the FW of you first batch tinySA as the newer FW contains an overload warning (the marker info turns red) to help you make a good measurement.

Today DHL delivered me a couple of tinySA. Still no powered it up, but I want to note that the packaging was really good, thanks Maggie. The only negative comment is about DHL. DHL is a carrier and also a customs clearance agent and they make extra money with it. When using normal mail for receiving parcels from China usually I have not to pay anything, but DHL charged me 10€ for customs duties plus 20€ for the "service". I forgot to say Maggie to sent it using common mail, it is cheaper for both. I had a similar experience when I bought my first AirSpy SDR receiver, I choose FedEx or UPS (I don't remember which one) instead of common mail expecting a safer service, but when it arrived they called me asking for a ridiculous sum for clearing the customs. I refused and made the clearance myself, not before a long discussion about charging me just for giving me the shipping documents. So when I bought another Airspy receiver I choose mail and the parcel arrived at my door without paying any extra. This may not apply to all countries, but it is true for Spain and even worse for other countries. Now I (and a friend) have another toy to play with. Regards, Ignacio EB4APL -- El software de antivirus Avast ha analizado este correo electr¨®nico en busca de virus. https://www.avast.com/antivirus

Hi, I'm trying to send console commands to the tinySA, but I don't know which speed should I use. Also, I have seen ch> and > as the command preamble. Which one is the right one? Thank you, Ignacio EB4APL -- El software de antivirus Avast ha analizado este correo electr¨®nico en busca de virus. https://www.avast.com/antivirus

For those that want to do QRM hunting, having a LNA with the tinySA would be nice. This can be easily done in about 10 minutes. More detail here: https://tinysa.org/wiki/pmwiki.php?n=Main.LNA Result: noise floor with a 3kHz RBW at -135dBm

Waiting for Amazon to get them . They have a lot of NanoVNA at reducing prices. Is there a good source from China or elsewhere with fast shipping? Hunting for some QRM.

The site at TinySA.org is quite helpful. But I am having problems updating the Firmware. It directs me to st.com to download DfuSe Tools. However, when I get there, all I see is STSW-STM32080 and no mention of DfuSe Tools ??? Am I to concur that the STSW file contains the DfuSe Tools ?? Also, still trying to register on that site to download that file. Tnx, Dick, W1KSZ

New FW released Version v1.0-61 Changes: - After a marker search using the menu, a marker can be moved to any position using the lever. - When the sweep is paused you can directly select a marker as active marker by touching the marker info and this is reflected in the marker info

Seems whatever I try to do results in a "complex division by zero" error. Setting marker, clicking on trace... I am running it from the Anaconda prompt, and I get first error right after starting saver: Second one when entering frequency in marker 1 box Gary W9TD

Erik, I combined this request with another topic so you may have missed it. When you get the time could you post what the "help" console command returns? I'd like to know what commands are available for use with the tinySA. Just a list is fine, no need to explain. I'd like to eventually contribute to the group by producing a console command document like the one by Larry on the NanoVNA groups.io. - Herb

I saved a different setup in [store as startup]. When Tiny boots, for a moment we have the setup, then it defaults. You need [load startup] to recall the setup. Is this right? I tried to record it on a video. Thank you.

I¡¯m testing an enclosure and need to place the tinySA inside and test received signal strength of a fundamental. I would think I can enter it into a peak hold type setting for when I can get it out of the enclosure. Is it there and I am just missing it? Thanks in advance!