View Full Version : Mercedes DAS Star3 users.....
Andywill
15th January, 2010, 07:44 PM
I have a problem with my Merc Star3 not communicating with any Merc vehicle Gateway module, this prevents diagnosis of any module not directly connected to the CARB socket. All other functions/comms of my Star3 are working fine that do not rely on comms with the Gateway module. The Star3 has a self diagnosis programme in Star Utilities - Self Diagnosis - Caesar. With the Star3 connected and powered up, this programme will perform a internal integrity check, I've attached a copy of my Star3 report for reference of what one looks like.
Would someone with a Star3 execute the same and upload the report for comparisons.
Thank you.
DIAGNOSE64
15th January, 2010, 07:48 PM
I have a problem with my Merc Star3 not communicating with any Merc vehicle Gateway module, this prevents diagnosis of any module not directly connected to the CARB socket. All other functions/comms of my Star3 are working fine that do not rely on comms with the Gateway module. The Star3 has a self diagnosis programme in Star Utilities - Self Diagnosis - Caesar. With the Star3 connected and powered up, this programme will perform a internal integrity check, I've attached a copy of my Star3 report for reference of what one looks like.
Would someone with a Star3 execute the same and upload the report for comparisons.
Thank you.
My org head has the same result only baud rate is 115200.
Andywill
15th January, 2010, 07:52 PM
yours has the same CAN error logged....??? Mine is a clone and has worked fine until recently. Cable continuity has been eliminated.
would you mind posting/sending a copy of your report?
DIAGNOSE64
15th January, 2010, 07:54 PM
yours has the same CAN error logged....??? Mine is a clone and has worked fine until recently. Cable continuity has been eliminated.
would you mind posting/sending a copy of your report?
Sorry no error on Can
Andywill
15th January, 2010, 07:58 PM
Thanks for the confirmation. If you have a copy of your report that would be great.
JR2
16th January, 2010, 05:31 AM
Common issue with the Chinese MUX clones.
I shipped my MUX back 3 times and I just gave up on them.
Regards,
JR
Andywill
16th January, 2010, 09:11 AM
JR2 - thanks. Who did you buy from? Do you now have an original?
SadCriss
16th January, 2010, 03:23 PM
Hi,Can you make any comunication whit any of the cars?1. you should check COM setings need to be on COM2 and Bit per second 115200.2.If all these ok Please type down the error what you hawe exactly.Or P.M me for contact each other.B.R.
motorsport
16th January, 2010, 03:50 PM
hello with witch laptop you use mb star
Andywill
16th January, 2010, 04:17 PM
SADCRISS and MOTORSPORT - thanks for the reply. I am running IBM T30. I can comminicate with any module on any car providing i dont need to access the gateway controller eg. diagnosing airbag on SL500 W230 is run through the gateway and i can not access this. Any controller with a direct line to the CARB socket i can communicate no problem. Also when selecting a vehicle from the menu, the Star3 seems to da a quick check of the Gatway for correct vehcile ID - it fails this and asked to enter the vehcile details manually. Before this problem it would pick up the vehcile automatically.
How do i check the comm settings? All i have is the self CAESER report attached, does this necessary info?
Any further help would be great.
mercis
16th January, 2010, 05:18 PM
i have same problem,my china dealer change mux,
this is error in production,mux nr.027685
Andywill
16th January, 2010, 06:06 PM
Yes, my serial no. seems to be the same 27685.
Merci - did you get a new MUX, what serial no. was that?
mercis
17th January, 2010, 07:40 PM
new mux:029866
cesar selfdiagnoe.all ok
Andywill
17th January, 2010, 07:49 PM
Great thanks. So the serial number 27685 is not my individual number then, if you had the same serial number.
Where did you purchase your from please?
ant21
17th January, 2010, 11:38 PM
:giveup:mercedes
PremierD
18th January, 2010, 12:25 AM
:giveup:mercedes
??????????????????????:giveup:
andycjx
5th March, 2010, 02:57 PM
I have a problem with my Merc Star3 not communicating with any Merc vehicle Gateway module, this prevents diagnosis of any module not directly connected to the CARB socket. All other functions/comms of my Star3 are working fine that do not rely on comms with the Gateway module. The Star3 has a self diagnosis programme in Star Utilities - Self Diagnosis - Caesar. With the Star3 connected and powered up, this programme will perform a internal integrity check, I've attached a copy of my Star3 report for reference of what one looks like.
Would someone with a Star3 execute the same and upload the report for comparisons.
Thank you.
check that your multiplexer authorized level is 3, it is old dear, the new one is authorized level is 4. check it. please try YOU HAVE BEEN WARNED BEFORE MATE >>>>>> you will get level 4 report
cocutanu
5th March, 2010, 05:09 PM
@ andywill
My friend...you're problem has nothing to do with serial number or authorization level !
I saw many , actually many more with the authorization level 4 and serial number 029866 which has this problem plus k-lines errors instead of D3 with s/n 27685...
The problem is related to poor voltage stabilizers and cheap capacitors...it's a guy here who knows this problems very well...Bigovic. Try to PM him for some sollutions.
No offence for this guys from anyscancn but definately they will tell you that their stuff is better because they are selling this !
And by the way mine is D3 with s/n 27685 and working perfect for about 4 years but it was made in Europe.
Regards
mitedupev
7th March, 2010, 10:56 PM
Das error 9500 help from someone. THANKS
sosautomotive
9th March, 2010, 03:24 PM
@ andywill
My friend...you're problem has nothing to do with serial number or authorization level !
I saw many , actually many more with the authorization level 4 and serial number 029866 which has this problem plus k-lines errors instead of D3 with s/n 27685...
The problem is related to poor voltage stabilizers and cheap capacitors...it's a guy here who knows this problems very well...Bigovic. Try to PM him for some sollutions.
No offence for this guys from anyscancn but definately they will tell you that their stuff is better because they are selling this !
And by the way mine is D3 with s/n 27685 and working perfect for about 4 years but it was made in Europe.
Regards
you mean your mulpex is D3, please try with x entry, does it work on W212, 207,, looking forward to your reply. thanks mate
cabreador22
9th March, 2010, 05:05 PM
thank you very much!!!
gmatj
13th July, 2010, 10:42 PM
new mux:029866
cesar selfdiagnoe.all ok
I have a mux # 0299866 and I get the same bloody error - (I just received it and checking it !!)
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 (-)
So where do we go from here ????
Andywill
13th July, 2010, 11:10 PM
Special Test ... 3001 Error in CAN1 environment on Part D2 board
....yep. Had very similar on my old one, if you can, check OBD socket pins 6 and 14 with star connected and trying to communicate, if no can signal appears - its dud! But the self test seems to have confirmed it for you.
gmatj
13th July, 2010, 11:38 PM
Special Test ... 3001 Error in CAN1 environment on Part D2 board
....yep. Had very similar on my old one, if you can, check OBD socket pins 6 and 14 with star connected and trying to communicate, if no can signal appears - its dud! But the self test seems to have confirmed it for you.
Hi there
More to come
Trying to test again and I get :
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:43
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 103 No D2 Hardware connected
No CAESAR components / Errors during detection
The thing is I am using an RS-232 Express Card, and I suspect it is not working all that good.
Message :
D2 SERCTL1 ... 2003 DSR / DTR lines at UART1 not connected is probably trying to spit that out !!
What do you make od all this ??
(As far as I am concerned , I am going down to the garage to run a few tests again!! - and it is 02:00 in the night!!!)
gmatj
13th July, 2010, 11:42 PM
I forgot to mention I am running DAS 2010.01 on VMware.
Also use COM port 2 on both Host and VMware with Max speed 115200.
gmatj
16th July, 2010, 02:15 PM
I forgot to mention I am running DAS 2010.01 on VMware.
Also use COM port 2 on both Host and VMware with Max speed 115200.
Still I got no solution !!
If anybody has had similar experience please contribute to the thread.
diagnoza_auto2000
27th August, 2010, 05:05 AM
Firts open your mux an resolder with hotair can controlers both of them and Saf procesor.
Maiby some line not have a good contact.
If will not work i will give you another solution,pm pls
victor2k
27th August, 2010, 09:00 AM
Hi all,
I have the following error on my star das:
1.1-1.501.9302
What do you you think about this error?
I can't see D2 Power battery and D2 Power ignition.
On PCB I have 12v but not in diagnose.
I replaced a faulty 7808 IC inside the multiplexer but nothing was changed.ADC converter was replaced also with the new one-without any result.
Something not work on the supply side:
D2 ADC ... 2500 Error ADC
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 00.6 V
D2 Power Ignition ... Voltage KL15 = 00.2 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 0 (+), 0 (-), 35 Error(s)
Thank you.
gmatj
27th August, 2010, 10:23 AM
Still I got no solution !!
If anybody has had similar experience please contribute to the thread.
Just reporting back --(I should have done earlier...)
Changed RS-232 card and system is Ok now.
The one I use now has Oxford Chipset and of course coresponding drivers.
kenwood727
26th December, 2011, 03:02 PM
hello all
i have this problem my cesar
3001 Error in CAN1 environment on Part D2 board
can fixed
1-first check obd socket volt
must 12v
and change obd cable
%100 work
good work
kenwood
tommjd
18th October, 2016, 10:18 AM
hi mate, got the same error on mine? did u manage to resolve your issue and how?
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.