Good I also am having the same problem.
DAS works well but does epidemiology with the car.
Anybody can help me.
Good I also am having the same problem.
DAS works well but does epidemiology with the car.
Anybody can help me.
Last edited by ricar66; 20th April, 2010 at 11:31 PM.
hello,
That Fault from the Com port check it did you change it to com2
Good.
I hereby inform you that already have solved my problem with great help from our contributor Billboard.
Below is the link to see the solution and get file.
http://www.digital-kaos.co.uk/forums...3/index32.html
i hope its work
I have same problem and Im using a usb to rs232 db9 with no IRQ , because this converter dont need it, so my problem is the com port I understand we need a real comportfo DAS, I have in another laptop a PCMCIA rs232 db9 and das 0309 and is working fine, I need to know if there is a configuration to change in das in order to make it work with a usb adapter, any help will be apreciated.
Without any reason, with latest addons already installed, today my 03-2010 system send me ERROR: (1.1)-1.501.9551 with mux powered and ERROR: (1.1)-1.501.9503 with mux without power
and into test:
device '0 (-1) isn't in state available
error
Device: Part D
Toolkit-Resultcode: -1
I change the cables,with same results.
I change the laptop with 2008 DAS and tell me:
Check serial ... 0 Ok
CAESAR HW Detection :
D2Access ... 0 Ok
D2DownLoad ... 104No download possible
I open the mux, all voltage seams OK.
My mux just died?
Thanks,
Last edited by trigital; 15th July, 2010 at 03:18 PM.
I have same problem: Multiplexer connection failure 9550. Ceasar is test is ok. Have try changed paltform = W->D->D2
Please anything to do?
DAS will nor work with USB->serial cards (using Prolific drivers).
Try to find a "real" comport card. The best and most compatible chipset I found is Oxford chipset.
So get a real COP port PCMCIA / Express card - They are a little more expensive but they will work !!!.
All the best
G.
I do not think your mux has "died".
104 fault is Serial Port/Serial Cable / Mux communication fault (to the best of my knowledge!)
I was faced with this problem (i.e. get this error ob CAESAR test ) however my Mux was and is working fine. It remains a mystery why D2DownLoad gives error 104
All the Best
G,
P.S. Is your mux diagnosing Ok ?? or do you have a problem ??
What type of serial port are you using ??
No, I cant connect Mux diagnosticsl. Ceasar Ok? I use normal rS232 serial port with IBM T30.
Ceasar test:
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 23.07.2010 13:53
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 ... 0 Ok
D2 Display Power Supply :
D2 Power Battery ... Voltage KL30 = 11.6 V
D2 Power Ignition ... Voltage KL15 = 11.5 V
D2 Voltage K-Lines :
D2 State K-Lines (35) ... Total 3 (+), 32 (-)
Everything seems to be Ok and theoretically !!! you should be Ok.
Have you tried a different set of cables ??
Also have you installed the fixes by Zolookas ? (copy the three files cal.ini, c32s.dll, lic.sli)
Did you ever run DAS with the Mux connected before copying above files ?
Also try another key for DAS.
and we will always be here to try to help !!!
Thank you. I have tested mux/cables with other older hdd and it worked wit it. Noe older version is formated and new installed over it..
I have tryed many fix files. Have also tryed change cal.ini platform W => D, D2 .. I will try other das key. Xentry gives same error. Is bin folder same for das and xentry?
EDIT:
ZADAA! It works. Both DAS and Xentry!
First I changed star developer key. After that it gived error 872. After that I changed cal.ini PLATFORM = D -> D2. Then it started to work. My Serial Port settings are now:
-Com 2
-115200 bit/sec (why ceasar detect 19200??)
-Fifo enabled
-Resources [x] Automatic settings
P.S. Now I need to install some Wis or Asra or EPC net. What do you prefer and witch is easy to install? Is Wis possible to full Finnish language?
Last edited by simppa80; 23rd July, 2010 at 05:47 PM.
Bookmarks