NI TestStand Idea Exchange

I'm working extensively with LabVIEW VIs and Test Stand, and one of the most helpful features existing is the ability to configure a TestStand type to pass its data to and from a LabVIEW Cluster.

I think a great way to expand upon this would be to allow the developer to override specific variables within the LabVIEW cluster.

For instance, say I have defined a TestStand type with 5 total variables, all of which may pass to a LabVIEW cluster. If my LabVIEW cluster has at least the same number and type of variables, then this cluster passing has no issue.

However, if my LabVIEW cluster has 6 variables, then the TestStand type can only account for its defined five variables, and I am effectively locked out from the sixth variable. I cannot edit the sixth variable, nor can I assign it a default value (see Ex1_broken.PNG)

This wouldn't cause an issue if I could override specific variables within the cluster passing. That is to say, if I were given access to that sixth variable from the example, then I could assign it to a local variable. The other five variables would still be satisfied by the TestStand type, and no errors should be generated by the step. (see Ex1_fixed.PNG for what I envision this to look like)

Hi,

I'm using TS2016. I'd like to suggest adding multiline watch view. I put some serial communication data in a variable, and watch it, but I can only see the top line. Of course, I can mouse over it, and see the entire thing, but it would be nice if I could see it automatically.

I am a AE here in the UK. Just had a customer with TestStand.

He was given a project to do in TestStand that was estimated 5 days to develop, but his managers told him to add another 5 days on just for deployment of the system, mainly because they have issues deploying the system.

The problem was including a DLL in the Workspace. Of course this is very easy to do, but they were expecting that it would automatically add the DLL to the workspace when in the sequence they were calling it, given how powerful TestStand is. 

Would it be wise to add this small feature into TestStand to smoothen out the process of deployment for newer customers?

It looks like it's a widerspread issue due to the fact that the manager would recommend 5 days for deployment due to experiences with previous projects. I understand to those who have used TestStand before may think it is not much to just add the DLL into the workspace, however adding an auto include feature would be nice and could even save newer engineers time.

In addition, he suggested including .NET and C++ installers because most of the Engineers he knows use these instead of LabVIEW.

Let me know what you think of this Idea.

Daniel