crio 9014 - RT App takes too long to start

[rpereira]

Hi to all,

We are having troubles with an App running in a cRIO 9014 (part number 196267E-02L). It happens that when the cRIO is turned on, the APP doesn't start automatically, and it takes almost 2 hours to start. This is definitely not what we want. 

While the application runs, there is no problem connecting to the cRIO (via FTP, MAX, pings, etc.), but during that 2 hours period mentioned before, images can't be taken (see picture attached)..

This App works perfectly in other cRIO systems (even in cRIO9014). ¿Could this, for example, be caused by a firmware issue?

I would really appreciate any comments or help.

[Texas_Diaz]

In my experience, when this happens there are timeouts being tripped within LabVIEW RT whenever accessing drivers/services that are corrupted.  For example, if the startup app is trying to access an FPGA that has a corrupted bitfile, the startup app is trying to communicate with services whose files have been corrupted, or other corruption on the target has taken place.

What is recommended is to format the drive, reinstall all application dependencies, reinstall all FPGA bitfiles, and deploy your code and try again.  

-Danny

[rpereira]

Thanks Texas_Diaz,

we tried new tests, specifically with the console out. Everything seems fine until an error messagecomes out, as described below (marked in red). Is at this point were the delay starts (1 hour, more precisely).

Regards, Roberto.

cRIO-901x Boot

Copyright 2007 National Instruments Corp.

Bootrom version: 2.4.5
Creation date: Jun 14 2007, 10:04:44

Press any key to stop auto-boot...
0
auto-booting...

boot device : tffs=0,0
unit number : 0
processor number : 0
host name : host
file name : /c/ni-rt/system/vxWorks
flags (f) : 0x8

Attaching to TFFS... Mounting disk-on-chip to /c/
Datalight Reliance v2.10.1053
Copyright (c) 2003-2006 Datalight, Inc.
Registered to #D469CF2F
done.
3909664
Starting at 0x100000...

ATA device not detected.

Adding 8651 symbols for standalone.
Mounting onboard storage...
Reliance File System Driver
Datalight Reliance v3.2.2 Build 1376BV
VxWorks Edition for ppc603
Copyright (c) 2003-2008 Datalight, Inc. All Rights Reserved Worldwide.

-> lvusEngine: PPC603 CPU detected...
CPU tick frequency: 32.999942 MHz [Using: 1000 MHz]
MAX system identification name: cRIO-PAB06
Initializing network...
Device 1 - MAC addr: 00:80:2F:11:19:BB - 172.20.2.74 /23 (primary - static)

Loading LVRT...
* Loading EarlyStartupLibraries: tsengine
Time sync source: rtc now active
* Loading EarlyStartupLibraries: nisvcloc
...nisvcloc failed to initialize.
* Loading EarlyStartupLibraries: mxssvr
* Loading StartupDlls: taggerrt
* Loading StartupDlls: NiRioRpc
* Loading StartupDlls: niserial
* Loading StartupDlls: niorbs
NI-RIO Server 3.2 started successfully.
* Loading StartupDlls: NiViSrvr

NI-VISA Server 4.5 started successfully.

Welcome to LabVIEW Real-Time 8.5.1

[Texas_Diaz]

---

@rpereira wrote:

we tried new tests, specifically with the console out. Everything seems fine until an error messagecomes out, as described below (marked in red). Is at this point were the delay starts (1 hour, more precisely).

* Loading EarlyStartupLibraries: nisvcloc
...nisvcloc failed to initialize.

---

nisvcloc is the NI Service Locator.  It translates NI services so that you can use them by name instead of by port (for TCP primitives, for example).  If there is a failure in the NI Service Locator, it is quite likely that other components that require the NI Service Locator will fail to load (and/or experience significant timeouts). That's what appears is happening here.  

Have you tried formatting the controller and reinstalling software from a clean (known good) host machine?  It's possible the software on the host was corrupted, and so when the files were transferred to the target during install time they were in a corrupted state.  Is that possible?

-Danny

[rpereira]

Thanks Danny,

problem solved after formatting the controller, the application start and runs normally. The only weird thing that is that the nisvcloc error message still appears, but in practice this doesn't create problemas or booting delays.

Greetings, Roberto.

[Texas_Diaz]

Just in the effort to "leave as few stones unturned as possible", the nisvcloc error kept bugging me and I wanted to find out why it was erroring on initialization.  This lead me to this KB:

• http://digital.ni.com/public.nsf/allkb/7D361FB68EC7656A862578A0005D13F1

I'm fairly convinced this is your case from the output you've shown.  If you aren't concerned about the error message, as the KB insists is benign, then I'll let it stand there.  

-Danny

[rpereira]

This controller has LV RT 8.5.1 and NI RIO 3.4.0 on it. Although It doesn't totally match with the description shown in the KB, it could have something to do with it, taking into account that the LVRT used is old.

Greetings, Roberto.