> > There's no way to know/control how much time is spent between the > actual "execution" of two consecutive FTDI commands: clock jitter > comes from various sources: FTDI FIFOs, USB bus latency + async clock > delay (USB HW frames vs. USB stack), various software stacks, multi > tasking scheduling, etc. > > If you need a precise clock, I think you should not rely on bit > banging mode at all. >
Sorry I was not more specific. We do not need 50Hz frequency. The scenario is to send (max) 3072 bytes to the SPI and than to pull the trigger (to set LATCH ENABLE pin HI). Above mentioned will be executed in the infinitive loop. The maximal speed to repeat the loop is about 30 to 50Hz. Petr -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to libftdi+unsubscr...@developer.intra2net.com
