Better understanding PULSIN

[Acetronics2]

Hi,

But why should the preference go for a PULSIN command first?

... just to be sure to catch the first pulse ... RCTime is somewhat "out of normal use" for the leading pulse ... result is not guaranteed !!!

Any idea why I get a result of 0 or 1 at bit 8 (sometimes bit 7)?

your scoping looks strange ... just at bit 8 !!! ... try to raise the TSOP decoupling caps value and to place a ~ 50 - 100 pF as load to the TSOP output - that could catch possible ns glitches ...

Also take care to have neat 0-5 v levels : the pic Thresold is @ ~1.5 v for TTL inputs ... and Schmitt trigger needs "good" levels ...

Have a nice evening

Alain

[flotulopex]

Merci Alain,

I can't see any change with the decoupling cap and the power is ok. I'll go for some other values and check again.

PBP manual: PULSIN normally waits a maximum of 65535 counts before it determines there is no pulse.

It looks to be the same for RCTIME... but as you say, RCTIME has not the same behaviour as PULSIN.

I think, depending on the IR remote type and protocol, I miss the first bit of the pattern.

Is it possible to make PULSIN scan a pin without time limitation (=until a signal is detected)?

[flotulopex]

Hi,

To make PULSIN wait "forever" for an incoming signal, I added:

LOOP1:
PULSIN p_in, 0, l_Bit[Ctr_A]    ' measure neg leading pulse
if l_Bit[Ctr_A] = 0 then LOOP1:
led1 = 1
RCTIME p_in, 1, h_Bit[Ctr_A]    ' measure time staying High
for Ctr_A = 1 to (bit_count - 1)
   rctime p_in, 0, l_Bit[Ctr_A] ' measure time staying Low
   rctime p_in, 1, h_Bit[Ctr_A] ' measure time staying High
next Ctr_A
RCTIME p_in, 0, l_bit[bit_count]

Thanks again for the RCTIME info, Alain. Is there something you don't know about, hein???

Bon dimanche et bonnes salutations hélvètes!!!

[Acetronics2]

Is it possible to make PULSIN scan a pin without time limitation (=until a signal is detected)?

Hi, Roger ...

Of course :

place a waiting loop,

you detect the first pulse with an interrupt: Alain's interrupt is the best here for latency ... as there is nothing to save ! ( RCTime is to use at first here !!! ) and place your RCTime's "gang" in the interrupt stubb ...

( no RETFIE or GOTO needed ! )

then, your display routine ...

Then back to the waiting loop.



now, for better precision ...

you should use

PULSIN
RCTIME
RCTIME
RCTIME
...

instead of a FOR-NEXT Loop ...

Is there something you don't know about, hein???

Easy answer is ... WOMEN !!!

True answer is Biology, Medicine and such specialities ... more generally what do not accept a mathematical model !!! ( at least yet ...)

One exception : Horses !!!

Have a nice Sunday

Alain