Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
A little background:
I have a VScomm PCI-200L dual serial port board installed and the ports are set to COM5 and COM6.

A script that uses Win32::SerialPort to communicate with some hardware via the serial port which works fine as long as I use the "on-motherboard" COM ports (COM1, COM2). Once I move the device to the add-on board, communication ceases.

The script reports no errors opening COM6 but never "sees" any data sitting on the port. To add a twist to this all dilemma I have a Win32 App that came with the hardware and it can communicate with the hardware when connected to COM6 just fine.

So my question is this, is there a known limitation with Win32::SerialPort and COM ports greater than 4? Or a known issue when used in conjunction with a serial port expansion board? Or is there some completely obvious setting that I'm overlooking (this is the most likely scenario).


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

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.