HP Model 748 HP Model 748 Service Handbook - Page 46

Introduction to Troubleshooting, Diagnostic Philosophy, Analytic Troubleshooting

Page 46 highlights

Troubleshooting Introduction to Troubleshooting Introduction to Troubleshooting Troubleshooting information and procedures for the Model 743/744i board computers are divided into these sections: • Introduction to Troubleshooting • Diagnostic Overview Model 743 and Model 744 board computers use different firmware and diagnostic tools. Consult the appropriate Service Handbook for the model you are working with for specifics on the various tools and tests for that model. Diagnostic Philosophy The diagnostic philosophy is to support the repair strategy. As a result, the goal of the troubleshooting process is to isolate a problem to a specific board or assembly. Several diagnostic methods may be used. When a system problem is traced to the board computer, the diagnostic is run to isolate the problem to the defective part. The defective part is then replaced. Analytic Troubleshooting Troubleshooting is the process of getting answers to these six questions: • What is different now from what the board computer was before? • What exactly is wrong, or what are the bad symptoms? • When do the bad symptoms occur? • How bad is the problem or to what extent does it occur? • What actually caused the problem in the first place? Getting the answers to these questions usually makes the troubleshooting process much more effective and less costly. When a failure in a computer system occurs, use these questions and their answers to begin your diagnostic procedure. The troubleshooting strategy for these board computers is in the form of a bottom-up approach. That is, you note any error or status messages, and then you run the power-up Boot ROM diagnostics known as Self-Test. If the Self-Test diagnostics fail, replace the assembly that is indicated. 4-2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98

Troubleshooting
Introduction to Troubleshooting
4-2
Introduction to Troubleshooting
Troubleshooting information and procedures for the Model 743/744i board computers are
divided into these sections:
Introduction to Troubleshooting
Diagnostic Overview
Model 743 and Model 744 board computers use different firmware and diagnostic tools.
Consult the appropriate Service Handbook for the model you are working with for specif-
ics on the various tools and tests for that model.
Diagnostic Philosophy
The diagnostic philosophy is to support the repair strategy. As a result, the goal of the
troubleshooting process is to isolate a problem to a specific board or assembly. Several
diagnostic methods may be used. When a system problem is traced to the board computer,
the diagnostic is run to isolate the problem to the defective part. The defective part is then
replaced.
Analytic Troubleshooting
Troubleshooting is the process of getting answers to these six questions:
What is different now from what the board computer was before?
What exactly is wrong, or what are the bad symptoms?
When do the bad symptoms occur?
How bad is the problem or to what extent does it occur?
What actually caused the problem in the first place?
Getting the answers to these questions usually makes the troubleshooting process much
more effective and less costly. When a failure in a computer system occurs, use these
questions and their answers to begin your diagnostic procedure.
The troubleshooting strategy for these board computers is in the form of a bottom-up
approach. That is, you note any error or status messages, and then you run the power-up
Boot ROM diagnostics known as Self-Test. If the Self-Test diagnostics fail, replace the
assembly that is indicated.