Quote:
Originally Posted by Richard
I'm not following your reasoning there.
|
I figured I wasn't very clear.
I like some prebuilt solutions--Victors, PWM cables, the RC/OI, and the rest of the control system comes to mind. However, I like building my own devices for more than one reason. I like building my own devices because there is a higher sense of accomplishment--I built that vs. I bought that. Second, I learn a lot when I make these devices. I don't want a "black box" on the robot that I don't know even the slightest of its internals--NO! I want to know what goes on inside that box. And, since I think a PIC would be useful here, and our controller is PIC based, it might do me some good to get my feet wet with PIC programming. So I see it more beneficial to "roll my own" hardware solution on this.
Plus, "rolling your own" is just so much cooler.
Realistically, will I use something like this during build season? Probably not. What will I probably end up doing? hooking up my lappy to the dashboard port and logging on PWMs 7ish - 12. (BTW, are 13-16 still transmitted through the dashboard port even if I don't generate their signal from code? Are they even transmitted at all?)
Quote:
Originally Posted by Richard
What is it about pre-built solutions that you don't like, and why wouldn't you use them on an FRC robot? Interpreting your statement above literally, I guess you'd buy raw stock and make your own screws? [EDIT: of course that's rhetorical. I know very well that you are part of a great team that would not let you waste time making screws. ]
|
Can you program a screw to write to an SD card?
Also, me, make a screw? I'd probably not only thread it the wrong direction, but I'd destroy 3-4 tools in the process, along with removing some fingers...never EVER let the programmer touch the machines...
So why don't I like prebuilt solutions? Because homebrewn is so much sweeter!
(hey, I'm a dreamer

)
JBot