Hi,
I'm using FTDI IC FT201XB for I2C to USB conversion for reading a EEPROM accessing as a Virtual COM Port. I have programmed the device to enumerate as Virtual COM port and it is visible in the device manager also but I cannot find any kind of read or write operation occurring between my FTDI chip and the EEPROM ( I2C).
I am guessing there might be issues in the configuration settings of VISA VCOMin VISA test panel and I tried by trails using multiple options changing the baud rates, stop bits, flow control etc .. but nothing worked out to my application.
The examples provided in the FTDI site is made using the D2XX drivers (.dll files) but whereas my task is to achieve the Read and write operation via VCOM port.
If anyone worked on it or if with any idea about it; share the steps involved in setting the VISA test panel configuration kindly share it.
Thanks in advance.
Fredrick Johnson JOSEPH
Are you using the dll o labVIEW drivers for that IC? Some time agou I used one FTDI IC, dont remeber wish one, but I programmed it using its dll funtions and LabVIEW driver very well.
I have been using LabVIEW and the FTDI and I had some issues when I used rates out of limit. If I try to read faster then the limit I get blue screens. But this is the only issue I had. If you send me your email I can send you some example VI's. You can find some help on Arduino forums. The arduino board also uses the FTDI.
Hey thanks to all for your suggestions.
I have found the solution for it; the problem was not with VISA or LabVIEW but was with FTDI device. The clocking factors were the point of issue between the master and slave architecture. I didn't use any clock generator externally to connect both slave devices. Being FT-X series of converters are clock-less I can't establish the protocol conversion between slaves unless FT-X inputs are clocked for example a micro controller with I2C outputs. though it was a blunder mistake according to the datasheet of FT-X series converters ( including FT200XD, FT201XB.. Etc.. ) the internal clock was used only for the internal protocol conversion and was not connected to communicate with the slave devices. Hence it went out wrong.
Therefore the SCK input for the I2C was single directional (i.e. as an input ) and that can't serve being an output. In applications like interfacing a I2C based sensors and I2C based acquisition these FT-X series devices can play a major role in PC or portable device based control and operation.
Hence FT-X series can be literally called as " PROTOCOL CONVERTERS" for USB ended application.
Anyways latest version of FT4222H could serve being Master-Slave for establishments.
Thanks a lot all for helping me out.
- Badges
- Science topic
- Similar topics
- Biological Science
- Physiology
- Biosignals
- Biomedical Signal Processing