Serial port number in windows
-
My colleagues uses serial port and they use "QextSerialPort":http://qextserialport.sourceforge.net/, have look of this, this may help
-
I just know, my problem is not to use serial, but know what com port number the os assign to a device.
[quote author="Immii" date="1293096664"]My colleagues uses serial port and they use "QextSerialPort":http://qextserialport.sourceforge.net/, have look of this, this may help[/quote]
-
Judging by your wording, I guess you're talking about USB devices that act as a serial device? Or are you talking about real serial ports on your system?
I just did a bit of "Googling":http://www.google.nl/search?sourceid=chrome&ie=UTF-8&q=windows+usb+serial+port+api#hl=nl&expIds=17259,17291&xhr=t&q=windows+usb+api&cp=14&pf=p&sclient=psy&source=hp&aq=0&aqi=&aql=&oq=windows+usb+ap&gs_rfai=&pbx=1&fp=32b4510a29fc6da5, and it already turned up some starting points, like the "third hit":http://www.google.nl/url?sa=t&source=web&cd=3&sqi=2&ved=0CC8QFjAC&url=http://www.codemiles.com/download/file.php?id=719&ei=zxgTTYXfFciEOtHI7ZgJ&usg=AFQjCNH6tdyMFNHdG17twCGsJXSOxKYNJQ on that query. This is really Windows specific, though it would be nice to have a Qt-like API to get these kinds of notifications in a platform independent way. In KDE, I guess it would be in Solid. Perhaps the Windows port of that part of the KDE project contains the code you need?
-
I need know what the com port is assignet to a serial-usb adapter, because every time that i insert a device i always go to control panel, i want create a program to quickly get this information.
After much time of googling i see this "link":http://www.naughter.com/enumser.html , but is hard to port on a mingw, i lost many headers.
But i think there aren't much way to do this. And yes is very useful if this can be cross-platform. But for unix a simple dmesg can resolve this :P[quote author="Andre" date="1293097662"]Judging by your wording, I guess you're talking about USB devices that act as a serial device? Or are you talking about real serial ports on your system?
I just did a bit of "Googling":http://www.google.nl/search?sourceid=chrome&ie=UTF-8&q=windows+usb+serial+port+api#hl=nl&expIds=17259,17291&xhr=t&q=windows+usb+api&cp=14&pf=p&sclient=psy&source=hp&aq=0&aqi=&aql=&oq=windows+usb+ap&gs_rfai=&pbx=1&fp=32b4510a29fc6da5, and it already turned up some starting points, like the "third hit":http://www.google.nl/url?sa=t&source=web&cd=3&sqi=2&ved=0CC8QFjAC&url=http://www.codemiles.com/download/file.php?id=719&ei=zxgTTYXfFciEOtHI7ZgJ&usg=AFQjCNH6tdyMFNHdG17twCGsJXSOxKYNJQ on that query. This is really Windows specific, though it would be nice to have a Qt-like API to get these kinds of notifications in a platform independent way. In KDE, I guess it would be in Solid. Perhaps the Windows port of that part of the KDE project contains the code you need?[/quote]
-
Looks like an interesting project. If anything, it shows that Windows is a bit of a mess if you need to try 9 ways to actually get all the serial ports. If it is hard to use with MinGw, then why not use it with MSVC instead? You could make it a small, separate process that just communicates the data to your main application when needed. You can use any IPC mechanism you want for that, including just outputting the data over the stdout and reading that with QProcess.
Still, you could try and see if the simple way of reading out the registry would be enough in your case? You can use QSettings for that...
-
You can do with QextSerialPort. Example code:
@QList<QextPortInfo> ports = QextSerialEnumerator::getPorts();
qDebug() << "SerialSettings::LoadPorts(): List of ports availables:\n";
for (int i = 0; i < ports.size(); i++) {
qDebug() << "port name: " << ports.at(i).portName;
qDebug() << "friendly name: " << ports.at(i).friendName;
qDebug() << "physical name: " << ports.at(i).physName;
qDebug() << "enumerator name: " << ports.at(i).enumName;
qDebug() << "===================================";
}
@ -
What is it?!?
When this function was added to the project?!?
QextSerialEnumerator?!? QextPortInfo?!?[quote author="gronerth" date="1293126666"]You can do with QextSerialPort. Example code:
@QList<QextPortInfo> ports = QextSerialEnumerator::getPorts();
qDebug() << "SerialSettings::LoadPorts(): List of ports availables:\n";
for (int i = 0; i < ports.size(); i++) {
qDebug() << "port name: " << ports.at(i).portName;
qDebug() << "friendly name: " << ports.at(i).friendName;
qDebug() << "physical name: " << ports.at(i).physName;
qDebug() << "enumerator name: " << ports.at(i).enumName;
qDebug() << "===================================";
}
@[/quote] -
This methods of this library: "QExtSerialPort":http://qextserialport.sourceforge.net/
-
It might just be me, but I don't see the classes mentioned in the code fragment in the documentation linked from the page you give. I am looking at http://qextserialport.sourceforge.net/qextserialport-1.1.x/
Is this new API? Newer than the latest API docs on the webpage?
-
This API is very strange!
Look this "http://code.google.com/p/qextserialport/source/browse/#hg/src":http://code.google.com/p/qextserialport/source/browse/#hg/src
-
The api version that i have downloaded is: qextserialport-1.2win-alpha (win version), you can download from here: http://sourceforge.net/projects/qextserialport/files/qextserialport alpha/
-
This is a new alpha API, that include enumerator :) Great news!
[quote author="gronerth" date="1293458810"]The api version that i have downloaded is: qextserialport-1.2win-alpha (win version), you can download from here: http://sourceforge.net/projects/qextserialport/files/qextserialport alpha/
[/quote]
-
Yes, i use the old api in static mode, this api is writing for build shared library, look the macro
@define QEXTSERIALPORT_EXPORT Q_DECL_EXPORT
@ in the code
[quote author="gronerth" date="1293461425"]Well, i have worked with that api, using the dlls, do you mean that u need to link statically?[/quote]
-
Where is that definition?, i have never tried to link statically, but in the "qextserialport.pro" there is a line that says: #CONFIG += staticlib, have you tried to uncomment it?, and then compile it again( qmake, make)....