[SOLVED] Read status of FT245RL pins

mackowiakp · 09-03-2016, 06:03 AM

Sorry for my ignorance but I am very new in FTDI chip Linux software development.
I have module based on FT245RL chip, programmed to be 4 port output (relays) and 4 port opto isolated input unit.
I found out in Internet program in C to turn on/off relays connected to outputs D0 to D3. After compiling it works properly. Below draft of this working program:

Code:

/* switch4.c
 * # gcc -o switch4 switch4.c -L. -lftd2xx -Wl,-rpath,/usr/local/lib
 * Usage
 * # switch4 [0-15], for example # switch4 1
 * */
    #include <stdio.h>
    #include <stdlib.h>
    #include "./ftd2xx.h"

    int main(int argc, char *argv[])
    {
       FT_STATUS ftStatus;
       FT_HANDLE ftHandle0;
       int parametr;
       LPVOID pkod;
       DWORD   nBufferSize = 0x0001;
       DWORD dwBytesWritten;

              if(argc > 1) {
                      sscanf(argv[1], "%d", ¶metr);
              }
              else {
                      parametr = 0;
              }  

         FT_SetVIDPID(0x5555,0x0001);  // id from lsusb
         FT_Open(0,&ftHandle0);
         FT_SetBitMode(ftHandle0,15,1);

         pkod=&parametr;

        ftStatus = FT_Write(ftHandle0,pkod,nBufferSize,&dwBytesWritten);
        ftStatus = FT_Close(ftHandle0);
    }

My question is. How can I read in the same program, status of D4 to D7 pins, programmed as inputs? I mean about "printf" to stdout the number representing status (zero or one) of input pins (or all input/output pins).
Can anybody help newbie ?

rtmistler · 09-08-2016, 11:50 AM

Zero experience with this chip, however have done similar stuff with other peripherals in the past and typically a function such as FT_Write() has a concurrent FT_Read(). I see that the ftd2xx.h file does contain a read function. I can't tell in your program how you addresses D0 through D3, except for the parameter. Therefore I would try using FT_Read() and see if I could specify the D4 through D7 bits using that function.

mackowiakp · 09-08-2016, 01:03 PM

Finally I found out whats going wrong. The problem was the version od ftdi library. Correct and actual version dedicated for x86_64 platform is HERE