Before running a motion control program, you must initialize the motion controller. One way to initialize the controller is to use the special utility that is included with each version of National Instruments motion control software: pcRunner for ValueMotion controllers or FlexCommander for FlexMotion controllers. However, you can also initialize the controller programmatically. The motion control LabVIEW VI libraries include special VIs for initializing the controller that you can run prior to running other programs. To initialize the controller programmatically in development environments other than LabVIEW, you have to write special routines, as outlined below.
Below is a recommended list of FlexMotion functions you should execute--in the order you should call them--for system-level and per-axis initialization. This recommended list covers the minimum areas of initialization for basic motion control. You can add additional functions to this list for enhanced system configuration requirements.
At power-up, all axes are automatically stopped, or they are killed when the axis circuits are disabled (when the motor is off). You must always execute a Clear Power Up Status function before attempting to initialize or control the FlexMotion controller. This power-up state is for safety and cannot be bypassed by saving custom defaults. If you use the Enable Auto Start function to specify an onboard program to start when the controller boots, the power-up state will be cleared automatically so the onboard program can run. A power cycle also resets velocity override back to 100%.
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.