Deactivation or Activation Issue

When I try to deactivate the product I have some issues like below. Activate Add-ons Issue (One or more required input elements are missing) Activate Add-ons (Winsock cannot connect to server) Solution Check if the internet connection is proper to the machine in order to activate the toolkit.Contact NI for tools support
Read More

FT4222 Modes

Reference Documents: An_329_user_guide_for_libft4222D2XX_Programmer’s_Guide(FT_000071)DS-UMFT4222 Evaluation Module FT4222 operates in 4 modes and it's important to consider the modes while any error occurs due to resource constraints. Table explaining the modes and associated interface to those modes. Below table explains the DCNF0 and DCNF1 pins on UMFT4222 evaluation board for different modes of operation. Below is the jumper pin positions for the mode-0 and mode-3
Read More

5000 series error codes in FT4222 Library

Most of the error code from FTDI library is generated from actual LibFT4222 driver DLL. Below table explains the error code equivalent match between those. Refer below docs for more details from FTDI. An_329_user_guide_for_libft4222D2XX_Programmer's_Guide(FT_000071) FT4222 LabVIEW Error CodesError Description (Equivalent to LibFT4222 DLL)5100FT_OK5101FT_INVALID_HANDLE5102FT_DEVICE_NOT_FOUND5103FT_DEVICE_NOT_OPENED5104FT_IO_ERROR5105FT_INSUFFICIENT_RESOURCES5106FT_INVALID_PARAMETER5107FT_INVALID_BAUD_RATE5108FT_DEVICE_NOT_OPENED_FOR_ERASE5109FT_DEVICE_NOT_OPENED_FOR_WRITE5110FT_FAILED_TO_WRITE_DEVICE5111FT_EEPROM_READ_FAILED5112FT_EEPROM_WRITE_FAILED5113FT_EEPROM_ERASE_FAILED5114FT_EEPROM_NOT_PRESENT5115FT_EEPROM_NOT_PROGRAMMED5116FT_INVALID_ARGS5117FT_NOT_SUPPORTED5118FT_OTHER_ERROR5120FT4222_DEVICE_NOT_SUPPORTED5121FT4222_CLK_NOT_SUPPORTED // spi master do not support 80MHz/CLK_25122FT4222_VENDER_CMD_NOT_SUPPORTED5123FT4222_IS_NOT_SPI_MODE5124FT4222_IS_NOT_I2C_MODE5125FT4222_IS_NOT_SPI_SINGLE_MODE5126FT4222_IS_NOT_SPI_MULTI_MODE5127FT4222_WRONG_I2C_ADDR5128FT4222_INVAILD_FUNCTION5129FT4222_INVALID_POINTER5130FT4222_EXCEEDED_MAX_TRANSFER_SIZE5131FT4222_FAILED_TO_READ_DEVICE5132FT4222_I2C_NOT_SUPPORTED_IN_THIS_MODE5133FT4222_GPIO_NOT_SUPPORTED_IN_THIS_MODE5134FT4222_GPIO_EXCEEDED_MAX_PORTNUM5135FT4222_GPIO_WRITE_NOT_SUPPORTED5136FT4222_GPIO_PULLUP_INVALID_IN_INPUTMODE5137FT4222_GPIO_PULLDOWN_INVALID_IN_INPUTMODE5138FT4222_GPIO_OPENDRAIN_INVALID_IN_OUTPUTMODE5139FT4222_INTERRUPT_NOT_SUPPORTED5140FT4222_GPIO_INPUT_NOT_SUPPORTED5141FT4222_EVENT_NOT_SUPPORTED5142FT4222_FUN_NOT_SUPPORTLabVIEW Error codes equivalent of LibFT4222 DLL
Read More

FTDI does not communicate after building executable

Questions Question 1 We have purchased a license for FTDI driver for I2C SPI and GPIO from NI. While working with a code we are successful in communicating with the FT4222H chip. But after building the executable, the EXE is not communicating with the chip. Question 2 There are problems when trying to build an application. The Vi is running well, but the executable fails to connect to the FTDI module. There are some dependency problems in the project. What is wrong? We're using LabVIEW 2020, 32-bit. Solution If you get some dependency problems while building the application, it's likely that files are moved to other locations from the regular directory where the library looks for the files. Try following steps to fix this issue, General Troubleshooting guidelines for DLL missing for executable:Step 1.  Ensure…
Read More