Gree GWF07DB window type a/c

[chuliu]

Hi Rob. I know you reverse engineering the timer for me. But the thing is I can't find a field to fill in that timer value. If you look at the available fields of a function of a upgrade with this protocol in question, there is no any field to fill up for the timer.

Please correct me if I am wrong.

[The Robman]

All I did was decode the signal, I didn't create a protocol entry in protocols.ini so you could program it into a remote because, as we discussed, I don't know how useful it would be as each button on the JP1 remote would need to include every single setting, so at best you could program a few "favorite" settings.

Anyway, if you look at the spreadsheet for this protocol you can see that the timings are in column T, and rows 43-90 are the learns that you gave me with times learned.

[The Robman]

Ah, I think I know what you're asking, I'm guessing you tried creating an upgrade using the Keeprite protocol in RM, and when I created that the timer hadn't been decoded. It was me that wrote the protocols.ini entry but that's not something that I do regularly, so I'm not real good at doing it. I wrote the Keeprite one 4 years ago, so nothing's fresh in the memory with that one.

If any expert would like to help out by modifying the Keeprite entry to add the Timer, here's what you need to know. The time goes up in 1/2 hour steps. It would help if you look at the spreadsheet to follow this description, and I'll refer to the bit positions the way Excel looks at them, so from left to right with the positions starting at 1 (rather than 0):

1. The timer is controlled by bits 13-20 of the first part of the signal (so, column L in the spreadsheet).
2. Bit 16 is an ON/OFF switch where 1=ON. When it's OFF, the whole byte is zeroes.
3. Bits 17-20 are decimal values 0-9
4. Bits 14-15 are "tens" (ie, multiply the result by 10 and add it to the result of #3 above
5. Bit 13 is the 1/2 hour indicator, so if it's set, add 0.5 to the running total
6. The times supplied go from 0.5 to 24 hours, so I assume that's the limit.
7. Everything is LSB, so read the bits backwards

I've broken out these elements and added them to columns E-H (rows 42-90) in the spreadsheet.

I see that I was able to decode the checksum when I did the Keeprite, so I need to remind myself what the formula is, because it might not take the timer into account.

[The Robman]

Never mind, I found my PB file for this and I see that I reduced it to 3 variable bytes by hard coding the timer byte to zeroes, so I'd need to modify the executor in order for you to be able to set the timer.