remote code learning

[Ioannis]

How about re-calibrating on every header to the possible slip?

If header is x% off then probably all the bits will be too.

Ioannis

[dhouston]

How about re-calibrating on every header to the possible slip?

Again, it really isn't necessary as the codes need not be precise. For example, NEC defines a 1-bit as ~2.2mSec between rising edges and a 0-bit as ~1.1mSec between rising edges. It's child's play to differentiate even if overall timing varies widely.

The only codes that require you to capture both pulses and spaces are the biphase protocols like Philips RC5, RC6, etc. where you need to recover the timing before you can decide between 1 and 0.

Ooops - I forgot about one protocol. I don't recall who uses it (it's a high-end RF home automation system used mostly in Europe). It uses 5 different pulse widths and 5 different space widths which allows for an enormous code base. If you assign ADCDE to pulses and abcde to spaces, you can see there are lots of possible 10 letter words (10^5 or 100,000)

[Bruce]

Thanks Dave. I agree. I have one version that simply spits out up to 100 pulse periods to a serial port. Then it's easy to see everything at a glance. The period between packets is easy to locate, etc,,.

Even fiddled with one version that actually printed out working PBP code to reproduce the data packets, adjust for various carrier frequency, etc. Was fun. Just cut & paste and viola...;o)

That sounds like a pretty nifty PC app you wrote a while back.

[cesar35]

Hello about mister Bruce code
Can i use another photo as pic16f876a
I appreciate it

[Ioannis]

Photo? What Photo?

Ioannis

[cesar35]

Excuse me
Hello about mister Bruce code
Can i use another o pic16f876
I appreciate it

[Ioannis]

You need a PIC with the motion feedback module. An there are not many.

Sorry...

Ioannis

[Ioannis]

Or you can write more code to emulate the motion feedback module.

Tedious I think.

Ioannis