From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-05-2011 12:13 PM
Hi, all,
We are running cRIO9074 with Labview Real-Time 9.0. We cannot even ping the cRIO even after doing multiple IP resets, connecting with crossover cable, connecting back up again to our network, etc. all of this results in us not being able to ping the cRIO. It makes sense that we can’t ping it when connecting through our network since we are on different subnets (see screenshots below). However, I cannot understand why we cannot connect when connected with crossover cable. Also not sure why the DHCP will not assign an IP. One thing I noticed was that “Halt on IP Failure” is set to “Yes” (see screenshots below). We have already tried everything suggested on the links sent.
It is additionally important to understand that this occurred randomly (and has occurred two times in the past) where we are testing then suddenly our connection is lost. In the past we have noticed that when this happens connecting via a crossover cable would work then several days later connecting up to the network with the same router would work again??? WE also initially had problems connecting to this cRIO when we first got it because it had software issues. This is becoming very frustrating and has resulted in significant time lost on this project.
Thank you
05-06-2011 04:14 PM
Hi,
Everything you have said leads me to believe that you have run out of IP addresses on your subnet. We are actually having a similar problem right now. If you set the IP Address to "DHCP or Link Local," your router will try to assign the RIO an IP address. If it can't (usually because there are none left on the subnet), it will set a link local address. From your screenshot, I can see that your IP is link local (169.254.xxx.xxx).
If you are having trouble connecting with a crossover cable then this could be a different issue. Have you looked at this KB to make sure you are setting both the IP address of your computer and RIO to static? If you aren't then a crossover cable won't work.
If it doesn't sound like I've described your issue, could you try using console out to get some more information? Here are instructions on how to do this.
01-23-2016 12:30 AM