Star C3 Part D & New MB W222, W217, W205 etc (Discuss)

  • -
c3-1

Star C3 Part D & New MB W222, W217, W205 etc (Discuss)

A good thread with posts: Part-D MUX (a.k.a Star C3) and W222/W205…

Hey dears

perhaps some of you have some insights on this: While we all know that the new model series like W222, W217, W205 etc have on board ethernet routed to the OBD socket, and the Benz diagnostic tool SDConnect is Ethernet/DOIP capable, the diagnosis still seem to be fully possible via D-CAN (pins 6,14 on the OBD socket). For instance, third party tools like BOSCH KTS and the BOSCH CDR (that we use for pulling crash data) do not communicate over Ethernet, they connect to several modules (well some 70% of what is in the car due to 3rd party limitations) via CAN, and they do it allright.

So what is the real reason for Part-D mux not communicating with these model series, could this be just a planned “programmed obsolescence” so the old units get retired faster than they really should?

Perhaps it would be possible to edit vehicle definitions so the old communication platform would still serve for these cars?

I have several Part D muxes, some original, some clones, and some of them work really, really reliably. Learning that purchase of a cloned MB Star C4 that would be as reliable as this is next to impossible, i am thinking about possible workarounds. Since it does not look like actual communication architecture limitation. Anyone?

 RE: Part-D MUX (a.k.a Benz star c3) and W222/W205…
There is nothing planned it is simply technology development. In time when was used PartD there was no ethernet/DoIP in the cars so was not needed have this technology in diagnostic device. Then came new technology and was build new communication hardware. For new technology is needed new technology that′s all. It is the same like car from year 2000 and car from 2015.

RE: Part-D MUX (a.k.a Star C3) and W222/W205…
The only thing is, that Part D is not supported in newer Xentry and Vediamo or dts monaco software.
This part would work also with the cars for CAN Bus only.

RE: Part-D MUX (a.k.a Star C3) and W222/W205…
(10-05-2017 12:45 AM)laco210 Wrote:
There is nothing planned it is simply technology development. In time when was used PartD there was no ethernet/DoIP in the cars so was not needed have this technology in diagnostic device. Then came new technology and was build new communication hardware. For new technology is needed new technology that′s all. It is the same like car from year 2000 and car from 2015.

Well that would be true if the newer vehicles would run ONLY in the DoIP mode/lacking CanBUS. But actually they DO have ordinary can BUS and even the documentation (WIS) states, that the diagnostics still take place using the D-CAN!

But guess what. We never know until we test ourselves.

I did a little experiment. I have installed a VOLVO DICE (capable of being a J2534 pass thru) drivers and configured that in Xentry (using the provided ptd_select program). Result – fully running diagnostics on a CAN (YES IT IS A PASS THRU CAN because DICE can’t do DoIP) on a 2016 S-Class.

I will test more interfaces and report. If that turns to be sufficiently reliable, i will stick to it and forget about other interfaces.

RE: Part-D MUX (a.k.a Star C3) and W222/W205…
Most of our SDconnect tools are not DoIP capable but can still do W222 and similar MB models. That is for the diagnostics tasks. They cannot do Telematics updates or similar that run through the IP port.

The issue with C3/PartD and these new cars is not CAN but support for UDS protocol.

RE: Part-D MUX (a.k.a Star C3) and W222/W205…
(10-05-2017 08:42 PM)DBmhh Wrote:
Most of our SDconnect tools are not DoIP capable but can still do W222 and similar MB models. That is for the diagnostics tasks. They cannot do Telematics updates or similar that run through the IP port.
The issue with C3/PartD and these new cars is not CAN but support for UDS protocol.

That would make sense and perfectly explains why i am getting full diagnostics using Volvo interface in J2534 mode that has CAN but also supports UDS (in fact, isn’t it rather a feature of the driver than the box itself?)

Anyway, quite happy with what i;ve found and if anyone’s interested i will give info on what tools, versions, setup etc was used to make this work.

RE: Part-D MUX (a.k.a Star C3) and W222/W205…
(10-05-2017 08:42 PM)DBmhh Wrote:
The issue with C3/PartD and these new cars is not CAN but support for UDS protocol.

Bud, D3 supports UDS protocol. For example Sprinter 3 up to 2014 model year. Delphi CRD2 is UDS.
(10-04-2017 11:02 PM)mikepl Wrote:
Hey dears
So what is the real reason for Part-D mux not communicating with these model series, could this be just a planned “programmed obsolescence” so the old units get retired faster than they really should?

The only reason is that MB discontinued its support.

RE: Part-D MUX (a.k.a Star C3) and W222/W205…
(10-08-2017 08:59 AM)efka Wrote:
Bud, D3 supports UDS protocol. For example Sprinter 3 up to 2014 model year. Delphi CRD2 is UDS.

“Supports UDS” or “only UDS”? Why does C3 not talk to a 2014 Sprinter CDI control unit when it does talk with the rest of the car?

How did you check C3 supporting UDS and really talking to the control unit with the UDS protocol? The control unit most likely accepts both when the 2014 only accepts UDS.

RE: Part-D MUX (a.k.a Star C3) and W222/W205…
The only difference PartD has no DoIP.
All other ECU protocols are supported.

c3-1


  • -
18-1

MB STAR C3 Xentry Error (1.3)-3.515.2019 (Solved)

Troubled with 18-2 Xentry Error (1.3)-3.515.2019 for a few days. Tried lots of ways from Obd2tool.com but didn’t work. Then finally talked to the people work for mbstashop via Facebook. Work OK!! Send my case to them and write this review for mbstarshop to express my gratitude.

Tools used:
Star C3 multiplexer with Xentry
Dell D630 Laptop
Mercedes-Benz C220 W203
Xentry Error (1.3)-3.515.2019 background information:
connect the vehicle with multiplexer and start my Dell D630. When the multiplexer is not connected to the computer, This task list is displayed

18-1

Then connect my computer to the MB Star Diagnosis c3, the task list will change now.

18-2

start the program Xentry.

18-3

choose the vehicle brand Merzedes and vehicle model: C220 W203

18-4

18-5

start the car’s ignition and then open the Diagnostic Program
18-5
18-7

the vehicle is not even recognized by the XENTRY

18-8

manually select the vehicle

18-9
choose a short test from the vehicle
18-10

vehicle data are determined and lessen

18-11

Not all ECUs can be found there. The controllers found but can not be processed. Also when I select the ECU itself without a short test, I get this error (1.3)-3.515.2019

18-12

In short, Once the vehicle is plugged in and I try to read out the fault memory, I get this error message number (1.3) -3.515.2019. I cannot find all ECUs.

Easy but useful solutions:
just modify the date and time of your computer
make sure that is the current date and time
Done!!
(Many thanks to mbstarshop technicians)

No related posts.