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

[alphadog0309]

This tells me that FIRST should create a "Kill at 1:57:050" VI for teams to put into their code as it is obviously a big problem. Or they should out right fix the issue and do this the correct way....

[PhilBot]

Originally Posted by alphadog0309

This tells me that FIRST should create a "Kill at 1:57:050" VI for teams to put into their code as it is obviously a big problem. Or they should out right fix the issue and do this the correct way....

This assumes that there isn't a temporary loss of communications during the match that would cause the timer to reset.....

The timer has to start when the robot is enabled... for the first time..

[alphadog0309]

this is true... is this a limitation within LabVIEW or just in the particular way the HiTechnic motor controllers are configured to run in LabVIEW?

[PhilBot]

Originally Posted by alphadog0309

this is true... is this a limitation within LabVIEW or just in the particular way the HiTechnic motor controllers are configured to run in LabVIEW?

Not sure exactly which "this" you are referring to, but if it's the run-on problem, I think it's a combination FCS timing, the labview template, and how the programmer writes their code.

This year's LabVIEW template used button events, rather than button states, so there is not a lot of motor control code running at any time, so the program is looping pretty fast, and can shut down the motors in response to a disable command quite quickly.

If the programmer has added a bunch of loops that read buttons and control servos (sending commands all the time) the drive loop gets slowed down to the point where it sometimes doesn't see the disable command before the FCS actually kills the program. In this instance, the Motor Controller keeps running the last issued command until it times out 2.5 seconds later.

I think a slightly longer delay between disable and kill in the FCS would solve this problem.

[maths222]

Just a note. RobotC does not have this issue. I have not looked at the source of "JoystickDriver.c," but I will do so and post my findings here (Hopefully teams will be able to apply this to Labview. I would, except that I only know RobotC).