LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

PXI-4071 DMM initialize failure, no soft panel in NI MAX

Solved!
Go to solution

I have an older system with a DMM (PXI-4071 in a PXIe-1062Q)  that stopped working the other day. I don't think this is a LabView problem, but I couldn't figure out a better place for it. I'm concerned it might be a hardware problem. The problem appeared when I ran my TestStand sequence and the LabView complained with the following error:

 

Error -1073807343 occurred at PLP initialize with Options.vi

driver status: (Hex 0xBFFF0011)

 

My searches mostly point to problems with VISA. When I go into NI MAX, I can run (and pass) the self-test, but I cannot get the soft panel to pop up. I click the soft panel button, it thinks for a few seconds and stops trying without an error message. In the 'VISA Properties' tab, it says the device is working properly and the VISA Alias has not changed. 

 

Any thoughts about what's going on, or suggestions to try? 

 

Thanks for your time,

Chris

0 Kudos
Message 1 of 4
(155 Views)
Solution
Accepted by topic author CSPy

Much more information would be helpful here.

 

What version of Windows? NI-DMM? What other software and hardware are in the system? Attaching a MAX Technical Report could help troubleshoot.

 

You mention NI-DMM, but then mention "PLP initialize with options.vi", which is a completely separate driver stack. That would seem to indicate the issue is with whatever hardware you are using with that, not NI-DMM.

 

Have you tried different slots in the chassis? Re-seating all your instruments? Full system shut down (as opposed to a soft reboot)?

Resetting MAX Configuration (note: This can be painful to recover so do this as a last resort)?

Tobias
Principal Software Engineer
Driver Software
National Instruments
Message 2 of 4
(122 Views)

Tobias,

Thanks for the response. It was exactly the kick-start my brain needed. You're right that I went down the path of troubleshooting the DMM and ran into issues, but it's really the next step in the TestStand that's having problems. Someone decided to steal a cable from a test setup that never changes and has no reason to change. Turns out it was required. My test is now up and running again. 

 

Thanks, again. 

 

Chris

0 Kudos
Message 3 of 4
(115 Views)

Glad to hear it!
Everything is obvious in hindsight, and it's easy to get stuck going down the wrong path.

Tobias
Principal Software Engineer
Driver Software
National Instruments
0 Kudos
Message 4 of 4
(96 Views)