开云体育

Hi Marc, Just a heads up. It is possible that static on your antenna crisped your NanoVNA. It is really good practice to short your antenna cable before connecting it to your Nano VNA. Also be very

John, Are you sure that your phase trace is looking at S21 phase and not S11 phase? --John Gord

I'm running into an issue trying to calibrate my NanoVNA H4 so that I can run S21 scans. I've done the calibration two ways: (1) using the NanoVNA-saver software and (2) using the on-screen menu on

The standards by their nature are delicate, as the manufacturer attempts to minimize parasitic capacitance/inductance. This often results in mechanically less-than-robust construction. This mechanical

Thanks, The question is which statement in the manufacturer's brochure is incorrect. But the "other cable" is the one that came with the NanoVNA and it worked a few minutes prior to the point at which

Hi, In point 8 you say that the new cable is identified as a "charging cable" and this type of cable is only for charging but not for data transfer. After that you say that in the description they say

hah, and I just sent a suggestion - yeah, it happens. And to someone with your callsign, how ironic. I've had more than one 50 ohm load turn into an open - or what's worse, 50 ohms at high

If you clear the calibration (reset), so it's totally uncalibrated, what does it show? It should show S11 fairly low with a load, and close to zero with either open or short. If it does, then check

Chronology of the Problem 1. Unpacked NanoVNA ordered from eBay vendor as a non-H unit, powered up and operated, including calibration, configuration, and testing an existing antenna system until the

I would think that someone with a call like yours would have checked the load first! (Just kidding!)

Thank you Owen Duffy for an off list suggestion. Turns out the 50 ohm load had failed open circuit, so it was not calibrated. Replaced the load and now working perfectly. Who'd have thought one of

I suggest you do a Clear Config before you calibrate. Also remember to Reset before you do the calibration. Check your cal loads and make sure they measure open , 0 ohms and 50 ohms. Then cal and when

Thanks for all your assistance - I'm pretty sure my NanoVNA has a serious fault. A new one is on order. I checked the antenna with a SARK 110, and got exactly the result I expected, so that eliminates

This is the third Topic generated during my trip along the path to becoming a NanoVNA user. In the first I described a problem with getting the NanoVNA to be recognized by my laptop running W10,

I have done the calibration a few times so I think it's OK. Leaving the NanoVNA connector open gives an SWR of 1.183 right across 1MHZ to 40MHz. I think it's broken. I have measured a different

Feedline is ~30m of RG213. Not really practical to disconnect coax at antenna as it's 15 meters in the air. This NanoVNA has correctly measured the SWR 2 years ago. I think it has died.

Apparently my use of the (Bricked?) description was confusing, and I apologize. I am going to open a new thread with the subject "NanoVNA not recognized by computer after upgrading Firmware with DfuSe

I found these two latest messages in my DRAFTS folder. Apparently I ever sent them, IDK how that happened. I apologize if these unsent messages contributed to the confusion.

The time from working with the original fw load and not identifying as a DFU unit was literally minutes, on the same cable, computer, software and drivers. The Version Page of the hardware with its

OK, synthesizing Stan and Tim's replies with what I read in the STM device data, From STM RM0091 Sec. 2.5: Under normal circumstances (Boot0 pin = 0) the device will boot from Main Flash Memory. I