cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base

Example Code

Top Contributors
Sort by:
Description Description-Separate-1 This Demo demonstrates how to acquire signals using the PXIe-5764 digitizer and perform signal analysis on FPGAs, such as FFT transformations. The demo system is composed of PXIe-5764 digitizer, PXIe-1095 chassis and PXIe-8881 controller, which can simultaneously collect data from 4 analog channels at 1GS/s sampling rate, with analog trigger, digital trigger, custom software trigger and other trigger functions, and the single-channel trigger frequency can reach 1MHz. Description-Separate-2 How to Use How-Separate-1 Download and unzip the attached ZIP-file Open PXIe_5764_Demo LabVIEW project and build the 5764_FPGA_FFT_DEMO.vi  Open the [Host] PXIe-5764 Demo Host.VI inside the LabVIEW project and follow the instructions on the Front Panel How-Separate-2 Additional Information Additional-Separate-1 Additional-Separate-2
View full article
Description Description-Separate-1 Simple Radar using MATLAB Phased Array Toolbox based on NI Hardware This example is the result of a project done in collaboration with Mathworks. The purpose of it is to Leverage Mathworks tools and NI rapid prototyping tools and hardware in order to excell in aerospace and deffense. A typical design flow in ADG starts with a simulation in a choosen language. (This can be c c# MATLAB or many other language). Then we have to move the concept to a test hardware to see how the design works in the real world Transitioning from modelling and simulation tools into hardware-based prototyping testbeds is a critical step in turning radar concepts into fielded capability. This example shows you how to model a radar system with MathWorks® Phased Array Toolbox™ and MATLAB, then how to use wrappers for LabVIEW to directly target NI vector signal transceivers from MATLAB. Allowing an accelerated, iterative design process, where new algorithms can be rapidly assessed both in simulation and with real hardware. The purpose of this example is to demonstrate standard capabilities of NI software and hardware. NI's contribution to this project is the interface with which the MATLAB Phased Array Toolbox is able to use a real PXIe-5840 hardware for transmit and receive.                 Description-Separate-2 How to Use How-Separate-1 Supported Devices: PXIe-5820/5830/5831/5832/5840/5841   Software Requirements: LabView 2020 or later NI RFSG Driver NI RFSA Driver MATLAB Phased Array Toolbox for MATLAB    Usage: Extract the attached .zip file Open the file below in MATLAB:MatLabCode\Examples\Radar_Example_NI_Hardware.mlx Set the generatorResource and analyzerResource parameter (needs to be the same as the name of the VST device in MAX you want to use) Run the MATLAB script Tweaking the signal parameters, the number of iterations and the parameters of the phased.RangeDopplerResponse function, you can get better range and speed resolutions.             How-Separate-2 Additional Information Additional-Separate-1 Description of attached files: MATLAB Phased Array Toolbox Based on NI Hardware.pptx Contains the explanation of the software layers, the hardware setup and the recommended calling sequence of the MATLAB wrapper functions.   RFSG_A_Wrapper for MATLAB.zip This file package contains the whole software stack and the MATLAB example code that has been built upon it. Also a few other minor but useful examples. MATLAB Radar example MATLAB NI.Transmitter System Object MATLAB NI.Receiver System Object RFSA/RFSG wrapper DLLs LabView project to build the RFSA/RFSG wrapper DLLs Preliminary Python wrappers for RFSG/RFSA Simple Python radar examples                 Additional-Separate-2
View full article
Description Description-Separate-1 Introduction   This example will demonstrate the synchronization capability of multiple reconfigurable scope devices (PXIe-5170/1/2) using the PXIe-6674T timing and synchronization module. The example is built using the standard Stream to Host sample project, modification to the FPGA target is possible, users can add inline DSP and make use of the general purpose PFI lines that are only accessible from the FPGA on these devices. The HW setup for this demonstration consists of a PXIe-6674T card in the timing slot of a PXI chassis, and arbitrary number of PXIe-517x cards in the other slots. It is advised to take care of proper thermal management considerations, keep the chassis’ fans on high and leave spacing between the cards.                                                                  Figure 1. Hardware Configuration Figure 2. PXI Express Star Connectivity Diagram Figure 3. PXIe-6674 clock and trigger routing   After downloading the attached zip, open the LabVIEW project and open Stream to Host (Host).vi in the project tree. Set the devices in the appropriate controls, and setup the proper DStarB trigger lines to each of the PXIe-517x modules in your system. Information regarding trigger routing can be found in the user manual of your PXI chassis. Configure the channel parameters and timing module routing. Make sure to click Send Trigger after the Ready to Trigger indicator turns on.   Figure 4. Synchronization example soft front panel   To get information about the accuracy of the acquisition, switch to the Time Skew Statistics Statistics tab, to get results from delays of adjacent channels, and further statistical analysis such as chart display and histogram.   Results    Time skew between devices has been measured using Arbitrary Waveform Generator (PXIe-5422) and RF splitter. Figure 5. HW Setup for time skew measurement   The connection diagram above describes the architecture of this application. The timing device shares its onboard OCXO clock to the PXI backplane, so each scope can derive their sample clock from the same clock source. The start trigger for the acquisition is also shared from the PXIe-6674T card, using the DStarB trigger lines. Time skew between devices during run to run is changed  sample=4ns. Standard deviation is up to 1ps.   Figure 6. Device to device time skew, histogram. Mean and std values     Description-Separate-2
View full article