NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Teststand generates error ' labview has encountered a problem and needs to close'

Hi,

I am using Teststand 3.1 and Labview 7.1.
My problem is that I have a 1D array of 6 elements in Labview that I need to receive from Teststand.
If the array size is set to variable in Labview there is no problem but if I set it to what I require ( fixed 6 ) then when I specify module in Teststand an error message appears , ' LAbview.exe has encountered a problem and needs to close '. Then I get an 18001 about ActiveX as labview has closed.
Why does this happen ?, is it a bug ?

0 Kudos
Message 1 of 7
(3,607 Views)
Hi Mike,

I hope you are doing well today! The following KB article should help you out:
How can I fix -18001 errors when using TestStand and LabVIEW?

If it still doesn't help, then upgrade would be the best option.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 2 of 7
(3,577 Views)
Hi ,

Thanks for the reply !

The 18001 error comes up after labview closes so I think thats ok.

My problem seems to lie in the way that I set up an array in Labview as of a fixed size ( 1 dimension size 6 elements )
When Teststand tries to open that vi Labview crashes and quits.
If the array is set to variable then there is no problem.

I hope its not an upgrade problem as my PC can barely take Labview 7.1 and Teststand 3.1 together at the moment !
0 Kudos
Message 3 of 7
(3,575 Views)
Is it possible for you to post a simple VI and sequence file which replicate the behavior?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 4 of 7
(3,568 Views)
No bother its attached !

The vi writes to a global variable.

The 'Bytes To Send ' 1D array seems to be the trouble, If its set to fixed 6 in LV then Labview crashes from Teststand when I specify module.
If its set to variable its ok.

0 Kudos
Message 5 of 7
(3,568 Views)
I was able to verify this error for LabVIEW 7.1 and TestStand 3.1. I tried it with LabVIEW 8.0 and TestStand 3.5 but don't get the error. I think the workaround which you described would work best. Otherwise, you will need to upgrade.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 6 of 7
(3,562 Views)
Thanks !, at least I know its not my setup. I have LV 8 lying around somewhere so I might upgrade.

Thanks again !
0 Kudos
Message 7 of 7
(3,558 Views)