16F88 internal clock configuration

[mister_e]

so there's no analog to digital conversion on a.0 and a.1 ???

you must disable those analog pins to make them digital.. at least

ANSEL=3 'set a.0 and a.1 as digital input

and capacitor should be consider.

[Tom Gonser]

Set the .. ANSEL=3 'set a.0 and a.1 as digital input, thx. Probably a good idea, but did not have any impact.

Oddly as I test, I find that my setting for OSCAL 8 mhz or OSCAL 4 Mhz does not have any impact on the system..

I have tried:

OSCCON=%01101000 ' 4 mhz
DEFINE OSC 4

----

and in another test...

DEFINE OSC 8
OSCCON=%01111000 '8 Mhz


Something must not be getting written somewhere. I'd expect that these settings would have a big impact on overall system operation.

Is there some prescaler setting that I am missing?

tg

[mister_e]

prescaller have nothing to do with your code if you're not using TIMERs. Can you post your code here or it's a 'military secret'

[Tom Gonser]

This program reads a data sentence sent at 9600b 8,1.n. The sentence has two start bytes, then 34 data bytes. It works on the 16F876A on the test board from Microchip, but the plain old F88 on my breadboard is acting strange as the thread indicates..

TG

[mister_e]

reason is simple... you run out of memory...

PIC16F876 : 8K
PIC16F88: 4K
YourCode :4287 words

so you can for sure shrink it using internal or external EEPROM instead of arrays and few other things. It has to fit in a 4k memory space

[Tom Gonser]

...wow, that easy huh? Well, I removed some of the code, and it does run much better, indeed!! I still see some odd behavior however:

1. The voltage calculation is inaccurate
2. The 'initialize' subroutine does not fire, or only partially fires
3. The N, S, E, W Select Case does not appear to be working as the values are missing in the output
4. The Select Case routine for the lock flag (which is 1,2, or 3. is showing an ERROR - or something besides these values.

The other calculations look right...

I think all this may be convincing me not to try to port over, as this program runs really well on the other chip... arghhh

[mister_e]

Post your new code here to see wha can it should be.