开云体育

Thank you DiSlord for helping realize my mistake. I was inputing the stimulus frequecy and instead of pressing the M, I was pressing the x1. 73, John - W7OTD

Thanks again for your help

For a rough and ready cal, for the open, just don't put anything on. For HF, there's not a lot of difference between a connector that's open, and a connector that's missing. It's the short that you

And maybe use fw from dislord... Am 18.06.2022 10:18 schrieb Hugen <hugen@...>:

I am sure it will all work out with a little bit of patience.

If you have any further questions, please check out my website. You may find new information. -- Gyula HA3HZ ( http://ha3hz.hu )

Mike, I'm glad you managed to 'speak' the device. I’ve been monitoring things since the release of NanoVNA and trying to describe this on my web page. Unfortunately, I can’t answer everyone’s

You can use the NanoVNA-App or NanoVNA-saver. https://www.zeenko.tech/saa2

On Stop frequency input you use x1 (input as Hz, not in MHz), so input result 7.3Hz, NanoVNA not allow set this value and set minimum 800Hz Start value less then 800Hz, so and Start value also set to

Hi , some time ago , I solved the proble forcing the installation of the ST driver . Go to location of you have installed the DfuseDemo programa like this on my PC C:\Program Files

That sounds great. Should I put the short cable on for calibration since it will be on for all testing that I have planned?Sent from my Galaxy Tab? S2

Mike, You can just leave the connector empty instead of using the "open" standard. There is very little difference at 1500MHz and below. (This assumes you are using the normally supplied standards

YeeHaw! I finally got that rascal updated and seems to be working right. Now just have to wait for the open calibration cap to get here to calibrate and test some antennas and coax.Sent from my Galaxy

Unfortunately some users have this problem, due to some driver conflict in windows. It has been discussed in several prior message threads - search for dfu driver to find them. It is possible that the

Mike, DiSlords latest release for the -H line is v1.2, found here. https://github.com/DiSlord/NanoVNA-D/releases Download link:

The likely cause of your current issue is that when you upgrade from a substantially earlier version of firmware, you need to "clear config", and then power-cycle the nano. Thus clears the config

Good evening Stan, I have had a UID and PW to STM for several years now and tried all this STM updating the NanoVNA-H4 at least a couple of years ago. I ultimately had a friend upgrade my Nano using

Well, I updated the firmware to the latest version I could find, and that was a joke. This thing is F;;;ed now. Can turn it on but I can’t calibrate the touch and save it. I touch in the center of

Hmmm... sorry, haven't seen this before. Looks like something hijacked your cal to be done at a cw freq of 800, rather than the range you wanted. I would just reset the cal and do it again.

FYI, for non Windows users, the ST Cube programmer works on the Nano as well, but requires .bin files (provided by Huygen).