Quote:
Originally Posted by Skyehawk
I'm a college student so I can't go test stuff. But I can see the concern, and why we need to fix this asap. When we first created a testbed project we just switched it to tank drive, and added a 2 solenoid pneumatics system. T
That is the extent of this little program.
The next thing we did was tether via USB, then build and deploy the project. any project that we would build and deploy would return the error from the first post. The IP being: roboRIO-876.local. This is the IP that it should be responding to correct?
I'm just confused, because in years past when the cRIO was 10.xx.yy.2, this is what I expected this year.
|
Last night we had connection issues and found that for some reason the roborio can be reached via the long 172 ip or the 10.xx.yy.20. I'm confused on how we would be able to use two different IP's for the same roborio. All of a sudden the 172 one just stoped working and it changed itself to the 10.xx.yy.20 one. How can this be?