Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
 |
« Reply #90 on: May 24, 2011, 12:08:08 PM »
|
|
|
Thanks for testing MTX.
It seems as though the EDC15 is not happy receiving any requests until the diagnostic session has been started. I believe this is why the TesterPresent messages are getting rejected. I will make some hacks for the next test release to immediately start the diagnostic session after the communication session has been started.
As for fast init not working, I can think of two things that the EDC15 could be tripping up on. Comparing the NefMoto logic analyzer logs to the log MTX posted a long time ago, it appears as though if the ECU responds in 26ms it will be a good response, but if it responds in 31ms it will be a bad response. When the bad response comes in it is addressed to 0xF4 and not 0xF1. I think what is happening is when we send the StartCommunication message (0x81, 0x01, 0xF1, 0x81, 0xF4), the ECU is timing out on receiving the message or runs into some other problem receiving the message. When it times out or has some other error, it starts detecting a new message starting at the second 0x81 in the StartCommunication message, which causes it to respond to address 0xF4 instead of 0xF1.
If the ECU is indeed timing out on receiving the message, it could be caused by the maximum time for the message, or the maximum time between bytes in the message. I think a good test would be to try to increase the "P2 inter byte time when connecting" from 17 to 19 ms. Hopefully this allows the ECU to correctly receive the message.
|
|
|
|
|
Logged
|
|
|
|
|
DJGonzo
Guest
|
|
« Reply #91 on: May 24, 2011, 09:13:34 PM »
|
|
|
Tony let me know if you need me to do some more testing. Ive been pretty busy but Ill give it a shot again. Actually if there is a way we can sniff K-line traffic we can sniff a professional tool I have here for EDC15 and work off that  |
|
|
|
|
Logged
|
|
|
|
Badnewsmike
Newbie
Karma: +2/-0
Offline
Posts: 10
|
|
« Reply #92 on: June 22, 2011, 11:43:14 AM »
|
|
|
Thanks for testing MTX.
It seems as though the EDC15 is not happy receiving any requests until the diagnostic session has been started. I believe this is why the TesterPresent messages are getting rejected. I will make some hacks for the next test release to immediately start the diagnostic session after the communication session has been started.
As for fast init not working, I can think of two things that the EDC15 could be tripping up on. Comparing the NefMoto logic analyzer logs to the log MTX posted a long time ago, it appears as though if the ECU responds in 26ms it will be a good response, but if it responds in 31ms it will be a bad response. When the bad response comes in it is addressed to 0xF4 and not 0xF1. I think what is happening is when we send the StartCommunication message (0x81, 0x01, 0xF1, 0x81, 0xF4), the ECU is timing out on receiving the message or runs into some other problem receiving the message. When it times out or has some other error, it starts detecting a new message starting at the second 0x81 in the StartCommunication message, which causes it to respond to address 0xF4 instead of 0xF1.
If the ECU is indeed timing out on receiving the message, it could be caused by the maximum time for the message, or the maximum time between bytes in the message. I think a good test would be to try to increase the "P2 inter byte time when connecting" from 17 to 19 ms. Hopefully this allows the ECU to correctly receive the message.
what ever happened with the diesel ECU stuff, ive been trying to work with my 01 jetta ALH and i cant connect...  |
|
|
|
|
Logged
|
|
|
|
lulu2003
Full Member
Karma: +11/-1
Offline
Posts: 242
|
|
« Reply #93 on: June 24, 2011, 06:55:33 AM »
|
|
|
I though NefMoto Flasher won't work with Galletto OBD Cables?! Here is your logs for slow init: 13/May/2011 07:20:57.777: LOG: Opened FTDI device.
13/May/2011 07:20:57.781: LOG: FTDI device info - Description[b]: F.lli Galletto ECU Flasher[/b] Serial Number: xxx Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
13/May/2011 07:20:57.783: LOG: FTDI ChipID DLL is loaded, checking chip ID...
13/May/2011 07:20:57.787: LOG: Unable to read FTDI device chip ID
13/May/2011 07:20:58.055: USER: Validated FTDI device is in dumb mode.
13/May/2011 07:20:58.199: LOG: Starting send receive thread.
13/May/2011 07:20:58.237: LOG: Send receive thread now started.
13/May/2011 07:20:58.243: USER: Disconnected
13/May/2011 07:20:58.263: LOG: Set timing parameters to defaults.
13/May/2011 07:20:58.283: USER: Connecting...
13/May/2011 07:20:58.342: USER: Starting slow init connection.
13/May/2011 07:21:00.961: USER: Connecting to address 0x01.
|
|
|
|
|
Logged
|
|
|
|
passuff
Jr. Member
Karma: +3/-9
Offline
Posts: 48
|
|
« Reply #94 on: July 18, 2011, 09:35:49 AM »
|
|
|
I would like to support EDC15 developement. Besides my edc15V+ ecu I have tools like this: -saleae logic analyzer -vag kkl -kwp2000 plus Here is a log of Version 1.8 connecting with 10400 baud slow init: (works) 18/Jul/2011 06:32:06.194: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
18/Jul/2011 06:32:06.207: LOG: Opened FTDI device.
18/Jul/2011 06:32:06.208: LOG: FTDI device info - Description: VAG KKL Serial Number: CARL007 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
18/Jul/2011 06:32:06.209: LOG: FTDI ChipID DLL is loaded, checking chip ID...
18/Jul/2011 06:32:06.210: LOG: FTDI device chip ID: 0x99BDEED9
18/Jul/2011 06:32:06.219: USER: Validated FTDI device is in dumb mode.
18/Jul/2011 06:32:06.222: LOG: Starting send receive thread.
18/Jul/2011 06:32:06.223: LOG: Send receive thread now started.
18/Jul/2011 06:32:06.225: USER: Disconnected
18/Jul/2011 06:32:06.233: USER: Connecting...
18/Jul/2011 06:32:06.239: USER: Starting slow init connection.
18/Jul/2011 06:32:08.841: USER: Connecting to address 0x01.
18/Jul/2011 06:32:11.051: LOG: Read incorrect sync byte, guessing baud rate is actually 9600.
18/Jul/2011 06:32:11.111: USER: Slow init succeeded.
18/Jul/2011 06:32:11.118: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
18/Jul/2011 06:32:11.120: USER: Switching to KWP1281 session.
18/Jul/2011 06:32:11.565: LOG: KWP1281 read block
18/Jul/2011 06:32:11.635: LOG: KWP1281 sent block
18/Jul/2011 06:32:11.757: LOG: KWP1281 read block
18/Jul/2011 06:32:11.823: LOG: KWP1281 sent block
18/Jul/2011 06:32:12.001: LOG: KWP1281 read block
18/Jul/2011 06:32:12.073: LOG: KWP1281 sent block
18/Jul/2011 06:32:12.213: LOG: KWP1281 read block
18/Jul/2011 06:32:12.286: LOG: KWP1281 sent block
18/Jul/2011 06:32:12.354: LOG: KWP1281 read block
18/Jul/2011 06:32:12.426: LOG: KWP1281 sent block
18/Jul/2011 06:32:12.427: USER: KWP1281 connect info: 038906012AH 1,9l R4 EDC 0000SG 2705 z?
18/Jul/2011 06:32:13.943: USER: Connecting to address 0x01.
18/Jul/2011 06:32:16.100: USER: Slow init succeeded.
18/Jul/2011 06:32:16.103: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
18/Jul/2011 06:32:16.105: USER: Switching to KWP2000 session.
18/Jul/2011 06:32:16.108: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
18/Jul/2011 06:32:16.460: LOG: Sent message with service ID StartCommunication
18/Jul/2011 06:32:16.461: USER: Sending start communication request.
18/Jul/2011 06:32:16.503: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:32:16.504: LOG: Received negative response for service ID: StartCommunication, with response code: SubFunctionNotSupported_InvalidFormat
18/Jul/2011 06:32:16.504: USER: Connected
18/Jul/2011 06:32:18.991: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:32:19.045: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:32:19.046: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
18/Jul/2011 06:32:21.521: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:32:21.564: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:32:21.565: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
18/Jul/2011 06:32:24.050: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:32:24.103: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:32:24.104: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
It works, but I can't go further (dtc /flash) log: 18/Jul/2011 06:34:19.135: USER: Disabling Windows sleep mode.
18/Jul/2011 06:34:19.138: USER: Reading ECU flash memory.
18/Jul/2011 06:34:19.143: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
18/Jul/2011 06:34:19.170: LOG: Sent message with service ID ReadECUIdentification
18/Jul/2011 06:34:19.224: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:34:19.225: LOG: Received negative response for service ID: ReadECUIdentification, with response code: UnknownEDC15ResponseCode
18/Jul/2011 06:34:19.227: USER: Failed to read ECU identification information.
18/Jul/2011 06:34:21.699: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:34:21.746: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:34:21.748: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
18/Jul/2011 06:34:24.227: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:34:24.265: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:34:24.266: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
18/Jul/2011 06:34:26.755: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:34:26.806: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:34:26.808: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
18/Jul/2011 06:34:29.283: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:34:29.326: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:34:29.327: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
18/Jul/2011 06:34:31.819: LOG: Sent message with service ID TesterPresent
18/Jul/2011 06:34:31.865: LOG: Received message with service ID NegativeResponse
18/Jul/2011 06:34:31.867: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode If I can do anything to help you developing let me know.. |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #95 on: January 06, 2012, 05:28:46 PM »
|
|
|
If people are interested in getting NefMoto to support EDC15, let me know, and we can start doing some testing again.
It would be great to get a logic analyzer recording of a working tool talking to this ECU using the KWP2000 protocol. This ECU isn't responding nicely to the standard KWP2000 protocol as I know it.
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #96 on: January 08, 2012, 04:57:09 AM »
|
|
|
Tests I have done with EDC15V have shown that this ecu does not use standard kwp2000 protocol. I've attached the saleae logic file showing the wakeup & identification process of this ecu. Initial wakeup is done at 10400 fast init but identification is send at 9600 with different packet format.
|
|
|
|
|
Logged
|
|
|
|
jonixins
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #97 on: January 09, 2012, 12:06:35 AM »
|
|
|
I don't know if it helps, but I have found out procedure to do when my crappy clone galletto do not connect to EDC15V or P.
I connect ECU old vag-com, read faults, swap cable to galletto and try. Usually it works.
|
|
|
|
|
Logged
|
|
|
|
passuff
Jr. Member
Karma: +3/-9
Offline
Posts: 48
|
|
« Reply #98 on: January 09, 2012, 04:05:51 AM »
|
|
|
I'm very interested in an EDC15 solution. Even more in the logguning solution, but I think therefor someone has to disassamble the edc15 first.
But I can help with saleae logs and I own a edc15v ecu with flash emulator (OLS16). So if I can help, just let me know!
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #99 on: January 09, 2012, 07:07:06 AM »
|
|
|
I've already worked on EDC15V/P to make the tunerpro checksum plugins and have pretty much all of the info needed to flash EDC15P but don't have the ecu for testing. If anybody has one that he is willing to sell "low cost" I will work on a free software solution.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #100 on: January 09, 2012, 12:13:27 PM »
|
|
|
Tests I have done with EDC15V have shown that this ecu does not use standard kwp2000 protocol. I've attached the saleae logic file showing the wakeup & identification process of this ecu. Initial wakeup is done at 10400 fast init but identification is send at 9600 with different packet format.
Your log shows that you do a fast init, and get no response, and then you do a slow init. The key bytes you receive for the slow init are KWP1281 key bytes though. Currently the NefMoto software seems to run into problems after sending a StartCommunication message after doing the double slow init to get a response with KWP2000 key bytes. I suppose I could skip sending the StartCommunication message when connecting with a double slow init. One thing I am confused about though, is when the ECU sends a negative response to the StartCommunication message, it sends an undefined response code... I believe that I may also need to send a StartDiagnostic session message before sending any other types of messages. Although, it may look that way because the StartCommunication message is making the ECU angry. I will try to put together a test release that doesn't send the StartCommunication message when connecting with a double slow init. |
|
|
|
« Last Edit: January 09, 2012, 12:18:03 PM by Tony@NefMoto »
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #101 on: January 09, 2012, 12:39:48 PM »
|
|
|
That log & bin file for EDC15V was kindly given to me by a person I am in contact with on skype, he logged communications while doing an identification procedure with a tool (I don't remember which exactly...)
I am not sure but I have the feeling that maybe older EDC15V might be using KWP1281 while some of the later models use KWP2000. This would explain why they first try Fast Init. and when they don't get a reply try again in KWP1281...
|
|
|
|
|
Logged
|
|
|
|
passuff
Jr. Member
Karma: +3/-9
Offline
Posts: 48
|
|
« Reply #102 on: January 09, 2012, 12:41:49 PM »
|
|
|
It was me. I did the log while connecting with KWP2000Plus tool...
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #103 on: January 09, 2012, 12:43:36 PM »
|
|
|
ok, sorry but I have you on skype with a different name |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #104 on: January 09, 2012, 01:55:05 PM »
|
|
|
I just ordered a 2000 VW Jetta/Golf 038906012BD 1.9L TDI off eBay for $55 shipped. Will be much easier to test all of this locally.
|
|
|
|
|
Logged
|
|
|
|
|
