# Find the network that matters Learn why a good-looking scan or DLC reading can answer the wrong question—and how the instructor turns an intimidating network into a smaller problem. Source-linked lesson candidate. Technician review pending. ## The GoTech way of thinking 1. Define the question — primary focus: What are we actually trying to establish? 2. Map the system — primary focus: What components, circuits, networks or relationships matter? 3. Observation ≠ conclusion: What did we actually observe, and what are we inferring? 4. Find the evidence boundary: What does this measurement, source or test establish, and what remains unknown? 5. Choose the next check: What additional evidence would reduce uncertainty the most? Choose a check that helps distinguish the remaining explanations. 6. Stop where the evidence stops: Do not turn a plausible explanation into a confirmed fact. ## This lesson’s focus Before interpreting a communication result, identify which network, branch and access path the evidence actually represents. Keep the vehicle's equipment in that picture. ## By the end - Distinguish the scan-tool access path from the network involved in a complaint. - Explain how vehicle options and symptom patterns narrow the source cases. - Recognize when experience with an older vehicle becomes an assumption about a newer one. ## GoTech Tips Core GoTech Tip: Identify the path that answered. In the conceptual example, the observed response leaves the other branch unestablished. Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=480s Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=925s GoTech Tip: Narrow the diagram to the actual complaint and equipment. The Escalade story removes irrelevant option branches before narrowing the search. Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=720s Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=810s GoTech Tip: Use the older case to ask a better question. The later Acadia needs its own network layout; the familiar warning is not enough. Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=1800s ## Conceptual example — not a vehicle wiring diagram 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. Lines show communication relationships, not conductors. The response establishes enough operation for that exchange—not complete health of every item on the path. ## 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. ## Choose the network before choosing the measurement The instructor organizes the work in an intentional order: communication network, physical topology, protocol, then testing. Modules share information and cooperate across systems, so the complete vehicle diagram can contain much more than the branch involved in the complaint. Why it matters: Knowing what a healthy waveform looks like does not tell you whether you are looking at the relevant wires. Pause and explain: Name the communication question first: which module needs to talk to which other part of the system? Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=40s (00:40–03:35) Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=240s (04:00–07:30) ## The diagnostic connector is an access point—not a whole-network verdict In the illustrated gateway arrangement, the diagnostic connector leads to the gateway rather than directly exposing every downstream network. A reading there describes that access branch. The instructor also shows why a module can still answer the scan tool over a different path while its module-to-module communication is affected. Pause and explain: What did the reported DLC reading establish about its own location? What did it leave unknown about the affected branch? Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=480s (08:00–10:55) Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=925s (15:25–18:05) ## Shrink the Escalade diagram using the actual complaint and options In the recalled Escalade case, replacing the fuel-pump driver module had not restored communication. After reporting power and ground checks, the instructor follows the module into its communication diagram. He removes irrelevant diesel-option branches from consideration and narrows the visual inspection area. He reports finding rodent-damaged wiring there. Pause and explain: Which facts let him cross parts of the diagram out, and which facts would be unsafe to assume on another vehicle? Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=720s (12:00–13:45) Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=810s (13:30–18:45) ## Keep the symptoms that initially look unrelated The 2013 Acadia story combines intermittent no-start, interior-light interruptions, a blank dash and a persistent object-detection warning. The instructor initially discounted some of them. On returning to the network diagram, he connects the lost low-speed communication with the key-reading dependency. He reports corrosion at an object-detection module and a return of operation during isolation. Why it matters: A symptom can be far from the system named in the complaint and still help identify a shared communication problem. The persistent warning became a useful lead in this case. Pause and explain: Why did the object-detection warning deserve a place in the explanation of the no-start? Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=1410s (23:30–28:35) Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=1700s (28:20–29:40) ## Use experience to ask a better question, not skip the diagram A later Acadia presents a familiar object-detection warning, but the instructor finds a different network arrangement. The object-detection and immobilizer functions are separated differently, and the earlier no-start pattern does not simply carry over. He explains how network separation changes the consequences of a fault. Pause and explain: What would need to match before you could reuse the older case's reasoning? Source: https://www.youtube.com/watch?v=YbF3idCk4EQ&t=1800s (30:00–32:50) ## Go deeper 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. Reference: https://gotech.com/reference/can-bus/does-60-ohms-mean-the-network-is-good/ Scope: Educational reading of the cited source examples only. Educational treatment of the cited source cases only. No live-vehicle instruction. Source: https://www.youtube.com/watch?v=mNjISEK5VMg&t=25s Source: https://www.youtube.com/watch?v=mNjISEK5VMg&t=630s Source: https://www.youtube.com/watch?v=mNjISEK5VMg&t=1030s Source: https://www.youtube.com/watch?v=mNjISEK5VMg&t=1560s Source: https://www.youtube.com/watch?v=mNjISEK5VMg&t=2115s Source: https://www.youtube.com/watch?v=7AAiP3Ryh2o&t=1085s Source: https://www.youtube.com/watch?v=7AAiP3Ryh2o&t=1215s 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. Reference: https://gotech.com/cases/subaru-ascent-network/ Scope: Educational reading of the cited source examples only. Educational treatment of the cited source cases only. No live-vehicle instruction. Source: https://www.youtube.com/watch?v=7AAiP3Ryh2o&t=500s Source: https://www.youtube.com/watch?v=7AAiP3Ryh2o&t=1085s Source: https://www.youtube.com/watch?v=7AAiP3Ryh2o&t=1215s Source: https://www.youtube.com/watch?v=7AAiP3Ryh2o&t=1460s ## 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. ## Check your reasoning New conceptual example: a scan tool reaches Gateway X through the DLC. Modules A and C respond on two separate branches; Module B on a third branch does not. What do A and C responding establish? A. The shared gateway is cleared, so the remaining question is confined to B’s branch or module. B. The paths used by A and C supported those exchanges; B’s path and the cause of its nonresponse remain unresolved. C. The three branches share the same access point, so B’s nonresponse identifies a local problem inside Module B. Explanation: 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. Why was the persistent object-detection warning useful in the 2013 Acadia story? A. Its persistence located the failed component within the no-start path. B. It could be treated separately because it remained present between the intermittent no-start events. C. It helped select a lead within the affected network after the symptoms were considered together. Explanation: Yes. Its value came from the case's symptom pattern and network relationship, not from the warning text alone. A newer vehicle has a familiar warning but lacks the older case's other symptoms. What is the best learning takeaway? A. Check the actual network and equipment relationships before carrying over the old explanation. B. Use the earlier explanation as the working layout until a new test result contradicts it. C. Use the missing symptoms to exclude the object-detection network before consulting its layout. Explanation: Yes. Experience suggests a question; the applicable diagram determines whether the old relationship still holds. ## Explain it in your own words Return to the opening Escalade claim. Explain why the DLC result and the responding modules do not clear the affected branch. Name the diagram or equipment information that made the problem smaller. ## Keep this Ask which network, which path and which equipment. Keep a successful scan response attached to the path it actually used. ## 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. https://gotech.com/reference/can-bus/does-60-ohms-mean-the-network-is-good/ ## 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.