Re: Bosch EDC15M and KW2000

Elm-Interface uses the fix target adress 01, there is no possibilty
to change it to access different targets. On my Smart CDI (an Bosch
EDG with KWP 2000)it does not work. I looked at the timings, but it
was all OK. I contacted ELM-Electronics, but there was no support and
no update to a working version. So i decided not to spend more time
in that fu**ing chip.

I use the vehicle-explorer (from 0bd-2.de or obd-2.com), it works
very good, but only at fast login. (It also works with Jeff's
Interface)
There is a testing function included, to send individual messages
directly to ecu, but there is a bug in the software, if you choose
another target than 01 you get no connect. So i patched the software
(look for the 01 and replace it by individual target adress) and now
i can connect to all ecus in my car.
But most functions are locked and i do not know, how to calculate the
key with the reveived seed.

--- In opendiag@yahoogroups.com, "Page, John" <John.page@e...> wrote:
> Radix,
>
> I haven't had any success with KW2000 on this ECU, although I am
getting some responses to 01 Mode commands within EOBD (ISO9141), so
I am getting a physical connection at 10400bps OK.
>
> My Elmscan 323 interface uses the default ISO addresses, and as far
as I can tell, the default sequence is:
> byte 1 0x68
> byte 2 0x6A
> byte 3 0xF1
>
> Does this mean that the ECU has a different target address (0x11)
for KWP2000 communications, compared with 0x6A for ISO9141?
>
> John
>
> -----Original Message-----
> From: radix [mailto:juglandis@g...]
> Sent: 17 October 2003 20:45
> To: opendiag@yahoogroups.com
> Subject: Re: [opendiag] Re: 1995 Opel diagnostic strategy change
>
>
> Your EDC15 Bosch is KW2000 OBD-II compliant. 10400 bps, 5 bps low
init
> too (0x33).
> Fast init is the best way: 10400bd, 8,N,1
> byte 1 0x81 format byte+length byte
> byte 2 0x11 target address
> byte 3 0xF1 source address
> byte 4 0x81 data byte
> byte 5 0x04 checksum byte
>
> radix

 
Received on Tue Oct 28 22:52:43 2003