Examples and IP for Software-Designed Instruments and NI FlexRIO
 |
NI Static Digital Host Example for the NI PXIe-5644R/45R »
This example uses NI-RFSA and NI-RFSG instrument driver FPGA extensions, along with the instruction sequencer and SPI IP to create FPGA personalities for the NI PXIe-5644R and NI PXIe-5645R that have the ability to implement static digital communication and control. |
Description: This example uses NI-RFSA and NI-RFSG instrument driver FPGA extensions, along with example IP to create FPGA personalities for the NI PXIe-5644R and NI PXIe-5645R that have the ability to implement static digital communication and control. The NI PXIe-5644R and PXIe-5645R Vector Signal Transceivers each feature 24 digital lines that can be used for either digital output or input. This VI Package installs example code and the necessary dependencies that provide the user with software-timed control over these lines.
Additional Documentation:
- After installation - C:\Program Files (x86)\National Instruments\LabVIEW 2012\examples\NI Static Digital Host Example for the NI PXIe-5644R-45R\documentation\NI Static Digital Host Example for the NI PXIe-5644R-45R
Compatibility:
This example was designed and tested using the following software packages:
- LabVIEW 2012
- LabVIEW FPGA Module 2012
- NI-RFSA 2.7
- NI-RFSG 2.9
- Hardware:
Dependencies:
- None
Latest Version:
Previous Versions:
- none available
Installation Notes:
After installing a VI package containing an instrument driver FPGA extensions host example, before opening any of the host VIs, move the sub-directories installed under the example parent directory into c:\Program Files\National Instruments\NI VST\Custom Bitfiles\ (32-bit Windows) or c:\Program Files (x86)\National Instruments\NI VST\Custom Bitfiles\ (64-bit Windows). The Custom Bitfiles directory may require manual creation, and this process requires administrative privileges. After moving these files, c:\Program Files[ (x86)]\National Instruments\NI VST\Custom Bitfiles\[Sub-directory Name]\Open FPGA Session.vi" should be a valid file path.
Note: All source on this community is distributed using VI Package Manager (VIPM). For more details on VIPM, please read A Note on VI Package Manager
