how can I change the DLL called by an action statment in Test Stand 3.5 during r

[VisualMath]

How can I change the DLL called by an action statment in Test Stand 3.5 during run time?

[CharlieRodway]

Hi GoSlow,

I think this can be done through the TS API's.

1). Create an ActiveX step to read the object reference of the module you wish to dynamically change.  

Automation Server: "NI TestStand API",

Object Reference: "RunState.Sequence.Main["DLLStepYouWishToChange"]"

Object Class: Step

Get Property: Module

Return Value: Locals.ModuleRef

2). Create an ActiveX step to set the module path.

Automation Server: "NI TestStand Adapter API",

Object Reference: Locals.ModuleRef

Object Class: CommonCModule

Set Property: ModulePath

newValue: "C:\\YourNewPath\\YourNewDll.dll"

Hopefully this will start you off!

[Lars_L]

Hey goslow,
I actually have an example program that I made for another customer that does this as well as lets you change the function that you reference. Take a look at it and let me know if you have any questions!

Lars

[VisualMath]

Hi Lars,

I was using nearly the same method as you (I was just toggling between two DLLS).  What I see when I run my code is that TestStand indicated that it is running DLL1, but it is actually running DLL2. 

 

When I try to run your DLLs, I get "-17004; Could not load DLL or library."  This is DLL not loadable.

Maybe you sent the wrong DLLs.

[CharlieRodway]

Hi goSlow,

Lars' example appears to work for me.

[Lars_L]

Hey goslow,
I also verified that the example I posted works on my computer. Try redownloading it and give it another try. Also, here is a DevZone document that lists some of the causes of that error: http://zone.ni.com/devzone/cda/tut/p/id/3351

Regards,
Lars

[VisualMath]

Hi Lars,

Still no luck.  This can' t be that hard.  I am not sure what I am doing wrong.  Thanks for checking the Dlls.  What did you use to develop the DLL?  Maybe I am missing some supporting DLLs.

Jeff

[VisualMath]

Hi Lars,

I finally got my version to work.  The key was that the dll had to be unloaded after the step executed.  Thanks for everyone's help.