I think I had it pointing to PBPW at the time.
Proteus saves the compiler path in the .dsn file.
Go to ... Source > Add/Remove Source code files..
Change the "Code Generation Tool" drop-down box so it points to your installation. (PBPMPLAB)
I think I had it pointing to PBPW at the time.
Proteus saves the compiler path in the .dsn file.
Go to ... Source > Add/Remove Source code files..
Change the "Code Generation Tool" drop-down box so it points to your installation. (PBPMPLAB)
DT
Nope same error
Can you post exactly whats in your source code boxes?
Here's the way that one was setup. But you should change it to use COF instead of HEX and add the -K# command line option.
And make sure your compiler setup is working with a new design.
![]()
Last edited by Darrel Taylor; - 18th February 2011 at 15:45.
DT
I've upgraded to a 16F88 chip now.
Just a thought, is it possible for SSPWM to use TMR0 instead of TMR1 on the 16F88 bearing in mind my 2khz
PWM requirement with variable 10-90% duty in 1% steps?
I'm not complaining SSPWM works well but freeing up TMR1 would let me use it for my
speedo routine.
Well, you could certainly write a program that uses TMR0 to generate frequencies.
But SSPWM will not do it.
It needs a 16-bit timer to meet the published Frequency/Dutycycle range.
DT
Bookmarks