Kenneth Goodwin 2022/01/14 10:12
nanovna-v2-02210726-v2plus4.bin which loaded Version: git-20210530-412578c Build Time: Jul 26 2021 When I look at my device menu options CONFIG --> VERSION only Version: git-20210530-412578c Build Time: Jul 26 2021 is displayed by the device. Without any problems I am using NanoVNASaver version 0.3.10 and Nano vna_qt which has no known version display that I can find but the vna_qt.exe file has a file date of 5/7/2020 which I downloaded from the Windows version labled 20200507. I use Windows 10 Pro 64-bit operating system on my computer. From your past postings it seems as if you have used the same files including the Cypress device installer but my newbie guess would be that your problem is with the USB interface, maybe a possible USB port conflict?? A prolblem like this should be displayed in the Device Manager with a detail note indicating that the attempted interface is not working. Just guessing. I use USBDeview from Nirsoft.net to diagnose my usb interfaces. With my NanoVNA V2Plus 4 connected to my computer, the USB Serial Port (COM8 for me) is established while USBDeview shows Device Name: CDC-ACM Demo as a USB to UART Adapter with a Serial Number: DEMO. When I put the NanoVNA V2Plus 4 into the Bootload configuration (no longer labeled DFU mode in the Config display, the available documentation is out of date for the NanoVNA V2Plus 4) to update the firmware, a new USB interface is established at COM7 for me and USBDeview shows that the previously established interface at COM8 as no longer connected. The now connected Bootload interface at COM7 (for me), has a Serial Number USB_DFU whereas the earlier USB interface at COM8 had a displayed Serial Number DEMO in the USBDiview listing. I find the change in the Windows computer Device Manager Ports (COM & LPT) listing from COM8 to COM7 as interesting noting that when I exit the Bootload mode back to the normal configuration, the connection is re-established back to COM8. For reasons I don't fully comprehend, USBDeview doesn't display the COM ports but the documentation tells me for certain 'drivers' this could be the case.
Soapbox: A side question for you, how do you know that you have a NanoVNA V2Plus 4 v2.4 ?? The only place I can find the label v2.4 of my recently purchased device is on the bill of sale. I believe both of us have v2.4 but I guess you have to take it on faith backed up by using the firmware that is delineated for v2.4 I surely haven't used the v2.3 files. I find that only the file dates and/or names have any hint as to their version in some cases. For example, when I go to Config --> Version it displays NanoVNA V2Plus4 without any hint of it being NanoVNA V2Plus4 v2.4 I find the hardware and software versions all very confusing but I came from a profession with some very stringent configuration controls and even then we ended up with some very famous accidents because of configuration issues.