Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   Well, this is getting a bit old, but here is round 3 (http://www.chiefdelphi.com/forums/showthread.php?t=153488)

MikePerreman 11-01-2017 19:30

Well, this is getting a bit old, but here is round 3
 
so, brand new laptop, i installed the update suite, cpp and java plugins, well, surprise surprise, the mdns doesn't work right, i can connect fine over usb and ethernet, if i set the roborio to a static 10.2.47.2, just put that in the ds, and dumping code seems to work ok. but i feel it more of a workaround, not a fix. i am running windows 10, and it would appear that, between windows and dell, its up to date. is there a mdns that im supposed to install as a worst case senerio, or what. this is the 3rd (unique) laptop that has this problem. what have i done wrong?

nevermind, dumping code doesnt work, it gets here:
get-target-ip:
[echo] Trying Target: roboRIO-247-FRC.local
Unknown host: roboRIO-247-FRC.local
[echo] roboRIO not found via mDNS, falling back to DNS
Unknown host: roboRIO-247-FRC.lan
[echo] roboRIO not found via DNS, falling back to static USB
[echo] roboRIO found via static USB
dependencies:
then stalls out, the bot is not connected via USB, only wireless

AustinShalit 12-01-2017 00:19

Re: Well, this is getting a bit old, but here is round 3
 
Using static IP addresses is perfectly fine and plenty of teams use them. If you want to continue troubleshooting the networking over mDNS, please make sure you have done the following:

Is your laptop able to obtain an IP address from the radio?

MikePerreman 12-01-2017 16:17

Re: Well, this is getting a bit old, but here is round 3
 
ok, everything has been updated, i am getting the ip 10.2.47.107, and everything has been restarted. still no mdns. (going to the ds and scanning tells me none found, however putting in 10.2.47.2 connects to the bot)

MikePerreman 13-01-2017 21:32

Re: Well, this is getting a bit old, but here is round 3
 
i dont approve of bumps, but this is urgent

frodobaggins05 14-01-2017 11:16

Re: Well, this is getting a bit old, but here is round 3
 
Do you have a roborio on your robot?

frodobaggins05 14-01-2017 11:17

Re: Well, this is getting a bit old, but here is round 3
 
If so, have you installed labview on your computer?

MikePerreman 14-01-2017 12:45

Re: Well, this is getting a bit old, but here is round 3
 
yes, we have the roborio on our bot, and i have not installed labveiw, we are a java team, so i havent even bothered with that. heres some more info on my situation:
So, our programming mentor and i cannot connect to the RIO over wireless, tethered works just fine, and infact, when tethered, one the tethered is disconnected, we keep wireless comms until you disconnect from the radio, and reconnect. in the DS the 'light' next to robot radio is on. pinging roborio-247-frc.local, on my laptop results in something to the extent of host name not found, and on the mentor's we get a destination host unreachable. however, on the other programming laptop, works first try, every try. ive disabled IPv6 and both mDNS and ni mDNS is allowed through the firewall of my laptop, if a model helps, its a dell inspiron 15.

here is the versions from the DS
DS: 17.0a11
RIO: FRC_roboRIO_2017_v8
Lib: Java 2017.1.1
PCM: 1.65
PDP: 1.40

MikePerreman 14-01-2017 12:47

Re: Well, this is getting a bit old, but here is round 3
 
is there a different board that this thread should be on?

frodobaggins05 14-01-2017 13:01

Re: Well, this is getting a bit old, but here is round 3
 
Try installing labview and using that.Roborio and Labview are both made by National Instruments and are made for each other

gbear605 14-01-2017 13:31

You definitely shouldn't need to install LabView (source: our team doesn't have this issue and doesn't have LabView installed).

Try the following fixes. Any one of them might solve your issue.

Have you tried reflashing the radio firmware (see ScreenSteps for instructions)?

Have you tried a different radio?

Have you tried a different roboRIO?

Have you tried reflashing the roboRIO firmware?


Sent from my iPhone using Tapatalk

frodobaggins05 14-01-2017 13:39

Re: Well, this is getting a bit old, but here is round 3
 
You dont need to use Labview but they work better together and can eliminate a lot of problems

Fletch1373 14-01-2017 14:55

Re: Well, this is getting a bit old, but here is round 3
 
Shot in the dark here... Have you checked whether Windows Firewall is disabled? That is strongly recommended. If you absolutely can't/won't disabled it, you can allow the NI mDNS Responder application through the firewall.

Quote:

Originally Posted by frodobaggins05 (Post 1631102)
Try installing labview and using that.Roborio and Labview are both made by National Instruments and are made for each other

No. Just no. The RoboRio was made by NI for FRC. It was made to support LabView, but most certainly does not require it. FIRST/WPI/et al. work in consultation with NI to get the C++/Java versions working equally as well.

nickmcski 14-01-2017 15:24

Re: Well, this is getting a bit old, but here is round 3
 
Check in your services to see if mDNS service is running (or if its listed), it should have been installed when you ran the FRC 2017 update suite.

Can confirm that your computer is properly connecting to the router? You should have an IP address like 10.TE.AM.x (You can see this by opening the command line and typing ipconfig)


As a last case scenario, you could try to install iTunes. (I know it sounds crazy) iTunes has apples Bonjor service, another mDNS responder. You shouldn't need to install this though, if you were to I would only use it as a temporary solution to ensure connectivity.

MikePerreman 14-01-2017 19:56

Re: Well, this is getting a bit old, but here is round 3
 
ok, i have installed labveiw, and the bot connects, so long as the rio is the first thing i connect to, however, once i connect to the internet, it can no longer connects to the rio. i do get my ip from the router (most often 10.2.47.107 most often) ive re-flashed the radio and the rio 3 times a piece, we dont have another radio/rio to test at the moment, the ni mdns responder is running and allowed through the firewall, and i have installed bonjior (or however its spells) from itunes.

MikePerreman 14-01-2017 20:07

Re: Well, this is getting a bit old, but here is round 3
 
Aha! if i disconect from wifi, disable my wifi chip, enable, then connect to the bot, it works, however if i disconnect and connect to the internet, i cant connect to the rio anymore.
just turning the wireless off and back on doesnt work

Fletch1373 14-01-2017 22:43

Re: Well, this is getting a bit old, but here is round 3
 
Do you have any 3rd party applications installed that manage network connections? Most major retail brands install something similar to this (including ASUS, Lenovo, Dell, etc).

abigailthefox 14-01-2017 22:47

Re: Well, this is getting a bit old, but here is round 3
 
We've had quite a few weird RoboRIO problems last season/this season, so I thought I'd just offer this quick checklist.

Step 0: Update your bridge firmware. If you are using the 2017 bridge that shipped with your KOP, your firmware needs to be updated if you have not already. Also, if you're using the 2016 bridge ( or anything older than that), you should update it as well.
Step 1: Reimage your RoboRIO. The WPI screen steps has an excellent set of instructions on how to do this.
Step 2: Reinstall the JRE on your robot (you stated you are a Java team). When you image the RoboRIO, the current JRE will be lost. Our team was getting some pretty ambiguous error messages, and it turns out we just forgot to reinstall the JRE after imaging.
Step 3: Try to connect to the RoboRIO in your browser. By typing in "roboRIO-####-FRC.local" (where #### is your team number with no leading zeroes, you should be able to get to the browser RoboRIO utility (this can also be used to ping the RoboRIO to test the connection. I recommend you try both).
Step 4: Use a different bridge. If you have access to a different model than the one you're using (i.e. if you've been using 2017, switch to 2016, and vice versa. You will also need to update the new bridge, if you haven't yet)
Step 5: Use a different RoboRIO (if you have one. These are expensive, and I know a lot of teams only have one. If this is the case, just skip this step. If you've tried absolutely everything and it's still not working, consider investing in a second RoboRIO. I would save this for when you're really desperate however, because it's not fun to be out $400 and then find that it didn't even solve your problem.)

Some other users have mentioned techniques for wrangling with the IP and firewall configurations. These are great steps to take, and I recommend taking them with someone who has experience with doing similar things, ideally a mentor or veteran student. Most of the things FIRST expects you to do (somewhat) routinely (such as imaging your RoboRIO or installing software) have great tutorials and documentation that help walk you through what you're doing. Messing with network configurations on a computer does not come with a nice made-for-FIRST guide, and it's easy to accidentally mess something important up. If you don't have a mentor who has IT experience, or a veteran student who knows about IP and network issues, then this is a great opportunity to tap your community for someone who can help you! Especially because once you make a partnership with a company/person who's willing to donate time and effort to help, you can go back to them as a resource in the future (because we all know that once one error gets resolved, it's only a matter of time before the next one rears it's ugly head).

MikePerreman 14-01-2017 23:34

Re: Well, this is getting a bit old, but here is round 3
 
ok, i discovered intel proset/wireless wifi software, so im uninstalling that, next step is to uninstall and reinstall my wifi driver, i guess

Poseidon5817 14-01-2017 23:42

Re: Well, this is getting a bit old, but here is round 3
 
Quote:

Originally Posted by frodobaggins05 (Post 1631057)
Do you have a roborio on your robot?

This is my new favorite post on CD.

MikePerreman 15-01-2017 13:20

Re: Well, this is getting a bit old, but here is round 3
 
AHA! it was the intel proset/wireless $@#$@#$@#$@#$@#$@#$@#$@# software! thank you all! now the mdns is working a-ok. thanks for the help guys!

ayeckley 16-01-2017 09:49

Re: Well, this is getting a bit old, but here is round 3
 
Quote:

Originally Posted by MikePerreman (Post 1631494)
AHA! it was the intel proset/wireless $@#$@#$@#$@#$@#$@#$@#$@# software! thank you all! now the mdns is working a-ok. thanks for the help guys!

Discussion somewhere in FIRST back in 2008-2009:

Person 1: Hey, let's ditch this proprietary IFI protocol and switch to TCP/IP!
Person 2: That's a great idea. Millions of devices can't be wrong!
Person 1: I don't see any potential downside!
Person 2: Me neither. Everything is plug-n-play! Teams won't have to waste valuable time and money trying to make stuff work anymore! It'll just happen.
Person 3: Someone in 2017 will probably complain though. There's always a complainer.
Person 1: We'll just point out to them that TCP/IP will make vision target tracking trivial! Participants will be more inspired and less frustrated!
Person 2: Hey, that's a great justification!
Person 3: <Nods in agreement> What could possibly go wrong?

Edit: I'm feeling frustrated/snarky today. All in all it was probably the right call, but certainly not without unintended consequences.

TylerHarmon 16-01-2017 10:36

Re: Well, this is getting a bit old, but here is round 3
 
This is probably a stupid question, but is the router plugged into the roboRIO? If you can tether fine but can't find the roboRIO when you're not tethered, the RIO and router may not be communicating.

This is my complete list of things to try that I think will fix the problem if done.
  1. Re image the roboRIO
  2. Re download java to the roboRIO
  3. Re image the router
  4. Make sure that your firewall is disabled (or allows the connection)
  5. Click on the wifi icon in the bottom right of your screen, click "Network Settings" > "Change adapter options" > Right click on wireless connection > Properties > IPv4 > Properties > Make sure that your IP and DNS server are both obtained automatically.
  6. Double check that the roboRIO is plugged in to the router via ethernet (It sounds silly but double check)

Good luck!

-Tyler

virtuald 16-01-2017 10:43

Re: Well, this is getting a bit old, but here is round 3
 
Quote:

Originally Posted by ayeckley (Post 1631794)
Discussion somewhere in FIRST back in 2008-2009:

Person 1: Hey, let's ditch this proprietary IFI protocol and switch to TCP/IP!
Person 2: That's a great idea. Millions of devices can't be wrong!
Person 1: I don't see any potential downside!
Person 2: Me neither. Everything is plug-n-play! Teams won't have to waste valuable time and money trying to make stuff work anymore! It'll just happen.
Person 3: Someone in 2017 will probably complain though. There's always a complainer.
Person 1: We'll just point out to them that TCP/IP will make vision target tracking trivial! Participants will be more inspired and less frustrated!
Person 2: Hey, that's a great justification!
Person 3: <Nods in agreement> What could possibly go wrong?

Edit: I'm feeling frustrated/snarky today. All in all it was probably the right call, but certainly not without unintended consequences.

It was absolutely the right call. Switching to Wifi+TCP/IP has enabled SO MUCH INNOVATION by teams in the last 6 years, and I'd bet has resulted in significant cost savings as well.

MikePerreman 16-01-2017 21:00

Re: Well, this is getting a bit old, but here is round 3
 
Quote:

Originally Posted by TylerHarmon (Post 1631818)
This is probably a stupid question, but is the router plugged into the roboRIO? If you can tether fine but can't find the roboRIO when you're not tethered, the RIO and router may not be communicating.

This is my complete list of things to try that I think will fix the problem if done.
  1. Re image the roboRIO
  2. Re download java to the roboRIO
  3. Re image the router
  4. Make sure that your firewall is disabled (or allows the connection)
  5. Click on the wifi icon in the bottom right of your screen, click "Network Settings" > "Change adapter options" > Right click on wireless connection > Properties > IPv4 > Properties > Make sure that your IP and DNS server are both obtained automatically.
  6. Double check that the roboRIO is plugged in to the router via ethernet (It sounds silly but double check)

Good luck!

-Tyler

lol, i found the problem was intel's proset/wireless software, its some kind of network manager. it didn't like mDNS, so that was the source of the problem, thanks for the help though!

David Lame 16-01-2017 22:20

Re: Well, this is getting a bit old, but here is round 3
 
Quote:

Originally Posted by virtuald (Post 1631821)
It was absolutely the right call. Switching to Wifi+TCP/IP has enabled SO MUCH INNOVATION by teams in the last 6 years, and I'd bet has resulted in significant cost savings as well.

I've been around four years now, and I'm the programming mentor Mike referred to.

Wifi+TCP/IP seems like a really good idea.

MDNS?......I'm not so sure. It just seems like ever since we went to that, an awful lot of laptops don't "just work" anymore. My connection wasn't working after reinstalling the 2017 suite, although the symptoms weren't exactly the same as Mike's. He suggested I turn off IPV6, and suddenly it started working. He said he had read it in a Chief Delphi post at some point.

I have absolutely no clue why it would have made a difference, but it did.

virtuald 16-01-2017 22:55

Re: Well, this is getting a bit old, but here is round 3
 
Quote:

Originally Posted by David Lame (Post 1632174)
MDNS?......I'm not so sure.

Yeah, I would agree on that point, I always use static IPs.

Abrakadabra 20-01-2017 12:44

Re: Well, this is getting a bit old, but here is round 3
 
But if you uninstall the Intel PROSet/Wireless software, doesn't that disable your wireless adapter altogether? (Which is normally NOT a good thing?)

See this page from Intel:

"Caution!
Uninstalling Intel® PROSet/Wireless Software also removes the Intel® WiFi adapter driver. You will not be able to use the wireless adapter on your computer. We only recommend uninstalling the driver as a final troubleshooting option. You shouldn't uninstall unless directed by an Intel technical support agent."

MikePerreman 20-01-2017 14:47

Re: Well, this is getting a bit old, but here is round 3
 
Quote:

Originally Posted by Abrakadabra (Post 1633960)
But if you uninstall the Intel PROSet/Wireless software, doesn't that disable your wireless adapter altogether? (Which is normally NOT a good thing?)

See this page from Intel:

"Caution!
Uninstalling Intel® PROSet/Wireless Software also removes the Intel® WiFi adapter driver. You will not be able to use the wireless adapter on your computer. We only recommend uninstalling the driver as a final troubleshooting option. You shouldn't uninstall unless directed by an Intel technical support agent."

not at all, the proset/wireless software seems to do nothing but get in the way of mDNS. ive removed it for a few weeks now and there seems to be no difference. if this was true, wouldnt that mean that my wireless adapter wouldnt work on Ubuntu? so, i think that the proset/wireless software only serves to save wireless settings after you disconnect. like how a DNS lease is still valid after the client disconnects.

TL;DR: proset/wireless seems to be non-essential


All times are GMT -5. The time now is 18:27.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi