View Single Post
  #1   Spotlight this post!  
Unread 30-11-2008, 17:16
Lowfategg's Avatar
Lowfategg Lowfategg is offline
Building cars now....
AKA: Tyler Moser
FRC #2016 (Mighty Monkey Wrenches)
Team Role: Mentor
 
Join Date: Dec 2007
Rookie Year: 2005
Location: Bridgewater, NJ
Posts: 471
Lowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond reputeLowfategg has a reputation beyond repute
Send a message via AIM to Lowfategg
Re: [FTC]: 35's Drive problem

Quote:
Originally Posted by gdo View Post
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.
__________________
Mechanical Engineering Student at WPI.

Mightly Monkey Wrenches FRC #2016 - 2010-12 (Mentor)

Past: FTC #74, FVC #3179, FVC #73, FRC #303, FRC #2753
Reply With Quote