Warning to Profilux Users

[sphelps]

Stanky, you might be looking at a bit of a different issue than I'm discussing here. I think you may experiencing a more typical issue of the float becoming temporarily stuck and your max on time is set too high.

First check your float switch:

• Using the 5 button section on your profilux controller do the following:
• Press the left direction arrow button
• Scroll through the options with the up or down arrow buttons until you see "level"
• Press the center or enter button
• Again scroll through the options until you see "diagnostic"
• Press the center or enter button
  
• Now you will see a number "1" and a number "2" each with either a "-" or "X" next to them. Your float should be corresponding to # 1 with "-" meaning on and "X" meaning off. Moving the float up and down should switch between these. If moving the float shows no response then you likely have a completely failed float.

Next check your max on time

• Repeat step above until you enter the level menu again but instead of diagnostic scroll and enter "sensor settings"
• It'll ask what sensor to either, using up and down arrow buttons pick the number that was previously responding which should be 1
• Next select "auto top off"
• Next it will ask "auto top off always" answer yes for now
• Next it will ask "reaction time", 10 seconds is probably a good number for now
• Next it will ask "Max on time" this is the key, what does it say now? Given you're using a pump and bucket type ATO 1 min is probably all you need if that. You can determine this number better in the next step
• Next it will ask "Aut. error reset", select no
• Next it will ask "Input reverse", select no
• Next it will ask "Save now", select yes

Now the tricky part.

• You need to determine an appropriate max on time for the top off. Something that's long enough to top the tank off but not long enough to cause issues. Plug the top off pump into a powered socket and time how long it takes to pump water from the bottom of the float to the top of the float/ Should be a good bench mark for a max on time.
• Once an appropriate time is established repeat the previous step and update the max on time.

[STANKYfish]

[quote=sphelps;733669]Stanky, you might be looking at a bit of a different issue than I'm discussing here. I think you may experiencing a more typical issue of the float becoming temporarily stuck and your max on time is set too high.

Oopps, you are right, just talked to Shane shortly after writing and he informed me that it is not the same issue Thank you so much for taking the time to give me instructions to fix my problem. I will now leave your thread