Mb Star DAS Fault

**icedillon** · 25th January, 2010, 09:06 PM

Hi All,

Bought a multiplexer kit some months ago from china. Used it a handful of times and it worked fine. However using it this morning it brings up a fault

Fault (1.1)-1.501.9302
initialization of multplexer failed
Possible causes:
The link between the multiplexer and diagnostic is interrupted
The link betweeen the multiplexer and diagnostic unit is interrupted
The voltage supply at the diagnostic socket(circuit 30 and or 31) is faulty
When using sd connect, check the connection status using the toolkit.

Just though I'd mention the kit has been in the trunk of my car for about 6 weeks, some days did get -8 degrees celsius although I'm sure that shouldnt make any difference. I have also warmed the unit up in the house with no joy.

Any ideas?

**Room** · 25th January, 2010, 09:43 PM

Run cesar selfdiagnostic in star utility.
Write the result.

**minvita04** · 26th January, 2010, 03:48 PM

you can use the self test on STAR Utilities and try what is the problems then after selftest you can got a result for it

**icedillon** · 26th January, 2010, 10:42 PM

Originally Posted by Room

Run cesar selfdiagnostic in star utility.
Write the result.

Dont you need a special lead to run the self test??

I tried it but can't really understand what to do.

**icedillon** · 26th January, 2010, 11:23 PM

Originally Posted by Room

Run cesar selfdiagnostic in star utility.
Write the result.

Also does the unit have to be connected to the vehicle to do a cesar test?

**Room** · 27th January, 2010, 09:56 PM

Run STAR Utilities then Self Diagnosis and CAESAR Self Diagnosis.

Unit must be power up ( led must be light).
You can do it by connecting to the vehicle or simply supplies power ( if you use OBD, pin 4 is GND and pin 16 is +12V )

**DB_member** · 28th January, 2010, 07:35 AM

Originally Posted by Room

Run STAR Utilities then Self Diagnosis and CAESAR Self Diagnosis.

Unit must be power up ( led must be light).
You can do it by connecting to the vehicle or simply supplies power ( if you use OBD, pin 4 is GND and pin 16 is +12V )

The standard setup should include the 4-pin diagnosis cable which is easy to connect to a power supply.

**automite** · 19th February, 2010, 04:37 PM

I have the same problem, below is my diagnostic result.

CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 19.02.2010 09:12
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 0 Ok

CAESAR Part D2 detected on COM3 with baudrate: 19200
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler-Benz AG
User Authentification 1
Classification 0
Serial Number 123456
Authorization Level 3
Part D
Hardware Authentification 010202
Hardware Date 080103
Special EEPROM check :
D2 Special EEPROM check:
Inst. date registered ... 303 Not possible to test this version of HW
D2 Special CAN Test :
Special Test ... 0 Ok
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler-Benz AG
User Authentification 1
Classification 0
Serial Number 123456
Authorization Level 3
Part D
Hardware Authentification 010202
Hardware Date 080103
Slave check :
D2 Slave check
D2 Processor ... 0 Ok C165 (mask step HA) is mounted.
D2 RAM ... 0 Ok
D2 FLASH ... 1703 Error occured while erasing FLASH
D2 EEPROM ... 1802 Error (access to EEPROM)
D2 SERCTL1 ... 0 Ok
D2 UART1/2 ... 0 Ok
D2 ADC ... 0 Ok
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 12.1 V
D2 Power Ignition ... Voltage KL15 = 00.3 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 1 (+), 34 (-)