Signal Generators

cancel
Showing results for 
Search instead for 
Did you mean: 

Using Basic Function Generator Example Project

I am a beginner in the NI world, so please bear with me on a very basic question:

 

I have a PXI-5402 function generator running in a PXI-1031 chassis. I am able to use the Test Panels in MAX to verify the generator is working. I am running Visual Studio 2008, and have installed Measurement Studio 2013. I have also installed FGEN, with it's associated drivers. I went to the Measurement Studio tab in Visual Studio, and then to one of the Measurement Studio Examples: BasicSignalGeneration. I built this project, and ran it. It creates a "virtual" function generator, with a scope where I can watch the output,  but triggers no actual output/control of the PXI-5402.

 

And now I'm stuck: what do I actually need to do to modify the BasicSignalGeneration example to actually trigger an output on my PXI-5402? Do I need to add a specific class to the example project? I added the niFgen_32.dll. I know the location of the PXI-5402 from MAX, but am not sure how to modify the example to reference my actual generator module. 

 

Thanks!

0 Kudos
Message 1 of 4
(5,206 Views)

Hey jvavra,

 

Take a look at some of the more advanced examples like the Triggering one. They should already have this functionality built in!

Libby B.
Applications Engineering Specialist - RF Wireless
National Instruments
0 Kudos
Message 2 of 4
(5,148 Views)

jvara,

 

There are C and Visual Basic examples installed with the NI FGEN driver. You can find them by navigating to Start -> Programs -> National Instruments ->NI-FGEN -> Examples

 

Jason L

Product Support Engineer
National Instruments
0 Kudos
Message 3 of 4
(5,145 Views)

FYI: In the latest version of FGEN, the VB versions of the examples are NOT included. They CAN be found at http://www.ni.com/examples/.

 

Also, as noted by NI Product Support Engineer "Libby", in the VB versions of the examples, the namespace declaration in the niFGEN.vb wrapper file is wrong (or, at least, doesn't match the examples).

 

The line "Namespace NationalInstruments.ModularInstruments.Interop" needs to be changed to "Namespace InstrumentDriverInterop.Ivi". 

0 Kudos
Message 4 of 4
(5,107 Views)