For the past 3 days I have been trying to decode my Air Condition's remote..
1stly the remote is not at all recognized by neither IRRemote nor the IRLib Libraries..
I started googling on how to decode and Air Condition's remote..
I came up with that most of the Aircon remotes sends a long commands..
From the below thread I came to know that the commands are sent twice.
http://forum.arduino.cc/index.php?topic=226419.15
On this thread's 16th post AnalysIR guesses "This may be to increase the chance of a good signal or it could be basic error checking"
AnalysIR has been doing a great job and has contributed his effort to understand and decode the signal of the ON/OFF button with his precious application..
MY VIEWS from what I found out today suddenly
- All the Aircon remotes sends two different values for ON and OFF
- The Temp UP and Temp Down buttons also sends different values for different temperatures..
3.The Air Swing and Fan speed also sends different values for each state..
So we come to know that most of the buttons sends multiple values.
4. NOW THE MOST IMPORTANT PART...
I found that these multiple value buttons not only sends the value of its own, but also checks the states of other buttons like (PWR, TEMP, SWING POSITION, FAN SPEED).
REASON for this-- In case sometime the remote's IR was blocked and some button states were changed accidentally or changed in the absence of electricity.
The next time you want to change any button's state purposely, the update to the Aircon will match with the remote and will not act like a false state.
** Example** - The Aircon is running and while the remote was out of IR range or was blocked, the PWR state of the remote is changed to OFF state. Now the remote status is shown false, as the remote shows the Aircon is OFF but in reality the Aircon is ON..
Now when you try to change the temperature purposely (in this false state position) the remote will check the states of other buttons and update the new values to the Aircon. The Aircon will turn OFF, because on the remote the present status was OFF (which was previously changed accidentally)
So my guessing is that the reason of sending codes twice may be that its updating the state of the changed button as well as the states of the other buttons...
I am trying to check the RAW values in different ways with AnalysIR's written code to decode long RAW values in the below link
Its really hard to check and compare each values manually ...
But I am still trying.. Let see how far can I go...