IR Library in 2.07

[PoltoS]

Nice to know GPT and Zerox are working!

Crazy usage of both Looks you have mastered Z-Uno!

May be you can share some project for community on our projects page?

[schmidmi]

I will do that, when it's working

[p0lyg0n1]

Thanks to all the programmers of the Z-UNO firmware!

Using the new Features of GPT and external interrupts I was able to analyse the protocol of my Mitsubishi A/C.
I connected the IR - receiver to the ZEROX (Pin 3).
With the GPT I measured the length of the pulses coming from the IR transmitter.
Now I can prove, that Mitsubishi is using a code length of 18 Bytes!

It sounds cool! You can use some of code of IRController library (see IRController.cpp inside z-uno cores), there are some basics concepts of IR-data and special format - RAW16. You will be able do decode mark/spaces to compact binary format. If you can give us you code futher we will be able to create a second "soft" IR library for Z-Uno together. Thank you!

[schmidmi]

I had a look to the file IRController.cpp already
I saw a fragment for Mitsubishi (not implemented yet).
Maybe that would be a sufficient way to handle my problems.

At the moment I have not much time to invest in theses items

[schmidmi]

Sorry, I wasn't reading the reply carefully enough...

If you can give us you code futher we will be able to create a second "soft" IR library for Z-Uno together. Thank you!

What kind of code do you need from me?

[schmidmi]

I think, it should be easier for you to think about an integration than me understanding the concept and code your IR library.
So I will provide a basic description of the protocol based on my investigations described in former posts:

Pushing any key on the IR transmitter will send a complete set of setting to the A/C equipment.
The telegram always consist of 18 bytes plus one header.
To be accepted by the A/C equipment the telegram has to be repeated once.
Between these two telegrams there is a special information (repeat Mark + Repeat space).
That means the complete telegram has 288 data bits + 2 headers (HeaderMark and HeaderSpace) + one repeat information (one RepeatMark + RepeatSpace).

Of course it would be nice to have a solution which handles the headers and repeat mechanism internally and allows the user to define the 144 data bits in a short description like "110100110....).

Attached to this post you will find a file containing the length of all mentioned marks and spaces in microseconds.

Name MITSUBISHI288AC

Header Mark 3400
Header Space 1700
Mark0 433
Mark1 433
Space0 433
Space1 1299
Repeat Mark 433
Repeat Space 17100