|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|
WiFi/Bridge/CRIO Boot Conflict
Sooooo. ever had one of those moments at competitions where you turn your robot on and it doesn't connect to the field control system?
I know why. This year's new D-Link Bridge boots up slower than the CRIO. The CRIO boots completely and then the Ethernet port is already configured. When the bridge then tries to connect to the CRIO and the wifi. It Can't. So I left the main robot power on and unplugged the power from the CRIO while the Bridge was still on. And the Bridge connected to the CRIO and WI-FI almost immediately. This is a real problem. Has anyone else experienced it and is there a way to fix it without just having a hard switch wired to the CRIO to make sure the bridge boots first. THANKS! John Fogarty |
|
#2
|
|||||
|
|||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
That is an interesting theory. Our robot never seemed to have that problem; our only FMS issue was that we had an outdated image on our RIO. Anyway, our dlink's slow boot time never seemed to effect connectivity.
|
|
#3
|
|||||
|
|||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
Ewwww, that would be a problem. Is that because the DAP-1522 is set to "Auto" mode instead of "AP"? "Auto" mode waits 30 seconds before it "boots" looking for a DHCP server (so it can swap itself to bridged if it can find one). That could be the source of the discrepancy here.
-Danny |
|
#4
|
||||
|
||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
Our 2011 robot works fine with the bridge booting up and communicating every time. Nice to know not to use auto-mode due to that delay timer.
|
|
#5
|
|
|
Re: WiFi/Bridge/CRIO Boot Conflict
Quote:
|
|
#6
|
|||||
|
|||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
With some robots there was a similar problem last year, too.
You can use the reset button on the cRIO itself to cycle it, rather than pulling power. |
|
#7
|
|||||
|
|||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
Quote:
FTP to the target, and find the following file in the root directory: ni-rt.ini In the file, you'll find a section called, "[TCP_Stack_Config]". Under that section, add the following token: [TCP_Stack_Config] Halt_On_Error=TRUE Yup, I know, it's poorly named, but for legacy reasons the name has lived on way past its deserved lifespan. Anyway, this will cause the cRIO to reboot up to 3 times looking for successful communication with a DHCP server. After 3 times, that's it, you must reboot the cRIO yourself (via power or reset button). Give it a shot? -Danny |
|
#8
|
|
Re: WiFi/Bridge/CRIO Boot Conflict
I'll make sure that this problem is well known at the palmetto regional this year. If the reset button solves the problem than we may save alot of time at the competitions.
Thanks! |
|
#9
|
||||
|
||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
This does not make sense to mew. The cRIO has no need of a DHCP server. The IP address is statically defined. There must be something else going on.
|
|
#10
|
|||||
|
|||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
Quote:
If you unplug the network connection from the cRIO, then reboot the cRIO, then after a couple minutes plug in the ethernet connection, can you talk to the cRIO? You should be able to ... -Danny |
|
#11
|
|||
|
|||
|
Re: WiFi/Bridge/CRIO Boot Conflict
We've been using the new robot radio in bridge mode all build season so that we have been using the same networking configuration (on both the robot and driver station) that we expect to compete with. The issue we have seen is that the new radio takes about 40s to bridge to another network after you apply power. We've been rebooting the cRIO from the driver station to avoid power cycling the robot and hence the radio. That's clearly not an option on the field, but it saves a lot of time in on the practice field.
We saw significant delays which I believe were bridging related at the week 0 event in Nashua, NH on Saturday as well. Noel |
|
#12
|
||||
|
||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
We've never had a problem this year, but then again we've been using AP mode.
I'm sure that the field personnel are aware of this problem, if it exists, and will know what to check/reboot if your robot doesn't connect. For a slightly off-topic question, am I right in saying that bridge mode connects to one wireless source and Access Point mode connects to many wireless sources? But the router will still communicate with a second wired source in bridge mode, like the camera, correct? |
|
#13
|
|||||
|
|||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
Quote:
Quote:
-Danny Last edited by Danny Diaz : 21-02-2011 at 01:55. |
|
#14
|
|||
|
|||
|
Re: WiFi/Bridge/CRIO Boot Conflict
Quote:
|
|
#15
|
|||||
|
|||||
|
Re: WiFi/Bridge/CRIO Boot Conflict
Quote:
-Danny |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|