Problem with watchdog and movement

[Ted3299]

Hey there, this is my first time using this site, its a little long, and I'm not really working on the programing so please bear with me.

My problem is that we have been using our robot the past couple of days perfectly. We attached a mechanism to lift ourself's and it worked great, the only problem being it was too slow so we decided to change the values on the system to pump a little more votage to those motors to get it to run faster. In the end, all we did on LabView was change a couple of values to get more voltage to it.

We removed the lifter to work on it a little more to make sure it will work proficiently. After removing it, we uploaded the code to the C-RIO and called it a night, without testing it agian.

Problem-
Today, we booted up the robot, got it all set to go. First thing I noticed when I pressed enable was that it said "Watchdog Not Fed" and then quickly switched to "Teleoporated Enabled". I then pressed forward on the joysticks. The robot moved approximately 6 in., stoped and lost communication.

I tried it agian after I got the ok on everything and tried it agian, same result. We then rebooted the router, computer, robot, robot/computer to no result.

After a few of the reboots, I started noticing the communication going in and out every half second or so. and the only error message I recieve on the Diagnostics Tab is "Watchdog expiration: System 1,3,4,5,6,7,8 (commas meaning different messages) User 1,2"

Possible help for solution-
UPDATED- I think I've narrowed it down to the wiring getting jolted when it hits something to hard or starts too fast.

(MOVE TOPIC PLEASE)

[Alan Anderson]

Originally Posted by Ted3299

I then pressed forward on the joysticks. The robot moved approximately 6 in., stoped and lost communication.

What's your battery voltage?

[NullEntity]

I remember having to reboot the cRIO to fix this problem once.