-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New variation of CN_WIRED #231
Comments
We get 66 symbols, but I have rx set to allow for 128 (I'll reduce that to save memory). So yes, we are checking for longer messages. This is exactly the right length and all timings match the protocol. |
set_val (swingv, (payload[5] & 0x20) ? 1 : 0); I'm sure I read "bit 5", but OK, changed. Changed. |
More examples... I'll keep the log going to try and find more.
All nibbles, including checksum, add up to F. Simples. The first 2 values on message type 4 look like temps, maybe min/max range and current? |
I have updated my checksum code, and made these report as unknown message type. |
My bad, Hit the wrong key. Or maybe counted from 1 like a n00b. Just pushed fix for the doc. I wonder, does this AC also transmit messages we know, or this is all it sends ? |
Sends the normal type 0 (and 1 on mode change) as well but also these 2 and 4 regularly. |
Do we know AC types ? |
FTV35PBV1MF and FTKG50 send type 2 and type 4: Sonic-Amiga#19
There's a suggestion that byte[0] in type 2 stands for outside temperature. Unable to verify. |
We are testing CN_WIRED protocol implementation; and we found some AC models, which don't conform to current documentation: https://github.com/Sonic-Amiga/ESP8266-Faikin/blob/main/Tools/Simulators/CN_WIRED/README.md
Symptoms are: physical format seems to be correct, but data encoding appears totally different.
Examples are:
#126 (comment)
#126 (comment)
I tried calculating checksum by hands and indeed i can't see any pattern here.
Some questions:
We mostly have to restart the research (mostly) from scratch with this A/C.
The text was updated successfully, but these errors were encountered: