VI's with DAQmx run, but compiled to .net dll the functions hang

[HansWi]

We have a library for simple IO (Read/Write Bit/Byte N Bits)

It runs fine if I use the VI's directly, however, when I compile to a .net dll something goes wrong...

In a labview aplication I am able to call the constructor, call methods (the functions are also recognized) and everything looks fine.

When I run the program, it hangs at the first custom function called. It hangs, so I dont get any error...

I have added the project, VI.llb and compiled dll

I tried to mass-compile, but it didnt help and I call a standard added function (gettype) as initialization like this link (but they apply it in C#)

Could anyone help me?

[HansWi]

Could anyone confirm that the dll is indeed not working?

And what could be the problem?

Tip: close/save all other LV vi's: LV could hang (kill Labview.exe in taskmanager is enough to recover)

Other .net compiled dll's work fine, so only the one with DAQmx give problems...

[HansWi]

Can no one help me?

[HansWi]

Hmm, 1 day further....

Is there by any chance a Labview designer that knows how to help me?

[HansWi]

Could anyone look at my problem please?

[ninlmartijn]

Dear Hans,

Sorry for the delay in our response. I rebuild the .NET assembly and it was located in the \build directory at the directory where the VI selftest-manual.dll.vi was located in. This last VI did run without any problems (did run it multiple times).

- Was the assembly located in the same directory as your PC?

- does a simple assembly (so without calling a DAQ driver but only basic Labview functions) work?

Best regards,

[HansWi]

I did rebuild the assembly too and at my side it still hangs at the code call.

I have another .net dll with labview only modules which works fine:

- Create a directory

- WaitwithGUI

- Transpose2DArray (when I swith from bare vi to .net dll the 2 dimensions are switched...)

- Measurement to HTML file (2D array)

- Measurement to PNG (2D array)

I have a third .net dll which runs semi-stable

- 1 function goes wrong sometimes but that could be a code problem. Teststand however only gives error code -17500: exception in .net call, so I dont know what the real problem is.

I forgot to mention which version I use:

Teststand 2010 + patch f1 (developer version)

DAQmx 9.2.3

At the end it has to run on an operator machine.

Alvast bedankt voor de hulp / thanks in advance