YesNoMaybe
Getting Fingers Dirty
- Joined
- Apr 13, 2008
- Messages
- 13
- Reaction score
- 0
- Points
- 22
Greetings. I own a Canon MP530 and have just started refilling cartridges to save $$$ (am a novice refiller). My situation appears to be somewhat similar to others noted on this forum (which I am new to), but I havent found the definitive final answer.
My situation is that I refilled 2 of my 5 carts after getting ink low" messages on them. Subsequently, for these 2 carts, I rcvd software warnings that ink level monitoring would be disabled; I acknowledged it by holding down the reset button for 5 seconds each time. Anyway, after bypassing those 2 carts, the printer worked fine for that session - but when I powered it up the next day, it gave me a new error message - "ink tank errors have occurred" .... "some ink tanks cannot be recognized" - the pictoral showed all 5 tanks empty. Well, it just won't let me print at all. If I open up the printer to reset the carts (the lights on the 2 reset carts are out when I do), they flash initially when I reseat them but it just ends up turning them off again and giving me the same error code. I'm in a no-print do-loop.
So, when all is said and done, has anyone (a common user w/out high-priced chip resetting systems) found a way to bypass this "second" error message?
My situation is that I refilled 2 of my 5 carts after getting ink low" messages on them. Subsequently, for these 2 carts, I rcvd software warnings that ink level monitoring would be disabled; I acknowledged it by holding down the reset button for 5 seconds each time. Anyway, after bypassing those 2 carts, the printer worked fine for that session - but when I powered it up the next day, it gave me a new error message - "ink tank errors have occurred" .... "some ink tanks cannot be recognized" - the pictoral showed all 5 tanks empty. Well, it just won't let me print at all. If I open up the printer to reset the carts (the lights on the 2 reset carts are out when I do), they flash initially when I reseat them but it just ends up turning them off again and giving me the same error code. I'm in a no-print do-loop.
So, when all is said and done, has anyone (a common user w/out high-priced chip resetting systems) found a way to bypass this "second" error message?