> On a separate note, I am using the latest B3 (the last one attached to
> the e-mail with reduced ticking sound). The tick is still there but
> beat is slower. A few days ago, I found that cat genie bowl was keep
> rotating even after the genie scooper finished scooping, and the red
> led was blinking constantly. (two quick bursts of red led, then pause,
> then two quick bursts of red led, etc). I stopped the cycle manually,
> and attempted to run the scoop only cycle again, but same error. I
> fixed the problem by unplugging the cord, and no more bowl keep
> rotating without stop. Unfortunately, it is not attached to the PC to
> log errors. Has anyone experienced this behavior?
Version B03b still doesn't have error handling implemented. It does detect errors, but it doesn't act upon them. Instead it just waits for error to go away automatically. Older versions stopped all motors at that time, rendering the box useless without user intervention. But in my specific case, the error seemed to resolve itself after some time. At that time we though a residual drop of water still hanging onto the light guide was causing false-positive water detections. After up to 20 minutes, the drop fell off and the program continued. Logging on the serial port would reveal the occurrence and the box would be in business again. That's why it is the way it is now. At that time, we were discussing the need to 'season' the light guide with WD40 of candle wax, to make the last drop fall off easily.
Later I too had situations where the bowl has been spinning for a very long time. My record is 2 days... In my case, it turned out that my water sensor LED was weakening, resulting into false-positive water detections. The error you're reporting (Error 2) is a draining error, indicating that water is still being detected after pumping. This either means you have a weakened water sensor LED too, or you have a water drop hanging onto the light guide (or both). It fixed my problem with the bowl spinning for a long time for sure. Though I'm no longer logging the serial output lately, so I'm not sure if a drop hanging onto the light guide is still a problem. I do know that I haven't cleaned or seasoned it for a long time, so I consider both problems cured by installing a new LED.
If you haven't done so already, I strongly recommend you to change your water sensor LED. If you already did, we would like to hear that too because we may learn something from that. In any case, you could check your LED's intensity with a digital photo camera. You will need to reflash you box with a GenieDiag version that still uses the old water sensor algo. I'm not sure what algo the most recently posted version does. But you gave me the idea that implementing a water sensor LED diagnosis mode in GenieDiag will add some value here.
But we have more good news on this: Two developers have access to the code, a third one is still hesitating, I think. Supporting these guys has given me new inspiration and I have just implemented Pause functionality of the washing program. This function is essential for proper error handling. When an error occurs, the running program will be paused and the error will be displayed. The user can either resume the program, have the washing program retrying to solve to problem, or he can stop the program and resolve the problem himself.
Until that works, using B03b firmware, the best thing you can do in such a situation is to unplug the box, clean and dry the light guide and plug in the box again. This will trigger the cleanup program, which will drain and dry your box.
Cheers,
Robert.
The easiest preventive fix I can think of is put some duck tape to
immobilize the drain hose or use a zip tie through a small hole on the
side, and put more silicone caulking. Or I can put a big plastic basic
under the Cat genie and not worry about possible future leak. Does
anyone have this concern?
Ok, but I still recommend you to check it because it's fairly easy to do and it will either learn us that you'd better replace your LED or that light guide seasoning is still necessary with a healthy LED.
The new water sensor algo pulses the LED, instead of keeping it on continuously. If you have a modern camera, it will be able to see this. For the best result it's better to check using either an older version or GenieDiag with the older algo
> Will it be possible to allow users to trigger manually the pause
> functionality?
Yes; The pause function is intended to work like it does in the original firmware, but better: If the original firmware is pause while the arm is moving, timing is lost upon unpausing and the arm will make a too long movement. CatGenius will store the context of all timers, so the program should resume exactly as if it were never paused.
Besides that, the pause function is also activated in case an error occurs.
> I pour hot water or extra detergent (oxyclean) when the
> cat genie is pumping water. It will be nice to pause cat genie at this
> state (bowled filled with water) to allow for this. Or, pause the
> program to allow for manually picking up the cat poops too small.
> Right now, I have to be quick or cancel the program (which will result
> in re-running the entire cycle,
Yes, you will be able to do that. We are suffering from the same problem, because we do the same.
> and running the scooping function when
> the granules are wet seems to waste a lot of granules because granules
> clump up when wet and get thrown down the drain.
You could start a cleanup cycle to deal with that by just unplugging and replugging the box. If your granules are wet, the box will find so in it's non-volatile memory. If not, you can still force a cleanup cycle by pressing and holding the start button (if I'm correct) while replugging the box in.
If you don't have time for that, you can just attend the scooping and manually shake the scoop while it's going up. That's what I do.
> Got it. Thanks for the suggestions. The stuck bowl has occurred only
> twice thus far (in many months of using your firmware) but otherwise
> the firmware has been rock solid.
Twice is not that much. But did both cases occur recently?
'Rock solid', I like the sound of that!
You could be right here. Even though the wax may repel water, it may be sticky to other dirt. I'm no longer priming my light guide anymore since I have replaced the LED.
> Last time, I thought if I used the original cat genius 120 cartridge
> it might keep my unit more clean and also have cleaner water sensor.
> But it seems this is not the case. I know that the original cleaning
> solution is stickier than my custom (water and liquid dish washing
> soap) detergent as the granules seem to stick more to cat genie wall
> (almost none with my custom mix or with no detergent).
That's good to know: I thought the original fluid would keep the water sensor working better too, but I suppose any other soap - breaking surface tension - will do just was well. BTW: I'm running without soap for a year now and I don't have any problems.
> Right now, I am running on auto cat activated mode (full wash with
> water every 3 uses) but I have two cats. So I might be running full
> wash once every six use. I think that's like four urination plus 2
> defecation before full cycle with water. So this might make my water
> sensor especially dirty quickly as it is dealing with more dirty
> water. So I might set the full wash to run more often. So full wash
> once 2~4 uses instead of 4~6 uses.
I'm running a full wash after every use, one on one. The scooping smears the urine around the box. It dries pretty quickly, so it's not a problem for a long time, but one of my cats doesn't like to use the box shortly after the smearing.
> You mentioned that you changed the water pump relay to reduced the
> tick with beta 3-3, and I indeed notice slower tick. I rarely had
> false water sensor error with the original Beta 3 (with faster ticks).
> I might try going back to the original Beta 3.
You have to check the change list on the release page on the group to see what more has changed. I don't think you need to replace the relay. Some may tick, others may not, but it doesn't harm the relay because it's not a full move of the lever. It's just a very brief rattle.
> Related observations:
> The Beta 3-3 seems to use up the detergent more quickly than either
> previous versions or the stock firmware. In just 20 days, the new
> original cartridge was almost empty (this with about 2~3 full washes
> daily, so about 40~60 full washes before empty). Anyways, I don't have
> any original cart anymore (other than the maintenance cart which I
> have yet to use).
The dosage is base on a manually triggered washing program, so you should get 60 washes out of a cartridge. We could make this configurable.
If there's a difference with other releases, it could be caused by the auto-dose command. Again you can check the release notes to see when this was introduced.
> On the future version of the firmware, would it be possible for the
> scoop-only/full-wash cycle to reset after running the full cycle
> manually? So if I run a full cycle manually, the scoop only cycle
> count will reset before running the full cycle.
It should. If it doesn't, that's a bug.
Richard
Sent from my iPhone
I had that once, I think. In my case the box didn't respond to the keyboard either, so I had to power-cycle it. In my case, probably the whole software stack was hanging. In the next release we will re-enable the watchdog again, which will reset the whole board in these situations. I had to disable it, because I noticed a number of un-explained resets.
In your situation, it was probably just the washing program that was hanging. We run a program-within-a-program to do the washing cycle. This could be due to a bug in the timer implementation. We could guard the program for that, but I doubt if that's of any use.
> Second error: Freezing box. A few days ago, there was another error
> where the Catgenie just froze after a cat has used it. No spinning
> bowl, no led error, no scooping, and all the buttons didn't seem to do
> anything (no beep). I reset the machine by removing the power. There
> was a few times before where the catgenie would just freeze. It has
> been only 13 days, but I have yet to get the classic water sensor
> error (blinking red led plus spinning bowl).
That will be worked-around by the watchdog.
> Interestingly the Beta 3 posted on the file page (rather than the
>slower click version that was e-mailed) didn't have this strange
> behavior.
I can check if beta 3 has it enabled.
> I am now logging the Catgenie Beta 3 (e-mail version) using serial
> port. It seems I am getting strange error once a week so hopefully the
> log would catch it.
That would be great! Without it, it's just guessing. With it, we may have some insight.
I these situations, it's very important to check if the box still responds to the keyboard and the cat sensor. If it still responds to the keyboard, we know that the software didn't hang up. If it even responds to the cat sensor, it must have missed a couple of detections.
That has been my suspicion too. The next version will have brown-out detection enabled, so at least the whole processing unit will reset along. I'm intending to buy a logging multi-meter, a Fluke 289, but even that one will only take 10 measurements per second so a brief surge will still go unnoticed.
> Any updates on the next beta of the Catgenius? I know Rob is working
> on the pause functionality, but re-enabling the watchdog would be
> nice. On the other hand, I think I can proactively reduce the chance
> of catgenie locking up by resetting power to the catgenie every week
> or day (to clear the buffer and such).
The pause function is in. So is a more decent error handling: The box will go into pause in case of an error. The big bug Christian found in the LitterLanguage interpreter is fixed too. For the rest it's just cosmetics and small bug fixes. For example: If you unplug your box while it is running a wet cleanup program, it ran a dry cleanup program when plugged in again. I still need to test all these features to some degree.
I'm also thinking about making an improvement in the washing program we discussed in the group earlier, called 'flushing'.
After scooping we stop the bowl before we open the tap. When the tap is open, we wait until the level hits just below the bottom of the bowl. At that moment we start the pump, while leaving the tap open. The pump drains faster than the tap fills, so the water level will decrease. When the water is almost drained, and the waste is flushed away, the pump will stop, the bowl will start spinning again and hence the bowl will fill. The purpose of this flushing is that we will flush out the waste before we give it a chance to spread over the whole box when filling it.
The copy protection is mostly implemented too, but we won't activate that.
> Rob, was the watch dog function
> enabled in the Beta 3 posted on the files page (as opposed to the e-
> mail version)?
I have checked, but I cannot see: The code was in at that time, but it is not active when a debug version is built. Unfortunately I cannot see if the binary I have posted is a debug build or a release build.
> On an unrelated note, I am using Ajax dish washing detergent (about 1
> part in 10 part water), and this seems to be extremely effective. One
> thing I have definitely noticed is that, unlike other detergents I
> have tried, including the original quad formula, there is no more
> brown ring of excrement in my toilet after a full wash. Before, I
> would have to flush the toilet immediately after the finish of the wet
> wash OR I will get a rather hard to clean brown ring of excrement on
> my toilet bowl. Now, with Ajax dish washing detergent, I don't have
> this ring even after now flushing the toilet after the finish of the
> wet cleaning cycle. I guess this detergent is really good at cutting
> grease and making the excrement non-sticky after being liquified, and
> I think this (in addition to weekly hot water treatment) will lead to
> less frequent Water sensor error in the future.
Warm water helps, but don't make it hot: The water valve is not made to withstand hot water. Jaime had his water valve partially molten, leading to a weak stream filling the box. It took him quite some time to diagnose the filling timeouts down to the hot water damaging the valve.
Dish washing detergent seems like a good idea. Are you sure that it won't damage the internal silicon tubing? Or dull the water sensor light guide? It is excellent in degreasing and I'm pretty sure it's killing germs as well. But how do you get it into the cartridge? I have tried to solve dish washer detergent powder in water before and It was very difficult. It seems to take a long time, probably to spread the time it is active within the machine.
> Rob has mentioned that
> he is running his machine with just plain water, and has yet to
> encounter any water sensor error after replacing his LED. As for me, I
> noticed with my last water sensor error, my original cartridge has
> almost run out and I have been running 2 dry to 1 wet (with two cats
> this can mean that I would have had only one wet wash after 3 ~ 6 uses
> by 2 cats).
We are no longer using scoop-only, but I know other people who still use it. One of our 3 cats refuses to use the box if it's not completely clean, so we're back at one-on-one. This, and the lack of the 12 hour sleeping of the box, has caused our water usage to increase to 150%. But fortunately water is still cheap.