Add support for Airton AC

[jonesy2]

Hi,
Hoping to contribute to this great project.
I'm adding all that I have, and will add more/ do more test as required.
The AC did not respond to any codes in the library version v2.7.18

The AC is AIRTON (bought in France). There is no model number, but it is the 2500W version. The remote has no part number, but the chip underneath the lcd is SH77P1652 SINO WEALTH. On the inside of the battery cover is the code RD1A1

Following the I have captured the usual modes (hot/cool etc) at all temperatures. I don't use the timers, or change away from auto fan etc.
The spreadsheet is here
https://docs.google.com/spreadsheets/d/1l-qo6LPPkBYUGSJ65j3-j3iQJg7lGAo96AzR4s6NDOA/edit?usp=sharing
56 bit.
The auto_analyse_raw_data.py code produced code that worked with the slight modification of 56 bit, rather than 57 bit that was suggested.

Manual here https://cdn.shopify.com/s/files/1/2600/0244/files/409730-409731-409732-409733_MANUAL_INSTRUCTION_V01052021.pdf?v=1619861501

[crankyoldgit]

Hey, we can probably add this, but you need to follow: https://github.com/crankyoldgit/IRremoteESP8266/wiki/Adding-support-for-a-new-IR-protocol#obtaining-the-data

Without some of the raw data etc, we can't be sure we can decode the underlying signal. We need it for testing

Also, please update to 2.7.20 (or the master branch) as the protocol may have already been added.

[jonesy2]

I've updated to 2.7.20, and the protocol hasn't been added.
I've updated the spreadsheet to show uint16_t rawData I used for testing (the 'all' tab)
I think that's it, but happy to do more if you point me in the right direction

[crankyoldgit]

Thanks for the raw data. That allowed me to build basic support for your protocol.
You'll need to recollect, recapture, & reanalyse all of your data because after analysis of the temperature data, the protocol uses LSBF bit ordering. Your existing spreadsheet has MSBF ordering.

To help your analysis:
The first byte of data will be the checksum byte. (0x5E1400090C11D3) You will need to work out how that is calculated
The temp is stored in this nibble (0x5E1400090C11D3). i.e. That nibble + 16 gives the temp in Celsius. e.g. 0x9 + 16 = 25C

Once you've mapped out all the bits, what they mean, how they work, what the values mean in terms of modes/swing positions etc etc, and have it all nicely & clearly documented in a spreadsheet or some document, I'll re-look at this and code up the detailed support (i.e. setting modes, power, temp etc).

For now, it should decode to a 56-bit hex number in IRrecvDumpV2 or V3 etc if you download & compile using branch: https://github.com/crankyoldgit/IRremoteESP8266/tree/airton_basic / PR #1681

[jonesy2]

Thank you for the update.
I have compiled PR #1681 and it correctly decodes the remote

`IRrecvDump is now running and waiting for IR input on Pin 14
Timestamp : 000140.459
Library : v2.7.20

Protocol : AIRTON
Code : 0x591400060C11D3 (56 Bits)
uint16_t rawData[115] = {6648, 3310, 408, 1258, 406, 1258, 408, 426, 434, 398, 406, 1258, 406, 426, 404, 1258, 406, 1258, 406, 1258, 408, 426, 434, 398, 406, 426, 406, 1258, 408, 426, 406, 426, 434, 398, 406, 426, 406, 426, 406, 1236, 430, 1256, 408, 424, 406, 426, 406, 426, 432, 398, 406, 426, 406, 1258, 406, 1258, 408, 426, 406, 426, 436, 398, 404, 426, 404, 426, 406, 426, 406, 426, 432, 398, 406, 426, 406, 426, 406, 426, 406, 428, 404, 426, 406, 426, 406, 426, 406, 1256,
408, 426, 406, 1258, 408, 426, 404, 426, 406, 426, 406, 1258, 408, 426, 406, 426, 406, 1258, 408, 1256, 408, 426, 406, 1258, 408, 426, 406}; // AIRTON 591400060C11D3
uint64_t data = 0x591400060C11D3;`

I've done a new spreadsheet LSBF, which is here https://docs.google.com/spreadsheets/d/1Kpq7WCkh85heLnTQGlwUfCR6eeu_vfBHvhii8wtP4LU/edit?usp=sharing
There were a few mistakes which I've fixed.
The old link is still valid.

The checksum escapes me still. You can see in state[0] that is works for some codes, but not all.

[crankyoldgit]

Thanks for confirming receiving/decoding works. Have you tried transmission/sending also?

The checksum escapes me still. You can see in state[0] that is works for some codes, but not all.

No idea also. I tried a few things, but it alludes me too. Until you've worked that out, there is next to no point on me starting the coding for detailed support.

Try also playing with the data in MSBF format too, ya never know.

[jonesy2]

Transmission is fine both rawData and irsend.sendAirton.
I can't help feeling the checksum is simple, but after spending a couple of days I decided to save my sanity and stuck with sending codes.
Thank you for your help. Hopefully someone else will want Airton support and will crack it.

[crankyoldgit]

Thanks for the confirmation. Sorry about the checksum or what ever it is etc.

Marking this issue closed.