开云体育

Remember: Whinders is inherently low quality, and tends to get things wrong. *Always* question what it claims!

I have finally solved my problem and have successfully updated the firmware on my NanoVNA H4. Thank you to all that made comments that helped me. In the end I deleted the drivers that were there and

From time to time, I have seen some Erik and Hugen (and others?0 post a message with new release info. If they could pin the new posts and delete the old one, that should work.

FYI, I acquired a multifunction TL-WR902AC Travel Router and set up a Lan using it router mode (no internet). This works fine under Windows 10 on a Lenovo Laptop but didn't on my Toshiba running

David: See /g/nanovna-users/message/20899 The procedure shown there tells Windows how to see the "STM device in DFU mode". Hope this helps, Don

I use Thunderbird as my email client, I just tag all the software update posts with an appropriate color so they standout. Other email clients provide the same function. 73, Geoff AB6BT

I agree completely. I'm still not sure how to find the appropriate software versions (NanoVNA-H4) from reading this reflector. Karl D. Henry, Architect, EIT KE3IF 286 Arona Road, New Stanton, PA 15672

May I suggest that there be a pinned post at the top of the message list for the current version of firmware for each of the various forms of the NanoVNA? It's getting a bit confusing.....

thanks， I've recently taken some time to add a rotary encoder and the basic functionality is implemented, the menu bar scrolls well, but the trace scrolling shows that the marker points are moving

David, Since it shows up as a STM device when you put it in DFU mode, it means a lot of correct things are happening (good cables, good hardware, nano in dfu mode, etc.). As happens in some cases that

If the VNA is put into DFU mode you MUST use the DFU driver. The STM Bootloader driver will not see it and no COM port is created. Period. It is a DFU device now, which is a directly driven device

STM32 Bootloader *IS* correct - Dfuse should be able to see that if it's drivernhas been correctly installed. (Comes with Dfuse, not Whinders . . .)

Thanks for the responses but DfuSeDemo doesnt recognise the vna either. When connected normally it appears in Device Manager under ports as a vitual com port . When in dfu mode that disappears and

and..if you use nanovna app.. and change device to update mode.. com port number may change... select that comport... click on connect in app and the soft will say "found vna in upload mode.. do you

If you have DfuSeDemo installed, what is preventing you from doing the upgrade with it? Oh, and when in Dfu mode, the Nano's ID changes, so you would see it as a Dfu device, not as the NanoVNA - that

I have been unable to carry out this update. I currently have vesion 0.5.0. I have downloaded several newer versions, have DfuSedemo installed with up to date drivers - did i say i am using windows

Note that if you do the SOL calibration not with a load of 50 Ω but with, for example, a load of 75 Ω, then the values displayed from the S11 are correct (compared to 75 Ω) and the same for the

I have found that the impedance/match of chip resistors depends upon how it is mounted, positioning the resistive element towards or away from the ground plane, or on edge, changes its shunt

Are you looking for DFU mode to update the firmware? If so, you might consider the VNA App program. It is similar to the VNA saver application, but it has a built in firmware upload function.

I suspect that there's so many applications where a 50 ohm resistor is nice (e.g. driving coax from a low Z source, as a series termination), or as a RF termination with a High Z receiver. yeah, it's