ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView Cluster Passing

Hello,

I am creating a TestStand sequence that is calling a LabView Action Step. In the LabView Action Step I am trying to pass a rather large data cluster from the LabView VI into TestStand. When I try to create a new custom data type from the "Create Custom Data Type From Cluster" window, I get an error message, but the custom data type is created. However when I look at this data type in the LabView ACtion step, I see that not all of the data parameters in the custom data type exist (as they do in the LabView cluster). THis VI also passes a second cluster, which is much smaller then the first, and I can successfully create a TestStand data type and pass the cluster information from the VI to TestStand. I cannot do this with the larger cluster in this same VI.

My question: Is there a limit to the size of a cluster that can be passed/created between a LabView VI and a TestStand data type?

Thank you in advance for your help.

Newbie

P.S. I am using LabView 7.0 and TestStand 3.0 running on Windows 2000.
0 Kudos
Message 1 of 4
(3,868 Views)
You might make sure all your LabVIEW types are boolean, numeric and string only.

FYI there is a bug when passing a LabVIEW cluster that is a LabVIEW typedef to TestStand. If you run into that it is fixed with LV 7.1.

dn
0 Kudos
Message 2 of 4
(3,861 Views)
Can you please post the VI with the cluster? I would like to see the cluster and figure out why TestStand is giving an error when creating the custom data type.

Regards,
Jose
0 Kudos
Message 3 of 4
(3,852 Views)
Dn and Jose,

Thank you for your response. I did figure out the problem thanks to dn's response. IT appears that the LabView VI cluster was using a non-standard naming convention (from a TestStand perspective) for naming some of the data parameters within the cluster. A number of parameters were named with a simple number (i.e. "0", "1", etc.). (Since I did not cerate this VI, I have no idea why the person who created the VI decided to use such a naming convention for some of the data parameters in the cluster.) According to TestStand requirements, a data variable NAME cannot consist of just numberic characters (i.e. "0", "1", ...). Once I changed the name of the data parameters in the VI cluster to a more standard format (i.e. changed "0" to "P0"), I was able to automatically create a container in TestStand that matched the VI cluster.

Thanx,
Jim
0 Kudos
Message 4 of 4
(3,832 Views)