Chief Delphi
Page 2 of 3 < 1 2 3 >
Show 100 post(s) from this thread on one page

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   FIRST Tech Challenge (http://www.chiefdelphi.com/forums/forumdisplay.php?f=146)
-   -   [FTC]: 35's Drive problem (http://www.chiefdelphi.com/forums/showthread.php?t=70250)

Lowfategg 30-11-2008 17:16
Re: [FTC]: 35's Drive problem
 
Quote:
Originally Posted by gdo (Post 778190)
The NXT is faster, I think the lag has as much more to do with the bluetooth. I found that it was better to incorporate FEWER interface commands, where the code looks for the joystick commands, which definately has a slowing affect.

There are more factors, but the bluetooth speed is the biggest problem I think.

I have had very few problems with the bluetooth interface in RobotC, but I haven't been using the FTC Control station, but the included software in RobotC. It will be interesting to see what the robots will do at scrimages with the competition setup. (the only scrimage I went to, people used personal laptops and all used RobotC)
I can't see why it would be the blue tooth. They use blue tooth in a number of things (my Wii comes to mind), and they don't have laggy controls, it must be something in the code.

Monty Python 30-11-2008 21:39
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.

willson.thomas 01-12-2008 01:16
Re: [FTC]: 35's Drive problem
 
Quote:
Originally Posted by Monty Python (Post 778233)
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.
I would agree that it shouldn't be the bluetooth, unless it is the software implementation of it. I use a bluetooth mouse with my notebook and while hardcore gamers tell me there is some lag, I definitely haven't noticed it.

ttldomination 01-12-2008 09:14
Re: [FTC]: 35's Drive problem
 
Well...we're not exactly running mouse from this. Idk, let's wait for an reply from labview.

wilsonmw04 02-12-2008 19:08
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.

KayyPii 02-12-2008 22:57
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?

ttldomination 03-12-2008 09:10
Re: [FTC]: 35's Drive problem
 
How far do you want it to go? I doubt you'll have problems at competition.

KayyPii 03-12-2008 21:55
Re: [FTC]: 35's Drive problem
 
That's true

wilsonmw04 03-12-2008 22:04
Re: [FTC]: 35's Drive problem
 
Quote:
Originally Posted by ttldomination (Post 778981)
How far do you want it to go? I doubt you'll have problems at competition.
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.

ttldomination 04-12-2008 10:05
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.

wilsonmw04 04-12-2008 14:22
Re: [FTC]: 35's Drive problem
 
Quote:
Originally Posted by ttldomination (Post 779300)
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.
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.

Monty Python 04-12-2008 15:03
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.

ttldomination 04-12-2008 15:50
Re: [FTC]: 35's Drive problem
 
First regional is tomorrow? Well, be sure to take lots o' pics for me?

Monty Python 04-12-2008 16:06
Re: [FTC]: 35's Drive problem
 
I'll be driving, but I'll try to take a couple.

wilsonmw04 04-12-2008 21:45
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?


All times are GMT -5. The time now is 12:29.
Page 2 of 3 < 1 2 3 >
Show 100 post(s) from this thread on one page

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi