|
prj
|
 |
« Reply #30 on: February 22, 2013, 04:16:46 AM »
|
|
|
Thanks for the info about the code.
|
|
|
|
|
Logged
|
|
|
|
|
AARDQ
|
|
« Reply #31 on: February 22, 2013, 10:50:49 AM »
|
|
|
The immo-off files in this thread won't work on the me7.1.1 allroads. If you flash one, you'll get a
p1640, EEPROM error.
The attached immo-off has worked for me on four different ME7.1.1 ECUs. All running 4Z907551R or N software. Also worked on a 551S but I had other issues ('programming not finished' error) so can't vouch for consistency. The ME7.1.1 uses a 5p08c3 rather than 95040, but 95040 file does work given that half of the 5p08c3 isn't used. Another option... I can't for the life of me find the thread the file was originally posted in, but credit to whomever modified it to begin with. |
|
|
|
« Last Edit: February 22, 2013, 10:52:51 AM by AARDQ »
|
Logged
|
|
|
|
ddillenger
Moderator
Hero Member
Karma: +641/-21
 Offline
Posts: 5640
|
|
« Reply #32 on: February 22, 2013, 10:57:20 AM »
|
|
|
I flashed every immo-off file I had. Every time, the ecu coding field was all 0's, wouldn't allow changes, and was stuck with the eeprom error code. I finally just Off'd my own bin (don't ask me why I didn't do this to begin with, I just got in the habit of flashing a universal off) and cleared the death code and all was well. The immo-off bin I attached is the one I created, I filled the vin and immo-id portions with placeholders and corrected the sums. In any event, I'm not unfamiliar with the Immobilizer, but this threw me for a loop. I figured why not update the thread as it seems more and more me7.1.1's are being tuned.  |
|
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
|
AARDQ
|
|
« Reply #33 on: February 22, 2013, 11:07:01 AM »
|
|
|
Your way is more correct, immo (sorry, bad pun).
Oh, just remembered, the file I posted will require that cruise be recoded.
|
|
|
|
|
Logged
|
|
|
|
ddillenger
Moderator
Hero Member
Karma: +641/-21
Offline
Posts: 5640
|
|
« Reply #34 on: February 22, 2013, 11:14:36 AM »
|
|
|
Oh, just remembered, the file I posted will require that cruise be recoded.
Try my immo-off next time, It should work without any additional coding. I pulled it from an R-box that read out as S, and modified it accordingly. My goal with this thread is a one stop shop for all me7 Immobilizer research. As such, I'd love feedback on ways to make it better, along with results! |
|
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
|
k0mpresd
|
|
« Reply #35 on: February 22, 2013, 11:19:26 AM »
|
|
|
I flashed every immo-off file I had. Every time, the ecu coding field was all 0's, wouldn't allow changes, and was stuck with the eeprom error code. I finally just Off'd my own bin (don't ask me why I didn't do this to begin with, I just got in the habit of flashing a universal off) and cleared the death code and all was well. The immo-off bin I attached is the one I created, I filled the vin and immo-id portions with placeholders and corrected the sums. In any event, I'm not unfamiliar with the Immobilizer, but this threw me for a loop. I figured why not update the thread as it seems more and more me7.1.1's are being tuned. why would you not use the original bin each time? using a "universal" file is such a bad idea. it will get you in trouble one day. and i think that day was yesterday. it takes about 5 seconds to modify the original bin. |
|
|
|
|
Logged
|
|
|
|
ddillenger
Moderator
Hero Member
Karma: +641/-21
Offline
Posts: 5640
|
|
« Reply #36 on: February 22, 2013, 06:07:07 PM »
|
|
|
why would you not use the original bin each time? using a "universal" file is such a bad idea. it will get you in trouble one day. and i think that day was yesterday. it takes about 5 seconds to modify the original bin.
When you're right, you're right. But to be honest, I'm glad I did run into this. Had I not, I couldn't have written this up. It was a bit frustrating, I'll give you that. |
|
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
cyril279
Full Member
Karma: +12/-2
Offline
Posts: 140
|
|
« Reply #37 on: April 04, 2013, 08:09:08 AM »
|
|
|
24c02 Immo & checksums  |
|
|
|
|
Logged
|
|
|
|
|
eliotroyano
|
|
« Reply #38 on: April 04, 2013, 01:25:34 PM »
|
|
|
24c02 Immo & checksums Great info friend. But does this apply to all M382, M383 and M592 Immo II ecus?  |
|
|
|
|
Logged
|
|
|
|
cyril279
Full Member
Karma: +12/-2
Offline
Posts: 140
|
|
« Reply #39 on: April 04, 2013, 02:45:25 PM »
|
|
|
I don't have the answer to that, this is just an illustration of the patterns of usage that I've seen thus far that have worked. trial and feedback is the best way to know for certain.
|
|
|
|
|
Logged
|
|
|
|
cyril279
Full Member
Karma: +12/-2
Offline
Posts: 140
|
|
« Reply #40 on: April 05, 2013, 11:33:17 AM »
|
|
|
the image was generated to give pictoral reference to the structure of the 95040. If i've crossed up a few details, please let me know, and I'll fix them. cheers  |
|
|
|
|
Logged
|
|
|
|
esilviu
Newbie
Karma: +1/-0
Offline
Posts: 22
|
|
« Reply #41 on: April 24, 2013, 04:17:11 AM »
|
|
|
I have next situation I bought a spare used ME 7.5.10 ECU and I don't have its pin code, I know my original pin code from the ECU I have now on the car. If I install the spare ECU in the car and try to start - the immo will come on . In this particular case is it possible to read over OBD not in bootmode the content of 95040 chip with ArgDub tool ME7_95040 in order to decode the pin from the spare ECU
In other words:
Has somebody succeeded to read the content of 95040 chip with ArgDub tool ME7_95040 over the OBD port from an ECU not matched with the cluster?
|
|
|
|
|
Logged
|
|
|
|
cyril279
Full Member
Karma: +12/-2
Offline
Posts: 140
|
|
« Reply #42 on: April 24, 2013, 04:52:36 AM »
|
|
|
esilviu,
This is a relatively small board, whose members take the time to read through most if not all of the threads.
Posting the same question in different locations within one hour will not help the amount or quality of feedback that you receive.
Post once, give the board some time to respond, and in the meantime, enter "site:nefariousmotorsports.com [your question]" into google for the best results.
I appreciate the specific nature of your question, but most questions about eeprom-over-OBD using argdubs' tool, end in "bench-and-bootmode it"
-Cyril
|
|
|
|
|
Logged
|
|
|
|
esilviu
Newbie
Karma: +1/-0
Offline
Posts: 22
|
|
« Reply #43 on: April 24, 2013, 05:19:06 AM »
|
|
|
Thanks for you fast reply  |
|
|
|
|
Logged
|
|
|
|
automan001
Full Member
Karma: +47/-0
Offline
Posts: 153
|
|
« Reply #44 on: July 10, 2013, 05:20:46 AM »
|
|
|
Next 7 bytes after pin code (0x34-0x3A & copy in 0x44-0x4A) is a immo key which links cluster with ecu. In example above it's 69 D9 38 E6 D3 B2 71. When cluster is bind, same key is stored in the cluster. To make cluster linked with ECU you just need to make these byte sequences equal. Read from cluster and write into ecu without any adaptation. Or read from ecu and write into cluster, but then you will need to rebind your keys  This is very helpful when you try to bind incompatible cluster and ecu or you constantly get an immo error. Instead of just immo off this is better solution. |
|
|
|
« Last Edit: July 10, 2013, 05:26:18 AM by automan001 »
|
Logged
|
|
|
|
|
