Teststand 2010 can't load DLL build by labview 2016

[Tambrook]

I am using teststand 2010. Recently I update my labview from 2010 to 2016 and find the DLL built by labivew 2016 is not able to call in teststand 2010. While the one built by labview 2010 is OK. Is it a compatibility issue?

[kosist90]

I didn't find clear information regarding some chart compatibility between LabVIEW and TestStand versions; but are you able to run some simple code module (vi) in LabVIEW 2016 in TS 2010? If so, then they are compatible.

What come to my mind - in what environment are you trying to run dll? In development, or Run-Time? Are really versions of dll, and adapter the same (I mean, that if dll is build in LV2016, it has to be run in dev environment of LV2016; or with Run-Time LV 2016). Did you re-built dll in LV2016, or just trying to run via LV2016 dll, which was built in LV2010? If so, it's better to rebuild dll in LV2016, and then execute it with this version of LabVIEW.

I know, that I didn't give any particular answer - it's just brainstorming, maybe something will be helpfull for you...

Sincerely, kosist90

Check out new features of LabVIEW 2017!

[Tambrook]

hi kosist,

Thanks for your quick reply.

Both labview and teststand are development enviroment. I can run labivew 2016 vi in teststand 2010. But when I open my labivew project and rebuild the DLL build and call the one of the function in DLL using 'c/c++ dll' adapter in teststand, it return with error 'This function either does not have parameter information in the DLL or uses types not recognized by Teststand'

[red.free]

The functionality you are looking for is not supported between these versions.

TestStand 2010 is only supported with LabVIEW 8.5 to 2013. 

This means you might be able to get some functionality between the TestStand 2010 and LabVIEW 2016, but anything that doesn’t work is not necessarily unexpected.

This link shows the compatibility between TestStand and LabVIEW.

http://www.ni.com/teststand/product_lifecycle/

[Tambrook]

This is really inconvenient. I have new labview, but because of that, I can't use it. :(((((

[j_dodek]

Hi

I am not really an expert on LabView.

But i if have a dll not running my first choise is Dependency Walker. (www.dependencywalker.com) Just to "see"  dll's dependencies. Most

time there is another dll missing.

And take care that you are building the dll for x86.

Hope this helped

Juergen