S.T.

Fail Code

Claim
Type

ZTX-43

PA

*Please note in the claim comments if the vehicle had an open WQZ-61R campaign and it will be
closed with either of these submissions.
** This operation number can only be claimed when a software update retry is performed / attempted.
For all software update retry work, an accurate punch count must be recorded. The Straight Time
(S.T.) Labor Time for operation number C067-919 is not to exceed 2.0 hours.

IMPORTANT REMINDERS:
•

SOA strongly discourages the printing and/or local storage of service information as previously
released news and electronic publications may be updated at any time.

•

Always check for any open recalls or campaigns anytime a vehicle is in for servicing.

•

Always refer to STIS for the latest service information before performing any repairs.

Continued...
Bulletin Number: 15-280-21R; Revised: 04/13/21

Page 33 of 39

Reflash Precheck Flow
Precheck Step 1:

Precheck Step 1:
Make note of the Telematics LED status.

Precheck Step 1:

Precheck Step 1:

Telematics LED is
displaying solid
GREEN.

Telematics LED is displaying
solid RED, RED and GREEN
Flashing or RED and GREEN
LEDs are dark (no color visible).

1.

STOP the upgrade.

2.

Inform customer repairs
outside the scope of upgrade
reprogramming service may
be needed.

Customer authorization for
diagnosis is required prior to
continuing.

Precheck Step 1:
Refer to TELEMATICS LED NOT GREEN in APPENDIX B on
page 31.
Use SSM4 to check for the presence of any Telematics DTCs.
If B2A0C or B2A0E are in memory, this does not prevent
completion of the reprogramming service.

Precheck Step 2:
Press the red SOS button to
perform a functional check of
Telematics confirming VIN and
location once connected to a
call center operator.

Precheck Step 1:

Precheck Step 1:

Customer authorizes additional diagnosis and repair.

Customer declines diagnosis
of repair condition.

Telematics system is DTC free and
Telematics LED is GREEN.

STOP. End of Procedure until
required diagnosis and repairs have been completed.
Document Technician
findings on Repair Order.

Precheck Step 3:

Precheck Step 3:

Red SOS button push
SUCCESSFULLY connects to
an operator. VIN and Location
ARE confirmed.

Red SOS button push FAILS
to make connection to an
operator. VIN and Location
ARE NOT confirmed.

Precheck Step 3 (continued):
1. STOP the upgrade.
2. Inform customer repairs needed are outside scope of
upgrade reprogramming service.
Customer authorization decision on needed maintenance
activity is required prior to continuation of reprogramming
service.

Precheck Step 4:
Connect the SSM4 to the
vehicle.

Precheck Step 3 (continued):

Precheck Step 3 (continued):

Customer declines required maintenance work.

Customer approves /
completes maintenance work.
Telematics system is now DTC free,
GREEN LED and connecting to an
operator.

END of Procedure until required maintenance has
been completed. Document Technician findings on
Repair Order.

Continue with reprogramming service.

Precheck Step 6:
Verify Current DCM Software Version.
If the current version of DCM
software is not one of the
listed versions, STOP. Take
no further action and verify
the car is part of the target
population before
proceeding.

Follow Procedure to verify DCM Software
Version ID in the TSB for help on performing
this task.
Is DCM Software Version
05.00.10
05.00.17
05.00.22
05.00.30

Precheck Step 5:
If the current version of DCM software is:
DCM_06.00.17_20190816, the vehicle has the
most recent version of software. STOP, take no
further action and release the car back to the
customer.
Proceed to the Claim Reimbursement, and
Entry Procedures section and process a Version Check Only claim.

YES - Proceed to connect the Midtronics to the
vehicle in Power Supply Mode.

Precheck Step 6:
Open the hood and connect Midtronics GR8 / Midtronics
DCA-8000 in Power Supply Mode.
Refer to 12V Battery / Power Supply Preparations
APPENDIX A on page 29 for more information.

Precheck Step 7:
With the vehicle connected to the Midtronics
equipment in Power Supply mode and battery voltage stabilized, continue procedure
on Reflash Flashing Flowchart.

Continued...
Bulletin Number: 15-280-21R; Revised: 04/13/21

Page 34 of 39

Reflash Flashing Flow
Precheck Step 7c:

Precheck Step 7:

Precheck Step 5:
If the current version of DCM software is
DCM_06.00.17_20190816, the vehicle has already
received the reflash or the DCM was replaced and is
equipped with the most recent version of software.
Take no further action. Proceed to the Claim
Reimbursement, and Entry Procedures section
and process a Version Check Only claim.

If the current version of DCM software is
DCM_06.03.17_20191029, Phase 1 reflashing is
complete proceed to Phase 2: Flashing
Gen1VoLTE 86229DCM02.pk2

With Midtronics equipment connected, confirm DCM software is one of the following: SW
05.00.10, 05.00.17, 05.00.22 or 05.00.30.
If DCM version has not been confirmed in
Step 4, perform Procedure to verify DCM
Software Version ID in the TSB before
proceeding.

(NOTE: It is unlikely a vehicle will enter the
repair facility with this version. This version
should only be present after Phase1 reflashing
procedure has been completed.)

Precheck Step 9:

Precheck Step 8:

Confirm DCM software version.

Confirm DCM software version.

If current version of DCM software is 05.00.10 or 05.00.17, proceed
to Step 1: Phase 1: Flashing intermediate 86229DCM01-1.pak.

If current version of DCM software is 05.00.22 or 05.00.30, proceed to Step
1: Phase 1: Flashing intermediate 86229DCM01-2.pk2.

Precheck Step 9:

Precheck Step 8b:

Confirm DCM software
version.
If current version of DCM
software is 05.00.10 or
05.00.17, proceed to Step 1:
Phase 1: Flashing intermediate 86229DCM01-1.pak.

Reflash FAILS at any time in
Phase 1:

Follow Procedure on page 15:

Follow Procedure on page 8:

Phase1: Flashing intermediate
86229DCM01-1.pak (If the OE SW Version is
05.00.10 or 05.00.17.)

Phase 1: Flashing intermediate
86229DCM01-2.pk2 (Current version of
DCM software is 05.00.22 or 05.00.30.)

Precheck Step 9b (continued):
Reflash FAILS in mid-progress.
Refer to APPENDIX C:
DCM REPROGRAMMING RETRY.
Follow applicable retry strategy as directed
by APPENDIX C.

Precheck Step 10:

If DCM reflash procedure fails
while in progress of Phase 1,
DCM replacement will be
necessary to complete service
campaign on eligible vehicle.

Precheck Step 8b (continued):

If the current version of DCM software is
DCM_06.03.17_20191029, Phase 1 flashing is
complete proceed to Phase 2: Flashing
Gen1VoLTE 86229DCM02.pk2.

Reflash FAILS in mid-progress.

(NOTE: It is unlikely a vehicle will enter the
repair facility with this version. This version
should only be present after Phase1
reflashing procedure has been completed.)

Follow applicable retry strategy as directed
by APPENDIX C.

Refer to APPENDIX C:
DCM REPROGRAMMING RETRY.

Follow Procedure on page 23:
Phase2: Flashing Gen1 VoLTE 86229DCM02.pk2
DCM software version is DCM_06.03.17_20191029

Precheck Step 10a:
Cycle ignition off for 3 to 5 minutes, then back
to on.

Reflash is SUCCESSFUL:

Reflash Fails or DCM Version fails to update
Reflash FAILS at any time in Phase 2.

Refer to APPENDIX C:
DCM REPROGRAMMING RETRY.
Follow applicable retry strategy as directed
by APPENDIX C.

Verify DCM is communicating by retrieving DCM
software version number.

Phase 2 reflash complete successfully but DCM
software version fails to update to correct version.

Proceed to Functional Check of Telematics System.

Reflash Complete:
Step 6 of Reflash procedure: Phase2: Flashing Gen1 VoLTE
86229DCM02.pk2. on page 23.
1.

Perform functional test of the Telematics system with
red SOS button push requesting VIN and location from
an operator.

2.

If vehicle equipped with remote services, it is highly
recommended to confirm operation by having customer
perform remote horn honk.

Functional Check of Telematics System FAILED:
Functional Check to Telematics System SUCCESSFUL:
Release vehicle back to customer.

VEHICLE CANNOT BE RELEASED TO CUSTOMER! DIAGNOSIS
AND REPAIR MUST BE PERFORMED TO RETURN VEHICLE TO
OPERATIONAL STATE IT ARRIVED IN.
Refer to TSBs: 15-267-20 and 15-195-16R for assistance in testing
and operational compliance.

Continued...
Bulletin Number: 15-280-21R; Revised: 04/13/21

Page 35 of 39

APPENDIX C: DCM Reprogramming Retry Strategies
DCM Reprogramming Retry Strategy for Reprogramming Failures Occurring During Update
Completion:
REMINDER: Due to the duration of each reprogramming procedure and consecutive
reprogramming file transfers required to complete this 3G Sunset reprogramming update
successfully, the use of a Subaru- approved Denso SSM4 cable is STRONGLY recommended.
Cables sourced from other manufacturers may not meet data transfer rate and / or interference
shielding requirements to ensure error-free data transmission during reprogramming.
If either of the reprogramming updates fail (update completion is less than 100%), make another
attempt to reprogram using the last file attempted from the beginning of that file's procedure after
confirming the correct file was being used. It does not matter if the reprogramming failure occurs
on the first or second update file installation attempt. If it was the second update file installation that
failed and installation of it fails again, an attempt should be made to start over from the beginning
of the entire procedure and try to install the first update pak file again. The following three retry
procedures are intended to prevent unnecessary DCM replacement. Each retry procedure should be
attempted up to three times with a five minute pause between each.
Retry Procedure 1 is to be used when either the first or second file installation failed- Try up to one
additional time after the initial failed attempt on either file. For example: 86229DCM01-1.pak fails
in the middle of reprogramming. The Technician would perform Appendix C Retry Procedure 1
(Attempt 2).
Retry Procedure 2 is to be used following Retry Procedure 1 (Attempt 2) in a case where the file
installation of Appendix C Retry Procedure 1 (Attempt 2) failed. The Technician should now perform
Appendix C Retry Procedure 2 (Attempt 3) to make one final effort to complete reprogramming
with that file. If reprogramming is successful, continue the procedure as outlined in the TSB. If the
second reprogramming file is the next step, understand that it may be necessary to perform this same
process again with the second file should an initial reprogramming attempt fail. If, after a total of
three (3) attempts, DCM recovery is still unsuccessful, proceed with DCM replacement. Refer to
TSB 15-279-21R "Gen1 Telematics DCM Replacement for 3G Sunset," starting with Step 4 of the
DCM replacement procedure.
Retry Procedure 3 is to be used in a case when both files appear to have successfully completed, but
the DCM version does not match the intended final version as listed in the bulletin. In this case, the
Technician should attempt another reprogramming of the DCM, starting over again with the first file.
Follow the TSB as if it was the first time the procedure is being performed on the vehicle. If, after a
total of two (2) complete reprogramming attempts, DCM recovery is still unsuccessful, proceed with
DCM replacement. Refer to TSB 15-279-21R "Gen1 Telematics DCM Replacement for 3G Sunset,"
starting with Step 4 of the DCM replacement procedure.

IMPORTANT STEPS:
•

Ensure the vehicle is connected to the Midtronics DCA8000 in power supply mode and voltage
has stabilized.

•

Ensure the reprogramming is being performed with the CVT selector in Neutral with the
parking brake set.
Continued...

Bulletin Number: 15-280-21R; Revised: 04/13/21

Page 36 of 39

•

As each update file is completed, ALWAYS:
1. Move the CVT selector into Park.
2. Turn the ignition to OFF and remove the ignition key or, confirm the START button LED is
OFF.
3. WAIT A FULL 30 SECONDS before turning the ignition ON again.

Retry Procedure 1 (attempt #2):
1. Ensure the vehicle has been powered OFF with the selector in Park and the ignition key has
been removed for 5 minutes before starting the next reprogramming attempt.
2. Confirm the correct file was applied based on Repair Order notes. Re-attempt to install the file
which failed again from the beginning of that file’s procedure.
a. If the retry attempt is successful, continue to follow the TSB and proceed to the next steps
as instructed.
b. If the first retry attempt is unsuccessful, move the selector to Park and the ignition to OFF
in preparation of continuing with Retry Procedure 2 (attempt #3) below.
Retry Procedure 2 (attempt #3):
1. Ensure the vehicle has been powered off for at least 5 minutes before the next reprogramming
attempt.
2. Perform the reprogramming from the beginning of the TSB procedure. If that file installation
is successful, continue to follow the TSB procedure and move ahead to the next steps as
instructed.
a. IF the file installation is not successful, move the selector to Park and switch the ignition to
OFF. DCM replacement is now necessary.
b. Refer to TSB 15-279-21: “Gen1 Telematics DCM Replacement for 3G Sunset” starting
with Step 4 of the DCM replacement procedure.

DCM Reprogramming Retry Strategy for Reprogramming Failures Resulting in DCM
Software Failing to Update to Version DCM_06.00.17_20190816:
In a case where both the first and second reprogramming file updates complete successfully BUT, the
DCM Software Version fails to update to DCM_06.00.17_20190816, another reprogramming attempt
must be made beginning with the first reprogramming file and application procedure.

IMPORTANT STEPS:
•

Ensure the vehicle is connected to the Midtronics DCA8000 in power supply mode and voltage
has stabilized.

•

Ensure the reprogramming is being performed with the vehicle in Neutral with the parking
brake set.
Continued...

Bulletin Number: 15-280-21R; Revised: 04/13/21

Page 37 of 39

•

Ensure once reprogramming has completed the selector is moved to Park and the vehicle is
turned OFF for at least A FULL 30 SECONDS before switching the ignition back on for any
reason.

Retry Procedure 3 (attempt #2):
1. Ensure the vehicle has been switched OFF for 5 MINUTES before beginning the next
reprogramming attempt.
2. The original DCM software version was recorded on the Repair Order in Step “e” on page 5 of
the TSB. Reference this version and proceed with Step 7a or 7b as applicable to the recorded
ORIGINAL DCM software version.
3. Continue following the TSB in its entirety from this point as if it is the first time the procedure
is being attempted.
NOTES:
Following a single file’s reprogramming failure, it may be necessary to refer to Retry Procedure 1
and Retry Procedure 2 above to continue attempting successful reprogramming.
Should the reprogramming complete a second time without the DCM Software Version updating
to DCM_06.00.17_20190816, DCM replacement is necessary. Reference TSB 15-279-21: “Gen1
Telematics DCM Replacement for 3G Sunset” starting with Step 4 of the DCM replacement
procedure.

Continued...
Bulletin Number: 15-280-21R; Revised: 04/13/21

Page 38 of 39

Bulletin Number: 15-280-21R; Revised: 04/13/21

Page 39 of 39