Turns out we are having a bit of a problem here, maybe someone has run into it and can help us out:
We are not able to image our 8-slot cRIOs. whenever we try we get a “could not connect to ip (10.22.83.2), ensure you have a network adapter in the same subnet…”
I have checked and have the configuration of the laptop all in order, have tried both windows 8 and 7, on 4 different machines, and every time we get the same mistake, the strange part is: all 4 of those machines can image our 4-slot cRIO, just not the 8-slot ones. no matter what i do, i always get the same error, I’ve tried:
setting the Subnet Mask to both: 255.0.0.0 and 255.255.255.0 .
disabling all other network adapters.
disabling the firewall in windows.
using both a cross-over and regular UTP cable.
safe mode restoring the cRIO (i am able to reformat, but when the time comes to load an image, i get the connection error)
do you guys have any idea for why we would be unable to image the 8-slot? when we can do the 4-slot just fine?
Try it with a router (e.g. the D-Link) between the computer and the cRIO.
(The Imaging Utility is supposed to try to ride out the momentary loss of network connection when the cRIO changes its configuration, but maybe the 8-slot version is a little slower?)
I would also like to know if you have changed your computer’s IP address to the specified 10.xx.yy.5 that is required to connect. I know our team did this and ran into a similar problem. And when we looked into it we found that there were two different IP addresses which required us to go into the advanced settings and remove one. We had to command line and ipconfig to locate that problem.
yes i did, although you can have it be either 10.xx.yy.5 (this is the default for the classmate) and 10.xx.yy.6 (this is the one recommended for your development machine), tried both ways, did ipconfig to verify the adapters, and check that everything was in order. It was, and still no luck, also, the last number shouldn’t really matter. or should it? as long as you do not try and use an address already taken up by another device. From what i understand its all about being on the same subnet.
REad something on the cRIO imaging regarding SAFE Mode. Directions say to make sure SAFE Mode is off. How do you know Safe Mode is off. I see the switch on the cRIO panel but which way is off?
Hmmm… no luck with using the bridge as an intermediary, still get the same mistake, I´ve used MAX to check the configuration on the cRIO and it is configured properly as far as the IP address goes, namely the same as my laptop (with the only notable exception being the last block, which is a 2 as should be expected), do you guys know if there is any way to do a manual upload of the image using MAX? its a bit unorthodox, but i really need some way to get this done
Let’s see if we can find out why the Imaging Utility running on your laptop can’t connect to the cRIO.
Copy the results of the ipconfig command here so we can double-check that everything looks proper. There are a couple of “gotchas” that might be giving you problems.
I had similar issues reconfiguring the 8 slot this year. I’ve imaged it before, but this year has given me many issues.
1st point of attack should be seeing if any connection at all exists between the cRIO and the laptop. If you’ve used it before, ping the ip address and see if it responds.
If not, the problem exists either in its ip address or in a physical connection. If it’s ip, try and reset the cRIO and configure it again.
If it does respond to a ping, and since you’ve already tried using the bridge as an intermediary, check the bridge setting. Make sure it’s configured correctly.
Next, if you still have issues, check the laptop’s LAN settings, although I think you’ve already done so.
If it still gives you issues, try just getting the ip address to configure using the imaging tool. There’s an IP RESET switch on the cRIO you will have to turn on.
Check to see if your modules are in the right place. The 8 slot cRIO hates having it’s modules out of order.
Vacuum the cRIO as well. It’s surprising how determined metal shavings are to find their way into it.
And if all else fails, shutdown the whole system, restart everything back to factory settings, and try again. It was probably just a cosmic ray.
I know, I know, but try, I did this for two hours with our home built 100’ competition tether, that has worked just fine for other things without issue, but I switched to another cable and it worked?
I haven’t remembered to bring in my Ethernet tester from home to test the 100’ yet, but it worked perfectly fine for setting up the camera.
I’ve found that the only way I can reliably get the imaging to work is by directly connecting my computer to the cRio, with no switches/routers in between.
Thanks all for helping. Im on the same team as Korakos. Worth noting, as korakos stated, that we have been able to reimage the 4-slot CRIO without any hitch. That should tell us that our base configuration and network settings areat least sound, right? So when we try to reimage any of our two 8-slot spare CRIOS it fails. What could be different between the 4 and 8 slot crios to cause this problem? any ideas?
or perhaps im giving too much thought to the fact that these are different-slotted crios and just happens that the 8 slots are in a particular state that blocks the imaging process and the slot numbers have nothing to do with this?
Here’s how we’ve had the best (only) success. First, no network devices between the cRIO and the computer. We use the pink cross-over network cable that was in the kit of parts a couple years ago (back when the camera was connected to the cRIO second network port). Third, we disable any non-wired network adapter on the computer. Fourth, we set the computer ethernet adapter with a fixed ip address (10.xx.yy.zz) I forget the netmask, but its either 255.0.0. or 255.255.255.0. The xx.yy are based on your team number and zz is typically in the 5-99 range. Fifth, we disable the windows firewall on the PC. Then we run the imaging tool. That has always worked.
If the cRIO is new, it has a factory set IP address that I forget. Good luck.
We had similar trouble today. When we were reimaging, we chose a different team number so that the cRIO’s IP would be different. The first time we tried, the tool changed the cRIO’s IP to the new address, then lost connectivity. After trying many times, we found that we needed to change the IP address of the computer so that it would work with the cRIO’s new IP. For example, if we started with the cRIO on team 123, the cRIO’s address would be 10.1.23.2, and the computer would be 10.1.23.5. After you run/fail the imaging tool setting the robot on team 999, your computer’s IP would need to be 10.9.99.5. Also, be sure to check the advanced menu in network adapter settings and make sure your network adapter only has ONE address. If it has two, it doesn’t work!
Everything looks correct, but something is obviously wrong. Otherwise it would be working.
Does your computer not have a wireless network interface? I don’t see one mentioned in the ipconfig output.
I assume you’ve tried simply rebooting. That fixed a network problem for me today.
The only clue I have to a potential problem is that the imaging tool error message doesn’t actually tell you what your network adapter addresses are set to. That suggests that it isn’t able to read something from the system properly. I doubt it’s something as silly as the program being confused by the Spanish language, but if you have another computer with Windows running in English you might try using it instead.
We had the same problem with our original 8 slot cRio. I don’t know what it is about this year, but we have never had this much trouble with it.
I would suggest turing off IPV6 on the adapter being used. The fact that it doesn’t list an address in the error message is odd. The “unreachable” message means it’s on the wrong ip address to me. I have seen the network address revert to something else after a reboot.
This is what we did to get ours to image today.
We shut off the wireless adapter with a hardware switch and then disabled it in the control panel (it still showed up).
Second, we also had to delete another internet address under the advanced setting of the ethernet adapter. I think it may have been added by running the driver’s station on the development laptop.
We used a crossover cable between the laptop and crio, although I don’t see any reason it wouldn’t work with the router in between.
We set the internet address to 10.x.y.6 (x.y is our team number of course) and the mask to 255.255.255.0 as per the “Getting Started” guide.
Finally the student noticed that we had been running the 2012 verion of the imaging tool running. It was still on the laptop from last year. Running the 2013 version and entering the team number helped.
Firewall has been off the whole time.
Finally, with all that fixed, we were able to image it.
The cRio is howerver, acting flakey when we put robot code in it and run it, but that’s a post for another day if we can’t get it settled down.
