Thanks for the info about the code.

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.

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!

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.

Great info friend. But does this apply to all M382, M383 and M592 Immo II ecus?

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

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

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.