Quote:
Originally Posted by Mark McLeod
That's not good.
The Jaguars are the least of it.
Just work at getting the "No Comms" message off the DS.
You should be able to at least ping the DS while connected to the ETH2 port.
I assume your PC is set to 10.0.56.6
PC mask set to 255.0.0.0
Disable any firewall you may have running for testing.
You should have your cRIO IP address set to 10.0.56.2 and your DS set to 10.0.56.5 at this point in the testing.
DS ETH1 port connected to the cRIO port 1
P.S.
When you updated the cRIO with the FRC cRIO Imaging Tool the settings you were supposed to use would not have resulted in an IP address of 10.0.0.2
Under "Format Controller"
Select Image = FRC_2009_v2.zip
Device name = FRC-cRIO-56
Team ID = 56
|
I realize the issue of not being able to ping the DS. I have tried it with my PC at 10.0.0.6 and 10.0.56.6. Similarly, I have tried pinging both 10.0.0.5 when the team number was set to 0000 and 10.0.56.5 when the team number was set to 56.
When I flashed the cRIO, I did set the team number and thus the IP to 10.0.56.2. I was mentioning some work I did earlier, before flashin the cRIO when the IP was still set to the default of 10.0.0.2.
All of this makes me think something is broken inside our DS.