NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Vi not running when using NI´s SiimpleErrorHandler.vi (TS2010/LV2011) in runtime - Windows 7

Hello,

i have a simple VI in LV2011 that i call as action in Teststand 2010.

In teststand the LAbview-Adapter is set to 2011-runtime.

 

The Vi cannot be executet if i use inside the SimpleErrorHandler.vi which creates this error-cluster for teststand.

When i delete this subvi then it can be executed.

 

Also if i run labvie win development-mode it works.

 

I already recompiled multiple time all labview-things and also complete drive C:

 

When i manually open the SimpleErrorHandler.vi then there is no * in the title which means it should be already compiled as version 2011.

Or are there any write-protected parts somewhere in the NI-directories?

 

Operating System is "Windows 7"

 

Thanks for all ideas.

0 Kudos
Message 1 of 15
(4,098 Views)

you might need this patch

 

http://joule.ni.com/nidu/cds/view/p/id/2102 

 

Regards
Ray Farmer
0 Kudos
Message 2 of 15
(4,095 Views)

Hi,

.

I am running a small example which has a VI with the Simple Error Handler.vi . I am running Teststand 2010 SP1 with LabVIEW 2011 in Window 7 and I am not seeing your error condition.

I have switched to using the LabVIEW RTE 2011 and it runs fine.

 

I have attached my example

 

 

 

Regards
Ray Farmer
Download All
0 Kudos
Message 3 of 15
(4,093 Views)

Hi,

 

This sounds like an issue with the object cache in LabVIEW

 

Let me know if the steps in this article fix the issue!

Al B.
Staff Software Engineer - TestStand
CTA/CLD
Message 4 of 15
(4,092 Views)

@Ray Farmer: The example is mpt running. Exactly the same problem that i have.

"Picture not available"-text and blinking red icon.

Attachached a screenshot.

What search-pathes do you have set in teststand?

 

 

@Ballington: I cleared the cache, the directory is also not write protected.

 

0 Kudos
Message 5 of 15
(4,085 Views)

I tested on another PC with TS 4.2.1.83 / Labview 8.6. There i have also this problem when using runtime.

0 Kudos
Message 6 of 15
(4,085 Views)

That error is because it's looking for the VI in the Examples folder so if you have placed it somewhere else then it will not find it. Just use the browser and relink the VI.

 

 

 

 

Regards
Ray Farmer
0 Kudos
Message 7 of 15
(4,081 Views)

Strange things happen.

If i copy the vi to a new directory like c:\Example and set the path with browse-button then it works.

 

But when i move the file to my project-directory and change the path then its not working.
Also if i set it to "absolute-path" i get the red icon.

 

I have no idea why this happens. It is exactly the same vi which is working in another path.

0 Kudos
Message 8 of 15
(4,078 Views)

Hi,

 

do you have another copy of the SiimpleErrorHandler.vi  somewhere in your project directory?

Regards
Ray Farmer
0 Kudos
Message 9 of 15
(4,075 Views)

No, there no duplicate file.

0 Kudos
Message 10 of 15
(4,073 Views)