QtSerialPort - SerialPortInfo returns 0 ports available

[slanina]

I have Qt 5.0.1 on Windows 7 64-bit and I have downloaded and installed QtSerialPort following instructions on Wiki. I use MS VC++ Express 2010 compiler.

With simple example code from cenumerator I get 0 ports available. However, in Control Panel and using terminal program I can connect to my serial device.
I also did a quick Python script and it works from there using PySerial.

Any thoughts how to fix this?

QList<QSerialPortInfo> serialPortInfoList = QSerialPortInfo::availablePorts();
    QTextStream out(stdout);
 
    out << QObject::tr("Total number of ports available: ") << serialPortInfoList.count() << endl;
 
    foreach (const QSerialPortInfo &serialPortInfo, serialPortInfoList) {
        out << endl
            << QObject::tr("Port: ") << serialPortInfo.portName() << endl
            << QObject::tr("Location: ") << serialPortInfo.systemLocation() << endl
            << QObject::tr("Description: ") << serialPortInfo.description() << endl
            << QObject::tr("Manufacturer: ") << serialPortInfo.manufacturer() << endl
            << QObject::tr("Vendor Identifier: ") << (serialPortInfo.hasVendorIdentifier() ? QByteArray::number(serialPortInfo.vendorIdentifier(), 16) : QByteArray()) << endl
            << QObject::tr("Product Identifier: ") << (serialPortInfo.hasProductIdentifier() ? QByteArray::number(serialPortInfo.productIdentifier(), 16) : QByteArray()) << endl
            << QObject::tr("Busy: ") << (serialPortInfo.isBusy() ? QObject::tr("Yes") : QObject::tr("No")) << endl;
    }

QList<QSerialPortInfo> serialPortInfoList = QSerialPortInfo::availablePorts();
    QTextStream out(stdout);

    out << QObject::tr("Total number of ports available: ") << serialPortInfoList.count() << endl;

    foreach (const QSerialPortInfo &serialPortInfo, serialPortInfoList) {
        out << endl
            << QObject::tr("Port: ") << serialPortInfo.portName() << endl
            << QObject::tr("Location: ") << serialPortInfo.systemLocation() << endl
            << QObject::tr("Description: ") << serialPortInfo.description() << endl
            << QObject::tr("Manufacturer: ") << serialPortInfo.manufacturer() << endl
            << QObject::tr("Vendor Identifier: ") << (serialPortInfo.hasVendorIdentifier() ? QByteArray::number(serialPortInfo.vendorIdentifier(), 16) : QByteArray()) << endl
            << QObject::tr("Product Identifier: ") << (serialPortInfo.hasProductIdentifier() ? QByteArray::number(serialPortInfo.productIdentifier(), 16) : QByteArray()) << endl
            << QObject::tr("Busy: ") << (serialPortInfo.isBusy() ? QObject::tr("Yes") : QObject::tr("No")) << endl;
    }

To copy to clipboard, switch view to plain text mode 

QT       += core gui sql serialport

QT       += core gui sql serialport

To copy to clipboard, switch view to plain text mode 

Output:

Total number of ports available: 0

[ChrisW67]

This may be an issue with Windows Setup API not showing the errant device.

What happens if you just try to open COMx?

[kuzulis]

2 slanina,

Possibly it is regression which belongs to a recent patch which had to optimize enumeration: https://codereview.qt-project.org/#change,53725

Also already created issue about this bug: https://bugreports.qt-project.org/br...TPLAYGROUND-27

May you give detailed information on the used device (VID/PID/Class GUID and etc), and also give *.inf driver files?


UPD:
At present the solution isn't known. Temporarily you can use workaround - simply to roll away change to this patch for QSerialPortInfo.

PS:
Win32 API again and again throws to us "surprises".
The behavior of Setup API doesn't give in to logic, or I don't understand something...

[slanina]

2 slanina,

Possibly it is regression which belongs to a recent patch which had to optimize enumeration: https://codereview.qt-project.org/#change,53725

Also already created issue about this bug: https://bugreports.qt-project.org/br...TPLAYGROUND-27

May you give detailed information on the used device (VID/PID/Class GUID and etc), and also give *.inf driver files?


UPD:
At present the solution isn't known. Temporarily you can use workaround - simply to roll away change to this patch for QSerialPortInfo.

PS:
Win32 API again and again throws to us "surprises".
The behavior of Setup API doesn't give in to logic, or I don't understand something...

It is a custom device I am developing from one sample given by NXP for their LPC series of microcontrollers (LPC11U35). It is based on the code that works fine on the device side as given by NXP. Actually based on that code I did a device and one code in October 2012 but then I have used QtExtSerialPort and it enumerated fine.
Enumeration would be beneficial to me, since I could then detect and parse manufacturer name and device name (basically me) and make sure the user does not need to select a COM port - so I could have an "auto connect" upon application loading.

Any hints how to rollback the patch? I have never done this on Windows.

Upload of .inf file seems to fail so I am copying it below. It uses NXP VID/PID since it is their example...

;************************************************************
; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation
 
 
[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
LayoutFile=layout.inf
CatalogFile=%MFGFILENAME%.cat
DriverVer=11/15/2007,5.1.2600.0
 
[Manufacturer]
%MFGNAME%=DeviceList, NTamd64
 
[DestinationDirs]
DefaultDestDir=12
 
 
;------------------------------------------------------------------------------
;  Windows 2000/XP/Vista-32bit Sections
;------------------------------------------------------------------------------
 
[DriverInstall.nt]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.nt
AddReg=DriverInstall.nt.AddReg
 
[DriverCopyFiles.nt]
usbser.sys,,,0x20
 
[DriverInstall.nt.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
 
[DriverInstall.nt.Services]
AddService=usbser, 0x00000002, DriverService.nt
 
[DriverService.nt]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys
 
;------------------------------------------------------------------------------
;  Vista-64bit Sections
;------------------------------------------------------------------------------
 
[DriverInstall.NTamd64]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.NTamd64
AddReg=DriverInstall.NTamd64.AddReg
 
[DriverCopyFiles.NTamd64]
%DRIVERFILENAME%.sys,,,0x20
 
[DriverInstall.NTamd64.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
 
[DriverInstall.NTamd64.Services]
AddService=usbser, 0x00000002, DriverService.NTamd64
 
[DriverService.NTamd64]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys
 
 
;------------------------------------------------------------------------------
;  Vendor and Product ID Definitions
;------------------------------------------------------------------------------
; When developing your USB device, the VID and PID used in the PC side
; application program and the firmware on the microcontroller must match.
; Modify the below line to use your VID and PID.  Use the format as shown below.
; Note: One INF file can be used for multiple devices with different VID and PIDs.
; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of the line.
;------------------------------------------------------------------------------
[SourceDisksFiles]
[SourceDisksNames]
[DeviceList]
%DESCRIPTION%=DriverInstall, USB\VID_1FC9&PID_2047
 
[DeviceList.NTamd64]
%DESCRIPTION%=DriverInstall, USB\VID_1FC9&PID_2047
 
 
;------------------------------------------------------------------------------
;  String Definitions
;------------------------------------------------------------------------------
;Modify these strings to customize your device
;------------------------------------------------------------------------------
[Strings]
MFGFILENAME="CDC_vista"
DRIVERFILENAME ="usbser"
MFGNAME="http://www.lpcware.com/content/project/LPCUSBlib"
INSTDISK="LPCUSBlib CDC Driver Installer"
DESCRIPTION="Communications Port"
SERVICE="USB RS-232 Emulation Driver"

;************************************************************
; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation


[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
LayoutFile=layout.inf
CatalogFile=%MFGFILENAME%.cat
DriverVer=11/15/2007,5.1.2600.0

[Manufacturer]
%MFGNAME%=DeviceList, NTamd64

[DestinationDirs]
DefaultDestDir=12


;------------------------------------------------------------------------------
;  Windows 2000/XP/Vista-32bit Sections
;------------------------------------------------------------------------------

[DriverInstall.nt]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.nt
AddReg=DriverInstall.nt.AddReg

[DriverCopyFiles.nt]
usbser.sys,,,0x20

[DriverInstall.nt.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.nt.Services]
AddService=usbser, 0x00000002, DriverService.nt

[DriverService.nt]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys

;------------------------------------------------------------------------------
;  Vista-64bit Sections
;------------------------------------------------------------------------------

[DriverInstall.NTamd64]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.NTamd64
AddReg=DriverInstall.NTamd64.AddReg

[DriverCopyFiles.NTamd64]
%DRIVERFILENAME%.sys,,,0x20

[DriverInstall.NTamd64.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.NTamd64.Services]
AddService=usbser, 0x00000002, DriverService.NTamd64

[DriverService.NTamd64]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys


;------------------------------------------------------------------------------
;  Vendor and Product ID Definitions
;------------------------------------------------------------------------------
; When developing your USB device, the VID and PID used in the PC side
; application program and the firmware on the microcontroller must match.
; Modify the below line to use your VID and PID.  Use the format as shown below.
; Note: One INF file can be used for multiple devices with different VID and PIDs.
; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of the line.
;------------------------------------------------------------------------------
[SourceDisksFiles]
[SourceDisksNames]
[DeviceList]
%DESCRIPTION%=DriverInstall, USB\VID_1FC9&PID_2047

[DeviceList.NTamd64]
%DESCRIPTION%=DriverInstall, USB\VID_1FC9&PID_2047


;------------------------------------------------------------------------------
;  String Definitions
;------------------------------------------------------------------------------
;Modify these strings to customize your device
;------------------------------------------------------------------------------
[Strings]
MFGFILENAME="CDC_vista"
DRIVERFILENAME ="usbser"
MFGNAME="http://www.lpcware.com/content/project/LPCUSBlib"
INSTDISK="LPCUSBlib CDC Driver Installer"
DESCRIPTION="Communications Port"
SERVICE="USB RS-232 Emulation Driver"

To copy to clipboard, switch view to plain text mode 

[kuzulis]

It is clear. It seems that this problem is observed with USB CDC ACM devices.

Please try new patch: https://bugreports.qt-project.org/br...TPLAYGROUND-27

And please let me know about results.