- Feb 28, 2024
- 2
- Pool Size
- 15000
- Surface
- Plaster
- Chlorine
- Salt Water Generator
- SWG Type
- Pentair Intellichlor IC-40
Hi all,
So I have an intellicenter automation panel with a IntelliFlo3 VSF pump and MasterTemp 400 HD gas heater. Both the pump and heater are controlled via RS485. When I turn the heater on(via the intellicenter) the heater will accept the set point specified, and also the pump will ramp up to the specified speed. This is all as expected, however when the pool heater reaches the set point the heater turns off(also as expected) but the intellicenter does not recognize that the heater has shut off(still shows it in heating mode). As a result the intellicenter does not show the heater as idle and will not ramp the pump back down to its normal speed. The heater and the pump are both clearly communicating with the intellicenter so I am not sure why the intellicenter is not recognizing the heater as idle which leaves my pump running at the higher speed setting intended for heating mode. I am thinking about flashing to the newest firmware to see if that may correct this issue. Any thoughts?
So I have an intellicenter automation panel with a IntelliFlo3 VSF pump and MasterTemp 400 HD gas heater. Both the pump and heater are controlled via RS485. When I turn the heater on(via the intellicenter) the heater will accept the set point specified, and also the pump will ramp up to the specified speed. This is all as expected, however when the pool heater reaches the set point the heater turns off(also as expected) but the intellicenter does not recognize that the heater has shut off(still shows it in heating mode). As a result the intellicenter does not show the heater as idle and will not ramp the pump back down to its normal speed. The heater and the pump are both clearly communicating with the intellicenter so I am not sure why the intellicenter is not recognizing the heater as idle which leaves my pump running at the higher speed setting intended for heating mode. I am thinking about flashing to the newest firmware to see if that may correct this issue. Any thoughts?