GOTECH CAN SERIES · PART 3 OF 3

CAN bus diagnostics & troubleshooting

A Subaru Ascent will not crank, but some modules still respond. Follow how GoTech narrows the affected network—and why temporary communication recovery is not a verified repair.

Original video · 58:433 reasoning checks

SUBARU ASCENT · NO-CRANK CASE

From scan results to a narrower suspect

Reported findings from the original GoTech video. “Next question” connects the reasoning; it is not a vehicle-specific test procedure.
Location / connection stateObservationWhat it meansNext question

Module scan · manual identification

05:00–08:15 ↗

Body unit and combination meter respond. ECM, TCM, ABS and EyeSight do not during this scan.

The fault is not a loss of every communication path.

Which network connects the nonresponding group?

Diagnostic port · initial resistance check

20:15–22:00 ↗

The first interpretation changes after the diagram identifies a separate access branch.

The expected result must match the branch being measured.

Does this test reach the network involved in the complaint?

Main CAN · comparison with body unit disconnected

47:30–49:15 ↗

The measured termination path disappears when the body unit is unplugged in the reported comparison.

GoTech traces the observed path back toward the body unit and focuses on the ECM end.

Is the remaining wiring path present when checked from the ECM end?

ECM end · module disconnected, harness-side check

52:20–53:55 ↗

The path back toward the body unit is still seen from the harness side.

The ECM end is the reported suspect; the extent of internal damage is unresolved.

Can the other modules communicate under the temporary test condition?

Temporary substitution · scan repeated

55:30–56:40 ↗

TCM communication returns under the temporary test condition.

Communication recovery is evidence. It is not a completed repair.

Replacement, engine start and final network/road checks are not established here.

Outcome: temporary TCM communication recovery. Completed ECM replacement, engine start and final repair verification are not established in this case.

Conflicting meter values and connector pin details remain unverified. See the unresolved details →

All case source moments

FROM THE ORIGINAL LESSON

Follow the Ascent investigation

Which modules communicate—and which do not?

The Ascent would not crank, yet some accessories and modules still responded. Manual identification and targeted checks produced a useful split: the body unit and combination meter answered; the ECM, TCM, ABS and EyeSight did not during the reported scan. Match that pattern to the diagram before choosing a suspect.

Check your thinking

Keep two columns while watching: reported responding modules and reported nonresponding modules. Do not reconstruct exact DTCs from unclear captions.

Why did the diagnostic-port reading need a second look?

The initial diagnostic-port resistance reading was judged against a familiar expectation. The diagram then identified a separate diagnostic-port/body-unit branch, changing what that reading meant. Starting a scan conversation later produced activity on this access path. Neither observation cleared the main CAN network.

Check your thinking

Write the original interpretation and the information that changed it. Which fact changed: the reported observation, or the expectation used to judge it?

How did the investigation narrow to the main CAN network?

The diagram separates diagnostic access, body CAN and main CAN. The nonresponding group points the investigation toward main CAN; later comparisons narrow suspicion toward the ECM end. Record the connection state with each finding: a battery or module disconnection can also clear an intermittent condition.

Check your thinking

At each new observation, name the branch and connection state before carrying its interpretation forward.

Which readings and connector details remain unverified?

Exact meter values and connector pin identities in the conflicting source passages remain unverified. Use the table to follow the diagnostic reasoning, not as a pinout or a set of pass/fail specifications for your vehicle.

Check your thinking

Mark the uncertain detail as unresolved. What original display, connector view or service reference would be needed to settle it?

What did the final test establish?

TCM communication returns during temporary substitution. GoTech suspects the ECM end but leaves the extent of internal damage unresolved. The video does not establish completed ECM replacement, engine start, a full post-repair network check or a successful final drive.

Check your thinking

Finish two separate notes: the source reports…; final confirmation would still need evidence of…

Keep this example in scope This is a reading of the narrated Ascent case. It deliberately withholds connector/pin instructions, disputed readings, universal resistance criteria and resistor-substitution procedures. Unclear source details are not used as vehicle-specific instructions.

FROM THE ORIGINAL LESSON

Watch the original GoTech video

58:43

The original Ascent investigation shows the presenter changing the question as evidence develops. Follow both what changes and the final confirmation the source does not supply.

Original GoTech lesson thumbnail

Video loads only when you choose to play.

YouTube connects only when you choose to play.
Watch on YouTube ↗ · CAN Bus Troubleshooting and Diagnosis Explained (Part 3)

Watch the full video, or use the timestamp links beside each explanation to jump to that moment.

Want to study this in more depth?

Use the learning goals and GoTech’s reasoning framework, then try the questions below.

By the end of this lesson

  • Use the responding and nonresponding module groups to follow the source's network selection.
  • Explain why identifying the branch changes a measurement's meaning.
  • Separate temporary communication recovery from a completed vehicle repair.

Before you start Lessons 4 and 5: access path versus affected network, topology and the meaning of connection state. This is a case-reading lesson, not a procedure to perform on a vehicle. Foundations ↗

This lesson’s focus

Carry the reasoning as far as the evidence supports—and no farther. Keep a changed response, a stronger hypothesis and a confirmed repair as separate claims.

The GoTech way of thinking · 6 steps

WAY OF THINKING

The GoTech way of thinking

01Define the question

What are we actually trying to establish?

02Map the system

What components, circuits, networks or relationships matter?

03Observation ≠ conclusionAlso used

What did we actually observe, and what are we inferring?

04Find the evidence boundaryAlso used

What does this measurement, source or test establish, and what remains unknown?

05Choose the next check

What additional evidence would reduce uncertainty the most? Choose a check that helps distinguish the remaining explanations.

06Stop where the evidence stopsPrimary focus

Do not turn a plausible explanation into a confirmed fact.

GoTech Tips

More GoTech tips · 1
Before the questions: make your own prediction

01 · MAKE A PREDICTION

Start with the question

The instructor gets a previously silent module to respond during a temporary intervention. Before treating that as success, decide what kind of success it is: a changed observation, a stronger hypothesis, or a completed repair.

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 scan response keeps its access-path limit

In the cited examples, a module can answer the scan tool over one communication path while another path has a problem. A scan response alone does not establish that every network is healthy.

Revisit the communication lesson →
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.

Keep the expectation attached to the branch

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.

Read the resistance reference →
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.

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

QUESTION 01Why does the presenter revise the interpretation of the diagnostic-connector reading?
Read the full explanation
The later scan response establishes that the earlier resistance expectation was correct.

The branch and service-information review changes the applicable expectation; a later response cannot retroactively verify the assumption.

The identified branch has a different applicable expectation from the one initially assumed.

Yes. The reading must be judged in the arrangement that produced it.

The same familiar expectation remains valid after the test is moved to another branch.

Moving branches can change the relevant arrangement. The source identifies that difference before reinterpreting the result.

QUESTION 02Two source notes describe the same resistance check differently. Which evidence would most directly resolve that conflict?
Read the full explanation
The original meter display and the documented branch and connection state for that moment.

Yes. The disputed observation needs its own context and visual verification; the later outcome cannot supply it.

The later communication response, used to select the earlier reading that best explains it.

That uses the ending to choose missing evidence. It does not resolve what the meter showed.

A clear reading from another branch, used as the value for the disputed moment.

A different observation cannot replace the disputed one without establishing that the test and conditions are the same.

QUESTION 03A different case report ends when a previously silent module answers after a temporary change. It contains no documented recheck of the original customer complaint. Where should your explanation stop?
Read the full explanation
The temporary change confirms the cause because the predicted communication response returned.

The response is useful, but it does not establish the cause’s full extent or resolve the original complaint. The report needs those separate observations.

The repair is likely complete, with the complaint recheck serving only as final paperwork.

The missing complaint recheck is missing evidence, not a formality. Do not report an outcome that the case has not established.

The reported response changed under the temporary condition; cause and completed repair remain limited to what was actually documented.

Yes. Preserve the useful change without filling in the ending. A different case still needs its own complaint recheck and applicable confirmation evidence.

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

Keep the observation, its interpretation, the intervention and final confirmation as separate entries. A changed response is evidence; a completed repair needs its own evidence.

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.

This is a reading of the narrated Ascent case. It deliberately withholds connector/pin instructions, disputed readings, universal resistance criteria and resistor-substitution procedures. Unclear source details are not used as vehicle-specific instructions.

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

Use the communication-versus-repair reference to write a bounded handoff: what changed, what explanation it supports and what confirmation remains missing. Ask GoTech about the reviewed concept, without turning this case into a replacement recommendation.

KEEP BUILDING

Build your evidence worksheet

Use the evidence worksheet to reconstruct another source case while keeping its unknowns and confirmation boundary visible.

Mark studied & continue →

Saves your place on this device. Your answers and written note are not saved.

Did this help you move forward?

Optional. No written response is collected.