NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Cluster within a Cluster

Hi,

 

I have a piece of code which uses a cluster along with two string controls in another cluster. But when I pass the variables to LabVIEW from TestStand, it shows error code 17311 (see the attachment). If I remove the outside cluster and configure it, it is working properly. Could anyone please tell me what the problem with the first approach is?

 

I am using TestStand 4.0, LabVIEW 8.5 and SwitchExecutive 2.1.1.

 

Thanks in advance.

Sanad MM

Download All
0 Kudos
Message 1 of 5
(3,542 Views)
Sanad,
 
Your TestStand Container needs to have identical structure as your LabVIEW cluster. This include variable hierarchy as well as names. Therefore, it's best to use the shortcut button (see attached picture) to create the type for you. If you still can't get it to work, can you post a simple vi that has your control and a simple sequence using it.
Regards,

Song Du
Systems Software
National Instruments R&D
0 Kudos
Message 2 of 5
(3,508 Views)

Hi Song,

 

I have created the container using the shortcut button only. I am attaching the dummy codes. I will really appreciate you if I get a solution as soon as possible.

 

Thanks in advance.

Sanad MM

Download All
0 Kudos
Message 3 of 5
(3,490 Views)
Sanad,
 
It looks like your excel file is the culprit here. You probably use the import/export tool to generate this file in the very beginning. The problem is that you included the top container, middle container, and low level components. In certain cases, you would have 3 copies of the same variable, such as AveragingState_F__Off_. It is present in RLInputs, RLInputs.ReturnLossParameters, and RLInputs.ReturnLossParameters.AveragingState_F__Off_. Although it's unlikely you will modify the value for the top level containers in the excel file, it still causes confusion.
 
If you are doing both the import and export programmatically, then you just need to include RLInputs in the excel file. If you want to manually change that file, then I would recommend exclude all the containers. For now, if you just want a quick workaround, you can edit your property loader step so that it's not loading RLInputs.ReturnLossParameters.
Regards,

Song Du
Systems Software
National Instruments R&D
0 Kudos
Message 4 of 5
(3,481 Views)

Thank You Song. It is working now.

 

Sanad MM

0 Kudos
Message 5 of 5
(3,465 Views)