Quote:
|
Originally Posted by Workaphobia
I'm a bit embarrassed to post this without extensively searching and researching the matter, but I'm low on time and the next couple of days are critical in my (rookie) team's design stage.
I'm the lead programmer. I essentially gave up on trying to comprehend all the drafts and discussion regarding the arm mechanism for our robot, because it kept changing so many times and we didn't seem to be getting anywhere. I'm now fully willing to butt out and let my teammates commit to whichever idea they will, but I'm wondering how critical it is that I tell them early on exactly what sensors I'll need and where. Is a potentiometer something that can't easily be added to an arm after it is already built? Does a gyro need a special mounting place reserved in the chassis? What if in two weeks I suddenly realize that my job would be vastly simplified if I only had an extra input device somewhere - am I doomed if I don't have the foresight to bring it up now?
I was thinking of at least a few touch sensors for collision and limit switches wherever there are moving parts. Is it worth it to add a potentiometer so I can also get the angle of a variable arm, or is that not such a great idea for a rookie team?
I'll admit that I haven't been as active in reading all of the manuals and white pages as I would have liked, so if you just want to throw me a link or two, I'll understand.
Thanks in advance.
|
It really sucks when this happens. You have at least two options that come to mind. Most importantly, you need a systems person(s) who can see the "big picture". This person(s) is responsible for making sure things like sensor mounts are in the design before the mechanical design team makes some assumption that will prevent you from mounting your sensor on the finished 'bot. If you can't make this happen, you gotta get in there and make people listen to you, so you'll get what you need. Sometimes engineering is a contact sport <grin>.
-Kevin