开云体育

Please can I gently draw attention to this forum front page general rule…..” Please only post content related to the tinySA and avoid all content that could lead to off-topic discussions as I'd

Yes. And my middle name is spelled with a single "l" and the vowel in the middle is an "u". Dave -

Dave, I don't mean to be 'picky' but doing a web search for "Allen Variances" yielded "Allan", so who is right? (yeah, techs like me tend to be that way, fun intended) Mike C. Sand Mtn GA

Yes, in those days we were flying Cs clocks even on commercial flights. Fun days. In the lab I was doing Allen Variances between Cs and Rb. We were finally convinced with all the flights that we had

If you read the specifications for any of the TINYSAs, Eric recommends measurements to remain faithful to the input signal (no compression or aliasing) stay less than -26 dBm. I usually shoot for -30

For best level accuracy, keep the level AFTER the internal attenuator below -25 dBm, preferably below -35 dBm. Below -35 dBm the accuracy is level independent as long as you stay 6 dB above the noise

Thanks Stan - that fixed it. Correct driver now installed.

Erik, thank you for your rapid reply. Is there a sweet spot (power level range) where the tinySA is most accurate? Reflecting on the situation:? I only need to know a power range of 20-30dB where

You have the wrong windows driver for use with tinysa-app.? ?Please see the document at the following link, and it will show you how to install the correct driver.? Note that tinysa-app is derived

On some windows systems the program fails to open the USB device when the name starts with \?\ Better use the dfu-util for upgrading. -- Designer of the tinySA For more info go to

[email protected]> wrote:

PS; Or you are trying to load your NanoVNA H or H4 using the software for updating the TyniSA? You either need the FW for the TyniSA instead of the NanoVNA or you need the correct software to update

Just purchased a tinySA ultra from the Zeenko store, so it's genuine, and I can't upgrade the firmware. 1. Running on Windows 11 2. Have installed STM32 drivers 3. When I go into DFU mode I see a

We had to do that here at the University of Illinois, too. Back in the early 70's we were doing some ionospheric propagation studies along with the University of Houston. We flew two cesium clocks to

Back 'in-the-day' I had to carry (transport) the 'flying clock' from Northwest to White-House (no not that wh house) to establish the exact 'phase' error for the ROTHR (Relocatable Over The Horizon

Early tinySA firmware was not very good at avoiding compression with strong input signals It is easy to check for compression Switch to manual attenuator mode and increase attenuation above the auto

I'm building a 1kW+ HF power amplifier.? I've a 2kW homebrew dummy-load with a 60dB PAD (measured with a nanoVNA it's around 60db flat to 100MHz). With an IC7300 at 100% FM, 7.2MHz, the tinySA reads

Which is why I wrote it as "milliHertz". MilliHertz just would not be right. :) "W0LEV via groups.io" <davearea51a@...> wrote: -- 73 -Jim NU0C

Yes. mHz is needed to "compete" in the FMTs. However, we should use correct abbreviations for the units. Having once been professionally involved in precision timekeeping in the early days of GPS,

We all like to poke fun about this but if you ever participate in the FMT you actually do need milliHertz precision to get into the "green box". "W0LEV via groups.io"