Problem:
Printer will not function.
Solution:
Corona Wire Issue - Replacement ordered
Goal:
Repair Printer
Data:
Printer will not function
Printer turns on
Error Code is 0B01
0B01 Error Code per manual - "An error occurred in the high-voltage power supply PCB ASSY while operating"
Missing Corona Wire upon visual inspection
Tools:
Screw Driver
PrinterĀ Documentation
Multimeter (not needed)
Oscilloscope (not needed)
Stretch Tools:
GitHub Repository
Hardware Tear-Down:
An important takeaway is to have photos of what a corona wire looks like in-situ. Knowing what I know now, in the future I know to take a second and third look at the suspect part prior to stripping printer down to PCB. Having an individual with practical experience taking an internal look at your hardware is priceless and reduces your touch time. Upon first visual inspection of the drum, the corona wire seemed to be intact. This was not the case. Upon reviewing material from various sources and prior to touching the PCB's with my digital signal processing equipment, it was determined that the corona wire was not intact.
Resolution:
New corona wire is on order.
Printer Drum and Toner Cartridge
Slider Sans Corona Wire (Horizontal View)
Closer Visual inspection of Drum
Slider missing Corona Wire (Vertical View)
Alternate Objectives:
As this is my personal project on my own time, I am serving as my own program manager. As program manager, the budgetary constraints currently allow for stretch funding to learn and solidify new concepts. Located on GitHub, there is a feature that by design looks to be primarily for software use case. In this case as I do not know currently know of another publicly available tool for integration of hardware, this currently serves as an intermediary.
Stretch Goal:
-Learn how GitHub's Retrospective Panel functions with respect to hardware as a meaningful manner to tracking hardware
-Create Fishbone Diagram for project
Notes and Considerations:
Retrospective panel populates all items as issues. As this site is primarily developed for coding application, this serves as a convenient way to track coding issues. Requires discipline for tracking hardware issues. This can be done, however it is not the intended use case for GitHub to my knowledge.
Update 5/19:
Stretch goal - Create Fishbone Diagram for project
Stretch goal has been abandoned due to lack of use at the user end. Fishbone Diagram has intent to improve quality process, not determine where error/failure occurred from user standpoint. Manufacturer would yield more benefit by implementing Fishbone Diagram than end user does.
Update 5/31:
It got more complicated. Corona Wire was received on 5/25. Upon closer inspection to install corona wire, it was discovered that the electrode had been eaten by the plastic gears. See photos down below for reference. Gears look workable upon closer inspection, life of printer is worn, however for casual use basis would be fine. Decision going forward is to repair electrode and try re-install.