2014 Imaging Tool Not Working

[sasha831]

Hello,

This year we got a new C-Rio, and wanted to load it up with the Java image. We have already updated all our software with the 2014 v6 update. We've set the network adapter's ip to 10.45.29.5, connected the C-Rio via Ethernet and turned on the imaging tool. Noting happens. It constantly says searching with no changes over the half hour for which we left it running. It can't find the c-rio, but nor does it tell us this like it used too.

We encountered the exact same problem when attempting to connect to our old C-Rio, which we know works.

We've also tried connecting through a working bridge.

Any Help Would be greatly appreciated,

Sasha

[Owen Makin]

Did you changing your computers ipv4 address and allow your computer to connect through the Ethernet port?

[cesaros]

So what you have to do is trying to connect a crossover cable between cRIO and computers network adapter.
Let me know if anything happens.

[Alan Anderson]

Do you have any other network adapters enabled?

Are you running the imaging tool as an administrator?

Does the green "connection" LED on the cRIO's ethernet port light up?

[rkoripalli]

Make sure your firewall is turned off.

[DjScribbles]

One thing to check is your alternate IP address settings; these were a nagging problem last year for me, but the symptoms were different (it would find the cRio and start imaging, but fail after the cRio was rebooted).

Where you configure your IP settings for the ethernet adapter, click the Advanced button, here there may be a 10.0.0.?? IP address, if so, remove it (this address was created by the bridge configuration utility last year, but it doesn't get removed).

Also make sure your subnet is set to 255.255.255.0 for imaging. (It should normally be 255.0.0.0 to work with the competition field though)

[chris.boyle]

A quick way to ensure that your IP address is correct is to open the FRC Driver Station and set your team number in the Setup Tab (also click Choose NIC... OK) prior to starting the cRIO Imaging Tool.

[TEAM1100soft506]

Originally Posted by sasha831

Hello,

This year we got a new C-Rio, and wanted to load it up with the Java image. We have already updated all our software with the 2014 v6 update. We've set the network adapter's ip to 10.45.29.5, connected the C-Rio via Ethernet and turned on the imaging tool. Noting happens. It constantly says searching with no changes over the half hour for which we left it running. It can't find the c-rio, but nor does it tell us this like it used too.

We encountered the exact same problem when attempting to connect to our old C-Rio, which we know works.

We've also tried connecting through a working bridge.

Any Help Would be greatly appreciated,

Sasha

What os are you using? In the past the imaging tool has not worked on windows 8.

[sasha831]

Thank You for all your help.

Actually, It turns out that we had to register our FRC vision assistant for 2014. Don't know how that's related, but it fixed the issue

Sasha

[sergioCorral842]

Originally Posted by TEAM1100soft506

What os are you using? In the past the imaging tool has not worked on windows 8.

Just to clarify, the imaging tool should work on Windows 8, since I configured our team's crio on Windows 8.

[kennethdharmon2]

sasha831,

We've been having imaging issues as well. And are using the FRC 2013 imaging tool in a work around mode. We have never got the FRC 2014 imaging tool to work. We did not get the LV disc in the KOP, and have back ordered it, in the meantime we installed LV in evaluation mode to get going, then NI gave us a serial number. Your comment about activation, makes me wonder if our LV is not fully or completely activated, and that is the root cause of our issue. Anyone else have a similar experience?

[kennethdharmon2]

On a hunch, and now that our team has the serial number. I did a complete uninstall and clean install of LabVIEW. (Our previous install was in Evaluation mode, with a post install activation). With the new install, the FRC 2014 imaging tool works, and the camera configuration tool works as well. So not for sure, but I think that was our problem.