|
Title: TP2.0 Initialization weird response Post by: Cadensdad14 on February 07, 2021, 10:37:06 PM *Problem found* The me7.5 ecu seems to only be running TP1.6.9
i may be out of my league here, but i have a teensy run to a mcp2515 breakout, to pins 58 and 60 on a 1.8t ecu. im sending: 200h 7 01h C0h 00h 10h 00h 03h 01h and im expecting: 201h 7 00h D0h 00h 03h 40h 07h 01h or similar but im getting back: 201h 3 14h D0h A1h ive tried to go through the FR looking for what's going on, but my german is non existent. Thank You for any help Title: Re: TP2.0 Initialization weird response Post by: Cadensdad14 on February 08, 2021, 02:52:36 PM Ive realized im having an issue with my RTR bit and setting it in my system. I thinking I'm sending yhe wrong one and getting something like an ack response and not the right response
Title: Re: TP2.0 Initialization weird response Post by: Cadensdad14 on February 08, 2021, 06:57:07 PM so 0x14 appears to be a responseTooLong code.
This response code shall be reported by the server if the response to be generated exceeds the maximum number of bytes available by the underlying network layer. Still stuck but trying Title: Re: TP2.0 Initialization weird response Post by: seishuku on February 14, 2021, 10:53:11 AM I get an identical response on my 018CM ME7.5 ECU, I would guess that over the CAN bus it doesn't fully support a KWP2k diagnostic session like it does over K-line.
I'm actually surprised that it responds at all, I would have at least expected a negative response instead of "responseTooLong". But as far as I knew, the CAN on the ECU and other modules in this era is only for internal data transfer, and just doesn't support a diagnostic session via KWP. |