Robert Mueller 2021/04/26 14:55
First of all, thanks for the advice on this, However, it interestingly
more complex than it originally appeared. When I first wrote I was using a
ThinkPad running Windows 10. Even with your advice I have basically been
bumping my head against a wall. With a newly installed Cypress driver,
rebooting, and after installing the VNA_QT software (again and again, just
in case), I gave up (temporarily) and I went to an older HP laptop and
after loading the vna software followed by the recommended Cypress
software, the first try worked! This runs Windows 7, and Not Win 10. I
have no idea whether the problem is the operating system or some difference
in the firmware of the two computers (I cannot believe the hardware is a
likely cause) but the difference in behavior is interesting. If somebody
can figure out what is critical maybe this can help others to get past any
similar experiences., or warn them to fall back on an older computer if
worst comes to worst with a newer model and operating system. One can
wonder whether some obscure setting in the Windows 10 is making trouble
here although it is harmless or beneficial in other cases. Anyway, your
advice was the basis of getting things running.
One other thing is that I suspect some slight tweak in the vna could
prevent such problems; I run several quite different devices on the
ThinkPad with no trouble. I should add that I also have an older vna
(probably a clone but I am less than sure of that) and the ThinkPad did not
agree with that either so that old device always ran by itself. Now, on
the HP it also instantly started to operate. Too bad, because the Plus4
will totally replace the old one because the measurements will be better,
leaving the old one as a gift or backup doing nothing until something fails
in the better model.
That was long but if it helps anyone recognize a similar situation it will
be worth the effort.
On Sun, Apr 25, 2021 at 2:24 PM OwO <OwOwOwOwO123@outlook.com> wrote:
> If NanoVNA-QT won't connect but the device shows up in device manager,
> then it is a driver issue and usually reinstalling the Cypress driver
> (and rebooting) should fix it.
>
> If NanoVNA-QT works fine but nanovna saver isn't connecting on windows
> 10, see if this firmware update fixes it. I suspect nanovna saver might
> be looking for the old device strings, which used to be "Black Sphere
> Technologies" (the default in libopencm3). I had changed that after
> someone in the discord chat suggested I rename it (as it could be
> confused with the Black Magic Probe), but I didn't think it would break
> some software. The new firmware reverts this.
>
>
>
>
>
>
>