[jasonbrooks]

Originally Posted by PhilBot

Hi

I've had several instances where our robot continues to run at the end of of Teleop.

It appears that the Teleop program is being killed before our program has a chance to receive or respond to the Disable command. So, if we are sending driving commands to the DC Motor controllers, they continue to run until the 2.5 Sec timeout shuts them down.

Has any one else seen this sort of thing?

We are uising Labview, and have quite a few motor controllers so the program may not be looping extemely quickly.

Also, we've had a couple of instances where the FCS loses connection with the Game Controllers (the FCS screen indicates that it is missing Joystick Messages) but in one instance the robot continued to drive forward, which implies that the last joystick command was being resent, despite the fact the the FCS knew it was gone. Seems like the FCS should have either stopped sending data (to cause the Robot to go offline), or it should have sent null joystick commands. As it was, the robot ran into the wall, and smoked a motor before we could shut down the FCS.

Phil.

This used to happen to us all the time with LabView. We had two main problems while using LabView:

1. The robot would never run properly when we were using two controllers. During "Hot Shot", if we were trying to move the robot while using our pitching-machine style shooter, and the shooter was already spinning, it would not stop spinning until the other controller stopped moving the robot, even if on controller one the spinner was stopped.
2. After each match, the program would keep running for a few more seconds. So, once again, in Hot Shot, we kept shooting into the offield goal even after the game was over which gave us some dirty looks from the refs

My recommendation would be to try robotC with a simple program and see if you get the error message again.

Let me know how it goes!