Search:

I'm not seeing any

zip files from a unvetted source , no thanks

a screen shot or a simple description of how A2 is derived and an explanation of how that voltage is to be displayed would help

its a simple thing....

just found this, no wonder i felt i had seen it all before
http://www.picbasic.co.uk/forum/showthread.php?t=24035

still finding the same lack of detail

10 bit adc @5v <=> .00488 volts per count
point A2 in sch = @1.76 v ie. 360 counts
360/12=30
this is the displayed result. what were you expecting


there is no visible relationship...

i doubt many would risk unvetted content from google drive, youtube would be safer.
there is no config settings in your code.
what type of osc and speed.
what have you tried to port code to 16f886...

i guess that its fair enough that he who pays the piper call the tune.

but advertisement executives in their race to the bottom seem to fail to realize that the odious nature of their methods...

why do the ads have to interfere with reading threads by intruding into them
or blocking vision of them?
why do ads popup and force you click over them to proceed ?

ads yes ok , but i don't want...

i find the ads appalling and intrusive

arduino uses a 7bit i2c address , so everything arduino-ish complies with that convention , pbp uses an 8bit i2c address scheme
no big deal just 1 shift left gets there from the 7 bit address.

...

its just like deja vu all over again
https://support.melabs.com/forum/picbasic-pro-compiler-3-0-and-later/pbp3-picbasic-pro-3-0/7303-symmetric-source-code-pic-16f877a
4 years later still the same...

Yes a hserin timeout that is too small causes some grief even the odd reset, i had to increase it to 300 for hand typed input for a successful
test.
my previous tests had the timeout commented out...

what did you try , post your code



all those calc's are for a 20MHz clock if you use a different OSC then they must be recalculated

the internal OSC is not brilliantly accurate and could...

how sure are you that your code is compiled with the modified inc as i suggested ?

if you examine the lst file generated and search for NoTimerInt
do you see

9248


pbp can be tricky if...

What those two chips have in common is auto context save for interrupts.
i simulated the 1824 and the problem was not experienced, but who would trust a simulator



try this for...

125KHz is [COLOR=#333333]only available with a pbpl compile

from the manual hpwm section



every chip you have posted about on this subject is quite capable of that output.
your posted code...

why would the uart need a TMR1 interrupt ?

code ?

your understanding is flawed and math is incorrect

Duty is Steps x 0.625% // steps = CCPR1L x4 + CCP1CON<5:4>

so:
80x0.625% = 50% <=> steps = 20x4 + 0
56x0.625% = 35% ...

totally missing the point

CCPR1L = $14 not 14 ; its hex 14 or dec 20

maybe more like duty cycle of 2.8us/8us * 100 = 35%




or correctly
' To get a 50% duty cycle output,
CCPR1L to $14 and CCP1CON<5:4> to <0:0>.

from the data sheet, my best guess . i see no attempt to read portb before sleep

You need to travel back in time ten years , last known semi workable setup was with mplabx 2.35

i would not expect to ever receive a malformed bit from a keeloq serial stream , the data may be useless however.
single point sampling should be ok imho

in simple terms adding the two's compliment of a var to a number is equivalent to subtracting the var from a number
providing they are all the same integer var type

In a noisy environment you can over sample a bit to be sure of data validity, i expect the serial data from a keeloq
chip to be quite clean so a single sample point would suffice

sample...

a couple of ways


pulsetrain:
index=67
while index
while !portb.0 :wend ;wait for hi
index=index-1
pauseus 600 ;bit period=3*te ie 3*400=1200uS
code.0[index]= ~...