perdikoula888
Banned
- Joined
- Feb 19, 2006
- Messages
- 66
Hi everybody,
I bought an original MB caesar Actia multiplexer a few months ago. However I still have a few problems making the multiplexer to communicate with my laptops and my car. I have tried a few dell and vaio laptops (6 laptops altogether). I have not tried a thinkpad yet (i do not own one) however I doubt if this will make any difference. Dell laptops are pretty steady, reliable and compatible.
I am using DAS 02/2006
Serial rs232 Configuration:
Com port 6 (I have tried all ports from 1 up to 6)
Bits per second: 19200
IRQ: 04
I/O Range: 03E8 03EF (I have tried also 03F8 03FF)
All the rest of the settings as default.
All I get is 3 different errors at different times when I choose w203 in the model series selection page in DAS:
1) Fault (1.1)-1.501.9323
Intitialization of diagnosos multiplexer failed. Possible causes: The link between the diagnosis multiplexer and the diagnostic socket is interrupted. The link between the diagnosis multiplexer and the diagnostic unit is interrupted. The voltage supply at the diagnostic socket (circuit 30 and (or) circuit 31) is faulty.
2) Fault (1.17)-7.870
Internal error: Communication software error (CAL Error number 870). Please contact the STAR DIAGNOSIS call center.
3) Fault (1.13)
Communication error: The RS232 interface of the PC is occupied by another program (e.g. HHT-WIN); please end this program
I have tried also CAESAR self diagnosis with the following results:
CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 29.05.2006 22:58
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 0 Ok
CAESAR Part D2 detected on COM6 with baudrate: 19200
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler-Benz AG
User Authentification 1
Classification 0
Serial Number 02xxxx
Authorization Level 3
Part D
Hardware Authentification 011200
Hardware Date 032001
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 02xxxx
Authorization Level 3
Part D
Hardware Authentification 011200
Hardware Date 032001
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 ... 2003 DSR / DTR lines at UART1 not connected
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 2 (+), 33 (-)
Also I have tried DMI diagnosis without any success. (It fails to communicate)
Could you please forum experts (richard, miro, sunil, steve) spend a little bit of your precious time and help me sort this out? I forgot to tell you that I bought from mercedes the original odb & odb2 cables that connect from the multiplexer to the car. From the laptop side of the multiplexer I am using the serial cable and the converter Sunil supplied. It is a shame having the real thing and not being able to fully utilise it...
I bought an original MB caesar Actia multiplexer a few months ago. However I still have a few problems making the multiplexer to communicate with my laptops and my car. I have tried a few dell and vaio laptops (6 laptops altogether). I have not tried a thinkpad yet (i do not own one) however I doubt if this will make any difference. Dell laptops are pretty steady, reliable and compatible.
I am using DAS 02/2006
Serial rs232 Configuration:
Com port 6 (I have tried all ports from 1 up to 6)
Bits per second: 19200
IRQ: 04
I/O Range: 03E8 03EF (I have tried also 03F8 03FF)
All the rest of the settings as default.
All I get is 3 different errors at different times when I choose w203 in the model series selection page in DAS:
1) Fault (1.1)-1.501.9323
Intitialization of diagnosos multiplexer failed. Possible causes: The link between the diagnosis multiplexer and the diagnostic socket is interrupted. The link between the diagnosis multiplexer and the diagnostic unit is interrupted. The voltage supply at the diagnostic socket (circuit 30 and (or) circuit 31) is faulty.
2) Fault (1.17)-7.870
Internal error: Communication software error (CAL Error number 870). Please contact the STAR DIAGNOSIS call center.
3) Fault (1.13)
Communication error: The RS232 interface of the PC is occupied by another program (e.g. HHT-WIN); please end this program
I have tried also CAESAR self diagnosis with the following results:
CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 29.05.2006 22:58
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 0 Ok
CAESAR Part D2 detected on COM6 with baudrate: 19200
CAESAR version check :
D2CheckSNVER ... 0 Ok
User is Daimler-Benz AG
User Authentification 1
Classification 0
Serial Number 02xxxx
Authorization Level 3
Part D
Hardware Authentification 011200
Hardware Date 032001
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 02xxxx
Authorization Level 3
Part D
Hardware Authentification 011200
Hardware Date 032001
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 ... 2003 DSR / DTR lines at UART1 not connected
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 2 (+), 33 (-)
Also I have tried DMI diagnosis without any success. (It fails to communicate)
Could you please forum experts (richard, miro, sunil, steve) spend a little bit of your precious time and help me sort this out? I forgot to tell you that I bought from mercedes the original odb & odb2 cables that connect from the multiplexer to the car. From the laptop side of the multiplexer I am using the serial cable and the converter Sunil supplied. It is a shame having the real thing and not being able to fully utilise it...

Last edited: