|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: [FTC]: 35's Drive problem
Quote:
|
|
#2
|
|||
|
|||
|
Re: [FTC]: 35's Drive problem
Bluetooth is not the problem. My team used to use Labview and there was lag even when using a USB. Also, the bluetooth was not a problem at the scrimmage I attended. Redownload the last Labview update as I'm not sure if they posted a new update, they may have just edited an old one (although I'm not 100 percent positive, this is just what I remember reading is one of the links on chief delphi). Labview had a ton of lag for us and RobotC has almost none. I would suggest trying to run the sample joystick code for RobotC and seeing if you have lag.
|
|
#3
|
|||
|
|||
|
Re: [FTC]: 35's Drive problem
Quote:
|
|
#4
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
Well...we're not exactly running mouse from this. Idk, let's wait for an reply from labview.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [FTC]: Problem with two controller setup in Labview | wilsonmw04 | FIRST Tech Challenge | 2 | 11-11-2008 19:58 |
| [FTC]: First problem with FTC and LabView.....? | PhilBot | FIRST Tech Challenge | 5 | 07-11-2008 10:36 |
| [FTC]: Team 35's Servo Test | wilsonmw04 | FIRST Tech Challenge | 11 | 03-11-2008 21:47 |
| [FTC]: FTC Servo-Motor Problem with Labview | dnhansen | FIRST Tech Challenge | 1 | 26-10-2008 00:43 |
| pic: FTC 35's prototype for 2007 | wilsonmw04 | Extra Discussion | 2 | 08-11-2007 18:38 |