开云体育

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

Hi, Now I have a VBAT: 4024mV, and measured after the diode: 3963mV. I don't know where I can enter vbat_offset. Can anyone "lead my hand"?

How would that error impact your other VNA?

I did. The resistance is a bit of and there is some capacitance. Do you suggest to add that capacitance to the cable? But that capacitance is already there in the open calibration? I'm not quick in

How about measuring CH0 impedance by another VNA?

I already did The same cables measured in the same way at another vna do not show these oscillations. Even though the same calibration kit calibrated perfect on both vna's. They must be specific for

Using the open for calibration also at the end of cables could eliminate one variable.

on the other end of the "scale" ..someone gifted me a HP Stream (2018 model) ...running Linux Mint 19.1 ..has more than 10 g freespace left on solid-state fixed drive (if you don't want to mess with

Setting power to 1 removed most of the noise and also the jump when switching to harmonics mode disappeared but it also resulted in yet another different oscillation pattern above 600MHz. For

Yes, there is a newer operating system available for your computer:? Linux.? Windows Vista is out of support and no longer updated, so, if you continue to use it, at a minimum you should keep it off

Rune, Yes, I did set the nanoVNA to non-TDR mode before making the readings. This is essential to getting good data in nanoVNA-Saver from the nanoVNA. I recalled cal0 which was created with my best

Has anyone tried it lately? YT9TP - Pedja could not calibrate over 310MHz on Oct 22 /g/nanovna-users/message/5510

Given custom NodeMcu/nRF5 firmware, nanoVNA need pass only 101x2x4 bytes of float per scan, which could then be converted to ASCII by BTLE micro for USB COM compatibility.

Hi, Maybe this in interesting for you: https://github.com/reald/NanoVNA 4 traces, big font, big info screen, 1500 Mhz, battery indicator https://github.com/hugen79/NanoVNA-H 2 traces (AA version), big

Dana, Indeed, and for that reason I measured the same cables with the same calibration kit on thee different VNA's. (one the nanoVNA) The results from the 3GHz VNA convinced me the fluctuations seen