2013/14 cRIO Imaging

[wywyit]

I'm working on getting our robots from the 2013 and 2014 years driving so that they can be in an upcoming parade with our 2015 and 2016 robots.

I have absolutely no idea what is on them code-wise (we use LabVIEW) and am trying to reimage them using the 2014 cRIO Imaging Tool, however I can't connect to either cRIO at all. No firewall enabled, all network adapters besides Ethernet disabled, and network settings set as:

IP: 10.31.2.5
Subnet: 255.255.255.0
Gateway and DNS are blank.

I can ping both cRIOs, but I can't get the imaging tool to detect them on a Lenovo laptop and a Dell laptop (both with Windows 10). Also, I can get a very old (from our first year, 7 years ago) 2GoPC with Windows 7 and the same settings to recognize the cRIOs, but can't image them because it says that there are no images available. Moving a 2014 image into the folder it specifies doesn't work, it still says nothing is available.

Any help? Thanks so much!!!

[wywyit]

Well, to make it short: I figured it out. It was incredibly obvious and only took half the day!

The 2014 cRIO Imaging Tool does not work with Windows 10. Got Windows 7 in a virtual machine on my laptop to connect to the cRIO perfectly and both robots are imaged and ready for code. Used LabVIEW 2014.

Now to see how deploying goes...

[Hitchhiker 42]

Always good to know. Thanks!