Chrysler Voyager. Manual — part 231

Symptom:

ORC MESSAGES NOT RECEIVED

When Monitored and Set Condition:

ORC MESSAGES NOT RECEIVED

When Monitored:

With the ignition in run, and the IOD fuse installed.

Set Condition:

The BCM does not receive any messages from the Occupant Restraint

Controller (ORC) for at least 5 seconds.

POSSIBLE CAUSES

ATTEMPT TO COMMUNICATE WITH THE OCCUPANT RESTRAINT CONTROLLER

BODY CONTROL MODULE

TEST

ACTION

APPLICABILITY

1

Turn the ignition on.
With the DRB, attempt to communicate with the ORC.
Was the DRB able to I/D or communicate with the ORC?

All

Yes

→ Go To 2

No

→ Refer to the Communication category for the related symptom(s).

Perform BODY VERIFICATION TEST - VER 1.

2

With the DRB, erase DTC’s.
Cycle the ignition switch from off to on and wait approximately 1 minute.
With the DRB, read DTC’s.
Did this DTC reset?

All

Yes

→ Replace the Body Control Module in accordance with the service

information.
Perform BODY VERIFICATION TEST - VER 1.

No

→ Test Complete.

351

COMMUNICATION

Symptom:

OTIS MODULE MESSAGES NOT RECEIVED

When Monitored and Set Condition:

OTIS MODULE MESSAGES NOT RECEIVED

When Monitored:

With the ignition in run, and the IOD fuse installed.

Set Condition:

The BCM does not receive any messages from the overhead console for at

least 5 seconds.

POSSIBLE CAUSES

ATTEMPT TO COMMUNICATE WITH THE OTIS

BODY CONTROL MODULE

TEST

ACTION

APPLICABILITY

1

Turn the ignition on.
With the DRB, attempt to communicate with the overhead console.
Was the DRB able to I/D or communicate with the overhead console?

All

Yes

→ Go To 2

No

→ Refer to the Communication category for the related symptom(s).

Perform BODY VERIFICATION TEST - VER 1.

2

With the DRB, erase DTC’s.
Cycle the ignition switch from off to on and wait approximately 1 minute.
With the DRB, read DTC’s.
Did this DTC reset?

All

Yes

→ Replace the Body Control Module in accordance with the service

information.
Perform BODY VERIFICATION TEST - VER 1.

No

→ Test Complete.

352

COMMUNICATION

Symptom:

PCI INTERNAL HARDWARE FAILURE

POSSIBLE CAUSES

PCI INTERNAL HARDWARE FAILURE

TEST

ACTION

APPLICABILITY

1

Connect the DRB to the Data Link Connector.
Turn the ignition on.
With the DRB, erase BCM DTC’s.
Turn the ignition off then turn the ignition on.
With the DRB, read BCM DTC’s.
Did this DTC reset?

All

Yes

→ Replace the Body Control Module in accordance with the service

information.
Perform BODY VERIFICATION TEST - VER 1.

No

→ Test Complete.

353

COMMUNICATION

Symptom:

PCM MESSAGES NOT RECEIVED

When Monitored and Set Condition:

PCM MESSAGES NOT RECEIVED

When Monitored:

With the ignition in run, and the IOD fuse installed.

Set Condition:

The BCM does not receive any messages from the PCM for at least 5

seconds.

POSSIBLE CAUSES

PCM MESSAGE NOT RECEIVED

ATTEMPT TO COMMUNICATE WITH THE PCM

PCI BUS CIRCUIT OPEN

POWERTRAIN CONTROL MODULE

TEST

ACTION

APPLICABILITY

1

Turn the ignition on.
With the DRBIII

t, enter Instrument Cluster, System Tests then PCM Monitor.

Does the DRBIII

t display: PCM is active on BUS?

All

Yes

→ Erase the DTC, if DTC resets, replace the Body Control Module in

accordance with the service information.
Perform BODY VERIFICATION TEST - VER 1.

No

→ Go To 2

2

Turn the ignition on.
With the DRBIII

t, attempt to communicate with the PCM.

Was the DRBIII

t able to communicate with the PCM?

All

Yes

→ Go To 3

No

→ Refer to the communication category and perform the appropriate

symptom.
Perform BODY VERIFICATION TEST - VER 1.

354

COMMUNICATION