Creating Velocity Profile Applications with the Motion Control Module
In the example, a velocity task is configured programmatically. The task consists of a single axis and a single move. The velocity and acceleration are set to default values. In the user interface, you can specify the motion controller board ID, axis number, and high and low values for velocity. A button simulates a trigger that toggles between the high and low velocity values. When the button changes state, the selected velocity is stored into the move. When you click the Start button, the current values for velocity and acceleration are downloaded to the controller. Changing the button state loads a new velocity value and the controller accelerates or decelerates as necessary to reach the new value. The velocity is maintained at that value until the button state is changed again or the Stop button is clicked.
To automate the trigger, use an NIMotionCapture object. Configure a single capture on the selected axis. You can use an external sensor to generate a digital trigger when you want the velocity to change. When the capture input changes state, the CaptureProgress event is generated. You can substitute the CaptureProgress event handler for the ValueChanged event handler that is associated with the toggle button.
Related Links:
Velocity Profiling (Template)
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).
