Error -1074118656 in NI-DMM

Updated Mar 15, 2021

Reported In

Software

  • Measurement & Automation Explorer (MAX)
  • TestStand
  • LabWindows/CVI

Driver

  • NI-DMM

Issue Details

  • My PXIe-4081 can be detected in NI Measurement & Automation Explorer (MAX), I can launch other instrument's test panel but I will get an error -1074118656 when I launch DMM soft front panel.
  • I am using TestStand and a NI 4060 to test a unit. However, when I run the test sequence, I receive the following message:

    Error.png
  • When I run an NI-DMM example VI in LabVIEW, I receive the following error:
     Error -1074118656 occurred at niDMM Initialize.vi 

     Possible reason(s):
     Error: (Hex 0xBFFA4000) ERROR: Device was not recognized. The device is not supported with this driver or version.

 

Solution

This error can be caused by:
 
  • Incorrect instrument descriptor.
Make sure a valid instrument descriptor for a NI-DMM device has been entered on the front panel of the VI. Valid instrument descriptors for such device should have one of the following formats:
  • NI-DAQmx name
  •  DAQ::NI-DAQmx name[::INSTR] 
  • DAQ::Traditional NI-DAQ device number[::INSTR] 
  • IVI logical name
The NI-DAQmx name or Traditional NI-DAQ device number for the DMM device is listed in NI MAX, under the hardware tab in Devices and Interfaces.

Refer to the NI IVI Driver Help for guidance on how create IVI logical names for a DMM. In this help file, refer to the IVI Driver Help Introduction»Configuring Your System Using MAX»Measurement & Automation Explorer Help for IVI section.
  • Incorrect settings at Initialize with Option VI.
Before calling the VI in driver simulation mode, Simulate should be set to 1 in the Option String control.
  • NI-DMM 3.0.6 version.
With the release of this driver, the support for the DMM devices NI 4050 or NI 4060 was broken on Windows XP machines. However, with the release of NI-DMM 3.0.6 f1, this issue has been fixed and normal operation of the NI 4050 and NI 4060 devices is restored.

In case of none of the solutions proposed resolve the issue, reset MAX database. After the reset, make sure the device’s name/number in MAX still matches the application's. Otherwise, the error will persist.