Generic Critical Error Example Image

The Fault Codes Project is an effort to centralize and collect the various knowledge required to diagnose and repair the faults encountered with technology in the modern age.

Our goal is to prevent the loss of capability associated with supporting, using, or restoring technology that may be no longer supported by the manufacturer, antiquated, or obsolete. As all technology is eventually superseded, we also catalog the workings of current era equipment, so that when the time comes for it’s retirement, the human labor invested in the development, design, and production is not ultimately irrelevant or forgotten.

Have you ever tried to fix some old piece of equipment only to be left looking at decade old forum posts, broken links, missing photos, and a variety of half-picture truths? Let’s fix that, together. The Fault Codes Database aims to serve as a central repository for owner-hacking and fix-it information, including all the information, resources, and procedures the O.E.M. would provide in the height of the products support. Where this is not possible, and often, even when it is, we also aim to provide the collective distillation of a variety of specialists or other users who have encountered the same fault circumstances, and have been able to resolve the problem.

What is a Fault Code? It doesn’t have to be electrical, though, in a world of ever-increasing integrated complexity, that’s where it began. How do we diagnose closed-source protocols without O.E.M. required information? There was often no good resource for trustable, referenceable, open-source information, that detailed the system on a deep level. In a larger perspective, though, and for the purposes of our project, a fault is anything that prevents the operation of a piece of equipment, that requires specialized knowledge, process, or material to rectify. We also include ‘bugged designs‘, that is, designs where technological revisions have prevented failures or faults that would occur in earlier implementations. We aim to do this in a ‘top-down’ approach, so that if you’re looking for a specific solution to a problem, you’ll be able to find the best one, even if it isn’t the manufacturer recommended one.

The Fault Codes Blog is our community hub for the people that keep the wheels turning. You’ll find how-to’s, guides, teardowns, crazy customizations, conversions, restorations, upgrades, and detailed build walkthroughs across a wide variety of topics- automotive primarily, but you’ll catch the occasional applianceelectronic, and workmanship post too- along with many others!

Have you figured out how to fix something? Do you have now-obsolete or antiquated O.E.M. data this is still of use? Are you a ‘repair guru’ who has written a novella or two worth of automotive forum guides, How-To’s, and DIY’s? Are you a veteran of your industry, looking to share and preserve your knowledge with a larger audience? Do you have the obscure solution for a common fault, or the common solution for an obscure fault? Or otherwise something you can provide?

We want you! The Fault Codes Project is entirely community-driven. We’re always looking for people like you to add knowledge to the database, clarify and categorize existing content, and show off their one-of-a-kind projects on our blog. Create a wiki account ; Create a blog account ; or Get In Touch to learn more !

Generic Critical Error Example Image
Time to get out the Fault Codes reference!

 

By ADV