the easy way out ...
Slow speed Software PWM
http://www.pbpgroup.com/modules/wfse...hp?articleid=6
Set the dutycycle to 50%
Then change the frequency at will.
<br>
the easy way out ...
Slow speed Software PWM
http://www.pbpgroup.com/modules/wfse...hp?articleid=6
Set the dutycycle to 50%
Then change the frequency at will.
<br>
DT
Thanks! now to go read and understand it. Really appreciate the replies.
Where do you come up with your answers skimask?
8-Ball?
Dart board?
Of course you can run it on a 12F675.
Just comment out the wsave1 wsave2 and wsave3 variables, since the 12F675 doesn't have GP RAM in those banks.
<br>
DT
Both of them...I assign points to each answer, then take the average point out of 7 tries.
Fine, it can be run on a 12F675. I thought there was only 24 bytes ram on a '675.
The average Joe isn't going to know to comment out those wsave variables until the compiler/assembler whines about it. Then the average Joe isn't going to know what 'Unable to fit variable wsave3' means after hitting F9. Then what is the average Joe going to do? Ask questions of course. A comment in the sspwm.inc file would fix that.
I haven't tried it on anything less than a 16F628A. I'll play with it this weekend on an 'F629 and see what happens.
Last edited by skimask; - 22nd October 2008 at 05:35. Reason: Took out those extra sentences in the beginning...WTH was that?
64, but it won't matter much.
SSPWM uses ASM interrupts. So the issue of saving all the PBP system vars doesn't apply.
Or maybe a note to use the current version.A comment in the sspwm.inc file would fix that.
SPWM_INT - Multiple Software PWM
http://www.darreltaylor.com/DT_INTS-14/SPWM.html
<br>
DT
Bookmarks