Caesar selftest - please analyse!

[lingnoi]

I am running DAS 11.2010 and while trying to connect to my car I get an error message regarding connection failed. This doesnt happen right away when I connect but after DAS going through some of the "connection steps"...

Here is my Caesar selftest results:


Selfdiagnostic
==============

Device: Part D
Toolkit-Resultcode: 1

SDconnect Toolkit - device diagnostic - Part D
==============================================

CAESAR STOS+ Rev.:2.12 from Jun 16 2005
generated protocol file from 17.12.2010 20:05
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 0298XX
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
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 0298XX
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
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 ... 2500 Error ADC
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 11.3 V
D2 Power Ignition ... Voltage KL15 = 00.3 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 0 (+), 35 (-)

What do you guys think? Actually, the first time I ran the selftest I did not get this ADC error. Then after applying timeout fix and trying to connect to car 1 more time and then running selftest I get the above...

Thanks.

Regards, Leo

[niki85]

look about max192bcp

regards

[lingnoi]

It is an IC or better known as a chip...So it is faulty and needs replaced?

ADC = Analog Digital Converter????

L

[gaiex]

I have the same problem with my mux/DAS, not all the time it works, and have to connect/disconnect cables many times and restart pc!

I have (1.1)-1.501.9302 Terminal 30 and 31 error, then (1.13)-4.115 RS232 in use error.

First Ceaser self test (Das no connection with above errors)

CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 05.02.2011 19:02
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 029866
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
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 029866
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
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 = 25.6 V
D2 Power Ignition ... Voltage KL15 = 25.2 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 9 (+), 26 (-)


Then DAS connection but with the ADC 2500 error but in DAS it connect but give DAS32R2.exe error after.
Then restarted the pc and it worked ok!

Self test while DAS connected and working:

CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 06.02.2011 10:52
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 029866
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
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 029866
Authorization Level 4
Part D
Hardware Authentification 011205
Hardware Date 031205
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 ... 2500 Error ADC
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 14.5 V
D2 Power Ignition ... Voltage KL15 = 14.1 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 3 (+), 32 (-)


What is causing the problems, Mux or DAS software?
If Mux, wich component could cause the problem, the max192bcp mentioned in the above post?

Thanks

[cbp]

look about max192bcp

regards
Thanks niki85, your advice helped me to solve the problem on my MUX !!!!
cheers.

[simppa80]

Hi!

I have problem:

CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 25.08.2012 10:52
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 104 No download possible

Any solution advice?

[tester4]

Thanks niki85, your advice helped me to solve the problem on my MUX !!!!
cheers.
Any cheap source for the specific component (max192bcpw) please?

[simppa80]

Hi!

I have problem:

CAESAR STOS+ Rev.:2.10 from Mar 11 2004
generated protocol file from 25.08.2012 10:52
SystemCheck :
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 104 No download possible

Any solution advice?

Cabels were broken. With other cables works fine.