NIDmm returns -1074118639 on Init

[OnlyOne]

Hello,

i am executing the generic IVI functions for IviDmm.

For my NI PXI 4070 i installed the NIDMM-Driver.

When executing under TestStand the Init returns 0 and all other DMM functions are working.

But when executing the testplan in a custom GUI then the Init returns -1074118639.

When asking the driver what the error means then it says "Unknown status code".

Does someone now what can be the problem here?

My IviSwtch instruments are working without problems direct in teststand and also under the GUI.

Thanks for all ideas.

BR

Windows 7 64bit

TestStand 2016 f1 32bit

Ni Max 16.0.0.f0

ICP 16.0.1

[NikoNR]

Hi OnlyOne,

when looking into this error, it seems that it usually has to do with drivers beeing in an old or corrupted state:

Archived: Error 1074118637 in Calibration Executive when Calibrating a DMM - National Instruments
http://digital.ni.com/public.nsf/allkb/46F62B301745498C8625730200754A14

(please do NOT send the board to us, I don't think this is the issue).

Have you tried the DMM Soft front panel? Does this work with the board?

Cheers, Niko

[OnlyOne]

Yes, of course this is an error of Ni-DMM driver.

The driver does not free the handle after executing "Close"-function.

Which means no other program can execute an "Init" because NI-DMM still blocks the access.

I dont have any problems when using only one program.

[NikoNR]

But the "close" works from teststand works without giving any error?

Can you share a simplyfied Teststand sequence that does not work? I might be able to get my hands on the hardware and test it.

Cheers,

Niko

[OnlyOne]

I am executing a custom teststep (not the Teststand builtin IVI) that executes:

viStatus = iviDmm_close(vi)

this line returns 0.
"vi" is the created object from Init-function which is saved in StationGlobals to pass it to the following functions.

[OnlyOne]

Perhaps the problem is that the created object from the "init" function is still there?

I found out that i can run the close function multiple times in the same program. Shouldnt be the error be something like "handle not valid"...?

Is there a TestStand-function to delete the object after executing the close-function? Perhaps this unlocks the instrument.
Hmm, or perhaps not because the close of my other instruments are not blocking when running in two programs...

[NikoNR]

Hi OnlyOne,

from your last posts, I just wanted to ask which adapter you are using? C?

When you hand over the handle of the instrument to the close function, it should only work once.

Is this true for you?

Cheers,

Niko

[OnlyOne]

I am using the DotNet-Adapter which is only a wrapper and is calling a c++ function.