|
|
|
 Man, Dave always has to one up us. We build robots to play games, he build robots to go on other planets, Elgin makes CD 30 inches, you make it 63 inches. - Levin571 [more] |
 |
|
|||||||
|
||||||||
 |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: cRIO Imaging Issue
If I remember right, it needs to be 255.0.0.0. We got our successfully flashed on a Windows 7 laptop with that subnet mask.
|
|
#2
24-01-2013, 21:57
|
|||
|
|||
|
Re: cRIO Imaging Issue
We are having exactly the same issue with the modules not showing up. Our cRio is a brand new 4 slot however. I am trying to image it with a Widows 8 laptop. When I get to school tomorrow I will try to image it with our old laptop and see if that will help. Thing is - the new Windows * laptop imaged the old 8 slot cRio not problem. This was my second day spent messing around with this new cRio. I was able to place Lab View code on it (no errors returned) using run as startup, but when I pull up the drivers station it does not recognize the cRio - no robot code. Any advice would be welcome. Could it be the drivers that came with the cRio? Should I re-install them?
|
|
#3
25-01-2013, 07:18
|
|||
|
|||
|
Re: cRIO Imaging Issue
Just to clarify, the laptop can't actually see the modules. The cRIO has to be imaged with a recent enough image to publish its module list to the imaging tool. Just graying out the image doesn't make that crystal clear, but that is one thing that can cause it.
Greg McKaskle |
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
