开云体育

Hi Erik, Back in 2023 I reported that the Interval trigger feature you implemented for me on the TinySA was not working properly on the TinySA Ultra. Today I upgraded the firmware on my TinySA Ultra to tinySA4_v1.4-196-g1e9c187.bin and I tested the Interval trigger feature again and it's still not working properly. My test is to feed in a 60 or 120 Hz square wave (which is rich in harmonics) into the TinySA Ultra, set the TinySA Ultra to Zero Span mode with a frequency of 1.8 MHz, set the display sweep time to 20 msec, select interval trigger with a time of 16.66 msec and I should see spikes that are stationary (very little movement left or right) but I do not get stationary spikes on the TinySA Ultra whereas I do on the TinySA when doing this same test. Sure would be nice to get this feature working properly on the TinySA Ultra as the TinySA Ultra has the built in LNA as well as expanded frequency coverage. I'm sure your buried with the new TinySA Ultra Plus (congrats) but please put this on your to do list if possible. Thanks, Don (wd8dsb)

My Android smart phone has that feature. You can zoom/enlarge the screen image by spreading two fingers on the screen. Is this possible with TinySA in the future?

Indeed, in the CONFIG/EXPERT CONFIG/FREQ CORR menu you can make a correction of the output frequency when Tinysa Ultra is configured in generator mode. The value to be entered must be negative if you want to increase the frequency and positive if you want to decrease the frequency. But the value to be entered does not correspond to the difference of the frequency entered in the Tinysa with respect to that of the precision frequency meter, at least that is what I have found. You have to try the correction value to reach a compromise point. Nor is this value the same for frequencies of, for example, 100-500-800 MHz or 1-2-3 GHz. In addition, you always have to wait a while until the RF output stabilizes. I don't know if it is due to the precision of the internal TCXO or some other factor. I mention this data in case it can be used for some kind of improvement in a large project like TinySa ultra, which is already being asked for too much in terms of its cost, and which cannot be compared with much more expensive and sophisticated laboratory equipment. Thank you and best regards. Efectivamente en el menú CONFIG/EXPERT CONFIG/FREQ CORR se puede hacer una corrección de la frecuencia de salida cuando Tinysa Ultra se configura en modo generador. El valor que hay que introducir debe ser negativo si se quiere subir de frecuencia y positivo si se quiere bajar de frecuencia. Pero el valor que hay que introducir no corresponde con la diferencia de la frecuencia introducida en el Tinysa respecto a la del Frecuencímetro de precisión, al menos eso es lo que yo he comprobado. Hay que ir tanteando el valor de corrección para llegar a un punto de compromiso. Tampoco ese valor es igual para frecuencias de por ejemplo 100-500-800 MHz o 1-2-3 GHz Además siempre hay que esperar un tiempo hasta que la salida de RF se estabiliza. No sé si será debido a la precisión del TCXO interno o a algún otro factor. Estos datos los comento por si sirven para algún tipo de mejora en un gran proyecto como TinySa ultra al que ya se le está pidiendo demasiado en función del coste que tiene, y que no se puede comparar con instrumental mucho más caro y sofisticado de laboratorio. Gracias y un saludo

Hello. First of all, congratulations on a great job with the Tinysa ultra. I have the ZS405 version with firmware 1.4-192 and I would like to discuss a topic with you. The frequency accuracy in RF generator mode. I have checked the output at different frequencies and there are errors which are the following: 1MHz +6.5Hz; 10MHz +3.8Hz; 50MHz -8Hz; 100MHz -23Hz; 200MHz -51.4Hz; 300MHz -81Hz; 500MHz -142Hz; 800MHz -242Hz; 1GHz -350Hz; 2GHz -611Hz; 3GHz -900Hz I cannot check beyond 3GHz because the Tinysa ultra does not have enough dBm output for my GPS-referenced frequency counter and the preamplifier I have only reaches up to 3GHz.

I'm working on resurrecting a Wiltron 6600 series sweeper (10 MHz - 18 GHz) with multiple problems (I think it was a combination of salvage parts). My old systron donner 762-2A spectrum analzyer (and a 436/8484 power meter) have been helping, but it occurred to me that the TinySA Ultra might help (as in detecting presence of a signal) as well, and perhaps aid in validating the sweeper's output (through appropriate attenuators; the YIGs can kick out +15..+20 dBm.) I'm curious as to how the original ("405"?) version Ultra can be expected to behave when encountering a (single) signal (a sort-of stable carrier from a fundamental-mode YIG oscillator) far above the ~5 GHz Ultra-mode ceiling? I suspect this has been covered (either by developer, by experimenter, or both) but my searches in the group archives didn't yield anything that might apply. Thanks!

Hey folks, I've bought a TinySA a while ago for some other project, but something has cropped up that makes me wonder if it can help here. I'm not an RF professional, I know enough to know I don't know anything. A good friend is going through a breakup, and there's credible evedince their evicted ex has been spying on them. We did find a hidden smartphone running a baby monitor app already. Wifi/Network are changed, so any devices relying on that (e.g. ESP32-equipped power bars) are eliminated. However we have reason to suspect there's a cellphone hidden in or the vicinity of the bedroom. My current approach is to inspect the power outlets one by one to see if a power supply has been connected and the setup stowed away behind some paneling. I wonder if there's a way to use the TinySA to home in on such a device as well. I've done some limited resarch into it, and found e.g. videos of people using a HackRF to decode some cellular traffic between the base station and their smartphone. These were quite sophisticated, seemed to rely both on a lot of protocol knowledge (I don't have) and even prior information from the smartphone itself about used channels/modulations, that for obvious reasons also are unknown. I don't even know which kind of technology is being used. 3G, 4G are most likely, but these to my knowledge are umbrella-terms that cover a broad range of frequencies and modulations and other protocol details. So I'm just overwhelmed where to start. If somebody has some idea if the TinySA can be used to at least detect the presence if not precise location of a cell phone so we can be sure that we have to rip half the room apart, that would be splendid. I know it's a moonshot and if it is just not working that way, then I'll accept that as well. Thanks for your consideration, and I'll be back in the future with my actual purpose I bought the little bugger for. Cheers, Diez

New FW release Version V1.4196 Changes: - Removed spur on ZS-407 -- Designer of the tinySA For more info go to https://tinysa.org/wiki

There’s a picture of the various tinySAs on the wiki that implies that the Ultra+ is physically larger than the Ultra. If it is, what are its dimensions? I can’t find them in the specs. _._,_._,_

Hi Erik, I just noticed that the Ham Band shading is incorrect for three of the USA band allocations. (I didn't check bands above 800MHz.) The 75/80 Meter band is 3.5 MHz - 4.0 MHz, but is only shaded from 3.5-3.8. The 40 Meter band is 7.0 MHz - 7.3 MHz, but is only shaded from 7.0-7.2. The 6 Meter band is 50.1 - 54.0 MHz, but is only shaded from 50.0 - 52.0.

Hello, I bought my Tiny SA Ultra some time ago from the suggested supplier so I am led to believe it is genuine. I have been lurking here for some time and have seen many messages from people who have "stuffed" their Tiny SA ultra's because they bought a clone. I worry about upgrading mine, just healthy paranoia :) Is there something I can post about my Tiny that will tell me that it is an original before I upgrade the firmware. I know Erik knows. I'm not asking for the "secret" to determining clone v original, just want to confirm that mine is original. Thanks Mark

I once turned on Listen mode on my TinySA ultra and shut it down - now it starts up in Listen mode by default every time; I have to manually uncheck the "Listen" checkbox at each startup. It saves all settings (e.g. frequencies) except the now unchecked "Listen" mode Version: v1.4-137-g1806825 Is there a way to reset this behaviour to factory default (i.e. start up in normal display mode), without deleting the factory calibration data? Looked at the firmware changelog, couldn't find a bugfix for this particular issue.