A machine screen can show temperature, speed and percentages together, but those values need not come from the same kind of source. Some describe a quantity measured by a sensing device. Others are calculated from several inputs or represent a selected setting. The field name matters before the number can be interpreted.
A sensing element responds to a physical quantity
Pressure, temperature and position are examples of quantities a sensor can detect. The device provides information that the receiving system can use. TE Connectivity's sensor overview describes this relationship between a physical stimulus and an electrical output.
The electrical representation is not necessarily expressed in the same unit as the physical quantity. A receiving circuit may need to interpret the specified relationship before it can produce a value in engineering units. The sensor's interface therefore matters as well as the name of the quantity.
For example, resistance-based temperature sensing uses a defined relationship between resistance and temperature. TE's RTD explanation describes one such approach. It is an example of a sensing principle, not a claim about the sensor installed on a particular diesel engine.
A calculated value can use more than one input
A control system can combine available information to produce another value. That output should not automatically be treated as the reading of one dedicated sensor. Use the equipment's definition to establish whether the field is measured, calculated or configured.
A percentage is particularly easy to misread. It might describe a measured level, a calculated quantity or a request, depending on the labelled field. The percent sign alone does not tell the reader which physical device, if any, directly provides the value.
A target value also differs from a measured response. A requested speed says what is being asked for; a measured speed describes the reported rotation. Their presence on the same screen does not make them equivalent observations.
The measurement point limits the statement
A temperature value belongs to a defined sensing location and quantity. It should not be renamed as the temperature of the whole engine merely because it appears on an engine page. Preserve the actual field description when transferring it into an equipment report.
The same care applies to pressure. Different measuring points can describe different parts of a system. Two values taken from the same machine are not necessarily expected to agree, even when both are displayed in the same unit.
If the source is unknown, record that gap. Guessing the sensor location from the position of a number on the screen can send a purchase request to the wrong component. The displayed layout is an interface arrangement, not a physical map of the machine.
More digits do not establish greater accuracy
A screen can present a value with several decimal places without proving that the entire measurement is accurate to that level. Display formatting, sensor characteristics and the receiving system are separate considerations. Do not use the number of digits as a substitute for the applicable specification.
Keep any stated accuracy with its conditions and source. A specification for a sensing element alone should not silently become a claim about the complete installed measurement system. If the requirement concerns a replacement sensor, obtain its documented characteristics for that application.
Keep a configured threshold separate from the measured quantity too. A limit displayed beside a reading describes a comparison setting; it should not be copied into the record as another sensor measurement.
Identify the source before naming a replacement
An unexpected field value does not identify a failed sensing device by itself. Establish what the field represents and let the responsible service process determine the component requirement. A calculated value may depend on information from more than one place.
The separate sensor-to-display data guide follows the information path. For pressure references, see gauge, absolute and differential pressure. A useful report preserves the field definition; a useful purchase request follows a confirmed part requirement.
