开云体育

Nothing in TDR apart from the reflection at the end I'm using a 1000 point calibration exactly matching the measurement points -- Erik, PD0EK

For Vista, v2015-14.0.24215 is wanted according to this: https://www.vistax64.com/threads/i-cant-run-some-exe-files.305497/#post-1412479

Before finally dismissing them, does TDR show some reflection at 3x cable length? If yes, then calibration does not fully compensate CH0 mismatch. Also, calibration for 200-900MHz stimulus will make a

I successfully started nanoVNA-Saver when I installed the SP1 service pack and Ms VC ++ multipack on windows7-32 bit. When I tried to install Python on a machine that didn't have it, but I didn't know

Measuring the same 25ohm resistor connected in the same way on my three VNA's . All three have been calibrated with the same calibration kit and show perfect calibration. (SOL at -1,+1,0 for all

Here is definitive evidence there is something to be improved in the nanoVNA design when measuring at higher frequencies (above 300MHz) DUT is a 25 ohm resistor close to the reference plane with a

Coaxial cable loss frequency depend. Higher frequency higher loss. But swr 3 with low or high impedance not same loss. Simple model not support this. Advanced model good. Now attenuation / frequency

Simple (dB/m) and advanced (k parameters) coaxial cable modell exist.

Does not fully understand this forum. Cable loss compensated? I see big errors from cable loss. Lossy coaxial line not circle on smith diagram. It s a spiral. I see electrical lenght compensated, but

Thank you, Just flashing using latest AA version from https://github.com/hugen79/NanoVNA-H 2 traces is enaough for me.

Port 1 mismatch is already corrected for by the usual SOL 3 term calibration. The only things left that it *doesn't* correct for are linearity error (e.g. signal source's output power changing

No problem, we're all here to help each other.? On Wed, 6 Nov 2019 at 7:05 PM, QRP RX<qrp.ddc@...> wrote: Larry Rothman, sorry. I opened groups.io, found question which I seen in email and

Just FYI and to keep with the original post. I have manged to extract multiple "projects" from simply cloning the original Github repository. So part of the goal is done. Now I have to figure out

I tried to create V 0.1.5 for my mac, OS version is Catalina. I got an error message trying to install scipy… I think scipy was new for v0.1.5? Has anyone else encountered this? Dana VE3DS

Larry Rothman, sorry. I opened groups.io, found question which I seen in email and wrote answer. Just didn't noticed that I replied on your answer :)

QRP, that is not my quote, below - that is from the other member whom I already explained what you just did as well....? just connect to your NanoVNA with PuTTY and use command "vbat_offset" This

just connect to your NanoVNA with PuTTY and use command "vbat_offset" This command will change battery offset until power off. In order to save current battery offset permanently, use command

You need to connect the Nano to a terminal session on a PC and use the console command vbat_offset [xxxx ] where xxxx is mV of offset.? Hi, Now I have a VBAT: 4024mV, and measured after

Hi Bryan, thanks for the Touchstone files - I'll have a look at them, and see if I can figure out what's going on. :-) -- Rune / 5Q5R [email protected]> wrote:

Hi Doug, as others have indicated, I build NanoVNA-Saver executables using the very oldest build environment I can get from Microsoft - namely Windows 7 32 bit. Mainstream support for Windows Vista