Bridge Configuration Utility Error

[matthewgkerr]

I have installed the FRC Bridge Configuration Utility on my brand new Windows 8 machine. When I start the application it opens an error dialog which says the following: "An error occured while initializing the computer network settings; The application must shut down"

I have a Windows 7 machine which looks like should work. But it would be fantastic if I can get it to work on my new machine. Or at least know if it doesn't work on Windows 8.

One thing I did see during the install (it might have been when i first ran the application) was that it required Java 1.6. I installed the latest version of Java (I think it was version 7; I installed both the 32bit and 64bit versions). So I got a bit further, but I still can't use the application. Please help.

[fjvillalpando]

Hello there,

We had the same problem, you can try by changing the compatibility settings of the application, right-click on the application, select Properties and then Compatibility Tab, we changed it to Windows 7 and also checked the "Run as administrator" box.

We hope it helps,

Regards,

Javier Villalpando
Programming and mechanical design mentor
ABTOMAT Team 3480
Leon, Mexico

[The Numenorean]

I had the same problem, im afraid I don't remember exactly how I got it to work in the end, but it IS possible to get it to work on win 8, so don't give up to easily. Changing the compatibility mode setting should help though.

[NLake]

I'm having an issue with our bridge.

After returning from our competition in March, we put our robot into storage.
Getting it out for club fair this year, I wasn't able to get the bridge configuration utility to work.

First, it told me I needed to install a newer version of Java than was on the machine the last time it was used (which is odd, because the machine hadn't connected to the Internet since before competition), which I wasn't able to do at work (no network access at the school, so I take the drive and dev station laptops home to update them).

I went home and updated the NI software, and while I was at it, updated from Windows 7 to 10. (This is on the 2GoPC which came with the KOP a couple of years ago.)

Now, when attempting to configure the bridge (after having updated Java and NI), it won't run. Not in compatibility mode; nothing. It keeps telling me there's a problem with network communication and it has to shut down.

I have a history of having received faulty radios from FIRST, but to have a radio fail after 2 years of sporadic use seems extreme. Does anyone have advice?

Thanks for your time, CD!

[Jonathan L.]

I am getting the same error: "An error occured while initializing the computer network settings; The application must shut down"

Note I'm not connected to the d-link while I'm testing. I am using a computer which has been upgraded from Windows 8 to Windows 10. I'm pretty sure the program worked before the computer was upgraded to Windows 10.

We still have Windows 7 computers available that will work.


Looking back at this tread posts 1, 2 and 3 are from 2013.

[timytamy]

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:

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.