Problems building DLLs for Teststand 3.1with CVI-7.1

[markus kossmann]

I have to modify some code running with the CVI-Adapter of Teststand-3.1. So I've loaded  the old project file, did some modifications and rebuild the DLL without problems. But the resulting DLL doesn't work with Testand any more, because it doesn't seem to export it's functions any more.

For example there is a function

void __declspec(dllexport) rfe_dc_init_instruments(tTestData * testData, tTestError * testError)

the DLL target settings for exports are set to "Export What: Symbols Marked for Export"

But when trying to run the teststep which uses that function, it fails with

Details: Could not find function '_ rfe_dc_init_instruments' in DLL (or external module)  'N:\IDZ\RFE\rfe-dc.dll'

Error code -17005: could not find function in library

Any ideas how to fix that ?  

[Ken_Tobler]

Hi!

It seams that something went corrupted changing the code.
Do the function appears in the step configuration when you load your DLL?

Try recreate the step for loading the function in the DLL. It could be that in the sequence file the step loose the entry point for the function.

Best regards
Ken

[markus kossmann]

Do the function appears in the step configuration when you load your DLL?

Yes, opening the "specify module" window shows the DLL being used by that teststep and  the function both in the listbox with the DLL functions and also in the functioncall editor at the bottom of the window.

And just leaving that window without any change  with "OK" fixes the problem for that step. The first time I checked that window , I used "Cancel" to leave that window, because I seemed OK to me.  However you need to do that for all 45  teststeps using functions from the DLL in that sequence to fix the problem finally. 

[mama007]

Hi,

I have similar problem:

 "-17005; Could not find function in library."

"Could not find function 'ReadSerialPort' in DLL (or external module) 'C:\Production\Support Library\DAQmx\Library\Library.dll'."

Is there any solution to this problem.

It works if function is reloaded in teststand. But it is annoying to do this for every step in whole sequence.

This happened to me before, but it is more worrying this time with no of steps I have to open and reload prototype.

Thanks in advance

Smartsarath2003