How to Read a Troubleshooting Flowchart

How to use a troubleshooting tree without blindly following boxes or skipping the logic behind it

Troubleshooting flowcharts can be extremely useful.

Published August 16, 2026 · Revised September 6, 2026

Back to Biomed Basics

What This Page Explains

This page covers:

The Simple Version

A flowchart converts observations and test results into decision branches. Begin at the stated entry condition, perform the test exactly as defined, and follow the branch that matches the actual result. Each decision should narrow the possible failure area rather than simply move you closer to a replacement box.

Read the notes, prerequisites, units, connector references, and safety conditions around every step. If your result does not fit either branch, stop and verify the setup instead of choosing the closest answer. Record measurements so you can backtrack when a later result conflicts with the path.

Start With the Correct Flowchart

Before following anything, make sure the flowchart actually matches:

A similar model may use different:

Do not assume one flowchart applies to an entire product family unless the manufacturer says it does.

Match the Symptom Exactly

Suppose the manual contains separate sections for:

A blank display is not automatically the same as no power.

The device may be booting normally with only the display path failed.

Choose the symptom that best matches what you actually observe.

Read the Whole Branch Before Starting

Before touching the device, scan the section.

Look for:

You do not want to reach Step 8 and discover the procedure requires a test adapter you do not have.

Understand the Starting Conditions

Flowcharts often assume a specific setup.

Examples:

If you test under different conditions, your result may not mean what the flowchart expects.

A Decision Point Is a Question

Example:

Is the AC power indicator illuminated?

That question divides the possible causes.

Yes

Some part of the AC detection path is working.

No

Focus earlier in the power path.

The question is doing diagnostic work.

Do Not Treat the Question as a Formality

Actually observe or measure the condition.

Do not assume:

It probably is.

A wrong answer sends you down the wrong branch.

Yes and No Need to Be Objective

Some questions are obvious.

Does the display turn on?

Others require measurement.

Is TP5 between 4.75 and 5.25 VDC?

Use the specified limit.

Do not convert that into:

Voltage looks okay.

Follow the Branch You Actually Measured

Suppose the manual says:

If voltage is above 23 VDC:

Go to Step 6.

If below 23 VDC:

Check power supply.

You measure:

18 VDC.

Follow the low-voltage branch.

Do not skip ahead because:

Main boards fail a lot on these.

The flowchart exists to stop that kind of guessing.

Understand What Each Test Proves

Example:

Test:

Measure 24 VDC at power supply output.

Result:

24.1 VDC.

That proves:

The power supply produced approximately 24 V at that point under the conditions tested.

It does not prove:

The next step may test those.

Flowcharts Work by Isolation

Imagine:

Possible causes:

Question:

Is AC present at the inlet?

If yes:

You eliminate much of the external path.

Next question:

Is the fuse good?

Each step narrows the field.

That is the underlying logic.

Use the Test Point Specified

If the manual says:

Measure at TP3 referenced to TP1.

Do not casually measure somewhere else and assume the result is equivalent.

Different ground references or circuit locations may produce different readings.

Verify Your Meter Setup

Before measurements:

Especially important when switching between:

A meter set incorrectly can create dangerous situations or misleading results.

Respect Energized Measurement Warnings

Some flowcharts require powered measurements.

Others specify de-energized testing.

Follow the manufacturer procedure.

Do not perform energized internal measurements unless trained and authorized.

Resistance Checks Usually Require Power Off

If a flowchart says:

Measure resistance across the fuse.

the device is generally expected to be safely de-energized unless stated otherwise.

Do not measure resistance on a live circuit.

Pay Attention to Connector Names

Flowcharts may reference:

Use the board diagram or schematic to locate them correctly.

Do not guess based on physical proximity.

Connector Pin Numbers Matter

Example:

Measure:

Pin 3 to Pin 7.

Pin 3 may be:

24 V.

Pin 4 may be:

Data.

One pin difference can completely change the result.

Read Notes and Footnotes

Important details often hide beside the chart.

Examples:

Do not ignore small print.

Timing Can Matter

A test point may only be active:

If you measure at the wrong time, you may falsely conclude voltage is missing.

Example: Motor Failure

Flowchart:

Command motor movement.

Then:

Is motor voltage present?

If you measure while the motor is idle, 0 V may be completely normal.

Test during the condition specified.

“Replace Board” Is Usually a Conclusion

When a flowchart eventually says:

Replace Main PCB

the steps before it usually exist to prove:

Do not jump directly to that box.

Why Manuals Sometimes Seem to Replace Parts Quickly

Manufacturer flowcharts may be designed for:

The manufacturer may not support repairing individual components on a PCB.

That does not mean the flowchart is saying:

This resistor is definitely bad.

It may mean:

The supported repair for this isolated failure is PCB replacement.

Follow Supported Repair Levels

If the manufacturer supports board-level replacement rather than component repair, follow your authorized scope and facility policy.

Do not modify safety-critical boards outside approved service procedures.

If a Test Fails, Confirm the Test

Before replacing an expensive component, make sure:

One bad measurement can send the entire diagnosis wrong.

Repeat Unexpected Results

If the manual expects:

12 VDC

and you see:

0.3 VDC

pause.

Verify:

Then repeat.

Do not automatically assume the manual is wrong or the board is dead.

Use a Known-Good Device for Context

If available, compare the same point on an identical working unit.

This can help when:

But manufacturer specifications still take priority.

Flowcharts May Use Functional Tests

Not every decision is electrical.

Example:

Does the pump create pressure?

Yes / No.

This may lead toward:

The logic is the same.

Flowcharts May Use Substitution

Example:

Install known-good sensor.

If problem remains:

Proceed to device-side troubleshooting.

This is still a decision point.

You are using comparison instead of voltage.

Do Not Skip Easy Steps Because They Seem Obvious

Flowchart says:

Check cable.

You think:

Cable looks fine.

That is not the same as testing it.

Use the prescribed method or known-good substitution when appropriate.

Skipping Steps Creates Bad Assumptions

Suppose you skip:

Verify power supply output.

Then replace the main board.

Device still dead.

You may have replaced a perfectly good board because you never proved power reached it.

The earlier steps existed for a reason.

But Do Not Follow a Flowchart Blindly

A flowchart is a tool.

If the actual symptom does not match the starting condition, stop.

Example:

Manual flowchart:

Device completely dead.

Your device:

That is not a completely dead device.

Use the display troubleshooting path instead.

Flowchart Does Not Replace Observation

If you discover:

do not ignore obvious evidence because:

The chart says check voltage next.

Safety and actual condition still matter.

Error-Code Flowcharts

Some manuals begin with an error.

Example:

Error 415.

Flowchart:

  1. Inspect cable.
  2. Run calibration.
  3. Measure sensor voltage.
  4. Replace sensor.
  5. Replace board.

The error identifies a detected condition.

The flowchart helps isolate why it occurred.

Self-Test Flowcharts

A device may fail:

Flow Sensor Calibration.

The troubleshooting tree may ask:

Again, do not jump from failed test to failed sensor.

Keep Notes as You Go

Record:

Example:

Step 2:

Fuse F1 continuity = 0.2 Ω.

Step 3:

24 V output = 24.3 VDC.

Step 4:

5 V rail = 0.4 VDC.

This prevents you from repeating work and makes escalation easier.

Notes Are Especially Helpful on Long Trees

If the troubleshooting path has twenty steps, write down your results.

Otherwise you may forget:

Did I check that connector before or after I reseated the board?

Preserve the sequence.

Do Not Change Variables Between Steps Unless Directed

If you reseat every cable before completing the flowchart, you may alter the failure.

Follow the process deliberately.

If Reseating Fixes the Problem

That is useful.

But ask:

What did I actually change?

Did you correct:

Document it.

Do not simply write:

Passed flowchart.

When the Flowchart Ends Without Solving the Problem

Sometimes the device still fails.

Possible reasons:

At that point, return to fundamentals.

Observe.

Isolate.

Test.

Use the flowchart as evidence, not as the entire troubleshooting universe.

Escalating After a Flowchart

Vendor support becomes much more useful if you can say:

Followed no-power flowchart through Step 9. AC input and 24 V rail pass. 5 V rail measures 0.2 V under load. Known-good peripheral produces same result.

That is far better than:

Device doesn't turn on.

Real-World Example: Patient Monitor No Power

Flowchart:

Check outlet.

Pass.

Check cord.

Pass.

Check fuse.

Pass.

Measure supply input.

120 VAC.

Measure 24 V output.

0 VDC.

Supported action:

Replace power supply.

You reached the replacement through evidence.

Real-World Example: SpO2 Not Recognized

Flowchart:

Check compatible sensor.

Pass.

Try known-good sensor.

Still fails.

Inspect connector.

Good.

Run module diagnostics.

Fails.

Supported action:

Replace SpO2 module.

Each earlier branch ruled something out.

Real-World Example: NIBP Failure

Flowchart asks:

Does pump run?

Yes.

Then:

Does pressure increase?

No.

Next:

Check pneumatic path for leak.

Hose leak found.

You never reach pump replacement.

The chart prevented an unnecessary part order.

Real-World Example: Blank Display

Technician initially chooses:

No power.

But device:

Wrong flowchart.

Switch to:

Display blank.

Now troubleshooting focuses on:

Choosing the right starting symptom matters.

Common Mistakes

Using the Wrong Model's Flowchart

Verify documentation.

Choosing the Wrong Symptom

Observe first.

Skipping Early Steps

Simple causes matter.

Guessing at Yes/No Answers

Measure or observe.

Ignoring Test Conditions

Timing and setup matter.

Jumping Straight to “Replace Board”

Follow the isolation.

Treating the Flowchart as Smarter Than Reality

Use your observations too.

Forgetting to Verify After Repair

The flowchart gets you to the repair.

You still need return-to-service verification.

A Useful Way to Think About Every Box

For each decision point, ask:

What possibility is this step trying to eliminate?

Example:

Try known-good cable.

The chart is asking:

Is the external cable causing the failure?

Understanding the reason behind the step makes the entire tree easier to follow.

Another Useful Question

Ask:

If I answer this question incorrectly, where will the flowchart send me?

That reminds you to verify ambiguous results before continuing.

What Did You Actually Prove?

Suppose a flowchart ends with:

Replace Main PCB.

You did not prove:

Every component on the main PCB is defective.

You proved:

The previous tests isolated the failure to a condition for which the manufacturer's supported corrective action is replacement of the main PCB.

That is a more accurate conclusion.

Final Thoughts for Biomeds

A troubleshooting flowchart is not a list of commands.

It is a logic tree.

Every step asks a question.

Every answer removes possibilities.

The better you understand what each question is trying to prove, the more useful the flowchart becomes.

Start with the correct symptom.

Verify the starting conditions.

Measure carefully.

Follow the branch your evidence supports.

Do not skip ahead to the part you expect to be bad.

And if the flowchart stops matching reality, return to the fundamentals.

Observe.

Isolate.

Test.

Verify.

The flowchart is there to organize that process.

Not replace it.

— Jake

Important Note

Troubleshooting flowcharts, test points, expected values, and corrective actions are specific to manufacturer, model, hardware revision, and software version. Follow current service documentation, safety warnings, approved repair levels, required post-repair testing, and your authorized service scope.

Related Biomed Basics

Back to Biomed Basics