Chrysler Repair: 1999 300M, 1999 chrysler 300m, chrysler 300m


Question
This is a follow up to my question below.

I did what you asked.

1.   The dealer indicated that there is no codes.

2.   The “on-off-on-off-on” showed the followings (P1687, P1964 and P1695).

3.   The self-testing showed the following (222222, 44444.4, 777777, 88888.8 and 999999) in the odometer.
In addition, this is what happened today. The fuel, break and ABS light all came and the reading in the odometer showed no bus and then the air condition came by itself.
Sorry for the long e-mail and thank you for your help.

Question
I have 1999 Chrysler 300M with 65K with the following problem.
The air bag light comes first then the check the engine light comes and then the gauges (temperature, speed and rpm) fails. The dealer initially told me that the cluster need to be replaced and after more testing, the dealer now think may be the air bag module is bad. At this point and after two weeks of testing by the dealer, the dealer is not willing to tell me for sure if the problem is the cluster, the air bag module or something else. I hope that you can help


Answer
Hi Mike,
What are the 4-digit fault codes? Usually they are specific enough that the dealer should not be so equivocal. If you have been charged for diagnosis then the work order form should state what fault codes were presented from the readout they did via the diagnostic plug that is under the dash to the left of the steering column.
If you don't have the numbers then if you have an Autozone parts store nearby they will often do the readout for free. Or a private garage should do it for $40 or less. Once you have the fault code numbers let me know.
Try doing two things:
Turn the ignition switch "on-off-on-off-on and leave on" doing that in 5 seconds or less elapsed time. Then watch to see if anything changes in the odometer window of the cluster.
Then turn the ignition key to the lock position. Then press the odometer reset button and hold it while you turn the key to the unlock position. Then release the button and watch the cluster to do some self-testing and again observe for any readout change in the odometer window.
Let me know and we'll go from there.
Roland  

Answer
Hi Mike,
I checked the codes (by the way I assume the '1964' code was actually 1694) and they all speak to a problem of the digital data bus communication with either the body computer, the cluster, or the transmission computer. Given the fact that the cluster did show those 5 different numerical readings on the odometer, and it also said 'no bus' (which means it isn't getting any digital data from the bus itself) I am inclined to the theory that there is a wiring or bias voltage or short problem somewhere in the bus network which includes the three module mentioned above as well as several others.
The analysis of what and where the problem is appears to need to be done by use of a Chrysler diagnostic readout box (DRB III). I am surprised the dealer said there are 'no codes' because clearly yu were able to read the three codes just using the ignition key, nothing fancy.
My inclination would be to see if there is any other Chrysler dealer within driving range and ask if they have a mechanic who specializes in digital data bus problem diagnosis and repair, and also that they have a working DRB III. Tell them the history, and then see what they offer and for how much.
I do have the wiring diagrams for all the modules and so if you were interested in checking the continuity of all the interconnections of the two bus wires that the modules share in common I could xerox copy and postal mail those pages to you. You also could verify whether the bias voltage is present on each wire. It costs me 10 cents per side and there would be probably 59 cents of postage and I would expect fewer that 16 sides would be needed.
You also could try disconnecting the various modules, one at a time, erase the codes (by disconnecting the battery for a minute or so which will only put back in a 1684 code (battery disconnected recently) and then see how the system behaves. Maybe one component when out of the bus network would prove to be palliative and thus suggest that it may be the source of the overall problem.
Roland