Compressor Electrical & Control Diagnostics, Power-System Fault & Automation Reliability Engineering

It requires competent isolation and measurement practice; begins with voltage imbalance, phase loss, protection trips, loose connections and settings; uses controller alarm/event history, sensor values, digital I/O and communications to reconstruct fault sequence; requires pressure/temperature transducers, wiring and reference signals to be verified before controller replacement; and requires firmware, parameters and logic to be backed up and altered only with authorised model documentation. These controls are expanded without inventing universal protection settings or control-panel/VFD competence.

Provisional new-series slug: /compressed-air-engineering/electrical-control-diagnostics-power-system-automation-reliability/ | CTA: Diagnose My Compressor Electrical & Controls System

Do not replace the controller because the screen shows a fault. prove whether the fault began in the supply, protection, motor, sensor, wiring, I/o, communications, logic or the mechanical load the control system is trying to manage

Electrical symptoms can mimic mechanical failures, and mechanical overload can trigger electrical protection. A pressure sensor can create a control problem; a loose connection can create a drive fault; a configuration change can create a process symptom.

The diagnostic objective is therefore correlation: preserve event chronology, verify supply and protection, validate sensors and I/O, compare controller commands with physical response, protect configuration and escalate hazardous or specialist electrical work to qualified personnel.

1 — Compressor Identity

Electrical-Control Foundation: govern compressor identity as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

2 — Controller Identity

Electrical-Control Foundation: govern controller identity as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

3 — Motor Identity

Electrical-Control Foundation: govern motor identity as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

4 — Starter/Vfd Identity

Electrical-Control Foundation: govern starter/VFD identity as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

5 — Supply Architecture

Electrical-Control Foundation: govern supply architecture as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

6 — Control Voltage

Electrical-Control Foundation: govern control voltage as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

7 — Operating Hours

Electrical-Control Foundation: govern operating hours as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

8 — Fault Timestamp

Electrical-Control Foundation: govern fault timestamp as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

9 — Operating State

Electrical-Control Foundation: govern operating state as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

10 — Recent Maintenance

Electrical-Control Foundation: govern recent maintenance as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

11 — Recent Parameter Change

Electrical-Control Foundation: govern recent parameter change as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

12 — Recent Electrical Work

Electrical-Control Foundation: govern recent electrical work as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

13 — Site Power Event

Electrical-Control Foundation: govern site power event as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

14 — Technical Documentation

Electrical-Control Foundation: govern technical documentation as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

15 — Revision Control

Electrical-Control Foundation: govern revision control as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

16 — Electrical Isolation

Safety Isolation & Measurement: govern electrical isolation as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

17 — Stored Electrical Energy Boundary

Safety Isolation & Measurement: govern stored electrical energy boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

18 — Dc-Bus Boundary

Safety Isolation & Measurement: govern DC-bus boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

19 — Remote-Start Prevention

Safety Isolation & Measurement: govern remote-start prevention as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

20 — Multiple Supply Boundary

Safety Isolation & Measurement: govern multiple supply boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

21 — Control Supply Isolation

Safety Isolation & Measurement: govern control supply isolation as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

22 — Pneumatic Stored Energy

Safety Isolation & Measurement: govern pneumatic stored energy as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

23 — Test-Before-Touch Boundary

Safety Isolation & Measurement: govern test-before-touch boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

24 — Rated Test Instrument

Safety Isolation & Measurement: govern rated test instrument as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

25 — Measurement Category Boundary

Safety Isolation & Measurement: govern measurement category boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

26 — Ppe/Site Rule Boundary

Safety Isolation & Measurement: govern PPE/site rule boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

27 — Competent Person

Safety Isolation & Measurement: govern competent person as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

28 — Live-Testing Boundary

Safety Isolation & Measurement: govern live-testing boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

29 — Re-Energisation Control

Safety Isolation & Measurement: govern re-energisation control as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

30 — Isolation Record

Safety Isolation & Measurement: govern isolation record as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

31 — Line Voltage

Incoming Supply: govern line voltage as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

32 — Phase-To-Phase Voltage

Incoming Supply: govern phase-to-phase voltage as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

33 — Phase Imbalance

Incoming Supply: govern phase imbalance as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

34 — Phase Loss

Incoming Supply: govern phase loss as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

35 — Frequency

Incoming Supply: govern frequency as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

36 — Supply Interruption

Incoming Supply: govern supply interruption as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

37 — Undervoltage

Incoming Supply: govern undervoltage as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

38 — Overvoltage

Incoming Supply: govern overvoltage as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

39 — Generator Supply Boundary

Incoming Supply: govern generator supply boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

40 — Transformer Boundary

Incoming Supply: govern transformer boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

41 — Harmonic Boundary

Incoming Supply: govern harmonic boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

42 — Earthing Boundary

Incoming Supply: govern earthing boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

43 — Connection Condition

Incoming Supply: govern connection condition as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

44 — Supply Event History

Incoming Supply: govern supply event history as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

45 — Source Verification

Incoming Supply: govern source verification as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

46 — Main Breaker

Protection & Switching: govern main breaker as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

47 — Fuse

Protection & Switching: govern fuse as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

48 — Motor Protection

Protection & Switching: govern motor protection as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

49 — Overload Relay

Protection & Switching: govern overload relay as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

50 — Contactor

Protection & Switching: govern contactor as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

51 — Starter

Protection & Switching: govern starter as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

52 — Phase Monitor

Protection & Switching: govern phase monitor as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

53 — Undervoltage Protection Boundary

Protection & Switching: govern undervoltage protection boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

54 — Earth-Fault Boundary

Protection & Switching: govern earth-fault boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

55 — Thermal Protection

Protection & Switching: govern thermal protection as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

56 — Trip Setting Boundary

Protection & Switching: govern trip setting boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

57 — Coordination Boundary

Protection & Switching: govern coordination boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

58 — Loose Terminal

Protection & Switching: govern loose terminal as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

59 — Heat/Discolouration

Protection & Switching: govern heat/discolouration as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

60 — Trip History

Protection & Switching: govern trip history as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

61 — Motor Nameplate

Motor Electrical Condition: govern motor nameplate as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

62 — Rated Voltage

Motor Electrical Condition: govern rated voltage as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

63 — Rated Current

Motor Electrical Condition: govern rated current as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

64 — Connection

Motor Electrical Condition: govern connection as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

65 — Running Current

Motor Electrical Condition: govern running current as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

66 — Phase-Current Balance

Motor Electrical Condition: govern phase-current balance as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

67 — Motor Temperature

Motor Electrical Condition: govern motor temperature as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

68 — Winding Sensor

Motor Electrical Condition: govern winding sensor as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

69 — Insulation Boundary

Motor Electrical Condition: govern insulation boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

70 — Bearing/Mechanical Load Interaction

Motor Electrical Condition: govern bearing/mechanical load interaction as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

71 — Cable Condition

Motor Electrical Condition: govern cable condition as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

72 — Terminal Condition

Motor Electrical Condition: govern terminal condition as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

73 — Starts Per Hour Boundary

Motor Electrical Condition: govern starts per hour boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

74 — Overload Evidence

Motor Electrical Condition: govern overload evidence as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

76 — Alarm History

Controller Evidence: govern alarm history as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

77 — Event History

Controller Evidence: govern event history as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

78 — Trip History

Controller Evidence: govern trip history as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

79 — Timestamp

Controller Evidence: govern timestamp as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

80 — Operating Mode

Controller Evidence: govern operating mode as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

81 — Load/Unload State

Controller Evidence: govern load/unload state as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

82 — Vsd State

Controller Evidence: govern VSD state as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

83 — Pressure Value

Controller Evidence: govern pressure value as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

84 — Temperature Value

Controller Evidence: govern temperature value as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

85 — Digital Inputs

Controller Evidence: govern digital inputs as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

86 — Digital Outputs

Controller Evidence: govern digital outputs as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

87 — Analogue Inputs

Controller Evidence: govern analogue inputs as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

88 — Command Outputs

Controller Evidence: govern command outputs as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

89 — Service Counters

Controller Evidence: govern service counters as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

90 — Event Export

Controller Evidence: govern event export as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

91 — Pressure Transducer

Sensors & Signal Integrity: govern pressure transducer as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

92 — Temperature Sensor

Sensors & Signal Integrity: govern temperature sensor as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

93 — Dp Sensor

Sensors & Signal Integrity: govern DP sensor as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

94 — Dew-Point Sensor Boundary

Sensors & Signal Integrity: govern dew-point sensor boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

95 — Current Sensor

Sensors & Signal Integrity: govern current sensor as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

96 — Speed Feedback

Sensors & Signal Integrity: govern speed feedback as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

97 — Raw Signal

Sensors & Signal Integrity: govern raw signal as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

98 — Engineering Scaling

Sensors & Signal Integrity: govern engineering scaling as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

99 — Sensor Supply

Sensors & Signal Integrity: govern sensor supply as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

100 — Wiring

Sensors & Signal Integrity: govern wiring as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

101 — Connector

Sensors & Signal Integrity: govern connector as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

102 — Shield/Ground Boundary

Sensors & Signal Integrity: govern shield/ground boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

103 — Reference Check

Sensors & Signal Integrity: govern reference check as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

104 — Plausibility

Sensors & Signal Integrity: govern plausibility as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

106 — Emergency Stop

I/O Interlocks & Permissives: govern emergency stop as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

107 — Door/Guard Interlock Boundary

I/O Interlocks & Permissives: govern door/guard interlock boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

108 — Pressure Permissive

I/O Interlocks & Permissives: govern pressure permissive as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

109 — Temperature Permissive

I/O Interlocks & Permissives: govern temperature permissive as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

110 — Oil-Level/Pressure Boundary

I/O Interlocks & Permissives: govern oil-level/pressure boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

111 — Motor Protection Input

I/O Interlocks & Permissives: govern motor protection input as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

112 — Dryer/Treatment Interlock Boundary

I/O Interlocks & Permissives: govern dryer/treatment interlock boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

113 — Remote Enable

I/O Interlocks & Permissives: govern remote enable as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

114 — Local/Remote Mode

I/O Interlocks & Permissives: govern local/remote mode as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

115 — Start Permissive

I/O Interlocks & Permissives: govern start permissive as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

116 — Run Feedback

I/O Interlocks & Permissives: govern run feedback as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

117 — Fault Feedback

I/O Interlocks & Permissives: govern fault feedback as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

118 — Output Relay

I/O Interlocks & Permissives: govern output relay as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

119 — Solenoid Command

I/O Interlocks & Permissives: govern solenoid command as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

120 — Physical-Response Verification

I/O Interlocks & Permissives: govern physical-response verification as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

121 — Fieldbus Boundary

Communications & Automation: govern fieldbus boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

122 — Serial Communication

Communications & Automation: govern serial communication as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

123 — Ethernet Boundary

Communications & Automation: govern Ethernet boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

124 — Controller-To-Vfd Link

Communications & Automation: govern controller-to-VFD link as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

125 — Sequencer Link

Communications & Automation: govern sequencer link as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

126 — Remote Monitoring Boundary

Communications & Automation: govern remote monitoring boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

127 — Gateway

Communications & Automation: govern gateway as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

128 — Communication Timeout

Communications & Automation: govern communication timeout as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

129 — Stale Data

Communications & Automation: govern stale data as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

130 — Address/Configuration

Communications & Automation: govern address/configuration as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

131 — Network Power

Communications & Automation: govern network power as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

132 — Shielding Boundary

Communications & Automation: govern shielding boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

133 — Data-Quality Flag

Communications & Automation: govern data-quality flag as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

134 — Fallback Behaviour

Communications & Automation: govern fallback behaviour as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

136 — Parameter Backup

Configuration Firmware & Change Control: govern parameter backup as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

137 — Controller Backup

Configuration Firmware & Change Control: govern controller backup as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

138 — Vfd Backup

Configuration Firmware & Change Control: govern VFD backup as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

139 — Firmware Version

Configuration Firmware & Change Control: govern firmware version as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

140 — Software Version

Configuration Firmware & Change Control: govern software version as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

141 — Setpoint

Configuration Firmware & Change Control: govern setpoint as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

142 — Scaling

Configuration Firmware & Change Control: govern scaling as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

143 — Motor Data

Configuration Firmware & Change Control: govern motor data as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

144 — I/O Mapping

Configuration Firmware & Change Control: govern I/O mapping as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

145 — Logic Revision

Configuration Firmware & Change Control: govern logic revision as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

146 — Sequencer Settings

Configuration Firmware & Change Control: govern sequencer settings as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

147 — Password/Access Boundary

Configuration Firmware & Change Control: govern password/access boundary as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

148 — Authorised Documentation

Configuration Firmware & Change Control: govern authorised documentation as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

149 — Change Record

Configuration Firmware & Change Control: govern change record as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

150 — Restore Verification

Configuration Firmware & Change Control: govern restore verification as part of the electrical-to-control-to-machine evidence chain. Record exact equipment identity, safe test boundary, operating state, measurement point/method, applicable model documentation, event chronology, result, confidence and unresolved uncertainty. Do not infer a failed controller from an alarm alone and do not alter protection, firmware, parameters or logic without authorised model-specific documentation and qualified competence. Correlate electrical evidence with actual compressor load and physical response.

151 — Premium Electrical & Controls Diagnostic Register

152 — Electrical / Control Fault Triage Matrix

154 — Controller Evidence Is Chronology

Alarm/event history, sensor values, digital I/O and communications should reconstruct what happened before the trip, not merely display the final alarm.

156 — Command Does Not Prove Physical Response

A controller output can be correct while a contactor, solenoid, valve or actuator fails. Verify the complete command-to-machine chain.

157 — Configuration Is an Engineering Asset

Back up firmware/parameters/logic before changes where supported. A replacement or reset without known-good configuration can create a second fault.

158 — Technical / Electrical-Control Verification Gate

Verify qualified isolation, supply/protection, motor load, controller events, sensors, I/O, communications and configuration. No control-panel/VFD competence or universal protection-setting claim is permitted.

160 — AEO / Engineering FAQ Layer

Answer why compressors fail to start, why breakers trip, how sensor faults mimic controller faults, how event logs are used, why configuration backups matter and when qualified electrical/drive review is required.