LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

restart.vi error the operation exceeded its time limit

Hello,

 

I am using the Replication and Deployment Utilitiy.

 

Recently I got an error from the utility, when I tried to deploy an image to a cRIO 9023 controller.

I don't know what this error is and how to fix it. I got the open source Labview Code for the RAD Utility aand tried to debug and fix it myself but my LabView skills are quite poor.

But I could find the location of the error.

Can you please help me to fix this problem?

 

Here is my analysis:

 

The VI - The error occurse in the restart.vi (from the ni syscfg)(its in the bottom left area)

Picture RAD_Deploy Image Wrapper VI.png

 

Error Log from the RAD:

Model    cRIO-9023    

Model Code    73D2    

Serial Number   016219C9     

MAC Address    00:80:2F:13:1F:41

IP Address    192.168.130.180    

Host Name    AIS9023    

App Image Name    test    

App Image Version    1.0.2    

Time    0%    

Result     Error -2147220323 at nisyscfg.lvlib:Restart.vi:1680001<APPEND>

(complete call path: nisyscfg.lvlib:Restart.vi:1680001
rad_Deploy Image Wrapper.vi:4490002)

Description of the error code -2147220323 from the Lab View help: The operation exceeded its time limit.

 

TargetSettings In (the variable out of which the session is created for the restart.vi, if I'm not mistaken)

Target Settings in.png

 

Session (the session variable for the restart.vi)

Session Variable.png

 

 

0 Kudos
Message 1 of 6
(4,433 Views)

Hello Simorgh,

 

I too am using the Replication and Deployment Utility, to deploy an image to a sbRIO 9642.

I faced the same issue as you. Not sure if my situation could help you, but still :

My sbRIO had an old image that I wanted to replace. Turns out, just as you said, that the remote reboot VI wasn't working (it's a timeout error, which the VI souldn't return) as intended.

I formated the sbRIO via MAX, then tried to deploy my image again, & it worked.

 

To sum up : try to format your cRIO before applying the image via RAD.

0 Kudos
Message 2 of 6
(4,404 Views)

Hi Plucchini!

 

Thank you for your reply.

 

I made the same observation. This problem only occurs when there is an older image on the RIO. BUT: sometimes it works with the RAD and sometimes it doesn't.

 

I am wondering what an "old image" is. Does the RIO Device (cRIO 9023 in my case) need a specific software to be able to work with a labview program that incorporates the restart.vi from the system configuration?

 

the NI software on the problematic image: (it uses NI System Configuration 5.0.0, while the RAD uses ?14.0.1?)

Software Old Image.PNG

0 Kudos
Message 3 of 6
(4,390 Views)

Arent there any LabView Engineers in this forum?

0 Kudos
Message 4 of 6
(4,349 Views)

What I meant by "older image" was that the softwares installed on my sbRIO were all using a version made for LabVIEW 2011, and it seems that the restart.vi isn't working anymore with this type of configuration. I actually used restart.vi outside of RAD, & had the exact same issue with a sbRIO using software from LabVIEW 2011 (which seems to be your case as well).

 

I'd like to point out that the restart.vi was working fine with the same sbRIO a few months ago, so to me it looks like this behaviour was changed in a recent update.

In a nutshell, the behaviour from the restart.vi function apparently changed, & will no longer work with older NI software, so try to update the NI software on your cRIO.

 

Hope that helps

0 Kudos
Message 5 of 6
(4,341 Views)

I narrowed down the error to the NI System Configuration 5.0. Which is not compatible with NI System Configuration 14.0 or higher.

Eventually NI Support confirmed this.

 

So a reboot into SafeMode is not possible with the restart.vi, except you got one from the older NI System Configuration.

 

A manuel workaround is to set the controller into safemode by yourself and then start the RAD Utility / my custum tool.

 

I would like to set SafeMode with MAX but it doesn't let me. What's that about ?:

 

cannotSetSafeMode.PNG

"Sicheren Modus erzwingen" means Force SafeMode...sorry I got the german version of MAX.

 

0 Kudos
Message 6 of 6
(4,287 Views)