开云体育

I have a nanoVNA with USB-C after charging, I turn it on without the USB-C power on, it turns on fine, but turns off again after approx. 30 sec. - but run with USB power plugged in, does anyone have a

Thanks Erik, I admit I was puzzled because its obvious that the nanoVNA has only limited memory storage and can only accumulate so many data points. I was guessing by Hugen's use of "segments" that he

Bayonet Neill–Concelman https://searchnetworking.techtarget.com/definition/BNC

Indeed. That is what I hoped but when I inspected his code I saw he did not copy my code but is using an array to store the frequencies. The frequency array has only 101 items

Bayonet-Neil-Concelman, after the inventors.? On Sat, 28 Sep 2019 at 18:21, hwalker<herbwalker2476@...> wrote: Bear, From my years in the military I believe BNC actual stood for bayonet

Bear, From my years in the military I believe BNC actual stood for bayonet connector (hope I spelled that correctly). Herb

Years ago somebody theorized that BNC stood for Baby N Connector. It's kinda similar in some ways. Bear W5VZB

I can't afford one either Herb but, thanks to the nanoVNA being so accurate, we don't need a FieldFox - at least for HF. We'll see tomorrow how the Nano does at higher freqs.

Erik, The latest edy555 release says the scan command supports more than 101 points: 0.2.0-20190928 edy555 released this 4 hours ago in-device TDR support (contributed by @cho45) add scan command for

John, Thanks for the comparisons. Until I can afford a Fieldfox N9913A (like never!), based on comparative results like yours and my own end user tests, I'll trudge along happily with the NanoVNA for

Hello Norbert, thank you for trying out the software! The VSWR plot is set by default to only show values up to a max of 25 - and the "draw lines" command isn't *yet* clever enough to draw a line to a

David The scan command implemented by edy555 can scan max 101 points. I tried to convince him otherwise but failed. Erik PD0EK

Hi Peter, after much popular demand, it's now hiding at the bottom of the readme on the GitHub page. Also available at the bottom of the "project homepage" (which is a nice looking version of the

Sounds good! If your firmware has similar / compatible commands, there shouldn't be any problems with it. I can't vouch for future releases, of course, as I develop for the NanoVNA I happen to have

I utilized an attenuator and a band-reject filter today to compare results of the nanoVNA with a Keysight analyzer: https://ae5x.blogspot.com/2019/09/nanovna-vs-keysight-n9913a-at-hf.html The results

It may be that there is a problem with my statement. We are currently testing nanovna-saver and nanovna-f, and it seems that they do not need to be modified to be compatible.Of course, we don't want

I do wonder whether with all the changes being proposed, you'll end up with something so expensive and esoteric that no-one will be able to afford it! Multi-board, plug-in processors, exotic

I'd have wished they'd contact me about it instead, but as it's open source, they are of course free to use the code. I may need to make sure they don't reuse the name, though, so there isn't

On Fri, 27 Sep 2019 at 20:00, yza <yzaVNA@...> wrote: 19 : "true value" - also : @Dr. David Kirkby : > /g/nanovna-users/message/3207 > > Hello, > > We both thank you very much

The NanoVNA firmware (as I understand it) assumes that the SMA Short, Open, and Load standards are ideal, with the single exception of defining the Open to have a C0 50 femtofarads. I was wondering --