LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

FTDI FT260 - Problem with LibFT260.dll

Hi,

 

I have a development board of the FTDI: the UMFT260EV1A. It is an HID that support I2C and RS232 over USB.

The FTDI provides a DLL (LibFT260.dll) that act as bridge between Application and the Window's driver for HID driver class.

 

I use "Call Library Function Node" to interface with the DLL, but the function that should be create communication channel with device return the Status of "Device not Found".

I am using Windows XP 32 bit as O.S.

Obviously, the device is recognized from my O.S.

The parameters of the function are correct. The prototype of the function is followed:

 

 

FT260_STATUS FT260_OpenByVidPid(WORD vid, WORD pid, DWORD deviceIndex, FT260_HANDLE* pFt260Handle)

 

FT260_STATUS is an enum that i defined it as uint8 enum in labview

 

This is how I configured the CLFN:

 

uint8_t FT260_OpenByVidPid@16(uint16_t Vid, uint16_t Pid, uint32_t DeviceIndex, uint32_t* SessionID)

Convenction call is: stdcall (WINAPI)

 

Can someone help me to understand what is the problem?

 

Thank you very much

0 Kudos
Message 1 of 8
(5,560 Views)

Hi,

 

I have a an FT260 IC and use the functions of the LibFT260.dll library

 

When i try to open a communication with it, the relative function return me the STATUS:  "Device not Found".

 

I am using Windows XP 32 bit as O.S.

Obviously, the device is recognized from my O.S.

The parameters of the function are correct. The prototype of the function is followed:

 

FT260_STATUS FT260_OpenByVidPid(WORD vid, WORD pid, DWORD deviceIndex, FT260_HANDLE* pFt260Handle)

 

FT260_STATUS is an enum that i defined it as uint8 enum in labview

 

This is how I configured the CLFN:

 

uint8_t FT260_OpenByVidPid@16(uint16_t Vid, uint16_t Pid, uint32_t DeviceIndex, uint32_t* SessionID)

Convenction call is: stdcall (WINAPI)

 

Can someone help me to understand what is the problem?

 

Thank you very much

0 Kudos
Message 2 of 8
(5,256 Views)

I have resolved the problem.

 

This thread can be closed

0 Kudos
Message 3 of 8
(5,520 Views)

I have resolved the problem.

 

This thread can be closed

0 Kudos
Message 4 of 8
(5,216 Views)

Hi,

thank you for the update. Out of curiosity, would you be kind enough to briefly explain (here or in this almost identical thread) what the problem was, and how you solved it? Although it may seem irrelevant to you, sometimes sharing your own experience can be unexpectedly helpful to other forum users.

Best regards,

Alessia

Message 5 of 8
(5,509 Views)

Hi,

thank you for the update. Out of curiosity, would you be kind enough to briefly explain (here or in this almost identical thread) what the problem was, and how you solved it? Although it may seem irrelevant to you, sometimes sharing your own experience can be unexpectedly helpful to other forum users.

Best regards,

Alessia

0 Kudos
Message 6 of 8
(5,201 Views)

I have the same problem.. 

how did you solve the problem? are there any reference Vi file you can work with? thanks

0 Kudos
Message 7 of 8
(4,430 Views)

I have the same problem. How can I solve it?
Can you provide the corresponding VI?
thank you!

0 Kudos
Message 8 of 8
(4,267 Views)