NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Labview-teststep when using Runtime-adapter

Hello,

i am using Labview and testand version 2022.

 

I have a problem executing a sequencefile with a labview-teststep that calls a DLL-function.

Direct under Teststand the teststep executes normally with Labview-Adapter = Runtime (autoselect)

 

Running the same in my custom c# opui  i get the attached error popup.

But when i switch to Adapter= Development, then it is working.

 

What can be the problem here?

 

Thanks for help

0 Kudos
Message 1 of 15
(1,078 Views)

Hello,

attached the detailed log from the error message.

 

When i remove the DLL from the VI then the teststep is running.

When i call only the dll as Donet-step then the dll is also running

 

But the error appears when executing a sequence with the VI containing the dll and running in runtime-mode

 

Thanks

 

0 Kudos
Message 2 of 15
(1,066 Views)

Does you C# OI happen to call the same DLL?

 

LabVIEW calling .net modules can be a PITA when using assemblies outside of the GlobalAssemblyCache (GAC).

 

Where is the dll located in respect to the calling VI?

0 Kudos
Message 3 of 15
(1,052 Views)

Yes, this dll is only oe time on the computer

The DLL is in a subdirectory below the VI.

The DLL is found from the  VI via the searchpath defined in labview at Tools->Options->Path->VI search path

Also in Teststand this path is defined.

 

 

 

0 Kudos
Message 4 of 15
(1,049 Views)

Would you mind trying with the DLL in the same directory as the VI?

0 Kudos
Message 5 of 15
(1,046 Views)

No difference 😞

(I moved the DLL to same location then opened the VI which notices the new location. Then saved the vi)

0 Kudos
Message 6 of 15
(1,043 Views)

Is the D Drive you are using a "real" drive or a mounted folder? If mounted... which method are you using for mounting?

 

0 Kudos
Message 7 of 15
(1,040 Views)

It is a real drive.

0 Kudos
Message 8 of 15
(1,037 Views)

Thanks for clarifiying!

 

So.... the sequence-editor is "just another" OI which is actually accessing the same API calls you C# OI is.

 

Have you tried using one of the example OIs that come with TestStand? Maybe we can get a hint where the difference lies

 

0 Kudos
Message 9 of 15
(1,028 Views)

It is working with the this UI:
C:\Users\Public\Documents\National Instruments\TestStand 2022 (32-bit)\UserInterfaces\Simple\CSharp\TestStand 2022 (32-bit) C# Simple UI

 

0 Kudos
Message 10 of 15
(1,025 Views)