For the past 2 or 3 days i’ve been trying to get my cRIO to image properly, but it keeps either getting stuck on rebooting compactRIO or it fails saying to check the IP reset switch on the cRIO. I’ve tested it both on the 4 and 8 slot cRIOs and two different computers and i’ve had one of my very experienced mentors go over the wiring and manuals with me and we can’t seem to get it to work. NEED HELP!
Are you imaging over wifi or ethernet? Be sure to use a wired connection because wireless can be disconnected and cause some of the problems you are encountering.
What have you tried? Have you reset the cRIO to factory defaults, i.e. hold the reset switch? Are your DIP switches all turned off? Is your computer using a static IP? It should be set 10.(first 2 digits of team #).(second 2 digits of team #).6 . Are you using the right subnet mask (255.0.0.0)? Have you installed the update to the imaging tool?
I have been using a wired connection to the cRIO and i might have to play around with the IPs more from the looks of it. I’ve tried reseting it and all of the DIP switches are off. I’ve updated my imaging tool many times and reinstalled it a few times. It may be the IPs that have been messing me up though. Have to double check on monday
We had this problem earlier this year and found some threads that led to causes. Can’t recall which one clinched it, but here are some keys.
- You must be wired.
- You must have your wireless adapter disabled.
- Use a hub/switch (like the d-link) between the imaging computer and the cRIO. The reasoning is that it keeps the port open on the imaging side while the cRIO boots. Otherwise they can lose comms across the reboot.
- Follow the IP address and net ask instructions closely.
- Make sure your Ethernet adapter doesn’t have multiple IP addresses configured. Click on the advanced button on the TCP/IP properties dialog to see if this is the case.
We always use a crossover Ethernet cable when imaging. I don’t see it in this year’s documentation, but last year’s documentation (Getting Started with the 2012 FRC Control System) said to use a crossover cable on page 17, step #1 under “Running the cRIO Imaging Tool”.
Generally speaking, any newer computer knows when to crossover and when not to, so that shouldn’t be the problem (but it might!).
We actually got stuck at the rebooting point, and I’d never seen it before. We found a couple things. First, the battery was nearly dead. Next, the cRio wasn’t being powered from the 24V on the power distribution board. Fixing those allowed a reimage (wierd huh?).
Did you update the software that was released 01/11/13? This happened to me and later realized there was an update.
I had issues with it too. For whatever reason, when I tried to image it on my laptop, it wouldn’t find the cRIO. I could ping it and everything but the imaging program wouldn’t find it.
The program worked fine on the white clamshell laptop, so we just imaged it on that one, then did everything else on mine. So i guess just try another laptop
Looking at NI’s documentation for the regular non-FRC version of the cRIO II (cRIO-9075/9076, page 12), it says: “use an Ethernet crossover cable to connect the chassis directly to a computer”. I don’t know if it is the issue that some teams are having, but I thought I would mention it since it was in last year’s documentation.
We were trying something out today and discovered that all of the indicator lights on the cRIO can be on but if the battery doesn’t have enough power, LabVIEW won’t be able to connect to the cRIO to deploy code to it. The cRIO is picky about having enough power. :yikes:
Darius,
I sent you a pm as to what worked for us when we were having the issues you are having. If you haven’t fixed it yet, please reply and I will walk you through the process.
Mr. B.
- Turn on DHCP in your D-Link.
- Set your computers Ethernet to Auto.
- Unplug PC from D-Link.
- Power cycle D-Link/cRio
- Plug computer back into D-Link.
- Run the Imaging tool.
You lose contact with the cRio as it changes IP addresses. But it will request DHCP service which will allow you to keep in contact with it throughout the imaging process. Don’t forget to turn DHCP back off in the D-Link or run the bridge configurater again.
I am haing the same issue, I tried the DHCP with the dLink but it still will not reboot. Any other method that might work?
I just fixed the problem. Try check your computer and ethernet cable. That seemed to be the problem for me. Once i switched cables it worked fine
The weird thing with mine is it is not showing the modules on the crio on the imaging tool either…
I tried the router and three different ethernets
Ours is not showing modules either. It pings, seems to format just fine with the imaging tool. Shows up like all is well in NI Max. I even deployed a simple Lab View robotic program onto it. It returned no errors. When I bring up the drive station however, it does not recognize it. I have tried everything I have read in these threads so far to no avail. Even spent several hours with NI Tech support on the phone. Our 4 slot cRio is brand new. This was my second day spent trying to get the modules to show up. Help!
Ok, we are starting to see the same problems. Never saw this in beta.
Directly connecting to the cRIO was not working. The imaging tool would take an extremely long time to find the cRIO. It was not identifying the modules at all: they remained blank on the cRIO picture on the imaging tool.
Attempted imaging resulted in getting stuck at the Rebooting… point, requiring a trip to the task manager to stop the imaging. After this, when restarting the reimaging tool the image would show as ‘not known’.
We rebooted the robot a number of times, tried with and without the gaming adapter in place, and tried two different computers. Then, suddenly, it ‘just worked’. I can’t point to anything that fixed the problem.
We imaged 2 cRIOs this year. One had last years image, and the other one was blank( FIRST choice). We used a cross-over cable. If I remember correctly, this is important because the cRIO cannot auto-switch. I don’t remember which IP we used, but it was the one assigned by the driver station. The imaging tool found both cRIOs, and we imaged them in less than five minutes. (Not at the same time mind you).
I might never trust a procedure that might brick a device to a wireless connection or a dlink connection, and will always trust my handy crossover cable. If you look up a cross-over cable, you can find out the wire pattern, and label yours so you can easily find it.
Cross-over cables make no sense in this application. :rolleyes:
The laptop you do the imaging from IS auto-sensing and it only takes one.