NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Programmaticaly editing the TestStand sequence in LabView

Solved!
Go to solution

I wanted to have an VI that automatically updates VI prototypes in a Test Stand sequence. The program does that, but also gives me some error messages:

 

References to PropertyObjects were not released properly.
Total number of objects: 6010
Number of top-level objects: 35
Note: Some top-level objects may be included if they are referenced by
an incorrectly released top-level object. For example, an unreleased
SequenceContext object references a SequenceFile object.
The following top-level objects were not released:
Type Definitions [35 object(s) not released]
Type Definition #1:
Name: MessagePopup
etc

But I tried my best to delete all the references that I got...

 

snippet TS prototypes.png

 

Did I miss something?

 

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

snippet TS prototypes.png

 

Oh my, is this any better?

0 Kudos
Message 2 of 9
(3,752 Views)
Solution
Accepted by topic author nikodem

You shouldn't need the call to Engine.ShutDown since you're using the Application Manager. ApplicationMgr.Shutdown will release the Engine for you.

 

Hope this helps!

Trent

https://www.linkedin.com/in/trentweaver
0 Kudos
Message 3 of 9
(3,737 Views)

It seems to work better now. I've never thought that too many stops and shutdowns can be a problem ;).

 

But on the other hand I've started seeing errors like:

 

Exception: Access violation (0xC0000005) at EIP=0x00000000309F9CA0

Version: 14.0.1 (64-bit)

 

The error comes from this VI (I guess) - this VI is part of the post-build process after packing an lvlibp; I'm still trying to debug it somehow.

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

The said exception/access violation happens somewhere inside the inner case. where the Modules are loaded or the modules are forced to reload prototypes. Why?

 

Is it a problem with the access to the file from which I want to reload the prototypes (an lvlibp)? It could make sense, as this VI is run from the post build action of the said packed library...

 

snippet TS prototypes 2.png

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

Have you had a look at these?

 

How Can I Update All The VI Calls In A TestStand Sequence?

http://digital.ni.com/public.nsf/allkb/D7CB87B8EE52E7978625758400762D2D

 

Reload Module Prototypes Programmatically with a TestStand Sequence

http://www.ni.com/example/30267/en/


CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 6 of 9
(3,681 Views)

@.aCe. wrote:

Have you had a look at these?

 

How Can I Update All The VI Calls In A TestStand Sequence?

http://digital.ni.com/public.nsf/allkb/D7CB87B8EE52E7978625758400762D2D

 

Reload Module Prototypes Programmatically with a TestStand Sequence

http://www.ni.com/example/30267/en/


 

Yes, and this is not what I was searching for. 

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

@nikodem wrote:

@.aCe. wrote:

Have you had a look at these?

 

How Can I Update All The VI Calls In A TestStand Sequence?

http://digital.ni.com/public.nsf/allkb/D7CB87B8EE52E7978625758400762D2D

 

Reload Module Prototypes Programmatically with a TestStand Sequence

http://www.ni.com/example/30267/en/


 

Yes, and this is not what I was searching for. 


I get that, the example sequence is doing exactly what you are doing but in teststand. The example uses flags for open sequence, module.load etc evaluate if they are relevant to you.


CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 8 of 9
(3,667 Views)

Actually I just did that, and managed to get it to work (generally) using TS.methods, but I ran into issues with some Access Violations, as stated above. More details about this problem is to be found here - http://forums.ni.com/t5/LabVIEW/Exception-Access-violation-0xC0000005-at-EIP-0x00000000309F9CA0/td-p... Robot Happy

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