W211 E500 Xentry/DAS C4 Issues

[Maximk]

Hi All,

I am having issues with Xentry/DAS. I have a C4Plus DOIP Multiplexer. 2015 Xentry. Dell Laptop. The setup worked fine with my 2015 ML250 CDI, but runs into issues with my older 2005 E500. I'm guessing some issue with DAS and the multiplexer. My current thought is that the 2005 vehicle isn't compatible with the C4 OBD2 DOIP cable, and that maybe it will work with a standard OBD to C4 cable. Does that make sense?

Error message I get is as below:

Fault (1.18)-890
Communication Fault
Incorrect vehicle connection cable used between diagnosis multiplexer and vehicle diagnostics socket
Diagnostics data sectors missing or incomplete.

Thanks,

Max

 

[gerryvz]

Per forum rules, moving this thread to OFF-TOPIC DISCUSSIONS because it has nothing to do with the W124 chassis, and relates to the W211.

@Maximk, please be cognizant that the sole focus of this forum is the W124 E-class sedans with V-8 engines, from 1991-1995.

 

[Maximk]

Oh jeeze, sorry about that guys. I saw E500 and thought I was in the right place but yup I missed that crucial detail on the chassis. No worries will get this sorted out. Safe driving everyone!!

 

[gsxr]

@Maximk - it does sound like a cable issue, although I'm surprised it won't communicate with a 2005 W211.

Where did you buy your SDS kit from?

 

[Maximk]

Number 1 Brand China. C4 Multiplexer purchased on Fleabay: Pardon Our Interruption...

Laptop is a Dell Latitude D620/D630 Laptop Windows XP pro running xentry 15.4.3.4.2 2015

 

[R129 UK]

Some possible causes here:

https://mhhauto.com/Thread-Error-1-18-9-890-with-SDConnect?page=2

 

[Maximk]

Thanks, yes I've read that thread a few times and if a different cable doesn't work then I am going to try and track down a different DAS BIN folder. Speaking of if anyone has a working DAS bin folder they can share with me that would be super helpful. Would be programme/DAS/Bin.

 

[R129 UK]

Thanks, yes I've read that thread a few times and if a different cable doesn't work then I am going to try and track down a different DAS BIN folder. Speaking of if anyone has a working DAS bin folder they can share with me that would be super helpful. Would be programme/DAS/Bin.

I just tried to attach my bin directory to this post as a .zip but it is too large...



My DAS is 07/2014

 

[Maximk]

Well new cable didn’t work, not surprised. R129 can you try emailing it to me? Shoot me a DM?

 

[R129 UK]

Post an email address in this thread and I will send you my file.

 

[Maximk]

Maximck at g mail

 

[Maximk]

Btw super appreciate it, hopefully small enough to email. Fingers crossed that this works.

 

[R129 UK]

Sent, I think it got through as I haven't had a delivery failure yet - hopefully it gets you up and running.

 

[Maximk]

Didn’t come through, shoot me an email without the attachment and I’ll send you a link where you can upload. Hate to eat up your free time with this. Can pay you a few bucks for your trouble. Maximck at gmail dot com

 

[R129 UK]

Didn’t come through, shoot me an email without the attachment and I’ll send you a link where you can upload. Hate to eat up your free time with this. Can pay you a few bucks for your trouble. Maximck at gmail dot com

Done just now.

I assume you checked your Spam etc. the file is 24MB.

 

[R129 UK]

To (partially) close the loop on this one, attaching the BIN file here didn't work, neither did an email attachment or a Google Drive upload (suspected as malicious) but eventually the file was transferred via WhatsApp.

Outcome - it didn't resolve the issue.

 

[Maximk]

Yes, unfortunately niether of those resolved the problem. Interestingly though with the different bin file the wrong cable fault went away and I’m just left with the bad data sector fault. Not sure what that points too. Maybe something in my software install or configuration, or could also be the vehicle ecu itself. I’m feeling like I got some bad luck on my setup.

Positive note, wife’s W166 had a check engine light come on today and scanned using xentry with no issues.

Big thanks to R129 for all the help transferring the file over.

If anyone else has any ideas let me know.

 

[Maximk]

Another clue perhaps, I just ran xentry simulation, and got the same error without anything plugged into laptop. That shouldn’t happen right?

 

[gerryvz]

BIN (binary) files are NOT an allowed type of attachment here. You could ZIP it and try it that way, as ZIP is an allowed file type.

BIN files contain code, which could be considere malicious and thus detrimental to the operation of the forum (or members downloading said code).

 

[R129 UK]

BIN (binary) files are NOT an allowed type of attachment here. You could ZIP it and try it that way, as ZIP is an allowed file type.

BIN files contain code, which could be considere malicious and thus detrimental to the operation of the forum (or members downloading said code).

It was zipped but at 24MB it was too large to be uploaded.

 

[gerryvz]

Yes, that is much too large even for the generous file sizes of this forum, which are somewhere around 8-12 MB.