|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||||
|
|||||
|
Re: [FTC]: 35's Drive problem
Quote:
|
|
#17
|
|||
|
|||
|
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.
|
|
#18
|
|||
|
|||
|
Re: [FTC]: 35's Drive problem
Quote:
|
|
#19
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
Well...we're not exactly running mouse from this. Idk, let's wait for an reply from labview.
|
|
#20
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
A quick update:
We put at deadband (+/-10) on the drive sticks and it has mitigated the problem. The underlying lag is still there, however. I'm sending our code to NI tomorrow. I'll keep you posted. |
|
#21
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
I should really try the deadband thing.
By the way, anyone has any idea how far bluetooth signal goes? |
|
#22
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
How far do you want it to go? I doubt you'll have problems at competition.
|
|
#23
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
That's true
|
|
#24
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
No one has been to a competition yet, so who knows what's going to happen. I see this as a quality control issue. If there is something slightly off with LabVIEW and the FTC hardware, I'd rather bring it to someones attention now and eliminate future problems. If this is just a coding error on our part, no harm no foul and my team and I learned something to boot.
|
|
#25
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
Well, there have been plenty of scrimmages. So, I'm sure if there were range problems at the scrimmages, then they would have been brought up.
|
|
#26
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
Did those scrimmages use the regulation field control system? I have a feeling that we are going to see some interesting bugs tomorrow in U-Hall.
|
|
#27
|
|||
|
|||
|
Re: [FTC]: 35's Drive problem
I attended a scrimmage where they used the regulation stuff, it was run by the NJ FTC people. There were very few problems and things went far smoother then I expected.
|
|
#28
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
First regional is tomorrow? Well, be sure to take lots o' pics for me?
|
|
#29
|
|||
|
|||
|
Re: [FTC]: 35's Drive problem
I'll be driving, but I'll try to take a couple.
|
|
#30
|
||||
|
||||
|
Re: [FTC]: 35's Drive problem
Update: While i was having my students do some commenting on the code before we sent it to NI, we noticed something interesting: we has 4 motor controller VI's where there should have been two. When we removed the extra two, the lag disappeared. We live and learn don't we?
|
![]() |
| 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 |