06-15-2005 03:04 AM
06-16-2005 02:20 PM
06-30-2005
09:02 PM
- last edited on
07-11-2025
08:45 AM
by
Content Cleaner
Hey Zhijun,
The manual that you are referring to is an old manual, from 1998 or 1999, and it was written before there was support for Windows 2000. This manual also refers to the old Flexmotion Driver, and not the newest NI-Motion driver that is available. We recomend that you download and install the newest driver which can be found at Motion Control driver page. Also, when you install the driver, you will get the newest Motion Software Reference Manual with it. This new driver and manual will have support for your Windows2000 operating system. Something to point out about the new driver is that it does not handle Interrupts like the old driver did, but it will still be able to do what you need it to do. When you said you would like to "use an interrupt upon motion complete", you can use the Wait Until Move Complete function in the new driver. Another function you can use to check if motion is complete is to read the status of your move (polling it) and check to see if the move is complete. Now if you are wanting to check for a move complete in order to know when you can start your next move, then you will want to use Blending. You can read more about blending at the following Blending Tutorial page. When you said you would like to use the "high-speed catch event", I am assuming you mean the High Speed Capture with the new driver which is basically the same function, and it is an input trigger to the motion controller to see where the motion is currently at. With the old manual that you are looking at, the Interrupts are not supported under Win2000. So in conclusion, we recommend that you upgrade to the newest NI-Motion driver (currently NI-Motion 7.0) and use those functions in your application.
I hope this answers your questions. Please let me know if you have any further questions. Thanks.
Regards,
DJ
06-30-2005 10:09 PM
07-06-2005 05:01 PM
Hi Zhijun,
As you know, interrupts were replaced in favor of DMA transfers. This was overall a great improvement to the board.
Though priority of an onboard program is relatively low, the processing is done on the CPU of the motion controller - completely free from Windows scheduling. This makes an onboard program a possibility, but it will work best if you do not have a great deal of calls to the motion controller.
On the 735X series boards, we have upto 120 variables. I cannot think of a situation in which you would need to pass an indirect variable.
As far as help goes, what kind of compiled help file are you looking for? The NI Motion function reference and something else..?
Can you tell me more about your application? Its possible that the controller has other features available to it that might take the place of these interrupts you are looking for.
Thanks,
Robert
Applications Engineering
National Instruments