Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   truncated mDNS name (http://www.chiefdelphi.com/forums/showthread.php?t=142663)

wireties 27-01-2016 18:44

truncated mDNS name
 
Our robot is occasionally coming up as roboRIO-1296-FRC (as shown on radio status summary page) instead of roboRIO-1296-FRC.local, anyone else experienced this? We are using the new radio and a Windoze 10 development environment, C++ if that matters.

TIA

RufflesRidge 27-01-2016 18:56

Re: truncated mDNS name
 
I haven't looked, but I would expect that it would always come up like that. That's the actual host name. ".local" is a shortcut that indicates to use mDNS for the resolution.

wireties 28-01-2016 00:20

Re: truncated mDNS name
 
Quote:

Originally Posted by RufflesRidge (Post 1531148)
I haven't looked, but I would expect that it would always come up like that. That's the actual host name. ".local" is a shortcut that indicates to use mDNS for the resolution.

That is what I thought but I could ping one and not the other. It finally worked itself out, frustrating to wait for though.

wt200999 28-01-2016 21:52

Re: truncated mDNS name
 
We are seeing the same issue on our side. We can ping 'roboRIO-3005-FRC' and 'roboRIO-3005-FRC.lan' but not 'roboRIO-3005-FRC.local' which means we cannot connect to the driver station. We can send code over LabVIEW, but only by changing the address.

We are using Windows 7 and LabVIEW with the new radio.

To fix, the only thing I have found that works is to reboot the system.

We tried updating the roboRIO firmware as well as disabling other network devices. None of this seemed to help.

Anyone have any ideas?

euhlmann 28-01-2016 22:01

Re: truncated mDNS name
 
The OM5P-AN uses .lan, while the d-link uses .local.

We just assigned the rio to 10.te.am.2 and used that. mDNS has always been problematic.

wt200999 28-01-2016 22:18

Re: truncated mDNS name
 
Quote:

Originally Posted by euhlmann (Post 1531786)
The OM5P-AN uses .lan, while the d-link uses .local.

This can't be it, when I reboot I can see the .local address just fine using the OM5P-AN.

Quote:

Originally Posted by euhlmann (Post 1531786)
We just assigned the rio to 10.te.am.2 and used that. mDNS has always been problematic.

What do you do for competition?


All times are GMT -5. The time now is 02:59.

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