Go to Post Team spirit is not all about the tools/noise makers. The Tigertrons didn't have any sort of noise makers. Consider other aspects of the award by making signs, mascots, cheers, and how you interact with other teams. - team222badbrad [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
View Poll Results: Do you ever lose control of your robot?
Never- our controls are always 100% with no sluggishness nor dropouts 26 37.14%
we started paying careful attention to radio placement and never had another problem 17 24.29%
Yes we sometimes have sluggishness and dropouts: We always just blame it on our software. 26 37.14%
We thought sluggishness was a requirement listed in the rule book 9 12.86%
Multiple Choice Poll. Voters: 70. You may not vote on this poll

 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #13   Spotlight this post!  
Unread 15-03-2011, 14:48
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Robots not under driver control- does it happen- do you determine why?

At a pre-ship scrimmage, our robot would occasionally start spinning in circles or take off at high speed in reverse. This would happen with nobody touching the driver joysticks. The program was definitely using only those joysticks to control the drive motors. Some of the team believed it was a communication issue, but I couldn't see any evidence of that kind of problem.

It took us most of the day to track down a bug in our rate limiting code. It was intended to keep the robot from accelerating backwards quickly so a chain tensioner wouldn't be overstressed. The bug was being triggering whenever a joystick went just barely outside the deadband in reverse. We spent a few minutes puzzling over the code, first trying to figure out how it was broken, then trying to figure out how we had intended for it to work in the first place. Finally we just threw it out and rewrote what it should have been originally.
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 13:19.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


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