|
PART_D2 unknown origin became a brick? - Printable Version +- MHH AUTO (https://mhhauto.com) +-- Forum: MHH AUTO FORUMS. (https://mhhauto.com/Forum-MHH-AUTO-FORUMS) +--- Forum: General Automotive Help & Discussions. (https://mhhauto.com/Forum-General-Automotive-Help-Discussions) +---- Forum: Daimler Group Mercedes-Benz, Smart Discussions. (https://mhhauto.com/Forum-Daimler-Group-Mercedes-Benz-Smart-Discussions) +---- Thread: PART_D2 unknown origin became a brick? (/Thread-PART-D2-unknown-origin-became-a-brick) |
PART_D2 unknown origin became a brick? - temo4ka - 12-03-2016 Hi all members ![]() One my friend brought me a multiplexer (its not classic C3 MUX, its analog without any markings), so I figured out why he is cann't connected to the car. He also brought a laptop with installed DAS 01/2008 . ![]() First of all I made Caesar selftest -> ![]() I was immediately alarmed by the error 1802. I re-solder all pins of microcontroller SAF-C167 and SecureFlash x76F041A. Ineffectually ![]() Considering PCB further I found two bloated capacitors 12V circuit. I replace them. (Then I looked at the 1st results of the test, with bloated capacitors, power supply voltage is 16-17V )![]() When you try to connect to the car through the DAS see error -> ![]() In 12/2014 DAS same error code, but without CAL 503 -> ![]() But most of all I was confused by the fact that I have successfully connected to the car through HHTWIN -> ![]() What is it? HW problem (burned track, no power supply to EEPROM, dead SAF-C167 or x76F041A), blocked MUX for serial number or SW problem? ![]() I need your help! I would appreciate any advice and tips. Thx ![]() Mammoth
RE: PART_D2 unknown origin became a brick? - Anturage - 12-03-2016 Trash it and forget RE: PART_D2 unknown origin became a brick? - fabek - 12-03-2016 Where are you from? I can repair your C3 mux with warranty. |