Newsgroups: comp.robotics
Path: brunix!sgiblab!spool.mu.edu!howland.reston.ans.net!sol.ctr.columbia.edu!news.kei.com!ub!netfs.dnd.ca!dres.dnd.ca!news
From: sburton@stan.dres.dnd.ca (Stan Burton)
Subject: Re: 68HC11 Reset
Content-Type: text/plain; charset=iso-8859-1
Message-ID: <1994Feb9.154416.12431@dres.dnd.ca>
Sender: news@dres.dnd.ca
Nntp-Posting-Host: stan
Reply-To: sburton@dres.dnd.ca
Content-Transfer-Encoding: 8bit
Organization: Defence Research Establishment Suffield
X-Newssoftware: GRn 2.0j Jan 8, 1994
References:  <2j4krv$p3o@agora.rain.com>
Mime-Version: 1.0
Date: Wed, 9 Feb 1994 15:44:16 GMT
Lines: 17

In article <2j4krv$p3o@agora.rain.com> marvin@agora.rain.com (Marvin Green) writes:
[removed background info on HC11 reset and 34064 operation]
> When engaging a R/C servo with the BOTBoard, I found that as the servo
> motor kicks on, the 68HC11 would often reset itself.  It seems that the
> MC34064 would drop to a reset state when the R/C servo started to move.

If the power supply spikes caused by the servo are enough to trigger the
MC34064 then they may also be strong enough to disturb the processor,
memory or peripherals.  I don't think that the right answer is to find a
different reset chip.  I would isolate the servo power from the
processor power so the the spikes caused by the servo (and it does make
some good ones) don't have any effect on the processor.

--

Stan Burton (DND/CRAD/DRES/DTD/MSS/AGCG)                 sburton@dres.dnd.ca
(403) 544-4737     DRE Suffield, Box 4000, Medicine Hat, AB, Canada, T1A 8K6
