Why does nobody talk about shielded cable degradation in warm hoistways?

For years, I've been battling sporadic communication dropouts between the car controller and the machine room in routine checks. It wasn't just annoying, it added hours to jobs because we'd be chasing ghosts, re-terminating connections that seemed fine. The real kicker was how it only happened under specific load conditions, which made replicating the fault a nightmare. After countless service calls, I started logging every variable: temperature, humidity, even the time of day. Turns out, a particular batch of shielded cable from a few years back has insulation that degrades faster near heat sources, like the motor. By mapping out where those cables were installed and proactively replacing them in slow periods, I've cut those troubleshooting marathons in half. It's not glamorous, but finally having a repeatable fix for something that felt random is a huge weight off. Sharing this here in case anyone else is pulling their hair out over similar gremlins.

3 comments

3 Comments

the_jordan1mo ago

Man, this is such a classic case of the hidden costs in built environments. We're surrounded by systems failing slowly from cheap materials, and it's always the techs who have to detective their way through the mess. Makes you wonder what other time bombs are ticking away in plain sight.

grayy721mo ago

My buddy spent three months chasing phantom packet loss in an old office retrofit. Turns out the original installers used this bargain-bin Cat5e that basically turned to salted licorice inside the walls. He’d get intermittent drops every afternoon when the sun hit that side of the building, just enough heat to change the impedance. They finally tore out a whole chase and the jacket crumbled in his hands like wet cardboard. He said it smelled like burnt sugar and regret.

the_ben1mo ago

Ever notice how the most elusive faults always seem to tie back to something you installed years ago and forgot about? I spent a week once convinced a PLC was possessed, only to find a similar batch of cable had turned brittle behind a conduit clamp. Your method of logging variables is smarter than my approach, which mostly involved a series of increasingly creative curses. It's always the unglamorous fixes that save the most sanity, even if they make you feel a bit silly for not spotting them sooner.