NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I create a custom step that does nothing but make calls to a dll

What I'd like to end up with is a Custom step that
1. Takes several string parameters
2. Makes several calls to functions in a DLL
3. Returns and stores error codes returned from the function

I've been through the KB article "How Do I Make a Custom Step Type". This got me about halfway there; while helpful, it didn't provide a reference for some of the questions I had, specifically:
1. What sort of sequence action type should I start with (to use as a template)?
2. If I start with a "Call Executable", do I need to specify the module when I incorporate the step into the sequence?
3. How does one pass parameters in and out of a custom step type?
4. How does the step type report progress/errors to the report?

Thanks in advance.

Mike
0 Kudos
Message 1 of 3
(2,615 Views)
Hi,
 
To interface to a DLL you will need to use either the DLL Adapter or the CVI Adapter, not the Call Executable adapter.
Have you been through the Using LabWindowsCVI with TestStand manual. This should answer all your questions, all the chapters are relevant.
 
Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 2 of 3
(2,605 Views)
Thanks, Ray.
I've gotten a lot farther. I'll check into using CVI also as a way to get user input; the message popup isn't that great even for a demo.
Mike
0 Kudos
Message 3 of 3
(2,585 Views)