XPost: rec.crafts.metalworking, alt.comp.os.windows-xp   
   From: muratlanne@gmail.com   
      
   "Lloyd E. Sponenburgh"  wrote in message   
   news:XnsA0836DB33819Elloydspmindspringcom@216.168.3.70...   
   > "Jim Wilkins"  fired this volley in   
   > news:jspm3l$heq   
   >>   
   >   
   > Jim, I won't be didactic, but you _know_ that loop timing isn't the   
   > way   
   > to "time" anything accurately, unless the entire system is running   
   > with   
   > disabled interrupts....   
   > LLoyd   
      
   We are discussing different things. The loops I described generated   
   timing for I2C data transfer, which was mostly self-clocking the way   
   we did it. The parallel port A/D converter made single resistance   
   measurements. The DAQ I'm planning will monitor temperature or battery   
   voltage and current. I have a digital storage scope and a spectrum   
   analyzer for high-speed signals.   
      
   I built a 16-bit A/D converter on a Mac NuBus proto card and during   
   its checkout tried to check its frequency response with an FFT of a   
   precision sine source, because I had one. As expected the clock   
   interrupt disturbed the results too much. The project manager though   
   windowing the data might help since we couldn't time it accurately in   
   LabVIEW, but as I could show that its noise and monotonicity was +/-   
   one bit he accepted it.   
      
   It went into an instrument like this to measure the power sensors:   
   http://www.navair.navy.mil/frcsw/npsl/articles/Pages%20from%20WR   
   28-42%206-Port%20(old).pdf   
      
   jsw   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)