![]() |
Static IP from .2 to .20?
Background: The Windows mDNS responder is horridly slow and builds take nearly 40 seconds, 3 for the build and 37 to connect to the roboRIO 5 times. To fix this, I switched the order in build.xml from mDNS->USB->Static to Static->mDNS->USB and build times dropped to ~8 seconds.
However, recently, I tried to build and I couldn't get any static IP whatsoever, even though I had router and IP camera communications. I tried reflashing to no avail, only to notice that the reflasher tool said "Robot IP: 10.16.84.20" When did it switch to .20? Now, SmartDashboard can't connect over static IP as well as the old build tools (half second fix for the build tools, using mDNS on the dashboard causes quite a bit of update rate lag) |
Re: Static IP from .2 to .20?
The DLink will begin assigning IP addresses starting at 10.XX.XX.20. You may be able to log into the online control panel for the roboRIO and force it to take a static address, but this might interfere with the Field Management System at events.
|
Re: Static IP from .2 to .20?
This year the roboRIO dosent use a static IP, it uses a dynamic IP address, that means when the robot restarts the RIO can have a different IP. If you want it to have the same IP every time you have to either:
a) Set a mac reservation on the router or b) Set a static IP on the RoboRIO That way the RoboRIO will always have the same IP. |
Re: Static IP from .2 to .20?
Quote:
My build times with mDNS and a large java project (86 classes) are 12 seconds. |
Re: Static IP from .2 to .20?
According to that link,
Code:
NI mDNS Responder - Installed with the NI FRC Update SuiteIf it's worth anything, command line Code:
ping roborio-1684.localfirewall has been totally disabled for years now |
Re: Static IP from .2 to .20?
Could you post the results of ifconfig and arp -a? I've never seen it take anywhere near that long if the device exists. You should see a ping response within a second.
Greg McKaskle |
Re: Static IP from .2 to .20?
Greg,
I have a question regarding mDNS and the LabVIEW dashboard. We're trying to send some data from the dash to the robot over a UDP connection. In the past, we've done this using the robot's static IP address and have had no issues. This year, we've not had much success unless we use a workaroung which isn't going to work at competitions. I'll apologize in advance for not being able to post code or look for minute details as I'm at home today and our team's computers are at the school. Here is what we've done: The main strategy is to use the part of the dashboard where it binds the smart dashboard to capture the IP address. In Loop 3 in the case structure where Bind Controls to Smart Dashboard.vi is located, we pull the robot IP address in the TRUE case and store it to a global variable. We use this global variable as the IP address in our UDP loop. Here's the issue: the global variable that is supposed to contain the IP address comes back as an empty string around 80% of the time. We've been working around the issue by figuring out the IP address manually, but that won't work for competitions. Any suggestions? |
Re: Static IP from .2 to .20?
No need to apologize.
The dashboard relies on the DS to learn what the robot IP address is. It seemed like a good idea to not have the DB and DS looking at different robots. The notifier is necessary because the binding otherwise won't return. Storing the value in a local or global in the top loop or the third loop is a fine way to notify the rest of the DB of the robot IP. So the way the IP sharing is supposed to work is for the robot IP and camera IP to be sent to the DB over TCP. The error handling for the DB TCP connection wasn't as good as it should have been, so I've seen some issues where the connection simply doesn't exist. The update last week corrected the known issues. PM me when you have access to the code, as I can tell you how to debug and improve it. Greg McKaskle |
Re: Static IP from .2 to .20?
Quote:
Code:
C:\Users\Arhowk>ifconfig |
Re: Static IP from .2 to .20?
It looks like this is connecting through your school's WiFi, and the school uses the same 10. address range.
Any reason why you aren't connecting directly to the robot DLink SSID 1684? |
Re: Static IP from .2 to .20?
Quote:
Won't be able to get data like that with the robot for a week or so. If it's any help, our rookie team's driver station (x86 compared to my x64, Windows 8 compared to my windows 7, decently different laptops) also has the same hangtime. |
Re: Static IP from .2 to .20?
Sorry, we have several DLink's left to test with after one got bagged with our robot.
Does your rookie team work in the same space as your team? Is it a common WiFi environment or a common school system that might utilize similar AP setups? It looks like you might be describing troubles only using the direct USB connection though. Do you have the same issues with USB, Ethernet and wireless? |
Re: Static IP from .2 to .20?
Quote:
Quote:
Quote:
|
Re: Static IP from .2 to .20?
Quote:
|
Re: Static IP from .2 to .20?
Oops. Yeah, I meant ipconfig, but auto-correct fixed it for me.
I was wondering if there were many interfaces up and whether the DNS server may be sent the .local name and be taking quite awhile to give up and revert to mDNS. I think the thing I'd do is to disable the wifi and see if the USB timing changes. If that helps, you at least know why it takes so long. I'm not sure how to get the .local to go to mDNS immediately. Greg McKaskle |
| All times are GMT -5. The time now is 01:43. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi