Flowcode Support Board

This is the 1 extending the signal

This is the 2

Hi

I found a transmitter and receiver in my Toy box—according to my checks—operate at 38 kHz. I displayed the signal received by the RX when pressing the "0" button on the screen. How can I get the PIC to decode the signal and identify that I'm sending a "0" with the TX

Not sure I understand you. What screen are you seeing the "0" on? Do you mean you are just capturing the pulse train as displayed in your following posts?

As far as I am aware, the Flowcode component is for RC5 encoded signals so NEC encoded signals won't work. Don't quote me on that as I am no expert in IR-RC protocols.

However, as you have a logic analyser you can figure out what you are receiving. You can see that the output remains high until transmission begins, therefore set your analyser to trigger on a falling edge, capturing an entire frame (until it goes back to high and stays there).

You will then be able to measure the duration and how many pulses are contained (including each pulse width).

With a "google" search you will find the format and difference between RC5 and NEC protocols, and can compare to what you have received. This will help you identify what is being used. This sounds far more complicated than it actually is. Once you have identified the protocol you can look at decoding.

Regards

PS
As far as I am aware RC5 is primarily used by European manufacturers and NEC by Japanese, but don't quote me.

Hi Lein,

I’m not looking at screens; I’m pressing the '0' button on the IR remote I’m showing, and the signal I see encoded on the logic analyzer is the one you recommended I check. However, based on what you said, I think it would be better to use the Flowcode 11 component to avoid complications—that component comes with built-in macros, so it’s just a matter of connecting and programming. Could you tell me which component that is I’ll see if I can get it from a store, provided it hasn't been discontinued.

In the meantime, if Martin (Mnfisher) keeps helping me, we’ll keep testing an alternative. This subject is complicated for me; I have absolutely no prior knowledge. Martin seems to know a bit about it, so I hope we can resolve the RC5 issue or use a component that yields the same results as RC5.

In any case, I appreciate your contribution. Thank you.

And perhaps Martin (Medelec) might be able to help with something as well.

Saludos

Hi,

I tried to build a reader for those small IR remote controls—I think it uses the NEC protocol—but after testing it all week, it didn't work. I suspect the programming involved requires an expert level of knowledge, but at least I gave it a shot.

Saludos

I'm still waiting on the 'receiver' PIC.

However - The transmit / decode (on Arduino) seems good.. I've made a few 'tweaks' to the decoder and I used a couple of transistors to toggle the signal pin on the transmission side.

Top line - transmission, second received signal:

Martin

Hi, thanks Martin.

I have an Arduino and the IR remote; let me run some tests. I'm just getting back, so I'll run the tests in a little while.

Saludos

Look forward t hearing how you get on - I just found another small remote. NEC format again

One thing I don't handle (transmit or receive) is the repeated key signal... Maybe jumping ahead slightly - let's get the basic working first!

PIC16F1847 arrived today!

I wired one up - and to a FTDI UART converter to display the received signal... I used the internal oscillator - giving a 32MHz clock.

Modified the pin and timer interrupts - here I use RB4 as input (I used an IOC interrupt - which allows either edge - it is possible to use INT0 and toggle direction)

Output looks reasonable

Martin