Quick answer: The name testo 150 describes a group of modular loggers within the testo Saveris 1 monitoring system, not one instrument that measures both temperature and humidity. Select the module and sensor channels for the required parameters, connect an appropriate communication module, configure the Saveris installation and test alarm delivery before relying on the records.
Choose the correct testo 150 module
| Module | What the module accepts | Typical application |
|---|---|---|
| 150 T1 | Integrated NTC temperature sensor | Room or storage temperature |
| 150 TC4 | Up to four thermocouples | Several industrial temperature points |
| 150 DIN2 | Two miniDIN probe connections | External sensor locations |
| 150 TUC4 | Four compatible digital-probe connections | A multi-parameter installation with supported sensors |
A standalone 150 T1 or TC4 is not a temperature-and-humidity logger. Humidity requires an appropriate supported probe and logger configuration elsewhere in the Saveris 1 system; verify the channel combination in the official module and probe documentation. For related guidance, see testo 190-T1: How to Log Sterilization Cycles Step by.
Build a system, not an isolated logger
A Saveris 1 installation also needs a compatible communications path, system base/software and the chosen sensors. Testo documents WLAN, LAN/Ethernet and optional UltraRange radio modules. These are hardware selections, not automatic features present in every individual logger. Sites with regulated records should plan user access, traceable time, alert escalation and retention before configuring measurement intervals.
Commission a representative monitoring point
- Create a list of rooms, products or process points; specify temperature and humidity where required, plus applicable alarm limits.
- Match each measured quantity to a supported module and probe; confirm ranges, cable routing, channel labels and calibration status.
- Select and fit the compatible communications module, then commission the logger in the actual Saveris 1 infrastructure.
- Configure the recording interval, the clock, alarm notifications and the destination for records. Test an out-of-limit simulation under the approved procedure.
- Inspect a live trend, check its timestamp, interrupt connectivity in a controlled test, and confirm the recovery and data-retention behavior documented for the chosen configuration.
Example: designing a four-location deployment
Hypothetical plan: four refrigeration zones each require one temperature point, and one warehouse also needs humidity. Four temperatures can be assigned to supported temperature channels; the warehouse humidity needs an additional humidity-capable channel and probe rather than being assumed to appear on a TC4. At a 10-minute sample interval, each monitored channel generates 144 readings per day (24 × 60 ÷ 10). Data rates and storage limits still depend on the device and software deployment. For detailed guidance on the four-channel temperature module, see testo 150-TC4 channel setup.
Test an alarm before validation
A trend alone does not show that an alert reaches someone. Confirm threshold, delay, recipient, escalation and acknowledgement, using safe simulated conditions when appropriate. For regulated operations, validation of the installed configuration, change management and backup procedures are separate from the physical instrument’s product claims.
What to do when a channel is missing
- Check whether the chosen 150 module actually supports that quantity or probe connector.
- Inspect physical sensor connection and channel mapping in the system interface.
- Verify the communication module and network path before blaming the sensor.
- Investigate whether a sample is missing versus delayed synchronization, keeping a record of the gap.