Yes, it can. I use K+ Dcan.
Yes, it can. I use K+ Dcan.
Col19 (18th November, 2019), jo?o antonio (7th May, 2015), speedy100 (7th May, 2015)
Col19 (18th November, 2019)
I use the K+ Dcan with CASCADE on older cars, which usually do not have CAN.
Ok Mate, thanks for the reply.
tomorrow I will ordered one to buy, ( IMPA ) bmw K+CAN D+CAN, Silver cable.
IMPA-EDIABAS BMW , anyone can confirm if it works with separated protocol, example :
K line ( for old cars )
K +can ( new cars )
K+ Dcan ( cars 2008 )
speedy100 (2nd June, 2015)
For K Line diagnostic using KKL 409:
"
- No automatic pin switching. The original device?s diagnostic interface is able to connect to ECUs with the K line on pins other than 7 on the OBD connector. The low-price USB interfaces used with CASCADE do not have that capability, so it may be required to physically modify the USB interface in order to be able to connect to such ECUs. "
Also diagnostic cable should have FTDI chip inside
antonypaul (24th June, 2015), speedy100 (2nd June, 2015)
H? to all, I will buy a IMPA K+Dcan
searching for data base , ROMs for GM Brazil , old cars ( Multec, Bosch, Rochester, Motronic ) systens.
Seems to work on a Peugeot 307 1.6 2008 diesel engine but got disconnected after two seconds ,someone said this is because of a Read only attribute of the cascade folder ,but can t manage to change the attribute ,it remains always Read only ?
Tested with BMW K+DCAN
Hello,
Has anybody any experience with Mercedes 180 (W202) 1998 model? Does this works with these cars and with what cable + adapter for round type plug?
Best Regards
Knowledge is to share... so if I have helped just press [Thank You + Rep.]...
Col19 (18th November, 2019)
I use some sharp pins for K ,L and ground to connect in OBD connector when I don t have the right adaptors .This worked also on 1994 Passat which seems to have some wiring issues so I pinched the wires near ECU
Here you can see the original Carman ,pretty cool tool
Col19 (18th November, 2019)
After a while when I fall in love with Autocom and Cascade was left unused ,Autocom get corrupted or something (VCI not found) so tried again old Cascade on a 2002 diesel Santa Fe CRDI engine .At beginning it didn t connect but after lowering latency in port settings to 1 msec worked like a charm,I am pretty sure it would connect to any other module but interface need pin switching for this .
Spent half a day with a Golf 3 ECU wired on the bench along with an active buzzer between 12 volts and Kline which will buzz whenever is communication .
At final gathered some facts :
-whatever brand / control unit is chosen ,there is ALWAYS communication /attempt to connect .The difference is in time ,it takes a few seconds for asians brands and over a minute for Golf 3 ECU ,so sometimes patience is required .The sign of beginning of communication is the red LED "break" which stay lit during that phase .
After 3 attempts communications is finished and must return to a previous menu and start over again diagnosis
-success rate of connection is almost 0 (zero) for Automatic baud rate ,random for Incremental and almost 100 % for fixed baud rate ,which for Golf 3 seems to be 9600 bits
I think baud rate is the key factor and different values for each car should be tryied.and saved for later use .
-On the bench there were no interrupt communication problem as in real diagnosis often occur ,communication last for about half hour before it drops ,maybe because of user inactivity ?Maybe electrical interference in real diagnosis is the cause of interrupt communication ?
Test made with KKL ,INPA and K+CAN Commander which seem to perform identically ,latency of port set to 1ms ,size of USB buffers (64 to 4096 ) does nt seem to affect something .
thank you, appreciated
Bookmarks