[Ajay]

Hi Infant

Have you installed FTDI Driver on the target machine?  Can you try installing this FTDI Driver CDM21228_Setup.zip here before executing the EXE?

—
Thanks,
AJ

[Ajay]

Hi Infant,

In most cases you don’t require to install FTDI installer separately on the destination PC.   When the executable runs, the FTD2XX.dll is expected in the “data” folder in parallel to executable file location.  Can you please confirm the folder target for FTD2XX.dll is at data folder?

FYR: Below is the screenshot of the logic used to find the DLL location in driver.

Thanks,
AJ

[Ajay]

Hi Syed Ulhaq,

Please find my answers below

Message Body:
1) The free trial version FTDI Driver for I2C SPI GPIO does not download. Can you send the evaluation file to my email?

You can download the driver either from ni.com here or from vipm.io here.

2) I want to control and monitor from control panel in LabView, the Microchip Fan RPM monitoring and PWM Controller device EMC2305, via I2C bridge FTDI device FT230X (CS-I2CMINI-01). Is there any LabView app/Vi code which connects to the I2C bridge consisting of FTDI device FT230X. Any help in this regard, explained step-by-step is highly appreciated

I believe there is no FT230X driver in LabVIEW so far.

3) I only want to use I2C bus. If i use FT4222H for I2C bridge instead of FTDI device FT230X, will i be able to control and monitor from control panel in LabView, the Microchip Fan RPM monitoring and PWM Controller device EMC2305 on I2C bus?

That should be possible as FT4222H supports I2C modes.

—
Thanks,
AJ

[Ajay]

You can find the examples that installed with the FTDI driver under NI Example Finder in Help menu or right under NI installation location in C:\Program Files (x86)

[Ajay]

Usually you would have installed 32-bit and 64-bit together.  You may find it in the Start Menu search.

 

[Ajay]

Hi Sarunas,

Thanks for reaching out.

This error might raise if you have missed installing and following the python installation as per this document

—
Thanks,
AJ

[Ajay]

Hi Bernhard

Could you confirm the bitness of LabVIEW (32-bit or 64-bit) where you’re trying to access quick drop or function palette?  It’s likely to happen if the driver is installed in 32-bit LabVIEW which goes under Program Files (x86), but then when you try to access it in 64-bit LabVIEW it will not show up in quick drop or function palette.

Please be noted, this FTDI driver is built for 32-bit LabVIEW and it will not reflect in 64-bit.

Thanks,
Ajay

[Ajay]

Hi Bernhard,

Can you please check in your VI block diagram Function Palette?

I just tried to install it in a fresh PC and found that Show In Palettes button is disabled as below.

However it’s available in the block diagram.  In both Quick Drop as well as in Function palette

Thanks,
Ajay

[Ajay]

The coercion has been there for quite a long time and it is not at all a trouble for many applications implemented so far.😊  I would suggest trying out with a simple VI (with a combination of examples from SPI read & write) to get a single read and write.

[Ajay]

Hi Masao,

You’re correct, the coercion dot exists in example VI as well.  I just noticed it’s hidden and only becomes visible when I moved blue wires.  I missed it in our remote session due to high resolution display on your side (& lower resolution display on myside).

However, we noticed in our session that example VI (SPI Master Write) works very well without any errors, and we even did the continuous run of the example VIs for repeatability for 10s of times.

I hope the change we did this morning is helpful to you, if the application doesn’t repeatedly run whiteout errors then I would recommend you to develop a simple plain VI with all required SPI write & read in linear sequence (without events or loops structures).  I believe that would prove your concept before taking to the application.  I strongly believe something on main application is bugging down to this issue.

Regards,
Ajay

[Ajay]

Hi Masao

As we had discussed over the remote session support, the root cause of the error here is due to the coercion dot we noticed in D2XX Open VI after passing Open flags from List Devices VI.  After replacing those VIs from example VIs it got resolved and we notice no errors through these VIs below

As a recommendation, I always suggest starting the work from prooved Example VI

Reference Example VI:

• Example_FT4222H_SPI_Master_Read.vi
• Example_FT4222H_SPI_Master_Write.vi

We noticed that there are no errors in example VI as in the screenshot below from our support session

There are application-level cleanups that might be required where proper handing of sessions (and closing wherever necessary).

Thanks
Ajay

[Ajay]

Hi Masao,

Can you please try with the example as shown in below using List Devices?  Use the device index 1 (from your screenshot) and open by serial number for that, it will eventually give the proper flags to the FTDI OPEN to open correct device.

Thanks,
Ajay.

[Ajay]

Hi Ajay-san

So far I tested with my FTD2XX driver and your FT4222.
Now I replace those FTD2XX to your driver.
Tested vi is below.

By using my driver, I checked all port are closed.
Then invoke above session and get result below.

The error happened at SPI_Master_Init.vi
Do you have any clue?

Regards,
Masao

[Author]

Posts