LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error code -17306 while accessing container from TestStand

 

Hi,

 

I am getting an error -17306 while accessing the TestStand container present in Station Globals using invoke node property object. Please find below the code snippet.

 

 

 

 

Code_Snippet.jpg

 

Thanks,

Neha

0 Kudos
Message 1 of 9
(3,439 Views)

Hi

you would probably have more luck in the teststand forum, However why are you not using http://zone.ni.com/reference/en-XX/help/370588D-01/lvteststand/teststand_-_get_property_value/

Function?

You should be able to go Globals.UUT1.Name

 

Nick

 

 

0 Kudos
Message 2 of 9
(3,337 Views)

Hi Nick,

 

Thanks for help. The problem got resolved. But I'll try with the alternate method which you mentioned above.

Just 1 question, how to pass a context to Get Property Value VI when the TestStand is launched from LabVIEW.

 

Regards,

Neha Kulkarni

0 Kudos
Message 3 of 9
(3,332 Views)

It shouldn't matter what launches TestStand.

"ThisContext" (without quotes) is what you need to pass to the VI object reference for the Get Property Value VI

0 Kudos
Message 4 of 9
(3,308 Views)

Hi Nick,

 

Yeah that's true. But my VI is not getting called from TestStand. The VI is stand alone and from that VI TestStand is being launched. So there will be no container pane from where I can map that reference to TestStand sequence. How to pass the sequence context in this case.

 

Regards,

Neha

0 Kudos
Message 5 of 9
(3,304 Views)

Ok so you are in Chicken or Egg situation... sorry can't hlep there. Other than suggesting that the globals are stored in a file somewhere. 

0 Kudos
Message 6 of 9
(3,300 Views)

 

Ok. Thanks 🙂

0 Kudos
Message 7 of 9
(3,294 Views)

Hi

 

I am not sure too, how to obtain sequence context from TS application manager. However, did you try using the lookupstring as "StationGlobals.UUT1.Name" or as "FileGlobals.UUT1.Name"?

 

I think, the reference to globals will include Station Globals and File Globals. so, you might have to be specific in the lookup string.

 

the error says the name of the variable or property is not valid.

 

also, you wired "0" which means do not create the variable if not found. is that what you wanted to configure?

 

Regards
Freelance_LV
TestAutomation Consultant
0 Kudos
Message 8 of 9
(3,288 Views)

Hi,

 

I have done it by the same way using lookup string. And that's working fine now.

I just wanted to find some alternate way if any.

 

Thanks.

0 Kudos
Message 9 of 9
(3,281 Views)