LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Fatal Internal Error : "ctrlop.cpp", line 1860

This error is linked to the Type Def Controls.   With little luck you can get around this error by removing the type def controls to get the vi causing the error open.  After it is open the controls can be replaced with the original controls and saved. 
 
Any idea why this error happens to begin with?
0 Kudos
Message 1 of 6
(3,413 Views)

Could you post some steps to reproduce this? Maybe attach a VI.

Charlie M. CLD
0 Kudos
Message 2 of 6
(3,392 Views)
When you restart LabVIEW, you should see an "investigate error" dialog.  If you choose "investigate now" you can get a log file and send it to an NI AE who can file a bug report to us on it, and sometimes offer some recommendations for troubleshooting.


Travis M
LabVIEW R&D
National Instruments
0 Kudos
Message 3 of 6
(3,386 Views)
The same error occured in 8.2.1.
 
Steps to initiate error.
 
1.) Open type defined control cluster
2.) Modifiy control
3.) Apply settings
4.) Close calling vi with out saving
5.) Open calling vi and this error will occur
 
I have code that duplicates this but I am not able to post it here.
0 Kudos
Message 4 of 6
(3,382 Views)

Andy,

I was not able to reproduce this on my machine. However, I do believe that there may be a bug here because I have filed a Corrective Action Request for something very similar. Could you perhaps be more specific on you step to reproduce (hold my hand)? Also, the error log that Travis described helps us too.

For example, I:

1)      Opened a new VI and put a few different things in a cluster control.

2)      Right-clicked on the cluster boarder and went advanced>>customize. Changed type to type def, saved the control and then the VI

3)      Closed out of the main/calling VI

4)      Re-opened the main VI and customized the control by changing the order of the controls. I saved the control but not the VI.

5)      Re-opened the main VI and saw no error.

 

Charlie M. CLD
0 Kudos
Message 5 of 6
(3,369 Views)
I submitted code and detailed steps to reproduce this error via an e-mail bug technical support.
0 Kudos
Message 6 of 6
(3,320 Views)