开云体育

You have the latest official version from Hugen. https://www.zeenko.tech/litevna?spm=a2g0o.detail.1000023.1.5861433fFOpOSx DiSlord has made many updates to the firmware since then. Try joining this

I received my LiteVNA today and calibrated it right away over several frequency ranges, one up to 6 GHz. I checked the response of a 1.3 GHz and a 2.3 GHz microstrip LPF and a 2.3 GHz microstrip BPF

I am still unable to get the nanoVNA to assign a port. I have Windows 10 and the nanoVNA will not automatically assign a port and the program suggested above does not assign a port. When I place the

Hi to all, I am new to this group. Thanks. I was using mi nanovna-h , hardware ver. 3.5 , with dislord 1.2 firmware. All went fine till i had the bad idea of changing the firmware to Hugen version

Same experience with their headphones. Great price if they’d last more than a week.

Correction to last post. One of the Short plots was mislabelled. Corrected versions attached. Roger

YES there is something wrong with NanoVNA app calibration routine when using longer cables. I did some experiments with the original OneOfEleven, DiSlord and Duffy versions and all gave poor results

I've noticed that with some of the cables I have purchased from Dollar Tree also, but mine are two or three years old, maybe more. Some are plugged into and unplugged from the phone or other devices

I do intend to use those adapters at the end of the short bits of coax that came with the unit, rather than stressing the conn

David, There are two different drivers required when using a NanoVNA-H or NanoVNA-H4. One is required to get a COMxx: port so that your PC can exchange data with a NanoVNA. The other driver is

Could someone be so kind as to reproduce this measurement at his computer, on his copy of the NanoVNA-App, with his NanoVNA and his cable of several meters? If the result is good, it means that I am

Hi Don, Wow, what an insight that document is. The comment on SMA connectors is very telling : "These connectors do not work well in applications that require repeated connections; they wear out

Just a Thought. Perhaps it is the dreaded 5351 clock instability around 300MHz. The "900MHz" 3rd harmonic being my thought here. Try setting the Threshold to 280MHz and Clear all the calibration data

David, Here’s the link to the one I used. https://www.st.com/en/development-tools/stsw-stm32080.html

Can you give me some more information on the STM boot loader and a source to download? Thanks for your help!! David

Under-torquing an SMA (or any connector) will extend its life but compromise repeatability. For quick-and-dirty at HF finger-tight is fine, Above UHF one must be more careful and so on up into the

YES that is very old firmware. Many bugs and improvements to the firmware have been made by DiSlord and Hugen. If you update the firmware in your -H to a recent version you will get the binary

Could the problem be, an RP-SMA cable. Been there done that! Richard K8CYK [email protected]> wrote:

Roger, My NanoVNA-H has v.0.2.3-2-g8ac9166, (not sure of the "g"), dated Build Oct 10, 2019. Does that fall into what you call "old FW"? If so, Don't know what is involved in gaining "the required the

I don't use NanoVNA-App, but if I recall correctly, the short and open standards can be defined with an offset (as opposed to "ideal" with no offset). How are they defined in your setup? If they are