|
Re: Team Update #18
Folks,
If I were to carefully read this entire thread, instead of only quickly scanning the last 100 or so posts, what useful information/conclusions would I acquire?
I have gathered that the tower targets are close to FUBAR status and many mini-bot designs are consequently pseudo-randomly finding themselves up the proverbial creek. It that all we have here?
My goodness, does it take 200+ posts of grouching at each other, and at FIRST, to convey that clearly?
I know everyone is tired, but this could be a fun topic.
Who has tested some work-arounds and can reports their results to teams that need to modify their mini-bots???? Is slower better? Would putting a broad squishy nose on a mini-bot help? Would leaving the mini-bot motors energized an extra few fractions of a second after target-contact help? Anything else?
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|