Similar Carrier_AC40 Protocol issue #1190

[rucko24]

Hi,

I have a detail with this, but apparently it does work, but something strikes me.

I have not been able to test with the kRawTick at 3, it seems to work fine.

Ok, my detail is this right now I have this output.

Timestamp : 000057.620
Library   : v2.8.4

Protocol  : CARRIER_AC40
Code      : 0xD02716C0CD (40 Bits)
uint16_t rawData[83] = {8454, 4176,  570, 1526,  566, 1532,  566, 482,  566, 1530,  564, 482,  566, 484,  564, 482,  560, 482,  566, 482,  564, 482,  566, 1532,  564, 482,  566, 484,  564, 1528,  564, 1532,  566, 1530,  566, 482,  566, 482,  560, 484,  564, 1532,  566, 482,  566, 1526,  566, 1532,  566, 482,  566, 1530,  566, 1528,  564, 482,  566, 482,  566, 482,  566, 482,  564, 482,  566, 482,  564, 1528,  564, 1532,  564, 482,  566, 482,  566, 1530,  566, 1530,  566, 482,  566, 1526,  566};  // CARRIER_AC40 D02716C0CD
uint64_t data = 0xD02716C0CD;


Timestamp : 000057.842
Library   : v2.8.4

Protocol  : CARRIER_AC40
Code      : 0xD02716C0CD (40 Bits)
uint16_t rawData[83] = {8450, 4180,  566, 1526,  570, 1526,  566, 482,  564, 1532,  566, 482,  566, 482,  564, 484,  564, 482,  566, 482,  564, 484,  564, 1526,  564, 488,  562, 482,  564, 1532,  564, 1532,  564, 1532,  566, 482,  566, 482,  560, 482,  564, 1532,  566, 482,  566, 1530,  566, 1528,  566, 482,  566, 1532,  566, 1526,  570, 484,  560, 484,  564, 482,  564, 484,  564, 482,  564, 482,  566, 1530,  566, 1528,  566, 482,  566, 482,  566, 1532,  566, 1526,  566, 482,  566, 1532,  566};  // CARRIER_AC40 D02716C0CD
uint64_t data = 0xD02716C0CD;


Timestamp : 000058.065
Library   : v2.8.4

Protocol  : CARRIER_AC40
Code      : 0xD02716C0CD (40 Bits)
uint16_t rawData[83] = {8450, 4176,  566, 1532,  566, 1526,  566, 482,  566, 1532,  564, 482,  566, 482,  566, 482,  562, 486,  560, 482,  566, 482,  566, 1532,  564, 482,  566, 482,  562, 1530,  564, 1532,  564, 1532,  566, 482,  566, 482,  566, 482,  562, 1530,  566, 482,  566, 1532,  564, 1528,  566, 482,  566, 1532,  566, 1532,  564, 482,  560, 488,  560, 484,  566, 482,  566, 482,  566, 482,  566, 1532,  560, 1532,  566, 482,  566, 482,  566, 1528,  564, 1530,  566, 482,  566, 1532,  566};  // CARRIER_AC40 D02716C0CD
uint64_t data = 0xD02716C0CD;

I don't understand why I don't see this, from IRrecvDumpV3

if (description.length()) Serial.println(D_STR_MESGDESC ": " + description);

It would be very useful for me to know the state of the air.

Style as follows

Mesg Desc.: Power: Off, Mode: 3 (Fan), Temp: 21C, Fan: 0 (Auto), Turbo: Off, Quiet: Off, XFan: Off, Ion: Off, Light: Off, Swing(H): Off, Swing(V): 1

According to the code contained in "IRac.cpp".

Line 152, only works with CARRIER_AC64 not CARRIER_AC40 ? CARRIER_AC64

Greetings.

[crankyoldgit]

The reason you're getting no "details" for the CARRIER_AC40 protocol is because it does not yet have detailed support in the library. It currently only has basic support. i.e. The library doesn't yet know how to decode the binary blob into useful controls & settings.

In order to add detailed support, you'll need to decode it. See: https://github.com/crankyoldgit/IRremoteESP8266/wiki/Adding-support-for-a-new-AC-protocol