Re: KW2000 problem (programming session)

What software do you use? Thats exactly what i'm looking for.

the first dyte describes count of bytes and adressing mode

HM0 No adressing
HM1 ???
HM2 physical adressing
HM3 functional adressing

i think your ECU only accepts functional or physical adressing mode

--- In opendiag@yahoogroups.com, "bitbo2000" <bitbo@g...> wrote:
> Hi All!
>
> I traced a programming session and got strange effects.
> It seems to me that everything works fine until
> a telegram with a leading "03" instead of "8x" is sent
> to the ECU. Then i get framing errors, which could result
> after a baudrate change. Has someone an idea ?
>
> Is the leading "03" a "HM0" telegram and if, where are
> HM0 and HM1 defined ?
>
> Greetz
> bitbo
>
> ----trace-----------------------------------------------------------
-
> 00:00.331.185 81 ISO 14230-3
> 00:00.336.034 01
> 00:00.340.888 F1
> 00:00.345.741 81 ISO 14230-3 StartCommunication
> 00:00.350.592 F4 CRC
>
> 00:00.363.737 83 = 3 data bytes
> 00:00.364.249 F1
> 00:00.364.715 01
> 00:00.365.181 C1 ISO 14230-3 positive reply
> 00:00.365.646 6B
> 00:00.366.112 8F
> 00:00.366.578 30 CRC
>
> 00:00.394.700 82 = 2 data bytes
> 00:00.399.112 01
> 00:00.403.963 F1
> 00:00.408.817 10 ISO 14230-3 StartDiagnosticSession
> 00:00.413.669 85 programmingSession
> 00:00.418.522 09 CRC
>
> 00:00.431.934 83 = 3 data bytes
> 00:00.432.400 F1
> 00:00.432.866 01
> 00:00.433.332 50 ISO 14230-3 positive reply
> 00:00.433.798 85 programmingSession
> 00:00.434.263 2F response code
> 00:00.434.729 79 CRC
>
> 00:00.462.750 82 = 2 data bytes
> 00:00.467.527 01
> 00:00.472.380 F1
> 00:00.477.230 1A ISO 14230-3 ReadECUIdentification
> 00:00.482.084 8D systemSupplierSpecific
> 00:00.486.934 1B CRC
>
> 00:00.501.019 8C = 12 data bytes
> 00:00.501.485 F1
> 00:00.501.950 01
> 00:00.502.416 5A ISO 14230-3 positive reply
> 00:00.502.882 8D systemSupplierSpecific
> 00:00.503.348 30
> 00:00.503.814 31
> 00:00.504.279 32
> 00:00.504.745 33
> 00:00.505.211 34
> 00:00.505.677 35
> 00:00.506.143 36
> 00:00.506.608 37
> 00:00.507.074 38
> 00:00.507.540 39
> 00:00.508.006 72 CRC
>
> 00:00.536.402 82 = 2 data bytes
> 00:00.540.794 01
> 00:00.545.644 F1
> 00:00.550.497 1A ISO 14230-3 ReadECU ID
> 00:00.555.348 8A systemSupplier
> 00:00.560.201 18 CRC
>
>
> 00:00.574.156 91 = 17 data bytes
> 00:00.574.668 F1
> 00:00.575.180 01
> 00:00.575.646 5A positive response
> 00:00.576.112 8A systemSupplier
> 00:00.576.578 56
> 00:00.577.043 34
> 00:00.577.509 2E
> 00:00.577.975 31
> 00:00.578.441 07
> 00:00.578.907 FD
> 00:00.579.373 7F
> 00:00.579.838 00
> 00:00.580.304 00
> 00:00.580.770 00
> 00:00.581.236 00
> 00:00.581.702 00
> 00:00.582.167 E7
> 00:00.582.633 00
> 00:00.583.099 FF
> 00:00.583.565 B9 CRC
>
> 00:00.618.284 03 Is this a HM0 telegram of length 3 ?
> 00:00.622.792 10
> 00:00.627.646 85
> 00:00.632.497 87
> 00:00.637.349 1F
> 00:00.650.879 03
> 00:00.651.345 50
>
> 00:00.651.811 85
> 00:00.652.276 87
> 00:00.652.742 5F
> 00:00.681.899 FF it seems, that somewhere
> 00:00.686.314 FF here is a baudrate change !!!
> 00:00.691.166 FF
> 00:00.696.018 FF
> 00:00.700.871 FF
> 00:00.705.722 FF
> 00:00.710.574 FF
> 00:00.715.427 FF
> 00:00.719.903 Framing error STARTBIT
> 00:00.733.049 FA
> 00:00.740.018 E6
> 00:00.741.026 18
> 00:00.741.073 Framing error STOPBIT
> 00:00.741.108 Framing error STARTBIT
> 00:00.741.539 FF
> 00:00.744.611 16
> 00:00.746.002 98
> 00:00.754.560 04
> 00:00.755.971 FA
> 00:00.759.735 85
> 00:00.759.782 Framing error STOPBIT
> 00:00.760.199 2C
> 00:00.760.246 Framing error STOPBIT
> 00:00.760.667 04
> 00:00.760.714 Framing error STOPBIT
> 00:00.761.132 8C
> 00:00.761.179 Framing error STOPBIT
> 00:00.761.600 54
> 00:00.761.647 Framing error STOPBIT
> 00:00.762.065 CE
> 00:00.762.147 Framing error STARTBIT
> 00:00.762.173 Framing error STARTBIT
> 00:00.762.574 4E
> 00:00.762.621 Framing error STOPBIT
> 00:00.763.042 16
> 00:00.763.089 Framing error STOPBIT
> 00:00.763.131 Framing error STARTBIT
> ----and so on------------------------

 
Received on Fri Nov 28 13:19:13 2003