LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

PXI-4071 Driver C File

I installed NIDMM 3.0.1 and noticed there wasn't .C file like I've found with other NI drivers.I'm looking for some basic PXI-4071 functions.

 

Is there a C file that accompanies nidmm.h?

0 Kudos
Message 1 of 8
(4,404 Views)

eatmontr:

 

NIDMM 3.0.1 includes the function panel nidmm.fp, which has all the DMM functions that NI has exposed in the driver.  You don't need the .c file to use the functions in the function panel: you just need to #include the .h file in your .c file and add the .fp and .lib files to your project.  (Use the CVI project window menu: Edit >> Add files to project >> Instrument (*.fp) or Library (*.lib)).

 

Once the files have been added to your project, you can just double-click on the .fp filename in the project window, and you can see all the exposed functions.

 

 

0 Kudos
Message 2 of 8
(4,395 Views)

If you are not using, LabWindows/CVI, then you can reference the C++ instructions as the process and header for C and C++ are the same.  The function and their descriptions can be found in the DMM Help file.  Hopefully this helps!

Regards,


h_baker
National Instruments
Applications Engineer
0 Kudos
Message 3 of 8
(4,369 Views)

Is there a way to make a .dll file (requested by project head) from the .fp file?

0 Kudos
Message 4 of 8
(4,337 Views)

Take a look at this article.  It walks you through the process of creating the dll.  Let me know if you have any issues.

Regards,


h_baker
National Instruments
Applications Engineer
0 Kudos
Message 5 of 8
(4,300 Views)

Does this allow a .DLL file to be created strictly from the .FP file? I'm looking to make a .DLL out of the nidmm.fp file, but without the .C file I'm getting errors.

0 Kudos
Message 6 of 8
(4,291 Views)

Hi,

 

No, it does not. The actual implementation is in the .C file, so that file will still be necessary.

 

Best Regards,

 

John M

National Instruments
Applications Engineer
0 Kudos
Message 7 of 8
(4,265 Views)

So at some point you need to go back to your project head and say that the source code is not available, but a fully debugged and functional driver is available.  I'd suggest that rather than trying to reinvent the wheel, you use the existing driver as is and move on to more important issues.

0 Kudos
Message 8 of 8
(4,259 Views)