Eclipse won't connect to roboRIO

[Cryptogenic]

Originally Posted by TheMechanic40

I know, I feel like that happened as well because me and three other people are using Windows 8.1, two others are using Windows 7 and the last one is using a mac (not sure about his operating system's version) and one of the first things I tried was uninstalling and reinstalling eclipse and reinstalling the WPI plugins.

I am also using windows 8.1

I am going to use m friends laptop tomorrow which also uses 8.1 to test it. It seems like it would be a problem with 8.1 and the station.

Anyone else using windows 8.1 and getting the same error?

[Cryptogenic]

Originally Posted by joshtt

I was experiencing the same problem. The wpilib jar in eclipse prompted me to update, and when I did, the problem went away. Hope this is the same for you

Are you using Windows 8.1?

[TheMechanic40]

Originally Posted by joshtt

I was experiencing the same problem. The wpilib jar in eclipse prompted me to update, and when I did, the problem went away. Hope this is the same for you

I checked for updates in eclipse and found one for robot java development so I will follow up on this in a few days when I am next with the robot.

[virtuald]

You might want to check out the end of http://www.chiefdelphi.com/forums/sh...d.php?t=132607.

After some investigation, I found that there are two mDNS services running on the roborio, and I believe they are fighting each other. Once we disabled one of them, we were able to resolve the roboRIO's address without any problems.

I suspect that the reason this hasn't been a problem for anyone yet is that there are a few different mDNS implementations being used, and some work differently in the face of conflict than others.

[TheMechanic40]

Originally Posted by virtuald

You might want to check out the end of http://www.chiefdelphi.com/forums/sh...d.php?t=132607.

After some investigation, I found that there are two mDNS services running on the roborio, and I believe they are fighting each other. Once we disabled one of them, we were able to resolve the roboRIO's address without any problems.

I suspect that the reason this hasn't been a problem for anyone yet is that there are a few different mDNS implementations being used, and some work differently in the face of conflict than others.

Ok thanks, I will try this the next chance I can.

[Cryptogenic]

Originally Posted by virtuald

You might want to check out the end of http://www.chiefdelphi.com/forums/sh...d.php?t=132607.

After some investigation, I found that there are two mDNS services running on the roborio, and I believe they are fighting each other. Once we disabled one of them, we were able to resolve the roboRIO's address without any problems.

I suspect that the reason this hasn't been a problem for anyone yet is that there are a few different mDNS implementations being used, and some work differently in the face of conflict than others.

I will also try this when I get to the lab to test it out. But if this is the problem, why can other computers compile to it?

[Cryptogenic]

Originally Posted by virtuald

You might want to check out the end of http://www.chiefdelphi.com/forums/sh...d.php?t=132607.

After some investigation, I found that there are two mDNS services running on the roborio, and I believe they are fighting each other. Once we disabled one of them, we were able to resolve the roboRIO's address without any problems.

I suspect that the reason this hasn't been a problem for anyone yet is that there are a few different mDNS implementations being used, and some work differently in the face of conflict than others.

I spent a part of today investigating this, but I don't see where you saw the two mDNS services. If you could post a pic of where you found it, I would greatly appreciate it.

[virtuald]

Originally Posted by Cryptogenic

I spent a part of today investigating this, but I don't see where you saw the two mDNS services. If you could post a pic of where you found it, I would greatly appreciate it.

I don't have the roborio available, so no pictures. I did grab some logfiles, however. If you ssh into the roborio, check out /var/log/messages. You'll find messages like this:

Jan 25 16:55:38 roboRIO-1418 nimDNSResponder: Local Hostname roboRIO-1418.local already in use; will try roboRIO-1479.local instead
Jan 25 16:55:40 roboRIO-1418 nimDNSResponder: mDNSCoreReceiveResponse: Received from 10.14.18.20:5353   20 20.18.14.10.in-addr.arpa. PTR roboRIO-1418.local.
Jan 25 16:55:40 roboRIO-1418 nimDNSResponder: mDNSCoreReceiveResponse: Unexpected conflict discarding   20 20.18.14.10.in-addr.arpa. PTR roboRIO-1479.local.

Looking at the log closer, you'll see messages from avahi-daemon and nimdnsresponder, which have the same purpose. However, if you look at my other post, some further investigation today has shown that if I disable one or the other, then I end up with different effects. Apparently the driver station requires the avahi-daemon, but my OSX machines cannot resolve the hostname when it's enabled.

You can also use "ps -Af" to see avahi-daemon and nimdnsresponder both running.

You might check to see if you have iTunes/bonjour installed, as they provide a similar mDns service, and it might have the same problems that we have on OSX.

You can find rc.d symlinks to activate the services in /etc/rc5.d/...avahi-daemon and /etc/rc5.d/...nimdnsresponder

[Cryptogenic]

Originally Posted by virtuald

I don't have the roborio available, so no pictures. I did grab some logfiles, however. If you ssh into the roborio, check out /var/log/messages. You'll find messages like this:

Jan 25 16:55:38 roboRIO-1418 nimDNSResponder: Local Hostname roboRIO-1418.local already in use; will try roboRIO-1479.local instead
Jan 25 16:55:40 roboRIO-1418 nimDNSResponder: mDNSCoreReceiveResponse: Received from 10.14.18.20:5353   20 20.18.14.10.in-addr.arpa. PTR roboRIO-1418.local.
Jan 25 16:55:40 roboRIO-1418 nimDNSResponder: mDNSCoreReceiveResponse: Unexpected conflict discarding   20 20.18.14.10.in-addr.arpa. PTR roboRIO-1479.local.

Looking at the log closer, you'll see messages from avahi-daemon and nimdnsresponder, which have the same purpose. However, if you look at my other post, some further investigation today has shown that if I disable one or the other, then I end up with different effects. Apparently the driver station requires the avahi-daemon, but my OSX machines cannot resolve the hostname when it's enabled.

You can also use "ps -Af" to see avahi-daemon and nimdnsresponder both running.

You might check to see if you have iTunes/bonjour installed, as they provide a similar mDns service, and it might have the same problems that we have on OSX.

You can find rc.d symlinks to activate the services in /etc/rc5.d/...avahi-daemon and /etc/rc5.d/...nimdnsresponder

As you were saying about having iTunes since that has similar mDNS service as OSX, does that mean it is just having that apple software on your computer?

[virtuald]

Originally Posted by Cryptogenic

As you were saying about having iTunes since that has similar mDNS service as OSX, does that mean it is just having that apple software on your computer?

If I recall correctly, iTunes installs Bonjour, which is an implementation of Apple's mDNS. I'm curious to see if people who are having the same problems I am happen to have that installed.

If not, then no correlation. If there is a correlation, that could be interesting to look into more.

[Cryptogenic]

Originally Posted by virtuald

If I recall correctly, iTunes installs Bonjour, which is an implementation of Apple's mDNS. I'm curious to see if people who are having the same problems I am happen to have that installed.

If not, then no correlation. If there is a correlation, that could be interesting to look into more.

I disabled bonjour on my computer(remember how you did this since it will disable iTunes with it) and tried to recompile and encountered the same error.

Thursday I will have my friend install iTunes on his computer and try compiling again. If anyone wants to test this before then, please do.

[Cryptogenic]

Other members on my team upgraded to 8.1 and they are now not able to compile to the robot. So the problem is something within 8.1, not the roboRIO.

So if anyone finds a way to get around 8.1 not being able to compile, please post it.

[TheMechanic40]

Originally Posted by Cryptogenic

Other members on my team upgraded to 8.1 and they are now not able to compile to the robot. So the problem is something within 8.1, not the roboRIO.

So if anyone finds a way to get around 8.1 not being able to compile, please post it.

This is interesting because I have 8.1 and 3 other members of my team also have 8.1 and they can compile using mDNS just fine.

[Cryptogenic]

Originally Posted by TheMechanic40

This is interesting because I have 8.1 and 3 other members of my team also have 8.1 and they can compile using mDNS just fine.

Did the computer start with 8.1? The computers that we tested on were originally 8 and upgraded to 8.1 are the ones that don't work. We don't have any computers that were originally 8.1 to test it on.

[Alan Anderson]

Were the computers upgraded to 8.1 after the programming tools were installed? Perhaps the upgrade modified a path setting, or replaced a .dll file, or moved a folder. Has anyone tried uninstalling and reinstalling Eclipse and the plugins after doing the upgrade?