cRIO Imaging Tool trouble

[Brobotics12]

For the past few weeks we have been trying to get our robot from last year to work. The driverstation is giving us a greenlight for everything including robotcode. We think it's a problem with the cRIO.

[ebarker]

Originally Posted by Brobotics12

For the past few weeks we have been trying to get our robot from last year to work. The driverstation is giving us a greenlight for everything including robotcode. We think it's a problem with the cRIO.

not a lot of information in your post to go on here !!

have you upgraded the cRio to version V43 ?

have you upgraded the imaging tool to the latest that came out a week ago ?

have you rearranged your modules to this years arrangements. If you haven't then you will get just what you described.

[Brobotics12]

Okay I think I've managed to upgrade to the latest imaging tool, but I every time I try to re-image it with v43 an error pops up. When we tried it said "Unable to complete operation because of unexpected error:
Error 56 occurred at TCP Open Connection in NI_InternetTK_FTP_VIs.lvlib:FTP Open Data Connection.vi->NI_InternetTK_FTP_VIs.lvlib:FTP Data Send.vi->NI_InternetTK_FTP_VIs.lvlib:FTP [STOR].vi->ConfigUtility.lvlib:2012_FTPSubFolder.vi:1->ConfigUtility.lvlib:2012_FTPFolder.vi->ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlibialog.vi

Possible reason(s):

LabVIEW: The network operation exceeded the user-specified or system time limit."

[Alan Anderson]

Originally Posted by Brobotics12

Okay I think I've managed to upgrade to the latest imaging tool, but I every time I try to re-image it with v43 an error pops up. When we tried it said "Unable to complete operation because of unexpected error:
Error 56 occurred at TCP Open Connection..."

If you search the Chief Delphi forums for that error, you will find many suggestions for how to proceed. The first one is to make sure you don't have a Windows firewall active. The second one is to disable all network interfaces except the one you're actually using to connect to the cRIO. The third one is to connect both the computer and the cRIO to the D-Link router instead of using a cable directly between them, though that usually gives a different error and should have been resolved in the most recent Imaging Tool.