|
|
|
 If I can make a comeback, so can you. - Warren Boudreau [more] |
 |
|
|||||||
|
||||||||
 |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| If I can make a comeback, so can you. - Warren Boudreau [more] |
|
|
|||||||
|
||||||||
|
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
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 Last edited by MikePerreman : 11-01-2017 at 20:05. 
|
|
#2
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?
|
|
#3
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)
|
|
#4
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
|
|
#5
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?
|
|
#6
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?
|
|
#7
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
|
|
#8
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?
|
|
#9
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
|
|
#10
14-01-2017, 23:42
|
||||
|
||||
|
Re: Well, this is getting a bit old, but here is round 3
Quote:
|
|
#11
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!
|
|
#12
16-01-2017, 09:49
|
||||
|
||||
|
Re: Well, this is getting a bit old, but here is round 3
Quote:
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.
|
|
#13
16-01-2017, 10:43
|
||||
|
||||
|
Re: Well, this is getting a bit old, but here is round 3
Quote:
|
|
#14
16-01-2017, 22:20
|
|||
|
|||
|
Re: Well, this is getting a bit old, but here is round 3
Quote:
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.
|
|
#15
16-01-2017, 22:55
|
||||
|
||||
|
Re: Well, this is getting a bit old, but here is round 3
Quote:
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
