Replies: 3 comments 1 reply
-
|
I also tested v8 in a separate folder. Same behavior. v8 details:
Relevant v8 startup: First repeated valid broadcast packet: So this does not appear to be v9-specific. |
Beta Was this translation helpful? Give feedback.
-
|
Update: I patched the detection condition locally and it now works. After removing the IntelliCenter detection condition: njsPC now detects: It discovered my real circuits: It also discovered valves: So for my IntelliTouch i9+3 Rev B / part 520074, model bytes [0,2] should not be classified as IntelliCenter. I have fully tested all functions, and it is working great! I would like to see this patched in the codebase so when I do pulls, I get code that will work with my system. Thanks!! |
Beta Was this translation helpful? Give feedback.
-
|
My pleasure, and thank you for all the hard work on this! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m trying to connect nodejs-poolController to an existing Pentair IntelliTouch i9+3 system over RS-485.
Hardware:
Software:
Problem:
njsPC detects the controller as IntelliCenter even though the board is IntelliTouch i9+3.
Startup log:
Starting Pool System undefined
Listening for any installed OCPs
RESETTING DATA -- Controller type changed from undefined to intellicenter
Found Controller Board IntelliCenter, awaiting installed modules.
Observed state:
Example received packet:
255,0,255,165,18,19,16,110,2,0,0,1,74
What I’ve tried:
Question:
Is there a way to force detection as IntelliTouch/i9+3, or does this look like an auto-detection issue that needs a replay capture?
Attached reply capture and board photo. Board is old, around 2006 I believe.
packetLog(2026-05-01_10-33-46).log
Beta Was this translation helpful? Give feedback.
All reactions