Mb Star DAS Fault

[tatisoft]

D2 FLASH ... 1703 Error occured while erasing FLASH
D2 EEPROM ... 1802 Error (access to EEPROM)

[BramageOMC]

I ran CESEAR test with MUX connected to car (Light On) and no MUX found. PC and VMWARE serial port both Com 2. I can communiate with com port through terminal via VMWARE.. Only thing I can think is that XENTRY is looking for differnt com port, or bad mux

[AdnanB]

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.

CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 16.04.2010
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 103 No Hardware connected
No CAESAR components/Errors during detection

help please.

[Ameerco2010]

AdnanB . do you use it with cars or trucks ?

[AdnanB]

Fault (1.1)-1.501.9302 with truck

[Ameerco2010]

Fault (1.1)-1.501.9302 with truck

Did you try to change language or speed and your MB star not original.I am asking you frist after I will tell you hardware or software .I bought one from china does not work I find fault in small box in that cable to laptop IBM T30.

[icedillon]

to connect a multiplexer for caesar test. is a 13.8v adapter ok??? basically alternator voltage

[icedillon]

to connect a multiplexer for caesar test. is a 13.8v adapter ok??? basically mimics alternator voltage when a car is running

[chickenboy]

I have the same error (and only error) on Compact 4:

"D2 FLASH ... 1703 Error occured while erasing FLASH"

I don't believe there is anything wrong with DAS or COM Ports because I'm able to use Compact 3 Mux successfully under the same configuration. Does this mean there is a faulty IC??? I believe my Compact 4 mux is made in china from its cheap casing. Has anyone opened the unit and determined what are the possible components fried or needs to be replaced?

I have opened it, noticed it has a Microcontroller from Lattice Semiconductors, some latches/RAM manufactured by Infinity (same components on PC3200 DDR RAM) and alot of red colored components that I haven't yet researched and determined.

[Bigovic]

Fault (1.1)-1.501.9302 with truck

OPen your Multiplexer and replace

1. All Diodes (on relayboard)
2. All Power IC (7805 or 7808)
3. TIP32 or TIP42
4. Change the Capacitors
5. Remove the BCP56
6. Heat sink cooler on this IC (2) dont contact the TIP with
Case or other Power IC !!!!

than hope you have Luck and Multiplexer will working!

Hope Help you :-)

[Bigovic]

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.

CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 16.04.2010
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 103 No Hardware connected
No CAESAR components/Errors during detection

help please.

See my Last Posting hier, and make this steps in 90% will the Multiplexer working. Your Multiplexer is Destroyed but you can Repair this self!

add in my Instruction last Step: Change St232 or MAX232 and MAX485 IC (on Main Board)

THat you know, your Multiplexer is Damaged with the High Voltage from Truck the Mercedes Truck if the Engine is On don?t have only 24 Volt have 28 - 29 Volt Power, the Problem is the Power Regulators in CHINA CLONES don?t have Heat Sink cooler on the IC!!!!.
IF you Replace all the components maybe you can make your Multiplexer that work.

Good Luck!

[gmatj]

Hi Bigovic
Sorry to hijack the thread but I feel I may have a similar problem



a)That is what you get when no multiplexer is connected which is normal.
See picture P1




b) That is what you get when the multiplexer is connected and to OBDII socket
See picture P2





c) This what you get after running the SelfDiagnosis !!!!
See picture P3 That

----------------------------------------------------------------------------------
The first time the CAESAR test was run I got this
Selfdiagnostic
==============
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 13.07.2010 22:22
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-Benz AG
User Authentification 1
Classification 0
Serial Number 029866
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-Benz AG
User Authentification 1
Classification 0
Serial Number 029866
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 ... 2003 DSR / DTR lines at UART1 not connected
D2 UART1/2 ... 0 Ok
D2 ADC ... 0 Ok
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 2 (+), 33 (-)
I have put in red what I believe was suspect. I have been unable to get a full Caesar report.again , no matter how many times we have tried , the report we get is as in photo i.e. D2Access ... 103 No D2 Hardware connected - No CAESAR components / Errors during detection (like in picture P3)

Some tmore things to be noted are :
a) the green (power) light of the multiplexer turns on when you connect to OBD socket
b) The Mux is connected to the laptop through an, Express Serial RS-232 card , fully compatible to 16550 UART chip.
d) The version of DAS running is v.2010.01
e) All tests carried out on a W211/E200K /MY2007

Hope all the above information is enough to let you make a good conclusion of what is happening.

[victor2k]

hi,
Any one can tell me what diodes are:
VD7,VD8 ,VD151 and VD10?
Thank you.

[netxxl]

Hi,

I have China Clone Mux which worked well for almost 3 years, now I get
2500 Error ADC 2500.
But only first time when I run Selftest. Second try everything shows OK. Only first test after powerup of mux. Also I get from DAS error something like:
Some Sectors of Diagnosis might be corrupted, please contact MB.
This error I get always, even when Selftest runs OK.
I tried several Installations from 2007 to 2010, even with old HDD Images which I still had and which did work some years ago with this multiplexer.
So what could it be.
Already tried resoldering, but no change.
Can anybody repair mux, I am not a fine electrician myself...

Regards,
Netxxl

[strda50es]

Hi,

I have China Clone Mux which worked well for almost 3 years, now I get
2500 Error ADC 2500.
But only first time when I run Selftest. Second try everything shows OK. Only first test after powerup of mux. Also I get from DAS error something like:
Some Sectors of Diagnosis might be corrupted, please contact MB.
This error I get always, even when Selftest runs OK.
I tried several Installations from 2007 to 2010, even with old HDD Images which I still had and which did work some years ago with this multiplexer.
So what could it be.
Already tried resoldering, but no change.
Can anybody repair mux, I am not a fine electrician myself...

Regards,
Netxxl

Hi friend.
Have you tried to another computer?