HP Z6100 has error code 46.03

[kerriewal]

Hi can anyone tell me how to solve this problem please.HP Z6100 has error code 46.03. I have checked printheads and replaced two which were not showing faulty on the machine but looked marked to me.This happened after a paper jam .. thanks kerrie 

[Ronaldo_Ferrei2 · Accepted solution]

Hi Kerrie, how are you doing ?

Unfortunately this error it's necessary repair.

Check ther service manual below:

http://www.partsnow.com/docs/service-manuals/hp-designjet-z6100-service-manual.pdf

Page 62 Chapter 2 System Error Codes:

System Error:

46:03

Problem Description:

Primer servo shutdown.

Corrective Action:

Try the following:

• Switch the Power OFF from the back of the Printer and disconnect the Power cord. Reconnect the power cord and power On the Printer.

• Replace the Primer Assembly ⇒ Page 294.

• Replace the PrintMech PCA ⇒ Page 384.

• Replace the Interconnect PCA ⇒ Page 357.

I hope that helps !
🙂

I would give a great kindness ...

If the question is clarified, mark my answer as "resolved" and click on the icon of the "hand" to provide "congratulations" in recognition.

Have a nice week !
🙂

[Mikeg81]

Hi,

If hte primer is broken, or not moving, you will need to replace it.

If it moves and is not broken, clean the encoder strip and do a primer calibration

[kerriewal]

thank you for taking the time to help me Ronaldo.. ..it has really helped ..many thanks 🙂 

[kerriewal]

it is not moving ..thanks for your help Mike .. really appreciate .. kerrie 🙂

[Roy_Kuzmich]

Hi Kerrie,

I am having a similar issue and was wondering What was the actual solution that resolved the issue?

Did you clean the encoder?

did you replace the Primer? Printmech? or Interconnect?

Please advise thank you.

RoyK

[Mikeg81]

Hi @Roy_Kuzmich

Remove the right cover and reboot the print, check if the primer is broken or not moving.

Clean the encoder strip with a lint free cloth

If the primer moves is ok, and the printer clean, do a primer calibration

Take in consideration that there could be different causes for the error, just need to find the root cause