|
prj
|
 |
« Reply #15 on: March 06, 2023, 04:20:23 AM »
|
|
|
It was worth a try, but unfortunately it fails to connect to BMW ME7.2 [21:53:45] Connecting using VAG ME7 C167 K-Line (Free) - Advanced... [21:53:52] Reading ECU data... [21:53:52] HW: 0261207106 [21:53:52] Bosch SW: 1037368796 [21:53:52] VAG SW: 011195005A012401 [21:53:52] Checking ECU... [21:53:54] ERROR: Unsupported ECU: Address verification failed. Not that I was expecting it to work, but I had hope  IDK why you had hope. I'm surprised it even went that far. BMW will be loggable with basic protocol soon. This only works on VAG ME7 C167 K-Line, nothing else. |
|
|
|
|
Logged
|
|
|
|
Rick81
Full Member
Karma: +0/-11
 Offline
Posts: 99
|
|
« Reply #16 on: March 28, 2023, 12:03:04 AM »
|
|
|
Hi will this log on the me7 1.1 ecu
Kind regards
|
|
|
|
|
Logged
|
|
|
|
Rick81
Full Member
Karma: +0/-11
Offline
Posts: 99
|
|
« Reply #17 on: March 28, 2023, 12:04:06 AM »
|
|
|
Typo
|
|
|
|
« Last Edit: March 28, 2023, 12:08:24 AM by Rick81 »
|
Logged
|
|
|
|
|
prj
|
|
« Reply #18 on: March 28, 2023, 02:21:21 AM »
|
|
|
Why don't you try?
|
|
|
|
|
Logged
|
|
|
|
Rick81
Full Member
Karma: +0/-11
Offline
Posts: 99
|
|
« Reply #19 on: April 01, 2023, 12:06:12 AM »
|
|
|
I will do. When some one says me7 I assume it's just one model in particular not different versions of me7 .
Thanks for the logger though
|
|
|
|
|
Logged
|
|
|
|
|
IamwhoIam
|
|
« Reply #20 on: April 01, 2023, 04:10:13 AM »
|
|
|
When one says ME7 in general, it means the entire family, including subtypes like ME7.5 ME7.1 ME7.1.1 etc, SMDH
|
|
|
|
|
Logged
|
I have no logs because I have a boost gauge (makes things easier)
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #21 on: April 07, 2023, 02:00:49 PM »
|
|
|
Can you do logger in ECU ST10?
|
|
|
|
|
Logged
|
|
|
|
|
IamwhoIam
|
|
« Reply #22 on: April 08, 2023, 08:47:58 AM »
|
|
|
I know I've asked him to  |
|
|
|
|
Logged
|
I have no logs because I have a boost gauge (makes things easier)
|
|
|
|
prj
|
|
« Reply #23 on: November 16, 2023, 05:21:34 AM »
|
|
|
Since releasing the free functionality of the tool there have been 88 different A2L id's that have been logged.
Today I've added ST10 support, as well as full C167 support for KWP2000 based ECU's. For example VW R32 Mk5, Audi TT 8J, but also Audi A4 8E, and even the A6 4F.
Logging is possible on K-Line and CAN.
This functionality however is in the paid portion of the tool - the VAG KWP - Advanced protocol.
The reason is that I have to generate the definitions manually on demand if they have not been logged before, because there is no ME7Info like tool.
However, unlike the ME7Info definitions these definitions have the complete A2L content.
The method used is the original APR method with the 2C exploit, because it is universal and not dependent on the bootrom.
38400 baud is supported including security access bypass if needed.
The speed of logging on CAN controllers is about the same as K-Line at 10400 baud, which is about half the speed of 38400 baud.
For this reason when connecting to a CAN controller, once the ECU is identified as ME7, it will check if K-Line communication is possible and switch to K-Line for the better speed. If not (eg. A6 4F V8), then the logging is done over CAN.
It is now possible to RAM log nearly all the VAG gasoline cars with the logger since ME7:
ME7, MED9, MED17, MG1, SIMOS8.4, SIMOS8.5, SIMOS16, SIMOS18, SIMOS19.
|
|
|
|
|
Logged
|
|
|
|
|
Blazius
|
|
« Reply #24 on: December 22, 2023, 05:03:42 PM »
|
|
|
So I gave this a go tonight.
Chipsoft Pro cable used. (Already tested with PCMFlash etc.)
After the setup and registration the first connection I left all on Auto baud and auto init. Engine off Ign on
It started going through the connections one by one , none managed to do anything. So after I tried 56000 baud and double slow init 0x01 and it said it started KWP1281 session but then immidietly it times out.
So I gave it a go again on auto baud and init and when it got to double slow 0x01 it did the same thing again.
Now, I would like to say that ME7logger only works with slow-0x00 too not 0x01. Btw I already patched my file manually to connect while engine is running for ME7logger, but I am not sure it made a difference here.
Could you take a look into this, because at the moment it's not working unfortunately and ME7logger remains. Thanks!
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #25 on: December 23, 2023, 12:18:32 AM »
|
|
|
It's your cable, K-Line does not work properly. Get a different one.
KW1281 via J2534 requires the cable to properly follow all the K-Line settings, and if KW1281 session times out then the cable does not.
UCM100 also had problems, but we fixed that with EVC.
Tactrix works out of the box.
|
|
|
|
« Last Edit: December 23, 2023, 12:20:06 AM by prj »
|
Logged
|
|
|
|
|
Blazius
|
|
« Reply #26 on: December 23, 2023, 09:38:00 AM »
|
|
|
It's your cable, K-Line does not work properly. Get a different one.
KW1281 via J2534 requires the cable to properly follow all the K-Line settings, and if KW1281 session times out then the cable does not.
UCM100 also had problems, but we fixed that with EVC.
Tactrix works out of the box.
Since the dawn of time this car only ever worked with slow 0x00 even on blue k line cable ch340/ ftdi(I've got both). Be aware this was originally a non turbo 1.8 car with the most basic ass cluster and nothing was changed except for the ECU ofcourse, but the cluster is still a POS aswell as the k line wiring or however its setup. I'll try with engine running or something see if anything changes. |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #27 on: December 23, 2023, 04:05:04 PM »
|
|
|
Since the dawn of time this car only ever worked with slow 0x00 even on blue k line cable ch340/ ftdi(I've got both). Be aware this was originally a non turbo 1.8 car with the most basic ass cluster and nothing was changed except for the ECU ofcourse, but the cluster is still a POS aswell as the k line wiring or however its setup.
I'll try with engine running or something see if anything changes. Double-slow IS SLOW-0x00. The problem is your cable, it is not following standards according to P1/P2/P3 configuration and because of that it is impossible to complete a KW1281 session. You will never ever be able to connect with this cable through the dash, because that requires completing the KW1281 session first. Get another cable or contact the cable support and ask if they can make a firmware update. There is nothing that can be done with this on logger side. |
|
|
|
|
Logged
|
|
|
|
JeanAwt
Full Member
Karma: +10/-12
Offline
Posts: 241
|
|
« Reply #28 on: December 26, 2023, 01:09:38 AM »
|
|
|
Hello, I too was ready to buy the Chipsoft Pro China too (I have A4 B5 2000). would it be possible to provide a china link for a compatible cable? on aliexpress for example there is openport2 (benz) kwp2000 dual kline? the codiag? thanks
|
|
|
|
|
Logged
|
A4 B5 avant 1.8T 2000 NO QUATTRO
|
|
|
|
prj
|
|
« Reply #29 on: December 26, 2023, 02:35:42 AM »
|
|
|
The tactrix clones should work.
J2534 has no support for KW1281. It is somewhat of a hack to communicate on it.
It is done by setting certain timeouts (e.g. P2) to zero, so that the cable instantly returns every byte that it receives to the PC.
This works fine if the cable is standards compliant, however if it is not, then it ignores the settings and can not work.
That's the case with the Chipsoft. While it reports setting the timeout as successful it does not actually abide by it and continues working as if it was never set.
To even get a successful wakeup the cable has to not ignore the checksum calculation configuration. This was the case with the UCM100 until we fixed it with Axel.
I think most likely the Scanmatik 2 will work too, whether original or clone, as they try to be as standards compliant as possible...
|
|
|
|
« Last Edit: December 26, 2023, 02:40:06 AM by prj »
|
Logged
|
|
|
|
|
