Skip to content

Configuration

Jump to bottom
tagyoureit edited this page Jul 23, 2016 · 32 revisions

Configuration

It always seemed that there should be a way for the Main controller to tell the remote controls/wireless/etc what the pool configuration is. Sure enough, if any material changes (change temperature, circuit names, circuit configuration, schedules, egg timers, etc the controller will re-broadcast the setup to all devices. The setup seems rather confusing, but with some collaboration (and testing), we should be able to decode it.

Here is what I know so far:

1. Initial Request (Date/Time)

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Request Get Date/Time 16 34 197 1 0 1 167
Response Date/Time 15 16 5 8 19 45 4 31 5 16 0 1 1 84

2. Next Request(s) - Some configuration information TBD

2.1 Request for Pump (or valve) information??

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Request 16 34 216 1 1 1 187
Response 15 16 24 31 1 128 0 2 0 1 6 2 12 4 9 11 7 6 8 128 8 132 3 15 5 3 214 128 46 108 2 152 232 220 232

| Request|16|34|216|1|2|1|188| Response|15|16|24|31|2|128|3|2|0|12|3|5|5|13|7|14|11|0|3|0|3|0|3|0|3|12|232|220|208|184|232|232|232|232|28|8|242|

2.2 Request for ___?

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Request 16 34 253 1 0 1 223
Response 15 16 252 17 0 2 90 0 0 1 10 0 0 0 0 0 0 0 0 0 0 2 66

| Request|16|34|222|1|0|1|192| Response|15|16|30|16|0|0|0|0|1|72|0|0|0|46|0|0|0|2|0|0|1|117| | Request|16|34|221|1|0|1|191| Response|15|16|29|24|2|0|0|0|128|1|255|255|255|0|7|2|1|8|5|6|7|8|9|10|1|2|3|4|4|204 | Request|16|34|224|1|0|1|194| Response|15|16|32|11|0|7|2|1|8|5|6|7|8|9|10|1|56| Pump or valves??| | Request|16|34|224|1|1|1|195| Response|15|16|32|11|1|1|2|3|4|5|6|7|8|9|10|1|49 | Request|16|34|214|1|0|1|184| Reponse|15|16|22|16|0|2|0|0|0|1|50|10|1|144|13|122|15|130|0|0|2|220| | Request|16|34|226|1|0|1|196| Response|15|16|34|3|7|128|0|1|122 | Request|16|34|225|1|0|1|195| Response|15|16|33|4|1|2|3|4|0|253| | Request|16|34|227|1|0|1|197| Response|15|16|35|2|16|0|1|3 | Request|16|34|232|1|0|1|202| Response|15|16|40|10|0|0|0|254|1|0|0|0|0|0|1|255 |

3. Custom Names 1-10

These are the custom names that can be configured from the screenlogic interface. Bits 6+ are the Ascii characters.

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Request 16 34 202 1 0 1 172
Response 15 16 10 12 0 87 116 114 70 97 108 108 32 49 0 251 4 236
Custom Name 1 W t r F a l l 1

| Request|16|34|202|1|1|1|173 Response|15|16|10|12|1|87|116|114|70|97|108|108|32|49|46|53|4|85| Custom Name 2||||||W|t|r|F|a|l|l| |1|.|5| | Request|16|34|202|1|2|1|174| ResponseResponse|15|16|10|12|2|87|116|114|70|97|108|108|32|50|0|251|4|239 Custom Name 3||||||W|t|r|F|a|l|l| |2 | Request|16|34|202|1|3|1|175| Response|15|16|10|12|3|87|116|114|70|97|108|108|32|51|0|251|4|241||||| Custom Name 4||||||W|t|r|F|a|l|l| |3||| | Request|16|34|202|1|4|1|176| ResponseResponse|15|16|10|12|4|80|111|111|108|32|76|111|119|0|228|251|5|179 Custom Name 5||||||P|o|o|l||L|o|w|||| | Request|16|34|202|1|5|1|177| ResponseResponse|15|16|10|12|5|85|83|69|82|78|65|77|69|45|48|54|3|220 Custom Name 6||||||U|S|E|R|N|A|M|E|-|0|6 | Request|16|34|202|1|6|1|178| ResponseResponse|15|16|10|12|6|85|83|69|82|78|65|77|69|45|48|55|3|222 Custom Name 7||||||U|S|E|R|N|A|M|E|-|0|7 | Request|16|34|202|1|7|1|179 ResponseResponse|15|16|10|12|7|85|83|69|82|78|65|77|69|45|48|56|3|224 Custom Name 8||||||U|S|E|R|N|A|M|E|-|0|8 | Request|16|34|202|1|8|1|180| Response|15|16|10|12|8|85|83|69|82|78|65|77|69|45|48|57|3|226||||| Custom Name 9||||||U|S|E|R|N|A|M|E|-|0|9||||||| | Request|16|34|202|1|9|1|181| ResponseResponse|15|16|10|12|9|85|83|69|82|78|65|77|69|45|49|48|3|219||||| Custom Name 10||||||U|S|E|R|N|A|M|E|-|1|0

Request

Byte Known? Definition Details
1 Y Destination Destination Address of message
2 Y Source Address Sender Address of message
3 Y Action 202 = Request Custom Name
4 N 1 Constant?
5 Y Number Index or ID of custom name (0-9)
6 Y Checksum High Bit This bit * 256 + low bit = checksum
7 Y Checksum Low Bit

Response

Byte Known? Definition Details
1 Y Destination Destination Address of message
2 Y Source Address Sender Address of message
3 Y Action 10 = Send Custom Name
4 Y Length Number of bytes in the message after this byte
5 Y Number Index or ID of custom name (0-9)
6 Y Char1 Ascii value of custom name digit 1
7-16 Y Char2-11 Ascii value of custom name digit 2-11
17 Y Checksum High Bit This bit * 256 + low bit = checksum
18 Y Checksum Low Bit

4. Circuit Names

The 7th bit refers to the list of circuit names. The ID #'s 200-209 refer to the custom names.

Byte 1 2 3 4 5 6 7 8 9 10 11
Request 16 34 203 1 1 1 174
Response 15 16 11 5 1 1 72 0 0 1 40

| Request|16|34|203|1|2|1|175| Response|15|16|11|5|2|0|46|0|0|1|14 | Request|16|34|203|1|3|1|176| Response|15|16|11|5|3|0|2|0|0|0|227 | Request|16|34|203|1|4|1|177| Response|15|16|11|5|4|5|22|0|0|0|253 | Request|16|34|203|1|5|1|178| Response|15|16|11|5|5|64|201|0|0|1|236 | Request|16|34|203|1|6|1|179| Response|15|16|11|5|6|66|61|0|0|1|99 | Request|16|34|203|1|7|1|180| Response|15|16|11|5|7|7|74|0|0|1|54 | Request|16|34|203|1|8|1|181| Response|15|16|11|5|8|7|63|0|0|1|44 | Request|16|34|203|1|9|1|182| Response|15|16|11|5|9|7|55|0|0|1|37 | Request|16|34|203|1|10|1|183| Response|15|16|11|5|10|0|0|0|0|0|232 | Request|16|34|203|1|11|1|184| Response|15|16|11|5|11|14|79|0|0|1|70 | Request|16|34|203|1|12|1|185| Response|15|16|11|5|12|0|200|0|0|1|178 | Request|16|34|203|1|13|1|186| Response|15|16|11|5|13|0|202|0|0|1|181 | Request|16|34|203|1|14|1|187| Response|15|16|11|5|14|0|203|0|0|1|183 | Request|16|34|203|1|15|1|188| Response|15|16|11|5|15|0|64|0|0|1|45 | Request|16|34|203|1|16|1|189| Response|15|16|11|5|16|14|53|0|0|1|49 | Request|16|34|203|1|17|1|190| Response|15|16|11|5|17|14|53|0|0|1|50 | Request|16|34|203|1|18|1|191| Response|15|16|11|5|18|14|53|0|0|1|51 | Request|16|34|203|1|19|1|192| Response|15|16|11|5|19|0|0|0|0|0|241 | Request|16|34|203|1|20|1|193| Response|15|16|11|5|20|0|93|0|0|1|79

Request

Byte Known? Definition Details
1 Y Destination Destination Address of message
2 Y Source Address Sender Address of message
3 Y Action 203 = Request Name
4 N 1 Constant?
5 Y Number Index or ID of name (1-20)
6 Y Checksum High Bit This bit * 256 + low bit = checksum
7 Y Checksum Low Bit

Response

Byte Known? Definition Details
1 Y Destination Destination Address of message
2 Y Source Address Sender Address of message
3 Y Action 11 = Send Name
4 Y Length Number of bytes in the message after this byte
5 Y Number Index or ID of custom name (1-20)
6 N Type? Possibly type of circuit (eg Feature, color wheel, spa, etc)
7 Y/N Name ID for a list of names (need to get these)
8 N Unknown/future?
9 N Unknown/future?
10 Y Checksum High Bit This bit * 256 + low bit = checksum
11 Y Checksum Low Bit

5. Schedules

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Request 16 34 209 1 1 1 180
Response 15 16 17 7 1 6 9 29 15 55 255 2 88
9:29 15:55 Every Day
Request 16 34 209 1 2 1 181

| Response|15|16|17|7|2|4|14|0|15|30|181|1|220| |||||||Cleaner|14:00||15:30|| TU, TH, FR, SU
| Request|16|34|209|1|3|1|182| Response|15|16|17|7|3|1|25|0|4|0|0|1|7| |||||||Spa|Egg Timer||4 hours||
| Request|16|34|209|1|4|1|183| Response|15|16|17|7|4|6|25|0|6|30|0|1|45| |||||||Pool|Egg Timer||6 hours, 30 mins|| | Request|16|34|209|1|5|1|184| Response|15|16|17|7|5|4|25|0|4|0|0|1|12| |||||||Cleaner|Egg Timer||4 hours|| | Request|16|34|209|1|6|1|185| Response|15|16|17|7|6|15|21|10|23|55|255|2|103 |||||||Pool Low|21:10||23:55||All days | Request|16|34|209|1|7|1|186| Response|15|16|17|7|7|15|1|1|9|20|255|2|26| |||||||Pool Low|1:01||9:20AM||All days
| Request|16|34|209|1|8|1|187| Response|15|16|17|7|8|7|25|0|2|0|0|1|16| |||||||Pool Light|Egg Timer||2 hours|| | Request|16|34|209|1|9|1|188| Response|15|16|17|7|9|0|0|0|0|0|0|0|239| Empty?| | Request|16|34|209|1|10|1|189| Respons|15|16|17|7|10|9|25|0|4|15|0|1|37| |||||||Path Lights|Egg Timer||4 hours, 15 mins|| | Request|16|34|209|1|11|1|190| Response|15|16|17|7|11|11|13|0|13|10|255|2|31| |||||||Spillway|1:00pm||1:10pm||All days | Request|16|34|209|1|12|1|191| Response|15|16|17|7|12|5|13|30|13|40|145|1|232| |||||||Spa|1:30pm||1:40pm||Tu, Thu

Request

Byte Known? Definition Details
1 Y Destination Destination Address of message
2 Y Source Address Sender Address of message
3 Y Action 209 = Get Schedule
4 Y 1 Constant; possibly pool address?
5 Y Schedule # Schedule 1-12
6 Y Checksum High Bit This bit * 256 + low bit = checksum
7 Y Checksum Low Bit

Response

Byte Known? Definition Details
1 Y Destination Destination Address of message
2 Y Source Address Sender Address of message
3 Y Action 17 = Schedule (as previously saved)
4 Y Length Number of bytes in the message after this byte
5 Y ID Schedule ID/# (1-12)
6 N Circuit Which circuit is the schedule on?
7 Y Start Hour If 25, then egg timer; if 1-24 then Start Hour
8 Y Start Min Ignore if egg timer, else minute
9 Y End Hour If egg timer, then # of hours. Else end hour of schedule.
10 Y End Min If egg timer, then # of minutes. Else end minutes of schedule.
11 Y Days of week Bitmask 0x0000000; 181 = Tu,Th,Fri,Sun; 145 = Thu,Sun; 255 = Every day; Need to do more research but it seems like 0x01 is always active and 128=Sun; 16=Thu... need to just do some testing.
12 Y Checksum High Bit This bit * 256 + low bit = checksum
13 Y Checksum Low Bit

6. Heat Set Points

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Request 16 34 200 1 0 1 170
Response Heat/Temp 15 16 8 13 86 86 84 86 100 7 0 0 87 0 0 0 0 2 251

7. Unknown??

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Request 16 34 231 1 0 1 201
Response 15 16 39 32 7 0 0 0 8 0 0 0 9 0 0 0 0 0

8. Date/Time

Byte 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Request 15 16 5 8 19 46 4 31 5 16 0 1 1 85
Missing response??
Clone this wiki locally