so i hooked up my computer and the rio to the drivers station just like it says in the instructions but my computer says it cant find a rio when i try to load the stuff on it. any ideas whats up there. i checked power to everything and all the lights on the Ethernet ports were lit up.
does it at least see that its there but just not let you download it, or will it completely not recognize it?
When you start the Imaging Tool, does it say “No CompactRIO devices were found. Verify the network connection.” or does it let you select the cRIO from the list and then it complains after you hit Apply?
Either way, double check that you have made your IP static to the right thing.
If you are going straight from the laptop to the cRIO, you’ll need to use the crossover cable (the orange one), if you are connecting to it through either the DS or the router, then normal cables will work.
If it still doesn’t work, try disabling your other network interfaces. I had a loopback device I forgot about that was within the range of the cRIO. Two interfaces in the IP range = bad.
Which instructions in particular are you using? There’s a typo in the IP address in one section, showing 10.x.x.1 where 10.x.x.6 is correct. Maybe that’s your problem.
yup, 1501 got hung up on that for aout 4 hours, basically a whole workday!
so i have my ip set to 10.0.0.6 and the computer is plugged in via Ethernet to the drivers station and the rio is plugged into the drivers station but my computer still cant see the rio. it just keeps saying no rio devices found.
Nick, I would suggest skipping the suggestion in the manual directing you to hook your PC to the cRIO through the Driver Station. If you have already updatedup your driver station, It’s new IP address will be 10.XX.YY.5, or in your case 10.0.8.5, and the cRIo is by default 10.0.0.2. Since they are on a different subnet, then they cannot communicate with eachother.
Assuming you have already updated your DS and set you team # into it, I suggest taking the orange crossover cable from the kit that is designated for the camera, connecting it from the PC to the cRIo port 1. For reference, you can always tell its a crossover if you hold the two connectors of the cable side-by-side and they ahve a different pinout/color arrangement.
Then set your IP address on the PC to 10.0.0.6. Power on the cRio and do the update process.
If you still have troubles, go to Start->Run and type cmd. This should bring up your prompt terminal. Two commands to remember are ipconfig and ping. If you type ipconfig, and there are at least two devices on the connection (in this case a cRio and a PC) this will show you what your ip and subnet are configured as. If you have multiple NICs or a wireless adapter, make sure you look for the right one. If you type ping <address> , where address is the IP address you want to see is communicating on your network, you should see a test of that address which at the end should tell you if there was a reply from the device in question.
In your case type ping 10.0.0.2. If the cRIO is there and has an IP as expected, you should see four successful message packets sent and replied to. If not, then you might have bigger troubles on your hands, or someone updated your cRIO and didn’t tell you.
As a last, and I mean last, resort, you can consult page 15 in the crio-frc_Operating_Instructions.pdf available on the NI.com/first site at:
http://decibel.ni.com/content/docs/DOC-2632
This will show you how to set the IP to 0.0.0.0. Then setting your PC to 0.0.0.X, where X is not zero with a subnet of 255.0.0.0, should allow you to update the cRio.
When you have successfully updated the cRio, make sure you set you PCs IP address back to 10.0.8.6 and test out the entire system as outlined in the manual on the network setup. I suggest a qiuck ping test to each of the devices in the network for confirmation.
Good luck…
Nick, I would suggest skipping the suggestion in the manual directing you to hook your PC to the cRIO through the Driver Station. If you have already updated your driver station, It’s new IP address will be 10.XX.YY.5, or in your case 10.0.8.5, and the cRIo is by default 10.0.0.2. Since they are on a different subnet, then they cannot communicate with eachother.
Assuming you have already updated your DS and set you team # into it, I suggest taking the orange crossover cable from the kit that is designated for the camera, connecting it from the PC to the cRIo port 1. For reference, you can always tell its a crossover if you hold the two connectors of the cable side-by-side and they ahve a different pinout/color arrangement.
Then set your IP address on the PC to 10.0.0.6. Power on the cRio and do the update process.
If you still have troubles, go to Start->Run and type cmd. This should bring up your prompt terminal. Two commands to remember are ipconfig and ping. If you type ipconfig, and there are at least two devices on the connection (in this case a cRio and a PC) this will show you what your ip and subnet are configured as. If you have multiple NICs or a wireless adapter, make sure you look for the right one. If you type ping <address> , where address is the IP address you want to see is communicating on your network, you should see a test of that address which at the end should tell you if there was a reply from the device in question.
In your case type ping 10.0.0.2. If the cRIO is there and has an IP as expected, you should see four successful message packets sent and replied to. If not, then you might have bigger troubles on your hands, or someone updated your cRIO and didn’t tell you.
As a last, and I mean last, resort, you can consult page 15 in the crio-frc_Operating_Instructions.pdf available on the NI.com/first site at:
http://decibel.ni.com/content/docs/DOC-2632
This will show you how to set the IP to 0.0.0.0. Then setting your PC to 0.0.0.X, where X is not zero with a subnet of 255.0.0.0, should allow you to update the cRio.
When you have successfully updated the cRio, make sure you set you PCs IP address back to 10.0.8.6 and test out the entire system as outlined in the manual on the network setup. I suggest a qiuck ping test to each of the devices in the network for confirmation.
Good luck…
nvm figured it out its a problem with my computer (which is old and a piece of junk)
We’re having issues updating the firmware on our cRIO too. The status in the “Reconfiguring Device” window shows us going through the following:
Extracting CompactRio Image…
Connecting to CompactRio device…
Formatting CompactRio device…
Assigning IP Address…
Updating CompactRIO Image…
unable to complete operation because of unexpected error 15425
FTP transaction 425 connection error
We are connected directly to the cRIO via a crossover cable. We have also tried through the driver station and the wireless. Additionally, we have tried different IP addresses on the computer. We have also disabled our firewall on the computer.
Any suggestions would be most appreciated. Thanks in advance.
This is probably not your problem since you said you’ve also tried it through the DS, but I’ll post anyway in case others have this issue.
We initially tried to update the Rio firmware with a direct connection between the PC and the Rio, but that caused the Labview updater program to crash, returning some cryptic error about an unhandled exception or something. (we tried a few times). In the end, I decided this was probably due to the fact that when using a direct connection, the Rio reboots and when that happens the laptop thinks the network cable is unplugged (because the Rio shuts down its network port for a moment). I suspect the updater program is trying to communicate at some point when Windows thinks the network is unplugged and this causes an error which the updater fails to handle. I ended up connecting the laptop to the DS and the DS to the controller as recommended (just had to find another ethernet cable) and then it worked OK.
Thanks for the input. We have tried through the DS and unfortunately we are continuing to get the same error. We’re not sure where to go from here.
Are you sure your firewall is off? I had disabled ours even before loading the FRC LabVIEW software, but we got the same FTP error the first time we tried to update the cRIO. I found that the firewall had mysteriously re-enabled itself, turned it off again, and the update succeeded on the next attempt.
The firewall was disabled and the error still shows up.
Does the camera have to be connected to the cRIO during the firmware upgrade?
We tried a new laptop and it finally worked. Thank you for all of the trouobleshooting advice!
We fixed the problem. We tried using a different computer and it worked.