My thinking, after not having success with the CPAN definition, was to follow D2XX Programmer's Guide Version 1.3
definition and see if that worked (obviously it didn't and remained in the code, sorry about that).
The definition in CPAN:
SetBitMode Parameters: {$mode} Return Success: TRUE Return Failure: FALSE Purpose: API Method - See FT_SetBitMode(). Note: The following EXPORTS for BitModes are available for convenien +ce: PFT_BITMODE_RESET PFT_BITMODE_ASYNCBB PFT_BITMODE_MPSSE PFT_BITMODE_SYNCBB PFT_BITMODE_MHBEM PFT_BITMODE_FOISM PFT_BITMODE_CBUSBB
Only asks for the $mode parameter, although I have tried this as:
my $mode = FTDIdev->SetBitMode(0x03, 0x01); #also tried in dec with 3, + 1 print "My mode is: $mode\n";
This changes the printed $mode to 244 (0xF4) (as opposed to 245 (0xF5), which may indicate we have eliminated one error...). But again the program gets stuck at the write stage.
Thinking about it, how are the two outputs (two DB9 com ports) represented on the one chip? is this done with the mask? which would make require more than two bytes for masking the full 18 pins...
This would imply that 0x03 is trying to mask/write from the port belonging to ComPort6...
In reply to Re^4: Problem Writing to FTDI COM Port using Win32::FTDI::FTD2XX
by PrfrrdUsrNm
in thread Problem Writing to FTDI COM Port using Win32::FTDI::FTD2XX
by PrfrrdUsrNm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |