开云体育

Perhaps we don't want to see theirs. These are not just used in the European market or counties. I am sure Erik does not want to lose the US and other countries just because someone in Europe might

Would be nice if able have a switch to select either US or EU/UK ham bands at user preferences.? Dont know how much trouble to do that but Erik is a master at making updates when possible. Thank you

:-) Maintaining code that was originally written by someone else would not be at the top of my list of things to do either.? I'm happy the shared code base for NanoVNA-App and TinySA-App allow users

I will not change the ham bands except to make then part of the config and editable using console commands. -- For more info on the tinySA go to https://tinysa.org/wiki/

And therein lies a problem for Erik who tries to satisfy everyone....perhaps the EU/UK do not want to see the expanded US bands.

Please don’t forget to expand the HAM BANDS to include the U.S. allocations. Thanks!

My error, the previous keypad will return Thought yes, but too many projects at the moment and working on tinySA-App is not my favourite job, to say the least -- For more info on the tinySA go to

Hi Erik Now firmware numbering is running backwards 1.4079 was issued on 25.03.2023 Kind regards Kurt Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek Sendt: 30. marts 2023

Hi Erik Besides comment from Herm there is no longer possibility to enter negative values and above 5.34GHz calibration now produces error messages as of too low level or incorrect frequency Kind

Erik, I've been doing my frequency correction at 1GHz and entering the correction in ppb.? Does the new k and M modifiers mean the frequency offset is now entered in +/- Hz?? If so, what would be

New FW release Version 1.4078 Changes - AUTO NAME is off after a clear config - Frequency correction keypad now includes k and M modifiers -- For more info on the tinySA go to

Here's a link by the same author for release notes for the tinySA 2.8" ... /g/tinysa/message/10037 ( /g/tinysa/message/10037 ) Herb

Couldn’t agree more with everything hwalker just said above. thank you for taking my request of 10 grid lines to a vote and making such a fast firmware upgrade to implemented it. I’m flabbergasted

Thanks, Herb. That looks like release notes for the Ultra. I don't have an Ultra. But do appreciate the response. I will look them over anyway as I might get an Ultra later.

Just as a hint: When it comes to measuring FM deviation with a spectrum analizer or an (already existing) SDR, then these three word should ringing a bell: "Bessel Null Methode" There are some nice

The tool must be adapted to the purpose, but the bottom line is to get new FW onto the tinySA without damaging the device or the PC.? And if Windows is too much of a hassle, you can also use Linux on

I'll leave the 9600 baud until later!? All of the radio's that we would press into 9600 baud service either have a port wired from the factory or are easily modified based on documentation (like the

Hi Vitaliy, Your problem sounds somewhat similar to a problem I previously had, and below is the copy of my posting that documents my solution. ———————- Thought I should close this post

I'll give a go.? Thank you.

I've been reading this thread and haven't put in my two-cents yet so, for what it's worth, here's my two cents . . . I use both a Dell laptop with Windows 10 Pro and a Dell desktop with Windows 10