CONCEPTUAL EXAMPLE — NOT A VEHICLE WIRING DIAGRAM
One responding module does not clear every branch
Lines show communication relationships, not conductors. The response establishes enough operation for that exchange—not complete health of every item on the path.
Read the diagram in words
A scan tool connects through the DLC and a gateway to two conceptual branches. Module A responds over Path A, shown with solid lines. Path B to Module B is dashed: its condition is not established by that response.
FROM THE ORIGINAL LESSON
Find the network involved in the complaint
Where should CAN bus diagnosis start?
Start with the modules involved in the complaint. Find their communication network and physical connections on the diagram, then identify the protocol before choosing a test. A whole-vehicle diagram includes branches that may have nothing to do with the fault.
Check your thinking
Name the communication question first: which module needs to talk to which other part of the system?
Why can a scan tool communicate while another network has a fault?
In the gateway arrangement shown here, the diagnostic connector reaches the gateway through its own branch. A good result there does not clear the downstream networks. A module may still answer the scan tool through one path while its communication with other modules is affected.
Check your thinking
What did the reported DLC reading establish about its own location? What did it leave unknown about the affected branch?
Escalade: narrow the diagram to the noncommunicating module
The Escalade’s fuel-pump driver module still would not communicate after replacement. With power and ground checks reported, GoTech followed its communication wiring and excluded diesel-option branches that did not apply. That smaller search area led to reported rodent damage.
Check your thinking
Which facts let him cross parts of the diagram out, and which facts would be unsafe to assume on another vehicle?
Acadia: connect the warning light to the no-start
On the 2013 Acadia, intermittent no-start, interrupted interior lights and a blank dash accompanied an object-detection warning. The network diagram connected the low-speed communication problem to the key-reading dependency. GoTech reports corrosion at an object-detection module and a return of operation during isolation.
Check your thinking
Why did the object-detection warning deserve a place in the explanation of the no-start?
Can you use the same diagnosis on a newer vehicle?
The later Acadia had a similar object-detection warning but a different network arrangement. Object detection and immobilizer functions were separated differently, so the older vehicle’s no-start explanation did not carry over. Check the applicable diagram before reusing a familiar diagnosis.
Check your thinking
What would need to match before you could reuse the older case's reasoning?
Keep this example in scope The Escalade and Acadia stories are the instructor's reported cases. Their exact diagrams, options, connector details and lasting repair outcomes are not independently verified here. The companion teaches the reasoning without prescribing module disconnection or a replacement.
FROM THE ORIGINAL LESSON
Watch the original GoTech video
The original lesson demonstrates this reasoning through the instructor's Escalade and Acadia network cases. Each story keeps its own equipment and communication relationships.
Video loads only when you choose to play.
YouTube connects only when you choose to play.
Watch on YouTube ↗ · CAN Bus Communication Explained (Part 1)
Watch the full video, or use the timestamp links beside each explanation to jump to that moment.
Before the questions: make your own prediction
01 · MAKE A PREDICTION
Start with the question
A fuel-pump control module will not communicate. Another technician reports a good-looking scope pattern at the diagnostic connector and says the other modules respond. Has the relevant network actually been cleared? Decide before reading the Escalade walkthrough.
Try the reasoning checks →GO DEEPER
Related explanations
These reviewed explanations draw on their own source examples. Keep each explanation within its stated scope.
A resistance reading belongs to a particular network state
A resistance reading only has meaning relative to the cited branch/topology, connection state, test point and applicable source expectation. The Ascent lesson changes its interpretation after identifying the diagnostic-port branch; a number alone does not establish whole-network health.
Does 60 ohms mean the network is good? →Sources and scope
Educational reading of the cited source examples only. Educational treatment of the cited source cases only. No live-vehicle instruction.
These explanations cover the cited examples. Use the applicable vehicle information for test conditions and specifications.
- CAN Bus Wiring and Protocol Explained (Part 2) · 00:25–03:40
- CAN Bus Wiring and Protocol Explained (Part 2) · 10:30–12:55
- CAN Bus Wiring and Protocol Explained (Part 2) · 17:10–20:50
- CAN Bus Wiring and Protocol Explained (Part 2) · 26:00–28:20
- CAN Bus Wiring and Protocol Explained (Part 2) · 35:15–37:25
- CAN Bus Troubleshooting and Diagnosis Explained (Part 3) · 18:05–19:05
- CAN Bus Troubleshooting and Diagnosis Explained (Part 3) · 20:15–22:00
Compare the access branch with the affected network
In the narrated Ascent example, source diagram review changes the expectation for the diagnostic-port/body-unit branch. That branch is distinct from the main network involved in the complaint; the revised interpretation does not establish whole-network health.
Follow the Ascent case →Sources and scope
Educational reading of the cited source examples only. Educational treatment of the cited source cases only. No live-vehicle instruction.
These explanations cover the cited examples. Use the applicable vehicle information for test conditions and specifications.
Review the case reasoning in four steps
FOLLOW THE REASONING
Revisit the opening claim: has the network been cleared?
Reported observation
One module does not communicate; other modules answer and the diagnostic-connector pattern looks acceptable to the previous technician.
Tempting conclusion
The vehicle network must be healthy, so the continuing problem must be the replaced module.
What changes the reasoning
The diagram distinguishes the scan-access path from the affected branch and shows which equipment belongs on that branch.
Supported account
The instructor narrows the branch and reports finding damaged wiring. The earlier access result did not clear that wiring; a completed repair record is not supplied here.
PRACTICE IT
Test your understanding
Choose an answer, then compare the explanation. These checks help you study; they are not a technician certification.
0 of 3 questions compared
Read the full explanation
Two responses do not clear every gateway function or every relationship to B. That conclusion narrows the problem farther than the observation supports.
Yes. Apply the solid-path idea to both observed exchanges. Adding another responding branch still does not establish the unobserved path to B or identify why B did not respond.
A shared access point does not make the downstream branches equivalent. The result does not distinguish B’s branch, its module or other applicable conditions.
Read the full explanation
Persistence made it a useful lead. The network relationship and further investigation still mattered.
The source revisits that separation after considering the shared communication problem and symptom pattern.
Yes. Its value came from the case's symptom pattern and network relationship, not from the warning text alone.
Read the full explanation
Yes. Experience suggests a question; the applicable diagram determines whether the old relationship still holds.
That carries an unverified architecture into the interpretation. The later Acadia example changes the relevant relationships.
Different network separation can change the consequences. The symptom difference alone does not establish the layout or exclude a branch.
06 · MAKE IT YOURS
Explain it in your own words
This note stays in this open page. It is not sent, graded or saved; copy it before leaving if you want to keep it.
Review your explanation
- Did I name the source example and the relevant conditions?
- Did I separate the observation from my interpretation?
- Did I say what the evidence still does not establish?
KEEP THIS
Ask which network, which path and which equipment. Keep a successful scan response attached to the path it actually used.
Download this lesson’s study notes ↓Source, scope & review
GoTech’s written companion to the original demonstration. Source moments support the case observations; the learning prompts are GoTech editorial guidance.
The Escalade and Acadia stories are the instructor's reported cases. Their exact diagrams, options, connector details and lasting repair outcomes are not independently verified here. The companion teaches the reasoning without prescribing module disconnection or a replacement.
Timestamp links identify supporting passages. They do not independently verify every source diagram or establish a procedure for another vehicle.
APPLY IT
Apply the way of thinking
Frame a concept question by naming what the source is trying to establish and which path it discusses. Ask GoTech using the reviewed CAN/wiring material, or compare the access-path question with the resistance reference. This is not a vehicle-specific diagnosis.
KEEP BUILDING
CAN bus wiring explained
CAN Part 2 asks what happens after you have selected the branch: how its physical layout changes the meaning of an isolation result.
Mark studied & continue →Saves your place on this device. Your answers and written note are not saved.