|
mtx-electronics
|
 |
« Reply #45 on: April 29, 2011, 11:17:15 AM »
|
|
|
I haven't done anything in KWP1281 so don't know much about it.
When do you think you'll have an update to try? I'm curious to see if NefMoto can read/write these ecu's or at least read/clear DTC's. If VW hasn't made any changes in specs. for their implementation of the KWP2000 then probably the only thing that might be different is the security access keys algo.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #46 on: April 29, 2011, 12:37:35 PM »
|
|
|
I just sent you an email with a link to the test release. Please let me know how it works out.
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #47 on: April 29, 2011, 12:57:02 PM »
|
|
|
ok, got the mail. I'm on my way home now so I'll test it asap and get back to you.
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #48 on: April 29, 2011, 01:51:31 PM »
|
|
|
Ok, so now the ecu is waking up in fast mode but they seem to have a few problem talking to each other. Slow init does not work at all.
Nefmoto logs attached.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #49 on: April 29, 2011, 02:12:29 PM »
|
|
|
Thanks for testing that version out. It's good to know that an inter byte time of 20ms works with this ECU. Maybe we can try some other timings between 5ms and 20ms to find some better middle ground. You said that using anything less than 20ms did not work for you?
I'm not sure why the slow init is not working when the VAGCOM slow init does work. If you have time could you record the NefMoto slow init connection with your Saleae Logic? I would like to double check all of the timings.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #50 on: April 29, 2011, 02:35:49 PM »
|
|
|
I forgot to mention that the problems communicating after the fast init succeeds, are likely due to a problem in the NefMoto code that doesn't handle the 20ms between bytes. This is the first time the NefMoto software has ever used an inter byte timing greater than 5ms. I will do some testing myself this weekend to track down what the issue is with this.
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #51 on: April 29, 2011, 03:55:29 PM »
|
|
|
I'll do the logic logs as soon as my wife's laptop is free because it's the only laptop with Vista installed and NefMoto will not allow me to install under XP.
I noticed that when I did the test in fast mode the software once reached the point that it could not understand the reply's just hung there... The grayed out buttons stayed disabled and I had to close the app. to get control back but the application was not frozen, just didn't enable buttons & things.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #52 on: April 29, 2011, 04:25:22 PM »
|
|
|
There are a few bugs in the echo handling code. There currently isn't any time out on trying to read the echo of the data you send. Currently the program assumes that if it sent data, then it should be able to read the echo back in, period.
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #53 on: April 30, 2011, 07:41:02 AM »
|
|
|
This is the 5 baud init. logic file.
|
|
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #54 on: April 30, 2011, 04:05:31 PM »
|
|
|
hey Tony,
Sorry I haven't been able to replay. Been busy for a few days now. The new version you sent doesn't work either.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #55 on: May 01, 2011, 02:02:55 PM »
|
|
|
orienz, and mtx, I just sent the two of you an email with the latest test release.
This release should hopefully work for both fast init and slow init.
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #56 on: May 02, 2011, 01:12:32 PM »
|
|
|
There are still some problems.
|
|
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #57 on: May 02, 2011, 03:02:36 PM »
|
|
|
I can't connect slow or fast init either, sent you an email as well.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #58 on: May 02, 2011, 03:40:03 PM »
|
|
|
MTX, it seems as though there is some noise in the communication.
The slow init says it received a sync byte of 0x85 when it should have received a 0x55.
The fast init says it received a message not addressed to the tester 0xF1. The logic recording shows that the message was addressed to address 0x0. Did the program freeze after this?
Do you get different results if you try to connect without the Saleae Logic attached?
Would you be able to get a logic recording of the slow init, because I would like ot see if an 0x85 sync byte really was sent.
|
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #59 on: May 02, 2011, 04:25:18 PM »
|
|
|
yes I have tried without the logic analyzer and have the same result. In the fast init logic file you will see that it seems that the ecu starts replying before nefmoto finishes transmitting the data.. but this only happens when I first boot nefmoto and try to connect, after if I try another connection the ecu correctly waits for nefmoto tx to finish and then replies but the reply is always a negative response. For the slow init. I'll get you a logic log. Actuaaly I did do it but my battery died on me while I was logging  |
|
|
|
|
Logged
|
|
|
|
|
