Here's the source:
sub SetBitMode { my $self = shift; my $mask = shift; my $mode = shift; unless( defined( $self->{_PFT_SetBitMode} ) ) { return( undef ) unless( _importDll( $self, "PFT_SetBitMode" ) ); } $self->{_PFT_STATUS} = $self->{_PFT_SetBitMode}->Call( $self->{_PFT_ +HANDLE}, $mask, $mode ); return( 0 ) if( $self->{_PFT_STATUS} ); return( 1 ); } # SetBitMode()
It wants a mode and a mask, and if you're passing in the ID, it's interpreting that as the mask. Unless you've got an older version or something, passing in the ID may supress some error, but it's not likely doing the right thing.

In reply to Re^3: Problem Writing to FTDI COM Port using Win32::FTDI::FTD2XX by kschwab
in thread Problem Writing to FTDI COM Port using Win32::FTDI::FTD2XX by PrfrrdUsrNm

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.