I have an update on this. I used portmon to watch the ports as I connect to them and I see the problem.

Here's a snippet of my test stub: 

my $ob = Win32::SerialPort->new("COM5") || die("Couldn't open COM5");
$ob->baudrate(19200);
$ob->parity("none");
$ob->databits(8);
$ob->stopbits(1);
$ob->handshake("none");
$ob->write_settings || die("Couldn't write serial port settings");

[download]
When I run this with COM1 (a motherboard port) portmon reports that it was opened at 19200b, which is what was requested. However, when I run this with COM5 (the add-on card) portmon reports that it was opened at 1200b. Any ideas to why the add-on card would be ignoring the baudrate request?

-Nitrox

In reply to Re: Win32::SerialPort with ports > 4 by Nitrox
in thread Win32::SerialPort with ports > 4 by Nitrox

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.