Welcome to DBSTalk
- Start new topics and reply to others
- Subscribe to topics and forums to get email updates
- Get your own profile page and make new friends
- Send personal messages to other members.
Posted 16 July 2008 - 08:56 AM
Spock's Law: When something breaks, suspect the least expensive component first.
If your satellite system stops working, it's a connector or a cable that's the most likely cause. Or it's an inexpensive multiswitch. It's least likely to be the expensive receiver.
This also works within a component. If your DVR goes down, it is most likely something inexpensive and mechanical (it's not original to me that mechanical pieces break more often than electronic ones). Even if it is a relatively expensive part within the component, like the hard drive, it is something cheap like a bearing that goes bad.
Spock's Law is not limited to electronics. If your vacuum cleaner stops working, it's probably a filter that's plugged. Problems with your car are usually bearings, gaskets, hoses and stuff like that. Rarely does the main computer die. It even works with expensive cars. For all of you who have problems with your Mercedes, it's not with the drive train, which is practically bullet proof. It's the switch that rolls us the passenger window up and down that goes bad. Now, with a Mercedes, it's probably $187 to replace that switch, but you knew that already.
It is only an advisory. Spock's Law says the most likely piece to be defective is a cheap one. It is not absolute. Your plasma TV can and will break (see my rant that all machines wear out), but if you lose your picture, the first things to check are your connectors.
Spock's Law applies to hardware only. Software is something different. I think it obeys the laws of the Devil.
In a recent thread, a guy believes his replacement DVR is bad. I'm trying to convince him it's more likely an optical cable or the optical connection itself. That's Spock's Law. I don't think I'm succeeding, but my forehead is already flat from slamming against brick walls.
Posted 16 July 2008 - 09:20 AM
Bad cables comprise 90% of the problems with the equipment.
those of DBSTalk.com, DIRECTV, DISH, The Signal Group, or any other company.
Posted 16 July 2008 - 09:32 AM
DirecTV Customer Since 1996
Posted 16 July 2008 - 09:38 AM
For example if you replace a DVR, you have changed that component, every cable that is connected to it, and potentially other equipment that could have been accidentally bumped or changed at the same time. (Since most of us have equipment that is in less than ideal spots for accessing the back of equipment where most of the connections are made, it is easy to affect things other than what we are directly working on.)
This would seem obvious for software changes as well. However, I can't count the number of times I heard a programmer say "My change couldn't have caused that problem." Ninety-nine times out of 100, it is that changed that caused the problem.
Posted 16 July 2008 - 09:43 AM
Posted 16 July 2008 - 12:47 PM
I took it to a buddy who had a B&O service center (I couldn't admit such abject stupidity to my store's own) and he fixed it for me for about $120. I paid that bill, gratefully.
Back on topic: the most likely piece to fail in a satellite system is the F-connector. Compression connectors have made this less so, but still, it is the trouble point.
Posted 16 July 2008 - 03:19 PM
Ah, another story that should have been caught on video tape.
I'd gone from a working piece to one that was trashed cosmetically, mechanically and electrically in less than an hour. Swift.
Posted 16 July 2008 - 03:48 PM
That explains why many of my project folks come back with exhorbitent estimates.
In my profession I'm more familiar with Scotty's Rule: Always overestimate the time required to solve a problem, in order to become a miracle worker when it does not take as long.
DirecTV Customer Since 1996
Posted 16 July 2008 - 09:39 PM
Ninety of those times, the change exposed a flaw in previous programming, and that was what malfunctioned. So the change itself was okay, but implementing it caused a breakdown. Which is why there's a testing department.
I can't count the number of times I heard a programmer say "My change couldn't have caused that problem." Ninety-nine times out of 100, it is that changed that caused the problem.
Posted 17 July 2008 - 03:57 AM
What can go wrong, will go wrong, at the worst possible moment and be totally unrepairable.