cRIO updating to v43 Image issue

[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]

Originally Posted by 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?

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..

[techdude]

Originally Posted by UriF

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

[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.

[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?