开云体育

You're seeing the round trip time of ~50 ns What does the S21 me

S11 or S21 delay? On S11 2x delay (to cable end and back) On S21 1x delay (from one port to another(

I am having difficulty constructing a set of phase matched cables using my NanoVNA SAA-2N and the tutorial available at this link

Might I suggest that we continue to meet via Zoom on Monday evenings at 7 pm (EST) to share what we know about the VNA? I don’t see my talk as a “lecture” to record and watch. I’m not a VNA

Great, thanks. So you get the same results if the end is either open or shorted right? Reverse the cable and you can confirm where the break is. With a dummy load the cable length should read very

Hello Barry, Some of us in the NanoVNA community actually live outside continental USA. Not sure where your QTH is, but there is also a 5 hour time difference across the continental USA as well. It

One graph shows the Time Domain response of the cable attached to CH0 (port1). The other shows the approximate impedance magnitude |Z|. In the annotated Saver graph below I measured 3M of RG-316

I have been asked many times if these Zoom sessions on Nano VNA were recorded. NO. They were not recorded. The reason is simple: I wanted these sessions to be discussions, not lectures. Many folks

That is truly unfortunate. I am sure there are hundreds if not thousands of people including myself who would love to watch the presentation, but who got late notice or were not available at the time.

DiSlord, Correction: My tinySA shows it on the "VERSION" screen, while the NanoVNA does not. But this is also more a topic deep in the HW/FW - we should discuss this on GitHub. Are you still using

When you click on the TDR in Nanovsaver. The length of the cable is already indicated, which I presume is the physical length once you specify the coax type or VF. There are two plots on the graph,

Are there recordings?

Strange, my LCD screens of nano and tiny do not show any artefacts, only the captured data on PC. But it's only a minimal issue in any case.

Robin, Good hint, should work for the bigger ones now - untested because of the HW not (yet) available. Martin usage: nanovna_remote.py [-h] [-d DEVICE] [-n | --h4 | -t | --ultra] [-z {2,3,4}]

I think this related to LCD driver, on screen capture i read LCD memory and send to CPU (you can see it also on Nano or Tiny LCD at right bottom) Artefact present on all LCD displays based on ILI9341

Martin, 1) thanks for doing this, it's much appreciated. 2) the link below took one straight to the code, where lines 60-64 show: which is OK for an original nanoVNA(-H) or a tinySA. *However*, the

The screen capture shows artefacts at the bottom of the image in the far right column. This is independent of the respective device and the recording program used; tinySA also shows the same

Hi Barry. This sounds like a really invaluable project. It is just too bad that we didn't know about it sooner, so that we could take in all five sessions. Is there any possibility that any previous

oops here is the much better Dummy Load trace Barry k3eui

This is what I see with the NANO VNA standard LOAD (50 ohm dummy load R) Nothing unusual here. de k3eui Barry