[FTC]: Robots running on at end of Teleop., and strange FCS Joystick behavior.

[dickswan]

Originally Posted by PhilBot

Hi
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?

This was how the "day one" design for LabVIEW (and ROBOTC) work. And, AFAIK it is still the current implementation. ROBOTC maintains a map of which HiTechnic motor controllers are equipped and as part of the "program has ended" code stops them. LabVIEW does not keep such a map and relies on the 2.5 (or is it 2.0?) second watchdog timer in the motor controller to shut down. This occurs at the end of both autonomous and teleop.

I always thought that the LabVIEW implementation was unfair as it extra couple of seconds of motor movement might potentially allow a scoring activity to complete.