View Single Post
  #6   Spotlight this post!  
Unread 13-11-2015, 19:19
timytamy's Avatar
timytamy timytamy is offline
Registered User
AKA: Tim
FRC #3132 (The Thunder Down Under)
Team Role: Electrical
 
Join Date: Nov 2009
Rookie Year: 2010
Location: Australia
Posts: 293
timytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant futuretimytamy has a brilliant future
Re: Bridge Configuration Utility Error

Every time I've tried to use the imaging utility, I've had similar errors. We got around it by manually configuring everything:

The basic procedure we've followed and have (so far) not had any problems with.

1) Start with a completely clean/reset router. (ie Do a reset using a paperclip into the button near the power connector), and plug in via Ethernet.
2) Set computer IP to 192.168.0.40*
3) Using a browser, log into DLink (192.168.0.50). Go to network settings and change IP to 10.TE.AM.1
4) Set computer DLink IP to 10.TE.AM.40*. After saving, the DLink will log you out.
5) Log back into DLink, go to advanced settings -> DHCP settings. Set the IP range to be 10.TE.AM.100 - 199*, netmask 255.255.255.0, default gateway 10.TE.AM.1
6) Go back to wireless setup (ensure you go to manual, not automatic) and set the SSID to TEAM*, etc.
7) After you disconnect your computer, make sure you go change the Ethernet driver back to DHCP

Hopefully that will work for you.

* all these need to be in a specific range to work, and can take on other values. I just picked a number that I know works.

As general info, a big thing to watch out for is a conflict between static and DHCP IP addresses. If, on one network, you have the DLink giving out ips in the range of 10.TE.AM.100-199, you CAN NOT set a static IP on your computer in that range (so 10.TE.AM.123 would be illegal) however, IPs out of that range (and on the same subnet) are allowed (for example, the cRIO at 10.TE.AM.2 would function fine with a DHCP server giving out 10.TE.AM.100-199)

Secondly, do all this with the roboRIO off. From the roboRIO manual:
Quote:
The first time you power up the chassis, it attempts to initiate a DHCP network connection. If the chassis is unable to initiate a DHCP connection, it connects to the network with a link-local IP address with the form 169.254.x.x .
I'm not sure if the roboRIO keeps the IP, or for how many power cycles. Nonetheless I've made sure that I only power on a roboRIO with a network which has DHCP running, and haven't had any problems.
__________________
Tim W
FIRST® Team 3132 - The Thunder Down Under
Sydney, Australia
Website | Facebook | Youtube
Reply With Quote