thank you man
thank you man
Hello, colleagues.
SDConnect C4 works fine with Xentry-DAS 03.2015 with SN:333333
After XDOS 12.2015 was installed, I try to update MUX using SDTOOLKIT with next result:
00_ClearCeFlashDisc.zip - OK
01 Bootimage 2_3.zip - OK
02_CSD_2_10.zip - Sdconnect is not connected to the diagnosis computer. (512)
02_CSD_2_11.zip - Sdconnect is not connected to the diagnosis computer. (512)
03_PmPic29_Cpld 13.zip - OK
11_CaesarEngine_090.zip - DCDI_eErrorCode=201 (201)
21_WlanRoamingEnable.zip - OK
22_WlanRoamingDisable.zip - OK
31_CyclicLogger_ON.zip - OK
32_CyclicLogger_OFF.zip - OK
99_SD_Fuso_CaesarEngine090.zip - DCDI_eErrorCode=201 (201)
Some items finish update with errors. The device still working OK.
Please suggest what could be wrong? How to fix this problem?
Update only 00_ClearCeFlashDisc.zip - OK
And Start Xentry Model S220 065
Update start Automatic please wait until the end
finished
Last edited by maxpolska; 18th March, 2016 at 01:51 AM.
Hi,
I get this unit from my friend. Someone tried to repair it but without success. I read on forum make test and replace max232 and t42. But before everything I am asking can you check photos and give comments. Also, I do not have software for it and link for corresponding SW will be great.
I can't attach photos here (too large), so here is the link on gdrive:
https://drive.google.com/drive/folde...CD?usp=sharing
Hallo everyone.
Should anyone have a problem with their multiplexer, do not throw away, I can fix for and revive it. Just pm me
hi...i have a problem my c3 with w203 coupe...cant connect car gateway error on das....half communicate car...cant connect ecu and ezs...but see serial esp control but cant connect....what is the problem my multiplexer this my selftest logs....
CAESAR STOS+ Rev.:2.12 from Jun 16 2005
generated protocol file from 05.09.2015 16:42
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 027685
Authorization Level 3
Part D
Hardware Authentification 011200
Hardware Date 040301
Special EEPROM check :
D2 Special EEPROM check:
Inst. date registered ... 0 Ok
D2 Special CAN Test :
Special Test ... 0 Ok
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler-Benz AG
User Authentification 1
Classification 0
Serial Number 027685
Authorization Level 3
Part D
Hardware Authentification 011200
Hardware Date 040301
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 ... 0 Ok
D2 UART1/2 ... 0 Ok
D2 ADC ... 0 Ok
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 14.7 V
D2 Power Ignition ... Voltage KL15 = 14.0 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 5 (+), 30 (-)
wich parts need check it? please help me 16pinodb cable are ok checked...
Last edited by tonyaki2; 10th December, 2018 at 08:45 PM.
Hello everybody,
I recently purchased a c3 off ebay, (the one made by actia - original one i believe). it was without the cables which i purchased separately. I read up on threads downloaded the 9.2014 software and installed it and ran it on a dell e5500, (after installing win xp) which has a native serial port configuring the ports as suggested. (com2, 115000 bitrate). Connected the mux with the cables i purchased, one obd ii and one rs232 with the box in the middle (it isnt empty - i checked) of the cable. Problem is as soon as i go into das the mux disconnects. I applied all the patches and the blacklist fixes (even manually) but cannot connect to the vehicle.
i ran a caesar test and here are the results:
SDconnect Toolkit - device diagnostic - Part D
Page 1 of 1
SDconnect Toolkit - device diagnostic
CAESAR STOS+ Rev.:2.12 from Jun 16 2005 generated protocol file from 17.12.2018 09:58
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
Authorization Level 3 Part D
Hardware Authentification 010202
Hardware Date 041900
Special EEPROM check : D2
Special EEPROM check: Inst. date registered ... 0 Ok
D2 Special CAN Test : Special Test ... 0 Ok
CAESAR version check : D2CheckSNVER ... 0 Ok
User is Daimler-Benz AG User Authentification 1
Classification 0
Authorization Level 3
Part D
Hardware Authentification 010202
Hardware Date 041900
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 ... 0 Ok
D2 UART1/2 ... 0 Ok
D2 ADC ... 0 Ok
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 11.8 V
D2 Power Ignition ... Voltage KL15 = 00.3 V
D2 Voltage K-Lines : D2 State K-Lines (35) ... Total 1 (+), 34 (-)
Testresult for Part D:
I changed the bin files to the d2,d,and t as well as the calfix872 for d2,d,and t. Changed com port from 1 to 2 in bios, no change either. Changed baud rates no connection too. With the d2 configuration it proceeds one screen after it disconnects, saying i should manually choose the data. All it reads is voltage. I proceed and it cannot read any units. With the T configuration it doesnt disconnect but the unlock icon changes to locked, and then an error appears. (applied also the blacklist patch for the 9/2014 installation).
Any help please?
Last edited by alex1313; 28th December, 2018 at 09:30 PM.
Hello, maybe it will be helpful for someone. I had a error (1.3)-3.515.2005 and i could not connect to any modules in my car W203. The DAS showed only the battery voltage and the serial number of ESP module. I found broken relay in my mux C3 (I attach a picture). Now after change to new everything works good without ESP module (shows the same error). Maybe someone known which relays are responibility about ESP communication?
mux.jpg
i try it repair and replaced this relay but the same problem....cant connect ecu and ezs...but see serial esp control but cant connect....which parts need check?
Here similar problem with SD Connect C4. Older cars like 2000-2003 doesnt work. I get stuck at the screen where it says turn on ignition. Any ideas for this error?
il mio c3 mux errore di comunicazione 501-9565
hanno una soluzione grazie
Does anyone have the pinout from the MAX202CWE to the 19 pin round connector? I'm trying to diagnose this chip to see if that is the reason why this old Part D mux is not communicating with the laptop.
Thank you.
Bookmarks