-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error code 128? #17
Comments
The Rinse Aid algorithm runs shortly after the door is closed. This is expected behavior for your model without the hardware to detect rinse aid level. |
So error code 128 means something failed in the rinse aid algorithm? |
I apologize for the cryptic response there. Fault Code 128 is logged when Rinse Aid is detected low. |
Ah, ok. Thanks. I'm not really sure I fully understand what the dishwasher is trying to do. Does it decide the rinse aid was detected low on a timer? Or is it more or less random based on the floating voltage returned from a non-existent sensor? Why didn't it set the rinse aid bit if when, or instead of, setting the error code? |
Rinse aid detection is based on an algorithm involving the door and a sensor in the d-cup module which your model doesn't get populated. I believe the voltage is pulled to make it appear as though there is no rinse aid. We actually set both the fault and the bit. Given that I have been wondering if the bit you have mentioned that keeps getting after cleared (the clean filter bit) is somehow masked wrong and is actually the low rinse aid bit. |
Ah, interesting. Could be. I've also seen the rinse aid bit get set though. Would it matter maybe if the "use rinse aid" mode was on or off? I have had that one set to both states in the past (as part of checking that i can read that state). |
Looks like we don't check for rinse aid at all if the mode is off. |
Today, running the dishwasher for the first time after rebooting it, I got an error code 128 shortly after operatingMode went to 5 (cycle active).
From my app:
The text was updated successfully, but these errors were encountered: