09-18-2008 08:53 AM
09-25-2008 05:30 PM
Hey chvogt,
Some of my colleagues are quite interested in the behavior you are experiencing, though we cannot reproduce it.
What happens when you replace your calls to NI-Motion with calls to NI-DAQmx? How about when you remove the calls to NI drivers altogether?
09-26-2008 07:11 AM
I modified the test program to include a loop that makes a call to a NI-DAQmx function, DAQmxReadDigitalLines, and there is no speed change. Here are the results of the test.
The code for the 'Calculation Loop' is the same as the 'NI-Motion' loop code except it doesn't call the NI-Motion function. The speed of the calc loop is not affected.
Please let me know if I can provide any more information.
09-26-2008 01:55 PM
Hey chvogt,
Interesting results... we are still trying to reproduce this phenomenon. Can you post your exe (the one you made with the 3 loops) to the forum?
Could you try running the program in Windows safe mode and post the results?
Thanks for your continued interest and help!
09-29-2008 12:15 PM
Here is the newest test program.
I wasn't able to run the program in safe mode. I kept getting a 'FlexMotion32.dll not found' error. The file exists on the hard drive and I tried moving it and explicitly stating where it was located but still couldn't make it work.
09-29-2008 07:01 PM
Hi chvogt,
I tried this program but am not seeing the results you are seeing. Can anyone else reproduce this?