2 - 68
Chapter 2 Troubleshooting
FIP-1.30 024-371: MCU-ESS Communication Fail
Step Check
Remedy
Yes No
Possible causative parts:
PWBA ESS AIO (PL8.1.2)
PWBA MCU (PL8.3.6)
HARNESS ASSY ESS MG AIO (PL9.1.1)
1
Checking after resetting the PWBA ESS AIO and PWBA
MCU.
Reseat the PWBA ESS AIO and PWBA MCU.
Does the error still occur when the power is turned OFF and
ON?
Go to step 2. End of work.
2
Checking the connectors for connection.
Check the connections between the PWBA MCU and
PWBA ESS AIO.
Are P/J10 and P/J101 connected correctly?
Go to step 4.
Reconnect the
connector(s) P/
J10 and/or P/J101
correctly, then go
to step 3.
3
Does the error still occur when the power is turned OFF and
ON?
Go to step 4. End of work.
4
Checking the HARNESS ASSY ESS MG AIO for continuity.
Disconnect J10 from the PWBA MCU.
Disconnect J101 from the PWBA ESS AIO.
Is each cable of J10 <=> J101 continuous?
Go to step 5.
Replace the
HARNESS ASSY
ESS MG AIO.
5
Checking the firmware version
Is the firmware the latest version?
Go to step 6.
Upgrade the
firmware.
6
Checking after replacing the PWBA MCU.
Replace the KIT PWBA MCU. (Refer to REP8.10.)
Does the error still occur when the power is turned OFF and
ON?
Replace the KIT
PWBA ESS AIO.
(Refer to REP8.2.)
End of work.
To Next Page
Loading...
Need help?
General
