Capabilities & Stock Installer Messages For LG Artcool Gallery & 4-Way-Cassettes (Multi) #11
Comments
|
Thanks for sharing these. I should probably add this to protocol.md. The CA message from your Artcool is exactly the same as the one from my wall units. Good to know that you were able to set the fan speeds. Because my units send zeros for these bytes, I was thinking they don't support this setting but it'd probably work then. I wish I could see the current values before changing them, though... The CB message: interesting that both have byte 1 set to 0x80, I haven't seen that bit being set yet. Bytes 3-4 are similar for all messages I've seen so far: maybe some kind of sensor values but I don't know what it is. Byte 5 is 0xFF for my wall units and your Artcool, but your cassette has it set to 0. No idea what it is. Your units also send model information, mine just send zeros for these bytes. |
|
@JanM321 do you have plans to use Another question - if you're using your AC for heating as well - I'm wondering why you set the min. setpoint to My Artcool Gallery does not support a cooling setpoint of 16°C, while the 4-Way-Cassette does. |
I never use setpoint < 18, so I just didn't think about it. My apartment stays pretty warm so I turn off the AC if I'm gone for a few days. Do you know if your Artcool handles a cooling setpoint of 16 by simply changing the setting to 18? In that case we could consider setting the minimum to 16 for now and letting the AC handle it. For my uses the software is mostly feature complete at this point. I can look into vane control + maybe a YAML parameter for the over heating installer setting when I have some time. I think having these in place would make it easier for people to add their own settings. |
Yes it does, I set it to 19°C in cooling via thinkQ and then requested 16°C with the controller.
No worries, I'll just update my fork to my requirements, there is no need to upstream everything 👍 |
|
I just committed some changes for vertical vane position (just a single vane since that's all I have here) and a YAML setting to change installer setting 15. I had been thinking about doing this for a while, but it required some refactoring to handle other message types. |
|
I've tested the 0.5 overheat settings on my units and they seem to perform well, so I've reset my fork to your codebase and created a small PR for the setpoint. Also I've taken a look at your latest commit and have a few questions:
|
Yes, I made a change on Saturday to set the request-settings flag when the ESP32 powers on. This matches the LG controller and makes my units send all of the settings. Does that work?
Maybe installer setting 46, "Setting the fan continuous"? My unit doesn't support this option with the official controller so I wouldn't try this myself. Probably worth looking at the PREMTB001 and PREMTC00U manuals. Unfortunately a lot of these settings are poorly documented and I had to get information from various manuals.
This is an issue with LG multi split systems for heating unfortunately. They call this an "oil return cycle" and it happens in heating mode every ~3 hours. With the -0.5/+0.5 installer setting I haven't seen it yet because the unit makes much shorter runs. Modulation isn't great for me either. My MU2R17 is less powerful than your MU3R19 which helps a bit I think. This is for last night with just one unit turned on: 
This is with fan speed 4 of 5 (it uses less power at higher fan speeds because less heat is needed if the fan helps spread it). Typical stable power consumption after running for at least 10 minutes is < 500W, but sometimes it's 800W or so and I don't really know why. I think I do see fewer peaks with the over heating setting set to 4, but I'm not sure. |
Totally missed that, works well!
I'll take a look at that, thanks.
For me it's really hit-and-miss. It's kinda sad, I heat a large house with 3 Multisplits and the others (Toshiba RAS-3M18U, 2M14U) do perform much better and module to below 200W easily. The Toshiba 3M18U (pink) has equal capacity to the MU3R19 (blue) and is handling around 60% of the thermal load here: Next I'm gonna look into the repositories covering their A/B TCC-Link protocol and build an esphome component. It's also cool that Toshiba reports all sensor values for indoor and outdoor units, frequencies and so on. |
|
I just realized there's still a minor issue with the initialization code: I should set
Yeah, it seems that for LG the heating feature is more of an afterthought and their main focus is on cooling. MHI, ME, Daikin, Panasonic are also better at this. I've heard the LG single split units work better than the multis as well. In March I got really annoyed with the internal temperature sensor (wall units are located near the ceiling so the sensor was often way off and rooms were either too cold or too warm). After that I started reverse engineering an LG wall controller and I'm really glad this all worked out in time for this winter. The behavior still isn't perfect, but the external temperature sensor has made a huge difference. |
|
Hello everyone, I'm currently pressed for time and unable to delve into my unit further, but I wanted to share the C9/CA/CB messages from my three S12ET units with you. Perhaps they might be of interest: If it's too off-topic for this issue, just ignore it. |
Thanks, that's helpful. These are the messages for my AP09RT unit (before I changed installer setting 15, "over heating"): The C9 message is almost identical to your units (as expected because they're similar wall units), except:
The CA message is similar except for byte 9 where mine has an extra unknown bit set. The Artcool has this set too but not the cassette. The CB messages are very interesting. Until now I've seen bytes 3 and 4 have similar values that change regularly and byte 5 is either 0x00 or 0xFF. With your units, that's kind of reversed: bytes 3 and 4 are 0xFF but byte 5 has the kind of value that other units have in bytes 3-4. I really wonder what these 3 bytes are for. I've been thinking about adding some sensors to report these values to Home Assistant every N minutes, to see if tracking them over time tells us something... |
|
@JanM321 Thanks for the explanation of the various bytes. Regarding byte 2: You mean your unit has air purifier built in, mine does not, correct?
If you could provide me with a modified version in another branch or just a diff, I could test it out for you. |
Correct.
Thanks. I haven't made these changes yet but if I do I'll let you know 👍 Below is a list of known CB message bytes 3-5. Looking at these values and when I collected some of them, it could be a temperature value. |
|
The air purifier flag does not indicate whether an plasma ionizer is built in though. Here are some CB messages from my Cassette: And from my Artcool: |
|
It does look like two similar temperature/humidity/something sensor values. E0 is pretty high. Maybe the heating was on here? I think it's unlikely that we can use these bytes for anything interesting. It would be nice to have a newer controller like the PREMTB100 to see if that tells us more, but they're pretty expensive so I've found it hard to justify getting one - we can already implement pretty much all of the available features. |
|
Progress! These 0xCB bytes are pipe temperature values. I documented them in protocol.md I figured this out by playing more with the PREMTB100. I'm not sure yet which flag enables the menu option for this, because with my unit's settings it doesn't show this. This is pretty interesting information to monitor. I might add sensors for these values, but I don't know yet if I can get my unit to send 0xCB regularly. |
|
To request a This also works in the other direction: the PREMTB100 will immediately send I have this implemented now to request a I'll monitor this for a bit to see if it works as expected. |
|
OK I made these changes. The controller will request and then report the pipe temperature values every 10 minutes. In heating mode these values can get pretty high (30-50 degrees) but when the units are off I get values close to the room temperature. @drbugfinder based on your CB messages, your units only report the 'Mid' value. Most other units report 'In' and 'Out' but not 'Mid'. If you have a chance to verify this sensor works too that'd be great. |
|
Great finding! |
|
Okay this is a tiny bit confusing. EDIT: I guess this is correct and the sensor values are not swapped in heating mode when the refrigerant flow is reversed? Artcool Gallery My (problematic) 4-Way-Cassette Are the sensors reversed (like swapped connectors) or did I somehow (unlikely) manage to reverse the pipes? And yes, In is always 1+°C below Out for all temperature ranges I saw. |
It's the same with my units. I read it as "air coming out is hotter than air going in" but not sure if that makes sense. Typical stable values are In: 37 / Out: 42 or In: 30 / Out: 33. Both drop to around-zero when there's an oil return operation. |
I see the following output: (I guess this one was during de-icing) So I think this works 👍🏻 |
These are my Artcool Gallery and 4-Way-Cassette messages for anyone interested:
LG ARTCOOL GALLERY (Multi) ORIGINAL MESSAGES:
If anyone with an Artcool Gallery stumbles upon this,
23is the minimum LOW fan configuration that doesn't keep the compressor from stopping (overheat) and is a lot more bearable than the default fan noise:LG 4 WAY CASSETTE (Multi) ORIGINAL MESSAGES:
The text was updated successfully, but these errors were encountered: