HP Designjet Z6100 - Faulty Cartridge/Missing Cartridge issue?

[natallica]

Looking for theories on what causes this error.

Started a job on it before I left for the day. Came in this morning to a "replace faulty cartridge" error. So luckily I had a NIB one and dropped it in. Then it say's "Replace missing cartridge".
Tried this half a dozen times, even cleaned the chip and the connector back inside the cartridge slot... no luck
I've also power cycled it a few times, pressed the little button inside the reset hole etc.
I'd prefer not to buy yet another full cart just to have this same error.

Any ideas on what I may look into as far as checking or replacing something.
I have a service manual, but I can't find any pertinent info on this issue.

Thx
-N8

 

[Steenland]

Unfortunately, this is a fairly common problem with the Z6100. I had to replace the Ink Supply Tubes and Trailing Cable Assembly.
See this thread from 2012:

Designjet Z6100 faulty cartridge issue

Printer: Z6100ps 60-in., p/n Q6654C, Firmware version GG-GG_11.0.0.2 (latest). The printer thinks every Light Gray cartridge I install is faulty. Per HP phone support, I replaced the entire Ink Supply Tubes and Trailing Cable assembly. No change. EEROM reset did not help. Hard disk wipe did not...

www.signs101.com

My Z6100 still likes to reject cartridges when they get down to 109ml remaining. If a rejected cartridge is within its expiration date, HP will usually replace it.

 

[natallica]

Well, I took the side panel (ink cart side) off and found my issue. There is an 'ink sac' attached to the back of the cartridge slot with a black plastic 'pinch' clip. The ear was broken off the clip and the resistance spring was dangling out.
Using Gorilla Gel Super Glue, I reattached the tab and then reinforced both sides of it with 2 small pieces of aluminum bent to an 'L' shape, clamped it all together overnight.
I put the ink sac back on the bracket (with a twist/click) and reinserted it and...viola!
Problem is now solved, printer is back up and running.

Just in case anyone else has this issue, it was a super easy fix.

-N8