开云体育

When I study the ultra with version 187, and use measure->more->THD, whatever I move the marker, the THD always 0, can someone give me some suggestions?

New FW release Version V1.4189 For ZS405 (original tinySA Ultra) and ZS406 Changes: - Bug solved: TinySA-App can not control tinySA - Improved level correction table for ZS406 WARNING: This FW update will do a clear config and can not load previously saved configurations and settings -- Designer of the tinySA For more info go to https://tinysa.org/wiki

Tiny Ultra SA purchased from R&L has worked flawlessly for many months. While checking bandwidth of my oscilloscope using the Tiny Ultra as signal source it failed when I Tee'd in a 50 ohm input frequency counter. It failed within seconds of the counter attachment. The Tiny Ultra had a DC block attached at the time of failure. It now fails Self test 3, signal level fail. Below is the check of the attenuator as described for Tiny SA Signal generator partially functions, 100 KHz at -20 dbm, should be 22.4 mv RMS. Sine wave is distorted from what it was when working properly A 50 ohm termination on this signal results in flat line, zero volts ! Below is 2 MHz at -20 dbm 900 microvolts RMS, At 3 MHz the signal is around 400 microvolts RMS and at frequencys higher than 3 MHz no signals are seen. Below is in spectrum analyzer mode. 100 Khz from Fluke 6060B signal generator at -10 dbm. Any ideas on what died?

When I was (playing) testing with my Nose source noise source and TinySA, everything was fine at lower frequencies, but when the max frequency was 5GHz, there was a 10-20dB step at 3GHz. I don't think noise source does that, but I wouldn't think TinySA would do that either. I ran calibration after this and as always it passed. Should TinySA Ultra be calibrated before use? Yes, in the noise source PCB, there is a text NOSE SOURCE. Bg7tbl 2016-03-06 By the way, the noise source runs very hot at 12V. Amplifiers in it may do something extra. https://www.eevblog.com/forum/testgear/_nose-source-bg7tbl-2016-03-06_/

I was browsing TinySa examples from https://tinysa.org/wiki/pmwiki.php?n=Main.Mixer TinySas where directly coupled to each other. May I ask, does it really work and can I make one TSA to output the same frequency other is measuring. I am not rushing to buy a second TinySA, but this is interesting.

I am using Tiny SA- App v1.1.20.1. I watched several videos about this the Tiny SA and I did a search on all the prior messengers here. I don't see a solution – How do I make this software work with ultra frequencies? What does work with the Ultra frequencies is the screengrab window – but not the big window. I'm sure this is a cockpit error and I am simply overlooking the setting or switch for this. PS: bonus question: is this the best software to use to upgrade the firmware? When I click on the icon at the top for Firmware Upload, all the instructions discuss the Nano VNA. -- -.- ...-- .-. .-. .-. 73 de Robert K3RRR X/(Twitter) @K3TripleR YouTube.com/K3RRR Website: K3RRR.com -.- ...-- .-. .-. .-.

Hi Eric and everyone, Happy Holidays Updated my two Ultras ((from Zeenko), to ver 191. No issues and everything works as expected. However, I happened to notice an unusual spur on one unit that did not occur on the other one, This with no input, and both inputs terminated, and the units placed next to each other. They both showed the internal spurs that normally have occurred that will come and go intermittently (Spur removal is ON in both units) . In the plot pix below, both units are in MAX HOLD and left tracking for several minutes. FIG 1 is the unit with the substantial intermittent spur of substantially higher amplitude at 3.995GHz that only occurs on this unit, the other marked spur positions are normal (seen all the time at the same spectral positions on both units) that come and go, as does this bad one. FIG 2 is the other unit showing the normal spectrum with the inputs terminated. FIG 1 tinysa4_screen_2024-12-23_15-51-37.png FIG 2 tinysa4_screen_2024-12-23_15-55-01.png Not a big issue to me as I don't often work in the affected band, but I'm just curious as to what might be the source of this. It's internal to the unit and not picked up in the environment as it doesn't appear on a non-ULTRA analyzer.

I want to use the square wave signal from the cal output to measure my scope's risetime. When I loop back the calibration signal (30MHz) and measure the harmonics with SA ultra, I see some deviation from the expected 1/N amplitude. Since this output is used as level calibration, there must be some correction done during selftest to correct the limited bandwidth. I don't have any RF measurement equipment other that the TinySA Ultra, hence the question :-)