Go to Post Also, I'm tired of the "FIRST is a simulation of the real world"-- it isn't. If the real world was like FIRST, there wouldn't be any need for this organization. - cadandcookies [more]
Home
Go Back   Chief Delphi > Technical > Control System
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 26-01-2016, 15:04
coach_zac coach_zac is offline
Registered User
FRC #5104 (Breakerbots)
Team Role: Mentor
 
Join Date: Jan 2016
Rookie Year: 2014
Location: California
Posts: 1
coach_zac is an unknown quantity at this point
Re: Bridge configuration failed on OM5P-AN radio

Our team worked for several hours to use the Radio Configuration Utility last night and I thought I'd share our solution in case it helps other teams.

When we attempted the steps from the FRC documentation,
screenstepslive.com, we ran into the same problems described in this thread.

Our team member, Henry, discovered the solution which turned out to be two problems. The first is running the configuration tool as Admin. The second is properly disabling the wifi interface.

First, in order to conform to best security practices we have our driver station laptop set up with a admin account and an underprivileged user account that has the FRC software loaded onto it. However, the configuration utility must run as admin in order to change IP addresses. So we had to right click on the application and select "Run as administrator" when we launched the Radio Configuration Utility.

Second, we were getting the errors everyone else is talking about on this page that Henry discovered were caused by the wifi interface not being disabled properly. What makes this tricky is that the graphical icons in in the Windows 10 control panel are NOT intuitively clear.

The first preliminary step in the link above states, "Disable WiFi connections on your computer, as it may prevent the configuration utility from properly communicating with the bridge." So, in the image below you would think the big red "X" next to the Bluetooth interface would mean that it is disabled. BUT THE RED "X" DOES NOT MEAN THE INTERFACE IS DISABLED.



In order for the interface to be disabled it has to be "greyed out" like you see the Wi-Fi interface in the image above after we solved the problem.

In order to get more clarity I think the command prompt is much clearer. Open a command prompt window and type
Code:
netsh interface show interface
and you will get a very clear report on the status each interface. The image below shows the Wi-Fi interface in its three possible states. You must be in 'Admin State Disabled' for the configuration utility to work.



So....in order to get to this state use the Windows GUI to start at the control panel and follow this link chain: Control Panel ->Network and Sharing Center -> Network Connections. Then right click on the Wi-Fi interface and make sure you select "Disable". You can run the command prompt again to confirm the correct state.

After these steps we were able to upload the radio firmware and continue our build.

Good luck out there this year. I'm really looking forward to watching teams play Stronghold. This is gonna be great!
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 22:00.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


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