View Full Version : cRIO not being found by imaging tool
I have been trying for two days to reimage the cRIO and our computor still cant find it.
I am using the correct ip address and subnet mask, I have turned off wireless connections, I am using our newest ethernet cable, I have turned off the firewall, and I have the latest update for all FRC NI programs.
I have tried going through the router and directly to the cRIO (both of which still have the correct ip adress as well, as far as I know, though I have forgotten how to check on the router), neither has worked.
Please provide me with anthing you think I may have done wrong, or direct me to another thread if this has already been covered (I coudnt find one)
2185Bilal
17-01-2014, 16:26
Hey
I was in the same position you were in, heres a checklist that I went through to troubleshoot this problem
1) make sure the cRIO is has full power (including the modules)
2) try restarting your computer ( I realized that after I installed the NI updates and stuff, I didnt do a full reboot, so be sure to do that)
3) replace the battery
4) reinstall the softwares
try these, btw try replacing your cRIO (maybe its damaged)
anyways try these steps, and if the problem doesnt get fixed let me know.
daniel_dsouza
17-01-2014, 16:32
We were having a similar problem. Here what we needed to do to solve it.
make sure you have a static IP. Anything that is not 2, 1, or 5 should work.
try using a crossover cable, if your device does not support auto-switching
make sure that the cRIO is getting the right power from the PD board
make sure that the ethernet cable/crossover cable is not bad
Hugh Meyer
17-01-2014, 16:39
Drew,
It can take a long time.... besides what you have done I would suggest you make certain the wireless is turned off on the laptop. If you are familiar with the IP stack you could try turning off everything except the IP 4 wired port part. We have had the same problem on a few of our computers and we think it is having a hard time deciding which network interface to use. The newer systems like win8 seem to have lots of places network code can look. Another option would be to try a different computer.
One of our systems we let search all night, but it had found the CRIO when we arrived the next morning. We never will really know how long it took.
Be sure the mask on the computer is 255.255.255.0 not 255.0.0.0 which is the standard operating mode for the robot network except for imaging. This is covered in the instructions but is easy to miss.
You also might try just talking to the CRIO with the driver station to confirm you really have a path to the device....that just depends what is on the CRIO now.
-Hugh
ip is 10.3.6.4 on computer, mask is 255.255.255.0
we may try switching cRIOs, but it will have to be done tomorrow because we will be switching frm an 8 slot to a 4slot and the connections are different.
wil alo try redoing updates tonight
Alan Anderson
17-01-2014, 17:35
I am using the correct ip address and subnet mask
Check the advanced settings for the IPV4 properties. Make sure there is only the one address defined. Sometimes an additional address sneaks in to the list (when the D-Link configuration utility runs, for instance).
I have turned off wireless connections
Don't just "turn off" the Wi-Fi radio. Actually disable the wireless network adapter.
Can you ping to the cRIO? Do you have the cRIO II? Is the cRIO properly powered? Are you on the same subnet?
kennethdharmon2
17-01-2014, 21:47
We are having a similar connection problems as well. The FRC 2014 imaging tool can't find the cRIO. It searches, and searches. We tried two different robots, and 3 different laptops with FRC 2014 s/w, all running W7. No luck. When we use a different W7 laptop that still has the FRC 2013 s/w on it, the imaging tool connects and works properly. As far as we can tell the settings for all the laptops were the same, IP addresses, subnet masks, wireless adapter disabled, etc... Any Thoughts
Greg McKaskle
18-01-2014, 05:53
The primary thing to check for is that the firewall is completely off. If you cannot do this or aren't sure, try right clicking and running the imaging tool as administrator.
Determine if you can ping the IP of the cRIO -- if you think it is a known address.
It may be worth imaging it to a 2013 image, and then try imaging with 2014.
Greg McKaskle
We had the same problem when we first tried to connect cRIO to the computer which runs Windows 7. After trying all the possible solutions suggested on forums, it didn't change. However when we tried the same process on a different computer which runs Windows 8, it worked in our first try. We only lost 2 hours by doing this on the first computer and I suggest that you should try the same process on different computers. Maybe it's easier to connect to cRIO on Windows 8. Give it a try...
we have switched to the new cRIO, re-downloaded the updates, we disabled wireless and firewall, and set the router to bridge (which I had previously forgotten to do). Still no luck
NI MAX finds it, but is unable to change anything
kennethdharmon2
19-01-2014, 18:59
Drew G,
We still haven't gotten the FRC 2014 imaging tool to work either, have tried many times, and did about everything everyone suggested. No luck. We've done the re-imaging many times over the last several years and never had as much trouble as we did this year.
We did however find a work around that uses last years imaging tool, the FRC 2013 imaging tool. This worked very reliably and we were able to image 3 robots this way. And then built, downloaded code, ran the bots etc....
The work around that we used is: Use a laptop that still has the FRC 2013 s/w installed on it from last year. Copy the new FRC_2014_v52.zip file over to the laptop and folder location the 2013 imaging tool uses. Run the 2013 imaging tool, select the 2014 image, format the cRIO. This worked with the cRIO, and cRIO II, very reliably.
If you try this let me know how it works for you. What would be nice is if the 2014 imaging tool worked. But it doesn't, at least not now for us, and we have to move on. Getting the correct image on the cRIO is the important thing, not sure the tool matters that much. Good luck.
kennethdharmon2
21-01-2014, 21:50
There are several threads on this topic, but wanted to post here also, in case it might help someone.
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.
Apologies for not responding sooner, but I was sick and unable to come to work sessions for a few days.
I copied the zip file to the designated location (C:\Program files\National Instruments\LabVIEW 2012\Project\CRIO Tool) and tried the 2013 imaging tool. No luck. it said no images could be found.
I then changed the name of the zip file to FRC Images, as I noticed that was where the tool was looking. Still did not work.
Is there anything else I need to do or do a different way to use the new image with the old tool?
gave the zip file its original name and put it into a folder with the name FRC images. that worked.
PROBLEM SOLVED! thank you for your help
I wanted to chime in because we've had some serious problems as well; much worse than 2013.
Like others, our 2013 tools all work fine, but moving to 2014 has been hard.
We mostly get an error from the 2014 tool, after starting the format, that it cannot determine IP settings. Once we're in that mode, that error happens consistently.
Our theory is that the imaging tool has a non zero chance of failing, and once it fails, you're dead in the water. Either an IP reset or the 2013 imaging tools are required to get it back to try again.
We've tried a pretty wide range of actions; we didn't have enough time to really pin it down, but we did get success on a Windows 7 laptop, that had full Labview installed (which we don't need; we use C++), with a fresh battery.
So for others struggling, as superstitious as it is, it's probably worth installing the full Labview DVD and trying again.
I'll try to post again if we pin it down.
Cheers,
Jeremy
There are several threads on this topic, but wanted to post here also, in case it might help someone.
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.
I think we can safely affirm that as well. The other odd thing we found was that if we imaged a CRIO II with the 'console out' switch in the 'green' position, it would fail, but if we flipped it over to grey, the imaging went through. That could just be that it fails 50% of the time, and luck had it go that way.
But our recipe now seems to be: Full Labview, switch off console out, and all is good.
Cheers,
Jeremy
vBulletin® v3.6.4, Copyright ©2000-2017, Jelsoft Enterprises Ltd.