11-11-2019 08:01 AM - edited 11-11-2019 08:02 AM
This archive of course contains the 64-bit DLL too. You simply need to use the DLLs in the i386 subdirectory instead of the amd64 subdirectory. And yes you also need to use 32-bit LabVIEW installation as the 64-bit version can't use a 32-bit DLL.
02-13-2020 10:21 PM
How to include D2XX functions(FT_OPEN_EX) in labview.and what are the versions that support for an I2C communication using FTDI CHIP (FT201XB)
03-19-2024 04:23 AM
Could you please help me in interfacing FTDI FT245RL with labview.
03-19-2024 05:12 AM
How do you want to interface it? If you need it as a normal serial port, simply install the latest FTDI VCP driver (usually already present in any OS installation that is not from the stone age) and it should be accessible through NI-VISA as serial port.
If you try to do anything else, things might get a bit painful. 😀
If you want to program it through the shared library interface you need to install the FTDI D2XX driver which supports this device too. Then start using any of the LabVIEW interfaces that are out there. The one from FTDI itself is pretty old (LabVIEW 7.0) and is not properly adapted to work for 64-bit but should be a starting point.
I guess you have a lot of reading ahead. This would be a good starting point. Read the entire thread, and also follow the threads on LAVA mentioned in there. Yes it is a lot of information but with a simple "Please help" we have very little to start giving more specific information.
08-28-2024 07:25 AM
Hi Ralf, thanks for your helpful post about LabView and the 64-bit version of FTDI D2XX driver. I had just encountered the same problem that you solved - the FT_HANDLE does not work on D2XX-64 when defined in the CIN as type 'U32'. I also cant find any FTDI documentation that describes the 64-bit versions of the D2XX-64 functions and parameter types. I dont think I'm brave enought to make a new set of CINs for D2XX-64 as I dont really understand the 'void pointer' data type. I saw from another of your postings that you recommend using this to correctly return FT_HANDLE. For now I will keep with 32-bit LabView where the D2XX CINs seem to work ok.
I wanted to ask you if there is a new problem with Win 11 (which is only 64-bit)? Can we still use LabView 32-bit (eg 2021 version) with D2XX on Windows 11, or will I be forced to use LabView 64-bit with D2XX-64?
Thanks
Paul Sellin
08-28-2024 07:52 AM
@phs2ps wrote:
Hi Ralf, thanks for your helpful post about LabView and the 64-bit version of FTDI D2XX driver. I had just encountered the same problem that you solved - the FT_HANDLE does not work on D2XX-64 when defined in the CIN as type 'U32'. I also cant find any FTDI documentation that describes the 64-bit versions of the D2XX-64 functions and parameter types. I dont think I'm brave enought to make a new set of CINs for D2XX-64 as I dont really understand the 'void pointer' data type. I saw from another of your postings that you recommend using this to correctly return FT_HANDLE. For now I will keep with 32-bit LabView where the D2XX CINs seem to work ok.
I wanted to ask you if there is a new problem with Win 11 (which is only 64-bit)? Can we still use LabView 32-bit (eg 2021 version) with D2XX on Windows 11, or will I be forced to use LabView 64-bit with D2XX-64?
It's not called CIN, that was an old technology in LabVIEW 5.0 to about 8.6 for LabVIEW specific external code components. The new node is called Call Library Node or CLN and interfaces to whatever is the platform standard for shared libraries, under Windows this are DLLs.
Of course can you install and run LabVIEW 32-bit under Windows 11. Windows 11 still can execute 32-bit applications and if you use DLLs they also have to be 32-bit in that case. However there will be a time where LabVIEW will not be available in 32-bit anymore. On all other LabVIEW platforms such as Linux and MacOS (until LabVIEW 2023Q3 at least) LabVIEW is purely 64-bit only since about 2016. The Windows version will at some point follow too, there are many software manufacturers who only support 64-bit applications for Windows anymore already.