Custom Procedure Steps

[Call_Me_Vinny]

Is it possible to create custom procedure steps? (as in steps to run from VeriStand Procedures)

Thanks!

[Jarrod_S.]

What kind of custom step are you hoping to create? What would this step do?

[PackersFan]

(sorry, mistaken post)

[Call_Me_Vinny]

I was trying to send a text message with a procedure step.  I can easily do this through a LabVIEW VI assuming that my target has an internet connection.

I realize that there are definitely other ways to do this, but I thought a procedure step might be the most flexible and I was curious if this was an option.

[Jarrod_S.]

There are currently no ways to do custom procedure steps like you want. It's a feature we've definitely pondered before. Thanks for sharing what types of functionality you'd want from it.

It sounds like you already know a couple other ways to do it, but using the Easy Custom Device Tool to create a basic custom device that you can trigger with a channel value from a procedure sounds like the easiest way to me.

[Jarrod_S.]

Alternatively, on the host side you can use the .NET API to register for alarm triggers. If your VI gets notified of an alarm, you can then text whatever information you want.

[Call_Me_Vinny]

Thanks Jarrod, that's what I figured.

I had considered writing a custom workspace tool, but not a host side custom device using the .NET API to register for alarms.  Interesting idea.....

[StephenB]

the host code wouldn't be a custom device. Could be a "service". Services are launched whenever the project connects. The service VI would then register for alarm events and react to them as need be. This is actually exactly what the alarm responses section of the project does.

[Call_Me_Vinny]

Stephen, so I've seen the services portion of the project before, but never known what it was for.  Is there some guide for creating services for VeriStand?  (like the Custom Device Developer's guide)

[StephenB]

Unfortunatley there is no comprehensive guide. However, there is an example.

"C:\Program Files (x86)\National Instruments\LabVIEW 2011\examples\NI Veristand\Workspace\Workspace Tool Example.vi"

Tools and services are the same thing, except services are automatically launched.

You will need to build any tool or service into an LLB the same way a custom device is built.