Pages: 1 ... 4 5 [6] 7 8 ... 10
Author Topic: Diesel ECU?  (Read 103448 times)
mtx-electronics
Full Member
***

Karma: +11/-1
Offline Offline

Posts: 66


WWW
« Reply #75 on: May 07, 2011, 09:43:55 AM »

Both fast & slow init. connect. Fast init. works with minimum 16ms.

Other commands like identifing ECU & DTC stuff don't work.

Logs Attached.
Logged
orienz
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 113


« Reply #76 on: May 09, 2011, 08:53:15 AM »

Hey Tony,

Unfortunately I can't check up on this anymore. My father left (he came for a visit) and it was his Passat TDI with EDC15+.
If I find some other car with diesel ECU I will let you know. I also have an Mercedes E320 CDI but it has EDC16 ECU which uses CAN I think so it won't work I suppose.
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +130/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #77 on: May 09, 2011, 05:50:33 PM »

orienz, no problem with not being able to test. You've already helped a bunch.

mtx, I've got another test release for you. This one has better support for unexpected key bytes, as well as a different format for TesterPresent messages that the EDC15 ECU may like more.

One thing I can recall though, is did we ever test with MonoScan trying to connect to the EDC15 for KWP2000?

Currently I am wondering if we should use the 17ms inter byte time for connecting, but then switch to a shorter inter byte time after we get a StartCommunicationPositiveResponse. The EDC15 ECU seems to keep sending response messages that collide with the testers requests. All I can think is that the long inter byte time may be causing some time outs in the ECU.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
mtx-electronics
Full Member
***

Karma: +11/-1
Offline Offline

Posts: 66


WWW
« Reply #78 on: May 10, 2011, 01:58:50 AM »

Test I have done show that the long inter byte time seems to be needed only for the wakeup, after you can drop timing down at least 9ms.
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +130/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #79 on: May 10, 2011, 10:55:08 AM »

Test I have done show that the long inter byte time seems to be needed only for the wakeup, after you can drop timing down at least 9ms.

That may give us better results. It would have to be a bit of a hack in code though to do that.

Let me know how the current test release fares, and then we can try the shorter inter byte timings after connection next.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
DJGonzo
Guest
« Reply #80 on: May 12, 2011, 10:56:48 PM »

I have an EDC15 on my bench right now. If anybody needs a guinea pig to get some logs or run some tests I'd be glad to do it.
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +130/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #81 on: May 13, 2011, 12:25:25 AM »

I have an EDC15 on my bench right now. If anybody needs a guinea pig to get some logs or run some tests I'd be glad to do it.

Just send me a PM or email and I can send you the latest test release.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
DJGonzo
Guest
« Reply #82 on: May 13, 2011, 05:27:26 PM »

Here is your logs for slow init:
Code:
13/May/2011 07:16:19.605: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.7.1.0
13/May/2011 07:16:25.274: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.7.1.0
13/May/2011 07:20:57.700: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x8F
13/May/2011 07:20:57.777: LOG: Opened FTDI device.
13/May/2011 07:20:57.781: LOG: FTDI device info - Description: F.lli Galletto ECU Flasher Serial Number: 47514789 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.
13/May/2011 07:21:03.193: LOG: Read incorrect sync byte, guessing baud rate is actually 9600.
13/May/2011 07:21:03.253: USER: Slow init succeeded.
13/May/2011 07:21:03.257: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x8A
13/May/2011 07:21:03.266: USER: Switching to KWP1281 session.
13/May/2011 07:21:03.710: LOG: KWP1281 read block
13/May/2011 07:21:03.792: LOG: KWP1281 sent block
13/May/2011 07:21:03.930: LOG: KWP1281 read block
13/May/2011 07:21:04.006: LOG: KWP1281 sent block
13/May/2011 07:21:04.208: LOG: KWP1281 read block
13/May/2011 07:21:04.286: LOG: KWP1281 sent block
13/May/2011 07:21:04.440: LOG: KWP1281 read block
13/May/2011 07:21:04.516: LOG: KWP1281 sent block
13/May/2011 07:21:04.590: LOG: KWP1281 read block
13/May/2011 07:21:04.666: LOG: KWP1281 sent block
13/May/2011 07:21:04.670: USER: KWP1281 connect info: 038906012BD 1,9l R4 EDC G100AG  2507  ?
13/May/2011 07:21:06.912: USER: Connecting to address 0x01.
13/May/2011 07:21:09.135: LOG: Read incorrect sync byte, guessing baud rate is actually 9600.
13/May/2011 07:21:09.195: USER: Slow init succeeded.
13/May/2011 07:21:09.232: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x8A
13/May/2011 07:21:09.669: LOG: KWP1281 read block
13/May/2011 07:21:09.767: LOG: KWP1281 sent block
13/May/2011 07:21:09.905: LOG: KWP1281 read block
13/May/2011 07:21:09.981: LOG: KWP1281 sent block
13/May/2011 07:21:10.183: LOG: KWP1281 read block
13/May/2011 07:21:10.259: LOG: KWP1281 sent block
13/May/2011 07:21:10.413: LOG: KWP1281 read block
13/May/2011 07:21:10.489: LOG: KWP1281 sent block
13/May/2011 07:21:10.563: LOG: KWP1281 read block
13/May/2011 07:21:10.639: LOG: KWP1281 sent block
13/May/2011 07:21:10.642: USER: KWP1281 connect info: 038906012BD 1,9l R4 EDC G100AG  2507  ?
13/May/2011 07:21:12.147: USER: Connecting to address 0x11.
13/May/2011 07:21:14.960: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
13/May/2011 07:21:15.002: LOG: Not enough key bytes, read: 0
13/May/2011 07:21:15.013: USER: Slow init failed.
13/May/2011 07:21:15.018: USER: Disconnected
13/May/2011 07:21:15.076: USER: Connecting...
13/May/2011 07:21:15.110: USER: Starting slow init connection.
13/May/2011 07:21:17.715: USER: Connecting to address 0x01.
13/May/2011 07:21:19.935: LOG: Read incorrect sync byte, guessing baud rate is actually 9600.
13/May/2011 07:21:19.995: USER: Slow init succeeded.
13/May/2011 07:21:20.001: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x8A
13/May/2011 07:21:20.433: LOG: KWP1281 read block
13/May/2011 07:21:20.509: LOG: KWP1281 sent block
13/May/2011 07:21:20.647: LOG: KWP1281 read block
13/May/2011 07:21:20.721: LOG: KWP1281 sent block
13/May/2011 07:21:20.923: LOG: KWP1281 read block
13/May/2011 07:21:20.999: LOG: KWP1281 sent block
13/May/2011 07:21:21.154: LOG: KWP1281 read block
13/May/2011 07:21:21.228: LOG: KWP1281 sent block
13/May/2011 07:21:21.302: LOG: KWP1281 read block
13/May/2011 07:21:21.378: LOG: KWP1281 sent block
13/May/2011 07:21:21.382: USER: KWP1281 connect info: 038906012BD 1,9l R4 EDC G100AG  2507  ?
13/May/2011 07:21:22.887: USER: Connecting to address 0x01.
13/May/2011 07:21:25.027: USER: Slow init succeeded.
13/May/2011 07:21:25.033: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x8F
13/May/2011 07:21:25.038: USER: Switching to KWP2000 session.
13/May/2011 07:21:25.043: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x8F
13/May/2011 07:21:25.429: LOG: Sent message with service ID StartCommunication
13/May/2011 07:21:25.435: USER: Sending start communication request.
13/May/2011 07:21:25.462: LOG: Received message with service ID NegativeResponse
13/May/2011 07:21:25.467: LOG: Received negative response for service ID: StartCommunication, with response code: SubFunctionNotSupported_InvalidFormat
13/May/2011 07:21:25.472: USER: Connected
13/May/2011 07:21:27.939: LOG: Sent message with service ID TesterPresent
13/May/2011 07:21:27.976: LOG: Received message with service ID NegativeResponse
13/May/2011 07:21:27.980: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
13/May/2011 07:21:29.776: USER: Disabling Windows sleep mode.
13/May/2011 07:21:29.782: USER: Reading ECU DTCs.
13/May/2011 07:21:29.793: LOG: Starting diagnostic session type: StandardSession
13/May/2011 07:21:29.797: USER: Starting diagnostic session.
13/May/2011 07:21:29.857: LOG: Sent message with service ID StartDiagnosticSession
13/May/2011 07:21:29.864: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 4 of 7 bytes.
13/May/2011 07:21:29.868: LOG: Expected: 83 01 F1 10 81 14 1A
13/May/2011 07:21:29.873: LOG: Read:     83 01 F1 10 83 01 FF
13/May/2011 07:21:29.877: LOG: Clearing remaining expected echo bytes.
13/May/2011 07:21:29.892: LOG: Could not construct valid message from received data: InvalidChecksum
13/May/2011 07:21:29.897: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x83
13/May/2011 07:21:29.902: LOG: Could not construct valid message from received data: InvalidChecksum
13/May/2011 07:21:29.906: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x01
13/May/2011 07:21:32.915: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
13/May/2011 07:21:32.920: LOG: Discarding first 3 bytes from the receive buffer because a message starts there.
13/May/2011 07:21:32.924: LOG: Received message with service ID NegativeResponse
13/May/2011 07:21:32.930: LOG: Ignoring message with service ID NegativeResponse because it was unsolicited
13/May/2011 07:21:32.935: LOG: Unsolicited negative response, request ID: TesterPresent response code: UnknownEDC15ResponseCode
13/May/2011 07:21:32.939: LOG: Message received no replies.
13/May/2011 07:21:32.944: LOG: Resending message. Send attempts: 2
13/May/2011 07:21:32.984: LOG: Sent message with service ID StartDiagnosticSession
13/May/2011 07:21:33.034: LOG: Received message with service ID NegativeResponse
13/May/2011 07:21:33.038: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: UnknownEDC15ResponseCode
13/May/2011 07:21:33.133: USER: Failed to start diagnostic session.
13/May/2011 07:21:33.140: USER: Received negative message response with code: UnknownEDC15ResponseCode
13/May/2011 07:21:33.204: USER: 100% complete.
13/May/2011 07:21:33.208: USER: Reading ECU DTCs failed.
13/May/2011 07:21:34.596: USER: Restoring Windows sleep mode.
13/May/2011 07:21:35.517: LOG: Sent message with service ID TesterPresent
13/May/2011 07:21:35.574: LOG: Received message with service ID NegativeResponse
13/May/2011 07:21:35.578: LOG: Received negative response for service ID: TesterPresent, with response code: UnknownEDC15ResponseCode
13/May/2011 07:21:36.708: USER: Disconnecting...
13/May/2011 07:21:36.785: LOG: Sent message with service ID StopCommunication
13/May/2011 07:21:36.834: LOG: Received message with service ID NegativeResponse
13/May/2011 07:21:36.842: LOG: Received negative response for service ID: StopCommunication, with response code: UnknownEDC15ResponseCode
13/May/2011 07:21:36.848: USER: Received negative response to StopCommunication request, disconnecting anyway.
13/May/2011 07:21:36.861: USER: Disconnected
13/May/2011 07:21:36.907: LOG: Closing FTDI device.
13/May/2011 07:21:36.922: LOG: Send receive thread now terminated.
Logged
DJGonzo
Guest
« Reply #83 on: May 13, 2011, 05:28:21 PM »

10000 char limit... Didn't feel like making .txt files  Tongue
Fast init
Code:
13/May/2011 07:25:44.687: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x8F
13/May/2011 07:25:44.716: LOG: Opened FTDI device.
13/May/2011 07:25:44.721: LOG: FTDI device info - Description: F.lli Galletto ECU Flasher Serial Number: 47514789 Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
13/May/2011 07:25:44.725: LOG: FTDI ChipID DLL is loaded, checking chip ID...
13/May/2011 07:25:44.728: LOG: Unable to read FTDI device chip ID
13/May/2011 07:25:44.758: USER: Validated FTDI device is in dumb mode.
13/May/2011 07:25:44.763: LOG: Starting send receive thread.
13/May/2011 07:25:44.770: LOG: Send receive thread now started.
13/May/2011 07:25:44.775: USER: Disconnected
13/May/2011 07:25:44.815: USER: Connecting...
13/May/2011 07:25:44.880: USER: Starting fast init connection.
13/May/2011 07:25:44.887: USER: Connecting to address 0x01.
13/May/2011 07:25:47.619: USER: Fast init sent, sending start communication request.
13/May/2011 07:25:47.721: LOG: Message received no replies.
13/May/2011 07:25:47.726: LOG: Failed to send message 1 times, message send failed.
13/May/2011 07:25:47.731: USER: Start communication request did not receive any response.
13/May/2011 07:25:47.742: USER: Disconnected
13/May/2011 07:25:47.770: USER: Connecting...
13/May/2011 07:25:47.834: USER: Starting fast init connection.
13/May/2011 07:25:47.840: USER: Connecting to address 0x01.
13/May/2011 07:25:50.574: USER: Fast init sent, sending start communication request.
13/May/2011 07:25:50.675: LOG: Message received no replies.
13/May/2011 07:25:50.685: LOG: Failed to send message 1 times, message send failed.
13/May/2011 07:25:50.693: USER: Start communication request did not receive any response.
13/May/2011 07:25:50.703: USER: Disconnected
13/May/2011 07:25:50.781: USER: Connecting...
13/May/2011 07:25:50.815: USER: Starting fast init connection.
13/May/2011 07:25:50.823: USER: Connecting to address 0x01.
13/May/2011 07:25:53.559: USER: Fast init sent, sending start communication request.
13/May/2011 07:25:53.660: LOG: Message received no replies.
13/May/2011 07:25:53.668: LOG: Failed to send message 1 times, message send failed.
13/May/2011 07:25:53.673: USER: Start communication request did not receive any response.
13/May/2011 07:25:53.681: USER: Disconnected
13/May/2011 07:25:53.702: LOG: Closing FTDI device.
13/May/2011 07:25:53.722: LOG: Send receive thread now terminated.


I tried reading DTC's with slow init with no luck, but it did connect successfully with slow init.
Edit: Just tried reading and failed as well. Ill run some logs again tomorrow. At least it connects though. That's a start  Smiley
« Last Edit: May 13, 2011, 05:31:19 PM by DJGonzo » Logged
mtx-electronics
Full Member
***

Karma: +11/-1
Offline Offline

Posts: 66


WWW
« Reply #84 on: May 15, 2011, 09:19:18 AM »

Sorry Tony I haven't gotten around to testing the new version, time has not been on my side in the last few days... I'll do some tests wednesday morning and post the logs.
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +130/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #85 on: May 16, 2011, 12:04:12 PM »

Gonzo, thanks for posting the logs. It appears as though the EDC15 does not like receiving tester present messages before the diagnostic session has been setup. I will send you another test release that starts the diagnostic session right after connecting.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
DJGonzo
Guest
« Reply #86 on: May 16, 2011, 01:50:58 PM »

No problem.

Here is slow init again:
http://pastebin.com/pmL4JTm0
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +130/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #87 on: May 16, 2011, 02:57:40 PM »

Gonzo, thanks for the new test. It seems as though my test of sending the start diagnostic session message right away was only setup to work with a positive start communication response, while you got a negative start communication response.

I will send you another test release. Please try with fast init and slow init if possible.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
DJGonzo
Guest
« Reply #88 on: May 16, 2011, 03:02:14 PM »

I will try again in a bit.

There is a swarm of mosquitos in my studio right now and I really don't want to get any more mosquito bites  Grin

BTW if you know any way to get rid of em let me know. Haha
Logged
mtx-electronics
Full Member
***

Karma: +11/-1
Offline Offline

Posts: 66


WWW
« Reply #89 on: May 24, 2011, 08:38:15 AM »

Finally got around to testing release 11 using the default settings. I first tested the fast init. without success and afterwords tested the slow init which worked on the second try, still have issues that ecu id, dtc reading & clearing do not work.

You can see all from the attached log.
Logged
Pages: 1 ... 4 5 [6] 7 8 ... 10
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.024 seconds with 17 queries. (Pretty URLs adds 0s, 0q)