开云体育

A long time ago I spent too much time going around just getting the part. They cost more back then when money wasn't worth a lot. Recently I needed an attenuator and went to Amazon. They seem to have

Official name SMA connectors. https://www.ebay.com/sch/i.html?_from=R40&_nkw=miniature+SMA+coaxial+connectors+termination+load+50+Ohms&_sacat=0&rt=nc&LH_FS=1 Please note how many are being

https://www.amazon.com/gp/product/B08N4DHJHS 73, Willie N1JBJ

OK, I will freely admit I have no clue where I put the ones which came with the unit. Secondly - I am not looking to measure stuff to 3 decimal points precision - I just want to see the "resonant

For HF frequencies the effect of resistor lead inductance will have a very small affect on calibration. Roger

So a 50ohm metal film probably is going to be a horrible choice for calibrating my NanoVNA on HF at the end of a coax run not terminated with a coaxial connector (terminated with lugs to fasten to my

Carbon film resistors are made by depositing a thin carbon film on a substrate, and then a laser cuts a spiral into the film to achieve the desired resistance. That spiral cut will make the resistor

It will be a few days before I get home. Would you be kind enough to send me a good email address to which I can send a link. I’d rather not publish it here on the forum. My email is

Zack, You also need a good test jig when making these measurements. What are you using for your tests? Roger

Not hard to imagine that a nichrome wire wound power resistor will have a lot of series inductance. Metal film resistors are carbon ink coated ceramic forms. After firing they are trimmed to value

Hi. Same here !! Appears 27-30 mhz I have nanovna-f from deepelec. Is not problem of the firmware Humm. Nanosaver bug ...

All of my gear is in storage so I can't test ATM but if I remember correctly, upon first connect it does not detect the version string that it expects, so it newer runs the get_running_frequencies

Ward, if you have something that I can beta test on my NanoVNA H4/V2plus4 I‘m very willing to do that Uwe.

If i correct understand problem in loaded from NanoVNA start/stop range? NanoVNA Saver not correct do this if not detect VNA: Here this code: def _get_running_frequencies(self): ''' If possible, read

That is a quirk with Saver when it can't detect the version of NanoVNA. Disconnect / connect fixes it on occasion.

The same behaviour, on a quick test, appears under firmware 1.0.53 DiSlord, nanoVNA Saver 0.3.8, running Python 3.7 in a PVE on Ubuntu 18.04. If the latest DiSlord firmware would seem to deal with the

Thanks Barry. It seemed like an excellent job to me for my low knowledge. This has clarified issues that I could not understand. Jose EA7GAH

Original NanoVNA 2.8" screen https://github.com/hugen79/NanoVNA-H/releases/tag/1.0.45 Linux Mint 19.3 Python 3.7.5 NanoVNA Saver 0.3.9 When NanoVNA Saver connects to device Sweep Range always defaults

Thanks again everyone! I've watched several of W2AEW's videos but hadn't seen this one yet. 73, David, K2DBK k2dbk.com twitter: @k2dbk

David, I have been following this thread and thought I might add something that might help you. This link that I have attached should give you an easy way of making your Short/Open/Load standards