Problems Configuring Radio

[iggy_gim]

Hey guys, sorry to dump more problems onto you, but yesterday our team was trying to configure our dlink radio for home use following the instructions on the FIRST Technical Resources. However it kept failing. We suspected that it might be our crappy Windows 8, so we tried it on Windows 7, still no luck.

We get no error except: Failed to change IP Address Check connection to Radio. Does anyone have any ideas as to how we can fix this issue?

[Tungrus]

Last year the config utility had to be run in Windows7 compatibility mode, not sure if this is fixed this year. See following steps to run in compatibility mode:




Tip from Microsoft:

You can also open the Program Compatibility troubleshooter by right-clicking a program's icon or shortcut and then clicking Troubleshoot compatibility.

To change compatibility settings manually
To change compatibility settings manually for a program, right-click the program icon, click Properties, and then click the Compatibility tab.

[iggy_gim]

So, even in Windows 7 we still have to run it in compatibility mode?

[Team118Joseph]

The issue could be the radio. Try a factory reset by holding the reset pin down for 10 seconds. Then try configuring the radio again. The configuration tool may fail the first two time (it always fails for us). Also make sure your computer is set to the correct ip.

[tr6scott]

We have successfully run the configuration on windows 7 x64 native without any issues this year. Multiple computers multiple times, we were beta. Just a data point.

[Alan Anderson]

The issue could be the radio...

I thought the "failure to change IP address" was talking about the address of the computer, not the router. It sounds like it could be an administration permission issue.

Or maybe there's another network adapter already configured with the address the tool wants to set the wired adapter to. Or perhaps something has set a secondary address on the network adapter, and that's keeping it from working with the configuration tool. It might help to go through and set every network adapter to DHCP, make sure there are no additional IP addresses set, then disable all of them except the one being used to connect to the router.

[Sparkyshires]

Hey guys, I'm getting a similar error. it makes it to the end and then sends a message:
"Bridge configuration failed: IP address not restored to DHCP
please ensure the bridge is connected to this computer and try again

I've gotten this same error message on three different D-Links(two Rev-B and one Rev-A), and two laptops (both Windows-7 64-bit). The d-link is most definitely connected to the computer. Also, when I followed the manual set-up instructions to finally get it working in this (http://www.chiefdelphi.com/forums/showthread.php?t=132337) thread (last post) it worked for one meeting :D then the next it didn't! I could ping the roboRIO, but the driver station wouldn't connect to it, and yes the Driver Station is v15.0. I've reset the bridge and tested it multiple times, turned off windows firewall (mcAfee isn't installed), turned off the wireless network adapter, and it still gives that same error when I try to image it. I've run it in compatibility mode also, and still the exact same error.

[MamaSpoldi]

I thought the "failure to change IP address" was talking about the address of the computer, not the router. It sounds like it could be an administration permission issue.

Or maybe there's another network adapter already configured with the address the tool wants to set the wired adapter to. Or perhaps something has set a secondary address on the network adapter, and that's keeping it from working with the configuration tool. It might help to go through and set every network adapter to DHCP, make sure there are no additional IP addresses set, then disable all of them except the one being used to connect to the router.

I agree that I thought the IP change was referring to the PC. Although the variations in the possible system configurations for this year's control system proved a bit daunting when we tried to get it all set up we did finally manage to get it working... consistently so far. The advice above to set all adapters to DHCP and then disable the ones not being used seems to be good advice in general for all stages of usage this year. I definitely would try that.

[Sparkyshires]

Just making sure, is there a difference between DHCP and "Set IP address automatically"?

[aryker]

Just making sure, is there a difference between DHCP and "Set IP address automatically"?

That is what DHCP does for you, so no. The "Set IP Automatically" is the option you want.

[Sparkyshires]

Okay. The bridge configuration utility still fails :/

[MamaSpoldi]

Just making sure, is there a difference between DHCP and "Set IP address automatically"?

If you select the check box next to "Set IP address automatically" and then click on the Advanced button it will show that you have DHCP enabled on that screen.

[RufflesRidge]

Okay. The bridge configuration utility still fails :/

There was a bug reported in Beta similar to what you described, but I haven't seen it in the kickoff release. Are you sure you are using the Kickoff version?

[MamaSpoldi]

Okay. The bridge configuration utility still fails :/

I know how frustrating this can be. We have had trouble with it in the past. I know you said that you followed all directions, but just to check... do you have the D-Link set to "AP 2.4GHz"? Did you try powering off and then resetting the bridge between attempts?

And you turned off (disabled) the wireless adapter while you were doing the Bridge Configuration, right? And you have no other devices plugged into the ethernet besides the bridge?

I know that they warn about firewall issues in association with many communication issues. Can you maybe disable your firewall completely and try it again?

[Sparkyshires]

There was a bug reported in Beta similar to what you described, but I haven't seen it in the kickoff release. Are you sure you are using the Kickoff version?

I believe so. Where is the kickoff configuration utility download link?

EDIT: nevermind, it worked when I went to the file location. I think when I installed it, I or it must have accidentally created a shortcut to the beta utility on the desktop, and I had been using that. It worked, thanks!

[Jared]

Our programming laptop has never worked properly with the radio configuration tool. Is there a guide to change the settings manually, like their has been in the past?

[Sparkyshires]

Our programming laptop has never worked properly with the radio configuration tool. Is there a guide to change the settings manually, like their has been in the past?

Yeah, check out my first post on the previous page, there's a link in there to a guy who wrote out a manual way of doing it. That worked fine for me, although as you can read it was a bit flaky. What error are you running into? I think every possible one has been posted on ChiefDelphi, each with their own fix.

[iggy_gim]

Thanks everyone for all of your help. To give you an update today (sorry I didn't respond sooner, our meeting was busy to say the least). Anyways...

Yeah, check out my first post on the previous page, there's a link in there to a guy who wrote out a manual way of doing it. That worked fine for me

I tried following those instructions and it did not work as we could not access the router from the internet browser via its IP address.

I know how frustrating this can be. We have had trouble with it in the past. I know you said that you followed all directions, but just to check... do you have the D-Link set to "AP 2.4GHz"? Did you try powering off and then resetting the bridge between attempts?

And you turned off (disabled) the wireless adapter while you were doing the Bridge Configuration, right? And you have no other devices plugged into the ethernet besides the bridge?

I know that they warn about firewall issues in association with many communication issues. Can you maybe disable your firewall completely and try it again?

Yes, yes, yes, yes. The firewall is down, everything was off. What we did find is that if we set the computer's IP address to match the "supposed"
IP address of the router, the config tool got to the second step of configuring the radio, but still failed (according to the program it could not find the router). Because the program could not find the router, neither could Google chrome and our computer is saying that the router doesn't have a correct IP address (as per troubleshooter), I think that the router's IP address is all coockoo for some reason, as in it isn't set to its default 192.168.0.50 (idk if that is correct IP, I'm working off of memory). Any ideas? Thank you so much again for all of you guys help with this frustrating issue.

[Sparkyshires]

Yes, yes, yes, yes. The firewall is down, everything was off. What we did find is that if we set the computer's IP address to match the "supposed"
IP address of the router, the config tool got to the second step of configuring the radio, but still failed (according to the program it could not find the router). Because the program could not find the router, neither could Google chrome and our computer is saying that the router doesn't have a correct IP address (as per troubleshooter), I think that the router's IP address is all coockoo for some reason, as in it isn't set to its default 192.168.0.50 (idk if that is correct IP, I'm working off of memory). Any ideas? Thank you so much again for all of you guys help with this frustrating issue.

Hmm well in my (limited) experience with these things, I've always been able to talk to the router following these steps:

1. Turn everything off and unplug everything, meaning also disconnect the roboRIO and anything else plugged into the radio.
2. Turn the router on, wait for it to boot then hold the reset button for like ten seconds
3. Turn your computer on.
4. Once you're booted and logged in, connect the computer and radio with an ethernet cord
5. Disable the wireless network connection on the computer, and set the wired network connection IP address to 192.168.0.40.
6. Open internet explorer and go to 192.168.0.50.

If that really doesn't work, there might be something wrong with your radio. Good luck!

[rich2202]

Yes, yes, yes, yes. The firewall is down, everything was off. What we did find is that if we set the computer's IP address to match the "supposed"
IP address of the router

"match" is not a precise word. The computer and router IP address need to be similar, but not the same.

Similar: Identical first 3 numbers, but different 4th number. Ideally less than 10 different from each other, and not spanning 127/128, less than 255, and greater than 0.

[iggy_gim]

Thanks for your response. Just a couple questions.

Similar: Identical first 3 numbers, but different 4th number. Ideally less than 10 different from each other, and not spanning 127/128, less than 255, and greater than 0.

Thank you for that. I am really not the one troubleshooting this problem, someone else is, I am just the liaison for Chief Delphi, so I don't know exactly if the person actually working on this problem set the IP addresses to the same address, she just told me that she "matched" them. Maybe that mean she set them to the same IP address or she set them correctly.

Turn everything off and unplug everything, meaning also disconnect the roboRIO and anything else plugged into the radio.

Was the roboRIO supposed to be connected to the router to begin with. We have just done it disconnected from the roboRIO.

Lastly, I noticed two things today. Firstly, in the initial dialog box of the utility, the Local Area Connection 3* option does not show up anymore (it did before). What does that mean? Secondly, I noticed in the Labview folder there are two configuration utilities one Java named FRC_Team_Radio_Kiosk and one normal application FRC Bridge Configuration Utility. We have been using the latter, is that the correct application?

Thanks again for all of your help, we have been struggling with this for a week now and it really is frustrating, yet I know that all problems have a solution!

[timytamy]

Thank you for that. I am really not the one troubleshooting this problem, someone else is, I am just the liaison for Chief Delphi, so I don't know exactly if the person actually working on this problem set the IP addresses to the same address, she just told me that she "matched" them. Maybe that mean she set them to the same IP address or she set them correctly.


Next time you follow through a procedure (like this one (http://www.chiefdelphi.com/forums/showpost.php?p=1425484&postcount=9)),could you post the output of "ipconfig" (when run from command line) each time you change IPs?


Was the roboRIO supposed to be connected to the router to begin with. We have just done it disconnected from the roboRIO.


We've also always done it disconnected. Theoretically everything should fix itself on reboot, but if you keep it disconnected then that's one potential problem you've eliminated. Also, if your imaging/installing firmware. I highly recommend you use the USB connection. It's much simpler and should work better.

Another quick test you can do is once you've followed the procedure to set up DHCP, connect a completely different computer up, run ipconfig, and check that the ip, subnet and gateway all match what you've set up. If they don't, then it's likely a problem with setting up the DLink (such as not saving or incorrect settings)


(snip)...We have been using the latter, is that the correct application?

TBH, I don't know. I've always set it up manually..

[iggy_gim]

BH, I don't know. I've always set it up manually..

I thought that the radio had to be set up via the utility because of the new control system. In any event, we will try your suggestions tomorrow and I will tell you how they went. Thanks for your help!

[timytamy]

I thought that the radio had to be set up via the utility because of the new control system.

Theoretically, it should be. However at the end of the day, it's just a network. We've actually run DHCP on the DLINK for the past few years with the cRIO. If your smart about your address ranges, it allows you to connect any laptop/computer up to the network and begining coding/driving without mucking around with other settings.

When you get to competition however, you are required to re-program the DLink like always (I'd expect). But this will be organised by the FTA/Event Staff so you don't have to worry too much. The utility that your given is a modified version of the one they use at events. There is the argument that you should use the utility to be as close to the event system as possible. But unless you're doing something quite complicated/heavy on bandwidth you won't notice any difference (we haven't). At least, that's what I'm infering from documentation and previous experience, someone who's worked on it could confirm/clarify.