DTC INDEX
| DTC | Description |
|---|---|
| DTC B100051 | EOL Not Programmed |
| DTC B100252 | EPB Missing Error |
| DTC B100255 | EPB Present Error |
| DTC B100352 | ABS Missing Error - without ABS unit or connector fault |
| DTC B100355 | ABS Present Error - Coding code error |
| DTC B100552 | Airbag Missing Error - without Airbag unit or connector fault |
| DTC B100555 | Airbag Present Error - Coding code error |
| DTC B100752 | AFLS Missing Error - without AFLS unit or connector fault |
| DTC B100755 | AFLS Present Error - Coding code error |
| DTC B100852 | MDPS Missing Error |
| DTC B100855 | MDPS Present Error |
| DTC B100952 | 4WD Missing Error - without 4WD unit or connector fault |
| DTC B100955 | 4WD Present Error - Coding code error |
| DTC B101052 | ESC Missing Error |
| DTC B101055 | ESC Present Error |
| DTC B102052 | TPMS Missing Error |
| DTC B102055 | TPMS Present Error |
| DTC B104052 | LKAS/LDWS Missing Error - without LKAS/LDWS unit or connector fault |
| DTC B104055 | LKAS/LDWS Present Error - Coding code error |
DTC INDEX
Scheme 101
General Description
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
DTC Description
This DTC B100051 means that it is not programmed cluster in the End of Line. Virgin status. After assembling vehicle or replacing cluster, it is essential to perform coding procedure for the cluster in order to put in the optional information.
If the coding procedure has not performed or made incorrect coding, this DTC will be set so that technicians can recognize it. This DTC can be set from assembly line and will be erased if the EOL programming is completed successfully.
Cluster message in case of virgin status or EOL programming error: "Coding error" will be displayed at LCD monitor on the cluster.
DTC Detecting Condition
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check SCC/EPB/ABS/Airbag/AFLS/MDPS/4WD/ESC/TPMS/LDWS/ECS Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | Not performed cluster coding | |
| DTC Erasing Time | Performed correct coding procedure | ||
| Case 2 | Threshold Value | Failed initial coding performance | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 2, 000ms | ||
Scheme 102
Scheme 103
Scheme 104
Scheme 105
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions". (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis__dtc-detecting-condition) " table)
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to «"VERIFICATION OF VEHICLE REPAIR"»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis__verification-of-vehicle-repair) procedure. NO Fault is intermittent caused by poor contact in the CLU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to «"VERIFICATION OF VEHICLE REPAIR"»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis__verification-of-vehicle-repair) procedure.
Verification of Vehicle Repair
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 106
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100252 is set when variant coding is incorrectly performed as if EPB option is installed on the vehicle even though real vehicle has not EPB on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check EPB ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | EPB CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has EPB option information even though EPB has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 107
Scheme 108
Scheme 109
Scheme 110
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the EPB ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 111
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100255 is set when variant coding is incorrectly performed as if EPB option is not installed on the vehicle even though real vehicle has EPB on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check EPB ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case1 | Threshold Value | The EPB EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case2 | Threshold Value | The EPB is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 112
Scheme 113
Scheme 114
Scheme 115
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the EPB ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 116
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100352 is set when variant coding is incorrectly performed as if ABS option is installed on the vehicle even though real vehicle has not ABS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check ABS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | ABS CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has ABS option information even though ABS has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 117
Scheme 118
Scheme 119
Scheme 120
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the ABS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 121
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100355 is set when variant coding is incorrectly performed as if ABS option is not installed on the vehicle even though real vehicle has ABS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check ABS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The ABS EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The ABS is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 122
Scheme 123
Scheme 124
Scheme 125
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the ABS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 126
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100552 is set when variant coding is incorrectly performed as if Airbag option is installed on the vehicle even though real vehicle has not Airbag on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check SRSCM Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | Airbag CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has Airbag option information even though Airbag has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 127
Scheme 128
Scheme 129
Scheme 130
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the SRSCM's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 131
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100555 is set when variant coding is incorrectly performed as if Airbag option is not installed on the vehicle even though real vehicle has Airbag on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check SRSCM Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The Airbag EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The Airbag is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 132
Scheme 133
Scheme 134
Scheme 135
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the SRSCM's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 136
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100752 is set when variant coding is incorrectly performed as if AFLS option is installed on the vehicle even though real vehicle has not AFLS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check AFLS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | AFLS CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has AFLS option information even though AFLS has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 1, 000ms | ||
Scheme 137
Scheme 138
Scheme 139
Scheme 140
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the AFLS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 141
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100755 is set when variant coding is incorrectly performed as if AFLS option is not installed on the vehicle even though real vehicle has AFLS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check AFLS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The AFLS EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The AFLS is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 1, 000ms | ||
Scheme 142
Scheme 143
Scheme 144
Scheme 145
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the AFLS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 146
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100852 is set when variant coding is incorrectly performed as if MDPS option is installed on the vehicle even though real vehicle has not MDPS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check MDPS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | MDPS CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has MDPS option information even though MDPS has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 147
Scheme 148
Scheme 149
Scheme 150
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the MDPS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 151
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100855 is set when variant coding is incorrectly performed as if MDPS option is not installed on the vehicle even though real vehicle has MDPS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check MDPS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The MDPS EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The MDPS is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 152
Scheme 153
Scheme 154
Scheme 155
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the MDPS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 156
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100952 is set when variant coding is incorrectly performed as if 4WD option is installed on the vehicle even though real vehicle has not 4WD on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check 4WD ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | 4WD CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has 4WD option information even though 4WD has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 157
Scheme 158
Scheme 159
Scheme 160
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the 4WD ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 161
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B100955 is set when variant coding is incorrectly performed as if 4WD option is not installed on the vehicle even though real vehicle has 4WD on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check 4WD ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The 4WD EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The 4WD is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 162
Scheme 163
Scheme 164
Scheme 165
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the 4WD ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 166
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B101052 is set when variant coding is incorrectly performed as if ESP option is installed on the vehicle even though real vehicle has not ESP on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check HECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | ESP CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has ESP option information even though ESP has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 167
Scheme 168
Scheme 169
Scheme 170
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the HECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 171
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B101055 is set when variant coding is incorrectly performed as if ESP option is not installed on the vehicle even though real vehicle has ESP on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check HECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The ESP EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The ESP is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 172
Scheme 173
Scheme 174
Scheme 175
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the HECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 176
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B102052 is set when variant coding is incorrectly performed as if TPMS option is installed on the vehicle even though real vehicle has not TPMS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check TPMS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | TPMS CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has TPMS option information even though TPMS has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 2, 000ms | ||
Scheme 177
Scheme 178
Scheme 179
Scheme 180
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the TPMS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 181
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B102055 is set when variant coding is incorrectly performed as if TPMS option is not installed on the vehicle even though real vehicle has TPMS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check TPMS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The TPMS EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The TPMS is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 2, 000ms | ||
Scheme 182
Scheme 183
Scheme 184
Scheme 185
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the TPMS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 186
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B104052 is set when variant coding is incorrectly performed as if LDWS option is installed on the vehicle even though real vehicle has not LDWS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check LDWS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | LDWS CAN error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | End of line has LDWS option information even though LDWS has not been detected on the CAN BUS | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 187
Scheme 188
Scheme 189
Scheme 190
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the LDWS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.
Scheme 191
Cluster memorizes what kinds of control unit are installed on through the CAN-BUS. vehicle optional information is memorized in cluster by EOL coding procedure in the End Of Line.
DTC will be set if the optional information is different when compared between memorized optional information from CAN-BUS and optional information sent by EOL.
In the assembly line, EOL communication will be finished in case that DTC is not set during DTC searching.
In service field, it is necessary to set cluster by using variant coding procedure with GDS in order to synchronize the optional parts on the vehicle after replacing cluster.
This DTC B104055 is set when variant coding is incorrectly performed as if LDWS option is not installed on the vehicle even though real vehicle has LDWS on the CAN BUS.
| Item | Detecting Condition | Possible Cause | |
|---|---|---|---|
| DTC Strategy | Check CAN communication | Check option information and performance of cluster Perform cluster coding procedure Check LDWS ECU Check CAN line Check Cluster | |
| Enable Conditions | IG key "ON" | ||
| Case 1 | Threshold Value | The LDWS EOL coding error | |
| DTC Erasing Time | In case of correctly performed coding procedure | ||
| Case 2 | Threshold Value | The LDWS is on the CAN bus but no EOL information | |
| DTC Erasing Time | Erased DTC after solved problem | ||
| Diagnostic Time | 500ms | ||
Scheme 192
Scheme 193
Scheme 194
Scheme 195
- Connect GDS.
- IG "ON" and engine "OFF".
- Select "DTC Analysis" mode.
- After erase DTC, keep the vehicle condition within "the enable conditions" (Refer to " «DTC DETECTING CONDITION»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " table).
- Is the same DTC occurred again? YES After checking installed option on the real vehicle firmly, perform "CLU Variant Coding" procedure. And then, go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure. NO Fault is intermittent caused by poor contact in the LDWS ECU's connector or was repaired and CLU memory was not cleared. Thoroughly check connectors for looseness, poor connection, bending, corrosion, contamination, deterioration, or damage. Repair or replace as necessary and then go to " «VERIFICATION OF VEHICLE REPAIR»(/hyundai/santa-fe/iii-2012-2016/remont/communication-devices/#cluster-module-diagnosis) " procedure.
After a repair, it is essential to verify that the fault has been corrected.
- Connect GDS and select "DTC Analysis" mode.
- Clear the DTCs and Operate the vehicle within DTC Enable conditions in General information.
- Is any DTC outputted again? YES Go to the applicable troubleshooting procedure. NO System performing to specification at this time.