Configuring DAS/Xentry to Read Converted Mercedes S400 Hybrid with VIN Mismatch
Thread Starter
Newbie
Joined: Jan 2021
Posts: 7
Likes: 0
S class
Configuring DAS/Xentry to Read Converted Mercedes S400 Hybrid with VIN Mismatch
Hello fellow enthusiasts and experts,
I am facing a challenging situation with my 2010 Mercedes S400 Hybrid and am in need of your expertise. This vehicle was converted to operate on fuel only, and during the conversion, the VIN in the ECU was changed to that of an S350. This has led to a significant diagnostic hurdle that I'm hoping to overcome with your help.
The Core Issue:
My main problem is with the Adaptive Brake (ABR) system diagnostics. When using the DAS/Xentry tool, it defaults to the VIN from the ECU (now S350), which causes it to misidentify and misdiagnose the ABR system issues.
Specifically, the system is displaying 'unknown fault' errors because it's not recognizing the car as a hybrid. I believe that if DAS/Xentry reads the car using the original Hybrid VIN, it would show the correct fault codes, allowing for accurate diagnosis.
Attempts Made:
I've tried manually entering the original Hybrid VIN in DAS/Xentry, but the software automatically reverts to the VIN from the ECU.
I'm considering the possibility of a configuration file within the DAS/Xentry software that might be editable to address this issue, but this is where I need guidance.
Seeking Your Assistance:
Has anyone dealt with a similar VIN mismatch issue in DAS/Xentry, especially regarding hybrid vehicles?
Are there known methods or workarounds to make DAS/Xentry read the vehicle as a hybrid, despite the ECU VIN being different?
Insight into the software's structure for this specific purpose would be invaluable.
I am facing a challenging situation with my 2010 Mercedes S400 Hybrid and am in need of your expertise. This vehicle was converted to operate on fuel only, and during the conversion, the VIN in the ECU was changed to that of an S350. This has led to a significant diagnostic hurdle that I'm hoping to overcome with your help.
The Core Issue:
My main problem is with the Adaptive Brake (ABR) system diagnostics. When using the DAS/Xentry tool, it defaults to the VIN from the ECU (now S350), which causes it to misidentify and misdiagnose the ABR system issues.
Specifically, the system is displaying 'unknown fault' errors because it's not recognizing the car as a hybrid. I believe that if DAS/Xentry reads the car using the original Hybrid VIN, it would show the correct fault codes, allowing for accurate diagnosis.
Attempts Made:
I've tried manually entering the original Hybrid VIN in DAS/Xentry, but the software automatically reverts to the VIN from the ECU.
I'm considering the possibility of a configuration file within the DAS/Xentry software that might be editable to address this issue, but this is where I need guidance.
Seeking Your Assistance:
Has anyone dealt with a similar VIN mismatch issue in DAS/Xentry, especially regarding hybrid vehicles?
Are there known methods or workarounds to make DAS/Xentry read the vehicle as a hybrid, despite the ECU VIN being different?
Insight into the software's structure for this specific purpose would be invaluable.
MBWorld Fanatic!
Joined: Aug 2014
Posts: 5,319
Likes: 1,675
S500
I thought diagnostics reads the CGW (gateway) for vehicle ID - and that only the engine immobiliser and associated parts (like the cluster and gearbox) are going to 'have to match' the engine ECU
that said, sounds like you already have the CGW of the other car hence how its finding that chassis number - but then the airbag control modules need to know whats going on for the ABR to work
the complexity of correctly converting a hybrid - can only ever be a real mix and match of hardware and software across the entire car - it will need lots of experience and knowledge of how these cars work, access to software you'll not know what it is or how to get it (aka everything in Merc software is muddled in to each other in weird and wonderful ways Merc never really understood) - and its highly likely you will always retain some "fun"
so many looms and other modules would be required to totally convert it to a normal conventional petrol car - and then - unless every single part of wiring and 50 plus control modules came from the very same perfect car - likely you'll never manage the secret online only SCN coding to get many features to fully behave as a std car should
that said, sounds like you already have the CGW of the other car hence how its finding that chassis number - but then the airbag control modules need to know whats going on for the ABR to work
the complexity of correctly converting a hybrid - can only ever be a real mix and match of hardware and software across the entire car - it will need lots of experience and knowledge of how these cars work, access to software you'll not know what it is or how to get it (aka everything in Merc software is muddled in to each other in weird and wonderful ways Merc never really understood) - and its highly likely you will always retain some "fun"
so many looms and other modules would be required to totally convert it to a normal conventional petrol car - and then - unless every single part of wiring and 50 plus control modules came from the very same perfect car - likely you'll never manage the secret online only SCN coding to get many features to fully behave as a std car should
