[sphelps]

This is not an anti-profilux campaign, from the start here my goal was very clear to make others Profilux users, many of which I consider friends, aware of what I believe to be an issue. However I have no control how others choose to use this information. I have provided only fact or exactly what I was told by support staff to which I can only assume to be fact.

To come here and instantly state my intentions being only to damage Profilux clearly illustrates Profilux owner failed to even read the first post of this thread. It's also insulting to a customer who has been with Profilux virtually from the start and at times aiding in many sales, setup and support. Be aware I also received comments from support staff that I found insulting however these have since been removed and even my posts on the support forum were edited which may have made my comments look overly full of frustration while the only real frustration came from first being insulted and the issue being shrugged off as user error. In addition I can conclude all Profilux staff has failed to even fully understand the issue as despite my numerous attempts of stating reasoning for my max on time it's continuously blamed as an issue. Top off water is added slowly, 10min has prematurely set off alarms in the past on summer days, 20min is a perfectly reasonable number given how my system operates. Increasing flow rate and decreasing on time will do absolutely nothing in regards to this issue. While support staff claims to attempting to propose solutions, in my eyes their goal seemed more related to pointing blame which is not a solution. If you're looking for an example of an actual solution I posted one in this thread.

In regards to a float sensor, again I've said numerous times, I don't care. I found it alarming that such things can expire which is I pointed it out as one of the issues people should be aware of. The fact the owner of the company calls this complete nonsense and then reverts back stating otherwise after discovering what support staff has stated is rather amusing. Also be aware support staff strongly felt the use of stored sensor was a clear issue and the key to whole failure, not something they just had to say because in extremely rare cases it could happen. Also note according to GHL sensor is 4 years old while I purchased it approximately 2 years ago. I have no intention of getting retailers involved but just be aware obviously inventory of such devices are not controlled despite what support staff suggests. At the very least adding a date of manufacture that the rest of the world can understand might not be a bad idea.

In regards to the real issue I'm glad revisions are being made which is what I wanted. It's obvious without such a thread nothing would have been done. Again I have no intentions of destroying Profilux reputation or boycotting nor do I have interest in compensation or warranty replacement.

My initial attempts on the profilux support forum were to first find out out if what I believe to be an issue is related to perhaps just a firmware bug or perhaps just something only relating to my device alone. If this was not the case I thought pointing out some issues would be in the best interest of everyone and my hopes were profilux staff would take this more seriously and at least notify both the public and the owner of the company. As I suspected they did neither hence why I left that site and came here. I also wanted a reason to why something as critical as an error alarm can be so easily reset, obviously there is a reason for this as the the developer has now stated yet I still wait for it. If the reason is sound stating it would justify it's existence perhaps turning what I consider a flaw into a feature I just wasn't aware of.

As a professional engineer I have obligations towards public interest in all aspects of my life, not doing my best to make the public aware of this goes against not only these ethical obligations but also my personal beliefs.