[FTC]: NXT control delay

[Dkt01]

Originally Posted by PhilBot

This is a hugely open-eneded question.

Yes... please provide more information.

eg:
Programming Language,
Connection method (usb/samantha/bluetooth),
Teleop code sample, (could be any number of bugs)

Sorry about that, I was hoping it was some common issue.
We're using LabView.
We're downloading code via bluetooth, but running everything via the Samantha and the FCS.

A correction on the error stuff: there is still a half-second delay, but I was able to fix the E-Stop delay (now the motors don't run for several seconds after the E-Stop command). I did this by making the teleop a loop that continues while the robot is in teleop and there hasn't been a communication error (used the block that checks time between packets). I then used a sequence to force all motors to brake when teleop is ended or a connection error occurs. This seems to fix the danger issue, but if there is a connection pause in competition, this code would effectively disable the robot for the remainder of the match. If you have any suggestions, they'd be appreciated.

Like I said, our teleop code is basically just a loop that checks for new packets, then we made a VI to output a cluster of named axes and buttons. We then unbundle the cluster and use different buttons and axes to control the two drive motors (we made our own tank drive vi for programming practice, should we use the supplied vi instead?), a conveyor motor, a scissor lift motor, and a few servos.

Again, if I left out some important information, please let me know.