|
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
|
|
Output impedance of RF sinewave generator (Tiny Ultra)
6
Today, as I was going to measure the frequency (sensitivity) plot of a 500 MHz Keysight oscilloscope, I found that the measured amplitude was going to increase by approx. 6 dB from approx. 150 to 300 MHz, and then drops down somewhat. Despite a direct connection using SMA-BNC adapter and direct coupling without coax cable and a 50 ohms scope input. At any case: the behaviour got (expectedly) a bit worse when I selected a high impedance input while using a BNC T-connector for termination with a BNC 50 ohms termination resistor. After doing some experiments, I discovered this: with the latter configuration I also switched the internal 50 ohms to active state (resulting termination: 25 ohms). It was a nice surprise that the amplitude shown on the screen was really constant over the whole range that was used (up to 500 MHz), while the amplitude under 150 MHz was fairly the same as in the case of a single 50 ohms termination. The question: what about the output impedance of the generator? Rob
|
|
What accessories do I need for a TinySA Ultra?
29
I'm new here and new to my TinySA Ultra and NanoVNA. Trying to keep it affordable, I'm just trying to figure out what accessories I should buy first and which ones I should still buy but can wait until later. What attenuators should I get first? I have an assortment of connectors/adapters and I have these two attenuators, https://a.co/d/bFnpBAT, https://a.co/d/b4JeLwu . And a 15w 0-500Mhz Dummy Load https://a.co/d/8fGnqdi Is there anything I should buy to protect the SMA connectors with adapters on the TInySA like some people have mentioned? And do I need anything for the antenna? Someone mentioned a DC blocker like this, https://a.co/d/aHC3juo Is there an upgraded antenna worth buying? I'd like to have a second one on hand as backup anyway. I'm wanting to test out some Ham radio handhelds and my mobile Anytone AT-778UV Ham Radio. They are UHF/VHF. And then I'd also like to test out some CB radios. I've been reading mixed reviews on everything so I figured I'd ask here before I started ordering things I don't need or end up ordering the wrong things. Thanks for the help.
|
|
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)
|
|
WinSpectrum III v3.0.1.1 每 Update & Fixes
Some users reported that nothing was displayed on the graph when using tinySA (basic). The issue was caused by WinSpectrum's default scan setting of 450 points, which the tinySA (basic) does not support (it has a 290-point limit). Fixed in version 3.0.1.1: WinSpectrum III now detects tinySA (basic) failure when the number of points exceeds 290, adjusts the scan to 290 points, and correctly displays the graph〞no user intervention required. Additionally, this update includes several improvements and fixes: ? Added LNA on/off command. ? Start/Stop Frequencies are now displayed at the bottom of the graph. ? Fixed logfile reading issue. ? Various marker-related fixes and improvements. ? Added Delta calculation for markers. Tested successfully on tinySA (basic) version 1.4-40, tinySA Ultra (non plus) version 1.4-156 and tinySA Ultra+ versions 1.4-196 and 1.4.197. About the marker's 'Tolerance' field Some users may wonder why WinSpectrum III includes a Tolerance (%) setting for peak markers when this parameter is not explicitly found in most VNAs, Spectrum Analyzers, or tinySA devices. This feature is not mandatory and does not modify the raw measurement data. Instead, it is an optional tool that helps locate peaks within a user-defined range rather than just a single frequency point. For example, if a peak frequency is set to 10 MHz with a 5% tolerance, WinSpectrum will search for the highest peak within the 9.5 MHz to 10.5 MHz range, rather than just at 10 MHz. This can be useful in cases where signals fluctuate slightly due to environmental factors or device tolerances. The goal of this feature is to make peak identification more flexible and user-friendly, especially when dealing with noisy signals or spectral variations. Of course, if users prefer a fixed peak frequency search, they can simply ignore this setting. https://xrjunque.nom.es/swdownload#winspectrum 73
|
|
2025 SVHFS Conference Update
Below is an update on the schedule of speakers and presentations for the Southeastern VHF Society Conference. The conference will be held at the Quality Inn at Exit #4 in Clarksville, TN April 4-5, 2025. This is an opportunity to meet other VHF+ enthusiasts, learn, exchange ideas, and have FUN. The $69 registration fee for the conference is required, and it includes a 1 year membership in the SVHFS. Details are here: https://svhfs.org/wp/2025-conference/. Advance registration is highly recommended as the hotel requires a head count in order to prepare the food for the event. There will be door prizes given away at the banquet on Saturday evening. Feel free to contact me via email if you have any questions: RobinK4IDC@.... Preliminary 2025 SVHFS Conference Schedule Friday 8:00 AM Registration 9:00 Charles Osborne -K4CSO 每 RF Zero - 30 min 9:30 Robin Midgett 每 K4IDC 每 RF Zero 2 Meter Beacon- 30 min 10:00 Bob Lear 每 W4ZST Power Dividers and Cable Loops 每 30 min 10:30 15 Minute Break 10:45 Mike Stipick 每 KC4RI 每 5.7 GHz SDR Transceiver - 45 min 11:30 Bill Pence 每 Grid Square Locator 每 30 min 12:00 PM Lunch - Steve and Sandra Kostro 每 Designing a Multi Band Transverter 1:15 2:00 Paul Wielozenski - K4PEW - VHF Nets 每 30 min 2:30 Ben Lowe 每 Rover Radiators 每 30 min 3:00 George Presley 每 10 GHz Beacon 每 30 min 4:00 Charles Osborne / Kent O＊ Dell 每 10GHz Antenna test Range - 30 min 5:00 Dinner 每On your own 7:00 Swap Fest and Hospitality Suite Saturday 9:00 AM Brian McCarthy 每 Lunar Rover Truck, 2.3GHz Amp 每 1 hour 10:00 Peter Van Horne 每 KA6U - Moon Bounce Rover 每 45 min 10:45 15 Minute Break 11:00 Chris Arthur - NV4B 每 45 min 12:00 PM Lunch - On your own 1:30 Larry Cagle - K4WLO 每 Meteor Scatter with MSK144 - 45 min 2:15 SVHFS Business Meeting 3:00 每 5:00 Rover Round Up and 10GHz Antenna Range 6:00 Social Hour- Hotel Bar 7:00 Dinner Banquet followed by the Door Prize Extravaganza! Thanks, Robin Midgett K4IDC Thanks, Robin Midgett K4IDC
|
|
Settings for measure Lora signals
3
Hello there, I am having some strange behaviors between rx and tx in my personal project and have thought of using tinysa to better monitor what is going on. The use will be for short/medium range so there is no need to measure signals below -90db at most. My settings are BW500khz, SF5 and 868.0 Mhz, I have set tinySA center frequency 868, span 500Khz and I see perfectly the signals but, depending on the RWB I use, I get a RSSI or another, I would like to know what would be the appropriate settings or any advice to compare the RSSI between tinySA and LoRA modules. Thanks!
|
|
TinySA Ultra exists DFU when connected to PC
3
All was fine, until I flashed custom firmware. Didn't like it, tried to go back to stock. Basically, on Windows 10, when I connect USB to PC and try to enter DFU mod, it throws me right back out of the DFU mode. If I disconnect USB cable, TinySA Ultra enters DFU mode, screen stays black. Also, if I connect to Linux, it enters DFU mode (but dfu-util does not work). How to approach this situation? Let's focus on windows, what can I do so that TinySA Ultra stays in DFU when I connect USB cable? For in case I'll include the output from Linux. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 0408:5222 Quanta Computer, Inc. HP Webcam Bus 001 Device 008: ID 0483:df11 STMicroelectronics STM Device in DFU Mode Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub dfu-util 0.11-dev Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ dfu-util: Warning: Invalid DFU suffix signature dfu-util: A valid DFU suffix will be required in a future dfu-util release Opening DFU capable USB device... Device ID 0483:df11 Device DFU version 011a Claiming USB DFU Interface... Setting Alternate Interface #0 ... Determining device status... DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations Clearing status Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present DFU mode device DFU version 011a Device returned transfer size 2048 DfuSe interface name: "Internal Flash " Downloading element to address = 0x08000000, size = 181632 Erase [ ] 0% 0 bytesdfu-util: ERASE_PAGE not correctly executed
|
|
TiySA ULTRA APP for sweeping during hours/days with CSV exports
6
#features
#software
#tinysa
#ultra
#WindowsAPP
Hi ToniZG, please share your software - any download links ? greetings
|
|
UHF Bessel Null
4
First of all I must explain that I am pretty much a newbie when it comes to spectrum analyzers and I apologize if the answer to my question should be obvious. I have a TinySA and I've been working on an amateur DMR repeater that is using a Repeater Builder STM32-DVM controller. It became necessary for me to null out the FM carrier and the Bessel null procedure was recommended. However, I wasn't able to properly discern any carrier level changes when adjusting the Tx on the controller. To my understanding, the High channel input does not have enough resolution but the Low channel input does. All the examples of using a TinySA that I can find seem to be performed on a VHF or lower frequency. My question is this, would a TinySA Ultra+ model work in this situation? If so, any help with setup recommendations would be greatly appreciated. Regards and thanks in advance, Chris
|
|
Noise figure measurment not built into standard (2.8") TinySA?
4
I have both the standard and Ultra versions of the TinySA. Both incredibly useful tools. I recently became aware that the Ultra has built in ability for noise figure measurements on LNAs. Purely out of curiosity I am wondering why this measurement is not possible with the standard TinySA...i.e. is there something intrinsic in the design that makes it impossible? I am also wondering if there are any "tricks" to making a NF measurement with a standard TinySA....i.e. would I have to have a calibrated noise source etc?
|
|
I am starting this new thread because the old thread below is locked: /g/tinysa/topic/possible_design_issue_with/109589683 Yesterday, the earphone jack on my 2-year old TinySA detached from the PCB. The jack's footprint has three pads, two of which are connected by a very fine trace (fig. 1) and one of the two connected pads is missing. I did not attempt to join back the missing pad because soldering a fine wire on the broken trace is beyond my dexterity. Fortunately, the jack's 3 solder terminals are replicated on the top of its body (fig 2). So, I replicated the missing connection by soldering a fine wire between the 2 top terminals. Then I soldered back the other two terminals to their respective PCB pads. I would prefer to mechanically secure the jack by tying it down to the PCB using either cable tie or twisted wire, but cannot do so because the LCD on the opposite side prevents me from drilling holes (fig. 3). So, I ended up slathering epoxy glue on the jack and PCB (fig. 4). To prevent the jury rigged jack from detaching again in the future, I resort to permanently leave a pigtail connected to it (fig. 5). Feedback welcome! 73, Leong, 9M2LCL, ex-9W2LC.
|
|
ALL, I'm GUILTY of continuing an OFF topic thread. Sorry. Is 82 old or .........? Remain WELL & be SAFE! Robin - - - - - - - - - - - - - - - - - - - - - On 3/6/2025 10:21 AM, Mike C. wrote: Gotcha ya beat, Dave, I was born the day before Ruzevult DIED. So that puts me up on the stack. Mike C. Sand Mtn GA On 3/5/2025 11:12 AM, W0LEV via groups.io wrote: Welcome to the elete "Old Fossil Club", Dan. I'm 78.25 years "wise". Dave - W?LEV On Wed, Mar 5, 2025 at 12:39 PM Dan Heather via groups.io <jdanheather@...> wrote: at 77.5 years, I learn something new everyday! But this topic makes my head hurt (in a good way)! Thanks folks! -- Dan N1DH Middleboro MA -- Dave - W?LEV
|
|
Good day, I would like to know whether I can apply the Antenna Factor (AF) for my calibrated biconical antenna to measurements being made by the TinySA Ultra. Antenna theory refresher: The AF is a value that lets you go from measured intensity to actual E-field intensity. It is critical when doing compliance testing of radiated emissions. If the AF was just a single value I could apply it to the TinySA settings as a pretend attenuator between the antenna and the TinySA. But the AF of my antenna is highly frequency-dependent, varying by over 20dB over my frequency range of interest.
|
|
QtTinySA update to v1.0.2
26
#software
I have updated the QtTinySA PC App to version 1.0.2 Note: Any existing config database QtTSAprefs.db must be updated, it's not backwards-compatible. Updated with improvements and new features. See the Wiki pages for details of how features work and how to update the database. New: Waterfall display. Save sweep data to a CSV file continuously. Github workflow now builds the executables for Linux, Windows and macOS directly in Github runners. Improved: Any marker can be associated with any trace. Marker max/min tracking much improved and now with 9 levels. All markers can have a delta marker. Peak detection threshold and frequency boundary lines de-cluttered. All Python files moved into 'src' folder. Please report any issues or start discussions on the Github pages , not here. It would be interesting to know on here if the macOS executable works ok since I can't test it. Thank you to Clive, Bill, povnz and xros for testing and contribution of ideas. Ian G4IXT
|
|
Hello. Me and my friend bought both a zs-407. He didn't know better and bought from banggood... and I bought from the aliexpress zeenko store linked in the wiki. His device arrived earlier and we tried the same things done in this video https://www.youtube.com/watch?v=I5IzLAGgKg0 by Mr. Kaashoek, and we where a little confused. The device was showing a lot of signals that in the video are not seen, but all the tests didnt passed, even affter updating the firmware....so we waited my device to see the difference. There is basically none....same dbs same shapes....now wea re very confused....because it could be both are genuine, and the wave seems different from the tinysa of the video because the ultra has a bigger screen and can show more mm of graph....or has better sensors....or they could be both fake, but...zeenko store selling fakes? I can post a video if needed. Thanks in advance for any help
|
|
Many thanks to Erik's efforts, we expect to be able to launch tinySA ULTRA plus in the coming month! Includes two versions, the ZS-406 and ZS-407, the ZS-406 will go on sale next week and the ZS-407 is expected to go on sale at the end of December. The ZS-406 version is used to replace the current version of tinySA ULTRA,up to 900MHz in normal mode to cover the European 868MHz ISM band. The ULTRA mode of the ZS-407 version can go up to 7.3 GHz without the use of harmonics, and the LNA is effective over the full frequency range. With LNA on at 6GHz, DANL is as low as 163dBm/Hz, possible to use the fastest 850kHz RBW to find small signals as low as -100dBm. The look of tinySA ULTRA plus will remain the same as the current version of tinySA ULTRA, and the firmware will remain compatible with tinySA ULTRA, which means that any of your peripherals and apps developed for tinySA ULTRA can be seamlessly migrated to the new tinySA ULTRA plus. Below are the pre-release specs, there may be some changes in the final version, the final version is based on what Erik has posted on the wiki. Parameter tinySA ULTRA tinySA ULTRA+ ZS-406 tinySA ULTRA+ ZS-407 Display size 3.98§ IPS-TFT LCD (480℅320) 3.98§ IPS-TFT LCD (480℅320) 3.98§ IPS-TFT LCD (480℅320) Max low input frequency 800MHz, 5.3GHz in Ultra mode 800MHz, 5.4GHz in Ultra mode 800MHz, 7.3GHz in Ultra mode Resolution filters in 1,3,10 steps from 200Hz to 850kHz from 200Hz to 850kHz from 200Hz to 850kHz Max output frequency Sinus up to 800MHz, Square wave up to 4.4GHz Sinus up to 900MHz, Square wave up to 4.4GHz Sinus up to 900MHz, Square wave up to 6.3GHz output level -115dBm to -19dBm -115dBm to -19dBm -115dBm to -19dBm Ultra mode Level calibrated up to 6GHz Level calibrated up to 6GHz Level calibrated up to 8GHz Internal LNA gain 20dB up to 4GHz 20dB up to 4GHz 20dB up to 7.3GHz Displayed points per scan max 450 max 450 max 450 0-350MHz scan time 165ms 165ms 165ms Shortest zero span time 14 ms for 450 points 14 ms for 450 points 14 ms for 450 points DANL at 100MHz -153dBm/Hz (LNA Off) / -169dBm/Hz (LNA On) -153dBm/Hz (LNA Off) / -169dBm/Hz (LNA On) -153dBm/Hz (LNA Off) / -169dBm/Hz (LNA On) DANL degrading in ultra mode 10dB above 3GHz, 25dB above 5.3GHz 5dB above 3GHz, 20dB above 5.4GHz 5dB above 5GHz, 24dB above 7.3GHz Phase noise at 10kHz offset -92dBc/Hz -92dBc/Hz -100dBc/Hz Phase noise at 100kHz offset -108dBc/Hz -108dBc/Hz -103dBc/Hz Input 1dB compression level +0.5dBm (LNA Off) / -26.5dBm (LNA On) +0.5dBm (LNA Off) / -26.5dBm (LNA On) +0.5dBm (LNA Off) / -25dBm (LNA On) IIP3 without LNA +18dBm (at least 2MHz apart) / 0dBm (500Hz apart) +18dBm (at least 2MHz apart) / 0dBm (500Hz apart) +18dBm (at least 2MHz apart) / 0dBm (500Hz apart) IIP3 with LNA -8dBm (at least 2MHz apart) -8dBm (at least 2MHz apart) -8dBm (at least 2MHz apart) Frequency stability <1ppm ( -10⊥ ~ +55⊥) <1ppm ( -10⊥ ~ +55⊥) <1ppm ( -10⊥ ~ +55⊥) SD card slot micro SD card micro SD card micro SD card Audio out 3.5mm headphone plug 3.5mm headphone plug 3.5mm headphone plug FW update mode activation Push jog button before switch on Push jog button before switch on Push jog button before switch on Maximum current consumption 330mA 350mA 400mA Maximum charging current 1300mA 1300mA 1300mA Battery Li-polymer 3.7V 3000mAh Li-polymer 3.7V 5000mAh Li-polymer 3.7V 5000mAh RF connectors SMA female SMA female SMA female Communication Interface USB-CDC(Type-C)ㄛUART-TTL(2.54mm Connector) USB-CDC(Type-C)ㄛUART-TTL(2.54mm Connector) USB-CDC(Type-C)ㄛUART-TTL(2.54mm Connector) Appearance Size 117x72x23mm (Excluding protruding parts) 117x72x23mm (Excluding protruding parts) 117x72x23mm (Excluding protruding parts)
|
|
model Ultra calibration signal issues (and issues on the RF input)
4
Regarding the calibrator output, I have been aware of an artifact. Because I have been doing some measurements (related to the new Fault Finding page, I also decided to catch the artifact now): This is the calibrator at 30 MHz. Every approx. 250 or 400 ?s, the artifact appears. The calibrator output also has a steep negative slope but a rounded positive slope (HW 0.4.5.1): The level is okay, fft midscale dBm reference = -55 dBm, and 10 dBm/div. Hence level is -35 dBm - okay. === RF input === The RF input also has artifacts: It has been verified that the generator is switched off, but it seems that the RF spectrum analysis operation is not affected. Disclaimer: I'm talking about my defective tinySA with defect LNA and quite sure also defective input switch, but it is hard to believe that this sort of artifact would occur just because of this. Rob
|
Image Name
Sat 8:39am
Sat 8:39am