Structured troubleshooting: divide and conquer
Цель: Изучить тему «Structured troubleshooting: divide and conquer» и закрепить её практическими заданиями и самопроверкой.
2 акад. часа чтение и разбор теории, решение задач, работа со схемой или виртуальным стендом и проверка понимания.
Основной материал
Good troubleshooting reduces system into sections and tests boundaries. Determine whether problem is process, sensor, transmitter, wiring, input module, logic, communication, HMI or actuator.
Use independent evidence
If local mechanical gauge and transmitter disagree, investigate measurement. If local transmitter and HART agree but HMI wrong, investigate downstream. If controller output and valve command agree but stem doesn’t move, investigate actuator/air/mechanics.
Avoid shotgun replacement
Replacing sensor, card and cable one by one without measurements may accidentally fix loose terminal but teaches nothing and wastes parts.
Практическая работа
For symptom «level stuck at 50 %» design diagnostic tree from physical level verification to echo profile, 4-20 mA, AI raw and HMI.
Самопроверка
• What is divide-and-conquer?
• Why independent reference useful?
• When inspect actuator?
• What is shotgun troubleshooting?
• Why document test results?
Что нужно запомнить
- Good troubleshooting reduces system into sections and tests boundaries.
- Determine whether problem is process, sensor, transmitter, wiring, input module, logic, communication, HMI or actuator.
- If local mechanical gauge and transmitter disagree, investigate measurement.
- If local transmitter and HART agree but HMI wrong, investigate downstream.
- If controller output and valve command agree but stem doesn’t move, investigate actuator/air/mechanics.