"Run as Startup" doesn't work in CRIO9082 with FPGA and RT

[juanmanuelveng]

Hi, i am working with a LabView 2017 and CRIO9082 with 2 modules 9208 and 9425. Also I use the 2 port Rs232 and RS485. Working with the IDE of LabView, all run perfect. And Works OK. Now my problem it is that I set to run at startup the the application and when CRIO start nothing happen.

I attach the main VI of RT CRIO. You could see that there is a Led toggle of 1sec, before anything start. Application never reach that point.

Also there is a vi that log each step. Never write into the disk.

I try doing a dummy application with the same configuration, that read from FPGA a digital input and send it to RT and HMI with Network Variable, and works fine with Run at startup.

So I read that in max there is and option to see a Error Log. And this option give and error that couldn't establish communication with CRIO. 

I don't know what to do now to find the trouble. One thing that i could try , (but will be very slow) it is erase by turn a VI and try if work in that way.

If there is a way to debug this will be very helpful.   

Thanks,      

[juanmanuelveng]

Well doing the last debug, I found in the error log some bug.

This one appears using a VI from an example that turn on and off the user LED of CRIO. 

####
#Date: Mon, May 13, 2019 3:17:04 PM
#OSName: PharLap ETS 13.1
#OSVers: 13.1
#OSBuild: 257
#AppName: PH_EXEC_SMP
#Version: 17.0 32-bit
#AppKind: AppLib
#AppModDate: 
#LabVIEW Base Address: 0x015A90D0

LVRT.DLL load address: 0x0249B000


InitExecSystem() call to GetCurrProcessNumProcessors() reports: 2 processors
InitExecSystem() call to GetNumProcessors()            reports: 2 processors
InitExecSystem()                                      will use: 2 processors
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
starting LabVIEW Execution System 2 Thread 4 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
starting LabVIEW Execution System 2 Thread 5 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
starting LabVIEW Execution System 2 Thread 6 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
starting LabVIEW Execution System 2 Thread 7 , capacity: 24 at [3640612625.46786550, (15:17:05.467865468 2019:05:13)]
VI_BROKEN (0): [VI "NI_Real-Time Target Support.lvlib:RT LEDs.vi" (0x04454110)]
VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_Real-Time Target Support.lvlib:RT LEDs.vi" (0x04454110)]
this->flags=50471424, compilerError=6
VI_BROKEN (0): [VI "NI_Real-Time Target Support.lvlib:RT board LEDs.vi" (0x04f02020)]
VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_Real-Time Target Support.lvlib:RT board LEDs.vi" (0x04f02020)]
this->flags=50471424, compilerError=6

 This one come from a VI that I use to save a log file. This VI comes from an example of Boiler

####
#Date: Mon, May 13, 2019 2:37:24 PM
#OSName: PharLap ETS 13.1
#OSVers: 13.1
#OSBuild: 257
#AppName: PH_EXEC_SMP
#Version: 17.0 32-bit
#AppKind: AppLib
#AppModDate: 
#LabVIEW Base Address: 0x015A90F0

LVRT.DLL load address: 0x0249B000


InitExecSystem() call to GetCurrProcessNumProcessors() reports: 2 processors
InitExecSystem() call to GetNumProcessors()            reports: 2 processors
InitExecSystem()                                      will use: 2 processors
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
starting LabVIEW Execution System 2 Thread 4 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
starting LabVIEW Execution System 2 Thread 5 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
starting LabVIEW Execution System 2 Thread 6 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
starting LabVIEW Execution System 2 Thread 7 , capacity: 24 at [3640610246.09587530, (14:37:26.095875264 2019:05:13)]
VI_BROKEN (0): [VI "NI_FileType.lvlib:LVFileType.ctl" (0x04ff1cd0)]
VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_FileType.lvlib:LVFileType.ctl" (0x04ff1cd0)]
this->flags=34611712, compilerError=6
VI_BROKEN (0): [VI "NI_FileType.lvlib:FT_FileTypes.ctl" (0x050c3f90)]
VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_FileType.lvlib:FT_FileTypes.ctl" (0x050c3f90)]
this->flags=34611712, compilerError=6
VI_BROKEN (0): [VI "NI_FileType.lvlib:Is File an LLB.vi" (0x050c1770)]
VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_FileType.lvlib:Is File an LLB.vi" (0x050c1770)]
this->flags=33563136, compilerError=6
VI_BROKEN (0): [VI "NI_FileType.lvlib:Get File Type.vi" (0x04b230d0)]
VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_FileType.lvlib:Get File Type.vi" (0x04b230d0)]
this->flags=33563136, compilerError=6

For now i will try to take out this VI. To see if there is other error. Because with the bug of file, the C-RIO9082 freeze.

If anyone has a suggestion will be very appreciated.

Thanks  

[juanmanuelveng]

Yesterday at end , I need to eliminate the VI that make a log. Because that one hang the RT. I attached the VI.

I don't understand why this library has problem, also I don't understand why only fail inside the CRIO. Because working from computer all is OK.    

NI_FileType.lvlib

I will made a log with TDMS, this is working with the data.

If someone know a workaround to fix the problem with library, will be nice

Thanks