|
elRey
|
 |
« on: March 04, 2011, 11:53:56 AM »
|
|
|
Does the ECU hardware or software? If software, does the flash code specific which protocol? If so, why can we just modify the flash of the KWP1281 ecus to allow use of KWP2000?
Thanks,
Rey
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #1 on: March 04, 2011, 02:29:03 PM »
|
|
|
It is the flash software the controls which protocols are supported. I don't believe the older ECUs contain the code necessary to run the newer KWP2000 protocol.
|
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #2 on: March 04, 2011, 02:52:14 PM »
|
|
|
It would be nice to see if that code could be added to the older ecus since we're modifying the flash anyway.
|
|
|
|
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #3 on: March 10, 2011, 02:46:41 AM »
|
|
|
It would be nice to see if that code could be added to the older ecus since we're modifying the flash anyway.
Which specific ecus are you talking about? Is it an ecu type different of ME7.1/ME7.5 where you want to add KWP2000? If it is an ME7.1/ME7.5, you could provide the binary so I can have a look into it. |
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #4 on: March 10, 2011, 12:29:08 PM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #5 on: March 11, 2011, 04:26:34 AM »
|
|
|
This image definitely contains the protocol implementation for KWP2000. If you can't connect to this ECU using KWP2000, it can be a problem of used communication parameters. The image supports fastinit to address 0x10(physical) or slow init to address 0x11, the following communication should use address 0x10(physical) or headermode 0 (none). Or something on the K-line in the car gets in the way (like the strange behaviour I face in my car). In this case you could try with a separate K-line wire only from ECU to the tester or on the bench. |
|
|
|
|
Logged
|
|
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #7 on: March 12, 2011, 11:33:10 PM »
|
|
|
The image supports fastinit to address 0x10(physical) or slow init to address 0x11,
the following communication should use address 0x10(physical) or headermode 0 (none).
The NefMoto software only uses address 0x01 for fast init with KWP2000, and addresses 0x01 and 0x11 for slow init KWP1281. Adding support for different connection addresses is on the list for future versions. |
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #8 on: March 13, 2011, 08:22:43 AM »
|
|
|
I'm more interested in getting vagcom to connect and log with kwp2000 for higher sample rates. Can the addresses be moved around in the flash to facilitate this and nefmoto's flash software?
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #9 on: March 13, 2011, 05:21:50 PM »
|
|
|
As far as I know, VAG-COM only supports data logging with the KWP1281 protocol.
You could try to manually connect to address 0x11 in VAG-COM though and see what happens.
|
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #10 on: March 13, 2011, 07:52:41 PM »
|
|
|
As far as I know, VAG-COM only supports data logging with the KWP1281 protocol.
You could try to manually connect to address 0x11 in VAG-COM though and see what happens.
I didn't know vagcom had an option to manually connect to an address. Do you have more info on this? |
|
|
|
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #11 on: March 14, 2011, 06:29:14 AM »
|
|
|
This one also has KWP2000 protocol inside and communicates using the same addresses as the first one. Regarding VCDS with KWP2000: I don't think it is a problem of the addresses supported in the image, but you can try to set something under "Options -> TST Addr" in VCDS. What VCDS needs to log data using KWP2000 (Turbo! button) is an intelligent cable (not dumb one) and the readDataByLocalId service for id's 00-9F. The images you refered to do not support this service. In general, I did not find many ME7 supporting this, so I believe that we can log ME7 with VCDS in KWP2000-Mode only for very few ecu's. |
|
|
|
|
Logged
|
|
|
|
carlossus
Sr. Member
Karma: +38/-0
Offline
Posts: 394
Leon Curpa Stg1+
|
|
« Reply #12 on: March 14, 2011, 07:23:34 AM »
|
|
|
Does this mean that Tony's logging software will be similarly restricted to very few ECU's? Tony?
|
|
|
|
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #13 on: March 14, 2011, 07:43:48 AM »
|
|
|
No, this will not be restricted the same way.
VCDS work only with an official logging interface where you specify a group number and
get defined measurement values in return. This official interface exists in general for
KWP1285, but only on a limited number of ecus for KWP2000.
If you read out variables directly from ecu's memory and do the conversion to physical
values yourself, you can log almost any ME7 with kwp2000 protocol (like EcuX).
But the prerequisite is: you must know which variable is located at which memory
address and how to convert from internal to physical values. And this can differ between
the various ecu images.
|
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #14 on: March 14, 2011, 08:08:48 AM »
|
|
|
What VCDS needs to log data using KWP2000 (Turbo! button) is an intelligent cable
(not dumb one) and the readDataByLocalId service for id's 00-9F. The images you refered
to do not support this service. In general, I did not find many ME7 supporting this, so I
believe that we can log ME7 with VCDS in KWP2000-Mode only for very few ecu's. So, how hard would it be to 'add' this needed service to the ME7 ecus? Also, what few ME7 ECUs are you referring to that have the needed service? Thanks, Rey |
|
|
|
« Last Edit: March 14, 2011, 09:35:19 AM by elRey »
|
Logged
|
|
|
|
|
