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]

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.

[apalrd]

Do you have any other ethernet adapters enabled? We saw weird issues in the beta test (although only with the new cRio) if any other ethernet adapters were even enabled (let alone connected).

What image version does the imaging tool show? V43? What version is the imaging tool?

I honestly don't know how the imaging tool will handle several versions of the imaging tool at the same time. We were told to uninstall everything old and re-install everything again, I would recommend that next.

[UriF]

[+] I have disabled all other adapters as i have had problems with it before.
[+] the Imaging tool attempts to flash the v43 image.
[+] the cRIO currently has the v20 image.

And if i want to uninstall the old Imaging Tool to try and solve this, how would i go about that?

[RufflesRidge]

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]

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

[ayeckley]

On a related note, I saw the behaviour described by the OP when trying to use the 2012 reimaging tool under Windows XP Pro (did not recognize the cRIO, but the older update tool did). I did not encounter any documentation for this application that stated what OS was required, so I wasn't really suprised that it didn't work under XP. Using a different laptop with a Windows 7 OS the same 2012 reimaging tool was able to recognize the cRIO.

It's entirely possible that there was something else going on (non-obvious adapter differences between the two laptops, etc.). Has anyone been able to get it to work under Windows XP? Or found any documentation stating that it shouldn't/won't?

[UriF]

On a related note, I saw the behaviour described by the OP when trying to use the 2012 reimaging tool under Windows XP Pro (did not recognize the cRIO, but the older update tool did). I did not encounter any documentation for this application that stated what OS was required, so I wasn't really suprised that it didn't work under XP. Using a different laptop with a Windows 7 OS the same 2012 reimaging tool was able to recognize the cRIO.

It's entirely possible that there was something else going on (non-obvious adapter differences between the two laptops, etc.). Has anyone been able to get it to work under Windows XP? Or found any documentation stating that it shouldn't/won't?

I myself got it to work under Win XP. i described above what i have done.

[TimSchley]

I have also been having some issue re-imaging the cRIO to v43. I am using the old cRIO and a Windows 7 OS. My NI LabView is installed along with the newest java, which we are programming in. We are using a non-classmate driver station to try to update. The IPv4 is configured like this:

IP address: 10.9.97.6
Subnet Mask 255.255.255.0
Default Gateway 10.9.97.6

I have the computer plugged into the first link port on the cRIO. The power is on. Everything electrical is setup correctly. When trying to run the 2012 Re-Imaging Tool, I get the error message that says "No CompactRIO devices were found. Verify the network connection"

Any help would be most appreciated!

[JewishDan18]

I had some issues updating today, and the issue was having more than one network adapter enabled. Even though I was not connected to any wireless network, I consistantly got a timeout error while formatting. Turning off the wifi card fixed this. I hope this helps someone out there

[UriF]

If this has any value, I solved my problem by installing FRC Tools from the NI USB..

[jhersh]

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]

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]

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

[Blake L]

I could not FTP into the cRIO, but after doing a Safe Mode reformatting, it imaged properly.

Thank you so much for the help and the quick responses!

[CJay]

Our team is having trouble finding the v43 Image, if any of you could show me where to find it, that would be great!

[RufflesRidge]

Our team is having trouble finding the v43 Image, if any of you could show me where to find it, that would be great!

You need to install the update for the language you are using (C++, Java or LabVIEW)

[CJay]

You need to install the update for the language you are using (C++, Java or LabVIEW)

Thanks! this helped a lot, we got it working.

[mgurgol]

I am getting this error when I try to format. Has anyone seen it before?

Unable to complete operation because of unexpected error:
Error 1 occurred at TCP Read in NI_InternetTK_Common_VIs.lvlib:TCP Read xTP Reply.vi:14->NI_InternetTK_FTP_VIs.lvlib:FTP Get Command Reply.vi:13->NI_InternetTK_FTP_VIs.lvlib:FTP Open Session.vi->ConfigUtility.lvlib:2012_FTPOpen.vi->ConfigUtility.lvlib:2012_FTPFolder.vi->ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlib:Dialog.vi

Possible reason(s):

LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.

[Mark McLeod]

I am getting this error when I try to format. Has anyone seen it before?

Yes, I was able to make it do that.
I did a Safe Mode reformatting, followed by a regular reimaging to get rid of it.

[Programs-R-us]

I am having the same issue... I can not get the 2012 imaging tool to contact the cRIO in any way at all... I have tried resetting, formatting, everything.. I don't know if I'm doing it right, is there any way someone can explain how to do it in a noob perspective?

[Programs-R-us]

I was able to ftp into the cRIO, and it appears to be running
[IMAGE]
Name=FRC_2011_v28.zip;
Date=02/11/2011;
FRCProtocolVersion=1337;
FPGAVersion=1.5.3
InvariantFPGAVersion=1.0.0
FRC_NetworkCommunication_Version=2258
FRC_BlackJagBridgePlugin_Version=65
FRC_2CANPlugIn_Version=66
[CONFIGURATION]
Language=LabVIEW;

[Zuelu562]

Right now, our cRIO is not communicating with DS at all, although we can ping it.

Driver Station Version: 11.30.11
Language: C++
Problem:When attempting to image the cRIO with image v43, it will fail the first time (I will have access to the robot again Wednesday night, getting the same error as a couple people earlier in the thread) and the second time it will succeed, but we still can't get comms with the cRIO via the DS.

Attempted: Safe Mode Formatting, multiple attempts. Same end result.

Edit: Mark, I will attempt to use knowledge from post #19 in the thread. Thank you very much.

[KenBudnik]

Has anyone seen this re-imaging error message?
---------------------------------

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

Possible reason(s):

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


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

---------------------
The imaging tool version is 2011.11.18
The image is FRC_2012_v43.zip

When opening the re-imaging tool for the first time, it correctly identified the cRIO and its' current configuration... so appears to work somewhat and there doesn't seem to be an IP communication issue.

When attempting to re-image normally, the progress box indicates it has made connection, checked the dip switch settings, and was reformating. Then the error.

Tried to reformat in safe mode. Correctly indicated that a reformat was necessary. Ended up waiting 15-20 minutes because the display wasn't giving any progress information. Then went back and tried in normal mode and the same error message just keeps coming up no matter what I try.

Not sure what to try next. Frustrating.

[Aren Siekmeier]

Right now, our cRIO is not communicating with DS at all, although we can ping it.

Driver Station Version: 11.30.11
Language: C++
Problem:When attempting to image the cRIO with image v43, it will fail the first time (I will have access to the robot again Wednesday night, getting the same error as a couple people earlier in the thread) and the second time it will succeed, but we still can't get comms with the cRIO via the DS.

Attempted: Safe Mode Formatting, multiple attempts. Same end result.

Edit: Mark, I will attempt to use knowledge from post #19 in the thread. Thank you very much.

We have this same issue. We can ping the cRIO, but the "Communications" light on the Driver Station is not lit. We can also deploy code from LabVIEW, but we still can not enable because the Driver Station will not recognize the cRIO. The RSL is flashing quick blink with long wait, indicating no comm as expected.

We have tried Safe Mode formatting, repeating reimaging, updating the driver station and utilities, running both wirelessly and tethered, and everything else we can think of. Any ideas?

[Zuelu562]

Any ideas?

Read Mark McLeod's post #19 (http://www.chiefdelphi.com/forums/showpost.php?p=1101958&postcount=19). Some things to try. Post what happens if you try them.

[Mark McLeod]

Not sure what to try next. Frustrating.

That sounds like when comm gets dropped at the point of the changing of the cRIO IP address.
Disable ALL unused PC network connections, leaving only the Ethernet port active.
Set the Ethernet port to your 10.xx.yy.5
Connect the PC Ethernet port to the robot bridge (or any network switch really)
Connect the cRIO to the network switch as well
Attempt to Image the cRIOP.S. If you have network connection issues, some general recommendations:

Turn off PC firewall
Turn off anti-virus
Turn off all network ports, except for the one you're using for the cRIO
Check IP addresses all along the line
Look to see what all the cRIO status lights are doing, particularly Status, Power, & FPGA
Look at the Ethernet connection status lights all along the line: PC port, switch ports, cRIO port

[279 EMPIE]

Where is the imaging tool located?

Was it supposed to download with the USB or is it on wind river?

[Aren Siekmeier]

Read Mark McLeod's post #19 (http://www.chiefdelphi.com/forums/showpost.php?p=1101958&postcount=19). Some things to try. Post what happens if you try them.

Yeah sorry, forgot to mention that we tried exactly that. No changes. We are suspecting (based on some tips from a friend) perhaps a Windows firewall issue, and will check that out tomorrow.

[mgurgol]

Booting in Safe Mode solved the issue, thank you!

[Mark McLeod]

Where is the imaging tool located?

Was it supposed to download with the USB or is it on wind river?

In the Utilities Update: http://joule.ni.com/nidu/cds/view/p/id/2262

Check the bottom of the KOP Website (http://www.usfirst.org/roboticsprograms/frc/2012-kit-of-parts-control-system) to see if you missed other necessary Updates.

[jwakeman]

Has anyone seen this re-imaging error message?
---------------------------------

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

Possible reason(s):

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


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

---------------------
The imaging tool version is 2011.11.18
The image is FRC_2012_v43.zip

When opening the re-imaging tool for the first time, it correctly identified the cRIO and its' current configuration... so appears to work somewhat and there doesn't seem to be an IP communication issue.

When attempting to re-image normally, the progress box indicates it has made connection, checked the dip switch settings, and was reformating. Then the error.

Tried to reformat in safe mode. Correctly indicated that a reformat was necessary. Ended up waiting 15-20 minutes because the display wasn't giving any progress information. Then went back and tried in normal mode and the same error message just keeps coming up no matter what I try.

Not sure what to try next. Frustrating.



I want to second this post. This is EXACTLY what I saw today when trying to update 8 slot cRIO from 2011 with the v43 image. The only difference being I also got this error when trying the safemode imaging. I did try disabling the wireless radio on my laptop as some have suggested. I was able to recover the cRIO by using the 2011 imaging tool and v28 of the firmware. A couple of times I bricked it with the 2012 imaging tool and v43 and recovered with 2011 tool and v28. One other possible clue is that when the 2012 image fails I get the following sequence on cRIO status light. amber blink blink, 1 second pause, amber blink blink, etc. I am confident I installed all the labview software on my laptop correctly. USB stick, the three updates (lv, then utilities, then ds), then windriver. I tried many many times, safemode, rebooting everything...at this point i am pretty sure its not going to work.

[Mark McLeod]

Have you tried imaging from a different PC?

[jwakeman]

That's where i left off today, installing all the labview stuff on another pc. I will try it tomorrow night.

[Alan Anderson]

We can ping the cRIO, but the "Communications" light on the Driver Station is not lit. We can also deploy code from LabVIEW, but we still can not enable because the Driver Station will not recognize the cRIO... Any ideas?

What computer are you using as the Driver Station? If it's the Classmate, have you reimaged it from the 2012 USB flash drive?

There was an issue a year ago with network settings sometimes getting duplicated by the Driver Station software and causing communication to get confused. If you're using a computer that still has its files from back then, it might be worth checking deeply into the "Advanced" network settings of the interfaces and making sure there aren't any extraneous IP addresses defined.

[Alan Anderson]

I did try disabling the wireless radio on my laptop as some have suggested.

When you say "disabling the wireless radio", what did you actually do? Just turning off the WiFi doesn't help. The way I suggest is to right-click on the relevant icon on the Network Connection control panel and select Disable from the popup menu.

[Aren Siekmeier]

What computer are you using as the Driver Station? If it's the Classmate, have you reimaged it from the 2012 USB flash drive?

There was an issue a year ago with network settings sometimes getting duplicated by the Driver Station software and causing communication to get confused. If you're using a computer that still has its files from back then, it might be worth checking deeply into the "Advanced" network settings of the interfaces and making sure there aren't any extraneous IP addresses defined.

This issue was fixed by using a different laptop today, so it seems apparent that it was a firewall issue (even though we had checked some of the telltale signs of such a problem). The first computer was not the classmate, it was a computer with a 3 or 4 day old windows install (probably why the firewall hadn't already been configured appropriately for the driver station).

We later were trying to reimage our second cRio and got exactly the error in post 29 (http://www.chiefdelphi.com/forums/showpost.php?p=1105670&postcount=29), but after an hour so of monkeying with things (through switch, not through switch, safe mode imaging, disabled nics, etc.) it finally worked, so we're not sure what happened there. Sounds like NI is working on this one (see also http://forums.usfirst.org/showthread.php?t=18509).

[279 EMPIE]

We have the image tool now but we do not have the right image.

Where do i get the right image from?

[Mark McLeod]

The image comes when you install the language specific Update from the bottom of this page:
http://www.usfirst.org/roboticsprograms/frc/2012-kit-of-parts-control-system

[jwakeman]

That's where i left off today, installing all the labview stuff on another pc. I will try it tomorrow night.

I used another PC and everything went through fine. It probably was firewall settings on the first PC.

[Paul Manns]

We wound up with an "unknown" image after trying to upgrade from the Beta image to v43. It kept claiming that the boot timed out.

We resolved the imaging problen by turning on the safe mode switch (8 slot version) and reimaging. The dialog box said in effect that the safe mode switch is on and to recover from a corrupted image, select the "FORMAT" button in the dialog box. After formatting, the dialog box said to turn off the safe mode switch and reformat. We reformatted to v43 and it unbricked!

[279 EMPIE]

My teams cRIO is now re imaged and it successfully worked the first time.

[AlDee]

We're having a similar problem only a slightly different error message. After formatting, neither tool can see the cRIO. We've tried safe mode, reformatting, etc. but nothing. We've duplicated the error on a second cRIO. I'm going to try some of the suggestions here, like switching laptops, going through the bridge, etc. Any other suggestions would be greatly appreciated.

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

Possible reason(s):

NI System Configuration: (Hex 0x80040491) System failed to reboot after hard drive format.


Complete call chain:
nisyscfg.lvlib:Restart.vi:1
ConfigUtility.lvlib:2012_FormatSystem.vi
ConfigUtility.lvlib:ReImageTarget.vi
ConfigUtility.lvlibialog.vi

[Mark McLeod]

That message looks like a network switch intermediary is needed between your PC and the cRIO.

[billbo911]

We solved our issue with imaging the cRio II by simple installing the FRC "Tools" from the thumbdrive, something we had neglected to do because they were listed in the full install.

So, here is what we needed to get 'er done:

Fresh install of the 2012 FRC LabView from the thumb-drive,
FRC utilities from the NI website,
LabView update 4.00 from the NI website,
FRC tools from the thumb-drive.

After that, it was smooth as butta.

[JacobGH]

I'm getting the Error -2147220304 error too. Can someone explain how to flip the cRio into safe mode so I can try imaging it that way?

[PhilBot]

Hi

UPDATE....

This is the resolution to the problem I listed below.
It turns out that on my Win XP machine, there are two levels of Wireless Network Control.
I had been using the Intel Proset Wirless application that is connected to the Wireless status icon on the Status Bar.
This showed the Wireless as OFF, with an "Enable" button.

However, when I went to the Network Connections function of the control panel, the Wireless status showed up as "Enabled".. Hmm not nice.

So when I set the Wireless status to Disabled there, the problem was resolved.

So, the moral of the story is: Don't trust third part network tools to actually disable the Wireless interface. Make sure it's disabled at the Windows lowest level.

Hope this helps anyone using an older Win XP machine.

Phil.

----------------------


I'm having trouble formatting a brand new 4-slot CRIO.
I'm a seasoned beta tester so I expected this to go easier.
The error below shows what's happening.
The CRIO Has the correct IP, and so does my Laptop.
The wireless is turned off.
Firewall is off.
Router in between.
OS is Windows XP (oh oh!!)
The formatting process seems to be progressing but it does not complete.
I see the messages get all the way to "formatting....".
During the process I see the CRIO Network drop out twice. once at the beginning, and once a few seconds before the error occurs. It really does look like it's trying to reboot the crio.

Can I toggle the dip switches before it's formatted, to try a safe format?

The real question is how can it get so far along and then just tank... over and over again?

The MUST be a proven solution to this...
Many reboots later.

Phil.

-----------------------------------------------

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

Possible reason(s):

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


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

[JacobGH]

I used the Fn-F2 on my laptop to physically cut power to the wireless card and I'm still getting the same error. Windows XP. No third party wireless software. Ideas, anyone?

[Mark McLeod]

I used the Fn-F2 on my laptop to physically cut power to the wireless card and I'm still getting the same error. Windows XP. No third party wireless software. Ideas, anyone?
Do what Phil suggested in the post before yours.
Using Fn doesn't do what's necessary.

[AlDee]

UPDATE. We got ours working by trying a different laptop. As others have suggested here, it looks like the the first laptop we used was losing connectivity with the cRIO during the formating process. The cRIO was working fine, the laptop could just no longer see it.

If your still having issues, try the suggestions posted in this thread:
Make sure Firewalls are off.
Wireless is off.
Only one ethernet adapter is enabled.
Check IP settings.

--Al

[JacobGH]

Well that royally sucked, but I finally got it working. I used PhilBot's suggestion about disabling the network at the Control Panel Level, but even that wasn't enough. Here's what I did in Windows XP.

1. (PhilBot's instructions) Control Panel -> Network Connections. Right-click "Wireless Network Connection" and select disable. My machine also lists "1394 Connection" so I disabled that too (might be necessary, but don't know).
2. Physically disabled the wireless card. On my Dell Laptop that was accomplished with Fn-F2.
3. Run the cRio imaging tool.

Initially, I didn't do step 2 and it failed with the same error as before. I suspect that steps 1 & 2 must be done in order though I haven't tested it.

This whole setup process has been excruciatingly painful, even beyond the cRio imaging tasks, and as a professional software engineer FIRST will be hearing from me later about good software development and management practices.

[techdude]

If this has any value, I solved my problem by installing FRC Tools from the NI USB..
Correct. Installing only the Updates without first installing the tools from the lab view flash drive does not install NI-RIO which is needed to flash the cRIO

[ebarker]

If you install this update from National Instruments it will fix the cRio imaging problem.

For download and details, please visit http://joule.ni.com/nidu/cds/view/p/id/2262

[ayeckley]

This whole setup process has been excruciatingly painful, even beyond the cRio imaging tasks, and as a professional software engineer FIRST will be hearing from me later about good software development and management practices.

I remember lots of claims back in 2009 (when the new control system first came out) that we'd never have these sort of problems because [paraphrasing several folks at once] "everything is based on TCP/IP, which any child can use". Sigh.

[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 (http://firstforge.wpi.edu/sf/frs/do/listReleases/projects.wpilib/frs.2012_java_update_for_frc).

[Capakowski]

It doesn't sound like your Java installation has been updated to the 2012 version (http://firstforge.wpi.edu/sf/frs/do/listReleases/projects.wpilib/frs.2012_java_update_for_frc).

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

[moc601]

I've encountered the same problem with the 2012 imaging tool not finding my 2011 cRIO immediately after the update to V43 by the same imaging tool. I can run projects and didn't change the network, but did have to move the modules to new slots in the cRIO. I can ping from the .6 driver station to the .2 target, but the imaging tool can't seem to find it. This looks like an imaging tool bug to me.