Quote:
Originally Posted by DavidGitz
Again, just so everyone is on the same page, everything is configured per the Control Systems Section 2. All wired/wireless communications are pingable, all led's turn on the robot correctly and all on the driver station turn on correctly (with the exception of the above).
|
Thanks for checking that status light for me Mark. There is only 1 NIC on any laptop we are using, and have always been using a wired connection between the laptop and the router and were switching between the wired and wireless on the robot. The firewall was turned off on all laptops and no vpn software is running.
Quote:
Originally Posted by Mark McLeod
I think we only see the Timeout message if there's been at least an initial successful handshake between the PC and cRIO.
Otherwise, the usual message is "Target not found."
|
I agree with this statement Mark, as I can reboot the cRIO from MAX. So from what you're saying, once you can re-image the cRIO correctly, the only way you can get it to have a timeout issue is by having the wrong ip address set in the default project? That narrows it down a little, obviously we are setting up our project correctly but we are focusing in on the problem. We are going through the RMA process today to get our cRIO repaired.