开云体育

Hi guys, I got the TinySA Ultra+ ZS406 today from Eleshop. I updated the firmware to tinySA4_v1.4-198-g996a67b.bin (Picture 1). Before that, I had a Firmware from January 2025. I did the Self test two times, which failed on Test 8 Passband failed (Picture 2 and 3). Then I did the Level CAL" 100kHz to 5,42GHz" and then I tried the Self test again same problem with Test 8 Passband failed. Then I Reset Calibration and did and did the Level CAL "100kHz to 5,42GHz" again. And then the Self test again and now all Test passed two times again. ( picture 4 ) And the third time it failed again Test 8: Passband failed again, everything else passed ( picture 5 ) And the fourth and fifth time Self test all passed again. Then i did the Level CAL "100kHz to 5,42GHz" again and Self Test again Test 8: Passband failed again ( Picture 6 ) The next two Self test all Test passed again. The third Self test on Test 8 Passband failed again ( Picture 7 ) Should I return it to Eleshop and get a new one ? Are the Values of of Test 8 off by so much or just minimally off ?

Hello Erik and everyone. I've recently purchased a TinySA Ultra+ from a local vendor and the unit has an issue. It is a ZS-407 with HW version V0.5.4 and S/N SU-407-25011571. It has a spur at ~4.275 GHz that is present regardless of the Spur Removal or Sample Rep settings: When I narrow the frequency bandwidth to 100kHz and turn off Spur Removal, I see that the "spur" is actually five pulses: The instrument passes the self test and calibration successfully. This issue was present in the factory firmware (I believe it was V1.4-195) and is still present after upgrading to the latest V1.4-197. The vendor has checked a few other units they have in stock and they show the same spur: The vendor assures me that the units are genuine and that they get them directly from ZeenKo. I also have an older TinySA Ultra (up to 5.3 GHz, ZS-405 maybe, it has no model number on it) and it has no such anomalies. So my questions are: - Is this device really genuine? - Is this a known issue? - Is it faulty hardware? - How can this be fixed (if it's possible)? Thank you! Best wishes, Andrew PS: This is the device in question:

My TinySa Ultra+, just bought on Amazon from Pinsaitec, fails on selftest #8. I have implemented newest firmware, have done several calibration runs! No efford! What can I do, before returning the device to vendor? Best regards, Hartmut

WinSpectrum III is a spectrum analyzer application designed for Windows users working with Tiny SA Ultra+. Here are its key features: - **Lightweight**: The application is under 900 KB, ensuring quick installation and minimal system impact. - **No Installation Required**: Simply download and run the executable. - **Framework Requirement**: Requires .NET Framework to run. - **Tested & Stable**: Successfully tested on Windows 10 and Windows 11 (64-bit). - **User-Friendly**: Designed for ease of use. You can download it here: [Download Link) https://xrjunque.nom.es/(S(wdfgatyrxtvaewspynrrbwlp))/swdownload My friend Xavier and I collaborated on this project with the hope that it will be beneficial to the Tiny SA community. We've made every effort to ensure the application is effective and reliable. If you give it a try, we would appreciate your feedback and suggestions for improvements. Looking forward to hearing your thoughts! Best regards, Juan (M0WWA) & Xavier

Dear all, I've been playing with my TinySA, and I think I've passed the measure power limit during some test and now my device doesn't measure correctly. Probably I exceeded the +6 dBm. I've uploaded new FW and try to pass the self test, and I've obtained errors on tests: 3,4,7, 10,11 and 14. I attached a picture, Try to passed level calibration is not possible. I've appreciated that if I inject a signal from a signal generator of value is attenuated but measurable, however if I turn on the LNA I can't see anything, so my first thoughts is going about the LNA is broken. I've also tested the attenuator and it works well. So I join this group with the hope that you could help me to solve the issue. I also attach a picture of the back with the S/N. Thanks in advance for the support and I'll be waiting for your news. Greetings, Jorge

Hi I bought tinysa ultra from facebook. It fails attentuator and signal level. Can it be fixed? can it be used as a signal generator?

Hi Erik and gang, I owe Erik an apology as not to long ago I said the interval triggering feature that Erik implemented for me a few years ago on the TinySA was not working properly on my TinySA Ultra. In a recent post that Erik responded to someone on a different topic he mentioned setting the RBW to 850 KHz when using Zero Span mode and that made me revisit the interval triggering feature as I had ignored the RBW setting when using interval triggering. Today I tested the interval triggering feature with the display sweep time set to 20 msec, trigger interval set at 32.6msec which is a multiple of 1/60 (60 being the power line frequency in the US), set the RBW to 850 KHz, and the Zero Span frequency set to 146 MHz which is a frequency I know I can hear RFI that's generated by an LED light dimmer in my family room that I use for testing the interval trigger feature. I then turned on the LED lights and I can easily see the light dimmer going into conduction at a frequency of 120 Hz which would be each half cycle of the 60 hertz sinewave and it's a very stable display (apparently in sync with the 60 Hertz line frequency which is what I was hoping for). I've attached a screen shot showing the display generated by my LED light dimmer driving LED can lights (antenna used was a homebrew Moxon beam designed for 146 MHz). I originally wanted this interval trigger feature to help track down RFI like power line noise that's in sync with the electrical grid frequency, and will now continue my work on this subject now that I better appreciate the setting of RBW when in zero span mode. Having the ability to trigger in sync with the electrical grid is beneficial when there are other signals present which are not necessarily in sync while you are attempting to see signals in sync with the grid. Bottom line is that the interval trigger feature appears to working great and having the RBW set to 850 KHz really helps. Big Thanks to Erik, Don (wd8dsb)