1 Attachment(s)
destroying my last pic? driving a miniature motor
Hi everyone,
Please help me if you can....I don't want to destroy my last pic....
I'll get right on topic:
I had partial success driving a 4mm motor directly from the 4 pwms of my 16f690. I was using pulse steering to output hpwm signal on 4 pins. Testing this, I realized that this would not allow me enough current on the motor i am using.
Here's what I did initially:
I chose 250 ohm resistors for each pwm output because 5v/250ohm is 20 mA the max a pic can source or sink. After the resistor these lines converged going to the positive terminal of the motor. Because I gave moter 4 pwm signals, the resistance to 5v(supplied by PWM) was actually 250/4=62.5ohm.
My motor has 9.6ohm internal resistance
62.5ohm divider: 9.6/9.6+62.5ohm x 5V==>motor was only getting .666v….
Current through the motor 5v/72.1ohm = 69.3mA
This was not enough to get it spinning nicely...
Here's where I destroyed 2 pics:
I quickly tried hooking up one of the 4 pwm signals through a 2n2222 to
boost the current. Although i thought i had enough protection using diodes when I ran the program, not much happened... Also some sensors on i2c and power lines didn't blink as they normally do at startup. Only removing the pic 16f690 got those sensors blinking again. After adding some more diodes, safer resistor values I tried again with another pic....Same result... Unfortunately I can not reproduce the exact schematics as it was 5am and I was tired a little impatient and yes...drinking...;)
I think I may have left the other pwm pins floating, or possibly switched the collector and emitter. All I know is that I didn't even get to see smoke...
Can anyone advise me on a lowest partnumber/smallest parts solution that would do the beforementioned. HERE IS WHAT I HAVE IN MIND...
IVEX WinDraft and/or WinBoard
Quote:
Originally Posted by
Darrel Taylor
I guess I forgot to answer that part.
Or maybe I was unconsciously avoiding it, since the program I use is a constant source of mental anguish.
I use IVEX WinDraft/WinBoard.
Ivex went out of business a couple years ago, and now there's no one to fix all the bug's.
Which is probably why they went out of business in the first place. (there's a lot of bug's).
And when the company closed, so did it's online Auto-Router server.
So now everything has to be routed manually. And of course that's hard to do because of the Bug's.
The last board I did, ... 18F6720, 10 other chips, 101 resistors,35 capacitors, etc. took almost 2 months to route manually.
I've got to find another program. And PCB123 just doesn't do it for me. :o
<br>
I use IVEX WinDraft and WinBoard--and PentaLogix ViewMasterEZ for post-editing the Gerbers. Never much anguish, mental or otherwise. My last upgrade was to 3.12 on WinDraft and 2.26 on WinBoard.
I rarely have problems with WinDraft/WinBoard. Which bugs are "bugging" you? The only chronic, serious difficulty I've encountered is laying in copper zones (such as ground or power planes) with WinBoard, but I started doing that with ViewMasterEZ.
On routing, I don't know what to say--I learned PCB layout before CAD, when it was done on a drafting table!--so I find "manual" routing with WinBoard is a breeze (I never used their auto-routing service). As you've probably already discovered, the first secret of easy routing is starting with the right component layout--and that's more nearly art than science!
But if I can help you (or anyone) out with WinDraft and/or WinBoard problems, let me know. Fundamentally, they are good, powerful products and, since the company is gone, now very accessible.
IVEX was around for over a decade (that's a long time for a small company in a technology field) and did not fail because of a "buggy" product. While in business, they constantly improved and updated their offerings and were even distributed by NTE. They were, I believe, "caught in the middle" between the low end, inexpensive (or free) manufacturer-specific products (PCB123 is an example) and the high end (ORCAD). The founder decided to shut down and move on. I don't agree with how he did it, but I understand the why. And there are still a lot of IVEX users out here.