iorewasset.blogg.se

1. #PENTAIR SCREENLOGIC INTERFACE WIRELESS LINK TROUBLESHOOTING SERIAL#
2. #PENTAIR SCREENLOGIC INTERFACE WIRELESS LINK TROUBLESHOOTING DRIVER#
3. #PENTAIR SCREENLOGIC INTERFACE WIRELESS LINK TROUBLESHOOTING SOFTWARE#

Here is the link to the smartthings topic smartthings pentair. I have screenlogic and do the same thing as you, use a rs232 usb adapter hooked up to the wireless screenlogic adapter inside my house. I am able to pull all the information using a js.node program that was developed for smartthings. Perhaps when bPentair get a little further along, i can look at the differences between intellitouch and intellicenter and intelliconect. as an example, the screenshot is real/live data. but even then i'm not sure you can get the info into/do anything about it in C4. you can not get this info from iLink ($200) but can via pentair's screenlogic2 ($500+).

#PENTAIR SCREENLOGIC INTERFACE WIRELESS LINK TROUBLESHOOTING SERIAL#

of course, you will need a serial connection between your c4 controller and pentiar but everyone added that during construction, right! also would need a $10 rs485rs232 protocol adapter and because i'm running this on my development ea1, i needed a $15 3.5mm to rs232 adapter.Īlso, as noted above, a direct connection gives you access to everything on the bus - iChem, iChlor, detail pump info, etc. by going direct, you can bypass MQTT (your entire network really) and not get caught by a change in pentair's MQTT interface and not require a separate box as noted above.

disclaimer is that i have an intellitouch, not an intelliconect, but the intelliconect uses the same serial connection to talk to other pentair equipment.

#PENTAIR SCREENLOGIC INTERFACE WIRELESS LINK TROUBLESHOOTING DRIVER#

This is what you do, or more specifically, what i'm doing: i wrote a pool proxy driver "bPentair" (not released) with the ability to directly read/write to the Pentair serial bus. part of the issue is the c4 pentair driver (functionality and including an issue or two i have with the c4 pool proxy) and part the pentair iLink. I ended up drilling a small hole in the back, above the trace at pin4, in hopes of cutting the trace with a small drill bit or blade.My current pentair integration is probably the weakest and least reliable component in my setup. it's a little more difficult because the shell is fused and cannot be disassembled. I have since performed the same "hack" on a PSL4 wireless controller. Notice the hole in the pin 1-2 trace loop on an 8 button keypad. you could of course do the same thing with a blade. I didn't cut the loop trace on this particular controller, but if I had the controller would illuminate the LEDs for aux circuits 4-7 when they are active.īelow is an 8-button keypad cut off a wireless unit, showing the hole that breaks the loop trace.

on an 8 button keypad the loop trace is broken, but it is in-tact on a 4 button keypad. There's a loop trace from pin 1 to pin 2 that identifies the controller as having 4 or 8 buttons. It does still only have 4 buttons, but if really needed more, I could mount some switches, wire them to the keypad connector, and make one last keypad modification. it can program extra schedules and timers which is what I was hoping for. This modified indoor controller will now work as an Easytouch 8 with my outdoor board. **The early PSL4 firmware used a different "s19" file than the other ET4/8 controllers, but since 2.160 it's been combined to a single file - so that's what I used here. We've now got an Easytouch 8 controller (there are still only 4 buttons!)

#PENTAIR SCREENLOGIC INTERFACE WIRELESS LINK TROUBLESHOOTING SOFTWARE#

Pin 4 is 4th from the left, Pin 1 is indicated by the arrow.Īfter cutting the keypad trace and updating the firmware to 2.160**, the Software Revision now reports that this unit is an Easytouch 8 running 2.160.