开云体育

Hello, This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group. * /NanoVNA Console Commands Oct-7-19.pdf

Are there any *firmware* releases that have support for *proper* calibration kits? By that I minimum of * offset delay of the open * offset delay of the short. * C0 of the open More parameters would

Hi W5DXP (and others) - Help for use of FORMAT options is wanted. I know a little about LOGMAG, PHASE, SMITH, but: * when to use others? * what other settings interact?

On Mon, Oct 7, 2019 at 04:03 AM, Kurt Poulsen wrote: Kurt, Thanks for your more detailed explanation. I think I understand the "trick" you are suggesting more thoroughly. It certainly makes a

Erik, Your release 0.2.2_1 may have a bug with the 'capture' console command - device locks-up when I try to use capture. Regards, Larry

Good afternoon nikolitsa oe3zgn|sv7dmc & petros oe3zzp|sv7bax @ arg iaoi nfi; As I stated in an earlier post, our communications get somewhat contaminated in translation. Please understand that you

I have been unable to upgrade the firmware on my NanoVNA on Windows. Every approach I try ends up with the DFU tool claiming that the file I'm trying to program is the wrong format. I pointed to

Hi W5DXP: I notice that your PNG lacks recent TRANSFORM update. Tricky CSS in https://oristopo.github.io/nVhelp/html/Vnano.htm automagically draws menu tree leaves, branches and twigs by redefining

Thanks, just need to find the DFU programming software now.

How about this?

Please remember that with rapid S/W development, there will always be some kind of niggling issues somewhere in the code. To be safe, you can stick with releases from either edy555 or hugen. Erik also

When I heard there was the ability to extent the range to 2.5 GHz, I got over exited. Because I'm not forking out $800 bucks for a Analyzer. So which build do you recommend?

IMO, most danger comes from potential static discharge when jumpering DFU contacts. Firmware bugs may leave nanoVNA in hung state at power on, so forcing hardware DFU is an ongoing requirement. I and

Please DO NOT use that firmware - it was purely experimental and was indicated as such when Erik talked about it.There will be no support if you have any issues. However, it you DO want to play with

TRANSFORM submenu https://oristopo.github.io/nVhelp/html/Vnano.htm

37 : The [LeastVNA] @Gary O'Neil - 6 October 2019 : /g/nanovna-users/message/4194 35 : Straight In The Heart of The Matter - 6 October 2019

Sorry for the stupid question. But a recently saw a firmware update with the ability to go up to 2.5GHz freq. But I can't seem to find a solid wait to upgrade on windows. How would I go about

Ciao Roberto, I wish I had the time to look at the code but my 'real' job keeps me very busy. :-( The developer of the firmware you are using might be reading this group... or might not. It's good to

Hi aa_talaat, Your smith plot, using linear sample points, is similar to expected results using a Simsmith model. First straight line caused by very wide sample points. SimSmith model is shown in:

FWIW, I don't think DMR-CLEAR_MEMORY_DFU.dfu helps unless some desired firmware otherwise fails to load.