开云体育

I have thought of this as well, but what they have done actually follows the practice used on many commercial test instruments. I would like to see them make the box green if on or gray if not.

I wish that Saver would not automatically change the H4 when it connects. I think the sequence should be to read the H4, and then we can change Saver and send that to the H4. Not sure how to do that,

I saw a post about problems with Saver, and the ini file, so I renamed mine, and ran Saver. I have a cal that is reliable. The H4 shows the proper e-delay and phase change for an SMA adapter and for a

I suggest that all buttons that can change state - show the state that they will change TO, which is what we expect when we see a button of any sort to press TRANSFORM ON - should turn on transform

U.FL connector mating cycles (from recent personal notes) U.FL plugs and sockets. I just finished giving an intro lecture to NanoVNAs using these connectors. Went very well. I had read all the

SMA connector mating cycles (from personal notes)(just an opinion; we've all got them ;-)

Rudi (DL5FA), As Larry said, this is a goldmine of information and education especially for those of us who are not RF engineers by training but whose education and work-life intersected heavily with

Hi, It is a long time ago now that you experienced a startup error of NanoVnaSaver. I do not know if it still actual for you, but recently I had the same startup problem with this application.

Rich, I wonder how your testing has gone with the NWDZ RF test board. I measured all the test positions and it was an interesting exercise. The quality of my NWDZ board was quite good. The SMD

I did a new cal on the H4. It turned out as before, so the old cal was good. Here are my notes. H4 phase 1.5 after cal, no cal devices attached. w coax (75 VoP) extension, 1475 ps delay to correct,

thanks for confirming ~R~

Thanks...I was using an existing cal, and was resetting the delay to zero before connecting with the software. It makes sense that the delay will be sent to Saver if Saver uses VNA calibration. I was

I attached 3M of RG-316 to a NanoVNA-H4 and used the TDR function to calculate the round-trip delay. It measured 29.5 nanoseconds. Then the offset delay was adjusted on the NanoVNA until the S11 phase

Tested NanoVNA-H4 with Saver Version 4. Offset delay works OK - same as version 3.10. Note S11 phase is flat after delay added.... Roger

H/H4 firmware by default apply internal delay if set and after send it ti CPU. You must reset on device before use Saver software.

In your image, I see -1540 ps of correction. The value agrees w a VoP of .66 and .305 m of coax. When do we expect to see a negative angle? I cal'd with ~175 mm extensions, then when I ran the test

Just tested -App v 1.1.208 It needed -1750 ps where I expected the same. It is interesting that I calc the delay based on one way, but the H4 displays it as round trip.

I ran a quick test this morn. Don't have time to investigate, BUT nVNA-H4 v4.3_MS, firmware 1.1 Saver 0.3.10 Seemed to work better than 0.4, but still puzzling. On -H4, I corrected by -1750ps, as

I just tried this again ... and it worked. The difference? I have no idea. As a note ... my high end Tek VNA measured the "test awful load" at 57.91+97.35j (|Z|=113.27). The nanoVNA, with applied

/Sorry, no text. /I happened to have the opportunity to measure the same as Roger did when I read this post. Exactly the same measurements made (from 50 kHz to 50 MHz). Calibrated with SDR-Kits BNC