Converting a string to LPCWSTR for CreateFile() to address a serial port

21,294

Solution 1

You can either use std::wstring and std::wcin, std::wcout to perform input directly in "unicode strings", or you can look into Microsoft's conversion functions.

If you go for the 1st option (recommended), you still need to use the c_str() function to gain access to a LPCWSTR value (pointer to const wchar_t).

Sample solution (also not use of CreateFileW syntax, to prevent issues with UNICODE macro):

#include <iostream>    
#include <windows.h>
#include <string>

int main()
{
   std::wstring comNum;
   std::wcout << L"\n\nEnter the port (ex: COM20): ";
   std::wcin >> comNum;
   std::wstring comPrefix = L"\\\\.\\";
   std::wstring comID = comPrefix+comNum;

   HANDLE hSerial;

   hSerial = CreateFileW( comID.c_str(),
                     GENERIC_READ | GENERIC_WRITE,
                     0,
                     0,
                     OPEN_EXISTING,
                     FILE_ATTRIBUTE_NORMAL,
                     0);`

   return 0;
}

Solution 2

If you want to continue using std::string, then use its c_str() method when calling CreateFileA(), eg:

hSerial = CreateFileA( comID.c_str(), ...);
Share:
21,294
John
Author by

John

Updated on September 24, 2020

Comments

  • John
    John over 3 years

    I seem to be having a bit of a TEXT / UNICODE problem when using the windows CreateFile function for addressing a serial port. Can someone please help point out my error?

    I'm writing a Win32 console application in VC++ using VS 2008.

    I can create a handle to address the serial port like this:

    #include <iostream>    
    #include <windows.h>
    #include <string>
    
    int main()
    {
    
       HANDLE hSerial;
    
       hSerial = CreateFile( L"\\\\.\\COM20",
                             GENERIC_READ | GENERIC_WRITE,
                             0,
                             0,
                             OPEN_EXISTING,
                             FILE_ATTRIBUTE_NORMAL,
                             0);`
    
       return 0;
    }
    

    That works just fine (the \\\\.\\ bit is required for comports greater than COM9 and works for those up to COM9 also). The problem is that my comport will not always be COM20, so I'd like to have the user specify what it is.

    Here are some things I've tried:

    #include <iostream>    
    #include <windows.h>
    #include <string>
    
    int main()
    {
       std::string comNum;
       std::cout << "\n\nEnter the port (ex: COM20): ";
       std::cin >> comNum;
       std::string comPrefix = "\\\\.\\";
       std::string comID = comPrefix+comNum;
    
       HANDLE hSerial;
    
       hSerial = CreateFile( comID,
                             GENERIC_READ | GENERIC_WRITE,
                             0,
                             0,
                             OPEN_EXISTING,
                             FILE_ATTRIBUTE_NORMAL,
                             0);`
    
       return 0;
    }
    

    This does not compile and returns the error: error C2664: 'CreateFileW' : cannot convert parameter 1 from 'std::string' to 'LPCWSTR'

    I thought maybe specifying CreateFileA would work then, but that gave basically the same error.

    I also tried :

    /*
    everything else the same
    */   
    
    hSerial = CreateFile( TEXT(comID),
                          GENERIC_READ | GENERIC_WRITE,
                          0,
                          0,
                          OPEN_EXISTING,
                          FILE_ATTRIBUTE_NORMAL,
                          0);`
    

    which also does not compile and returns: error C2065: 'LcomID' : undeclared identifier

    I am not much of an expert but I have been working on this for a while now. Can someone tell me how to replace L"\\\\.\\COM20" in such a way that the user can specify the comport and so that CreateFile will still work? Thanks!

  • MSalters
    MSalters over 13 years
    +1, This is sufficient for the stated problem (serial port names).
  • MSalters
    MSalters over 13 years
    You can't disable Unicode. It's the native character set of Windows. You probably chose to use the wrapper functions such as CreateFileA. You should know that they will always convert their arguments to Unicode (outside your control) and then call the Unicode equivalent.
  • Paul Nathan
    Paul Nathan over 13 years
    @MSalters: #undef UNICODE and then turn off the various Wide Character compilation settings.
  • MSalters
    MSalters over 13 years
    That doesn't actually disable Unicode. The #undef causes CreateFile to be #defined as CreateFileA, as I suspected. That still is a wrapper for CreateFileW . The *W functions are not disabled by such #defines. Newer APIs, including COM , are not affected by this #define; they are always Unicode. Hence, if you do not want to deal with two character sets, choose Unicode only. if you choose ANSI, you always have to consider how that interacts with Unicode behind the scenes.
  • Mike Jablonski
    Mike Jablonski almost 10 years
    I came across the same problem. This solved it. Thanks!