nrp wrote:
nothing too fancy going on, DAQmx read, no network involved. Also, its not really a glitch, more like a burp of around 1/2 a second long every 12 seconds. I call it a burp as i causes my nice linear data to bulge out horribly.
Weird thing is this does not happen earlier in a different part of the test sequence, almost as if it is the actual hardware under test that is misbehaving...
As Ben would say "Sea-Story Time"--
I had the exact same thing happen to me a few years ago. While developing a test with hardware in the loop I noticed that every 12 seconds my measurements went way out of the expected range. We spent days looking into the cause since the electronics happened to be the inner guts of an implantable medical device, and, well --- that would be kinda upsetting to have it go wonky every 12 seconds. As I recall, I had tried to demo the issue to a senior engineer and could not repeat the issue untill I turned on the temperature chamber that held the DUT at 37C. Turned out the the exposed silicon IC was sensitive to the IR light element we used to keep everything at body temperature and the chamber needed to heat for about 1/2 a sec every 12 secs to maintain 37C.
Don't rule out unexpected system interactions just yet.
What is different between the stim package earlier in the sequence and the stim package in the offending step?
Message Edited by Jeff Bohrer on 12-21-2009 01:58 PM
"Should be" isn't "Is" -Jay
