Nothing yet, because of the command character issue. Basically the first thing the plugin does is disable itself (by setting the command character to something it's not expecting).

I see now that ascii 35 is the # char, but the command going to the serial adaper is setting the command character to '35' - of which only the 3 is used.

So the rest of the time the plugin spends its life sending stuff like "#AIRTMP?" when the adapter now needs to see "3AIRTMP?", and simply responds with INVALID COMMAND.

I can reset the command character manually, but to do so I have to disconnect the plugin from the serial port, connect manually with a terminal program, make the change and reactivate the plugin. First thing the plugin does? Change the command char back to 3.

This problem looks like it would affect any serial adapter, be it Pentair or Jandy. How does this work on your setup?

I think this all may have to do with the "end of response" character and ECHO command.

Can you post or send me by e-mail a copy of the log that you get when the device starts communication? This will help to figure out exactly what's going on.

My system sends and receives all of these commands with no problem.

Jim

I don't think so. The thing is: the first command actually works. The problem is that it's the wrong command.

When you send:

Code: Select all

#CMDCHR=35

It executes perfectly. I can confirm that the command character is indeed now set to '3'. Unfortunately, the plugin wants it to be '#' and now no other command the plugin sends is read correctly.

When I get home this afternoon, I'll post the logs, but that first line is definitely a problem. There may be some additional issue with LF characters, etc... but that remains to be seen.

Swancoat wrote:I don't think so. The thing is: the first command actually works. The problem is that it's the wrong command.

When you send:

Code: Select all

#CMDCHR=35

It executes perfectly. I can confirm that the command character is indeed now set to '3'. Unfortunately, the plugin wants it to be '#' and now no other command the plugin sends is read correctly.

When I get home this afternoon, I'll post the logs, but that first line is definitely a problem. There may be some additional issue with LF characters, etc... but that remains to be seen.

I think there is a problem with end-of-line for both send and receive - which is why the initial command is being truncated. The Jandy system expects a <CR> at the end of a command, but it seems the Pentair system expects something else, hence is truncating the last "real" character of the commands (in this case the 5 from 35).

The full debug log should help to determine this, but I will look again at the Pentair manual to see if there's anything that might help.

I created and e-mailed to you a stripped down version of the plugin for you to try, that gets rid of the command parsing, allowing you to send whatever command you like, and also provides the debugging automatically to determine what the Pentair system might be expecting.

Jim

So here's what I get when I activate the plugin:

Code: Select all

Sep 27, 2011 9:23:54 PM
  Enabling plugin "Jandy Aqualink Plugin 0.9.5"
  Starting plugin "Jandy Aqualink Plugin 0.9.5"
  Plugin "Jandy Aqualink Plugin" connected
  Plugin "Jandy Aqualink Plugin 0.9.5" started
  Jandy Aqualink Plugin Debug     <<-- entering deviceStartComm, Device: Pool Equipment; ID=903457918, Type=jandyAqualink-RS-8-Combo
  Jandy Aqualink Plugin Debug     Serial Port Name is /dev/cu.KeySerial1
  Jandy Aqualink Plugin Debug     Device name is Pool Equipment
  Jandy Aqualink Plugin           Logging of Jandy state changes set to log all changes.
  Jandy Aqualink Plugin Debug     In queue: #ECHO=0
  Jandy Aqualink Plugin Debug     In queue: #RSPFMT=0
  Jandy Aqualink Plugin Debug     In queue: #CMDCHR=35
  Jandy Aqualink Plugin Debug     In queue: #NRMCHR=33
  Jandy Aqualink Plugin Debug     In queue: #ERRCHR=63
  Jandy Aqualink Plugin Debug     In queue: #UNITS?
  Jandy Aqualink Plugin Debug     In queue: #LEDS?
  Jandy Aqualink Plugin Debug     In queue: #POOLSP?
  Jandy Aqualink Plugin Debug     In queue: #SPASP?
  Jandy Aqualink Plugin Debug     In queue: #POOLTMP?
  Jandy Aqualink Plugin Debug     In queue: #SPATMP?
  Jandy Aqualink Plugin Debug     In queue: #AIRTMP?
  Jandy Aqualink Plugin Debug     In queue: #COSMSGS=1
  Jandy Aqualink Plugin Debug     Starting concurrent serial communications.
  Jandy Aqualink Plugin Debug     Started concurrent thread.
  Jandy Aqualink Plugin Debug     exiting deviceStartComm -->>
  Jandy Aqualink Plugin Debug     Queue has 13 command(s) waiting.
  Jandy Aqualink Plugin Debug     Processing command: #ECHO=0
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #ECHO=0 command completed.
  Jandy Aqualink Plugin Debug     Processing command: #RSPFMT=0
  Jandy Aqualink Plugin Debug     Returned string is !00 RSPFMT = 0
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 RSPFMT = 0
, of length 15 characters
  Jandy Aqualink Plugin           Faulty response: !00 RSPFMT = 0
  Jandy Aqualink Plugin Debug     #RSPFMT=0 command completed.
  Jandy Aqualink Plugin Debug     Processing command: #CMDCHR=35
  Jandy Aqualink Plugin Debug     Returned string is !00 CMDCHR = 3
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 CMDCHR = 3
, of length 15 characters
  Jandy Aqualink Plugin           Faulty response: !00 CMDCHR = 3
  Jandy Aqualink Plugin Debug     #CMDCHR=35 command completed.
  Jandy Aqualink Plugin Debug     Processing command: #NRMCHR=33
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #NRMCHR=33 command completed.
  Jandy Aqualink Plugin Debug     Processing command: #ERRCHR=63
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #ERRCHR=63 command completed.
  Jandy Aqualink Plugin Debug     Processing command: #UNITS?
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #UNITS? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #LEDS?
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #LEDS? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #POOLSP?
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #POOLSP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #SPASP?
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #SPASP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #POOLTMP?
  Jandy Aqualink Plugin           Valves set to .  Cannot determine pool temperature; set to N/A.
  Jandy Aqualink Plugin Debug     Processing command: #SPATMP?
  Jandy Aqualink Plugin           Valves set to .  Cannot determine spa temperature; set to N/A.
  Jandy Aqualink Plugin Debug     Processing command: #AIRTMP?
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #AIRTMP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #COSMSGS=1
  Jandy Aqualink Plugin Debug     Returned string is ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     Remaining response to decode: ?01 INVALID COMMAND
, of length 20 characters
  Jandy Aqualink Plugin           Faulty response: ?01 INVALID COMMAND
  Jandy Aqualink Plugin Debug     #COSMSGS=1 command completed.


So you can see, when you tell the Pentair adapter to set CMDCHR to 35, it does not see that as '#'. It sees it as '35' and of course only takes the first character. My command character is now a 3, so I have to change it manually in a terminal.

Prior to that happening (which derails everything else) it seems like things are flowing too and from the serial adapter with no problem. The ECHO command doesn't seem to be available on the Pentair, but RSPFMT is. The response is appropriate too, but must differ from Jandy's response as the plugin doesn't seem to like it.

This time around, I made a small edit to your python code (hope that's ok!) and basically commented out a lot of the configure code so it looks like this now. (My serial adapter is set to those settings anyway as they are defaults).

Code: Select all

#         self.queueSerialCmd("#ECHO=0")   
#         self.queueSerialCmd("#RSPFMT=0")
#         self.queueSerialCmd("#CMDCHR=35")
#         self.queueSerialCmd("#NRMCHR=33")
#         self.queueSerialCmd("#ERRCHR=63")
#         self.queueSerialCmd("#UNITS?")
#         self.queueSerialCmd("#MODEL?")      # May use Model and Options in the future to
#         self.queueSerialCmd("#OPTIONS?")   # validate or set up device w/o user intervention.
#         self.queueSerialCmd("#LEDS?")
         self.queueSerialCmd("#POOLSP?")
         self.queueSerialCmd("#SPASP?")
         self.queueSerialCmd("#POOLTMP?")
         self.queueSerialCmd("#SPATMP?")
         if devProps["solHeatCheckbox"] == True:         
            self.queueSerialCmd("#SOLTMP?")
         self.queueSerialCmd("#AIRTMP?")
         self.queueSerialCmd("#COSMSGS=1")         


That returned this log on startup.

Code: Select all

Sep 27, 2011 9:32:23 PM
  Enabling plugin "Jandy Aqualink Plugin 0.9.5"
  Starting plugin "Jandy Aqualink Plugin 0.9.5"
  Plugin "Jandy Aqualink Plugin" connected
  Plugin "Jandy Aqualink Plugin 0.9.5" started
  Jandy Aqualink Plugin Debug     <<-- entering deviceStartComm, Device: Pool Equipment; ID=903457918, Type=jandyAqualink-RS-8-Combo
  Jandy Aqualink Plugin Debug     Serial Port Name is /dev/cu.KeySerial1
  Jandy Aqualink Plugin Debug     Device name is Pool Equipment
  Jandy Aqualink Plugin           Logging of Jandy state changes set to log all changes.
  Jandy Aqualink Plugin Debug     In queue: #POOLSP?
  Jandy Aqualink Plugin Debug     In queue: #SPASP?
  Jandy Aqualink Plugin Debug     In queue: #POOLTMP?
  Jandy Aqualink Plugin Debug     In queue: #SPATMP?
  Jandy Aqualink Plugin Debug     In queue: #AIRTMP?
  Jandy Aqualink Plugin Debug     In queue: #COSMSGS=1
  Jandy Aqualink Plugin Debug     Starting concurrent serial communications.
  Jandy Aqualink Plugin Debug     Started concurrent thread.
  Jandy Aqualink Plugin Debug     exiting deviceStartComm -->>
  Jandy Aqualink Plugin Debug     Queue has 6 command(s) waiting.
  Jandy Aqualink Plugin Debug     Processing command: #POOLSP?
  Jandy Aqualink Plugin Debug     Returned string is !00 POOLSP = 78 F
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 POOLSP = 78 F
, of length 18 characters
  Jandy Aqualink Plugin           Faulty response: !00 POOLSP = 78 F
  Jandy Aqualink Plugin Debug     #POOLSP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #SPASP?
  Jandy Aqualink Plugin Debug     Returned string is !00 SPASP = 103 F
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 SPASP = 103 F
, of length 18 characters
  Jandy Aqualink Plugin           Faulty response: !00 SPASP = 103 F
  Jandy Aqualink Plugin Debug     #SPASP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #POOLTMP?
  Jandy Aqualink Plugin           Valves set to .  Cannot determine pool temperature; set to N/A.
  Jandy Aqualink Plugin Debug     Processing command: #SPATMP?
  Jandy Aqualink Plugin           Valves set to .  Cannot determine spa temperature; set to N/A.
  Jandy Aqualink Plugin Debug     Processing command: #AIRTMP?
  Jandy Aqualink Plugin Debug     Returned string is !00 AIRTMP = 81 F
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 AIRTMP = 81 F
, of length 18 characters
  Jandy Aqualink Plugin           Faulty response: !00 AIRTMP = 81 F
  Jandy Aqualink Plugin Debug     #AIRTMP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #COSMSGS=1
  Jandy Aqualink Plugin Debug     Returned string is !00 COSMSGS = 1
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 COSMSGS = 1
, of length 16 characters
  Jandy Aqualink Plugin           Faulty response: !00 COSMSGS = 1
  Jandy Aqualink Plugin Debug     #COSMSGS=1 command completed.

So now without the CMDCHR problem, commands flow to and from the adapter again, but the responses look like they must differ from what is expected from a Jandy adapter.

So, after all of that, we can TALK to the adapter alright, but perhaps the protocols aren't quite as similar as I had hoped and I'm not going to ride on the coattails of the Jandy guys!.

Thanks to yergeyj for all of your efforts over the past couple of days!

Swancoat wrote:This time around, I made a small edit to your python code (hope that's ok!) and basically commented out a lot of the configure code so it looks like this now. (My serial adapter is set to those settings anyway as they are defaults).

Code: Select all

#         self.queueSerialCmd("#ECHO=0")   
#         self.queueSerialCmd("#RSPFMT=0")
#         self.queueSerialCmd("#CMDCHR=35")
#         self.queueSerialCmd("#NRMCHR=33")
#         self.queueSerialCmd("#ERRCHR=63")
#         self.queueSerialCmd("#UNITS?")
#         self.queueSerialCmd("#MODEL?")      # May use Model and Options in the future to
#         self.queueSerialCmd("#OPTIONS?")   # validate or set up device w/o user intervention.
#         self.queueSerialCmd("#LEDS?")
         self.queueSerialCmd("#POOLSP?")
         self.queueSerialCmd("#SPASP?")
         self.queueSerialCmd("#POOLTMP?")
         self.queueSerialCmd("#SPATMP?")
         if devProps["solHeatCheckbox"] == True:         
            self.queueSerialCmd("#SOLTMP?")
         self.queueSerialCmd("#AIRTMP?")
         self.queueSerialCmd("#COSMSGS=1")         


That returned this log on startup.

Code: Select all

Sep 27, 2011 9:32:23 PM
  Enabling plugin "Jandy Aqualink Plugin 0.9.5"
  Starting plugin "Jandy Aqualink Plugin 0.9.5"
  Plugin "Jandy Aqualink Plugin" connected
  Plugin "Jandy Aqualink Plugin 0.9.5" started
  Jandy Aqualink Plugin Debug     <<-- entering deviceStartComm, Device: Pool Equipment; ID=903457918, Type=jandyAqualink-RS-8-Combo
  Jandy Aqualink Plugin Debug     Serial Port Name is /dev/cu.KeySerial1
  Jandy Aqualink Plugin Debug     Device name is Pool Equipment
  Jandy Aqualink Plugin           Logging of Jandy state changes set to log all changes.
  Jandy Aqualink Plugin Debug     In queue: #POOLSP?
  Jandy Aqualink Plugin Debug     In queue: #SPASP?
  Jandy Aqualink Plugin Debug     In queue: #POOLTMP?
  Jandy Aqualink Plugin Debug     In queue: #SPATMP?
  Jandy Aqualink Plugin Debug     In queue: #AIRTMP?
  Jandy Aqualink Plugin Debug     In queue: #COSMSGS=1
  Jandy Aqualink Plugin Debug     Starting concurrent serial communications.
  Jandy Aqualink Plugin Debug     Started concurrent thread.
  Jandy Aqualink Plugin Debug     exiting deviceStartComm -->>
  Jandy Aqualink Plugin Debug     Queue has 6 command(s) waiting.
  Jandy Aqualink Plugin Debug     Processing command: #POOLSP?
  Jandy Aqualink Plugin Debug     Returned string is !00 POOLSP = 78 F
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 POOLSP = 78 F
, of length 18 characters
  Jandy Aqualink Plugin           Faulty response: !00 POOLSP = 78 F
  Jandy Aqualink Plugin Debug     #POOLSP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #SPASP?
  Jandy Aqualink Plugin Debug     Returned string is !00 SPASP = 103 F
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 SPASP = 103 F
, of length 18 characters
  Jandy Aqualink Plugin           Faulty response: !00 SPASP = 103 F
  Jandy Aqualink Plugin Debug     #SPASP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #POOLTMP?
  Jandy Aqualink Plugin           Valves set to .  Cannot determine pool temperature; set to N/A.
  Jandy Aqualink Plugin Debug     Processing command: #SPATMP?
  Jandy Aqualink Plugin           Valves set to .  Cannot determine spa temperature; set to N/A.
  Jandy Aqualink Plugin Debug     Processing command: #AIRTMP?
  Jandy Aqualink Plugin Debug     Returned string is !00 AIRTMP = 81 F
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 AIRTMP = 81 F
, of length 18 characters
  Jandy Aqualink Plugin           Faulty response: !00 AIRTMP = 81 F
  Jandy Aqualink Plugin Debug     #AIRTMP? command completed.
  Jandy Aqualink Plugin Debug     Processing command: #COSMSGS=1
  Jandy Aqualink Plugin Debug     Returned string is !00 COSMSGS = 1
  Jandy Aqualink Plugin Debug     Remaining response to decode: !00 COSMSGS = 1
, of length 16 characters
  Jandy Aqualink Plugin           Faulty response: !00 COSMSGS = 1
  Jandy Aqualink Plugin Debug     #COSMSGS=1 command completed.

So now without the CMDCHR problem, commands flow to and from the adapter again, but the responses look like they must differ from what is expected from a Jandy adapter.

So, after all of that, we can TALK to the adapter alright, but perhaps the protocols aren't quite as similar as I had hoped and I'm not going to ride on the coattails of the Jandy guys!.

Thanks to yergeyj for all of your efforts over the past couple of days!

Jeremy,

I think I've figured it out, from this log and the one you posted for Simple Serial.

1 - The Pentair system expects a <CR> rather than <CR><LF> at the end of a response. I can send a version to you (I'll even change all the "Jandy" to "Pentair" in case it works correctly) that I think should slve this problem.

2 - The Pentair system doesn't use the ASCII number codes for setting command characters, it uses the actual characters, e.g. it should have #CMDCHR=#, not #CMDCHR=35. I also agree with your logic, and will remove these commands at the start of the communications, but will likely add some code to do a serial adaptor reset, and check that it returns the correct response, before finishing up the startComm routine, as I need to make sure the adaptor can properly communicate. I won't get this piece for a few days.

3 - The Pentair system does not have the equivalent of the ECHO command. It always and only responds with a <CR>, and never echoing back the full command sent.

I'll try to get you something tonight, but have to head off to work now (EDT).

Jim

On the topic of using this plugin for Pentair IntelliTouch pool/spa systems:

I have created a version of the plugin that may support the Pentair IntelliTouch system; it is being tested, but if anyone else is interested, please send me a PM.

Differences from the current (0.9.5) version of the Jandy Aqualink plugin:

1 - Model selection is still based on Jandy numbering (RS-4, etc.) but hopefully that works for your system "ok" for now. I've tried to change all of the terminology to Pentair IntelliTouch from Jandy Aqualink.

2 - I've removed all of the initial commands except the ones we think should work properly. I will probably put back some sort of reset command with check that it operates correctly, as I had a few problems with the AppleScripts that folks didn't have ECHO or command characters set correctly. I'd like to have the plugin "error proofed."

3 - I've changed the response EOL expected to a <CR> rather than <LF>, but … the character count may or may not be off by one for every response, so let me know what you log shows; the Jandy sends a <CR><LF>, so I'm expecting the character count may be off, and too may characters may get stripped from any response that is multiple.

4 - I do not think the Pentair system has an equivalent to the #LED command. If it turns out this is the case, I will strip out the extensive decoding for this command from the plugin.

Keep in mind that with COSMSGS enabled, there may be "responses" coming from the adaptor for things like temperature changes at the same time as responses for commands that you intentionally send; these should be parsed correctly.

Jim

Closer...

This thing starts up and runs no problem. However, it still seems to choke on the response from the Pentair Adapter. Not sure why...

Here's what you get on startup

Code: Select all

Enabling plugin "Pentair IntelliTouch Plugin 0.9.5"
  Starting plugin "Pentair IntelliTouch Plugin 0.9.5"
  Plugin "Pentair IntelliTouch Plugin" connected
  Plugin "Pentair IntelliTouch Plugin 0.9.5" started
  Pentair IntelliTouch Plugin Debug <<-- entering deviceStartComm, Device: Pool Equipment; ID=1114660597, Type=pentairIntelliTouch-RS-8-Combo
  Pentair IntelliTouch Plugin Debug Serial Port Name is /dev/cu.KeySerial1
  Pentair IntelliTouch Plugin Debug Device name is Pool Equipment
  Pentair IntelliTouch Plugin     Logging of Pentair state changes set to log all but temperature changes.
  Pentair IntelliTouch Plugin Debug In queue: #PUMP?
  Pentair IntelliTouch Plugin Debug In queue: #SPA?
  Pentair IntelliTouch Plugin Debug In queue: #POOLSP?
  Pentair IntelliTouch Plugin Debug In queue: #SPASP?
  Pentair IntelliTouch Plugin Debug In queue: #POOLTMP?
  Pentair IntelliTouch Plugin Debug In queue: #SPATMP?
  Pentair IntelliTouch Plugin Debug In queue: #AIRTMP?
  Pentair IntelliTouch Plugin Debug In queue: #COSMSGS=1
  Pentair IntelliTouch Plugin Debug Starting concurrent serial communications.
  Pentair IntelliTouch Plugin Debug Started concurrent thread.
  Pentair IntelliTouch Plugin Debug exiting deviceStartComm -->>
  Pentair IntelliTouch Plugin Debug Queue has 8 command(s) waiting.
  Pentair IntelliTouch Plugin Debug Processing command: #PUMP?
  Pentair IntelliTouch Plugin Debug Returned string is !00 PUMP = 0
  Pentair IntelliTouch Plugin Debug Remaining response to decode: !00 PUMP = 0
, of length 13 characters
  Pentair IntelliTouch Plugin Debug Should now stop concurrent thread.


Also, I can confirm that the LED command is not operable on the Pentair.

Swancoat wrote:Closer...

This thing starts up and runs no problem. However, it still seems to choke on the response from the Pentair Adapter. Not sure why...

Here's what you get on startup

Code: Select all

Enabling plugin "Pentair IntelliTouch Plugin 0.9.5"
  Starting plugin "Pentair IntelliTouch Plugin 0.9.5"
  Plugin "Pentair IntelliTouch Plugin" connected
  Plugin "Pentair IntelliTouch Plugin 0.9.5" started
  Pentair IntelliTouch Plugin Debug <<-- entering deviceStartComm, Device: Pool Equipment; ID=1114660597, Type=pentairIntelliTouch-RS-8-Combo
  Pentair IntelliTouch Plugin Debug Serial Port Name is /dev/cu.KeySerial1
  Pentair IntelliTouch Plugin Debug Device name is Pool Equipment
  Pentair IntelliTouch Plugin     Logging of Pentair state changes set to log all but temperature changes.
  Pentair IntelliTouch Plugin Debug In queue: #PUMP?
  Pentair IntelliTouch Plugin Debug In queue: #SPA?
  Pentair IntelliTouch Plugin Debug In queue: #POOLSP?
  Pentair IntelliTouch Plugin Debug In queue: #SPASP?
  Pentair IntelliTouch Plugin Debug In queue: #POOLTMP?
  Pentair IntelliTouch Plugin Debug In queue: #SPATMP?
  Pentair IntelliTouch Plugin Debug In queue: #AIRTMP?
  Pentair IntelliTouch Plugin Debug In queue: #COSMSGS=1
  Pentair IntelliTouch Plugin Debug Starting concurrent serial communications.
  Pentair IntelliTouch Plugin Debug Started concurrent thread.
  Pentair IntelliTouch Plugin Debug exiting deviceStartComm -->>
  Pentair IntelliTouch Plugin Debug Queue has 8 command(s) waiting.
  Pentair IntelliTouch Plugin Debug Processing command: #PUMP?
  Pentair IntelliTouch Plugin Debug Returned string is !00 PUMP = 0
  Pentair IntelliTouch Plugin Debug Remaining response to decode: !00 PUMP = 0
, of length 13 characters
  Pentair IntelliTouch Plugin Debug Should now stop concurrent thread.


Also, I can confirm that the LED command is not operable on the Pentair.

Sorry, seems like there's a bug specific to the #PUMP? command that I somehow missed - aaargh!

Also, your log indicates that I do need to adjust the string math by one character.

I'll try to get you an adjusted plugin no later than tomorrow. Depends how long this Phillies / Braves game goes!

Jim

Found the error for the #PUMP and #SPA commands; fixed and edited main post to version 0.9.6.

Also fixed the string math for the Pentair version.

Jim

Declare Victory. It is working!

Thank you so much for all the mods to your plugin: I was just hoping to piggyback on the Jandy stuff since the protocol looked similar. I had no idea it would turn into a whole new plugin!

Swancoat wrote:Declare Victory. It is working!

Thank you so much for all the mods to your plugin: I was just hoping to piggyback on the Jandy stuff since the protocol looked similar. I had no idea it would turn into a whole new plugin!

Great to hear!

Can you post what equipment, AUX in particular, you have working, as this might help me know what features are now considered "operational" that I was not able to test on my system.

Thanks,
Jim

I basically have it all working. I haven't given everything a FULL shakedown, but I do have access to every device on the Intellitouch (except the water feature, but it is AUX41).

States are appearing to update correctly when activated outside of the plugin as well.

Swancoat wrote:I basically have it all working. I haven't given everything a FULL shakedown, but I do have access to every device on the Intellitouch (except the water feature, but it is AUX41).

For the water feature (AUX41), have you tried the action to send a direct command, e.g. "#AUX41=ON" to see if that works? In theory it should, and if so, I could possibly modify the code to allow AUX values higher than the current default of 8.

Also, if the direct command works, let me know what response the Pentair system sends back, as that would help to determine whether I could readily add a device state that would be kept up-to-date by the COSMSGS stream as well.

Jim