View Single Post
  #10   Spotlight this post!  
Unread 03-04-2016, 08:29
rich2202 rich2202 is offline
Registered User
FRC #2202 (BEAST Robotics)
Team Role: Mentor
 
Join Date: Jan 2012
Rookie Year: 2012
Location: Wisconsin
Posts: 1,240
rich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond repute
Re: Robot Communication Lost for odd reason

If your RoboRio wiring was wrong, then check your Radio wiring. It should be plugged in to the 12v2A socket, and nothing else on the other 12v2A connection.

If launching the catapult causes the robot to crash, then that is where I would start to look for code problems.

If it works when deployed, but not when rebooting, then look for:
1) access to devices that may not be there.
2) access to devices that may not have yet been initialized.
3) access to variables/network tables/etc that may not yet been initialized.

What sometimes causes the "works when deployed, but not when rebooting" (or some other similar type combination) is that you are referencing a variable with an undefined value. Sometimes you are lucky, and sometimes you are not. On reboot, the memory addresses are usually in a default state that doesn't seem to work for you. On Redeploy, the deploy process may leave memory in a state that just happens to work for you.

Something as simple as a while loop conditioned on a new variable that is not first used until inside the while loop.

Last edited by rich2202 : 03-04-2016 at 08:33.
Reply With Quote