In SX Microcontrollers, SX/B Compiler and SX-Key Tool, kmonsx wrote:

[quote="Keith M"]
Can I just use

handle = CreateFile("COMx", etc flags, params, etc);
and use SetCommState(handle, dcb); where dcb is the windows data structure that defines baud rate, parity, etc?

Using the VCP drivers that you redistribute, is it business as usual on the PC for accessing that port, except that I can pass high(and non-standard) baud rates? 
  

Keith 
[/quote]I hate to reply to myself here, but for the benefit of the community :
 

I got my USB2SER setup, and communicating with some software I wrote in VC++ in .net.

 

The answer is a resounding YES.  Using FTDI's Virtual Com Port drivers, the device shows up as COMx where x is the next available number.  In my case, it's COM4.  It was just a matter of modifying the DCB structure that contains the baudrate and passing it to SetCommState() as usual.  You can pass literally any number you like, provided it's one of the ones listed on the supported spreadsheet I attached in my original message.

 

It's surprisingly transparent.  Most apps seem to work fine with it.

 

I've attached some sample VC++ code that I wrote just to test basic functionality.  This is a console app that opens the port, sets the port up with baud rate etc, and goes into an infinite loop reading from the serial port.  I also included a line which shows how to write to the port.

 

Notice this is barebones code -- it doesn't rely or depend on any non-standard external headers, libraries, etc.  To build it, simply select "New Project", pick Visual C++ Projects, select the "Managed C++ Application" template, give it a name, and then just replace the default .cpp file with mine.

 

FYI

 

Keith

---------- End of Message ----------


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86434#m87350

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)