Crio is not communicating?

[CW2775]

Our Crio is not communicating.  It appears that the problem occurred after updating the DS software.  Attempts to update the Crio brought up the problem.  The Crio is not discoverable in the imaging tool or MAX.  A couple of hours have passed with numerous attempts at rebooting in safe mode and/or ip reset.  Status light flashes every few seconds indicating that it is not configured.  Any help connecting/formating the Crio would be greatly appreciated.

[NI-Bob]

Hello CW2775,

My first question that I have for you is how are you connecting to you cRIO to your laptop?  Are you using the specifications that are described in the FIRST Manual Section 5.1.2?  If you are connected via the Driver Station your Laptop's static IP address should be 10.XX.YY.6 (where XXYY corresponds to your team number).  As long as your system is configured as it is described and you do not have a Firewall active on your machine you should be able to see the cRIO.

If you have followed all of the steps in the manual and are still unable to communicate with you cRIO please verify that you do not have a Firewall active on your laptop.  Also, verify by using another crossover cable to make sure that the cable is not what is causing the bad connection.  My other question is if you have been able to connect to your cRIO in the past?  If so, has there anything that you have done between it working and not working?  This can help us determine other possible reasons for a bad connection.  Please let me know if you have any further questions after reading through this information and I will be happy to assist you!  Have a great day!

Thanks!

Bob

[CW2775]

Bob,

Thanks.  I found the problem shortly after I posted the question.  It was the firewall.  I was able to see cRIO earlier with the firewall enabled with exceptions.  This was a company laptop that does not allow the firewall to be disabled.  Since I got around the firewall earlier, I assumed that this was not the problem.  My personal laptop had no problem seeing the cRIO (0.0.0.0).  I configured it and was off and running again.

Thanks,

Chris