View Single Post
  #1   Spotlight this post!  
Unread 16-02-2014, 15:42
icecube45's Avatar
icecube45 icecube45 is online now
Drive|Programming|Captain
FRC #0114 (Eaglestrike)
Team Role: Driver
 
Join Date: Feb 2014
Rookie Year: 2013
Location: Los Altos
Posts: 30
icecube45 is a jewel in the roughicecube45 is a jewel in the roughicecube45 is a jewel in the roughicecube45 is a jewel in the rough
cRio Communication Errors

Hello,
starting about three days ago, after we finished wiring our robot, we encountered a communication error with our robot.

We can connect just fine, but after about 30 seconds of solid communication, the robot code light will start flashing, communications going in and out, until we eventually loose all communications, but are still connected to the dlink.

After about 15 minutes of waiting, the communications will come back, and the cycle will begin again.

What we have tried:
Reflashing the dlink
reflashing the cRio
swapping the crio
swapping the dlink
switched to barebones code
tried on another robot
tried other, non dlink routers
switched the dlink to a less populated wifi channel
setting up the dlink as a bridge to a router connected via lan to the DS.
swapped the power supply to the dlink
plugged the dlink into a wall socket
tried another driver station (went to a classmate, along with another laptop)
tried 5 ghz, get a watchdog error, which is caused by communication (acts the same exact way, and we killed the watchdog in code)




Essentially, we have no freaking idea what has gone wrong,


an interesting thing to note though, is that When tethered, we have no communication errors at all

We can't do everything tethered, and would love for any help you guys have.


-icecube45
team 114
Reply With Quote