5,366
edits
Changes
m
no edit summary
This is an overview of troubleshooting Zero motorcycles and attached products.
: This is ''not'' necessarily comprehensive.
: It consists of what owners have observed and inferred over time.
: We attempt to assemble the best generic advice available.
;Scope
: For now, we'll focus on just:
# Identifying, categorizing, and describing symptoms.
# Standardizing the language to describe symptoms so that Zero and dealer support people can understand you.
# Suggesting possible hypotheses to consider.
# Offering means to test hypotheses.
===Theory===
Read Wikipedia's [[wikipedia:Troubleshooting|Troubleshooting]] article for an overview of different aspects and methods:
* [[wikipedia:Troubleshooting#Half-splitting|Half-splitting]], AKA ''divide and conquer'' or ''basic block isolation'', is the strategy of bisecting a system at a testable system boundary with a falsifiable expectation that can be used to tell whether the problem is upstream or downstream of the boundary.
* [[wikipedia:Troubleshooting#Intermittent_symptoms|Intermittent symptoms]] are worth an extra consideration (depending on the risk) to attempt to create the simplest procedure which can induce the symptom reliably before diagnosis or describing for others.
* [[wikipedia:Troubleshooting#Multiple_problems|Multiple problems]] are a possibility to consider when attempting or evaluating fixes.
;[https://artoftroubleshooting.com/ The Art Of Troubleshooting]
: This website is an excellent resource.
:* [https://artoftroubleshooting.com/the-right-questions-a-universal-troubleshooting-guide/ The Right Questions, A Universal Troubleshooting Guide]
:* [https://artoftroubleshooting.com/2013/03/30/one-size-doesnt-fit-all/ One Size Doesn't Fit All]
:; [https://artoftroubleshooting.com/strategies/ Strategies]
:*[https://artoftroubleshooting.com/2013/03/30/one-size-doesnt-fit-all/ The Universal Troubleshooting Recipe]:
:*# Find the problem.
:*# Fix it.
:* [https://artoftroubleshooting.com/2012/01/10/change-just-one-thing/ Change Just One Thing At A Time]
:*: Minimalize actions so that the change produces information.
:* [https://artoftroubleshooting.com/2012/04/16/copy-one-that-works/ Copy One That Works]
:*: Reference a known-working bike to compare.
:*: Mind that models and years may have different operation in hardware, software, or in the bike's usage and wear over time.
:; [https://artoftroubleshooting.com/virtues/ Virtues]
:* [https://artoftroubleshooting.com/2011/09/20/skepticism/ Skepticism]
===Guide===
Navigate the [[:Category:Symptom|Symptoms]].
: This is ''not'' necessarily comprehensive.
: It consists of what owners have observed and inferred over time.
: We attempt to assemble the best generic advice available.
;Scope
: For now, we'll focus on just:
# Identifying, categorizing, and describing symptoms.
# Standardizing the language to describe symptoms so that Zero and dealer support people can understand you.
# Suggesting possible hypotheses to consider.
# Offering means to test hypotheses.
===Theory===
Read Wikipedia's [[wikipedia:Troubleshooting|Troubleshooting]] article for an overview of different aspects and methods:
* [[wikipedia:Troubleshooting#Half-splitting|Half-splitting]], AKA ''divide and conquer'' or ''basic block isolation'', is the strategy of bisecting a system at a testable system boundary with a falsifiable expectation that can be used to tell whether the problem is upstream or downstream of the boundary.
* [[wikipedia:Troubleshooting#Intermittent_symptoms|Intermittent symptoms]] are worth an extra consideration (depending on the risk) to attempt to create the simplest procedure which can induce the symptom reliably before diagnosis or describing for others.
* [[wikipedia:Troubleshooting#Multiple_problems|Multiple problems]] are a possibility to consider when attempting or evaluating fixes.
;[https://artoftroubleshooting.com/ The Art Of Troubleshooting]
: This website is an excellent resource.
:* [https://artoftroubleshooting.com/the-right-questions-a-universal-troubleshooting-guide/ The Right Questions, A Universal Troubleshooting Guide]
:* [https://artoftroubleshooting.com/2013/03/30/one-size-doesnt-fit-all/ One Size Doesn't Fit All]
:; [https://artoftroubleshooting.com/strategies/ Strategies]
:*[https://artoftroubleshooting.com/2013/03/30/one-size-doesnt-fit-all/ The Universal Troubleshooting Recipe]:
:*# Find the problem.
:*# Fix it.
:* [https://artoftroubleshooting.com/2012/01/10/change-just-one-thing/ Change Just One Thing At A Time]
:*: Minimalize actions so that the change produces information.
:* [https://artoftroubleshooting.com/2012/04/16/copy-one-that-works/ Copy One That Works]
:*: Reference a known-working bike to compare.
:*: Mind that models and years may have different operation in hardware, software, or in the bike's usage and wear over time.
:; [https://artoftroubleshooting.com/virtues/ Virtues]
:* [https://artoftroubleshooting.com/2011/09/20/skepticism/ Skepticism]
===Guide===
Navigate the [[:Category:Symptom|Symptoms]].
