Pages: 1 [2]   Go Down
Author Topic: Debugging - a dark art?  (Read 2415 times)
0 Members and 1 Guest are viewing this topic.
Central MN, USA
Offline Offline
Tesla Member
***
Karma: 75
Posts: 7267
Phi_prompt, phi_interfaces, phi-2 shields, phi-panels
View Profile
WWW
 Bigger Bigger  Smaller Smaller  Reset Reset

Not at all computer-related, but my f(l)avourite debugging story, ever.

Awesome! Thanks for sharing.
Logged


Maine
Offline Offline
Sr. Member
****
Karma: 14
Posts: 418
Caution: Explosives in use.
View Profile
WWW
 Bigger Bigger  Smaller Smaller  Reset Reset

Not at all computer-related, but my f(l)avourite debugging story, ever.

I actually had something similar happen with my truck. Every time I stopped at a store in this one specific town next to mine, my truck would either start hard, or not start at all. It only happened at stores in that town, and I never had a problem anywhere else. My friends always joked that it must be something in the air that my truck didn't like. It turned out to be a faulty oil pressure sensor. When heading to that town, I always took the interstate, which heated up the oil in my truck and lowered the oil pressure. In addition to that, the town was built on a wetland, so all the stores have slanted parking lots from the massive amount of fill that had to be trucked in to make the land suitable for building. The grade was enough to drain the already low pressure oil out of the sensor, and trigger a "low oil pressure" condition that is designed to prevent the engine from running in the event that it is severely damaged in a crash. Apparently the computer doesn't record that error condition, since it would normally be observable from outside the truck.

I was finally able to replicate the problem (by accident) in my driveway when I had one side of the truck up on ramps.
Logged

"Anyone who isn't confused really doesn't understand the situation."

Electronic props for Airsoft, paintball, and laser tag -> www.nightscapetech.com

Pages: 1 [2]   Go Up
Jump to: