Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   C/C++ (http://www.chiefdelphi.com/forums/forumdisplay.php?f=183)
-   -   cRIO imaging timeout error (http://www.chiefdelphi.com/forums/showthread.php?t=125882)

mr_abomination 05-02-2014 19:00

cRIO imaging timeout error
 
we are trying to image our cRIO using the FRC cRIO imaging tool, but whenever we attempt to do so we run into this error

Code:

Unable to complete operation because of unexpected error:
Error -2147220304 occurred at nisyscfg.lvlib:Restart.vi:1680001

Possible reason(s):

NI System Configuration:  (Hex 0x800404B0) Timeout while waiting for reboot. System is offline.


Complete call chain:
    nisyscfg.lvlib:Restart.vi:1680001
    ConfigUtility.lvlib:ReImageTarget.vi
    ConfigUtility.lvlib:Dialog.vi

any help would be appreciated as we need to put the code onto the robot

Alan Anderson 05-02-2014 21:42

Re: cRIO imaging timeout error
 
What is the IP address of your computer? It should be 10.47.73.xx, where xx is 5 (if you're going to run the Driver Station on that computer) or 6 (if you're just doing development on it) or something greater than 15 (if you have another computer at the .6 address). The subnet mask should be 255.0.0.0 in any case. Check the Advanced settings for IPv4 and make sure that only one IP address is set on the adapter. Delete any extra ones.

You should not be trying to image the cRIO over a wireless connection. You should have only the wired network interface enabled on your computer, with every other interface disabled. The computer's ethernet jack should be wired to one of the D-Link router's connections, and the cRIO should be wired to another connection on the cRIO. You can wire directly from the computer to the cRIO, but some computers take a long time to deal with the cRIO's dropping off the network during part of the reimaging process and that has been known to disrupt communication at a crucial time.

Do you have any antivirus or firewall software running on your computer? They should all be turned off when you're trying to load a cRIO image.

mr_abomination 06-02-2014 18:30

Re: cRIO imaging timeout error
 
Quote:

Originally Posted by Alan Anderson (Post 1338275)
What is the IP address of your computer? It should be 10.47.73.xx, where xx is 5 (if you're going to run the Driver Station on that computer) or 6 (if you're just doing development on it) or something greater than 15 (if you have another computer at the .6 address). The subnet mask should be 255.0.0.0 in any case. Check the Advanced settings for IPv4 and make sure that only one IP address is set on the adapter. Delete any extra ones.

did that, i also mis-typed my team name so the ip should be 10.47.33.6 if we are imaging right? also do we need default gateways and/or DNS servers?

Quote:

Originally Posted by Alan Anderson (Post 1338275)
You should have only the wired network interface enabled on your computer, with every other interface disabled. The computer's ethernet jack should be wired to one of the D-Link router's connections, and the cRIO should be wired to another connection on the cRIO.

can you be more specific, we currently have our laptop with everything but the ethernet disabled, it isnt the laptop we were provided because that one sucks, it a toshiba running windows 8.1 if that makes a difference.

Quote:

Originally Posted by Alan Anderson (Post 1338275)
You can wire directly from the computer to the cRIO, but some computers take a long time to deal with the cRIO's dropping off the network during part of the reimaging process and that has been known to disrupt communication at a crucial time.

we have now hooked it up cRIO --> router --> Laptop via Ethernet

Quote:

Originally Posted by Alan Anderson (Post 1338275)
Do you have any antivirus or firewall software running on your computer? They should all be turned off when you're trying to load a cRIO image.

first thing we did

Alan Anderson 06-02-2014 21:49

Re: cRIO imaging timeout error
 
Are you sure you've turned off the Windows firewall and any antivirus software? The error message you copied here sounds like one that's common when the network connection is being blocked.

mr_abomination 07-02-2014 15:47

Re: cRIO imaging timeout error
 
we fixed it, we were being geniuses and we sending the wrong code. all good now


All times are GMT -5. The time now is 12:49.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi