07-18-2006 12:59 PM
07-19-2006 07:08 PM
Jason,
Thanks for your post. This is indeed strange behaviour that we have not seen. Our older drivers (expecially value motion) are very inefficient and our development team has spent a considerable about of time to speed up and optimize the processing speeds of our newest Motion driver (7.2.1). We definatly want to make sure you see increased performance!!
Could you tell us a little more about your system setup - which motion card you are using, types of motor control application, number of axises, PID tuning (if applicable), etc? The more information the better!! Also, can you give us a more detailed view of your development PC and what benchmarks or spec you are using to get the rates you mentioned above?
Thanks,
Scott Savage
National Instruments
Applications Engineering
www.ni.com/support
07-19-2006 07:36 PM
Thanks for the reply. Here are the information you need:
Pls let me know what else you need. Pls also give it a try on both Motion Control 5.1.1 and 7.1 (or 6.0). You can tell the difference. I'm eagerly waiting for the response.
Thanks.
Jason
07-20-2006 06:36 PM
Jason,
I have informed our lead developer in R&D and we are eager to look into the issue. We will attempt to recreate this behavior you have seen. I am heading out of town next week, but another engineer on my team is looking into this issue now.
We will be in touch :).
Thanks,
Scott Savage
National Instruments
Applications Engineering
www.ni.com/support
07-20-2006 06:50 PM
Thanks. Please keep me posted.
Have a nice trip!
Jason