Help With cRIO not staying connected

[Statsman]

My team is having a problem with stayin connected to the cRIO after attempting to reimage and send robot code to the robot.

The robot was running fine on, we even were able to allow some of the fresheman students on teh team time to drive the robot. After lunch staurday afternoon we began to have have connectivity issues with the robot. We have replaced almost every component ralated to the control system starting with the cRIO. Nothing has corrected the issue. We have spent a week on this issue and are running out of time.

We tried the following to isolate the problem:

-Swapped out cRIO, d-link, digital side car.

-Re-imaged the cRIO, reset d-link to factory settings and reconfigured it according to the manual.

-Checked wiring

-Tried connecting via ethernet and wirelessly.

-Reset computer and robot multiple times.

Warning <Code> 44002 occurred at Ping Results:  link-bad,  DS radio(.4)-GOOD,  robot radio(.1)-bad,  cRIO(.2)-bad,  FMS-bad Driver Station

<time>1/31/2014 7:13:46 PM<unique#>165

FRC:  Driver Station ping status has changed.

Warning <Code> 44004 occurred at Driver Station

<time>1/31/2014 7:13:45 PM<unique#>164

FRC:  The Driver Station has lost communication with the robot.

Warning <Code> 44004 occurred at Driver Station

<time>1/31/2014 7:13:43 PM<unique#>163

FRC:  The Driver Station has lost communication with the robot.

Warning <Code> 44004 occurred at Driver Station

<time>1/31/2014 7:13:40 PM<unique#>162

FRC:  The Driver Station has lost communication with the robot.

Warning <Code> 44004 occurred at Driver Station

<time>1/31/2014 7:13:37 PM<unique#>161

FRC:  The Driver Station has lost communication with the robot.

Warning <Code> 44004 occurred at Driver Station

<time>1/31/2014 7:13:34 PM<unique#>160

FRC:  The Driver Station has lost communication with the robot.

Warning <Code> 44003 occurred at Driver Station

<time>1/31/2014 7:13:31 PM<unique#>159

FRC:  No robot code is currently running.

Warning <Code> 44004 occurred at Driver Station

<time>1/31/2014 7:13:31 PM<unique#>158

FRC:  The Driver Station has lost communication with the robot.

Warning <Code> 44004 occurred at Driver Station

<time>1/31/2014 7:13:27 PM<unique#>157

[sciencewhiz]

Please post a copy of a driver station log that shows the problem. See http://wpilib.screenstepslive.com/s/3120/m/8559/l/97119-driver-station-log-file-viewer

[Kevin_F]

I agree, a copy of the driver station log would be helpful. What we will be looking at there are the network diagnostics as well as CPU %.  It is a very common mistake in real time programming to add some code that runs a loop with no delay and causes the CPU to go to 100%.  The network communications code is a lower priority than user code so this can cause communication with the cRIO to drop off.

I would be very surprised if this were an issue related to hardware (more than just a loose wire in a power connector or something).  Are you running the default code on the robot? If not, do you have this problem with the default code?  Do you have this problem if you wire the driver station to the robot instead of using wireless?

[Team4457]

We were having a simmilar problem. Is your team using the 12V-24V to 5V DC converter that was included in your team's KOP? That was our problem. Might not be yours. (This is what it looks like: http://www.chiefdelphi.com/forums/attachment.php?attachmentid=9622&d=1294671172)

[Kevin_F]

I have seen issues where having the converter right next to the wireless radio was causing enough noise to create issues. Is that the problem you were having?