Code Deployment Error

[tmk]

http://skyehawk876.imgur.com/all/
We get this error when trying to deploy code to the roboRIO. It is a communications error, we have have tried deployment of code via Ethernet and USB. We have tried deploying default code. The roboRIO is running the 2015v23 image. I am out of ideas, thanks for any help in advance.

[Skyehawk]

- And we are able to ping the roboRIO at 172.22.11.2 and roboRIO-876.local

[tmk]

Never mind, we fixed the problem. Changed target IP of the roboRIO to 172.22.11.2 in the labview explorer.

[Alan Anderson]

What is the value in parentheses after the Real-time target line in the project? It should match the roboRIO-876.local name.

[tmk]

That's the target IP and we hadn't remembered before that the roboRIO was given a new IP when we imaged it. The target IP has to match the set IP, and that's what we finally figured out. Thanks!

[Greg McKaskle]

The target IP can be either a resolved IP such as 172.22.11.2, or it can be a DNS name that resolves to that same IP. What Alan was saying is that you really want it to be based on the team number so that it will work over ethernet and especially wifi. The project setting you have now will work on USB, but will fail to work over the others.

Greg McKaskle

[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.

[Mark McLeod]

Does this help your understanding of the new networking?
RoboRIO Networking (http://wpilib.screenstepslive.com/s/4485/m/13503/l/242608-roborio-networking)

The use of mDNS makes networking easier, because DHCP can be used, which is what people normally use on their laptops.
But there is a curve to unlearning some of what we used to have to do for the old system.

[TylerStaudigel]

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?

[Mark McLeod]

The mDNS address for both the Ethernet and USB network connections to the roboRIO is:
roboRIO-144.localUsing this address allows the network to automatically connect to whichever wire you happen to have plugged in-USB or Ethernet. It also automatically recovers and switches paths if one of the cables becomes unplugged, but the other is still available.


The fixed static IP address for the roboRIO via just the USB port is:
172.22.11.2It will stop working when the USB cable is disconnected. So this won't work via the Ethernet port, e.g., wirelessly.

The roboRIO Ethernet port IP is dynamically assigned by DHCP and can change based on what other IP devices are also requesting DHCP assigned address.
So it doesn't have a fixed IP address from session to session, so don't depend on the IP currently assigned. It may change the next time you boot and have added an IP camera or have a programming laptop connect before the roboRIO does.

[tmk]

I changed the target DNS address to roboRio-144.local in the Project Explorer, but now I am unable to communicate with the roboRIO with either USB or Ethernet.

[tmk]

Never mind, we fixed it. The mDNS address we should use is not roboRIO-144.local, it is roboRIO-876.local
We're supposed to use our team number in place of 144.

[Mark McLeod]

Sorry about that.
I was addressing the poster before mine who is team number 144.