View Single Post
  #19   Spotlight this post!  
Unread 17-11-2004, 16:21
SpaceOsc's Avatar
SpaceOsc SpaceOsc is offline
16 Years of FIRST!
AKA: Oscar Vasquez
FRC #4501 (Humans)
Team Role: Coach
 
Join Date: Feb 2002
Rookie Year: 2001
Location: Culver City, CA
Posts: 441
SpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant futureSpaceOsc has a brilliant future
Send a message via AIM to SpaceOsc Send a message via Yahoo to SpaceOsc
Re: Spikes

Quote:
Originally Posted by Andy A.
Recaliberting only takes 20 seconds, it seems easy enough to me, or am I forgetting something that makes it more complicated? It's one more thing to remember, but even forgetting wouldn't be catastophic. Or would it? I should preface this by saying that I've never really used a bot that had a great deal of autonoums programming going on, so I'm finding my self very much in the dark on an issue I thought I understood.



How is calibrating with a one joystick controller any diffrent then with a 2 stick system? It still seems to yields the same benifits, or am I missing something, again? I understand the point that sometimes the joystick and motor output arn't coupled and there is no benifit to calibrateing the victors then. But I thought that even in a one stick drive, the two still were coupled even though it was fed through software.




Well. You are right. I hadn't really considered that it would impair autonomous control that much, since I had just assumed that the program would be reading some sort of sensor feedback and make up the speed outputs on the fly. In that situation, it wouldn't matter what the victor calibration is, correct? Different calibrations are only an issue if the victors are being fed the numbers right from the controllers memory, correct?

Is there anyway that you could calibrate a victor, and have the program 'listen' in so that it could too could be calibrated and remember how the victor is scaling the input, and then use that its (the program) self? Would knowing exactly how much the victor is scaling the numbers help autonomous programming at all? I don't think I'm making my self very clear with this, but does anyone get it?

So, I spoke to soon. There are reasons not to calibrate. Don't I feel sheepish?

-Andy A.
I dont fully Comprehend why victor calibration would damage a working dead reckoning program. as in a previous post about saving the day with a paper clip. our programmers were having huge trouble just going foward straight, so they put in number that after trail in error comphensated for the issue. then i told them to stand back and give me 5 minutes (its amazing how hard it is to get a simple minute or two to fix a problem like this from an active pit team) and i calibrated, then i told them it should be fixed and discarded all the values for comphensation and went with the default numbers for neutral and full speed and half speed, as they were needed

The original program used these standard values for neutral and full speed but then they didnt work because of the calibration offset that i shoulda detected and fixed earlier in the season. so i suppose when a team isnt using sensor to drive in auton it would use a series of standard numbers for neutral and any other speeed it desired. if the victors are calibrated to begin with at the start of the season and someone actively takes care of that issue threw out the season ( maybe the pilots) then u can have your cake and eat it tooo, calibrated victors and a working auton.

-Osc-
__________________

2014-2017: Team 4501 Coach/Lead Mentor
2002-2011: Team 702, Mentor
2001-2002: Team 702 Captain