Gree GWF07DB window type a/c

[chuliu]

I have captured all buttons on the remote with oarusb04g with extender.
I have uploaded rmir file with learned signals to the file section.
http://www.hifi-remote.com/forums/dload ... e_id=26880

I am not very familiar with how a a/c remote works. Like does it send only one signal mode when I press mode, or does it send the temp set, fan speed, timer status, etc to the a/c. Also, does pressing temp+ temp- only send two signals? or does pressing temp+ at 16, 17, 18 , 19 etc all different.

I haven't take a look at the pattern of the signals. If they are simple enough, I maybe able to create a new protocol name FF FF and run it from there.

The ideal will be for someone to give it a protocol, maybe. But it is out of my scope.

So, due to my lack of understanding of how a remote for a/c works and my lack of capability to create a new protocol. I will wait for forum experts to come in and help.


Thanks. Let me know if you need more reads of the buttons on my remote.

[The Robman]

The signal is very similar to the NEC signal but it's longer. Normally, A/C signals are, as you suspect, really a combination of all the settings, so TEMP+ isn't really the code that gets sent, it's really the code for the next temp. The only way to truly capture an A/C signal is to set everything to a known state, preferably the lowest state for each setting, then capture the signal every time you raise one of the settings, like FAN (low), FAN (medium), FAN (high), TEMP+ (66*), TEMP+ (67*), etc.

And then once we have all of that data, the real question is, would a protocol that re-creates it be useful to you? Because, we won't be able to re-create a TEMP+ button, instead we will create discrete codes for each setting, so a single button would set the FAN to high, the TEMP to 68*, etc etc.

Here's what I got from your captures...

Code: Select all

power  +9000 -4500; 11001000011100000000010000001010010; +500 -20000; 00000000000000100000000000001111
fan    +9000 -4500; 11010100011100000000011000001010010  
uv     +9000 -4500; 11010100011100000000010010001010010; +500 -20000; 00000000000000100000000000000001
mode   +9000 -4500; 00110000001100000000010010001010010; +500 -20000; 00000000000000100000000000001110
swing  +9000 -4500; 00110010001100000000010010001010010; +500 -20000; 10000000000000100000000000001110
timer1 +9000 -4500; 00110010001100011010010010001010010; +500 -20000; 10000000000000100000000000000011
timer2 +9000 -4500; 00110010001100011010010010000110010; +500 -20000; 0000000000000011010000010001010
wifi   +9000 -4500; 00110010001100000000010010001010010; +500 -20000; 10000000000000000000000000001100
temp-  +9000 -4500; 00110010101100000000010010001010010; +500 -20000; 10000000000000000000000000000010
temp+  +9000 -4500; 00110010011100000000010010001010010; +500 -20000; 10000000000000000000000000001010

[chuliu]

Thanks for ypur explanation. It helps me understand the basics of how an a/c remote works. However, after second thought, I find programming all the a/c remote signals to a one for all remote to have little use for me. For example, setting one button to set temp to 27, a second button to 28, and one more to fan low, etc. It is not easy to memorize these buttons at all.

Maybe it is easier to buy a generic remote for gree for a spare.
But thanks for your help and explanation again.

[The Robman]

Do your learned signals work, and if so, do they do what you expected, or do they set everything to a specific level?

[chuliu]

Do your learned signals work, and if so, do they do what you expected, or do they set everything to a specific level?

I don't know how to send the learned signals from my oarusb04g. I normally convert the learned signals to an upgrade and send the "programmed" signals.

Maybe I need to check the manual for the extender for that.

[mdavej]

Just push the button you learned.

[chuliu]

Thanks for the reply. I assume that the learned signals take precedence over the programmed device signals. So I tried a few of the buttons I learned, but it did nothing to my a/c. This includes power on, fan auto, mode auto, mode cool.


You can find the rmir with more signals learned here

If you would like to deal with ict files, I have include it here

[chuliu]

So I decided to spend more time digging into the a/c remote control signals. I spend hours on creating manual protocol using pb and rmdu. Then upload to my rcrp05b. This is becuase the manual protocol only supports? s3c8 processor. The resulting signals have not been working. I was learning the signals with oarusb04g and it is of hcs08 processor. Just as I was about to give up, I decided to learn the signals with my vizio which is a s3c8.

I learned the signals as I normally do and check the protocol in the learned signal tab. To my surprise, it shows keeprite a/c protocol. I check the available input in the function tab and it seems to have most parameters for an a/c in one function. power, fan, temp, timer, etc, you name it. I don't want to mess up with it any firther without someone letting me know how I can go on to set it up. Can anyone shed some light as to how this keeprite a/c protocol is supposed to work? I can set up a few buttons to let the a/c run with the desired parameters and I will be good.

[chuliu]

http://www.hifi-remote.com/forums/viewt ... &&start=15

A quick google search leads to this thread. I found an upgrade to my a/c which works for most of my needs, except for the timer.

To set timer on my gree a/c, I press timer button once( no ir signal for this time), set the desired time by pressing up or down( no ir signal), and then press timer again( there is ir signal this time).

Will capturing the signal in the last step show me how to use my vizio or rca rcrp05b to set the timer?

[The Robman]

Well done finding that Keeprite upgrade. Your learns came out looking different to the Keeprite ones, in that they had the 35-bit string first and the 32-bit string second, whereas that is swapped in your captures, so I am impressed that you spotted that they are the same.

It's not that manual protocols only support S3C8, you can write executors in any language, but I've only learned how to do it using S3C8, so when we need support for the other processors, one of the other experts writes them.

For learning remotes, it doesn't matter which processor is used, the learned signals will look the same.

As for your question on how one would use an A/C upgrade in their JP1 remote, that is the million dollar question. There is no useful way to use them because we can't display the values on a screen in your remote, and it would take a LOT of complicated coding to try and replicate the UP and DOWN buttons that exist on your A/C remote. The best that you can do is pick some favorite settings and code those onto a couple of buttons on your remote.

If you want to figure out the timer, yes, you will need to capture the signal after every time that you change the timer because the time itself is probably encoded into the signal, and it's probably in the K13-20 part of the Keeprite signal. You would need to capture as many examples of the different times as possible in order for us to capture all of the bits that might be used in the signals. Now that I know that your remote uses the Keeprite signal, I will be able to decode the captures for you.

[chuliu]

I finally got the time to learn the timer functions.
It is hot these days and I couldn't learn the signals with my a/c on.
Therefore, the wait.

Here it is:
http://www.hifi-remote.com/forums/dload ... e_id=26891
http://www.hifi-remote.com/forums/dload ... e_id=26892

I have marked the time in hours of the timer in the notes field.

[The Robman]

Thanks, the timer does use the byte of data that was previously unaccounted for, so I've added a decoder to the spreadsheet to display the time. What is the time unit? I'm guessing it's hours. I think you messed up the learn for 5 hours because it shows up as "off".

http://www.hifi-remote.com/forums/dload ... e_id=26060

[chuliu]

Thanks, the timer does use the byte of data that was previously unaccounted for, so I've added a decoder to the spreadsheet to display the time. What is the time unit? I'm guessing it's hours. I think you messed up the learn for 5 hours because it shows up as "off".

http://www.hifi-remote.com/forums/dload ... e_id=26060

It's in hours.

[chuliu]

Thanks, the timer does use the byte of data that was previously unaccounted for, so I've added a decoder to the spreadsheet to display the time. What is the time unit? I'm guessing it's hours. I think you messed up the learn for 5 hours because it shows up as "off".

http://www.hifi-remote.com/forums/dload ... e_id=26060

I downloaded the excel file and took a look at it.
It appeared bit 13-20 has to do with the timer.
From here to arrives in a protovol entry in protocols.ini is beyond my scope.
I tried to download a few s308 datasheet and a couple of variables used in assembly. But decided for now I cannot do it. Let alone the resulting new keeprite a/c protocol. Please help, Robman. Thanks.

[The Robman]

It's more than "to do with the time", it IS the timer, I reverse engineered all of the bits. There are 4 bits that give the 0-9 portion of the time, 2 more bits give the tens digit, 1 bit gives the 1/2 hour portion and 1 bit is an on/off switch.

I haven't cracked the checksum portion yet though.

As for creating an executor (ie, something to add to protocols.ini ), what would be the point? Every remote signal includes every setting, so the best that you could do is create buttons for a few of your favorite profiles (ie, something like mode=cool, power=on, fan=auto, sleep=off, temp=21, timer=off, turbo=off, unit light=on, sing=top, temp display=on).

To make an executor that is really useful, we'd have to find a way to save all of those settings in the remote, so you could actually program buttons like TEMP+, or TIME+, etc but that's really advanced stuff, and I don't think we have enough unused registers in the remote to do that.