What you will see
A customer reports that the printer has print quality issues, even though the Imaging unit has not yet been completely depleted. Replacing the Imaging unit resolves the issue; however, the print quality defect re-occurs after consuming only 50% of its print life.
Issue verification
Before proceeding with the steps for verifying which part is causing the early print quality issue, first evaluate the printer and imaging unit functionality by acquiring the SysDebugData.
There are two different scenarios for acquiring this information, and only one needs to be performed depending on the situation encountered.
- Scenario 1 - The customer has two or more printers onsite and only one is encountering the print quality issue. Begin by removing the imaging unit from the one printer not producing any print quality issue and install it on the printer that exhibits the print quality defect.
- Scenario 2 - Only one printer is available onsite; however, a customer has a new Imaging unit that can be used for troubleshooting. Start by installing the new imaging unit in the printer.
Proceed to the steps on how to acquire the SysDebugData after verifying which of the scenarios best fits the situation.
How to acquire the Dump SysDebugData
Step | Action |
1 | Access the SE menu by typing the printer's IP address followed by /se in any web browser. |
2 | Under Menu Options, locate and select Dump SysDebugData. |
3 | Copy the information provided, paste it in Notepad, save it as .txt file, and label it as sysdebugdata1. |
4 | Print two pages from the printer. |
5 | Repeat Steps 1 – 3, and this time label the information provided as sysdebugdata2. |
Recommendation
Step | Action |
1 | Open the sysdebugdata1 file and sysdebugdata2 file using Notepad and locate the corresponding values for FilteredTnrInDvlpr. E.g., sysdebugdata1 >FilteredTnrInDvlpr = 71,234 sysdebugdata2 >FilteredTnrInDvlpr = 98,253 |
2 | Subtract the FilteredTnrInDvlpr values acquired from sysdebugdata1 file and sysdebugdata2 file. E.g., 98,253 – 71,234 = 27,019 |
3 | If the result is a value greater than 10 000, please proceed to Step 5. |
4 | Should the result be a value less than 10 000, the printer requires no additional service. |
5 | Go to the Contacting Lexmark section and provide the acquired data for analysis. |
LEGACY ID: TE759
Technical Service Bulletin | Problem Description |
Machine Type/Model | 4063 – xxx 7463 – xxx | Troubleshooting a Repeating Print Quality Defect due to Early Imaging Unit Failure Solution: Follow the service tip outlined below. |
Date Created | 02/16/2016 |
Last Updated | 02/16/2016 |
Safety Issue? | No |
Code Update? | No |
Engineering Change? | No |
New Parts? | No |
Old Parts Status | n/a |
Voltage: 120/240 | All |
Serial No. Range | All |
Step | Action |
1 | Print two pages before replacing any parts from the affected printer. |
2 | Access the service menu (SE) again and go to Menu Options>Dump SysDebugData>FilteredTnrInDvlpr. |
3 | Record the values obtained from FilteredTnrInDvlpr and replace the Controller board. |
4 | After replacing the Controller board, restart the printer and print another two pages. |
5 | Access the service menu (SE) once more, go to Menu Options>Dump SysDebugData and record the new value for FilteredTnrInDvlpr. |
6 | Subtract the values acquired from Step 3 and Step 5. |
7 | Take note of the value and subtract it with the Configuring wireless settings via the Embedded Web Server and switch from a wired to wireless connection obtained from sysdebugdata1 file and sysdebugdata2 from the customer-level section. |
8 | If the difference is less than 3000 or 4000, the printer has been corrected and it requires no additional service. |
9 | Should the difference still be greater than 5000, repeat Steps 1-8 and replace the Toner level contact assembly. |
10 | Should the difference still be greater than 5000 after replacing the Toner level contact, please contact Lexmark 3rd Level Support. |