开云体育

Hi Kurt Poulsen, I understand you, but something is false. Best way the fully calibrated instrument. But if not available, for example if can not do osl far end calibration port extension useful. This

Hi Rune and others First of all thank you for keeping the NanoVNA-saver a clean product sticking to "transmission delays" only all the way thru. For S11 reflections the "transmission delay" is

If * CMC means Common Mode Choke * connections are e.g. Fig 3 (a) in http://lib.tkk.fi/Diss/2009/isbn9789522481870/article7.pdf * CH1 was first calibrated without CMC then that will yield transmission

all of these versions jitter all over the screen for the first few mins,none show the marker in the smith chart,anyone else get this?,im on win7sp1

Hi Rune Very probably ? Regarding the comment where to place the field for delay adjustment so the calibration window does not shadow for the displays of data it is logical to have it under

When I use CH0 then LOGMAG is reflection loss (in dB). But if I use CHO/CH1 to e.g. check a CMC and I select LOGMAG for CH1 is it then true that LOGMAG will show transmission loss? Regards/ Torbjorn

Simplest is to connect 5 volt to the "OFF" position of the power switch. Easy to solder at the side of the PCB Now you can switch the nanoVNA on by switching it on -- NanoVNA Wiki:

Hi Bob Based on your description, you should read on "NanoVNA does not want to start-solved", I hope that what you have written there will help you. Use the "Search" window. 73, Gyula HA3HZ

Kurt and Roger, thank you for the correction! I'm sure I've messed up the conversion from picoseconds to seconds :-) I agree that shifting to the end of a cable using the delay is not very accurate -

Thanks the new version, experimential port extension very good news. Of course, loss compensation option(s) requied too. But math not easy, now next entry level is easy. Good start point to advanced

I tested it on arm-none-eabi-gcc (15:4.9.3+svn231177-1) 4.9.3 20150529 (prerelease) The latest github version can fit into memory with all commands enabled, just out of the repository.

On Wed, Dec 4, 2019 at 03:09 PM, Kurt Poulsen wrote: Kurt and Rune, I found the same thing as Kurt. I had to multiply the delay by 10. I have connector savers on my NanoVNA. They add a delay of 52 ps.

Well, if this is only for your own personal use, I would suggest you can begin removing all the help text and associated code, incuding the info text.?? Afterall, you already know how to use the

There is no need to download from the Play Store.? Go to GitHub/cho45 and download the release directly from the releases section then sideload it on the Fire tablet.? Here's the link:.? ?

That doesn't happen here.? Perhaps it's the version you are using. Bob

Hi, I got this: ..... /usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: build/ch.elf section `.data' will not fit in region `flash0'

I have a problem that the 5V input to the vna is shorted.? ?I cannot charge the battery.? So I tried charging the battery from a power supply and all works ok. I opened the unit and unsoldered the

Hi Rune The dealy to enter is by a factor of ten. E.g. if the measurement plane has to be shifted backward to the calibration plane by 50.7ps the I must enter -507ps and this the sign is Ok. I used

find some instructions to install the Google Play Store on your Fire then install the NanoVNA app right from the Play store profit!! used it on a repeater site last week again

Tom, the nanoVNA goes to 1500 MHz.? Just key in that frequency in the Stimulus menu. BobK6DDX