Gord Wedman
Well-Known Member
I recently sold my 99 Autobiography to a fellow who was looking for a cheap 4x4 as he lives in a hilly area. The car was in very good condition inside and out. He also liked the roof rack which could carry his kayak. I had bought this car to take off the factory Warn winch installation and swap it onto my offroader. After fixing a few things on the car and driving it a bit over over the summer it seemed to be fine. Before buying the car we test drove it twice, maybe for an hour and all was good. He drove it home, 50km, and no problems. Two days later the ABS and TC lights came on and the speedo stopped working.
I tried scanning for ABS codes with my Hawkeye Total but could not establish a connection. I could scan other modules. Yesterday I took the ABS module from my other 99 and put it in his car. I know this module is good as the other car has no issues and I was able to scan it while it was in the offroader. In his car I once again could not establish a connection so the problem does not seem to be the module.
I have a couple of questions in addition to "what the hell is going on".
1. Does a scanner like the Hawkeye or Nanocom look for trouble codes in the actual module or are these all stored in the BeCM?
2. If the codes are stored in the BeCM does the communication problem indicate a BeCM problem?
3. Do any wires relevant to this problem run through the connectors behind either kick panel? We have not looked there yet.
Hope you folks can help. We are bummed out as we cannot determine what is causing the problem. Thanks for any suggestions.
I tried scanning for ABS codes with my Hawkeye Total but could not establish a connection. I could scan other modules. Yesterday I took the ABS module from my other 99 and put it in his car. I know this module is good as the other car has no issues and I was able to scan it while it was in the offroader. In his car I once again could not establish a connection so the problem does not seem to be the module.
I have a couple of questions in addition to "what the hell is going on".
1. Does a scanner like the Hawkeye or Nanocom look for trouble codes in the actual module or are these all stored in the BeCM?
2. If the codes are stored in the BeCM does the communication problem indicate a BeCM problem?
3. Do any wires relevant to this problem run through the connectors behind either kick panel? We have not looked there yet.
Hope you folks can help. We are bummed out as we cannot determine what is causing the problem. Thanks for any suggestions.