Solved it.
When you init a new FTD, I needed to
sub init_FTD
{
my $FT = Win32::FTDI::FTD2XX->new();
unless( $FT->PFT_STATUS() == FT_OK )
{
printf( STDERR "FTD2XX::new() failed: %s (%s)\n", $FT->PFT_STATUS_
+MSG(), $FT->PFT_ERROR() );
return 0;
}
printf( "FTD2XX::new() allocated PFT_HANDLE: %d\n", $FT->PFT_HANDLE(
+) );
# $FT->PFT_DEBUG(1);
unless ($FT->OpenByIndex(0))
{
print "Problem opening Port 0\n";
return 0;
}
unless ($FT->SetBreakOn)
{
print "failed to set brake\n";
}
unless ($FT->Purge(FT_PURGE_RX))
{
print 'cannot purge';
}
unless ($FT->SetBaudRate(FT_BAUD_2400))
{
print "Baud is set\n";
return 0;
}
return $FT;
}
otherwise all the data that comes in is seemingly junk.
That was incredibly painful to figure out. I knew I would get there though, once I asked for other people's assistance. Its the way of things.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.