Jack I have a problem then. Because in simulink, if I give ONE and only one sync pulse, then the FFT stops after one compute. I am not sure what to do about that, because the simulation seems to disagree with the documentation. The reason I am trying to give ONE sync pulse in simulation is because that is how I would like the hardware to run. But the simulation does not run as advertised. I am probably doing something wrong.
Also, the time for the sync pulse to come out of the FFT is longer than FFTLen/N, where N is the number if inputs. Tim ________________________________________ From: Jack Hickish [jackhick...@gmail.com] Sent: Friday, May 02, 2014 2:15 PM To: Madden, Timothy J. Cc: casper@lists.berkeley.edu Subject: Re: [casper] FFT compute time Hi Tim, > > Also, if we supply ONE and only ONE sync pulse, should the fft block compute > indefinately? My simulink seems to require a series of sync pulses to get > the FFt to work more than once. > > That's right, one and only one sync pulse is sufficient to keep the FFT operating indefinitely on successive windows of data. In fact, having multiple sync pulses without the correct period is much more likely to cause trouble. (See https://casper.berkeley.edu/memos/sync_memo_v1.pdf) Cheers, Jack
