Error when I try to run the FTDI Driver_forI2C_SPI_GPIO:lvlib:D2xx_Open.vi”

Home / Topic / Error when I try to run the FTDI Driver_forI2C_SPI_GPIO:lvlib:D2xx_Open.vi”

Home Forums FTDI FT4222 LabVIEW Driver Discussions Error when I try to run the FTDI Driver_forI2C_SPI_GPIO:lvlib:D2xx_Open.vi”

Tagged: ,

  • This topic has 3 replies, 1 voice, and was last updated 1 year ago by Ajay.
Viewing 3 reply threads
  • Author
    Posts
    • #5627
      David Butterfield
      Participant

      I’m trying out the demo version of the FTDI LabVIEW driver for I2C SPI GPIO and I’m getting the following error when I try to run the FTDI Driver_forI2C_SPI_GPIO:lvlib:D2xx_Open.vi”

      FTDI_Driver_for_I2C_SPI_GPIO.lvlib:D2xx_Error_Decoder.vi
      Complete call chain:
      FTDI_Driver_for_I2C_SPI_GPIO.lvlib:D2xx_Error_Decoder.vi
      FTDI_Driver_for_I2C_SPI_GPIO.lvlib:D2xx_Open.vi

      I’ve tried by Location, serial number, and description and they all give the same error.
      Do you know what I’m doing wrong?

      The FT4222H device shows in my Device Manager as follows:
      Device Manager FT42222 USB Interface A & B

      Thank you,
      David

      • This topic was modified 1 year ago by Ajay.
      • This topic was modified 1 year ago by Ajay.
    • #5630
      Ajay
      Keymaster

      Hi David,

      In order to help better the error code is would be required in this case. Could you please share the error code that you find on the error screen?

      Regards,
      Ajay.

    • #5637
      David Butterfield
      Participant

      Hi,

      The error code is 5102.

      Thank you,
      David

    • #5639
      Ajay
      Keymaster

      Hi David,

      Please find that error code 5102 means Device Not Found.  More error code details here.

      So 5102 could be caused due to inappropriate device reference that you provided at initialization.  I would recommend going through example VIs in the FTDI driver that can help you get started.  In one of the examples, you may find the device interface identifying example which can list possible device interfaces address.

      Thanks,
      Ajay

      • This reply was modified 1 year ago by Ajay.
      • This reply was modified 1 year ago by Ajay.
Viewing 3 reply threads
  • You must be logged in to reply to this topic.