In 2017, I reset a Rittal cooling unit because the plant manager was standing behind me and the production line was already behind schedule. I held the button. The red LED went off. The compressor started again. For about 40 minutes, I looked like the person who had saved the day. Then the high-temperature alarm came back, and I had to tell the plant manager that the same fault was still there, only now we were also 40 minutes further behind.
If you have ever searched how do you reset a phone after a frozen screen, you already know the trap. If you have also searched how do you clear phone app cache when storage runs low, you know a second truth: clearing something is not the same as fixing it. A reset clears the active fault on a Rittal cooling unit. It does not clear the environmental or mechanical condition that caused the fault.
The Surface Problem: The Alarm That Keeps Coming Back
The most common call I get from maintenance teams is not our cooling unit is dead. It is we reset it twice and the alarm is back. Most people treat the reset as the fix. It is not. It is a way to tell the controller to try again.
On a Rittal Blue e+ wall-mounted cooling unit, the reset procedure clears the current fault and sends the unit back into run mode if conditions are within the allowed operating range. That part is real. I checked the Rittal US documentation for the Blue e+ series in January 2025. But if the condition that triggered the fault is still present, the alarm will return. This is not a design flaw. It is the controller doing its job. It is telling you that the enclosure is still outside safe limits.
The Deeper Cause: Why the Reset is a Symptom, Not a Solution
The question on every maintenance forum is how do you reset a phone. The better question is what made the phone freeze. With cooling units, the equivalent is what made the cabinet overheat. My first year, I did not ask that question. I reset, observed, reset again, and eventually ordered parts I did not need.
There are four real culprits behind a recurring high-temperature alarm. The first is a blocked condenser filter. This is the boring answer, and it is also the most common. The second is installation. A correctly sized Rittal cooling unit can fail because the exhaust from another cabinet is blowing directly into its air intake. The third is a loose or dirty connector on the temperature sensor. The sensor reports a value that is not real, and the controller reacts to it as if it were real. The fourth is ambient temperature above the unit's rated maximum. In that case, the unit is not the problem; the room is.
The deeper issue is a causal reversal. People think the alarm causes the shutdown. Actually, the alarm is the result of a condition that has already started to damage the electronics. The controller shuts down to protect the equipment. When you reset, you are not clearing the condition. You are clearing the warning that the condition exists.
The Cost of Treating the Reset as the Fix
I still kick myself for not checking the filter on a panel in a washdown area back in 2018. The alarm would reset in the morning and come back after lunch. I was convinced the sensor was drifting. I ordered a replacement controller. It cost $612. The problem did not go away. Then I opened the filter cover and found a layer of dust so dense that the filter could almost stand up by itself. A replacement filter cost $18. I turned an $18 problem into a $612 mistake, plus freight and downtime.
The hidden cost is even larger. On a telecom site, I watched a Rittal cooling unit cycle on and off for three days. The cabinet did not melt. The radio equipment throttled. Throughput dropped by half. Nobody measured that loss, but it was far bigger than the replacement controller I had almost ordered. The alarm was telling me the cabinet was too hot. I kept silencing the alarm, and the gear kept paying the price.
I went back and forth with our team about whether to keep an extra sensor connector in stock or rely on overnight shipping. On paper, overnight shipping was cheaper. My gut said we would need it on a Friday evening. We now keep spare connectors in the cabinet. That is not a sophisticated decision. It is a scarred decision.
What I Do Before I Hit Reset
Now I maintain a checklist for our team. It has caught 47 potential repeat failures in the past 18 months. The checklist is not from a textbook. It is from my own documented mistakes.
- Read the fault code and write it down before touching anything. (I missed that in my early years because I reset the code before recording it.)
- Measure return air temperature and ambient temperature. If ambient is above the unit's maximum rating, the room must be fixed first.
- Open the condenser filter cover and inspect the filter, not just glance at it.
- Check the coil, fan blade, and recirculation path for debris.
- Check the sensor connector for corrosion or looseness. A bad connection can create false high-temperature alarms.
- Only then reset the unit and watch a complete cooling cycle. A compressor that runs for 30 seconds and stops again is a different diagnostic situation than one that runs for 20 minutes.
This is also where I know my boundary. I am not a Rittal factory technician. If the problem is in the refrigeration circuit, high pressure, low pressure, or a compressor that will not start, I call Rittal US technical support. A third-party tech playing with the refrigerant loop can turn a $200 repair into a $1,400 replacement. The same logic applies to firmware. If a controller is stuck in a fault state that a normal reset will not clear, the answer is not to power-cycle it eight times. The answer is to ask Rittal US for the reset procedure for that firmware version. (I learned this in 2022 on a CMC III controller.)
A vendor who says this is outside our scope and here is who does it better earns my trust for everything else. A specialist who knows the limits of his own role is the one I listen to first. The reset habit is the opposite of that. It pretends every fault is the same fault. The good news is that a Rittal cooling unit is usually honest. It repeats the alarm because you have not fixed what caused it. Listen to that repetition. It is more useful than any search result for how do you reset a phone.
