Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #15 on: April 20, 2011, 11:57:12 AM »
|
|
|
If you guys send me a private message with your email, I can send you the test release which may fix the connection issue. Just make sure to mention the EDC15 diesel topic when you message me.
This is a test release because I don't actually know if my timing changes will make any difference.
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #16 on: April 20, 2011, 02:40:54 PM »
|
|
|
No luck again, I sent an email back with another log file.
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #17 on: April 20, 2011, 03:21:04 PM »
|
|
|
Too bad it isn't that easy. I will try to get my hands on my friends logic analyzer again and verify all of connection timings.
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #18 on: April 20, 2011, 04:32:58 PM »
|
|
|
Can i somehow capture what VCDS does when connecting and send it to you?
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #19 on: April 20, 2011, 06:23:26 PM »
|
|
|
There isn't any easy way to capture the connection data because it isn't standard serial RS232 UART data. You need a logic analyzer like the Saleae Logic, or OpenBench Logic Sniffer.
A friend of mine has a Saleae Logic and I should be able to borrow it again to double check the connection timings.
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #20 on: April 21, 2011, 04:41:56 AM »
|
|
|
|
|
|
Logged
|
|
|
|
carlossus
Sr. Member
Karma: +38/-0
Offline
Posts: 394
Leon Curpa Stg1+
|
|
« Reply #21 on: April 21, 2011, 06:23:07 AM »
|
|
|
It looks like that's designed for capturing data, but wont be able to look at the exact timing of the transitions.
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #22 on: April 21, 2011, 01:13:18 PM »
|
|
|
This could capture the data being sent over the USB port, but it wouldn't be able to record the timing of the bits that actually come out of the OBD cable.
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #23 on: April 25, 2011, 08:08:42 AM »
|
|
|
Just tried benchreading EDC15P and it didn't work...VCDS connected fine :/
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #24 on: April 25, 2011, 11:27:25 AM »
|
|
|
I've got my friends Saleae Logic analyzer again, so I will attempt to verify all of the connection timings in the next few days.
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #25 on: April 27, 2011, 02:59:02 AM »
|
|
|
Just to confirm that there is nothing wrong with ECU, i just read and flashed EDC15P using Galletto 1260 clone, worked perfectly.
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #26 on: April 27, 2011, 10:31:37 AM »
|
|
|
I have another test release that will hopefully solve this connection issue. I used a logic analyzer to double check the timings, and I increased the idle time between connection attempts.
|
|
|
Logged
|
|
|
|
Rick
|
|
« Reply #27 on: April 27, 2011, 12:44:18 PM »
|
|
|
Tony,
EDCxx and indeed MEx is used in lots of non VAG cars. Are we likely to be able to communicate with them using your software or are there car specific comms protocols?
Rick
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #28 on: April 27, 2011, 12:48:48 PM »
|
|
|
The slow init, fast init, and KWP2000 protocols are an industry standard and are not just used by VAG. The flashing protocol has some custom manufacturer specific algorithms though like compression, encryption, and security negotiation.
|
|
|
Logged
|
|
|
|
mtx-electronics
|
|
« Reply #29 on: April 27, 2011, 03:49:26 PM »
|
|
|
Recently I made a program to read/write EDC15C7 ecu's and at first I was having a few problems with waking up the ecu. The problems I found were:
1) Sometimes the ecu will not wakeup on the first init. sequence during fast mode so you might have to try 2 or 3 times; 2) The first communication done after init. (in my case Start Communication Service) must have a small delay between bytes sent and when finished you must wait a long delay after you receive the ecu reply before continuing with your next service request, this goes on until you reach the Start Diagnostic Session Service after which you can go full speed no problem. I don't remember of the top of my head the exact delay I used but will check my code and get back to you on this asap.
I don't know if this connection issue you are having with EDC15P is the same issue or not but anything is possible.
|
|
|
Logged
|
|
|
|
|