Mb Star DAS Fault

[icedillon]

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]

Run cesar selfdiagnostic in star utility.
Write the result.

[minvita04]

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]

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]

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]

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]

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]

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 (-)

[mercis]

wich DAS have you install?

[automite]

4/09 and 8/06 both give same error message.

[denis500]

yuo must change COM3 to COM2

[automite]

I have an original MUX and it's working fine with the same PC so the problem must be in the Chinese crappy MUX.

[denis500]

In my china multiplexer was burned RESISTOR
sorry for my english

[weryo]

The mux is out!

Replace flash memory!

[automite]

I will take it apart, take pictures. Would you be kind to tell me what flash I need to replace?

[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.:stupid:

[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

http://us.mg4.mail.yahoo.com/ya/download?mid=1%5f349781%5fABWniGIAAOt4TECgwwu0u1bQ 41I&pid=2.2&fid=Sent&inline=1


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

http://us.mg4.mail.yahoo.com/ya/download?mid=1%5f349781%5fABWniGIAAOt4TECgwwu0u1bQ 41I&pid=2.3&fid=Sent&inline=1



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

-----------------------------------------http://us.mg4.mail.yahoo.com/ya/download?mid=1%5f349781%5fABWniGIAAOt4TECgwwu0u1bQ 41I&pid=2.4&fid=Sent&inline=1-----------------------------------------
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?

[gmatj]

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

It seems on my mux the problem was the serial port(s) - Then I got a real one with oxford chipset and drivers and it seems everything is Ok now. Also i you are running DAS on VMware can give you sometimes erratic results on Caesar testing
Rgds
G.

[netxxl]

Hi,

I have tried several Notebooks, some with real COM Ports, some with USB converter, some with PCMCIA Adapter, all the same result. I even tried it with VMWare and without, just to be sure. And it used to work on that same Notebook computers for almost three years. So I'm afraid it has to be hardware.

Regards,
Netxxl

[gmatj]

Hi,

I have tried several Notebooks, some with real COM Ports, some with USB converter, some with PCMCIA Adapter, all the same result. I even tried it with VMWare and without, just to be sure. And it used to work on that same Notebook computers for almost three years. So I'm afraid it has to be hardware.

Regards,
Netxxl

I am afraid the most possible cause should be the hardware.
It is no use to try to repair - I think - You could get a set of PCBs for a couple of hundred euros...

[strda50es]

Hi,

I have tried several Notebooks, some with real COM Ports, some with USB converter, some with PCMCIA Adapter, all the same result. I even tried it with VMWare and without, just to be sure. And it used to work on that same Notebook computers for almost three years. So I'm afraid it has to be hardware.

Regards,
Netxxl
From what you describe it must be a hardware problem mate.
For this purpose the member "bigovic" posted a whole thread wich is really usefull.
Try his recomendations and i hope you will be OK.
Best off luck mate.

[gmatj]

From what you describe it must be a hardware problem mate.
For this purpose the member "bigovic" posted a whole thread wich is really usefull.
Try his recomendations and i hope you will be OK.
Best off luck mate.

Hi m8
Hope you are fine .
Have read bigovic 's suggestions but be warned all that is described ain't so easy without the right tools. It ain't easy at all.
All the best to you
G.

[netxxl]

Hi,

thanks for the answers, I'm afraid it must be hardware problem and I cannot repair it. I'm no good with the soldering iron, too big hands or something :)
Where could I get the new PCB ? Heard that they make pretty good ones in Europe, too, like in Bulgaria or something, but how to buy?

Net.

[gmatj]

Hi,

thanks for the answers, I'm afraid it must be hardware problem and I cannot repair it. I'm no good with the soldering iron, too big hands or something :)
Where could I get the new PCB ? Heard that they make pretty good ones in Europe, too, like in Bulgaria or something, but how to buy?

Net.

Hi m8
You can find a good supplier and ask him to buy only the internals of the MUX (i.e. the 2 PCBs). Most probably they will get them to you.

Just be carefull that is a credible supplier

Also be carefull as the sell some in Europe at a few times the price of the Chinese , but even those are made in China and imported to Europe !!!.

Bare in mind that even ACTIA manufactures in China and assembles in France.

So my opinion is find a credible supplier.

Regards
G.

[gmatj]

@netxii
Just FYI
Message "Some Sectors of Diagnosis might be corrupted, please contact MB." can come at any time NOT necessarily due to faulty hardware.
It can even come on when diagnosing CGW on DAS SIM !!! (obviously with no Mux connected)

Can you diagnose a car, any car at all ???

[netxxl]

Hi gmatj,

I cannot diagnose any car or van or truck. Tried it all.
Strange happenning is that this is since I tried to flash a CGW with a new flashware and now you are talking about CGW. Maybe somehow the mux is stuck in upgrade mode? But that would not explain the ADC 2500 Error, would it?

Greetz,
Net

[gmatj]

Hi gmatj,

I cannot diagnose any car or van or truck. Tried it all.
Strange happenning is that this is since I tried to flash a CGW with a new flashware and now you are talking about CGW. Maybe somehow the mux is stuck in upgrade mode? But that would not explain the ADC 2500 Error, would it?

Greetz,
Net

When you were trying to flash CGW what version of DAS were you using ??

[doslamer]

netxxl ->Hi,

thanks for the answers, I'm afraid it must be hardware problem and I cannot repair it. I'm no good with the soldering iron, too big hands or something
Where could I get the new PCB ? Heard that they make pretty good ones in Europe, too, like in Bulgaria or something, but how to buy?

Net.<-

For everybody came a first time to take over the thing's in his hand's :) You must open the box of DAS and see what is wrong. But more than 80% of problem's are hardware connection of the cable's. Open it and check where is desoldered. You have to look very good because if you have 2 or more cable's desoldered'(crashed) you must to know where to solder , that is the big problem. And more important if you think that this job is not for you then you must change your job. Be brave and unpack your box, look around and after that everything come to place you will see :)

[netxxl]

The DAS Version I used then was 09/2009, I think.

Yes, I already looked inside the cables and measured them through, they seem ok.
I already took my box apart and resoldered all bad looking joints. I could not see any obvious burn marks or anything on the pcb. What I meant to say is that I'm not a specialist especially with the small smd chips. I can of course do small soldering jobs, but wouldn't know when a IC or Diode is burned if it wasn't obviously burnmarked.

Greetz,
Net

[Bredpitt]

I have the same problem as the starter of this thread.

BUT, i just have the problem with the 16 pin ODB contact.
I can connect to older W210 cars with the cable for this car but it would not connect to W211 cars with the ODB cable.

Could it be a cable fault for my case ?!

Please help.

I bought a multiplexer with T30 laptop from China.


Stian

[Bredpitt]

Also it cannot connect to GL320 (X164). same problem.
I have 22 x W211 cars and i have try many of them. No one works..
I have 3 x W210 and this model works fine.

[strda50es]

Also it cannot connect to GL320 (X164). same problem.
I have 22 x W211 cars and i have try many of them. No one works..
I have 3 x W210 and this model works fine.
Hi mate.
Please tell me where did you get this multiplexer from?
I mean from wich seller?
Please give us your "lights".

[Bredpitt]

I bought it from Race Automobile Technology.

My lights ?

[strda50es]

I bought it from Race Automobile Technology.

My lights ?
Yes friend "your lights" to enlight the problem i mean.
And did you solve the problem?

[Bredpitt]

I did not solve it yet..
They agreed to send me another cable yesterday.
They are in China, and i am in Norway so it will take some time.

[Bredpitt]

Also very strange, i try to run the c?sar self diagnosis test and it shows up folowing error.

ERROR: device '0 (-1) isn't in state available
Device: Part D
Toolkit-Resultcode: -1

The MUX are connected to the car and the LED lights up.

But it works fine with connected to W210 with old cable and not with new 16 pin ODB cable.

[papalos_]

Also very strange, i try to run the c?sar self diagnosis test and it shows up folowing error.

ERROR: device '0 (-1) isn't in state available
Device: Part D
Toolkit-Resultcode: -1

The MUX are connected to the car and the LED lights up.

But it works fine with connected to W210 with old cable and not with new 16 pin ODB cable.

I also have the same problem like you with caesar selfdiagnosis test on SDS 11.2010. Did you solve it? Any solution for that?

Anyway, I can diagnosis all cars normally.

I have one more problem with DAS. After programming an module, at the end of the programming i get an error message about DAS32R2.exe and CAL_REAL.dll error, and DAS closes abnormally. How can i fix that?

Regards

[PeterOBD]

hello,
i have burned R12 /near ellyt/ on multiplexer board in last C3 clone /from carsung/ after conect to 24v.
can help somebody with resistor value please?
wbr
peter