Short answer
Use time-aligned engine-coolant temperature and a confirmed charge-air temperature measurement, alongside ambient conditions and vehicle load. Record where each value comes from. A channel labelled intake temperature cannot be assumed to represent air leaving the intercooler, and a dashboard screenshot cannot show the relationship between two circuits over a session.
Key points
- Keep exact channel names, units, logger details and any known sensor location.
- Include speed, engine speed and available load or boost information with the temperature traces.
- Retain warm-up, loaded running and recovery periods in the same timeline.
- State the fitted radiator, intercooler, software and relevant cooling changes.
Know what each measurement represents
- Data: Engine-coolant temperature Use in a parts comparison: Describes the coolant-temperature trend under the recorded use Limit to preserve: Does not directly measure the temperature of compressed intake air
- Data: Confirmed charge-air temperature Use in a parts comparison: Describes air temperature at the documented sensor position Limit to preserve: An unspecified IAT label does not identify that position
- Data: Dedicated intercooler inlet/outlet sensors, if fitted Use in a parts comparison: Allow separate upstream/downstream traces Limit to preserve: Development sensors are not automatically standard vehicle channels
- Data: Ambient, speed and load context Use in a parts comparison: Helps relate the traces to the operating conditions Limit to preserve: A peak number alone loses that context
The purpose is to distinguish measurements before choosing products. An engine radiator acts on the engine-coolant circuit; the charge-air intercooler acts on the compressed intake-air path. A rise in one channel does not identify the other component as the appropriate purchase. Both trends may be relevant, but their labels must remain separate.
What PRL's FL5 development data actually used
PRL's published FL5 intercooler test describes dedicated intercooler measurements and says OBD2 data could not be logged during that test; coolant and oil values came from the LogR display. That is a useful distinction in measurement provenance. Its development traces should not be presented as a ready-made set of channels available through every owner's logger.
For your own enquiry, name the logging device and preserve its original channel names. If sensor location is undocumented, label it as unknown rather than renaming the channel post-intercooler. Additional sensors, ECU-derived data and dashboard readings can all be informative, but the comparison must explain which is which.
Keep enough of the session to make the enquiry meaningful
A continuous record is more useful than only the hottest screenshot. It shows when the temperature rose, what the car was doing and how it recovered. Compare broadly similar operating periods and note changes in ambient conditions or hardware. If boost or load fell during a run, keep that information beside the temperature trace; the later section no longer describes the same demand as the earlier section. Keep timestamps when sharing separate files so air, coolant and load can be compared over the same period.
Important: These logs can make a cooling-parts enquiry more precise. They do not by themselves establish a fault, a safe temperature threshold or a guaranteed result from replacing an intercooler or radiator. Manufacturer development-test temperatures are not operating limits for your car.
