LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DWarn 0xC1EAEA9C: Internal error 2 occurred

Highlighted

The top-level VI "rio fusion.vi" was stopped at unknown "" on the block diagram of "NI_AdvSigProcWA.lvlib:WA Inverse 2D Discrete Wavelet Transform.vi".
/builds/labview/2016/source/server/RTEmbEditor.cpp(107) : DWarn 0xC1EAEA9C: Internal error 2 occurred. The top-level VI "rio fusion.vi" was stopped at unknown "" on the block diagram of "NI_AdvSigProcWA.lvlib:WA Inverse 2D Discrete Wavelet Transform.vi".


</DEBUG_OUTPUT>
0xB65E9BC8 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 149BC8
0xB6A799E0 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 5D99E0
0xB6A7A0A8 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 5DA0A8
0xB6722758 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 282758
0xB6962628 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 4C2628
0xB660E25C - /usr/local/natinst/labview/./liblvrt.so.16.0 + 16E25C
0xB6A556C8 - WSendEvent + 204
0xB6A55770 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 5B5770
0xB6A2A234 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 58A234
0xB6A28430 - /usr/local/natinst/labview/./liblvrt.so.16.0 + 588430
0xB6596BE8 - /usr/local/natinst/labview/./liblvrt.so.16.0 + F6BE8
0xB6596E48 - /usr/local/natinst/labview/./liblvrt.so.16.0 + F6E48
0x00008A44 - ./lvrt + A44
0xB6D27D3C - __libc_start_main + 114

 

 

 

Guys, anybody please help me to get rid of this internal error. We have done a myrio project on image processing application. Its very urgent..plz.....

Download All
0 Kudos
Message 1 of 4
(580 Views)
Highlighted

Sorry, I don't have the advanced signal processing toolkit installed. I am curious why you are constantly switching between integer and floating point. Wouldn't it be more reasonable to stick to a single representation?

 

Are you trying to run this on the myrio? How big are the 2D arrays?


LabVIEW Champion. It all comes together in GCentral GCentral
0 Kudos
Message 2 of 4
(552 Views)
Highlighted

Hello, I ran into same problem, got any solution?

 

No obvious memory leak, memory usage around 40 %, BUT I get 50 % CPU usage of the main process (one core to 100 %, other one to almost 0 %) at the moment when the application stops working. It keeps that way for 10 minutes until the watchdog restarts the system. In MAX, Error log shows this error: 

####
#Date: Tue, Feb 11, 2020 01:45:04 PM
#OSName: Linux
#OSVers: 4.14.87-rt49-cg-7.1.0f0-xilinx-zynq-41
#OSBuild: 265815
#AppName: lvrt
#Version: 19.0
#AppKind: AppLib
#AppModDate: 


InitExecSystem() call to GetCurrProcessNumProcessors() reports: 2 processors
InitExecSystem() call to GetNumProcessors()            reports: 2 processors
InitExecSystem()                                      will use: 2 processors
starting LV_ESys1248001a_Thr0 , capacity: 24 at [3664273510.14751005, (13:45:10.147510000 2020:02:11)]
starting LV_ESys2_Thr0 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
starting LV_ESys2_Thr1 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
starting LV_ESys2_Thr2 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
starting LV_ESys2_Thr3 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
starting LV_ESys2_Thr4 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
starting LV_ESys2_Thr5 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
starting LV_ESys2_Thr6 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
starting LV_ESys2_Thr7 , capacity: 24 at [3664273510.85769415, (13:45:10.857694000 2020:02:11)]
Thread consumption suspected: 1 Try starting 4 threads
starting LV_ESys2_Thr8 , capacity: 24 at [3664276882.94652700, (14:41:22.946527000 2020:02:11)]
starting LV_ESys2_Thr9 , capacity: 24 at [3664276882.94652700, (14:41:22.946527000 2020:02:11)]
starting LV_ESys2_Thr10 , capacity: 24 at [3664276882.94652700, (14:41:22.946527000 2020:02:11)]
starting LV_ESys2_Thr11 , capacity: 24 at [3664276882.94652700, (14:41:22.946527000 2020:02:11)]
Thread consumption suspected: 2 Try starting 1 threads
starting LV_ESys2_Thr12 , capacity: 24 at [3664277183.63375711, (14:46:23.633757000 2020:02:11)]

<DEBUG_OUTPUT>
02/11/20 04:40:45.666 PM
DWarn 0xC1EAEA9C: Internal error 2 occurred. The top-level VI "main_RT_general.vi" was stopped at unknown "" on the block diagram of "SDF_Data_Loop.vi".
/builds/labview/2019/source/server/RTEmbEditor.cpp(108) : DWarn 0xC1EAEA9C: Internal error 2 occurred. The top-level VI "main_RT_general.vi" was stopped at unknown "" on the block diagram of "SDF_Data_Loop.vi".


</DEBUG_OUTPUT>
0xB645F990 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 15A990
0xB6924160 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 61F160
0xB692471C - /usr/local/natinst/labview/./liblvrt.so.19.0 + 61F71C
0xB65A8CF8 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 2A3CF8
0xB67F66DC - /usr/local/natinst/labview/./liblvrt.so.19.0 + 4F16DC
0xB6484624 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 17F624
0xB68FFC30 - WSendEvent + 204
0xB68FFCD8 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 5FACD8
0xB68D433C - /usr/local/natinst/labview/./liblvrt.so.19.0 + 5CF33C
0xB68D2538 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 5CD538
0xB6406E78 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 101E78
0xB64070D8 - /usr/local/natinst/labview/./liblvrt.so.19.0 + 1020D8
0x00008AB0 - ./lvrt + AB0
0xB6BFD580 - __libc_start_main + 114

 

0 Kudos
Message 3 of 4
(31 Views)
Highlighted

My problem was a software bug obviously. First, cRIO worked for 1-3 hours and then threw error 2 in LabVIEW Log in NI MAX.

 

The problematic VI is a for loop with parallelism, inside of it was while loop which ran "permanently". In this loop there was a disable structure, and INSIDE THE ENABLED CASE there was one VI (with shared reentrancy). 

 

I focused on the disable structure because its behaviour was suspicious when ran through LabVIEW Project. Parallel for loops are not debuggable by its nature, so when you turn Highlighting Execution on, you cannot see anything happenning in parallel for loop. But, I could see the dataflow in wires and the green arrow on the subVI inside the disable structure, which caught my attention as it should not be possible. I could even place a probe on the wires inside, it should show No Debug Info when inside parallel loop but instead it showed Not Executed. There is some weird interaction between parallel loop and disable structure.

 

Just removing the structure and leaving the code the same as before did it for me.

 

Windows 10, LabVIEW 2019 32-bit, drivers 17.0.0f0.

0 Kudos
Message 4 of 4
(13 Views)