cRIO updating to v43 Image issue

[UriF]

Hey everyone.

I'm just getting ready for the 2012 season and tried to update my cRIO's (old cRio) Image to v43, as Wind River requires it.

Unfortunately, when i attempt at updating it using the Imaging Tool, i get the following error:

Unable to complete operation because of unexpected error 7:
File/Directory Info in ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlib:Dialog.vi<APPEND>
C:\Documents and Settings\Owner\Local Settings\Temp\lvtemporary_515166\CRIO

Updating to an older Image seems to be fine.

In addition, I've tried using the NEW 2012 Imaging Tool, and it doesn't even recognize my cRIO.

Has anyone here encountered this problem? how can i resolve it?
Thanks in advance.

[apalrd]

Due to major changes in the image format to handle multiple types of cRio's, you MUST use the 2012 imaging tool for the 2012 image.

As to it not recognizing the cRio, can you post more information?

[UriF]

Originally Posted by apalrd

Due to major changes in the image format to handle multiple types of cRio's, you MUST use the 2012 imaging tool for the 2012 image.

As to it not recognizing the cRio, can you post more information?

Thank you for your reply.

I believe my cRIO's IP is configured to be 10.22.13.(2?) and my PC is
configured to 10.22.13.6.

As i've said, the old Imaging Tool DOES recognize it. and it can successfully flash older Images.

Please tell me if you need any info that i have not mentioned.

[UriF]

Nevermind! I've managed to get the new Imaging Tool to recognize my cRIO. I've done this by restarting my PC and the cRIO itself.

However, when flashing the new v43 Image using the new Imaging Tool I've ran into the following error:

Unable to complete operation because of unexpected error:
Error 15 occurred at Call Library Function Node in nisyscfg.lvlib:Format.vi:1->ConfigUtility.lvlib:2012_FormatSystem.vi->ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlib:Dialog.vi

Possible reason(s):

LabVIEW:  Resource not found.

Could this have to do with the fact that i haven't installed the things from the NI USB? If so, where could i get the appropriate files? since i don't have the USB currently with me.

[RufflesRidge]

Originally Posted by UriF

Could this have to do with the fact that i haven't installed the things from the NI USB? If so, where could i get the appropriate files? since i don't have the USB currently with me.

Yes.

The 2012 Imaging tool will require the FRC Tools install from the NI USB to function properly.

[DjMaddius]

Myself, Everytime I try to open anything from the labview utilities tab on the FRC 2012 update nothing will open. The only thing that will open is the programmer for the boards. Axis setup wont open, cRio imager wont open. Etc.


Anyone else having this issue?

[RufflesRidge]

Originally Posted by DjMaddius

Myself, Everytime I try to open anything from the labview utilities tab on the FRC 2012 update nothing will open. The only thing that will open is the programmer for the boards. Axis setup wont open, cRio imager wont open. Etc.


Anyone else having this issue?

Have you installed the Utilities Update?
http://joule.ni.com/nidu/cds/view/p/id/2262

[jhersh]

Originally Posted by DjMaddius

Myself, Everytime I try to open anything from the labview utilities tab on the FRC 2012 update nothing will open. The only thing that will open is the programmer for the boards. Axis setup wont open, cRio imager wont open. Etc.


Anyone else having this issue?

This is caused by having not installed the utilities update. Sounds like you only have the driver station update.

[DjMaddius]

Originally Posted by jhersh

This is caused by having not installed the utilities update. Sounds like you only have the driver station update.

Ah, alrighty, Ill look for the update I missed later today then. Thanks!

[Blake L]

When trying to put the new image on the cRIO, I keep getting this error message:

"Unable to complete operation because of unexpected error:
Error -2147220308 occurred at nisyscfg.lvlib:Format.vi:1

Possible reason(s):

NI System Configuration: (Hex 0x800404AC) Could not contact remote target. Ensure that the system is online.


Complete call chain:
nisyscfg.lvlib:Format.vi:1
ConfigUtility.lvlib: 2012_FormatSystem.vi
ConfigUtility.lvlib: ReImageTarget.vi
ConfigUtility.lvlib: Dialog.vi"

I uninstalled all of my NI software from last year, and installed all of the new software for this year including all three updates in the correct order.

My adapter settings are as follows:
Wireless adapter: disabled
LAN: IPv4: IP Address: 10.20.16.6 Subnet mask: 255.255.255.0

I have the ethernet cable plugged into port 1 on the cRIO.
Safe Mode and the other switches are off.

The 2012 cRIO Imaging Tool is detecting the cRIO's MAC address, IP address (10.20.16.2), and name, but says that the current image is unknown.

What am I missing or doing wrong here?
Any help or advice would be greatly appreciated!

[RufflesRidge]

Originally Posted by Blake L

When trying to put the new image on the cRIO, I keep getting this error message:

Can you FTP into the cRIO? You can test this by typing "ftp://10.20.16.2" into Windows Explorer.

[Mark McLeod]

I encountered that error while imaging an old cRIO?

• Disable (right-click and choose "Disable") all NIC's, but the one Ethernet port you are using for the cRIO
• Use an intermediate switch between the laptop and the cRIO
• You can try a Safe Mode reformatting (Safe Mode dip switch. reset the cRIO, run Imaging tool, turn Safe Mode switch back off, reset cRIO)
• Followed by a regular Imaging

[Capakowski]

I'm having the same problem as the original poster, however, we're using Java and the only image I found was the FRC_2011_v28.zip.

I'm not sure if the problem is with using the 2012 imaging tool, but any help would be much appreciated.

[Mark McLeod]

It doesn't sound like your Java installation has been updated to the 2012 version.

[Capakowski]

Originally Posted by Mark McLeod

It doesn't sound like your Java installation has been updated to the 2012 version.

Problem solved, thank you. I guess I ignored the update because I had already downloaded a similar package.