Missing data from real bus trace

Question In slave mode, while reading data from “ftdi_slave_read” it is giving a data frame which is not transmitted from the opposite end. Below data is transmitted from the opposite end(line 7) Analyzer screenshot where data shows mismatching Data received from LabVIEW, notice line no 7 where data is mismatching. I feel that it taking from the FTDI chip buffer. Is there any steps or function to clear buffer data of FTDI hardware? Answer Scope/analyzer shows an extra nibble (one byte + a nibble) in every frame.  The driver's text file report shows only the first byte and doesn't show the extra nibble of the frame.  There could be a setting in the analyzer/scope which shows the extra nibble that confuses you.
Read More

32 bit vs 64 bit FTDI driver

Question 1 I use LABVIEW 32 bit and I cannot change it to 64 bit what can I do else? Answer FTDI FT4222 driver is tested only with 32-bit LabVIEW. Having said that, the most application can be built into a 32-bit version of LabVIEW with few exceptions where other dependencies of applications are 64-bit so it's necessary to build in 64-bit. In such a case, please feel free to contact for further support. Question 2 We purchased 64-bit LabVIEW, but this driver only supports 32-bit LabVIEW. Should we purchase 32-bit LabVIEW again? Answer Not necessarily. Usually, the same LabVIEW license works for both 32-bit and 64-bit versions. Refer NI website here that indicates LabVIEW doesn't license 32-bit and 64-bit separately.  It comes together all the time.  It would be just…
Read More