Remote Systems and NI-Motion

NI Motion Measurement & Automation Explorer

Remote Systems and NI-Motion

For an RT system, you can configure an NI motion controller on a remote PXI chassis through the remote configuration feature of MAX. You must install NI-Motion onto the remote system to use RT. Then, program the RT NI-Motion application exactly the way you would program any other NI-Motion application.

Complete the following steps to install NI-Motion onto the remote system.

  1. Install one of the following software options onto the host system:
    • NI-Motion (73xx controller support)
    • NI SoftMotion Controller
    Tip  Refer to the Getting Started: NI SoftMotion Controller for Copley Controls CANopen Drives manual for information about this product.
  2. Launch MAX.
  3. Expand the Remote Systems tree.
  4. Highlight the system on which to install NI-Motion.
  5. Select the Software tab.
  6. If NI-Motion is not already installed, right-click within the dialog box and select Install Software. A dialog appears that lets you select what to download. Make sure the checkbox next to NI-Motion RT is selected.
  7. Click OK and wait for the software to download.

After the software downloads onto the remote system, complete the following steps to configure the remote NI motion controller.

  1. Wait for the remote system to reboot so MAX is able to communicate with it.
  2. Expand the Remote Systems tree and then expand the Devices and Interfaces tree.
  3. Right-click the remote motion controller icon and select Map to Local Machine. This assigns a local board ID to the remote motion controller in the host system.

    Mapping the remote controller into the local system allows you to configure the controller through MAX exactly as you would a controller that is in the host system. You can initialize the controller, download firmware, and use the interactive and configuration panels exactly as you would on a controller installed in the host machine. You also can write VIs using the remote motion controller through the local board ID assigned to it.

    This allows you to write and debug your VIs on the host, and then download them to the remote system when you are ready. All you need to change is the board ID in your VI from the locally assigned Board ID to the ID assigned by the remote system.

  4. Browse to Devices and Interfaces under My System, where there is a shortcut icon next to a new controller name.

    For example, if the motion controller on the remote system is a PXI-7334, and the remote system has an IP address of 123.456.789.000, then the shortcut device would show a name like PXI-7334 (X) on (Y).

    X is the board ID assigned to the board by the remote system. Use this board ID for VIs that are downloaded to the remote system through LabVIEW RT.

    Y is the board ID assigned to the remote motion controller by the local system. Use this board ID for any VIs that run on the host and use the remote motion controller.

    To remove the mapped motion controller, browse to My System under Device and Interfaces. Right-click the mapped controller and select Unmap Remote Device. You should unmap devices when you no longer need to use them from the host machine.