Windows 7 USB Driver problem - not working
Checking the Windows device driver properties shows nanovna to be using ChibOS/RT Virtual Com port and Windows recognizes device being attached / removed.You could replace that driver with this: Virtual COM port operation to nanoVNA can be confirmed using .e.g putty.exe I don't bother with a .msi installer; the standalone .exe works fine. Try sending `help` from putty: /g/nanovna-users/wiki/shellcommands Nanovna-Saver uses pyqt5, which can be separately tested: `python -m serial.tools.list_ports` COM3 1 ports found NanoVNA USB driver is STMicroelectronics Virtual COM Port 8/2/2013 1.4.0.0 |
|
Hi Nigel,
I would like a simpler approach to repair. The nanoVNA saver also works under Windows 7. A prerequisite for this is that you have SP1 and Ms VC ++ installed. You can then start nanovna-saver-0.0.12.exe from Windows. If you want to access the nanovna saver by installing Python, make sure to check the PATH path when installing Python - and install it in the Program Files folder (not in the Users /.../../../ folder) ). Then install the required pyqt5, numpy, pyserial from the Windows command line using pip3 install .... You can verify the installation by calling the Python 3.7 Module Docs server on your browser page. I unpacked the contents of the nanovnasaver master downloaded from github into the C: root directory. You can start the program with nanovna-saver.py. If not missed something, it should work. I hope it works for you. Gyula |
|
Good afternoon from sunny South Africa :-)
Updates: Rune - Copy of log file(s) created below FYI but not much to analyze... Also a screen shot of the command window and log file from a USB 'trace' in case of interest / value) that may assist your development(s) in some way(?). Oristo - Thanks for the link to another driver, although was already on system I have updated with the newer version based on the file name (en.stsw-stm 32080 vs en.stsw-stm 32102) and after a re-boot and changing device driver from ChibOS/RT Virtual Com port to the one from st.com, the nanovna now has a port number - PROGRESS! Running NanoVNA-Saver now shows the associated port number AND connection is possible <BIG Smile>. Now I have additional (fun) stuff to learn which will hopefully keep my cerebral cells busy... Gyula - Thank you for taking time to reply, thankfully a change of driver was the 'simple' fix. Thank you all again for your interest and support, it really is a FANTASTIC community to be a party of :-) Best regards Nigel R Content below this line probably only of interest if similar issues encountered by others and / or for reference. Sorry for consuming bandwidth / space if inappropriate. ----------------------------------------------------------------------------------------------------------------------------- LogFile 1 2019-10-01 15:20:03,761 - NanoVNASaver - INFO - Startup... 2019-10-01 15:20:04,412 - NanoVNASaver.SweepWorker - INFO - Initializing SweepWorker 2019-10-01 15:20:04,512 - NanoVNASaver.NanoVNASaver - DEBUG - Building user interface 2019-10-01 15:20:05,303 - NanoVNASaver.NanoVNASaver - DEBUG - Finished building interface 2019-10-01 15:22:35,569 - NanoVNASaver - INFO - Startup... 2019-10-01 15:22:36,100 - NanoVNASaver.SweepWorker - INFO - Initializing SweepWorker 2019-10-01 15:22:36,190 - NanoVNASaver.NanoVNASaver - DEBUG - Building user interface 2019-10-01 15:22:36,981 - NanoVNASaver.NanoVNASaver - DEBUG - Finished building interface LogFile 2 after change of driver 2019-10-01 15:38:26,009 - NanoVNASaver - INFO - Startup... 2019-10-01 15:38:26,620 - NanoVNASaver.SweepWorker - INFO - Initializing SweepWorker 2019-10-01 15:38:26,730 - NanoVNASaver.NanoVNASaver - INFO - Found NanoVNA (0483 5740) on port COM17 2019-10-01 15:38:26,730 - NanoVNASaver.NanoVNASaver - DEBUG - Building user interface 2019-10-01 15:38:31,918 - NanoVNASaver.NanoVNASaver - DEBUG - Finished building interface 2019-10-01 15:38:36,845 - NanoVNASaver.NanoVNASaver - INFO - Opening serial port COM17 Screenshot is console with non working driver. Error message below reported after initial attempt to use with new driver but as reported all well second and subsequent times. \\?\usb#vid_0483&pid_5740#400#{a5dcbf10-6530-11d2-901f-00c04fb951ed} Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: nanovna-saver.v0.0.12.exe Application Version: 0.0.0.0 Application Timestamp: 5d24a31b Hang Signature: c143 Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 7177 Additional Hang Signature 1: c143197821453067c6fca61d7dec776f Additional Hang Signature 2: ef39 Additional Hang Signature 3: ef3942ff81a6672d8bee95d6e5eccc0c Additional Hang Signature 4: c143 Additional Hang Signature 5: c143197821453067c6fca61d7dec776f Additional Hang Signature 6: ef39 Additional Hang Signature 7: ef3942ff81a6672d8bee95d6e5eccc0c USB Tree (non working driver) ======================== USB Device ======================== +++++++++++++++++ Device Information ++++++++++++++++++ Device Description : ChibiOS/RT Virtual COM Port Device Path : \\?\usb#vid_0483&pid_5740#400#{a5dcbf10-6530-11d2-901f-00c04fb951ed} Device ID : USB\VID_0483&PID_5740\400 Hardware IDs : USB\VID_0483&PID_5740&REV_0200 USB\VID_0483&PID_5740 Driver KeyName : {88bae032-5a81-49f0-bc3d-a4ff138216d6}\0000 ({88BAE032-5A81-49F0-BC3D-A4FF138216D6}) Driver : system32\DRIVERS\WinUsb.sys (Version: 6.1.7601.17514 Date: 2010-11-20) Driver Inf : C:\Windows\inf\oem40.inf Legacy BusType : PNPBus Class : USBDevice Class GUID : {88bae032-5a81-49f0-bc3d-a4ff138216d6} Interface GUID : {a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE) Service : WinUSB Enumerator : USB Location Info : Port_#0002.Hub_#0005 Location IDs : PCIROOT(0)#PCI(1E00)#PCI(0400)#PCI(0000)#USBROOT(0)#USB(2) Container ID : {760c3622-4a59-596d-bacb-13523c1ebcfe} Manufacturer Info : STMicroelectronics Capabilities : 0x14 (Removable, UniqueID) Status : 0x0180600A (DN_DRIVER_LOADED, DN_STARTED, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER) Problem Code : 0 Power State : D0 (supported: D0, D2, D3, wake from D0, wake from D2) ---------------- Connection Information --------------- Connection Index : 0x02 (2) Connection Status : 0x01 (DeviceConnected) Current Config Value : 0x01 Device Address : 0x01 (1) Is Hub : 0x00 (no) Device Bus Speed : 0x01 (Full-Speed) Number Of Open Pipes : 0x03 (3 pipes to data endpoints) Pipe[0] : EndpointID=2 Direction=IN ScheduleOffset=0 Type=Interrupt Pipe[1] : EndpointID=1 Direction=OUT ScheduleOffset=0 Type=Bulk Pipe[2] : EndpointID=1 Direction=IN ScheduleOffset=0 Type=Bulk Data (HexDump) : 02 00 00 00 12 01 10 01 02 00 00 40 83 04 40 57 ...........@..@W 00 02 01 02 03 01 01 01 00 01 00 03 00 00 00 01 ................ 00 00 00 07 05 82 03 08 00 FF 00 00 00 00 07 05 ................ 01 02 40 00 00 00 00 00 00 07 05 81 02 40 00 00 ..@..........@.. 00 00 00 00 .... ---------------------- Device Descriptor ---------------------- bLength : 0x12 (18 bytes) bDescriptorType : 0x01 (Device Descriptor) bcdUSB : 0x110 (USB Version 1.10) bDeviceClass : 0x02 (Communications and CDC Control) bDeviceSubClass : 0x00 bDeviceProtocol : 0x00 (No class specific protocol required) bMaxPacketSize0 : 0x40 (64 bytes) idVendor : 0x0483 (STMicroelectronics) idProduct : 0x5740 bcdDevice : 0x0200 iManufacturer : 0x01 (String Descriptor 1) Language 0x0409 : "STMicroelectronics" iProduct : 0x02 (String Descriptor 2) Language 0x0409 : "ChibiOS/RT Virtual COM Port" iSerialNumber : 0x03 (String Descriptor 3) Language 0x0409 : "400" bNumConfigurations : 0x01 (1 Configuration) Data (HexDump) : 12 01 10 01 02 00 00 40 83 04 40 57 00 02 01 02 .......@..@W.... 03 01 .. ------------------ Configuration Descriptor ------------------- bLength : 0x09 (9 bytes) bDescriptorType : 0x02 (Configuration Descriptor) wTotalLength : 0x0043 (67 bytes) bNumInterfaces : 0x02 (2 Interfaces) bConfigurationValue : 0x01 (Configuration 1) iConfiguration : 0x00 (No String Descriptor) bmAttributes : 0xC0 D7: Reserved, set 1 : 0x01 D6: Self Powered : 0x01 (yes) D5: Remote Wakeup : 0x00 (no) D4..0: Reserved, set 0 : 0x00 MaxPower : 0x32 (100 mA) Data (HexDump) : 09 02 43 00 02 01 00 C0 32 09 04 00 00 01 02 02 ..C.....2....... 01 00 05 24 00 10 01 05 24 01 00 01 04 24 02 02 ...$....$....$.. 05 24 06 00 01 07 05 82 03 08 00 FF 09 04 01 00 .$.............. 02 0A 00 00 00 07 05 01 02 40 00 00 07 05 81 02 .........@...... 40 00 00 @.. ---------------- Interface Descriptor ----------------- bLength : 0x09 (9 bytes) bDescriptorType : 0x04 (Interface Descriptor) bInterfaceNumber : 0x00 bAlternateSetting : 0x00 bNumEndpoints : 0x01 (1 Endpoint) bInterfaceClass : 0x02 (Communications and CDC Control) bInterfaceSubClass : 0x02 (Abstract Control Model) bInterfaceProtocol : 0x01 (AT Commands defined by ITU-T V.250 etc) iInterface : 0x00 (No String Descriptor) Data (HexDump) : 09 04 00 00 01 02 02 01 00 ......... -------------- CDC Interface Descriptor --------------- bFunctionLength : 0x05 (5 bytes) bDescriptorType : 0x24 (Interface) bDescriptorSubType : 0x00 (Header Functional Descriptor) bcdCDC : 0x110 (CDC Version 1.10) Data (HexDump) : 05 24 00 10 01 .$... -------------- CDC Interface Descriptor --------------- bFunctionLength : 0x05 (5 bytes) bDescriptorType : 0x24 (Interface) bDescriptorSubType : 0x01 (Call Management Functional Descriptor) bmCapabilities : 0x00 D7..2: : 0x00 (Reserved) D1 : : 0x00 (sends/receives call management information only over the Communication Class interface) D0 : : 0x00 (does not handle call management itself) bDataInterface : 0x01 Data (HexDump) : 05 24 01 00 01 .$... -------------- CDC Interface Descriptor --------------- bFunctionLength : 0x04 (4 bytes) bDescriptorType : 0x24 (Interface) bDescriptorSubType : 0x02 (Abstract Control Management Functional Descriptor) bmCapabilities : 0x02 D7..4: : 0x00 (Reserved) D3 : : 0x00 (not supports the notification Network_Connection) D2 : : 0x00 (not supports the request Send_Break) D1 : : 0x01 (supports the request combination of Set_Line_Coding, Set_Control_Line_State, Get_Line_Coding, and the notification Serial_State) D0 : : 0x00 (not supports the request combination of Set_Comm_Feature, Clear_Comm_Feature, and Get_Comm_Feature) Data (HexDump) : 04 24 02 02 .$.. -------------- CDC Interface Descriptor --------------- bFunctionLength : 0x05 (5 bytes) bDescriptorType : 0x24 (Interface) bDescriptorSubType : 0x06 (Union Functional Descriptor) bControlInterface : 0x00 bSubordinateInterface[0] : 0x01 Data (HexDump) : 05 24 06 00 01 .$... ----------------- Endpoint Descriptor ----------------- bLength : 0x07 (7 bytes) bDescriptorType : 0x05 (Endpoint Descriptor) bEndpointAddress : 0x82 (Direction=IN EndpointID=2) bmAttributes : 0x03 (TransferType=Interrupt) wMaxPacketSize : 0x0008 (8 bytes) bInterval : 0xFF (255 ms) Data (HexDump) : 07 05 82 03 08 00 FF ....... ---------------- Interface Descriptor ----------------- bLength : 0x09 (9 bytes) bDescriptorType : 0x04 (Interface Descriptor) bInterfaceNumber : 0x01 bAlternateSetting : 0x00 bNumEndpoints : 0x02 (2 Endpoints) bInterfaceClass : 0x0A (CDC-Data) bInterfaceSubClass : 0x00 bInterfaceProtocol : 0x00 iInterface : 0x00 (No String Descriptor) Data (HexDump) : 09 04 01 00 02 0A 00 00 00 ......... ----------------- Endpoint Descriptor ----------------- bLength : 0x07 (7 bytes) bDescriptorType : 0x05 (Endpoint Descriptor) bEndpointAddress : 0x01 (Direction=OUT EndpointID=1) bmAttributes : 0x02 (TransferType=Bulk) wMaxPacketSize : 0x0040 (64 bytes) bInterval : 0x00 (ignored) Data (HexDump) : 07 05 01 02 40 00 00 ....@.. ----------------- Endpoint Descriptor ----------------- bLength : 0x07 (7 bytes) bDescriptorType : 0x05 (Endpoint Descriptor) bEndpointAddress : 0x81 (Direction=IN EndpointID=1) bmAttributes : 0x02 (TransferType=Bulk) wMaxPacketSize : 0x0040 (64 bytes) bInterval : 0x00 (ignored) Data (HexDump) : 07 05 81 02 40 00 00 ....@.. -------------------- String Descriptors ------------------- ------ String Descriptor 0 ------ bLength : 0x04 (4 bytes) bDescriptorType : 0x03 (String Descriptor) Language ID[0] : 0x0409 (English - United States) Data (HexDump) : 04 03 09 04 .... ------ String Descriptor 1 ------ bLength : 0x26 (38 bytes) bDescriptorType : 0x03 (String Descriptor) Language 0x0409 : "STMicroelectronics" Data (HexDump) : 26 03 53 00 54 00 4D 00 69 00 63 00 72 00 6F 00 &.S.T.M.i.c.r.o. 65 00 6C 00 65 00 63 00 74 00 72 00 6F 00 6E 00 e.l.e.c.t.r.o.n. 69 00 63 00 73 00 i.c.s. ------ String Descriptor 2 ------ bLength : 0x38 (56 bytes) bDescriptorType : 0x03 (String Descriptor) Language 0x0409 : "ChibiOS/RT Virtual COM Port" Data (HexDump) : 38 03 43 00 68 00 69 00 62 00 69 00 4F 00 53 00 8.C.h.i.b.i.O.S. 2F 00 52 00 54 00 20 00 56 00 69 00 72 00 74 00 /.R.T. .V.i.r.t. 75 00 61 00 6C 00 20 00 43 00 4F 00 4D 00 20 00 u.a.l. .C.O.M. . 50 00 6F 00 72 00 74 00 P.o.r.t. ------ String Descriptor 3 ------ bLength : 0x08 (8 bytes) bDescriptorType : 0x03 (String Descriptor) Language 0x0409 : "400" Data (HexDump) : 08 03 34 00 30 00 30 00 ..4.0.0. |
|
Hi Nigel -
I have updated with the newer version based on the file name (en.stsw-stm 32080 vs en.stsw-stm 32102)It's good when a plan works. I have little Windows 7 experience. (I found Vista so awful that I pretty much stuck with XP SP2 until 8.1) Firmware updates almost certainly require STM's driver, if you ever attempt. |
Oristo
Gyula Molnar
