Herbert Graf wrote:
>
> That's the plan, I'm actually going to do three channels and for simplicity
> I plan to use a seperate PIC for each channel with the same basic code (the
> differences in code will be due to the complexity of the control needed (ie.
> some will have position feedback, others won't) and the motor being driven
> (using a stepper on one channel and DC motors on the other two)). TTYL

Hi Herbert, first, i'm with you on the 16F84 issue,
I have hundreds of them and use them for anything
I want to whip up quick, whether "too simple" for
a 16F84 or "too complex" for a 16F84. The fact that
I have the chips, the boards, and many code projects
with register setups completed makes it easier to use
the chips you always use. You don't have to explain
WHY you're using a 16F84. :o)

Second, I can't help you directly with the gasoline
powered model car, apart from a basic suggestion.
My friend had a small-scale RC car using a gas motor,
it was about 18" long and did 40mph (real mph) and
was rather scary. My suggestion would be to take
care designing the throttle and brake systems to
be fail safe, so in the event of ANY failure the
throttle closes and the brakes are ON. Having seen my
friends car get out of RC range and crash into things
fast enough to break a human leg and destroy the
car, this is pretty important...

Maybe you could send a "good" code constantly to the
throttle and brakes, and the moment this code fails
the onboard PIC (watchdog?) etc goes into "safe"
mode. It's surprising how often an RC vehicle gets
bad info or loss of info from the controller. :o)
-Roman

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu