(Solved) Dead SDconnect C4 MUX
I also have a dead Star diagnostic MUX,
SDconnect C4, a clone China type. And finally I find the ideal solutions on forums to fix it.
But at first, it only works fine with 38 pin cars, but not with OBDII.
Here is the caesar test I did.
Device: Part D
Toolkit-Resultcode: 1
SDconnect Toolkit - device diagnostic - Part D
==============================================
CAESAR STOS+ Rev.:2.12 from Jun 16 2005
generated protocol file from 01.08.2011 09:12
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 0 Ok
CAESAR Part D2 detected on COM2 with baudrate: 19200
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler- AG
User Authentification 1
Classification 0
Serial Number 028594
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
Special EEPROM check :
D2 Special EEPROM check:
Inst. date registered ... 0 Ok
D2 Special CAN Test :
Special Test ... 3001 Error in CAN1 environment on Part D2 board
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler- AG
User Authentification 1
Classification 0
Serial Number 028594
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
Slave check :
D2 Slave check
D2 Processor ... 0 Ok C165 (mask step CA) is mounted.
D2 RAM ... 0 Ok
D2 FLASH ... 0 Ok
D2 EEPROM ... 0 Ok
D2 SERCTL1 ... 0 Ok
D2 UART1/2 ... 0 Ok
D2 ADC ... 2500 Error ADC
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 12.5 V
D2 Power Ignition ... Voltage KL15 = 00.3 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 1 (+), 34 (-)
Please notice in red are the faults.
Special Test ... 3001 Error in CAN1 environment on Part D2 board( I read that are caused by dead CAN CHIPS ( 2 of them on all MUXs)
D2 ADC ... 2500 Error ADC( I read that this caused by a bad MAX192BCWP)
Here is my dilemma:
a) I am not sure which are the CAN chips. i am guessing that the AN82527 are the ones that need to be replaced, since they are the only ones that are SERIAL COMMUNICATIONS CONTROLLER AREA NETWORK PROTOCOL chips found on the board.
b) I did found the MAX192BCWP)
c) main question is that, i don’t know which ones should I replace first, the CAN chips or the MAX192BCWP, or should I change all of them.
And then I fix the MUX !!!!!
I changed the 2 CAN chips, and MAX.
Now the caesar test is perfect !!!
I need to test the vehicles, but so far looks pretty dam good !!
elfdiagnostic
==============
Device: Part D
Toolkit-Resultcode:
SDconnect C4 + Dell D630 Toolkit - device diagnostic - Part D
==============================================
CAESAR STOS+ Rev.:2.12 from Jun 16 2005
generated protocol file from 06/02/2012 15:10
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 0 Ok
CAESAR Part D2 detected on COM2 with baudrate: 19200
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler- AG
User Authentification 1
Classification 0
Serial Number 028594
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
Special EEPROM check :
D2 Special EEPROM check:
Inst. date registered ... 0 Ok
D2 Special CAN Test :
Special Test ... 0 Ok
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler- AG
User Authentification 1
Classification 0
Serial Number 028594
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
Slave check :
D2 Slave check
D2 Processor ... 0 Ok C165 (mask step CA) is mounted. D2 RAM ... 0 Ok
D2 FLASH ... 0 Ok
D2 EEPROM ... 0 Ok
D2 SERCTL1 ... 0 Ok
D2 UART1/2 ... 0 Ok
D2 ADC ... 0 Ok
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 11.6 V
D2 Power Ignition ... Voltage KL15 = 00.3 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 0 (+), 35 (-)
